When running scriggo serve in a directory with an a.md file, I expected Scriggo to render that file as HTML.
In reality, the Markdown isn't rendered and is kept as is, as if it were plain text:
Discussing with @gazerro, it emerged that this is currently the expected behavior, because the Markdown file must be included from an HTML file or extended from an HTML file (if I understood correctly).
What to do
Option 1
Document the behavior, making it explicit when running scriggo help serve
Option 2
Make Scriggo also render Markdown files directly. This could be done by adding a minimal, unstyled HTML wrapper around them.
At that point, the user, if they wanted to add their own CSS style, intuitively understands that it's better to include the Markdown file from an HTML file (which defines the style) rather than rendering it directly.
When running
scriggo servein a directory with ana.mdfile, I expected Scriggo to render that file as HTML.In reality, the Markdown isn't rendered and is kept as is, as if it were plain text:
Discussing with @gazerro, it emerged that this is currently the expected behavior, because the Markdown file must be included from an HTML file or extended from an HTML file (if I understood correctly).
What to do
Option 1
Document the behavior, making it explicit when running
scriggo help serveOption 2
Make Scriggo also render Markdown files directly. This could be done by adding a minimal, unstyled HTML wrapper around them.
At that point, the user, if they wanted to add their own CSS style, intuitively understands that it's better to include the Markdown file from an HTML file (which defines the style) rather than rendering it directly.