News v2: scheduled publishing (auto-appear at publish date) #78

Open
opened 2026-07-17 19:03:14 +02:00 by dominik.polakovics · 0 comments

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.

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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Cloonar/deckle#78
No description provided.