Content

Application content is independent of website documentation

Flare's public content lives in apps/web/src/content. It is application MDX, not the musemvp-com Fumadocs tree. Your purchased source deploys independently and does not require the marketing website at runtime.

Public rendering lives in apps/web/src/modules/public, page registration in apps/web/src/routes/$.tsx, SEO in apps/web/src/lib/seo.ts, and robots/sitemap handling in apps/web/src/server.ts.

Edit an existing article

1. Find both locale files for docs, blog, changelog, or the relevant legal content.
2. Keep headings, links, and capability descriptions accurate in both languages.
3. Use Markdown headings, lists, links, and code blocks. Review scripts and remove credentials from examples.
4. Run development and inspect both the English and /zh pages.

Use paired <slug>.en.mdx and <slug>.zh.mdx files. The current loader uses a flat static glob; arbitrary nested directories do not automatically become collections. Legal paths normalize their prefix, so inspect the existing mapping before renaming files.

Register a new public page

Adding MDX alone does not add a route. Update the route allowlist and dispatch, public module title/slug/navigation, SEO title/description/canonical/hreflang, server sitemap/robots rules, both locales, and browser coverage together.

Unknown URLs must remain 404. Do not turn every path into a 200 response to simplify article loading. Keep API and protected workspace paths out of public sitemaps.

Legal and contact pages

Replace example policies, support addresses, data use, third-party services, and refund statements with your actual business terms. Do not retain promises your product does not implement. Rendering contact information does not automatically create a form-processing backend; implement explicit recipients, validation, and failure feedback if adding submissions.

Review and publish

Include relevant product descriptions, docs, changelog entries, and legal changes with a feature PR. Store stable images in public with useful alternative text rather than using temporary authenticated URLs.

Long code blocks should scroll horizontally without overflowing the whole page. Preserve appropriate locale links in both articles and use clear external destinations.

Verify and troubleshoot

An empty article usually means a slug, filename, locale, or glob mismatch. A new article returning 404 usually means it was not registered as a route. Old SEO requires checking config, messages, and seo.ts in addition to MDX headings.

Run build and inspect public pages, unknown URLs, both locales, and the public sitemap. Continue with internationalization and components.