Am 04.09.13 08:26, schrieb Lukasz Lenart: > 2013/9/3 Steven Benitez <steven.beni...@gmail.com>: >> I'm not sure that this would be a good fit for Struts2, but I'll throw the >> idea out there anyway. >> >> On my current project, we needed a way to have an internal documentation >> site and I am using Jekyll, Github's open source content generator (the >> same engine that powers Github Pages). The actual documentation are stored >> as markdown files in Git (could be in the S2 repository). >> >> http://jekyllrb.com/ > Good idea and we were talking about that - but first we must export > all the docs from Confluence to markdown format, setup comments engine > and so on - lot of work :-) But definitely is worth to engage as the > current ApacheCMS/SvnPubSub mechanism is a bit painful when used with > Confluence ;-) And thus allows contribute patches to documentation :-) > > Anyway, before we can start, docs must contain all the data - not to > be spread throughout the source code (example snippets, tag reference) I love Jekyll myself, +1 on that.
Can we export the docs in some way already? How can this be done? >> A wiki may be better for our purposes, but I think that the barrier to >> contribution needs to be re-worked. I've submitted patches to the code >> before, but to contribute documentation I need to fill out a form, print >> it, scan it, and email/fax it to Apache. Seems like more trouble than it's >> worth, IMO. > C'mon, it's just 5 sec! And opens doors to become committer :-) > > > Regards --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
