I’ve been blogging and hosting my website since 2006, but I’ve always been unhappy with the themes available for technologies like Blogger, WordPress, or Squarespace. I usually had a vision for what I wanted to create and would spend hours scouring marketplaces to find something that came close.
At first, I experimented with developing child themes for WordPress. If you’re not familiar with WordPress, I basically overwrote the CSS stylesheets and built my own page and post templates using PHP. I even got good enough that I had clients who would hire me to make changes to their WordPress themes and installations.
Still, all of the tweaks and changes felt cobbled together. They were cobbled together. I was building Frankenstein sites with dozens of overrides, plugins, and hacks that could break at any moment.
Searching for something better
I wanted to escape the bloat of platforms like WordPress, or the restricted design options available with a platform like Squarespace. I wanted to go back to static HTML and CSS and I wanted to code it myself.
I built a few starter projects with Jekyll and quickly fell in love with it. While there are a variety of open-source static site generators available now, I still enjoy the relative simplicity of Jekyll for getting started. The liquid templating language is easy to understand and your HTML/CSS/JS work cleanly together.
To use a CMS or not?
I built a few starter websites with Jekyll. One of the things I missed at first was the integration with my writing tool of choice (Ulysses). I also wanted some of the benefits of a CMS, like scheduling posts. Ulysses integrates with WordPress and Ghost so you can publish from mobile and desktop. I decided to give Ghost a try.
I worked with Ghost for a while but kept getting frustrated with the server upkeep that it invariable entailed. At first, I paid for a monthly subscription, but the functionality at the basic level is limited unless you spend $30/mo. At that level, you can either create your own theme to host with them or use their API to support a frontend framework built with Jekyll, Gatsby, or another tool. The cost is about the same as a good WordPress hosting provider, but that was more than I was willing to spend for the convenience of scheduling posts within a CMS.
I should note that Ghost also offers an option to self-host (starting at $5/mo through Digital Ocean) but I didn’t want to maintain the server myself. I already have enough reasons to not write without throwing in server updates…which were one of the reasons I wanted to leave WordPress.
Ultimately, I decided to forgo the CMS and focus on Jekyll. I’ll write more about this in the future, but Jekyll fits into my growing philosophy around working with markdown for personal knowledge management and publishing.
Publishing with Netlify
My first Jekyll website was published using Github pages. While I loved the option to publish a free project website directly from my repo, it was definitely more difficult to manage and came with a host of limitations.
Ultimately, I went with Netlify. They are a fantastic organization that makes it easy to build, deploy, and scale web projects. Using Jekyll, I can generate a website from my repo on Github and Netlify deploys it to edge servers across its network. Since I’m only serving static HTML files, this makes my websites incredibly fast for readers. And there is no server (on my end) to worry about securing, protecting, etc. Netlify handles the build and deploys the static files acrss the edge.
Getting set up
I won’t go into too much detail on the development process here, but I will link to the resources that I found the most helpful for getting started:
- Poole: Clean and concise foundational setup for Jekyll
- How to deploy Jekyll with Netlify
- How to deploy Jekyll with GitHub pages
- Formspree: Open-source form solution for static websites
- Liquid template language reference from Shopify
- Getting started with Netlify
As one of the original static website generators, Jekyll benefits from a large community of open-source contributors and users who have documented their techniques and solutions. If you get stuck, there is most likely a tutorial with the answers you need!
Overall I’m pretty happy with the results of the project. I learned a lot along the way and ended up with a website that doesn’t look too bad and is unique to me. While I don’t need to make any changes to start writing, there are a few areas I plan to explore in the coming months:
Implement Tailwind CSS to replace Bulma I used the Bulma CSS Framework to scaffold the development of this project. Previously, I used Bootstrap for a few starter projects. Bulma is great, but I’ve been wanting something easier to customize. Enter Tailwind CSS, which is a just-in-time, atomic framework for creating CSS. I can build and design the website, all within HTML. Then, I can filter out any unused classes, resulting in a very small file.
Buildout functionality for my digital garden I expect to write about this more in the coming months, but I’m planning to treat this blog more like a digital garden. There are some core functionalities I want to add, like sides notes, bi-directional links, and search, to make the reading experience more rich and interconnected.
I hope you have a similar positive experience, and please reach out if you have any questions about building your website with Jekyll and Netlify.