only disadvantages I noticed in GH Markdown are feature limitations compared to Pandoc Markdown. e.g. simple / complex table, definitionlist, automatic references, anchors (heavily used in CAS 3.0 Spec for TOC generation), strike-through, caption, etc. Also, newline handling in GH-Pages is awkward compared to other Markdown flavors.
Thats the reason I wrote the CAS 3.0 Spec in Pandoc Markdown and added a README how to convert Pandoc Markdown to PDF (with TOC). Mit freundlichen Grüßen, Robert Oschwald -------------------------------- Pernauer Str. 29 83024 Rosenheim Mobil: 0170/4723788 Tel: 08031/3044769 Fax: 08031/3044791 -------------------------------- Am 06.01.2014 um 17:35 schrieb Marvin Addison <[email protected]>: >> - If I am not mistaken, github pages also through branching allows us to >> maintain versions of the documentation per release. > > There's only one gh-pages branch that gets automatically published to > jasig.github.io/cas. We would have to develop a strategy around that > limitation to support multiple versions getting published. > > Regardless of technical issues, the ability to easily create a > version-specific manual should be a goal of our documentation efforts. > It's more work but our users will thank us for it. > > M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
