I posted an amalgam of maven site, bootstrap, and markdown: i.e. maven site generates a bootstrap branded site and doc is written in markdown. It looks like this: http://people.apache.org/~stack/htrace_website/ See issue https://issues.apache.org/jira/browse/HTRACE-19 for the patch and more detail. You all ok w/ this being our first cut at a website?
St.Ack On Thu, Dec 11, 2014 at 2:03 PM, Stack <[email protected]> wrote: > > On Thu, Dec 11, 2014 at 11:34 AM, Jake Farrell <[email protected]> > wrote: > >> cms has its advantages and drawbacks. I've used middleman, jekyll, maven, >> and the cms to generate different ASF sites and so far the one that I >> prefer for use is middleman. Having the ability to use markdown and live >> local dev vs having to push to buildbot (which if down then no site >> updates >> can occur). Example of middleman in use that I did is for mesos or thrift >> (thrift also has a cms version since we tested them all out). we can >> switch >> to whichever variant people are most comfortable with, just need to make >> sure that its documented so any committer can update the site easily >> >> > > Thanks Jake. > > I looked at middlman. It is for 'hand-made' sites. Looks nice. Just > putting our README.md in place of the index.html in default site I got this > http://people.apache.org/~stack/htrace_mm_site/ so markdown works (just > need to read how to get the styling in there). > > On other hand, just doing mvn site got me this far: > http://people.apache.org/~stack/htrace_mvn_site/ which is kinda > attractive. > > I don't have much time for website making. Maybe someone else does though. > Otherwise I'd be inclined toward the one takes the least amount of work. > > Thanks, > St.Ack > > > > >> -Jake >> >> On Thu, Dec 11, 2014 at 2:26 PM, Lewis John Mcgibbney < >> [email protected]> wrote: >> >> > CMS ROCKS >> > >> > On Thu, Dec 11, 2014 at 8:43 AM, Stack <[email protected]> wrote: >> > >> > > How should we do the website? Jake set up the svnpubsub for us so >> we'd >> > > generate the static site and then publish it only, we have no >> 'website' >> > > currently. >> > > >> > > I could do a little fixup and then generate the site with 'mvn site'. >> > > That'd be easy (if ugly). Going forward, changing the website, you'd >> > edit, >> > > stage, and the svn commit to deploy (a minor burden). >> > > >> > > We have a bit of markdown carried over the github deploy. If our site >> > used >> > > 'apache cms' [1][2], we could just put up our little bit of *.md. >> Devs >> > > could just login and edit the site; there would be no build, publish >> > step. >> > > >> > > Jake, is it even possible to move to 'apache cms' post setup? >> > > >> > > Any other opinions out there on how to proceed? >> > > Thanks, >> > > St.Ack >> > > >> > > 1. http://incubator.apache.org/guides/sites.html >> > > 2. http://www.apache.org/dev/cms.html >> > > >> > >> > >> > >> > -- >> > *Lewis* >> > >> > >
