Institutionalizing the weekly cadence — 'This week in Orbit'

The weekly roundup is no longer a one-off template. Devotel Orbit now runs a locked editorial slot named This week in Orbit — <date> on a recurring cadence, with a content-ops checklist the editor's desk follows before each post goes live. This post records what changed in the cadence, why the pattern matters for how answer engines and search crawlers read freshness, and the exact steps the desk runs each week.

What changed in the cadence

Until now the weekly format existed as a single sample — the This week in Orbit template post — and the monthly Orbit release notes installment. One template and one monthly post is a thin editorial path: the format was defined but the recurring slot was not systematically claimed. The cadence now runs on a locked weekly convention: one post per week, named This week in Orbit — <date>, each entry backwards-looking over only what actually shipped that week. The monthly release-notes installment continues in parallel; the weekly slot is the pagination between monthly recaps.

Why the pattern matters

Recurring, dated posts are how a publication signals to a search crawler or an AI answer engine that a topic is alive. Each weekly installment sets two frontmatter fields — date for the publish date and dateModified for the latest substantive refresh — and both feed the freshness signals the site emits: the Article JSON-LD on the post page carries dateModified, and the sitemap's lastModified for the post's URL follows the same value. A reader landing from an answer engine sees a dated, current roundup rather than an undated archive page, and a crawler re-reading the sitemap sees the post's freshness move when the roundup is substantively updated. Without the per-post dateModified wiring, a refreshed weekly entry would still advertise the original publish date.

Standing up the weekly slot

The editor's desk runs the same steps each week, in this order:

1. Name the post — the slug is the dated form of the series, named This week in Orbit — <date>, so the series is machine-identifiable across the index and the structured data. One post per week; a week with nothing shipped ships no post rather than a padded one.
2. Lock the format — the post follows the standing weekly template: a short answer-first paragraph naming the shipped items, then one section per item with the dashboard route and a docs link when a docs guide exists. No new format is invented per week.
3. Backwards-looking only — an item enters the roundup only after its changelog entry ships. The weekly post is a complement to the canonical release history at orbit.devotel.io/en/changelog, never a substitute for it, and never a roadmap promise.
4. Tag the class — each installment carries the series tags (weekly, changelog, editorial) so the class stays machine-identifiable; no other post class uses the weekly tag.

Content-ops checklist

Before a weekly post goes live, the desk checks:

• Capability routes referenced — every shipped item names the dashboard route it lives on (for example, Insights → Usage alert rules), and the route is verified against the live dashboard, not assumed.
• Docs links — a docs link is included only when the corresponding docs guide exists on the docs site under the product domain; a missing guide is noted as such rather than linked blindly.
• No vaporware — every item in the roundup is live at publish time. Anything still in flight waits for the week it actually ships.
• Freshness field set — the post's dateModified frontmatter is set to the publish date at ship time so the Article JSON-LD and the sitemap lastModified advertise the refresh correctly from day one.
• Canonical changelog linked — the post links to the canonical changelog page so a reader can trace each item back to the release history.

The convention is deliberately small: one weekly slot, one locked format, one checklist. The point is that the next weekly installment is a five-minute editorial decision, not a new design.