Eleventy is a pure-JavaScript site builder; after this conversion, we will not depend on Jekyll for local preview (so people will not need to install two tech stacks in order to work with us).
If we decide to adopt this, we will need to modify the CI to rebuild the site using Eleventy for publication.
One thing I'm not happy with: the files describing blocks are in _includes/LL/*.md (where LL is a two-letter language code). I tried using {% include ./whatever.md %} in guide.md, but Eleventy then insisted on creating pages for each of the included files (because of the .md extension). I then renamed them *.inc.md and told Eleventy's config to ignore these files, but then the Markdown wasn't processed. I'm sure there's a way around this...
Thanks for checking this one out - we'll need to modify the GitHub Actions to rebuild the site using Eleventy instead of Jekyll before we can merge and deploy this one.
Eleventy is a pure-JavaScript site builder; after this conversion, we will not depend on Jekyll for local preview (so people will not need to install two tech stacks in order to work with us).
If we decide to adopt this, we will need to modify the CI to rebuild the site using Eleventy for publication.
One thing I'm not happy with: the files describing blocks are in
_includes/LL/*.md
(whereLL
is a two-letter language code). I tried using{% include ./whatever.md %}
inguide.md
, but Eleventy then insisted on creating pages for each of the included files (because of the.md
extension). I then renamed them*.inc.md
and told Eleventy's config to ignore these files, but then the Markdown wasn't processed. I'm sure there's a way around this...