All,

Has any thought been put into leveraging GitHub pages for project
documentation, static site hosting? A lot of www.apache.org is simple
static content, as are project pages. Since a lot of projects are now using
git, and we mirror projects in GitHub, perhaps we can help the individual
projects maintain their site's static content by simply committing to a
gh-pages branch for their project?

Since it's just static content which is still hosted and controlled by ASF,
but simply placed in a way that GitHub can render it from the mirrors, I
don't think there's too many issues of concern, but wasn't sure if
anybody's put any thought into it. I know it would certainly be easier for
some projects than using the existing CMS system with SVN (especially those
otherwise developing exclusively with Git).

It might "just work" today, but I haven't tried it. I'd be willing to work
with INFRA to help experiment with it, though (especially if we wanted to
try out the CNAME feature).

More info: https://pages.github.com/

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii

Reply via email to