On Tue, Nov 9, 2010 at 3:19 PM, Felix Meschberger <[email protected]> wrote: > Hi all, > > We currently use Confluence to maintain our site. At the time this tool > offered IMHO the best cost-value tradeoff between ease-of-use (for those > of us not born with the APT gene) and functionality. > > Last week the fabulous infra guys now put the Apache CMS into life, see > [1]. This basically provides a user-friendly editing environment; > storing files in SVN and automatically generating the site on update. > > Since we always had the debate on Confluence vs. SVN-based site, I would > like to pick this debate up again with the following idea. > > We convert from Confluence to using the new Apache CMS leveraging the > subversion as a versioned store for the site. > > Not only would this give us close to immediate site updates (as compared > to today's 1-3 hours delay) but also more stable updates.
Sounds good. > Finally we could embark on another journey we once discussed in the dark > ages of Sling: Bundle the complete Sling documentation with the actual > Sling downloadable (e.g. as a docs bundle with bundle-resource provided > content). Well, the perhaps too obvious way to go is to host http://sling.apache.org on *Sling*. Maybe an idea for next year's GSoC? -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 22 00 84 76 Quando omni flunkus moritatus!
