Merge pull request 'fix(seo): use h1 as primary heading on about, schedule, events, and contact pages' (#3 ) from fix/seo-heading-hierarchy into main

Reviewed-on: kfj001/kmtnflower#3 Reviewed-by: kfj001 <kfj001@gmail.com>
fix(seo): use h1 as primary heading on about, schedule, events, and contact pages
2026-08-04 02:54:18 -07:00 · 2026-08-04 09:26:48 +00:00
4 changed files with 4 additions and 4 deletions
@@ -3,7 +3,7 @@
    <!-- Intro -->
    <div class="about-intro">
      <img [src]="resolveImageUrl(config().hero_icon_url)" alt="" class="about-flower-decor" aria-hidden="true">
-      <h2>About <span class="text-accent">{{ config().name_primary }} {{ config().name_secondary }}</span></h2>
+      <h1>About <span class="text-accent">{{ config().name_primary }} {{ config().name_secondary }}</span></h1>
      <p class="section-intro">{{ config().about_intro }}</p>
    </div>

@@ -2,7 +2,7 @@
  <div class="container">
    <div class="contact-header">
      <img src="svg/small-flower.svg" alt="" class="contact-flower" aria-hidden="true">
-      <h2>Get in <span class="text-accent">Touch</span></h2>
+      <h1>Get in <span class="text-accent">Touch</span></h1>
      <p class="section-intro">
        Have a song request, want to volunteer, or just want to say hello?
        We'd love to hear from you.
@@ -2,7 +2,7 @@
  <div class="container">
    <div class="events-header">
      <img src="svg/small-flower.svg" alt="" class="events-flower" aria-hidden="true">
-      <h2>Upcoming <span class="text-accent">Events</span></h2>
+      <h1>Upcoming <span class="text-accent">Events</span></h1>
      <p class="section-intro">{{ config().events_intro }}</p>
    </div>

@@ -2,7 +2,7 @@
  <div class="container">
    <div class="schedule-header">
      <img [src]="resolveImageUrl(config().logo_url)" alt="" class="schedule-flower" aria-hidden="true">
-      <h2>Program <span class="text-accent">Schedule</span></h2>
+      <h1>Program <span class="text-accent">Schedule</span></h1>
      <p class="section-intro">{{ config().schedule_intro }}</p>
    </div>
Author	SHA1	Message	Date
kfj001	da02687260	Merge pull request 'fix(seo): use h1 as primary heading on about, schedule, events, and contact pages' (#3 ) from fix/seo-heading-hierarchy into main CI Pipeline / backend-test (push) Successful in 4m24s Details CI Pipeline / frontend-test (push) Successful in 27s Details CI Pipeline / frontend-build (push) Successful in 29s Details CI Pipeline / backend-lint (push) Successful in 9s Details CI Pipeline / quality-gate (push) Successful in 2s Details Reviewed-on: kfj001/kmtnflower#3 Reviewed-by: kfj001 <kfj001@gmail.com>	2026-08-04 02:54:18 -07:00
robot	b7e67fa244	fix(seo): use h1 as primary heading on about, schedule, events, and contact pages CI Pipeline / backend-test (pull_request) Successful in 4m38s Details CI Pipeline / frontend-test (pull_request) Successful in 31s Details CI Pipeline / frontend-build (pull_request) Successful in 30s Details CI Pipeline / backend-lint (pull_request) Successful in 9s Details CI Pipeline / quality-gate (pull_request) Successful in 1s Details Each public page now has exactly one <h1> element for proper semantic heading hierarchy: - About: 'About [Station Name]' (h1), with subsection h2s for History/Team - Schedule: 'Program Schedule' (h1) - Events: 'Upcoming Events' (h1) - Contact: 'Get in Touch' (h1) The home page hero component already used <h1>, as did login and admin.	2026-08-04 09:26:48 +00:00