글쓰기 플랫폼

http://www.talk-with-hani.com/archives/1333

https://www.readthedocs.io/


Penfilp

https://www.penflip.com
http://madebyloren.com/github-for-writers

Dratfin

https://draftin.com/

authorea

https://www.authorea.com/


gitbook

https://www.gitbook.io/

사용사례 : http://www.wired.com/2013/06/cades-witty-headline-here/ https://github.com/HoTT/book

3rabbits

3rabbitz에서 Apache Ants로 PDF 내려받기 : https://www.3rabbitz.com/blog_ko/dc2b8ba89a13bbfb


Digram
http://asciiflow.com
http://weidagang.github.io/text-diagram/
http://www.jave.de/

Toool


http://maven.apache.org/wagon/

문서화 사례



https://github.com/spring-projects/gradle-plugins/tree/master/docbook-reference-plugin


Asciidoc

Spring쪽의 guide문서는 asciidoc 형식을 쓰고 있네요.

https://raw.githubusercontent.com/spring-guides/gs-actuator-service/master/README.adoc




http://spring.io/blog/2013/12/13/spring-s-getting-started-guides-migrated-to-asciidoctor


JBoss 사례
http://pressgang.jboss.org/



https://www.youtube.com/watch?v=R9o-0J2YKZ4


reStructuredText
http://sphinx-doc.org/
http://stackoverflow.com/questions/2746692/restructuredtext-tool-support




https://lobste.rs/s/k7rf9h/which_markup_restructuredtext_vs_asciidoc_vs
http://kaczanowscy.pl/tomek/2011-09/nice-presentations-in-no-time-with-asciidoc-and-slidy



http://blog.ser1.net/2011/06/restructuredtext-vs-asciidoc.html
https://news.ycombinator.com/item?id=8509062 (Pro Git 저자의 Markdown -> Asciidoc )



소프트웨어 업계에서 뿐만이 아니라, 공동으로 작성하고 발전시켜나갈  모든 문서는  이러이러하게 작성되어야하지 않을까.. 하고 꿈꾸던 모습이 있었는데, Orelly 출판사의 Atlas 시스템이 거기에 가장 가까워보인다. Asciidoc을 주요 포멧을 쓴다.

https://atlas.oreilly.com/

http://chimera.labs.oreilly.com/books/1230000000065/ch01.html
Comments