ruby.org.au makes most sense to me. +1 for a git-based solution along the lines of jekyll. In the unlikely event of a front-end talent shortage, Octopress provides a lot out of the box: http://octopress.org/
I've just ported my personal site to Octopress, so my entire hosting infrastructure is now an S3 bucket and a CNAME. See: http://www.allthingsdistributed.com/2011/08/Jekyll-amazon-s3.html -- Paul On 08/01/2012, at 6:06 PM, Pat Allan wrote: > > I registered ruby.org.au last night, and we've also got rubyaustralia.org, so > we have a few options. > > -- > Pat > > On 08/01/2012, at 6:00 PM, Ben Schwarz wrote: > >> Perhaps as a reference point, years ago Tim Lucas wrote something to power >> his blog from Markdown files (interestingly, this was before jekyll and >> other people doing such a thing - in a modern sense). >> >> The source is here: >> https://github.com/toolmantim/toolmantim/blob/master/lib/article.rb >> >> I've been using a variant of this to power my site for a few years now. >> >> … Perhaps that could be used as a starting point and adapted as hungry >> developers see fit. Either way it'd be nice to have something straight away >> that 'worked' and could be iterated on by those who cared. Otherwise, jekyll >> is good. >> >> Github as a CMS. >> >> -- >> on the domain issue: why don't we write to jeremy from segpub asking him to >> reconsider his stance. otherwise — new domain. 301 the old site to the new >> domain. >> -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
