Where should the Markdown tutorials and ecosystem content live?

This relates to the long-running markdown is awesome plans.

Separate site on integrated into flowershow.app?

We are deciding where to publish educational content about Markdown workflows and tools (e.g., tutorials on using Markdown, Obsidian, GitHub, and FlowerShow):

• Option 1: create a separate “Markdown movement” site (e.g., markdownisawesome.com).
• Option 2: host it as a Markdown knowledge hub inside flowershow.app (e.g., /markdown).

Recommendation: integrate the Markdown content hub into FlowerShow

Create a Markdown knowledge hub inside flowershow.app (e.g. /markdown) rather than launching a separate site. This allows the educational content (Markdown ecosystem, workflows, Obsidian, GitHub, etc.) to attract broad search traffic while consolidating SEO authority and converting readers into FlowerShow users. Splitting this into a separate domain would dilute authority and require significantly more marketing effort to gain traction.

Key reasons

• SEO leverage: content authority accumulates on one domain rather than being split across sites.
• Lower operational cost: maintaining one site is far easier than growing two independent ones.
• Natural funnel: tutorials about Markdown workflows can seamlessly introduce FlowerShow as one of the best publishing tools in that ecosystem.
• Movement narrative still works: the hub can present a neutral “Markdown ecosystem” story while still linking to FlowerShow where relevant.
• Future flexibility: if the movement grows, a separate domain (e.g. markdownisawesome.com) can later act as a landing page pointing into the hub.

Suggested structure

flowershow.app/markdown
flowershow.app/markdown/tutorials
flowershow.app/markdown/stack
flowershow.app/markdown/examples
flowershow.app/markdown/manifesto

Bottom line: start with a FlowerShow-hosted Markdown ecosystem hub—it maximizes reach, minimizes overhead, and keeps a clear path from discovery → education → product adoption.