Skip to content

Add source:markdown to RSS feeds#16

Merged
simonbc merged 1 commit into
mainfrom
m6-source-markdown
May 15, 2026
Merged

Add source:markdown to RSS feeds#16
simonbc merged 1 commit into
mainfrom
m6-source-markdown

Conversation

@simonbc
Copy link
Copy Markdown
Owner

@simonbc simonbc commented May 15, 2026

Summary

  • Add the source:markdown RSS extension (Manton, 2025-11-11; namespace https://source.scripting.com/) to both /<page>?m=history_rss and /site/changes.rss.
  • Each <item> now carries the page's raw markdown source alongside the rendered HTML in <description>.
  • JSON Feed gains the matching content_text field populated from the same markdown source.
  • The previous <description> content (the diff summary) is replaced with the rendered HTML of the revision content — that's what feed readers want to render anyway, and the diff summary is still visible in the HTML changes/history views.

Test plan

  • uv run pytest (331 passing)
  • uv run ruff check . && uv run ruff format --check jottit tests
  • uv run pyright

🤖 Generated with Claude Code

Implements the source:markdown RSS extension Manton documented at
https://www.manton.org/2025/11/11/markdown-in-rss.html (namespace
https://source.scripting.com/). Each <item> now carries the page's
raw markdown source alongside the rendered HTML in <description>,
so a reader that knows how can prefer the markdown.

This also reshapes the feeds: <description> previously held the
diff-summary string (e.g. "Added X to Y"); it now holds the rendered
HTML of the revision's content, which is what feed readers actually
want to render. JSON Feed gains the matching `content_text` field
populated from the same raw markdown source.

Wikilinks inside the rendered HTML are resolved against the absolute
site root so they survive in external readers.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@simonbc simonbc merged commit 3250f01 into main May 15, 2026
1 check passed
@simonbc simonbc deleted the m6-source-markdown branch May 15, 2026 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant