What is this article about?
I've always liked moving between platforms for this blog, and I've tried a few along the years: a self hosted WordPress installation, a ready made wordpress.com solution, a custom solution made with React and Contentful, and last year I settled for a static site generated starting from a local WordPress installation.
This worked fine, and I didn't have many complaints about it, except for one thing. There was a barrier about thinking about some content to add, or modifications to make to the theme, and going online. That barrier was the fact that I had to:
- connect my external SSD where I keep Virtual Machines.
- fire up the Vagrant installation containing my Wordress site.
- make my changes or write a post.
- fight with the WordPress editor which doesn't like code snippets.
- push a button and generate a static version of the WordPress site.
- drag and drop the generated static files to Netlify (because I didn't want to pay for the pro version of static generator).
As you can see, not difficult, but convoluted. If I felt like changing some CSS... I just wouldn't do it. If I wanted to write a blog post, I would probably not do it as well.
My colleague and friend Giustino, whose technical tutorial I linked above, gave me the inspiration I needed to switch from my WordPress setup to Eleventy. I read on Twitter he was about to write a book about Eleventy and since I already started playing around with Eleventy last year and got good vibes, but never did anything with it, I decided to actually do it and migrate to it.
There are a few compelling reasons for Eleventy.
- I can write in Markdown.
- The setup is simple.
- The integration with Netlify or Github pages is very simple.
- The layout system is also very simple.
- For my use case, barrier from thought to post is lower than with WordPress.
- While I write or edit content, Eleventy will watch for changes and save everything to the
_sitefolder. If you then push to Github, and you have linked Github with Netlify, the content of the
_sitefolder will be automatically served.
So, once I had this idea, I proceeded as follows:
- I installed Eleventy globally and made sure it was working.
- Using the WordPress to Hugo Exporter I exported all my posts to Markdown files. Probably there are other plugins that do the same job, but I just used this one. Then, the most painful part, has been to go and edit the meta information of each post in case it was wrong or outdated.
- I started creating all the layout parts that would make my site, by copying chunks of php files from WordPress to Eleventy. Eleventy uses nunjucks files by default but you can use something else if you want. Me, I couldn't be bothered so I went with
nunjucks. In any case, you will need to adjust your
phptemplates to whatever template engine you decide to use.
- I copy-pasted my css file to my new website.
- Very important: you will need to edit the
.eleventy.jsfile to allow for css to be copied to the
- In the process, I removed a ton of unused images. Right now only a handful of posts have images, and I like it like that. I can always start adding exactly what I need at any point in the future.
- I deployed to Netlify.
How long did it take
It took me about 6 hours all considered. 2 hours to actually setup Eleventy and port my theme from WordPress, and 3/4 hours to adapt my markdown files and review them.
The result is the site you are reading. So exactly the same as before, but faster, easier to edit, more fun to modify.
The Github repository
Here is the Github repository for this website. Feel free to have a look. Hopefully the setup is self explainatory. There are more things one can do with Eleventy, but for my use case I didn't need to dig too deep.
All considered, I give my satisfaction with Eleventy a 9/10 (because 10/10 doesn't exist). Thanks to it, have a newfound passion with both updating my website with content, and updating it's style and code (I even already have a new design in mind). The freedom it grants is really refreshing after having being tied to complex systems like WordPress for so long. True, it doesn't have an admin dashboard, like WordPress does so well, but if you are a bit technically inclined, then that would not be a problem, and even an advantage if you're used to switching between files in an editor. Plus, the fact that it has support for front matter, makes it so very intuitive and easy to add additional meta information to your posts.
I think it's a great creative boost for the developer type of blogger, and it could even be the right solution in many cases, for agency work