flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: AW: AW: [DISCUSS] Switch the site repo to GIT?
Date Mon, 03 Oct 2016 04:39:14 GMT
I poked around a bit more, and remain confused.

-Looks like folks already use Jekyll at Apache.  Is Jekyll different from
gitpubsub or a component of it?
-Is use of Maven to convert source to html an alternative to using Jekyll
or does Maven call Jekyll?
-Does gitpubsub also go to a staging server for final approval before
being "published"?  That's the way our workflow is today and IMO, 99% of
the time it is wasteful.  I'd like to be able to just push html and xml
files straight to the web server.  There's gotta be another way to "stage"
stuff, maybe just in a different folder.
-Is the asf-site branch an orphan branch like GH pages recommends?
-Could each of our code repos also have an asf-site branch similar to what
GH pages recommends?  If so, then maybe we don't have to rely on GH pages
and URLs.  Maybe we can replicate that sort of workflow at the ASF repo
-Having GH pages URLs if you are viewing our code on GH doesn't bother me.
 As long as we have a backup plan if GH becomes 'undesirable'.

IMO, the priorities are:
1) source control for website so we can rollback changes if needed
2) a way to 'prototype' before going live
3) a way to push html files direct to the server.

Whether we use Markdown or AsciiDoc doesn't matter too much to me.  Using
both is ok too, IMO.


View raw message