More extensible template syntax chaining.

[zachleat]

Note that markdown and HTML types have an option to preprocess with another syntax: https://www.11ty.dev/docs/languages/

Note also that Custom syntax has access to default renderer when aliasing: https://www.11ty.dev/docs/languages/custom/#aliasing-an-existing-template-language

I would like this to be more extensible beyond just markdown and HTML types, allowing folks to chain together whatever syntaxes they want.

[zachleat]

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open.

View the enhancement backlog here. Don’t forget to upvote the top comment with 👍!

[zachleat]

Related: #3302

[zachleat]

Moving off of the queue, related work in #3300 got us close here.

[zachleat]

Shipping with 3.0.0-alpha.11. This feature lets you alias to existing custom template syntaxes.

This removes the limitations on:

https://www.11ty.dev/docs/languages/custom/#aliasing-an-existing-template-language

“If key is the only property in the options object, we treat the extension as an alias and use the existing upstream template syntax.”

You can now add the other properties to your addExtension (init, compile, etc) and reference the upstream template syntax with defaultRenderer.

[zachleat]

Docs updates shipped.