# Jekyll Blog Setup

DevFeed: [Jekyll Blog Setup](<https://devfeed.tech/articles/my-blog-setup-37314.md>)

Original publisher: [Read original article](<https://muffinman.io/blog/my-blog-setup/>)

Author: Stanko

Published: 2017-09-27T00:00:00Z

Content type: tutorial

Language: en

Sources: [Stanko Tadić](<https://devfeed.tech/sources/stanko-tadic.md>)

Topics: [Jekyll](<https://devfeed.tech/topics/jekyll.md>), [GitHub Pages](<https://devfeed.tech/topics/github-pages.md>), [static-site-generator](<https://devfeed.tech/topics/static-site-generator.md>), [Markdown](<https://devfeed.tech/topics/markdown.md>)

Tags: [github-pages](<https://devfeed.tech/tags/github-pages.md>), [jekyll](<https://devfeed.tech/tags/jekyll.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [static-site-generator](<https://devfeed.tech/tags/static-site-generator.md>)

## AI overview

An outdated personal tutorial describing a Jekyll-based static blog hosted on GitHub Pages. It explains static-site generation, Markdown-based authoring, and starting from a quickstart guide or the Lanyon theme.

## Source excerpt

Please note that I'm not using Jekyll anymore, so this post might be outdated. Update, March 2020 # This post is outdated and I simplified my setup a lot. I'll try to cover my current setup in one of the future blog posts. Original post # Few days ago I got a following message on LinkedIn. Hi Stanko! I'm a junior front-end web developer and I recently found your amazing blog and fell in love with it. Since you don't have any other social media, I decided to contact you trough here even if it's not ideal. I was wonder what CMS you were using and if you could do a blog post about it ? So here it is, post about my blog setup. Jekyll # I'm not using a dynamic CMS but a static site generator called Jekyll. Static site generators take different approach to making websites. Instead of having a database, pulling data from it and dynamically building your pages, static site generators generate all the pages only when there are changes to the site. No moving parts, just plain HTML files. This approach is more secure, makes caching much easier and boosts performance. Smashing Magazine has a post on why static sites are awesome. Static sites are not limited to blogs. Bigger websites are also easy to build, once you get a hold of it. There are agencies that are even doing it for client work. It comes at the price that once it's built you need to deploy it somewhere. And you don't have fancy CMS interface, only good ol' markdown files. Build and deployment part is easy, just let GitHub pages1 do that for you. Handling a git repo with a bunch of markdown files should be fairly straight forward for any developer or tech savvy person. If you feel this is a big burden, then static site generators might not be for you. 1 There is Netlify as well, which I never used myself, but I've heard good things about it. How to start your own # I keep this blog on GitHub pages (obviously) and I would recommend you to do the same. If you want to start from scratch, start with official quickstart g