On Tue, 2014-06-10 at 12:31 +0000, Kiith-Sa via Digitalmars-d wrote: > On Tuesday, 10 June 2014 at 10:42:14 UTC, Sönke Ludwig wrote: […] > > * Are there any other opinions on this? I remember that there > > have been some strong proponents of using DDOC for things, so > > it would be bad if in the end Markdown were to be dropped, > > after all of the work has already been done. Personally I'd > > strongly favor Markdown, though.
Isn't DDoc for generating API documentation is the vein of Doxygen, JavaDoc, etc., and isn't this discussion about generating general (albeit technical) webpages? > Definitely support Markdown. > > DDoc is extremely discouraging/making bad first impression on > newbies, especially for people who want to write web content. > > (But I'd recommend extended GitHub-like markdown if possible, > plain markdown is pretty bare bones. Personally I use > ReStructuredText but I think the GitHub markdown is pretty good > and most potential contributors can already write it without > learning a new format. The Groovy community initially tried using GrailsDoc – not an API documentation system, but a way of writing general documentation that could easily access API documentation. However, the move now appears to be to ASCIIDoc using the ASCIIDoctor toolchain. As for ReStructured Text, I find Markdown beats it for short pages, but it beats Markdown easily for bigger documents. The Sphinx system may not be appropriate for D, but it works very well. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
