Fix heading hierarchy in HTML templates for proper SEO semantics. Each public page should have exactly one <h1> as the primary heading.
Changes
File
Change
src/app/about/about.component.html:6
<h2>About... → <h1>About...
src/app/schedule/schedule.component.html:5
<h2>Program Schedule → <h1>Program Schedule
src/app/events/events.component.html:5
<h2>Upcoming Events → <h1>Upcoming Events
src/app/contact/contact.component.html:5
<h2>Get in Touch → <h1>Get in Touch
Heading hierarchy after fix
Each public route now has exactly one <h1>:
Home (hero): <h1> with station name — unchanged
About: <h1> + <h2> subsections (History, Team)
Schedule: <h1> only
Events: <h1> only
Contact: <h1> only
Login: <h1> "Sign In" — unchanged
Admin: <h1> "Admin Dashboard" — unchanged
## Summary
Fix heading hierarchy in HTML templates for proper SEO semantics. Each public page should have exactly one `<h1>` as the primary heading.
## Changes
| File | Change |
|------|--------|
| `src/app/about/about.component.html:6` | `<h2>About...` → `<h1>About...` |
| `src/app/schedule/schedule.component.html:5` | `<h2>Program Schedule` → `<h1>Program Schedule` |
| `src/app/events/events.component.html:5` | `<h2>Upcoming Events` → `<h1>Upcoming Events` |
| `src/app/contact/contact.component.html:5` | `<h2>Get in Touch` → `<h1>Get in Touch` |
## Heading hierarchy after fix
Each public route now has exactly one `<h1>`:
- Home (hero): `<h1>` with station name — unchanged
- About: `<h1>` + `<h2>` subsections (History, Team)
- Schedule: `<h1>` only
- Events: `<h1>` only
- Contact: `<h1>` only
- Login: `<h1>` "Sign In" — unchanged
- Admin: `<h1>` "Admin Dashboard" — unchanged
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
kfj001
Summary
Fix heading hierarchy in HTML templates for proper SEO semantics. Each public page should have exactly one
<h1>as the primary heading.Changes
src/app/about/about.component.html:6<h2>About...→<h1>About...src/app/schedule/schedule.component.html:5<h2>Program Schedule→<h1>Program Schedulesrc/app/events/events.component.html:5<h2>Upcoming Events→<h1>Upcoming Eventssrc/app/contact/contact.component.html:5<h2>Get in Touch→<h1>Get in TouchHeading hierarchy after fix
Each public route now has exactly one
<h1>:<h1>with station name — unchanged<h1>+<h2>subsections (History, Team)<h1>only<h1>only<h1>only<h1>"Sign In" — unchanged<h1>"Admin Dashboard" — unchanged👍