Markdown (with Pandoc)
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Markdown and Pandoc
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
some of the docs teams in red hat seem to be using asciidoc. I have no personal experience tho.
-
@WildFlyAS uses AsciiDoc for their documentation: https://github.com/wildfly/wildfly/tree/master/docs …. Looks quite good when "rendered": https://docs.wildfly.org/18/
Kraj razgovora
Novi razgovor -
-
-
reStructuredText with Sphinx for rendering it, is the standard I think these days.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
RestructuredText and a shitload of pandoc
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Really depends on how complex the documentation gets... Sphinx or Pandoc + asciidoc/reStructured text are pretty good, for the high complexity that you rarely need DocBook+Publican works well (used for AppStream, as that was DocBook from the start). For HTML-only, I like MkDocs.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
More seriously? As a document consumer, readthedocs and whatever workflow they recommend. ( .rst and Sphinx?) usually makes me happy.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
readthedocs is just hosted reStructuredText + Sphinx. rST + Sphinx will get you serviceable docs + the alternate outputs you want. Asciidoctor is another viable option. For all other suggestions, the bug hurdle is PDF output.
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.