Status: draft, incomplete — covers what is known as of 2026-10-11.
What each tool did with the copyright year and the “last updated” date. A summary across tools comes first, then one section per tool, then what the tools share, the open question about the copyright year, and the conventions to record. How the pages were chosen and what the terms mean: README. How the book sets these values today: survey.
How to read the results:
access-control after conversion (author 2026-10-05, committer
2026-10-07).All builds ran on 2026-10-11 with the earlier rounds’ tool versions (Docusaurus 3.10.2, Zensical 0.0.69, Starlight 0.42.6, Antora 3.2.1).
Every tool prints a copyright notice with any of the three years, and every tool shows a “last updated” date written in the page. They differ in how much code the footer needs and in whether the tool reads dates from Git; where it does, the date is the conversion commit’s.
| Docusaurus | Zensical | Starlight | Antora | |
|---|---|---|---|---|
| Check, build / site / page | 4 of 4 each | 4 of 4 each | 4 of 4 each | 4 of 4 each |
| Footer year from the build | config (JavaScript) | not in the tool: make writes the year into a copy of the config |
footer component override (Astro) | the default UI’s year helper, in a replaced footer template |
| Footer year from the site’s content | SITE_YEAR read by the config |
the same config copy | SITE_YEAR in the override |
{{env.SITE_YEAR}} in the template |
| Year per page | a wrapped theme component (React) | the copyright template reads revision_date |
the same override reads the page’s date | the template, plus a one-line helper |
| Date written in the page | last_update.date |
revision_date |
lastUpdated |
:page-last-updated: and the template |
| Date from Git, by the tool | committer date; production builds only | none (the MkDocs plugin is dropped without a message) | committer date | none |
| History, native | 0 of 4: conversion or newest commit | 0 of 4: no date | 0 of 4: conversion or newest commit | 0 of 4: no date |
| History, helper | 4 of 4 | 4 of 4 | 4 of 4 | 4 of 4 |
| Shallow clone | every page dated by the newest commit | — | every page dated by the newest commit | — |
| Skip listed commits | with a custom VCS (experimental API): 1 of 4, no rename following | — | no | — |
Sitemap lastmod |
none by default | none | not tested (build warnings) | the build time, on every page |
buildtime.py --compare
takes the notice and the dates out of both pages and lists them apart;
what remains on access-control is the published page’s quick links,
its GitHub link and curly quotes, as in the headings round
(comparison).Site: sites/docusaurus/ — conventions: CONVENTIONS.md.
last_update.date in front matter wins over Git, and Git is then
not asked (lastUpdateUtils.ts L64-L96).%ct) of the newest commit to the
file, without rename following
(gitUtils.ts L148-L160):
access-control shows C6’s committer date, 2026-10-07, where Bookbinder
would show its author date, 2026-10-05.vcsDefaultV1.ts L13-L16).future.experimental_vcs,
configValidation.ts L355-L360).
With the conversion commit listed, the three pages whose earlier
history is under their old name get no date at all.| Mode | access-control | architecture | using-vol-services | high-availability |
|---|---|---|---|---|
| build, site, page | ok | ok | ok | ok |
| history, native | 2026-10-07 (C6, committer date) | 2026-10-01 (C5) | 2026-10-01 (C5) | 2026-10-01 (C5) |
| history, helper | ok | ok | ok | ok |
| history, shallow | 2026-10-07 | 2026-10-07 | 2026-10-07 | 2026-10-07 |
| history, vcs | ok | no date | no date | no date |
“ok” is the check: the year, the holder and the date as the intent says (check, history).
Site: sites/zensical/ — conventions: CONVENTIONS.md.
config.py L332, L533).
The build writes the year into a copy of the configuration
([project.extra]), and an overridden template prints it. Per page, the
template reads revision_date: no code.revision_date in front matter is shown as “Last update”, as written
(source-file.html L86-L89).config.py L1929-L1930;
probe).{#prerequisites} (“Missing end of comment tag”).| Mode | access-control | architecture | using-vol-services | high-availability |
|---|---|---|---|---|
| build, site, page | ok | ok | ok | ok |
| history, native | no date | no date | no date | no date |
| history, helper | ok | ok | ok | ok |
Site: sites/starlight/ — conventions: CONVENTIONS.md.
Footer component adds
one, with any of the three years
(user-config.ts L271).lastUpdated in front matter wins over Git, and shows even with the
option off
(routing/data.ts L79-L86).git.ts L58-L68).
Native and shallow give the same dates as Docusaurus.LastUpdated.astro L9-L10).| Mode | access-control | architecture | using-vol-services | high-availability |
|---|---|---|---|---|
| build, site, page | ok | ok | ok | ok |
| history, native | 2026-10-07 (C6, committer date) | 2026-10-01 (C5) | 2026-10-01 (C5) | 2026-10-01 (C5) |
| history, helper | ok | ok | ok | ok |
| history, shallow | 2026-10-07 | 2026-10-07 | 2026-10-07 | 2026-10-07 |
Site: sites/antora/ — conventions: CONVENTIONS.md.
year.js L3).
A replaced footer template prints the notice; it reads the environment
({{env.YEAR_MODE}}) and the page’s attributes
(build-ui-model.js L13, L70).
A year per page takes a one-line UI helper.docdate is the build date, or SOURCE_DATE_EPOCH’s
(document.rb L1256-L1270;
probe).lastmod
(map-site.js L50);
SOURCE_DATE_EPOCH does not change it.| Mode | access-control | architecture | using-vol-services | high-availability |
|---|---|---|---|---|
| build, site, page | ok | ok | ok | ok |
| history, native | no date | no date | no date | no date |
| history, helper | ok | ok | ok | ok |
The RFC moves all content into one repository (L69) and converts it centrally (L131). A Git-based date then needs the history before the conversion, and it needs Git to connect each converted file to its old one:
git log --follow connected access-control, converted whole, to its
old file; it did not connect the three excerpts
(follow probe). How many real pages would
pass Git’s 50% similarity after conversion was not measured.actions/checkout, which a GitHub Pages
workflow (L53) usually runs, fetches one commit by default
(action.yml L74-L76).
In the shallow builds every page showed the newest commit’s date.So the dates that exist today can reach the converted pages in two ways: the converter writes each page’s date into the page (all four tools show it), or the converted files keep a Git history that the build follows. Only the first was made to work here in every tool.
Bookbinder uses the author date
(git_accessor.rb L81);
Docusaurus and Starlight use the committer date. They differ when a
commit is rebased or cherry-picked: C6’s author date is 2026-10-05 and
its committer date 2026-10-07. Decision (this round): the helper uses the
author date, as Bookbinder does.
new Date(), date +%Y, the UI’s year helper). Builds in the hours
around New Year depend on the machine’s time zone.R-25 build-time values are expected
differences: buildtime.py --compare lists the
copyright year and the date of both pages, then compares the main text
without them (comparison):
access-control matches at 0.976–0.982 in the four tools
(Python’s difflib ratio over the words: 1.0 is identical).
The differences left are not build-time values: the published quick
links, its “Create a pull request” line and curly apostrophes; and, in
Starlight, the title, which is outside <main>.The open question (research area). This section lays out observations for each answer. It is not legal advice; the Docs WG may want the Cloud Foundry Foundation’s view, as the research area says.
The footer prints the build’s year, “© 2026 Cloud Foundry Foundation”
(_book-footer.erb L3).
The repositories’ NOTICE files say “YYYY-Present”, with first years from
2013 to 2019 (survey).
Under the RFC, every merge rebuilds and redeploys the site
(L83), so a build-year footer changes year with the first merge of each
year.
| Answer | What the footer says | Observed elsewhere | What this round found |
|---|---|---|---|
| A. The build’s year (today) | the year of the newest deploy | kubernetes.io: © {{ now.Year }}, Hugo’s current time (center.html L1-L2); Docusaurus’s site template (L149); cloudfoundry.org’s footer shows “©2026” (fetched 2026-10-11) |
works in all four tools; a format-only rebuild in a new year changes the year; builds differ by date alone, so a comparison must mask it |
| B. The newest content year on the site | the year of the newest content date | Sphinx replaces %Y with the current year, or with SOURCE_DATE_EPOCH’s year when that is set, citing the Reproducible Builds specification (config.py L694-L723) |
works in all four tools with the helper; it needs a decision about which commits are content (the candidate list) and a full history or dates in the pages; in 2026 it equals A |
| C. Each page’s content year | a year per page, with its date | not seen on the sites checked | works in all four tools; costs code in Docusaurus (a theme component) and Starlight (an override), a template in Zensical and Antora; years range 2023–2026 on the test pages |
| D. The first year, or a range to “Present” | for example “© 2015–Present” or “© 2001” | docs.python.org: “© Copyright 2001 Python Software Foundation”, and a separate build time, “Last updated on Oct 11, 2026” (fetched 2026-10-11; conf.py L74); the repositories’ NOTICE files |
a fixed string: no build-time value at all, nothing to mask |
| E. No year | for example “Copyright The Cloud Foundry Authors” | CNCF recommends notices without years for contributions to its projects, to avoid “years or ranges of years” (copyright-notices.md L19-L38) |
a fixed string |
Public statements that bear on the question:
copyright-notices.md L78-L82).community
2020). The Foundation’s charter, effective 2023-09-15, is a Linux
Foundation charter (L1-L12), and
trademarks are held by LF Projects, LLC or the Linux Foundation
(L263), so whether that
company still holds the copyright is for the Foundation to say.Observations from this round’s data:
Decision (Docs WG lead, 2026-10-11): B, the newest content year on the site, computed by the same helper that sets page dates, so a format-only conversion never moves the year; D if the Foundation prefers a fixed notice.
For cf-docs-migrate convert and the site build. Decisions of this round,
for review:
<time datetime>, as Bookbinder’s data-modified-date), and date
<meta> tags, listed apart as expected differences:
checks/buildtime.py --compare
(R-25 build-time values are expected
differences).last_update.date (Docusaurus), revision_date
(Zensical), lastUpdated (Starlight), :page-last-updated: (Antora).
The converter writes it once, from the page’s history before
conversion.using-vol-services is such a page: its
file’s date is 2023-05-31, its partial’s 2025-03-27 with the
candidates skipped. content-date.py does
this with --git: a page whose body holds only include calls, in any
of the four tools’ forms, also takes its partials’ dates
(test-content-date.py). On the
round’s history repositories it prints the same dates as before..git-blame-ignore-revs
in the docs repository: the conversion commits, and bulk markup
commits after review of candidates.txt. Git
(blame.ignoreRevsFile)
and GitHub’s blame view
(GitHub Docs)
read the same file. Accepted (Docs WG lead, 2026-10-11): the
central migration team reviews the list once before conversion; the
Docs WG owns it afterwards.--write):
the later of the written date and the newest listed-not-skipped
commit. The tools’ own Git lookups are not relied on. Decision
(Docs WG lead, 2026-10-11): compute the date at build first;
whether the updated dates are also committed is decided after the
proof of concept.fetch-depth: 0 for actions/checkout).YEAR_MODE: build,
site or page), so the decision on the open question changes one value.
Which value is the open question (above).
Set to site, answer B (Docs WG lead, 2026-10-11).lastmod is the content date or absent, never the build
time (R-20 search-engine and
AI-friendly output): Antora’s default
does not meet this; Docusaurus’s sitemap plugin can take the content
date (lastmod option), not tested.--expect.Last-Modified header and a serve-time style block,
which are not page text (survey).access-control keeps its text in every tool; the remaining
differences are known from the headings round.itemprop="dateModified"
(LastUpdated/index.tsx L37);
Antora’s sitemap gives every page the build time.using-vol-services takes the date
of its six-line file; whether such a page should take its partial’s
date, or the newest of both, is open. Decided (Docs WG lead,
2026-10-11): the newer of both when the partial holds the text
(convention 3); the helper does it as of
2026-10-11, checked by test-content-date.py.lastmod option and
Starlight’s sitemap integration were not tried; Zensical lists no page
without site_url (sitemaps).Last-Modified header (2026-10-09) is the only sign of when it last
ran (unverified as the build time).%Y and SOURCE_DATE_EPOCH
handling and Hugo’s now.Year (kubernetes.io) are cited from source
only.