fix(metrics): stop rendering stat values and labels as headings

Open Beginner friendly
#5,659 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
scss
Domain
documentation, frontend

Research direction

Start with src/components/common/Stacked.astro and src/components/enterprise/StatsHeader.astro, then compare their scoped styles with the heading rules in app.scss. Check the rendered Markdown for /, /features, /use-cases, and /enterprise, and run the visual regression suite; done means no metric headings remain and the suite passes.

Written by the indexing model from the issue text.

Description

area/frontend kind/website

Part of the Markdown for Agents Phase 1 epic (see #5652). kestra.io has Cloudflare Markdown for Agents enabled: Accept: text/markdown converts the SSR HTML at the edge, so defects in the HTML end up in what AI agents read. Cloudflare strips nav/header/footer/scripts/styles/inline SVG, ignores aria-hidden and empty alt, keeps .visually-hidden text and display:none content, and renders <dl> as separate lines (all verified on production).

Problem

  • src/components/common/Stacked.astro emits <h2 class="color">6x</h2> per feature value, giving ## 6x, ## 90%, ## 10x headings on /, /features, /use-cases.
  • src/components/enterprise/StatsHeader.astro renders the stat label as <h5>, giving ##### Faster Workflow Completion on /enterprise (the value is already a div).

Scope

  • Stacked: .cards-row becomes <dl>, each card <dt class="color">{value}</dt><dd class="color">{label}</dd>. Scoped CSS mirrors the current h2 metrics: font-size: $h2-font-size; font-weight: 600; line-height: 1.2; margin-bottom: .5rem, and $h3-font-size below lg (see app.scss heading rules).
  • StatsHeader: <h5> label to <p class="label"> with $h5-font-size, weight 600, $h6-font-size below lg.

Done when

  • No metric headings in the Markdown of the four pages.
  • Visual regression suite passes.
Dominant language
Astro
Stars
155
Forks
177
Avg merge
23h 17m
Merged PRs (30d)
191

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kestra-io/docs

All issues in kestra-io/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.