For OnShift’s 2016 Q4 Engineering Hack Day, I decided to create a blog for our department to share with the world our passion for the technologies we’ve used here at OnShift. I felt that it was very appropriate to write the first post, explaining what I did to setup this very blog.
I’ve decided to use Github.io for the hosting platform and jekyll–more specifically,
firstname.lastname@example.org:barryclark/jekyll-now.git–for the blog site generator. My reasons for choosing these options are as follows:
- It’s a free option
- There are no additional infrastructure that our team needs to manage
- It’s using a technology we are all familiar with. i.e. Github
- I have experience with setting up my own blog using these technologies
- I’ve used other blogging platforms and they all seem overkill for my use case, as well as this use case
For the purposes of the initialization steps, I am assuming that the username/organization name is OnShift. Anywhere you see OnShift, replace it with your own username or organization.
- Create an empty, public repository with the name OnShift/OnShift.github.io. Do not initialize the repo with any files. It must be an empty repo.
- Run these commands locally, essentially copying the email@example.com:barryclark/jekyll-now.git repo into the empty repo you just created.
git clone firstname.lastname@example.org:OnShift/OnShift.github.io.git cd OnShift.github.io git checkout master git remote add barryclark email@example.com:barryclark/jekyll-now.git git pull barryclark master git push origin master
The reason I chose to copy the repo instead of forking, is because we will be making a significant number of changes to the repo and it will deviate so much that it would not make sense to contribute to the original project using the fork. If the original repo were to have any improvements that we would like to have in our our repo, we are still able to pull in the changes either by pulling from the original repo or by creating a git patch and apply it over top our repo. Either way, we will most likely need to resolve merge conflicts. However, that does not stop us from contributing to the original repo via a forked repo.
One of the first things I did after the blog was up and running was to style it. We have a Front End Software Developer—Ali Orlando—that created a project called Flamingo to standardize our styles accross all of OnShift’s projects. Flamingo is an extension of the Twitter Bootstrap framework. We have a working demo.
I recognize that this blog has a very basic design and it has a few spacing issues. However, this site is on Github and I plan to have others contribute not only with content, but also with style modifications.