MRender v3.0.0

Highlights

• Added markdown frontmatter page options for layout and SEO.
• Added per-page TOC control and wide-content mode.
• Added reusable section configuration for docs/showcase/blog/releases.
• Added page-level origin link support for reposted articles (origin, originLabel).

Who should upgrade

• Teams managing docs, blog, and release notes in one markdown system.
• Teams that need page-level SEO tuning without touching TypeScript config for every page.
• Teams migrating external articles (for example from Medium) and needing canonical source attribution in content.

Upgrade notes

1. Keep existing provideDocumentation usage.
2. Add frontmatter keys only where page-level behavior should differ from global defaults.
3. Move repeated section wiring into a shared section factory.
4. Add origin frontmatter only for reposted content.

Frontmatter quick-start

Reusable section config pattern

Migration checklist

1. Update project to v3.0.0 dependencies.
2. Confirm all section routes still resolve markdown files.
3. Add frontmatter only where needed.
4. Validate TOC behavior on pages with toc: false.
5. Validate SEO tags on pages with custom frontmatter.
6. Validate origin link rendering on reposted pages.

Validation

• Verify table of contents behavior on pages with toc: false.
• Verify width expansion behavior on pages with wideContent: true.
• Verify title/description/canonical/og/twitter tags for pages with SEO overrides.
• Verify origin block above content for pages with origin.
• Run SSR/prerender and confirm no route errors.

Common pitfalls

• wideContent has no visual effect if TOC is still enabled.
• origin must be a valid URL; invalid values are ignored.
• Overusing page-level SEO overrides can make metadata inconsistent across a section.
• Forgetting validation in prerender can hide metadata issues until production.