Is this a real article?

No. This is a build-pipeline test page that exercises every component (byline, JSON-LD, TOC, anchors, CTA, FAQ schema). It will be removed before launch and is excluded from the sitemap and indexing via the noindex meta tag pattern in BaseLayout.

Why test with a real article shape?

Because the Drivewayz failure modes (byline–schema date drift, broken TOC anchors, missing schema fields) only surface when every component is rendered together. A stripped test page would not catch them.

Pipeline Test — Do Not Index | KitchenBudgetPlanner

What this page exercises

This page exists to validate the entire publication pipeline end-to-end before the first real article ships. It deliberately uses the same layout, schema, byline, TOC, and FAQ components that every production article will use.

How the date pipeline works

The byline and the JSON-LD dateModified are both rendered from a single value: the git committer date on this Markdown file. There is no manual date field for dateModified in the front matter — drift between the visible byline and the schema is structurally impossible.

How the TOC pipeline works

The TOC at the top of this page was generated at build time from the H2 headings below. The slugs used for the heading IDs and the TOC anchor links come from the same deterministic slugger, so a TOC link can never point at an ID that does not exist.

CI validators that protect this

Three GitHub Actions guard against regressions on every PR: a broken-anchor check, a JSON-LD schema check, and a byline–schema date-match check. Each is non-negotiable — a failing check blocks the merge.

What this page exercises

How the date pipeline works

How the TOC pipeline works

CI validators that protect this

Frequently Asked Questions