> > > * 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:
the issue is what to do is the documentation for a particular subproject
is again split into multiple directories (ie framework and phoenix atm).
We used to have
phoenix/
menu.xml
overview.xml
bdg-overview.xml
bdg-first-section.xml
bdg-second-section.xml
...
some-section-overview.xml
some-section-first-section.xml
some-section-second-section.xml
...
now we have
phoenix/
menu.xml
overview.xml
bdg/overview.xml
bdg/first-section.xml
bdg/second-section.xml
...
some-section/overview.xml
some-section/first-section.xml
some-section/second-section.xml
...
we do *not* have
bdg/menu.xml or some-section/menu.xml.
What Pete is saying is that he wants to keep it that way. What I said
recently is that it might be nicer to have those files, then reference
them from the phoenix/menu.xml.
- Leo
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
