<div class="gmail_quote">On Wed, Jan 5, 2011 at 4:15 PM, Uli Fouquet <span dir="ltr"><<a href="mailto:uli@gnufix.de">uli@gnufix.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Basically, we can publish API docs for packages on <a href="http://packages.pypi.org" target="_blank">packages.pypi.org</a> and<br>
enable the intersphinx feature with Sphinx. That would out-of-the-box<br>
enable references like<br>
<br>
:mod:`grokcore.view`<br>
<br>
in arbitrary other docs (for example in groktoolkit docs). So we could<br>
easily link docs from different packages together.<br>
<br>
For referencing more 'descriptive' or prosaic parts of other docs<br>
(contrary to pure code-describing stuff), say a certain 'chapter' of<br>
grokcore.component docs, this wouldn't help. But maybe sphinx has even<br>
some helper for that case and if we stick with the 'API-specific stuff<br>
into package docs, larger stories and tales into groktoolkit docs' it<br>
might even be unneeded.<br>
<br>
We _could_ also publish the docs of packages on <a href="http://grok.zope.org" target="_blank">grok.zope.org</a> and make<br>
intersphinx look it up. But I guess it is much easier to only publish<br>
the explicit groktoolkit docs (and maybe the grok-API aka reference) and<br>
let it link to <a href="http://packages.python.org" target="_blank">packages.python.org</a> which can be updated when a new<br>
release of a package was made.<br></blockquote><div><br>You can use an anchor in grokcore.component docs:<br>.. _mychapter:<br> <br>and you can use the intersphinx feature like this:<br>:ref:`My chapter <mychapter>`<br>
or explicitly say which sphinx you want to link:<br>:ref:`My chapter <grokcore.component:mychapter>`<br><br>Vincent<br></div></div>