You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Greg Stein <gs...@gmail.com> on 2010/05/15 01:58:10 UTC
community guide
Hey Mike,
What's with linking between sections of the community guide? There are
links like href="#log-messages", but that really should be
href="conventions.html#log-messages". But that might mess up the
one-big-document approach, right?
Is there a Proper solution here?
Cheers,
-g
Re: community guide
Posted by "C. Michael Pilato" <cm...@collab.net>.
On 05/14/2010 09:58 PM, Greg Stein wrote:
> Hey Mike,
>
> What's with linking between sections of the community guide? There are
> links like href="#log-messages", but that really should be
> href="conventions.html#log-messages". But that might mess up the
> one-big-document approach, right?
>
> Is there a Proper solution here?
See r967156. "Proper"? Beats me. But it seems to work well.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: community guide
Posted by "C. Michael Pilato" <cm...@collab.net>.
Greg Stein wrote:
> Hey Mike,
>
> What's with linking between sections of the community guide? There are
> links like href="#log-messages", but that really should be
> href="conventions.html#log-messages". But that might mess up the
> one-big-document approach, right?
> Is there a Proper solution here?
Yeah, I noticed this same thing last week. Would could:
a) convert them all into one-big-document links.
b) stop trying to auto-generate the one-big-document on the fly, and instead
put some tooling in place to generate it from the parts (while massaging
links like this).
c) use JavaScript to post-process the one-big-document on the client side to
fix up those links (ewww...)
d) dispense with the dual approach and just stick with static one-doc or
multi-doc (but not both).
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand