scavold 0.2.0-rc.4 → 0.2.0-rc.6

package/CHANGELOG.md

@@ -9,6 +9,113 @@ changes may occur in any release.
 
 ## [Unreleased]
 
+## [0.2.0-rc.6] — 2026-09-13
+
+### Added
+
+- `aliases` in a page's front matter names the former addresses it replaces, and
+  `retired_urls` in `.cratly.config.yaml` those that are not coming back. A site taking
+  over from an existing website declares them once and the build writes
+  `cratly-redirects.json` into its output: an address, where it went, and `301` or `410`.
+  The format names no server — only a server-side redirect passes a ranking on, and which
+  server that is cratly does not assume, so the deploy step translates the file for its
+  target. Keeping an address is still better than redirecting to it, which is what `url`
+  is for; the build refuses an alias that two pages claim, or that the site serves itself
+  and the redirect would therefore hide.
+- Every build now ends by reading its own result. A page that the generator listed but
+  never wrote, or a script a built page names and the output does not contain, ends the
+  build with the file named — the two states a bundling fault leaves behind while the log
+  says "build complete". Links and images pointing at absent files are reported and left
+  to the site, since one may legitimately name a path the web server provides. Turn it
+  down with `verify: { content: false }` or off with `verify: false`. A reference is read
+  the way a browser reads it: a relative one against the address of the page holding it, so
+  a link that forgot its protocol — `[Website](./www.example.com)`, which the build turns
+  into a sibling page nobody wrote — is seen as well. Proven against the
+  case-collision that used to build green: the page missing from the output is the only
+  trace it leaves on a file system that ignores letter case, and that is now enough.
+  Everything found also goes to `.cratly/build-report.json`, written before the build is
+  ended rather than after, each entry naming the source file an author would open. A build
+  log is read by whoever has access to it; a file can be handed to whoever wrote the page.
+- `ignoreDeadLinks` now defaults to `true`. VitePress ends a build on a dead link and does
+  so before writing anything, which leaves the reason in a job log that whoever wrote the
+  link often cannot read, and lets one typo stand between a finished page and its
+  publication. Scavold finds the same mistake in the finished output and reports it there
+  instead. Whether it should also stop a pipeline is a question whose answer differs per
+  branch, so it is left to CI: the site template fails a merge request over it and lets the
+  default branch deploy, since blocking there would answer a broken link with a stale site.
+  Ask for VitePress' abort back with `ignoreDeadLinks: false`.
+- A site whose page paths collide in VitePress's eyes now learns that from Scavold, by
+  name, before the build starts. VitePress identifies a page by its path flattened into
+  a single name — slash becomes underscore, and the page-hash map lower-cases it — and
+  uses that name for the page's bundle entry, its server module and its client chunk.
+  Two pages meeting there overwrite each other: either the build dies at render time in
+  `pageChunk.imports`, naming no file, or it succeeds and ships two pages pointing at a
+  script that was never written. Scavold now reproduces that identity when it reads the
+  config and aborts with both file names, whether they collide through an underscore in
+  a file name (`de_kontakt.md` beside `de/kontakt.md`), through letter case alone, or
+  through a `url` alias landing on a path another page already owns as its file — the
+  case the previous alias check, which compared aliases only with each other, let pass.
+- `date` and `datetime` join the type vocabulary of `frontmatter_fields` and of a
+  container's `props`. Scavold passes such a value through as the ISO 8601 text it is;
+  what changes is that the cratly editor now offers a date picker for it instead of a
+  plain text box. A `datetime` always carries an offset — a time of day without one is
+  a different moment on every machine that builds the site.
+
+### Changed
+
+- `@cepharum/vue3-i18n` moves to `2.0.0`, two majors on from the `0.5.4` a site would
+  have installed. Scavold uses `useL10n`, `setLocale` and `setLoader`, none of which
+  changed; what 2.0 breaks are the locale helpers now returning full BCP-47 tags, and
+  Scavold calls none of them. A site inherits the new version with its next install, and
+  gains what 2.0 adds along the way: regional locales overlaying a bare language, plural
+  and gender selection resolved through `Intl`, and `Intl`-backed formatters in
+  placeholders.
+
+### Fixed
+
+- `lib/href.js` ships the declarations it had been missing since it was split out, so
+  `typecheck` passes again — and the pipeline runs it now, which is why it could go
+  unnoticed at all. Nothing about the module changed; TypeScript simply had nothing to
+  read about it, and treated every href the hierarchy composes as `any`.
+
+## [0.2.0-rc.5] — 2026-08-17
+
+### Added
+
+- `:::pagelist` dates its entries the way the site wants them: `time-style` adds the
+  time of day, `timezone` names the zone the timestamps are read in, and both accept
+  `iso` alongside the `Intl` styles, writing `2020-10-20 12:16` in every language. The
+  default is unchanged — the date alone, read in UTC, which is where a front matter
+  value carrying no time of day belongs.
+- `formatTimestamp()` in `scavold/lib/dateFormat.js` renders timestamps the same way
+  for a theme's own components — a byline under a post's title, say. It is free of Vue
+  and VitePress and depends on its arguments alone, so pre-rendered markup and the
+  browser agree.
+
+### Changed
+
+- A `:::pagelist` that paginates reaches every page it found: `limit` now defaults to
+  `0` when `per-page` is set, rather than capping the selection at five entries and
+  leaving a pager to turn the pages of those five. A limit the author sets still wins.
+- Every link a site generates — menus, breadcrumbs, page lists, the feed, redirect targets
+  — names the file the page is built into: `/blog/post.html`, `/blog/index.html`,
+  `/index.html`. Links used to leave the extension off while VitePress's own markdown
+  links carried it, so one site spoke two dialects and the shorter one only worked on
+  servers that go looking for the file. Naming it is answered on the first attempt, and
+  the sitemap now lists the same URLs. The address bar still shows `/` and `/blog/`:
+  VitePress's router shortens them while navigating.
+
+### Fixed
+
+- The site's own `index.md` is no longer linked as `/index`, a URL no server has to
+  answer. The rule for a page's URL existed in three copies and now lives in
+  `lib/href.js` alone.
+- Scavold's built-in translations come from the bundle. They used to be fetched from a
+  URL that no build emits, so every page requested a file that was not there and the
+  interface silently fell back to English, whatever language the site is in.
+
+## [0.2.0-rc.4] — 2026-08-15
+
 ### Added
 
 - `metaChunk` is on by default, keeping VitePress's page-hash map out of the inline
