Replies: 3 comments
|
Status (April 2026): Partially done. Done:
Not done:
|
Remaining work decomposed into issuesReviewed the current codebase against the 4-phase plan. Most of the infrastructure and display work (Phases 1, 3A, 4A-C) is already done. The main gap is data coverage — the enrichment pipeline works but hasn't been run at scale. Completed phases
New issues for remaining work
Related existing issues
|
|
Branch: Status check (2026-04-08): Frontmatter still reads |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Problem
Resource tables across the site (legislation press tabs, org coverage, etc.) are underutilizing data we already have. Key issues:
Example: https://www.longtermwiki.com/legislation/california-sb1047?tab=press
Plan: 4 Phases, 13 PRs
Phase 1: Quick Wins (show data we already have)
OrgResourceRow/ResourceRowinto sharedResourceDisplayRowtypefetchStatus,archiveUrl,authorEntityIdsthrough build pipeline intodatabase.jsonPhase 2: Data Enrichment
authorEntityIds(data exists in PG, just not exposed)publications.yamldomain listsextractDateFromUrl()on legislation press tab (already works on org pages)Phase 3: Legislation-Specific
stancefield (support/oppose/neutral) with LLM classification pipelinePhase 4: Card Redesign
ResourceCard+ResourceListcomponents replacing inline tablesDependency Graph
Key Data Gaps
authorEntityIdsfetchStatusarchiveUrlsummary/abstractAll reactions