-1 from me too. We have far too much invested in Confluence at this point to move off of it when we don't have to. Besides, Jekyll looks like a big step backward in functionality from Confluence.
A quick reminder of just a fraction of the Confluence features we're currently using: 1) inclusion one page inside of others, to avoid duplicating content 2) generating "Related Articles" sections based on labels (e.g. http://tapestry.apache.org/type-coercion.html) 3) Automatic Prev/Next page navigation links based on an ordering of pages in a hierarchy (e.g. the FAQ & Cookbook pages) 4) Automatic "table of contents" listing sub-pages of a page (e.g. on the right side of http://tapestry.apache.org/documentation.html) 5) Automatic link verification 6) Easy publishing without having to drop to a command line 7) Automatic link updates when a page is renamed 8) Email notification of changes I think we need implement the http://www.dankulp.com/blog/2012/03/svnpubsub-for-confluence-sites/ approach as previously discussed. Uli driving the effort sounds good to me, and I'm happy to help. I would rather free Howard to focus on the much more challenging JS rewrite work than the more mundane documentation issues anyway. On Fri, Nov 2, 2012 at 4:21 AM, Ulrich Stärk <[email protected]> wrote: > And I will be happy to explain what the tools do and how to use them and even > drive the effort. > > Uli > > On 02.11.2012 09:19, Ulrich Stärk wrote: >> -1. >> >> We didn't even have a discussion about this, let alone a vote. I'm open for >> whatever documentation >> tool we find does the job best but the sources for the official >> documentation will not be hosted >> somewhere where it's not under the control of the PMC and we won't use a >> technology that not >> everyone has endorsed. Therefore, discussion first, than a vote, than an >> implementation. >> >> Uli >> >> On 01.11.2012 18:10, Howard Lewis Ship wrote: >>> I've taken some initial steps in setting up a Jekyll-based >>> documentation site for Tapestry. >>> >>> https://github.com/hlship/tapestry-site >>> >>> Please contact me if you want to help; I can add you as a committer to >>> the project, or accept patches. I will only grant access to people >>> who have a signed Apache CLA. >>> >>> The big challenge is our existing documentation. It looks like >>> there's some tools for extracting Confluence Wiki to Markdown, but I >>> haven't figured out exactly what they do or how they work: >>> >>> https://svn.apache.org/repos/infra/websites/cms/conversion-utilities/cwiki/ >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
