Skip to main content
Back to blog

Institutionalizing the weekly cadence — 'This week in Orbit'

Devotel Orbit now runs a weekly roundup series — 'This week in Orbit — <date>' — a dated, backwards-looking index of what shipped each week, with per-post freshness metadata so answer engines see current entries.

Orbit Editorial Team

The weekly roundup is no longer a one-off template. Devotel Orbit now publishes a weekly series — This week in Orbit — <date> — that indexes what shipped each week and links every item back to the dashboard it lives on. This post covers what the series is for, how the freshness fields on each installment reach answer engines and search crawlers, and what each weekly entry contains.

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 publication path: the format was defined but the weekly slot ran irregularly. The series now runs 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 series is the pagination between monthly recaps.

Why the weekly series publishes date and dateModified

Recurring, dated posts are what let a search crawler or an AI answer engine recognize a topic as current. Each weekly installment publishes two dates — date for the publish date and dateModified for the latest substantive refresh — and both become signals the site emits: the Article structured data 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 entry's freshness move when the roundup is substantively updated. For you as a reader, that means the weekly roundup you find in search is the current week's entry — not a stale copy of an earlier installment.

What a weekly installment contains

Every installment follows the same format:

  1. A short answer-first opening naming the week and what shipped, two or three sentences so the page answers the question before it expands on it.
  2. One section per shipped item, each naming the dashboard route the capability lives on (for example, Insights → Usage alert rules) with a link to the docs guide when one exists.
  3. Backwards-looking only — an item enters the roundup only after it ships and appears in the changelog. The series complements the canonical release history at orbit.devotel.io/en/changelog; it never substitutes for it and never makes roadmap promises.

How the dates drive ordering and freshness

The scheduled dates on each installment decide how readers and crawlers encounter the series:

  • Ordering. The blog index lists posts newest-first by publish date. Reading the series in sequence reads the product's history chronologically; jumping to the top of the index lands on the current week.
  • Freshness signaling. The post page's Article structured data carries dateModified, and the sitemap's lastModified for the post's URL follows dateModified when the entry is refreshed, falling back to the publish date otherwise. Answer engines weight freshness when deciding what to cite — a dated, current roundup gets cited where an undated page does not.

The publish date never moves after publication; the refresh date moves only when the roundup is substantively updated — never on a typo fix.

How to use the weekly series

  • Scan the week's shipped items — each entry names the dashboard route it lives on, so you can jump straight to the capability rather than hunting through the navigation.
  • Follow the docs links — entries link to the corresponding guide when one exists; an item without a guide is stated as such rather than linked blindly.
  • Trace back to the release history — the weekly series links to the canonical changelog page, so every item can be traced back to its entry in orbit.devotel.io/en/changelog.
  • Catch up on a missed week directly in the blog index — posts are listed newest-first, so the entries since your last visit sit together at the top.

The series is deliberately small: one weekly roundup, one fixed format, one canonical release history. Reading the current installment is a five-minute weekly habit that keeps you current on what Orbit shipped.

Institutionalizing the weekly cadence — 'This week in Orbit' — Orbit by Devotel