A sequence without a calendar
The technical blog now keeps its sequence without displaying publication dates. That is a deliberate presentation choice. Readers can follow the development of the website through the hub and the earlier and later entry links, while the underlying project record continues to preserve the evidence for that order.
The change removed more than a date label above an article. Month headings and month navigation also carried a calendar structure, and the structured data exposed dates separately from the visible page. Keeping an undated interface therefore required checking both what a visitor reads and what a machine can extract.
One record supports two different views
The internal source records retain their dated evidence and ordering information. The public generator uses that sequence to build the hub and neighbouring-entry links. It does not publish the internal evidence ledger or its operational file paths. The order is reproducible without exposing the working record.
This separation gives a maintenance check a precise job. It can compare the generated hub against the source order and test the earlier and later links, then separately check that calendar labels and date properties have not returned. A familiar date hidden in structured data would still break the public contract even if the visible page looked right.
Metadata must follow the editorial choice
The public BlogPosting records describe the title, summary, author, publisher and canonical page. They intentionally omit publication and modification dates. The blog remains outside the sitemap and carries its existing noindex instruction. These choices do not imply that the underlying work lacks a history, and they do not make a claim about search performance.
The date-removal release checked the hub, post pages, chronology, structured data and preserved private surface before public read-back. The same distinction applies to this entry: it adds a new point to the technical sequence without restoring public calendar signals. A later change to the presentation must preserve both the reading path and the evidence that makes the sequence defensible.
Evidence for this entry
This account is grounded in project records. Internal research and operational files are not published here.
What the records support
- Release 9e7bda2 removed public date labels and date metadata, retained internal sequence, and verified chronology, noindex and protected content.