Sum up: Sphynx cool with RST or Python. Sphynx bad with PHP API Documentation.
Ok. 2010/7/30 Jerome Renard <[email protected]> > Kore, > > On Fri, Jul 30, 2010 at 1:34 PM, Kore Nordmann <[email protected] > >wrote: > > > Hi Jerome, > > > > On Fri, 2010-07-30 at 13:26 +0200, Jerome Renard wrote: > > > > > You can check it out here : > > > > > > - http://jrenard.info/utils/zetacomponentsdoc-sphinx/ > > > > > > There are multilple versions of the doc, the contents is the same I > > > just used different templates so you can see different results. > > > > That looks interesting, but the rendering of the RST stuff is done by > > WCV and that would basically require us replacing the whole website > > engine. > > > > Haaaa ok, I see the problem now. > > > > > > I saw that Sphinx also uses docutils + pygments - which I could try to > > use, too, for highlighting the source code. (Docutils are used anyways > > for now) > > > > The major issue with the doc generation are not the tutorials, but the > > API documentation - and afaik Sphinx cannot really help here. > > > > Yes for that part, Sphinx does not really help. > > > > > > The source code highlighting in the generated HTML inside WCV is only a > > minor issue (XPath + php_highlight_source + regexp to link class names) > > and already implemented by Derick for the "old" website. > > > > Ok. > > > > > > The tutorials rendered by Sphinx look really nice, though. We might want > > to borrow some styling ideas from there for the tutorials ;). > > > > He he, feel free to take anything you want ;) > > -- > Jérôme Renard > http://39web.fr | http://jrenard.info >
