I'm not rigidly tied to any approach, but I would like to minimize the overall work involved for the 5.4 doc updates. By my count there are over 160 Tapestry doc pages in the Confluence wiki, not counting redirect pages. By my estimation (just a guess, really) there might be significant changes needed in only about 5% of those pages to have them fully updated for 5.4. Certainly the Javascript, Ajax and Zones, Forms and Validation, CSS and Assets pages will need major updates and in some cases splitting up. Almost all of the rest of the pages are still good, I think.
I'm personally not too interested in spending dozens and dozens of hours on a complete doc migration and cleanup work when I find the existing system pretty good (if not great). But Howard, if the proposed migration to something like Asciidoc and Jekyll is important enough to you for you to spend significant time on, I'm fine with that and will do what I can to help clean things up after the migration occurs. It does seem like more work than anybody is willing to handle right now, though. As another alternative, if you really want to write the documentation updates in something like Asciidoc but can't find anyone willing to write the code for a wholesale doc migration, I'm willing to do the manual work of getting those few pages of updates into the existing Confluence system and doing any formatting and linking and wordsmithing that is needed, if that's the way you want to go. On Mon, Jan 27, 2014 at 2:08 PM, Howard Lewis Ship <hls...@gmail.com> wrote: > Despite the number of bugs hanging around, the big blocker for Tapestry 5.4 > is documentation. > > I don't think I have the patience to continue writing documentation in > Confluence. > > I'm much happier using Asciidoc and using Jekyll as a publishing (and > blogging) platform. > > I've been pursuing this with my own site and think it will work quite > nicely for the Tapestry documentation. > > The main problem would be to extract our current content into a form that > can be used with Jekyll, such as Markdown. > > With Jekyll, each page can be in its own format; my own site does some in > Jade, some in Asciidoc. > > Jekyll is also easily extensible to support some of the features I'd like, > such as a "short" tag for JavaDoc links. > > -- > 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: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