@@ -143,6 +250,8 @@ First published release. Version `0.1.0` existed in-tree only.
 - Only images are processed out of `media_folder`; other file types (video, documents)
   are never copied into the build output and have to live in the static folder.
 
-[0.2.0-rc.3]: https://gitlab.com/cepharum-foss/cratly/scavold/-/compare/v0.2.0-rc.2...v0.2.0-rc.3
-[0.2.0-rc.2]: https://gitlab.com/cepharum-foss/cratly/scavold/-/compare/v0.2.0-rc.1...v0.2.0-rc.2
-[0.2.0-rc.1]: https://gitlab.com/cepharum-foss/cratly/scavold/-/tags/v0.2.0-rc.1
+[0.2.0-rc.5]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.4...v0.2.0-rc.5
+[0.2.0-rc.4]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.3...v0.2.0-rc.4
+[0.2.0-rc.3]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.2...v0.2.0-rc.3
+[0.2.0-rc.2]: https://gitlab.com/cratly/scavold/-/compare/v0.2.0-rc.1...v0.2.0-rc.2
+[0.2.0-rc.1]: https://gitlab.com/cratly/scavold/-/tags/v0.2.0-rc.1

package/COMPONENTS.md

@@ -504,7 +504,7 @@ Which pages are listed:
 | `from-root` | `number` | — | Absolute level from the site root: `1` = top-level pages, `2` = second level. Takes precedence over `from`. |
 | `from-path` | `string` | — | Path of the page whose sub-pages are listed, regardless of where the block sits. Supports the `{locale}` and `{lang}` placeholders. Takes precedence over both other selectors. |
 | `deep` | flag | — | List pages from every level below the selected one, flattened into one list — for posts filed in year or month folders. |
-| `limit` | `number` | `5` | Maximum number of entries. `0` lists every page found. |
+| `limit` | `number` | `5`, or `0` with `per-page` | Maximum number of entries. `0` lists every page found. A paginated list reaches every page it found unless a limit says otherwise. |
 | `offset` | `number` | `0` | Entries to skip at the start, so a second block can continue where the first one ended. |
 | `sort` | `"order" \| "date" \| "date-asc" \| "title"` | `"order"` | `order` follows the site structure (the `order` front matter and file names), `date` is newest first, `title` is alphabetical in the page's locale. |
 | `reverse` | flag | — | Reverse whichever order was selected. |
