MRender v2.9.0

Highlights

• Stability improvements for markdown rendering.
• Better handling for dynamic component containers.
• Incremental improvements for code highlighting and container parsing.

When v2.9.0 is still useful

• You need a stable baseline before frontmatter-heavy customization.
• You want to compare old and new behavior during migration.
• You are validating regressions in existing docs content.

Notes

Use this release as a baseline before moving to v3.0.0 frontmatter-based page controls.

Migration path to v3.0.0

1. Keep v2.9.0 content structure unchanged.
2. Upgrade dependencies and keep routes/navigation as-is.
3. Add frontmatter progressively page by page.
4. Validate layout and SEO effects after each batch.

Pre-upgrade checks

• Ensure all current markdown pages resolve without 404.
• Ensure custom containers (code-group, ng-component, alerts) render as expected.
• Record current SEO output for key pages so you can compare after upgrade.