Sometimes, you just have an HTML file you want to publish.
It might be:
- A portfolio page where you hand-coded every pixel.
- A complex report or dashboard exported from a data tool.
- A custom landing page that needs a specific structure.
In these cases, converting to Markdown feels wrong. You want the file exactly as it is.
Why this is useful (The Old Way vs. New Way)
Before, if you wanted a custom page, you had to paste HTML blocks into Markdown.
But if you had a full page—like something exported from a tool or generated by AI—it was painful:
- You had to use
layout: plainfrontmatter. - Yo...
Sometimes, you just have an HTML file you want to publish.
It might be:
- A portfolio page where you hand-coded every pixel.
- A complex report or dashboard exported from a data tool.
- A custom landing page that needs a specific structure.
In these cases, converting to Markdown feels wrong. You want the file exactly as it is.
Why this is useful (The Old Way vs. New Way)
Before, if you wanted a custom page, you had to paste HTML blocks into Markdown.
But if you had a full page—like something exported from a tool or generated by AI—it was painful:
- You had to use
layout: plainfrontmatter. - You had to deal with Markdown formatting errors breaking your HTML.
- You had to constantly check if the parser stripped your styles.
It was brittle.
The New Way:
Flowershow now supports publishing raw .html files directly.
flowershow publish index.html
How it works:
Just place your .html file in your content folder. When you run publish, we serve it as-is.
This means you can mix-and-match: keep your weekly notes and documentation in Markdown for speed, but drop in raw HTML files for special pages, reports, or interactive tools.
No configuration needed. It just works.
Want to know more? check our blog-post about it: https://flowershow.app/blog/announcing-html-support