> From: Leo Simons [mailto:[EMAIL PROTECTED]] > > > * I want to be able to include/exclude files based on ant > > includes/ecludes > > it is either this or a link crawling machine. Link crawling > has other advantages....should be relatively simple to do though.
Doable. Link crawling makes sure that all links are satisfied correctly. > > * I want to be able to have all the links in menu to be relative to > > base of > > site, not base of page they are in. SO I can put docs in > bdg/foo.xml and has > > all links work gracefully > > so you mean the base for the reference of links in > /phoenix/bdg/menu.xml should be /phoenix and not /phoenix/bdg? > > I'm not too happy with that, I think. I like the idea that > each subdirectory is a separate 'documentation subproject'. Are you saying that you want hard links everywhere? -1 When I generate documentation, and I want to see how it looks, I don't want to be redirected to the main site. I want to see the page I changed, I don't want to be forced to the internet site with every link. I also prefer all the information for a particular subproject to be in its own directory. By that convention, a user can make the appropriate assumption that if they type the project name based on the heirarchy of the project it would match the heirarchy of the site. Example: http://jakarta.apache.org/avalon/excalibur/fortress/ I can be reasonably assured that everything I need is in the proper location: Avalon > Excalibur > Fortress It also makes the breadcrumbs work properly (as they are). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
