Summary
Multiple documentation pages wrap frontmatter fields (sdk, languages, audience, complexity, keywords, updated) inside a metadata: object. However, src/content.config.ts declares these as top-level fields and does not declare a metadata block. As a result, these values are silently ignored by schema-based ingestion.
Problem
Frontmatter like the following is incorrect:
metadata:
topics: [authenticate]
sdk: []
languages: []
audience: [developer, product-manager]
complexity: intermediate
keywords: [WhatsApp, OTP, MFA, Meta, WhatsApp Business, messaging]
updated: 2026-03-03
The metadata wrapper causes all nested values to be ignored by the docs schema parser.
Fix
Remove the metadata: wrapper and move the supported fields to the top level, e.g.:
sdk: []
languages: []
audience: [developer, product-manager]
complexity: intermediate
keywords: [WhatsApp, OTP, MFA, Meta, WhatsApp Business, messaging]
Also verify whether topics is a supported top-level field in src/content.config.ts, and either map it to the correct field name or remove it.
Scope
This issue affects multiple pages across the documentation. A dedicated PR should audit and fix all affected .mdx files.
References
Summary
Multiple documentation pages wrap frontmatter fields (
sdk,languages,audience,complexity,keywords,updated) inside ametadata:object. However,src/content.config.tsdeclares these as top-level fields and does not declare ametadatablock. As a result, these values are silently ignored by schema-based ingestion.Problem
Frontmatter like the following is incorrect:
The
metadatawrapper causes all nested values to be ignored by the docs schema parser.Fix
Remove the
metadata:wrapper and move the supported fields to the top level, e.g.:Also verify whether
topicsis a supported top-level field insrc/content.config.ts, and either map it to the correct field name or remove it.Scope
This issue affects multiple pages across the documentation. A dedicated PR should audit and fix all affected
.mdxfiles.References