review-docs

To review documentation quality and SEO for a Nuxt Content project, the system analyzes frontmatter, MDC usage, clarity, and structure to generate a prioritized, actionable report. This process detects project type automatically and enforces frontmatter requirements to improve documentation search visibility.

The best way to audit generic Markdown docs for structure and clarity is to run a comprehensive review that validates navigation, analyzes frontmatter requirements, and checks section structure. This generates a detailed report with a recommended action plan and optional fix workflow for improving overall documentation quality.

Yes, you can check internationalization and frontmatter requirements in Docus documentation. The review validates proper MDC prefixes, enforces frontmatter rules, and analyzes i18n where present to ensure structural compliance and generate a structured quality report.

You generate a prioritized action plan for fixing documentation issues by analyzing your docs for clarity, SEO, structure, and i18n problems. The resulting structured review report outputs a recommended action plan and an optional fix workflow to address identified vulnerabilities systematically.

Yes, the documentation review works with both Docus and generic Markdown files. It automatically detects the project type to apply appropriate validations, analyzing MDC usage for Docus while validating navigation and section structure across generic Markdown documentation.

Your Nuxt Content documentation needs frontmatter and MDC prefix validation to enforce structural compliance and ensure proper rendering. Validating these elements prevents navigation issues, improves search visibility, and maintains documentation quality standards across the project.