@@ -516,7 +516,9 @@ What each entry shows:
 | `teaser` | flag | — | Show the introductory text of each listed page. |
 | `images` | flag | — | Show the teaser image of each listed page. |
 | `dates` | flag | — | Show the publication date of each listed page. |
-| `date-style` | `"short" \| "medium" \| "long" \| "full"` | `"long"` | `Intl.DateTimeFormat` style used for the dates. |
+| `date-style` | `"short" \| "medium" \| "long" \| "full" \| "iso"` | `"long"` | Style of the dates. The `Intl.DateTimeFormat` styles follow the page's language; `iso` writes `2020-10-20` in every language. |
+| `time-style` | `"short" \| "medium" \| "long" \| "full" \| "iso"` | — | Style of the time of day. Left out, entries show their date only. `iso` writes `12:16`. |
+| `timezone` | `string` | `"UTC"` | IANA name of the zone the dates are read in, e.g. `Europe/Berlin`. A date carrying no time of day belongs in UTC, the zone the build normalises it into; a list that shows times wants the zone the site publishes from. |
 | `heading-level` | `number` | `0` | Heading level of the entry titles. `0` keeps the entries a plain list of links; use `2`–`6` for teaser cards, one level below the heading above the list. |
 | `image-sizes` | `string` | `"(min-width: 60rem) 30rem, 90vw"` | CSS `sizes` descriptor for the teaser images. Set it to match the column the list is shown in — see [Responsive images](#responsive-images-let-components-own-sizes-not-content-authors). |
 | `label` | `string` | — | Accessible label (`aria-label`) for the list. Set it whenever more than one list appears on the same page so screen readers can tell them apart. |
@@ -706,7 +708,7 @@ Must be called inside a component's `setup` function (or `<script setup>`).
 | `currentLocale` | `ComputedRef<string>` | The resolved locale for the current page. Falls back to the browser locale when no page or ancestor declares one. |
 | `collectLocaleLinks` | `(detection, includeCurrent?) => LocaleLink[]` | Returns available locale links for the current page. See `ScavoldLocaleMenu` for detection mode details. |
 | `resolveByPath` | `(rawPath: string) => HierarchyNode \| undefined` | Resolves a path string to a hierarchy node. Supports `{locale}` (full BCP 47 tag) and `{lang}` (primary language subtag) placeholders. Tries the interpolated path as-is, then with `/index.md`, then with `.md` appended. |
-| `nodeHref` | `(node) => string` | Root-relative link target of a node, preferring its alias URL. |
+| `nodeHref` | `(node) => string` | Root-relative link target of a node, preferring its alias URL. Every page is linked as the file it is built into: `/blog/post.html`, a folder's index page as `/blog/index.html`, the site's own as `/index.html`. |
 | `nodeLabel` | `(node) => string` | Navigation text of a node: `label`, then `title`, then the path segment. For menus and breadcrumbs, where space is scarce. |
 | `nodeTitle` | `(node) => string` | Full text of a node: `title`, then `label`, then the path segment. For entries that stand on their own, such as a teaser heading. |
 
@@ -808,10 +810,34 @@ Spread into `defineProps` to declare all video-related props at once.
 ### `usePageList( props )`
 
 ```js
-import { usePageList, pageListProps } from "./scavold/composables/usePageList.js";
+import { usePageList, pageListProps } from "scavold/composables/usePageList.js";
 ```
 
-Composable for custom page-list components. Resolves the `:::pagelist` container props
+Composable for custom page-list components — the way a theme renders lists its own
+way instead of restyling Scavold's markup. Write a component, declare
+`pageListProps`, call the composable and render whatever the design asks for; map a
+container name to it in the site's configuration:
+
+```yaml
+# .cratly.config.yaml
+containers:
+  postlist:
+    label: "Posts, our way"
+    component: SitePostList
+```
+
+```js
+// .vitepress/theme/index.js — register it after Scavold's own components
+async function enhanceApp( context ) {
+	await scavoldEnhanceApp( context );
+
+	context.app.component( "SitePostList", SitePostList );
+}
+```
+
+Selection, ordering, paging and timestamp rendering stay Scavold's; only the markup
+is the theme's. Registering a component under a name Scavold already uses
+(`ScavoldPageList`) replaces that one everywhere instead. Resolves the `:::pagelist` container props
 into the entries to render, each carrying its link target, title, date, introductory
 text and responsive teaser image data — see the
 [arguments](#scavoldpagelist) for what each prop means.
@@ -833,7 +859,11 @@ argument arrives as `data…`, in the same way as `videoProps`: `dataFrom` for `
 | `dates` | `ComputedRef<boolean>` | `true` when the `dates` flag is set |
 | `imageSizes` | `ComputedRef<string>` | CSS `sizes` descriptor for the teaser images |
 | `ariaLabel` | `ComputedRef<string \| undefined>` | Accessible label for the list, `undefined` when the author set none |
-| `formatDate` | `(isoDate: string) => string` | Formats a timestamp in the page's locale, in UTC |
+| `formatDate` | `(isoDate: string) => string` | Renders a timestamp in the styles and zone the list was given |
+| `page` | `Ref<number>` | Page currently shown, `1` before the browser reads the query |
+| `pages` | `ComputedRef<number[]>` | Page numbers to offer, `[ 1 ]` for an unpaginated list |
+| `pageCount` | `ComputedRef<number>` | Number of pages the selection divides into |
+| `goToPage` | `(page: number) => void` | Turns to a page and remembers it in the URL |
 
 #### `PageListItem` properties
 
@@ -848,6 +878,30 @@ argument arrives as `data…`, in the same way as `videoProps`: `dataFrom` for `
 
 ---
 
+### `formatTimestamp( timestamp, options )`
+
+```js
+import { formatTimestamp } from "scavold/lib/dateFormat.js";
+```
+
+Renders a timestamp the way page lists do, for a theme's own components — a byline
+under a post's title, for instance. Free of Vue and VitePress, so build-time code can
+use it too.
+
+| Option | Type | Default | Description |
+|---|---|---|---|
+| `locale` | `string` | the runtime's | Locale to phrase the result in |
+| `dateStyle` | `"short" \| "medium" \| "long" \| "full" \| "iso"` | `"long"` | Style of the date; `iso` writes `2020-10-20` in every language |
+| `timeStyle` | same values | — | Style of the time of day; omitted, only the date is rendered |
+| `timeZone` | `string` | `"UTC"` | IANA name of the zone the timestamp is read in |
+
+The result depends on the arguments alone, never on the machine it runs on, so
+pre-rendered markup and the browser agree — a timestamp that changes on hydration
+would tear the markup apart. A timestamp that cannot be read renders as an empty
+string rather than as `Invalid Date`.
+
+---
+
 ### `useContainer( props )`
 
 ```js

package/FRONTMATTER.md

@@ -107,6 +107,20 @@ Menu links and breadcrumbs produced by Scavold automatically use the alias URL.
 with an error naming both conflicting files. Each alias must be unique across the
 entire site.
 
+The same applies when an alias lands on a path another page already owns as its own
+file — a `url: de/kontakt` next to a `pages/de/kontakt.md`. VitePress identifies a
+page by its path flattened into one name, slash becoming underscore, and it uses that
+name for the page's bundle entry, its server module and its client chunk. Two pages
+meeting there overwrite each other's output; the alias does not win, it collides. So
+does a page whose file name spells out a path another page reaches through folders
+(`de_kontakt.md` beside `de/kontakt.md`), and a pair differing only in letter case.
+Scavold checks all of these when it reads the config and names both files. Prefer `-`
+over `_` as the word separator in page names and the class cannot arise.
+
+To move a page and keep its URL, rename the file and declare the old URL as its
+alias — the alias belongs to the page that carries the content, not to a second file
+left behind at the old location.
+
 ---
 
 ## `locale` / `lang`
@@ -260,6 +274,44 @@ in the hierarchy tree — they are only excluded from rendered navigation.
 
 ---
 
+## `aliases`
+
+**Type:** `string | string[]`
+
+Former addresses this page replaces. Declared when a cratly site takes over from an
+existing website: every address a search engine already knows and the new site does not
+answer is a result its owner loses.
+
+```yaml
+---
+aliases:
+  - /kontakt.html
+  - kontakt.php
+---
+```
+
+Values are written as they stood in the browser, with or without a leading slash. A
+fragment is dropped — it never reaches a server. A query string is kept; whether it can
+be matched is up to whoever serves the site.
+
+Scavold collects them and writes `cratly-redirects.json` into the build output: an
+address, where it went, and a status — `301` for an inherited address, `410` for one a
+site declares as gone for good in
+[`retired_urls`](./docs/reference/config.md#retired-urls). Turning that into server
+configuration is the deploy step's job, because cratly does not assume who serves the
+site. Nothing about the file is Scavold-specific: another adapter writes the same format.
+
+**Keeping the address beats redirecting to it.** A permanent redirect passes a ranking on;
+a page that simply answers at the old address never spends it. Where the legacy path can
+be a file, [`url`](#url) is the better tool, and it works on every static server, whether
+or not it can redirect at all.
+
+**Conflict detection:** the build stops when two pages claim the same former address, and
+when a former address is one the new site serves itself — the redirect would win over the
+page, leaving it unreachable while every menu still links to it.
+
+---
+
 ## `redirect`
 
 **Type:** `string | object`

package/composables/hierarchy.ts

@@ -2,6 +2,7 @@ import { useData } from "vitepress";
 import { computed } from "vue";
 import { useL10n } from "@cepharum/vue3-i18n";
 import { hidesFrom } from "../lib/hide.js";
+import { nodePath, pageHref } from "../lib/href.js";
 import type { Scavold } from "../index";
 
 /**
@@ -262,8 +263,7 @@ export function useHierarchy() {
 	 * Converts a hierarchy node path to a root-relative href.
 	 * Prefers node.url (the alias output path) when declared.
 	 */
-	const nodeHref = ( node: Scavold.HierarchyNode ): string =>
-		"/" + ( node.url ?? node.path ).replace( /\.md$/, "" ).replace( /\/index$/, "/" );
+	const nodeHref = ( node: Scavold.HierarchyNode ): string => nodePath( node );
 
 	/**
 	 * The last meaningful segment of a node's source path, used wherever a page
@@ -402,7 +402,7 @@ export function useHierarchy() {
 				if ( translations ) {
 					for ( const [ loc, path ] of Object.entries( translations ) ) {
 						if ( !links.has( loc ) ) {
-							links.set( loc, "/" + String( path ).replace( /\.md$/, "" ).replace( /\/index$/, "/" ) );
+							links.set( loc, pageHref( String( path ) ) );
 						}
 					}
 				}

package/composables/useI18n.js

@@ -1,5 +1,32 @@
 import { useL10n } from "@cepharum/vue3-i18n";
 
+import de from "../l10n/de.json";
+import en from "../l10n/en.json";
+
+/**
+ * Scavold's own translations, keyed by language. They are part of the bundle on
+ * purpose: fetching them at runtime would have to name a URL, and a package that
+ * ships as source inside another site's build cannot know one. Each file is a few
+ * hundred bytes, and a site is free to override any key through its own loader.
+ */
+const TRANSLATIONS = { de, en };
+
+/** Language served to anyone whose locale Scavold does not translate. */
+const FALLBACK_LOCALE = "en";
+
+/**
+ * Picks the translations for a locale, accepting regional tags: `de-AT` is served
+ * the German set rather than falling through to English.
+ *
+ * @param {string} locale locale tag as requested by the l10n context
+ * @returns {object} set of translations
+ */
+export function translationsFor( locale ) {
+	const language = String( locale ?? "" ).toLowerCase().split( /[-_]/ )[0];
+
+	return TRANSLATIONS[language] ?? TRANSLATIONS[FALLBACK_LOCALE];
+}
+
 /**
  * Registers Scavold's built-in translations into the shared l10n context under
  * the `@scavold` namespace. All keys are accessed as `@scavold.<key>`.
@@ -13,9 +40,7 @@ import { useL10n } from "@cepharum/vue3-i18n";
  */
 export function registerScavoldI18n() {
 	useL10n().setNamespaceLoader( "@scavold", locale =>
-		import( `../l10n/${locale}.json` ).catch( () =>
-			import( "../l10n/en.json" )
-		)
+		Promise.resolve( translationsFor( locale ) )
 	);
 }
 

package/composables/usePageList.js

@@ -1,6 +1,8 @@
 import { computed, onMounted, ref } from "vue";
 import { containerProps } from "./useContainer.js";
 import { useHierarchy } from "./hierarchy";
+import { formatTimestamp, TIMESTAMP_STYLES, DEFAULT_TIMEZONE } from "../lib/dateFormat.js";
+import { asNumber, selectionLimit } from "../lib/pageList.js";
 
 /**
  * Props definition for page-list container components. Spread into `defineProps`
@@ -49,9 +51,20 @@ export const pageListProps = {
 	/** Show the publication date of each listed page. */
 	dataDates: { type: String, default: null },
 
-	/** Intl date style for the dates: "short", "medium", "long" or "full". */
+	/** Style of the dates: "short", "medium", "long", "full" — as Intl formats them
+	 * in the page's locale — or "iso" for the locale-independent 2020-10-20. */
 	dataDateStyle: { type: String, default: null },
 
+	/** Style of the time of day, in the same values as `data-date-style`. Left out,
+	 * entries show their date only. */
+	dataTimeStyle: { type: String, default: null },
+
+	/** IANA name of the zone the dates are read in, e.g. "Europe/Berlin". Defaults
+	 * to UTC, the zone dates are normalised into at build time — which is what a
+	 * date without a time of day should be shown in. A list that shows times wants
+	 * the zone the site publishes from instead. */
+	dataTimezone: { type: String, default: null },
+
 	/** Heading level of the entry titles, 2–6. 0 renders a plain list of links. */
 	dataHeadingLevel: { type: String, default: null },
 
@@ -75,21 +88,8 @@ export const pageListProps = {
 /** Orders a page list understands. */
 const SORT_ORDERS = new Set( [ "order", "date", "date-asc", "title" ] );
 
-/** Date styles Intl.DateTimeFormat accepts. */
-const DATE_STYLES = new Set( [ "short", "medium", "long", "full" ] );
-
-/**
- * Reads a container argument that carries a number.
- *
- * @param {string|null} value raw attribute value
- * @param {number} fallback value to use when absent or unusable
- * @returns {number}
- */
-function asNumber( value, fallback ) {
-	const parsed = Number.parseInt( value, 10 );
-
-	return Number.isNaN( parsed ) ? fallback : parsed;
-}
+/** Styles a page list renders its dates in. */
+const DATE_STYLES = new Set( TIMESTAMP_STYLES );
 
 /**
  * Compares two nodes by date, newest first. Pages without a date sort last, in
@@ -130,7 +130,7 @@ export function usePageList( props ) {
 	const deep = computed( () => props.dataDeep != null );
 	const reverse = computed( () => props.dataReverse != null );
 
-	const limit = computed( () => Math.max( 0, asNumber( props.dataLimit, 5 ) ) );
+	const limit = computed( () => selectionLimit( props.dataLimit, props.dataPerPage ) );
 	const offset = computed( () => Math.max( 0, asNumber( props.dataOffset, 0 ) ) );
 
 	const sort = computed( () =>
@@ -141,6 +141,14 @@ export function usePageList( props ) {
 		( DATE_STYLES.has( props.dataDateStyle ) ? props.dataDateStyle : "long" )
 	);
 
+	// No time of day unless the list asks for one: most lists date an entry, they do
+	// not timestamp it.
+	const timeStyle = computed( () =>
+		( DATE_STYLES.has( props.dataTimeStyle ) ? props.dataTimeStyle : null )
+	);
+
+	const timezone = computed( () => props.dataTimezone || DEFAULT_TIMEZONE );
+
 	// A plain list of links carries no headings; teaser cards do, and their level
 	// has to fit the document outline around them, which only the author knows.
 	const headingTag = computed( () => {
@@ -313,29 +321,18 @@ export function usePageList( props ) {
 	const pages = computed( () => Array.from( { length: pageCount.value }, ( _, index ) => index + 1 ) );
 
 	/**
-	 * Formats an ISO timestamp for display in the current page's locale. Dates are
-	 * rendered in UTC, the zone they were normalised into at build time, so a
-	 * date-only front matter value never shifts to its neighbouring day.
+	 * Renders an entry's timestamp in the styles and zone the list was given.
 	 *
 	 * @param {string} isoDate ISO 8601 timestamp
 	 * @returns {string}
 	 */
 	function formatDate( isoDate ) {
-		const date = new Date( isoDate );
-
-		if ( Number.isNaN( date.getTime() ) ) {
-			return "";
-		}
-
-		try {
-			return new Intl.DateTimeFormat( currentLocale.value || undefined, {
-				dateStyle: dateStyle.value,
-				timeZone: "UTC",
-			} ).format( date );
-		} catch {
-			// An unusable locale tag must not take the page down with it.
-			return date.toISOString().slice( 0, 10 );
-		}
+		return formatTimestamp( isoDate, {
+			locale: currentLocale.value || undefined,
+			dateStyle: dateStyle.value,
+			timeStyle: timeStyle.value,
+			timeZone: timezone.value,
+		} );
 	}
 
 	return {