Teaching in the open: Eleventy
Content Management Systems and structured data are part of my teaching duties. From the get go, I decided to cover both a database-driven CMS and a Static Site Generator. As far as the latter goes, I switched from Jekyll to Eleventy this year.
Both as a teacher and as a freelancer, I firmly believe that the JAMstack movement and the general trend towards decoupling the view and data layers are here to stay.
I have been teaching Craft CMS as a database-driven CMS since it was first released. Pixel & Tonic releasing a native headless mode and a solid native GraphQL API only confirmed my choice.
Jekyll, while very good at generating a site based on Markdown and static data files, requires either a plugin or a build process in front of it to consume data from APIs or headless CMSes.
Working within a familiar environment and being able to extend and configure Eleventy using a language students already know and understand is a game changer.
For students, this is invaluable. Granted, Eleventy might feel a bit closer to the metal compared to Jekyll but the increased flexibility, extensibility and familiarity is definitely worth it.
With React, Vue or Svelte being all the rage these days, SSG like Gatsby or Gridsome were also on my radar.
Personally, I feel that those solutions, while extremely valuable when you have to deal with app-like functionalities and / or state-based UI, come with a lot of baggage and are a bit overkill when building content-driven websites.
By comparison, Eleventy is a lot simpler and looks a lot less like a black box to me (if I am being completely honest). Fetching data from a GraphQL API is quite trivial and students can still use what they learned with my colleagues teaching them Vue or Node if the project requires it.
Workshop course and sample website
All things considered, I am really happy with how the course went this year. Students seemed to enjoy it and got the hang of it pretty quickly.
My "introduction to Eleventy" course is available on Github in French and English, along with a sample website hosted on Netlify. Feel free to check both out and to give feedback, open issues or make pull requests if you think something could be improved.
As I have said in the past, teaching in the open is part of my attempt to stay relevant while teaching front-end design in this ever-moving, ever-changing messy web of ours.