Skip to content

Generated reference content (database/tables, archive-providers, mdo-providers) still emits an H1, duplicating frontmatter title #192

Description

@digitaldiina

Background

#165 consolidated the body H1 into frontmatter title across the repo (H1 removed, title is the page's sole title). Two generators were fixed at the source in the same pass since they're owned by this repo:

  • tools/transform-crmscript.ps1 (en/automation/crmscript/reference/, en/automation/trigger/reference/) - no longer emits an H1, now stamps generated: true.

Three generators were left emitting an H1 because their generator isn't in this repo - it's ADO-hosted (confirmed via tools/fix-archive-providers-mdx.ps1's own docstring: "the (ADO-hosted, not present in this repo) archive-providers reference generator"):

  • en/database/tables/** (1234 files, generated: true)
  • en/api/archive-providers/reference/** (372 files, generated: true)
  • en/api/mdo-providers/reference/** (421 files, generated: true)

Editing these committed files directly would just be overwritten on the next regeneration from the external generator, so #165 deliberately excluded them (detected automatically via their generated: true frontmatter in the hardened tools/sync-title-h1.py).

Problem

These ~2000 files keep a body H1 that duplicates the frontmatter title indefinitely, which is exactly the pattern #165 eliminated everywhere else. This is also the residual scope of #164 (On this page sidebar H1 duplication) - the CSS fix in #164 only suppresses the symptom (sidebar dup) for these pages; the underlying duplication in the source content remains.

Ask

Whoever owns the ADO pipeline for these three generators should update it to stop emitting the body H1 (matching the fix already applied to transform-crmscript.ps1: drop the # {title} line, keep everything else identical), then regenerate. No frontmatter shape change needed - generated: true is already present on all three.

Related: #164, #165

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions