Extract "default" template languages (Nunjucks, Liquid, markdown) to plugins

[uncenter]

...like the more esoteric templating languages that were moved out of core to plugins with v3, Nunjucks and Liquid should also be plugins - so that I, someone who uses neither of those two (I use Vento), am not installing an extra 3MB every time.

Originally posted by @uncenter in #3587

As suggested by @Ryuno-Ki, opening as a new issue for this discussion.

---

Since Eleventy tries to remain unopinionated, I think moving these template languages to separate plugins in https://github.com/11ty/eleventy-plugin-template-languages would make sense. If it is felt that including (a) default template language(s) is important (i.e. new users, simplified configuration/setup - valid points), I would propose splitting Eleventy into two packages; @11ty/core and @11ty/eleventy, the former being a more barebones scaffolding tool and the latter coming with more defaults and reinforced structure. Just a thought :)

[Ryuno-Ki]

Thank you 🧡

I think, one of the beautiful aspects of Eleventy is the support for multiple template languages (as well as their mix-and-match). This eases the transition from other systems to it (Jekyll using Liquid, Python with Jinja2 which is almost identical to Nunjucks etc).

On the other hand there's this argument that by bundling all those template language engines the package download size goes up.

Splitting it up might be a good strategy. In the past, several pieces have been moved into plugin land.