Moving to 11ty on GitHub Pages
Starting, I have a standard Jekyll + GH Pages setup. A few pages in root, some posts, layouts, and includes, and CNAME entry for my domain. Something like:
_includes/
footer.html
_layouts/
default.html
home.html
page.html
_posts/
2023-06-03-moving-to-11ty.md 👋
_config.yml
.gitignore
404.html
a-page-of-mine.md
CNAME
Gemfile
Gemfile.lock
index.md
My goal is to get from that to an 11ty-based system, and just as easy to update (🤞; meaning I just have to update my master git branch, or similar). I’ve found several articles online about it, but they almost all assume you’re going to do this for a project and not your main project/namespace in GitHub, which is not the case for me (though I plan to do it for other projects as well). I also want several blogs, essentialy, on this project. So I’m going to follow them, but figure out what I need to do differently, and document the move.
Here are my resources so far:
- https://www.rockyourcode.com/how-to-deploy-eleventy-to-github-pages-with-github-actions/
Sophia Brandt. August 16, 2020; Last modified: January 21, 2022. - https://www.linkedin.com/pulse/eleventy-github-pages-lea-tortay/ Lea Tortay. December 4, 2020.
- https://keepinguptodate.com/pages/2019/06/creating-blog-with-eleventy/
Jon Keeping. June 1, 2019. (Nothing to do with GH Pages.)
Note they’re all a few years old (this being 2023).
Now, I could just make an empty folder and build an 11ty project. But wouldn’t it be better to use what you have (if you like it)?
I have to:
- Turn off Jekyll
- Remove or move out old files
- Install 11ty
- Install 11ty starter (sheesh)
- regen site