Description
Currently, content with a publishedAt date set in the future is still displayed on the frontend. We should respect the publishedAt field and filter out content that hasn't reached its publish date yet.
This would enable editors to schedule content for future publication by setting a publishedAt date in the future.
Collections affected
- Posts (used for blog sorting and date display)
- Pages
- HomePages
What needs to happen
- Frontend queries should filter by
publishedAt <= now (or publishedAt is null/not set)
- Consider whether this should also apply to ISR/caching — content with future dates would need revalidation when the publish date arrives
- Consider adding a "Scheduled" status indicator in the admin UI for content with future publishedAt dates
Context
Raised while working on #878 (publishedAt field standardization). The Pages collection previously had a misleading description claiming publishedAt "affects the page's visibility and can be used for scheduling future publications" — but this was never actually implemented.
Description
Currently, content with a
publishedAtdate set in the future is still displayed on the frontend. We should respect thepublishedAtfield and filter out content that hasn't reached its publish date yet.This would enable editors to schedule content for future publication by setting a
publishedAtdate in the future.Collections affected
What needs to happen
publishedAt <= now(orpublishedAtis null/not set)Context
Raised while working on #878 (publishedAt field standardization). The Pages collection previously had a misleading description claiming publishedAt "affects the page's visibility and can be used for scheduling future publications" — but this was never actually implemented.