As you might know, we had a hackathon this weekend in Augsburg, Germany (http://strutsathon.opensource.io/) where we experimented a bit with available options and requierements.
One of the outcomes was that we may want to start with a "real" user guide that helps to get started and addresses common learning topics. Meanwhile the Confluence docs could stay in place, still containing detailed reference information (which the user guide may link to) and technical information such as security bulletins etc. Thus we could address the general issue of ramping up users to be productive with Struts 2 without the need to throw away confluence for now. Once we have both a reliable lifecycle management for SCM authored content and the intended content itself in place, we can rethink our next steps with / without confluence. For the technical side, two smart guys who joined us at the hackathon started to address this together with Christian and me with research on how Markdown based authored content could be built in our maven environment and how Snippets could be integrated seamlessly here as well. Some work is already open for review now / in near future: https://github.com/organizations/opensourceio - René Am 09.09.13 11:32, schrieb Lukasz Lenart: > 2013/9/4 Steven Benitez <steven.beni...@gmail.com>: >> I know it's the plan to move to Git, but that can't happen soon enough. >> Subversion is like a big cloud of sadness. >> >> On the bright side, it would be great to get a concerted effort at creating >> new documentation. I'd be happy to help. > > One thing to think of when migrating to a new mechanism (i.e. Markdown > and Jekyll) - security. Right now in Confluence I'm able limit access > to some pages by specifying access rights - it's very useful mechanism > when we're preparing a Security Bulletin and Release Notes which > shouldn't be publicly available before patch is ready and we are > releasing new version. > > > Regards > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
