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 <[email protected]> wrote: > 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 as >> http://handlebarsjs.com/ >> >> On Mon, Jun 11, 2012 at 6:12 PM, Howard Lewis Ship <[email protected]> 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 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 >>> >>> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
