> 5). Add installation messages/descriptions to plugins, in backup > files. Probably will make a data value on the site.plugins.whatever > page. Easily retrievable into the plugins completion page. This could > include version numbers perhaps for the .backups. Php files could > define their own version numbers. We just need to set a convention.
What about a site.docs page branch? I created it to compile usage information for the editor. My goal is to provide context help with one icon of the admin panel. E.g. when the editor is working on the page news.2008 the help icon would link to site.docs.news.2008, if it exists, or its closer parent. That's an idea I have in my to-do list. And site.docs would contain only a TOC of all its descendants, a help index. A convention would be needed to let webmaster docs and system docs coexist. A conventional hierarchy under site.docs would let plugin authors to add their own help files to their plugins. It's easy: site.docs.farm.plugins.plugin1 site.docs.farm.plugins.plugin2 Or site.docs.plugins.plugin1 site.docs.plugins.plugin2 I think this is interesting. Cheers, Marcos -- http://alinome.net --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
