Thanks for all the feedback everyone. I didn't mean to exclude non-committers from providing feedback, all is welcome (just that I do need some committers to +1 this thing, thanks for that).
I've pushed the website and asf-site branches to the official git repo and created the following jira with INFRA if you want to track: https://issues.apache.org/jira/browse/INFRA-15589 Once this is live I will update the "how to release" instructions. If there are any other docs/etc... that I should update lmk. I looked into Tamas's feedback and oddly "github-markup" tool https://github.com/github/markup was working fine to convert the tables however the github site itself was not rendering properly as Tamas highlighted. Very odd. I fiddled with the formatting a bit and now seems to be working properly in both cases (github and jekyll rendering of the site html pages). Thanks Tamas! Patrick On Fri, Dec 1, 2017 at 3:57 AM, Tamas Penzes <[email protected]> wrote: > Hi Patrick, > > +1 is just my non-counting vote. > > Looks really good. > > I've just found some broken tables in the following file: > https://github.com/phunt/zookeeper/blob/website/credits.md > which might be because github's markdown is not the same as other > implementations. > > Regards, Tamaas > > On Fri, Dec 1, 2017 at 1:51 AM, Michael Han <[email protected]> wrote: > > > +1, the new publish process sounds much better. Thanks Pat. > > > > On Thu, Nov 30, 2017 at 5:00 AM, Camille Fournier <[email protected]> > > wrote: > > > > > +1 good idea to get this modernized thanks pat > > > > > > On Nov 30, 2017 2:17 AM, "Patrick Hunt" <[email protected]> wrote: > > > > > > Hi folks. After the issues a few weeks ago during the 3.4.11 release > > trying > > > to get the site published and INFRA no longer supporting CMS I've gone > > > through the effort to look at what other options are available. I > > reviewed > > > a number of other ASF sites and it looks like jekyll with markdown is > > very > > > popular. Additionally INFRA is currently supporting gitpubsub - which > > means > > > that if we can generate a static site and commit the results to git > INFRA > > > will take that and update the live production site. Basic workflow > would > > > then be: > > > > > > 1) manually edit the markdown pages which are the source of the website > > > (similar to what we do today) > > > 2) generate the static website using jekyll, review this as the > "staged" > > > site (locally) > > > 3) once we're happy with it commit/push the changes to the markdown > > source > > > 4) commit/push the changes to the generated/static site content - > > gitpubsub > > > will then push those live to zookeeper.apache.org. > > > > > > This is pretty close to what we are doing today as part of a release > but > > > it's streamlined and takes CMS out of the equation (the old content > > > management which is no longer supported by INFRA). > > > > > > I've converted the current website over to this new model and staged > the > > > change in my personal github repo. Please take a look as I'd like to > move > > > over to this new model soon - let's say about a week from today for > > > feedback. > > > > > > Any committers out there please give this a +1 if you're on board - otw > > let > > > me know your concerns. > > > > > > This would be the source of the website, markdown/jekyll based: > > > https://github.com/phunt/zookeeper/tree/website > > > > > > This is the generated site (html) - pushing this branch would cause asf > > > INFRA to re-publish the site (gitpubsub): > > > https://github.com/phunt/zookeeper/tree/asf-site > > > > > > Notice these are orphan branches (no history aside from the recent docs > > > changes) and both of these branches would live within the > > existing/current > > > zookeeper git repo. So if you clone the zookeeper repo you'll have the > > > website as well - no longer necessary to checkout multiple repos in > order > > > to update the website. > > > > > > Patrick > > > > > > > > > -- > > *Tamás **Pénzes* | Engineering Manager > e. [email protected] > cloudera.com <http://www.cloudera.com/> > > [image: Cloudera] <http://www.cloudera.com/> > > [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image: > Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera > on LinkedIn] <https://www.linkedin.com/company/cloudera> > ------------------------------ >
