fix(web): landing page heading structure

[yanthomasdev]

This PR fixes the heading structure of the pages to be semantically and hierarchly accurate. I can see the idea was probably to use the document outline algorithm (h1s separated between sections), but this particular feature was never fully adopted by user agents and assistive technologies.

Having a well-structure heading structure helps users of assistive technologies to navigate the page with shortcuts and structural navigation, as well as helps with SEO and AI to better index the content and its relationships.

---

Summary by cubic

Fixes the landing, components, and templates pages to use a correct heading hierarchy (explicit h2/h3) for better accessibility and SEO. Replaces implicit/visual headings with semantic levels under each page’s main heading.

• Bug Fixes
  • Use Heading as="h2" for section titles and as="h3" for subsections across Integration, Patterns, Playground, Primitives, Tools, and Template.
  • Update Components page category titles from h3 to h2.
  • Align Interactive Demo item titles to h3 for proper nesting.

^{Written for commit 4fedfde. Summary will update on new commits.}

[vercel]

@yanthomasdev is attempting to deploy a commit to the resend Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4fedfde

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cubic-dev-ai]

No issues found across 8 files