- pandoc 👉 11ty (static site generator)
- cypress (uat)
- github actions (cd)
- aws s3 (hosting)
- cloudflare (dns + cdn + ssl)
to bring the point home, i don’t even have
@11ty/eleventy npm package in my package.json. i can use
npx to serve and build my site.
this was important to me, since i didn’t want to have to deal with
latex to build my site ever again.
i learned from my mistakes and decided to go with something that i was familiar with:
so the most natural thing was to run
npx @11ty/eleventy --serve. and this is how my site is available and live-reloaded at
i have a custom eleventy configuration with a few additional features and build steps:
- copy assets
- create excerpts
- prepare posts
- minify html
- minify css
- add build commit to html footer
a post that explains how to deploy an 11ty static site with github actions on aws s3
cypress is now my choice when it comes to user acceptance tests.
cypress/integration you can find the following tests:
in runs on the ci with
npx cypress run, alongside a running http server listening on port
similar as above, i use
npx @11ty/eleventy to build this site to the static directory
aws s3 cp follows and updates my aws s3 bucket with the new static files.
finally, cloudflare’s http api comes in handy to purge the cdn.
an absolutely refreshing idea is to have a pretty stable ci/cd pipeline running quite easily.
i have written in another post how i deploy my site with github actions
what i delegate to github actions are the following commands:
- build (eleventy)
- uat (cypress)
- deploy (aws s3)
- cache (cloudflare)
- notify (telegram)
each of these lego pieces make the full cd pipeline.
i simply love this setup.
11ty gives me great flexibility, similar to jekyll and conceptually the same.
i will always love jekyll, it was the static site generator that got me into blogging in the first place.