Rewrite /docs/languages pages in _that_ templating language

This is a pretty meta idea—even for me—but what if each of the docs pages for the different supported templating languages were written in that templating language? (This idea may not work for .html, .md, or .jstl—but it'd be a potential game changer for the others.) What a tremendous benefit for readers—especially newcomers—to see the language being discussed in action, not merely in snippets wrapped in a different templating language they may not understand, but in the very templating language they're trying to learn about! I'm also thinking that it would reduce cognitive overload, at least in terms of editing individual docs pages, for that page to be all in one language. Thoughts?

I'm happy to begin converting the /docs/languages/javascript.md over to *.11ty.js. Any takers for the others?

Start by reviewing /docs/languages/javascript.md and the other pages under /docs/languages, then compare the proposed *.11ty.js format with the existing documentation structure. The issue does not define which pages should be converted or a completion condition, so the scope and desired result need clarification before implementation.