I've been pondering what to do about the current Assets structure in
Weblite. I'm not happy with Assets being associated with a page as they
are at the moment. I'm going to have a bit of a rant here about the
thoughts I've been having. Any feedback is appreciated.
I was thinking of making a global asset library which all pages could
use, but I also wanted to use the Policy system to determine which
assets could be modified by which users.
So I'd like to have resources associated with a hidden page, which can
then have Access Policies associated with it. Resources can then also be
grouped onto resource pages. The resource page can have its own class of
repository node which says which resources that page has, really the
same as the way Assets are associated with current pages. But i'm
thinking these resource pages will not be real pages, only 'virtual
containers' of resources.
I'm thinking of making a Resource Sitetree, stored as resources.xml in
the same directory as sitetree.xml. The repository nodes contained in
this tree would not be in sitetree.xml at all, and would not appear in
any navigation.
I was then thinking of making a resource library usecase, which loads
the resources.xml file in the same way as sitetree.xml is loaded to show
the navigation. When a node in this tree is selected the user will be
able to add / remove resources from that node.
The other thing I thought of doing was making the save usecase for the
content editor, scan the xml for img src and other resources, and then
recording which resources have been used by which pages. Then when a
page is published it will know which resources to copy as well.
Michael R
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
