131Notice

The dated line at the top of a post that has changed since it was published. Technical writing rots — a post about a platform that ships three releases a year is wrong within eighteen months, and the reader has no way to know unless the page says so.

Use it for

A post you have revised: what changed, and when
--archive for a piece kept for its inbound links but no longer true

Not for

A callout — that is an aside about the paragraph beside it; this is a statement about the whole document, so it spans the measure above the prose
A correction. A correction is a sentence saying what was wrong, and it belongs in the text
“Recently updated”. Either you have the date or you do not have the claim

Updated

markup

<aside class="ns-notice">
  <i class="ph ph-clock-clockwise" aria-hidden="true"></i>
  <div>
    <time class="ns-notice__date" datetime="2026-08-12">Updated 12 August 2026</time>
    <p class="ns-notice__text">Rewritten for API v62. The <code>Database.Stateful</code> workaround in the original is no longer needed — batch context now survives the callout.</p>
  </div>
</aside>

Superseded

Kept because other people linked to it. The reader deserves to know that before they act on it, not after.

markup

<aside class="ns-notice ns-notice--archive">
  <i class="ph ph-warning" aria-hidden="true"></i>
  <div>
    <time class="ns-notice__date" datetime="2024-03-01">Superseded &middot; March 2024</time>
    <p class="ns-notice__text">This describes the old Process Builder migration path. Start from <a href="#0">the Flow migration guide</a> instead.</p>
  </div>
</aside>

Accessibility contract

A real <time datetime>, so the date is machine-readable and gets localised rather than being a string that says August to everyone
The amber on --archive is a border and a label colour, never the only signal: the word Superseded carries it