News v2: scheduled publishing (auto-appear at publish date) #78
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Cloonar/deckle#78
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Deferred from the news-system design discussion (2026-07-17).
News v1 sets buildFuture=true so a future-dated news item is visible immediately once published — what the editor sees is what is live, no silent disappearance (Hugo's default buildFuture=false would hide future-dated content until some later rebuild happens to occur).
Real scheduled publishing would mean: item stays hidden until its datetime, then appears automatically. Since deckle sites are static and only rebuild on publish/deploy, this requires a rebuild trigger, e.g. a generated CI cron workflow that rebuilds periodically (with buildFuture back to false), plus editor UX marking items as 'scheduled'.
Needs triage: whether the CI-cron cost/cadence trade-off is wanted, and how preview should treat scheduled items.