A feed that sends <source:markdown> beside its HTML (Scripting News) has its Markdown kept in entries.markdown, added to existing databases by an ALTER. A stored item gets it when a scan finds it told differently, the Markdown counting as a change, the way corrections arrive (#141). The API sends it as written and made HTML, cleaned by ammonia like the description. The item's page has a choice between its meta line and its buttons: HTML, Markdown or Markdown source, remembered in the browser. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
9 lines
502 B
XML
9 lines
502 B
XML
<?xml version="1.0"?>
|
|
<rss version="2.0" xmlns:source="https://source.scripting.com/">
|
|
<channel><title>Markdown Blog</title><link>http://127.0.0.1:8792/</link><description>HTML and Markdown both, as Scripting News sends.</description>
|
|
<item><title>Both Ways</title><guid>md-1</guid>
|
|
<pubDate>Mon, 01 Sep 2026 10:00:00 +0000</pubDate>
|
|
<description><p>The <b>HTML</b> copy.</p></description>
|
|
<source:markdown>The **Markdown** copy.</source:markdown></item>
|
|
</channel></rss>
|