How about maintaining markdown and let ASF PubSub do the auto-generation job. ASF CMS expects a specific structure (http://www.apache.org/dev/cmsref.html)
IMHO, what ever makes it easy to maintain site, go for it. thanks ashish On Wed, Dec 18, 2013 at 6:55 AM, P. Taylor Goetz <[email protected]> wrote: > It is statically generated from markdown using Jekyll. So merging in the > wiki content should be easy. > > The svn structure isn't set up yet, but I think we only need to create a > "site" directory and push generated content there. Then I think it's just a > matter of generating the site and pushing the "_site" content to svn. > > Thank for the offer to help. I'll take a look tomorrow and let you know > where I stand. > > Taylor > > > On Dec 17, 2013, at 8:07 PM, Ashish <[email protected]> wrote: > > > > Do we have the base svn structure ready? I did this for my other > project, I > > can pitch in. > > There are two options, one is to use markdown and other is to use > > statically generated site. > > > > Let me know and I can spend some cycles on this. > > > > > >> On Wed, Dec 18, 2013 at 6:23 AM, P. Taylor Goetz <[email protected]> > wrote: > >> > >> Another task we need to take care of prior to our first release is to > >> setup our incubator website. > >> > >> I was thinking that initially we just port storm-project.net to conform > >> to the Apache requirements, and integrate the existing storm wiki > content. > >> > >> If anyone has any opinions, etc. or would like to help, please chime in. > >> > >> - Taylor > > > > > > > > > > -- > > thanks > > ashish > > > > Blog: http://www.ashishpaliwal.com/blog > > My Photo Galleries: http://www.pbase.com/ashishpaliwal > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
