Jonathan Hvid
1518bfa3d3
Two things lifted off /pulse in the follow-up pass need somewhere to live so they aren't forgotten: - The 'Recently from the council' feed (RecentlyFromTheCouncil reading from the contributions table). Component and underlying table stay in place; only the /pulse embed is gone. Records the options for re- introducing it: inline in the Latest-from-Fenja card, a dedicated Voices section further down, or stop surfacing on the home page. - 'This week's pulse' voting card. pulses/votes schema + admin Pulses tab stay. Records the merge-into-dispatches idea — fold poll-shaped dispatches into the Latest from Fenja stream rather than rebuilding a parallel block. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
43 lines
1.9 KiB
Markdown
43 lines
1.9 KiB
Markdown
# Todo
|
||
|
||
Deferred from the Phase 2 home-page simplification (commits after `ed2c272`).
|
||
|
||
## Recently from the council (the feed)
|
||
|
||
Removed from `/pulse` in this pass. Currently no surface for member-authored
|
||
contributions on the home page.
|
||
|
||
The underlying `contributions` table, the `RecentlyFromTheCouncil` component,
|
||
and the existing `/contribute` page all remain in place — only the home-page
|
||
embed is gone.
|
||
|
||
When we revisit this, options to consider:
|
||
- Inline a compact "What members are saying" row inside the
|
||
Roadmap + Latest from Fenja card — single quote, smallest possible
|
||
treatment, doesn't repeat dispatch real-estate.
|
||
- A dedicated Voices / Council notes section much further down the page
|
||
with a stronger editorial frame.
|
||
- Surface contributions only on the dedicated /contribute page (already
|
||
exists) and rely on dispatches as the primary "what's moving" signal.
|
||
|
||
## This week's pulse voting block
|
||
|
||
Removed from `/pulse` in this pass. The `pulses`, `votes`, vote-uniqueness
|
||
constraint, admin Pulses tab, and the activity `voted` kind all remain — only
|
||
the on-page voting card is gone.
|
||
|
||
**Idea worth trying:** rather than rebuild as its own block, fold polling
|
||
into the "Latest from Fenja" stream. A dispatch can be tagged as a poll
|
||
(one of the existing kinds, or a new `poll` kind) and rendered inline with
|
||
the 2–4 vote options + locked state + result bars. Single editorial channel
|
||
instead of two competing "what should I read first" surfaces on the home page.
|
||
|
||
If we go that way:
|
||
- Schema: extend `dispatches` with a nullable `pulse_id` foreign key (or
|
||
embed options on the dispatch directly).
|
||
- Render: when a dispatch is poll-shaped, its excerpt block becomes the
|
||
Pulse question + options; the "Read the full dispatch" affordance can
|
||
stay for context/comments.
|
||
- Admin: a checkbox on the dispatch form ("Attach an active poll") +
|
||
inline options inputs. No need for the standalone Pulses tab once this
|
||
lands — fold it in.
|