Context
Some event-driven content is rendered with Tailwind Typography prose, but nearby hardcoded text uses different typography tokens. This causes visible mismatches in font/color/spacing.
Why defer
Per docs/multi-event-restructure-plan.md, we should finish the multi-event restructure first, then do styling harmonization in one pass.
Scope for later
- Find all markdown-rendered blocks using
prose and align them with surrounding typography.
- Add a global Tailwind Typography configuration (
theme.extend.typography) so prose matches project fonts/colors (including dark mode).
- Fix markup edge cases where
prose appears inside wrappers that affect semantics/layout.
Known starting points
resources/views/components/home-content.blade.php
resources/views/pages/questions-and-answers.blade.php
resources/views/components/faq-question-answer.blade.php
tailwind.config.js
Context
Some event-driven content is rendered with Tailwind Typography
prose, but nearby hardcoded text uses different typography tokens. This causes visible mismatches in font/color/spacing.Why defer
Per
docs/multi-event-restructure-plan.md, we should finish the multi-event restructure first, then do styling harmonization in one pass.Scope for later
proseand align them with surrounding typography.theme.extend.typography) soprosematches project fonts/colors (including dark mode).proseappears inside wrappers that affect semantics/layout.Known starting points
resources/views/components/home-content.blade.phpresources/views/pages/questions-and-answers.blade.phpresources/views/components/faq-question-answer.blade.phptailwind.config.js