Github Pages just serves static files. You have to generate the HTML offline and upload it. Markdown is used extensively around Github, but it's in no way required for Github Pages.
http://nwcpp.org is written in reStructuredText; I use Pelican<http://blog.getpelican.com> to create the HTML. I wrote up <http://nwcpp.org/2013-website-refresh.html>how I created the site. I added a post last night and my workflow looked like this: $ source ~/.virtualenvs/nwcpp/bin/activate # Switch to working copy of https://github.com/nwcpp/pelican-site $ cd ~/src/nwcpp/pelican/ # (MacOS) view the local copy in a browser $ make devserver $ open http://localhost:8000/ $ vim content/2013/2013-05.rst # Refresh browser while tweaking new post $ git add content/2013/2013-05.rst $ git commit -m "May 2013 announcement" $ git push origin master # Automatically update gh-pages branch and push $ make github # Finish $ ./develop_server.sh stop $ deactivate For an experienced Python developer, this is easy stuff. You'd have a similar workflow with Jekyll and other static site generators. I'm not worried about the stability of Github (or Github Pages) for my domain. They raised $100 million last year and they seem to have a good idea of what they're doing. Mike, regardless of what else you decide to do, please register a *seapig* account at Github. I can provide some help in getting a Pelican site up there, if you want. -- /George V. Reilly [email protected] Twitter: @georgevreilly http://www.georgevreilly.com/blog http://blogs.cozi.com/tech On Wed, May 1, 2013 at 9:54 PM, Jim Gray <[email protected]> wrote: > Github Pages is fine if you just need static pages. It works well enough > that I've seen - my blog <http://hackthing.com/> has used it for a while > now because it was easy to deploy to from Octopress. > > I haven't had any trouble deploying other assets (e.g. zipped .py files) > but it might be more circuitous if you're using the Pages generator instead > of Octopress. > > Jim > > > > > > > > On Wed, May 1, 2013 at 9:38 PM, Mike Orr <[email protected]> wrote: > >> The wiki is still down, partly because I forgot about it. The server >> problems ceased when the wiki was turned off, so I'm not inclined to turn >> it on again. I'll put up a static page with the next meeting info... as >> soon as we decide on a next meeting. >> >> I like Kevin's idea of some kind of version-control based, github-ish >> website to replace MoinMoin. We should have a Github account anyway to >> encourage more SeaPIG projects. However, I don't know enough about Github >> webhosting to know whether we want to commit our website to a third-party >> service which may limit what we can effectively do with it. I'm also not >> sure if I like its Markdown-based format. Markdown *is* becoming more and >> more widely used (a commercial publisher has even standardized on it), and >> I guess its syntax is the best of the wiki syntaxes and allows direct HTML >> snippets. So maybe it would be OK. >> >> It's ironic because a version-controlled content with some kind of script >> that converts it to a static HTML site is precisely what Linux Gazette >> used. We resisted a CMS until the end (it was the early 2000s after all), >> but now that several years have passed since its demise and newer paradigms >> have flourished on the Web, several of LG's former editors think that if it >> were (re)started now they'd go the CMS route. And I have been exploring >> Kotti and it's got a lot of neat things, even if it's not fully polished >> yet. But for the SeaPIG's site simple needs, I can see version-controlled >> content with a static HTML converter as being sufficient. If it allowed >> attachments, which we'd need for uploading slides and things. Maybe we can >> talk about it at the next meeting. >> >> In the meantime, would somebody care to design a static home page with a >> place for the next meeting info and a link to the mailing list? >> >> The Mailman list is running fine so it's not as urgent to replace, but it >> will be an issue when I upgrade the OS. (Ubuntu 13.04 is not yet supported >> on Linode, so it won't be right away.) I still like the idea of migrating >> to Google Groups at some point. >> >> The $240 server bill has been paid so I'm still looking for donations to >> help offset it. Not tax-deductibe, bla bla bla. >> >> -- >> Mike Orr <[email protected]> >> > >
