Just a note, I miss the config.xml for site table of contents management. In my opinion I think we should add this back. (The reason it was removed is to deal with broken links from remote sites, and update the page toc manually)
My premise follows as much: Do everything possible lessing the impact on the writer that writes the docs. - that means, make writing easy in small units - make it easy to manage resources - make it easy to deal with less when writing docs. Currently: - I think its harder to deal with site toc management than it should be - TOC is manually derived by human writing in html file, monolithic resource management adds writing time - I think doc writing should not have to hunt down links. So how I see this impacting writing docs, config.xml allows for easy control over page TOC - it makes for easy site toc management - it makes for easy unitizing of doc writing - Site structure follows folder structure, so writer has to do no thinking on how to deal with doc management. - Solving config.xml remote url site breaking - Simple servlet redirects site request, with entity database, with old link to new link Just a note, I've got other automated site enhancements that use config.xml as the switch manager, although with out it, there is no way to programmatically tell the markdown translator to set that up. My goal in life is to make doc writing easy as possible and I thought config.xml provided one of those puzzle pieces at least in this system and having it gone makes it more challenging at least for me to write docs. Thoughts? Brandon -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/0b7136a9-2045-4dc7-b506-56ad46ccce3c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
