Fix frontmatter field name for Quartz date display #158

Merged

eblume merged 1 commit from fix-frontmatter-field-name into main

2026-02-11 16:45:13 -08:00

eblume commented

2026-02-11 16:43:55 -08:00

Owner

Summary

Rename date-modified -> modified in all 80 docs and the docs-check-frontmatter task

Quartz's CreatedModifiedDate plugin recognizes modified, lastmod, updated, and last-modified — but not date-modified. The wrong field name caused Quartz to ignore frontmatter dates entirely and fall through to filesystem timestamps (UTC inside Dagger), showing Feb 12 on pages built late on Feb 11 PST.

Test plan

mise run docs-check-frontmatter passes
Kick off docs release after merge — verify rendered dates match frontmatter values

## Summary - Rename `date-modified` -> `modified` in all 80 docs and the `docs-check-frontmatter` task Quartz's `CreatedModifiedDate` plugin recognizes `modified`, `lastmod`, `updated`, and `last-modified` — but not `date-modified`. The wrong field name caused Quartz to ignore frontmatter dates entirely and fall through to filesystem timestamps (UTC inside Dagger), showing Feb 12 on pages built late on Feb 11 PST. ## Test plan - [x] `mise run docs-check-frontmatter` passes - [ ] Kick off docs release after merge — verify rendered dates match frontmatter values

eblume added 1 commit

2026-02-11 16:43:55 -08:00

Fix frontmatter field name: date-modified -> modified ce59e9951b

Quartz's CreatedModifiedDate plugin recognizes `modified`, `lastmod`,
`updated`, and `last-modified` — but not `date-modified`. The wrong
field name caused Quartz to fall through to filesystem timestamps
(UTC in Dagger), showing incorrect dates on the rendered site.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>