Problem
The current press implementation is a functional v1, but it still needs production-readiness work around publishing flow, resilience, and editorial usability.
Scope
- Add clearer empty/loading/fallback states for
/press and /press/[slug]
- Review SEO behavior for press posts (metadata, Open Graph, canonical data, sitemap inclusion if applicable)
- Make sure spotlight/list queries degrade safely when spotlight content is incomplete
- Add a clear published-only content strategy so drafts do not create confusing public behavior
- Evaluate whether the index needs category filtering, pagination, or stronger archive navigation once content volume grows
Acceptance Criteria
- The press area behaves predictably when spotlight content is missing or partially configured
- Published content and draft content have an intentional separation
- Press pages have solid metadata defaults and social-sharing behavior
- The editorial workflow is documented enough that future content additions do not require code intervention
Problem
The current press implementation is a functional v1, but it still needs production-readiness work around publishing flow, resilience, and editorial usability.
Scope
/pressand/press/[slug]Acceptance Criteria