> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Remy Blank
> Sent: Thursday, June 04, 2009 3:16 PM
> To: [email protected]
> Subject: [Trac-dev] Re: Documentation thoughts
>
> Noah Kantrowitz wrote:
> > Two primary counter-points: PDF generation and automated index
> generation.
> > Both are very useful even for user docs.
>
> Fair enough. I have re-read the last "Sphinx" thread and had a look at
> your samples, and I'm ok with ReST/Sphinx for the user docs as well.
>
> Next question: how / when do you want to get the ball rolling again? ;-
> )
Every now and then I get a burst of free time and I convert about 5-10 pages
of docs. Outside of that I would say just look at what I've written as an
example (mostly look at how the index directives and anchors are setup above
each heading) and anyone that wants to convert existing wiki pages or write
something new, go for it. For those without commit-bits, I would just attach
the new files (or patches) to a ticket. If you want work on a doc in a
collaborative style (like the new recipes perhaps), I would recommend doing
them in ReST but not using #!rest processor since that won't support all the
Sphinx-specific notication. Just put in them in a {{{ }}} literal block.
--Noah
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
