Sorry to step in abruptly. Just my 2 cents here; that I suppose it would be easier if we start with porting the existing wiki as much as we can, polishing results and pushing upstream directly. I'd also vote that we exclusively stick to docs relevant to CAS 4 and leave previous version on the wiki. Lets create an umbrella JIRA to capture the migration process and we can communicate via list of JIRA the section we are working on.
Once we move beyond CAS 4, we can brainstorm on appropriate strategies to maintain versions and create individual JIRAs for each change in the doc. Misagh ----- Original Message ----- From: "Jérôme LELEU" <lel...@gmail.com> To: cas-dev@lists.jasig.org Sent: Friday, January 10, 2014 12:07:00 AM Subject: Re: [cas-dev] CAS 4.0 Documentation Hi, OK. Let's go for the GH pages... @Marvin : would you mind writing somewhere the process we need to follow to contribute on the documentation ? I think that we can also use links (in the GH pages) that point to the "old" wiki to ensure a smooth and quick transition. Thanks. Best regards, Jérôme 2014/1/7 Robert Oschwald < robertoschw...@googlemail.com > 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 < marvin.addi...@gmail.com >: >> - 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 cas-dev@lists.jasig.org as: lel...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: mmoay...@unicon.net To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
