docs-frontmatter-audit

You can audit markdown frontmatter by scanning files with Glob, Read, and Grep tools to validate `applies_to` keys, `products` IDs, and `description` formats. This ensures metadata completeness and correctness to prevent publishing errors.

A frontmatter audit checks Elastic documentation metadata fields including `applies_to` keys, `products` IDs, `description` length and format, and recommends `navigation_title` for long H1s. This ensures all required metadata is complete and correct before publishing.

Yes, you can validate metadata across a batch of markdown files by running the audit in directories like '/docs/reference'. It scans and parses file content to identify missing required fields, incorrect values, and formatting issues across the entire batch.

Elastic documentation fails frontmatter checks during publishing due to missing `applies_to` keys, invalid `products` IDs, incorrect `description` length or format, or missing `navigation_title` for long H1s. Running an audit identifies these specific metadata issues.

The best way to ensure frontmatter quality assurance for technical documentation is to automate validation of required metadata fields like `applies_to` and `products` before publishing. This catches incomplete or incorrect frontmatter consistently across all markdown files.

Yes, scanning and parsing markdown files for metadata validation requires Glob, Read, and Grep tools to access file content and extract frontmatter. These tools enable the audit to check required fields for completeness and correctness.