Hi Paolo,
I think we are getting there, please, Ian share your final structure with us.
The mock-up I'm working on is more about website architecture than content. Specifically, the current Apache CMS documentation is silent on techniques for building larger, more complex sites (without using mvn site or Apache Forrest). The standard site template that's suggested by the CMS documentation uses a simple compile-time server-side include mechanism to, for example, factor out the navigation menu. This is a good idea for keeping the navigation menu in one place, hence minimising maintenance cost as the IA changes, but is a bad idea for managing the complexity seen by the user for a large site.
I joined the site-dev email list at Apache, and asked questions about this, but have so far received no response.
What I'm working on is a compromise solution that uses the navigation SSI as suggested, should play nice with the Apache CMS wiki bookmarklet, and uses progressive-enhancement ideas to provide a good user experience on JavaScript enabled clients, but will also provide something workable in non-JS environments and therefore meets accessibility guidelines.
In part the question I'm trying to answer is: can we have a convenient three, or even four, level navigation hierarchy that plays well with the Apache CMS. The answer to that will help us determine how flat or deep the IA for the site can be. It's somewhat orthogonal to the current debate on content focii.
Ian -- ____________________________________________________________ Ian Dickinson Epimorphics Ltd, Bristol, UK mailto:[email protected] http://www.epimorphics.com cell: +44-7786-850536 landline: +44-1275-399069 ------------------------------------------------------------ Epimorphics Ltd. is a limited company registered in England (no. 7016688). Registered address: Court Lodge, 105 High St, Portishead, Bristol BS20 6PT, UK
