Repository navigation
Page data: categories, an authored updated date, scheduled pages, shell highlighting - #62
Merged
Merged
Conversation
…er dates a page page.updated, JSON-LD dateModified, article:modified_time and the sitemap's lastmod come from the page's own updated (the sitemap falls back to its own date). page.modified is retired: a layout that declares it is told to declare page.updated instead.
A page whose own date is after the build's day (UTC) stays out of pd build, as a draft does, with every page under a scheduled folder's index.md; the report names each and the day it is first built. pd dev shows it, listed with scheduled: true and a note.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The page data later 0.5.0 steps filter and sort by, plus shell highlighting.
Categories
storefront.categoriesdeclares them: key (a URL segment),label, optionaldescription, andaliases(old keys kept after a rename). An alias that is a key, or that two categories claim, is a config problem.categories:. An undeclared value fails the page with a "did you mean"; an old key builds as the new category, with a warning naming the page and line.page.categories({ key, label, description }, in the page's order); listing entries carry them;site.categoriesis every declared category whenpartials/baselists it.updated, and git's last commitupdated: YYYY-MM-DD, a real date, not beforedate.page.updated, JSON-LDdateModified(WebPage and Article),article:modified_time, and the sitemap'slastmod(which falls back to the page's owndate).page.modifiedis retired: a layout declaring it fails with a message to declarepage.updated.page.createdis unchanged.Scheduled pages
dateis after the build's day (UTC, fixed once per build) stays out ofpd build, as a draft does; a scheduled folderindex.mdholds back its pages until the later date.pd devshows it, withscheduled: trueon its listing entry and a note. The build report:scheduled: N held back (x.md until 2026-12-01).Shell highlighting
bash,sh,shell,zsh, andconsole/shell-sessionfor a prompt with its output, in docs, storefront pages and placed content.textstays plain.Tests
New specs:
shell-highlight,storefront-categories,storefront-updated,storefront-scheduled, config validation, and the storefront bench'scategoriesE2E plus a scheduled case incollections. Tests that pinned git's last commit now assert the new rule. Two build specs' fixed clock moved past the bench's dates. The workbench golden snapshot is unchanged.The CHANGELOG has an
Unreleasedsection with the visible changes.