Yes, markdown syntax is much better as this xml stuff used by Apache Forrest!
Markdown is just great, let's go for such an approach! What we need is: - better documentation - simple & fast - contributors can send their patches easily - edit with every editor - close to the source repo One approach might be to rename existing README files within source tree to README.md and replace the LICENSE header with a reference. Hyde or Jekyll, I don't know... I prefer minimal dependencies and just a few easy to manage config files. -roger > -----Ursprüngliche Nachricht----- > Von: Jake Farrell [mailto:[email protected]] > Gesendet: Freitag, 25. November 2011 00:12 > An: [email protected] > Betreff: Re: Thrift Web Site > > I took a quick look at Jekyll last night and was able to convert the existing site > over to markdown and get it up and running pretty quickly. I think using > something like Jekyll or Hyde with markdown content would be beneficial > because it would simplify the process for adding new tutorials and other > items. The CMS looks like it will be a good option for static pages that are not > in flux, but with our tutorials and other content needing so much work > keeping the site in source control and getting patches from the community > will allow for us to quickly generate content. Forest is great, but the setup, > configuration and xdoc format is a little more than we currently need. > Keeping it simple so people can easily submit back new pages will help get > our site to where is should be. Here is the jekyll sample I threw together if > anyone would like to take a look, css needs some cleaning up but overall > concept is there > > - Jake > > Site: http://people.apache.org/~jfarrell/ > Source: http://people.apache.org/~jfarrell/jekyll/ > > > > > > On Nov 23, 2011, at 8:31 PM, Jake Farrell wrote: > > > I'm taking a looking to the CMS right now to see what it has to offer, > > if we go down the road of a site generator I think looking at > > something like jekyll would be a good idea. Using a backend of simple > > markdown file and the addition of syntax highlighting via pygments and > > its current use for github pages it should be easy for people to use > > and add content to > > > > -Jake > > > > > > ________________________________________ > > From: Joe Schaefer [[email protected]] > > Sent: Wednesday, November 23, 2011 4:05 PM > > To: [email protected] > > Subject: Re: Thrift Web Site > > > > I'll still throw in my 2 cents for you guys to use the CMS. > > We don't currently support Forrest sites, but a guinea pig willing to > > sort that out would be appreciated. > > > > In any case I'll get you guys on svnpubsub if you decide to still not > > use the ASF CMS. It's important to infra to get you off rsync at some > > point. > > > > > > > > ----- Original Message ----- > >> From: Bryan Duxbury <[email protected]> > >> To: [email protected] > >> Cc: > >> Sent: Wednesday, November 23, 2011 5:02 PM > >> Subject: Re: Thrift Web Site > >> > >> Sounds like a worthy effort to continue. > >> > >> On Wed, Nov 23, 2011 at 1:23 PM, Roger Meier > >> <[email protected]>wrote: > >> > >>> Hi all > >>> > >>> I played a bit around with Apache Forrest and it might be an option > >>> to use it for a new Thrift Web Site. > >>> The homegrown static page generator CMS we have today is difficult > >>> to handle, so we get not that much contributions on documentation. > >>> Apache Forrest provides good formats to manage content and export it > >>> into several formats. > >>> > >>> Here's a first example http://people.apache.org/~roger/thrift/ > >>> > >>> What do you think? > >>> Should I proceed with this? > >>> Is this an option to get better documentation? > >>> Merge Wiki, White Paper, etc. into a Forrest based Web Site? > >>> > >>> -roger > >>> > >>> > >> > >
