Flowershow now lets you control how each page is rendered — as plain Markdown or as MDX. Here’s what you need to know:

  • By default, Flowershow uses auto mode: .md files render as plain Markdown, .mdx files render as MDX.
  • To change the default for your whole site, go to your site’s dashboard settings and adjust the Syntax Mode option.
  • To override it for a single page, add syntaxMode: md or syntaxMode: mdx to the page’s frontmatter.

If you’re an Obsidian user publishing regular notes, your .md files now just work — no more cryptic parsing errors from special characters or HTML.

If you want to use Flowershow components like <List> or JSX on a specific page, either rename it to .mdx or add syntaxMode: mdx to its frontmatter.

Why This Matters

Until now, Flowershow rendered everything as MDX — a powerful format that supports JSX components, but one that’s stricter than plain Markdown. Some syntax that works fine in Obsidian or GitHub Markdown doesn’t play nicely with MDX’s JavaScript-based parsing rules. For example:

  • HTML blocks may not parse if they aren’t valid JSX
  • <a, b> or other angle-bracket expressions (<a is treated as the start of a JSX tag) will break
  • {a} is treated as a JavaScript expression, not plain text, so you’ll get errors like “a is not defined”

With syntax mode configuration, you can:

  • Use Markdown rendering for content with HTML or special characters
  • Switch to MDX for JSX-based pages and Flowershow components
  • Mix both across your site as needed

Configuration Options

Global Configuration

Set the default rendering mode for your entire site using the Syntax Mode option in your site's dashboard settings.

Options:

  • `