Clarify Gospel-pericope/homily rendering as a decided design, not open
Deploy / deploy (push) Successful in 1m26s
Deploy / deploy (push) Successful in 1m26s
The pairing of a Nocturn 3 Gospel pericope with its patristic homily should render as two distinct, visually-distinguished parts rather than one concatenated lesson; bible-plan Gospel readings stay pericope-only. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D1LqodVbQdQVoTGPz9sSw4
This commit is contained in:
@@ -20,9 +20,13 @@ across every hour and content type in this app.
|
|||||||
1. **Mechanism gaps** — a real design/code piece not built yet, blocking any content pass on
|
1. **Mechanism gaps** — a real design/code piece not built yet, blocking any content pass on
|
||||||
it from starting:
|
it from starting:
|
||||||
- Easter's own octave — tabled, "a whole different discussion."
|
- Easter's own octave — tabled, "a whole different discussion."
|
||||||
- What "a Gospel reading is its own kind" should mean structurally/in the UI, beyond the
|
- Gospel pericope + paired homily rendered as one part: decided, not yet built. When a
|
||||||
`isGospel` flag on a plain Matins `lesson` — open; deferred until there's a UI to
|
Matins Nocturn 3 reading pairs a Gospel pericope with a patristic homily on it, render them
|
||||||
evaluate it against.
|
as two distinct parts, one after the other, with markup that visibly distinguishes pericope
|
||||||
|
from homily (not concatenated into a single `lesson` text as now). A bible-plan Gospel
|
||||||
|
reading has no paired homily — it renders as just the pericope, which is correct as-is.
|
||||||
|
Needs a schema change (splitting `lesson`+`isGospel` into a Gospel part with an optional
|
||||||
|
homily part) and matching UI treatment in `hour-view.ts`.
|
||||||
- Date picker: `day-nav.ts` currently only steps a day at a time (prev/next); there's no
|
- Date picker: `day-nav.ts` currently only steps a day at a time (prev/next); there's no
|
||||||
way to jump to an arbitrary date without walking there one day at a time or editing the
|
way to jump to an arbitrary date without walking there one day at a time or editing the
|
||||||
URL. Needs a calendar-grid picker UI — open, not started.
|
URL. Needs a calendar-grid picker UI — open, not started.
|
||||||
|
|||||||
Reference in New Issue
Block a user