Mailing-List: contact dev-help@htrace.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@htrace.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com
 designates 209.85.213.176 as permitted sender)
MIME-Version: 1.0
Sender: saint.ack@gmail.com
In-Reply-To: 
 <CANyrgvd3kZQQwaU-=BGa3j0gyGwovsqFTKiOLj_kPJg7c8UAPw@mail.gmail.com>
References: 
 <CADcMMgGOOcT92iLWyyG-cLNXjzseZsDMWbf9D=KijLGFMyXvvA@mail.gmail.com>
	<CAGaRif3UAcJXvBcxps3oKLcjakmzmGTJv_zM5JQ-rLX-yPOuZA@mail.gmail.com>
	<CANyrgvd3kZQQwaU-=BGa3j0gyGwovsqFTKiOLj_kPJg7c8UAPw@mail.gmail.com>
Date: Thu, 11 Dec 2014 14:03:07 -0800
Message-ID: 
 <CADcMMgGu5N1O27GFVZyGKtK3aGUHhqWEKHb-jfmwYhPUQhMBBw@mail.gmail.com>
Subject: Re: Website: mvn generated or apache cms or....
From: Stack <stack@duboce.net>
To: dev@htrace.incubator.apache.org, Jake Farrell <jfarrell@apache.org>
Content-Type: multipart/alternative; boundary=bcaec510194df134160509f7f0e5

--bcaec510194df134160509f7f0e5
Content-Type: text/plain; charset=UTF-8

On Thu, Dec 11, 2014 at 11:34 AM, Jake Farrell <jfarrell@apache.org> 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 <
> lewis.mcgibbney@gmail.com> wrote:
>
> > CMS ROCKS
> >
> > On Thu, Dec 11, 2014 at 8:43 AM, Stack <stack@duboce.net> 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*
> >
>

--bcaec510194df134160509f7f0e5--