What changed in Scriptor, scriptor-markdown-pages, this documentation site, and the bundled themes. One entry per release or notable milestone; entries don't get edited after they go up (corrections land as new entries).
Subscribe
The Atom feed lives at
/news/feed.xml. It carries the latest 20
entries with title, link, ISO 8601 updated timestamp, and a
short summary. Most modern readers understand Atom 1.0; the feed
also works with anything that speaks RSS 2.0 via a translation
layer.
The feed is generated on every request from the markdown files
under content/news/: no build step, no cache. Add an entry,
push, and the next subscriber poll sees it.
How each entry is laid out
Every news entry follows the same shape:
- One-paragraph lead. What shipped, who it's for, why it matters. Read this and you can decide whether to click into the rest.
- What changed. A bullet list of the user-facing diffs: commands you'd type differently, features you can now use, surfaces that moved.
- Upgrade path. If the entry covers a release, the steps to get from the previous version to this one. Skipped when the entry is purely informational (e.g. "documentation X is now complete").
- Links. GitHub release, relevant tutorial, relevant API reference page. The same five-link cap as Extensions entries.
Entries
The track opened in May 2026 with three launch milestones; newer entries land on top:
| Date | Entry |
|---|---|
| 2026-06-01 | scriptor-sitemap v0.1.0 |
| 2026-05-31 | scriptor-markdown-feed v0.1.0 |
| 2026-05-30 | scriptor-markdown-containers v0.1.0 |
| 2026-05-25 | Developer Guide is content-complete |
| 2026-05-25 | User Guide is content-complete |
| 2026-05-22 | scriptor-markdown-pages v0.1.7 |
Entries are listed reverse-chronologically by the date:
frontmatter; ties break on title.
What's not news
Three things are deliberately out of scope:
- Tutorials, recipes, and reference. Those live in the Developer Guide and User Guide. News links into them but doesn't replace them.
- Daily commit log. This is curated. A typo fix in a doc page doesn't earn a news entry; a new chapter does. Roughly one entry per merged feature or tagged release.
- External Scriptor sightings. Blog posts, talks, or third-party tutorials about Scriptor are great but live on the GitHub Discussions side, not here.
Where to go next
If you got here from a feed reader, the latest entry is at the top of the catalog above.
If you want to be notified about the next entry, subscribe to /news/feed.xml in your reader of choice.
If you're looking for what shipped before the launch entries, the Scriptor GitHub releases page has the full history with per-tag changelogs.
The feed is served by the
scriptor-markdown-feed plugin, activated from one
guard line in the info-theme's _ext.php
(Feed::handle($config)). It runs ahead of the theme: when the
request path matches /news/feed.xml it scans content/news/ for
.md files, parses the frontmatter, emits Atom, and returns. The
pattern is the
RSS / Atom feed from a page tree
cookbook recipe adapted to the markdown directory instead of
the DB-backed PageRepository.
