You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For SSG, Markdown is used as a Template engine while it's just a markup language and not a template engine. But it's not the case for AsciiDoc, RestructuredText, Textile, etc. Having the ability to filter by Markup language is also useful.
What should we do?
Also add AsciiDoc, RestructuredText, Textile in template or create a new category markup?
The text was updated successfully, but these errors were encountered:
I think they should be different categories. As you mentioned, Markdown is a markup language, not a template engine. Even if some SSGs allow attributes (Goldmark, for example) or extended Markdown via the parser they are using.
On the other hand, AsciiDoc and other markup languages, although more complex than Markdown and even similar to what a template engine offers, are focused on content markup and its compilation to, in this case, an HTML output (standard).
So, I would propose to create a new "Markup" category, which would be very helpful: for example, Hugo can use Markdown, AsciiDoc, Emacs Org-Mode or RST, Astro supports Markdown and MDX, etc.
In addition, markup language and template engine are term that should be defined in the glossary; they are somehow ambiguous.
For SSG, Markdown is used as a Template engine while it's just a markup language and not a template engine. But it's not the case for AsciiDoc, RestructuredText, Textile, etc. Having the ability to filter by Markup language is also useful.
What should we do?
Also add AsciiDoc, RestructuredText, Textile in template or create a new category markup?
The text was updated successfully, but these errors were encountered: