A month-grid calendar over a 21-day planning horizon. Each day the planner finds publish-day slots inside the horizon that nothing occupies, takes the top unlocked posts off the queue and stamps them with a date and an auto_planned flag. Anything beyond the horizon stays deliberately open. Dragging a chip to a different day clears the auto flag, which makes that date permanent.
Also called: content calendar · publishing schedule · editorial calendar · blog planning
- 1planContentWindow() runs daily from the SEO cron and needs no external data.
- 2Slots are publish days in the next 21 that no scheduled or published post already occupies.
- 3The backlog is ranked by rankQueue and filtered to unlocked posts only.
- 4Each fill writes scheduled_for and auto_planned = true, so the planner can identify its own decisions later.
- 5Dragging a post in the panel sets auto_planned = false — the planner and the implementer both refuse to move it after that.
- 6The pass is idempotent: it only ever fills empty days.
The migration behind it states the change: "The plan stops being fixed months ahead: keywords carry their 12-month search rhythm, the planner keeps only ~3 weeks scheduled, and everything else waits in a live-ranked queue." A fixed six-month calendar is wrong the moment demand shifts, and it was — the same migration pulled every far-future date back into the queue. The auto_planned flag exists so the machine can undo its own decisions without ever overriding a person's.
- A fixed long-range calendar goes stale as demand moves.
- Nothing distinguished a machine-set date from a human's deliberate one.
- Empty publish slots went unnoticed until the week they arrived.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →