Re: Documentation generation

For my part, I'm glad that using Confluence for content editing is an option for the short term. Anything else will be a lot more conversion work. On Tue, Jun 12, 2012 at 3:25 AM, Ulrich Stärk wrote: > IFF we converted the documentation to yet another format - which is not > required btw. - I'd

Re: Documentation generation

IFF we converted the documentation to yet another format - which is not required btw. - I'd go with something already supported by the current infrastructure. ATM my choice would be Markdown. Ul On 11.06.2012 18:22, Igor Drobiazko wrote: > I would prefer a JavaScript based template engine, such

Re: Documentation generation

On 11.06.2012 18:12, Howard Lewis Ship wrote: > So what are the details on the required switch away from Confluence? We don't need to switch away from Confluence. Just from the autoexport plugin. Instead we are supposed to use svnpubsub. > > I see notes here: > > http://www.apache.org/dev/cms.html

Re: Documentation generation

I would prefer a JavaScript based template engine, such as http://handlebarsjs.com/ On Mon, Jun 11, 2012 at 6:12 PM, Howard Lewis Ship wrote: > So what are the details on the required switch away from Confluence? > > I see notes here: > > http://www.apache.org/dev/cms.html > > Nothing about a to

Documentation generation

So what are the details on the required switch away from Confluence? I see notes here: http://www.apache.org/dev/cms.html Nothing about a tool to convert Confluence Wiki markup to Markdown. I still think Jekyll http://jekyllrb.com/ is a good candidate for the docs. -- Howard M. Lewis Ship C

Re: Documentation generation location

I've got a cron job running on people that's copying the content over to my home directory. I just need to change that and point it to the tapestry web space. We need to change the maven config though. Ideally we would want to generate all maven stuff in some sub-directory of its own, e.g. /mave

Documentation generation location

What's going to be involved in getting the CWiki documentation to be exported to a proper URL (http://tapestry.apache.org, rather than http://people.apache.org/~uli/tapestry-site/). Also, will the export interfere with Maven generated documentation (i.e., standard reports & javadoc)? I think it's