Description
All 146 MDX pages have title, description, and schema nested inside the seo.og block, but the DWT theme's OgConfig type does not include these properties. This causes a TypeScript build error and prevents CI from passing.
Steps to Reproduce
- Run
npm run build on the repository
- Observe TypeScript compilation failure in
pageMap.ts
Expected Behavior
Build completes successfully. og:title and og:description are derived automatically from the top-level title and description frontmatter fields. Structured data (schema) is rendered as a JSON-LD <script> tag in the page <head>.
Actual Behavior
Build fails with:
Type error: Object literal may only specify known properties, and '"title"' does not exist in type 'OgConfig'.
The schema block inside og is also silently ignored at runtime since it is in the wrong position.
Root Cause
OgConfig (from @document-writing-tools/kernux-theme v2.0.1) only accepts:
interface OgConfig {
image?: string;
image_alt?: string;
image_width?: number;
image_height?: number;
type?: "article" | "website";
}title, description, and schema must not appear inside og. schema belongs at the seo level. Additionally, schema type values WebSite and WebPage are not supported — valid values are Article, TechArticle, HowTo, FAQPage.
Proposed Solution
For all 146 affected MDX files:
- Remove
title and description from inside the og block (they are auto-derived from top-level fields)
- Move
schema from inside og to the seo level
- Drop
schema blocks whose type is WebSite or WebPage (8 pages total) since these types are unsupported
Acceptance Criteria
Description
All 146 MDX pages have
title,description, andschemanested inside theseo.ogblock, but the DWT theme'sOgConfigtype does not include these properties. This causes a TypeScript build error and prevents CI from passing.Steps to Reproduce
npm run buildon the repositorypageMap.tsExpected Behavior
Build completes successfully.
og:titleandog:descriptionare derived automatically from the top-leveltitleanddescriptionfrontmatter fields. Structured data (schema) is rendered as a JSON-LD<script>tag in the page<head>.Actual Behavior
Build fails with:
The
schemablock insideogis also silently ignored at runtime since it is in the wrong position.Root Cause
OgConfig(from@document-writing-tools/kernux-themev2.0.1) only accepts:title,description, andschemamust not appear insideog.schemabelongs at theseolevel. Additionally, schematypevaluesWebSiteandWebPageare not supported — valid values areArticle,TechArticle,HowTo,FAQPage.Proposed Solution
For all 146 affected MDX files:
titleanddescriptionfrom inside theogblock (they are auto-derived from top-level fields)schemafrom insideogto theseolevelschemablocks whosetypeisWebSiteorWebPage(8 pages total) since these types are unsupportedAcceptance Criteria
npm run buildpasses without TypeScript errorstitle,description, orschemainside theseo.ogblockTechArticleschema emit a valid JSON-LD<script>tag in the rendered HTMLWebSite/WebPageschema types have theschemablock removed