On Fri, Nov 2, 2012 at 9:55 AM, Howard Lewis Ship <[email protected]> wrote: > On Fri, Nov 2, 2012 at 6:17 AM, Bob Harner <[email protected]> wrote: >> -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 > > Jekyll does this, better.
Where's the docs on this? I couldn't find much of anything on Jekyll features and examples, except how it is used to publish a few not-very-polished blogs. I haven't used it, but by looking through the docs it strikes me as very basic. > >> >> 2) generating "Related Articles" sections based on labels (e.g. >> http://tapestry.apache.org/type-coercion.html) > > Jekyll does this, better. > >> >> 3) Automatic Prev/Next page navigation links based on an ordering of >> pages in a hierarchy (e.g. the FAQ & Cookbook pages) > > Jekyll can do this. > >> >> 4) Automatic "table of contents" listing sub-pages of a page (e.g. on >> the right side of http://tapestry.apache.org/documentation.html) > > Not clear about this. > >> >> 5) Automatic link verification > >> >> 6) Easy publishing without having to drop to a command line > > It's not easy. It's incredibly balky, and involves putting fake > updates into multiple pages in order to get them to publish, as well > as manually updating a bunch of elements across many pages (such as > version numbers). And it is slow! It's super easy in my experience, and I think I've done more edits on the Tapestry documentation under Confluence than anybody else. Click Edit, edit the text, click Save. In my experience there is nothing bulky about it. The slowness (which I consider almost inconsequential), is due to the multi-step export process and would be largely alleviated by the http://www.dankulp.com/blog/2012/03/svnpubsub-for-confluence-sites/ approach. The business about having to put fake updates into pages is a consequence of the poor autoexport plugin, not Confluence. The http://www.dankulp.com/blog/2012/03/svnpubsub-for-confluence-sites/ approach reportedly solves this problem cleanly, according to Dan Kulp: "It ALSO keeps track of which pages use {include} and {children} tags and can proper re-render those if the included page changes or the children structure changes. This is a big step above the autoexport plugin that would require a complete site regenerate for these things" As for manually update the version numbers in a lot of places, we could just put the version number in a separate page and include that page in most of the other pages that need it. I'll take care of that. > >> >> 7) Automatic link updates when a page is renamed >> >> 8) Email notification of changes > > GitHub does this. I didn't think we were considering moving to GitHub. > >> >> 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] >> > > I'd be happy for someone to take this off my hands, but the current > system is very constraining. > > Confluence is being end-of-lifed at Apache. Staying on Confluence is > not a long term solution. > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > > --------------------------------------------------------------------- > 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]
