socialnerds/website
socialnerds
/
website
1
0
Fork 0
Code Issues Pull Requests Activity

post edits

This commit is contained in:
Micah Cowell 2016-03-15 17:34:42 -07:00
parent d2525e19ef
commit 08bb1173bf
2 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
_posts/2016-03-10-ghost-to-jekyll.md
View File

@ -7,13 +7,13 @@ title: Why I Switched from Ghost to Jekyll
I made a new blog! For the past few months I had been content with [Ghost](https://ghost.org), the publishing platform for professional bloggers. I enjoyed its simplicity and even made a couple themes for it (check them out on my [Github](https://github.com/getmicah)), but as time went on I got tired of paying for server time every month. With all the buzz about "static blogs" I decided to give it a try. Inevitably, I came across Github Pages and Jekyll. Free hosting and a static site blog? Yes, Please.
It wasn't like there was anything wrong with Ghost. I was just tired of paying to host it on a server. There are quite a few things that I didn't even realize I would appreciate before using Jekyll.
It wasn't like there was anything wrong with Ghost. I was just tired of paying to host it on a server. Also, there were quite a few things that I didn't even realize I'd like before using Jekyll.
# Static Site
One of those being the idea of a static website being generated and no need for a backend. This just makes sense and everything is very fast. Jekyll also automatically generates your Sass files into css which is very handy (no need setting up gulp every project).
# Local Posts
Another thing I especially appreciate about Jekyll is how all your posts are stored locally. You just type out your post in markdown in your editor and push to Github to post. Also, its implementation of templates is extremely useful when constructing posts.
Another thing I especially appreciate about Jekyll is how all your posts are stored locally. You just type out your post in markdown in your editor and push to Github to post. Also, its implementation of drafts is extremely useful because you can see how they look locally before making them a post.
# Variables
The use of variables has to be my favorite feature. It splits variables up between site and page variables. Site variables would include the name of your blog and the description while page variables would be the name of the post or the date. You can include your own site variables inside the _config.yml file, such as a Google Analytics code or something of the nature.
@ -21,4 +21,10 @@ The use of variables has to be my favorite feature. It splits variables up betwe
# Data Files
Another way to access info in your blog is through data files. Instead of just variables, data files allow you to create a YAML, JSON, or CSV file to put data into. For example on this site I have /data/websites.yml file where I store the websites I've made, the fields being the name and url, and then loop them into a list inside my html.
[Jekyll Documentation](https://jekyllrb.com/docs/home/)
# Maintainable
Everything is through Github, which is where I would be putting my code anyways, so it makes sense that it would also be where I host my website. Making changes to my blog is painless. All I have to do is push the code to Github whenever I make changes (though all changes should be tested locally).
# Conclusion
So why did I switch to Jekyll? Simply the speed and price. The free hosting, static site generation, and complete control make it, in my opinion, the best option for any web developer desiring a blog. With Github Pages there's no need to check on your server nor do you have to worry about having the latest software, Github just does it for you.
For more information about Jekyll, check out the [Docs](https://jekyllrb.com/docs/home/).

4
assets/css/main.scss
View File

@ -108,7 +108,7 @@ ul {
margin-bottom: 10px;
}
&__date {
font-size: 0.8em;
font-size: 1em;
}
&__content {
padding-top: 40px;
@ -121,7 +121,7 @@ ul {
p {
font-size: 1em;
line-height: 150%;
margin-bottom: 10px;
margin-bottom: 15px;
}
strong {
font-weight: 700;