How We Build Rubynepal Using Octopress
This is not another getting started with octopress guide, this is sharing of our experience and couple of hacks we did while developing rubynepal, that may be helpful to others.
In the beginning of June 2013, We came up with this idea of building a community website for ruby developers of nepal. We didn’t need to have a full content management features but we needed features like blog support, pages support, ease for deployments and easy contributing mechanism. Finally, we decided to build rubynepal.org with octopress and github pages. With this we could to tap out Markdown without needing a web-based WYSIWYG editor and type a command to send everything up to the free Github Pages service and our whole website would be a github repo, perfect for collaboration.
The docs has pretty neat documentation for installing octopress, configuring setting up github pages. Within few minutes basic website was up at github pages.
Next, themes, we forked this beautiful and responsive theme greyshade and customized it. Upto here we had a basic rubynepal.org up and running.
Now, octopress has its root path that displays the posts ie. essentially blog index, but we needed to have a page instead of blog index. For this, first we moved source/index.html to source/blog/index.html. Then, created a markdown where we wrote what is to be there in homepage. We put all such kinds of markdown inside _partial folder. Then, in source/index.html we got rid of all exsiting code with
1 2 3 4 5 6
This way about.markdown will be rendered in root page while blog index will be available at /blog.
Now we had to put a list of developers and advisors info in members page. One way was to dump those info to a yml file and access data from there. Matt Swanson has excellent write on how to do that in his blog. With this, we could dump the data from yml file to jekyll site variable.
Finally, we built a small heroku app that powers the join page forms and we have rubynepal.org as how it is now.