kmtnflower

6 Commits

Include renames

Author	SHA1	Message	Date
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
kfj001	d2ab2240d5	transforms landing, about and schedule page content to data driven	2026-07-01 03:24:30 +00:00
kfj001	2d2b2d040b	additional files	2026-06-19 17:37:19 +00:00
kfj001	e5fef8b181	working 3 tier approach	2026-06-11 22:34:55 -07:00
kfj001	fd228896ea	fixes svg file pathing	2026-06-11 17:31:44 +00:00
kfj001	771e1e166f	first pass - kryz inspired	2026-06-10 18:34:23 +00:00