Enable with paginated = true and max-items = N (e.g., 20) in [preprocessor.rss-feed].

• Collects all .md chapters, sorts by date in frontmatter (newest first; falls back to file modification time).

• RSS:

  • rss.xml gets the N newest items only.
  • Older items go to rss2.xml, rss3.xml, etc. (e.g., with max-items = 4, rss.xml has top 4 by date).
  • Keeps the main feed small/fast for readers; full history available in extra files.

• Atom (when atom = true):

  • atom.xml, atom2.xml, atom3.xml, mirror the RSS pages.

  • Each Atom page includes rel="self" plus rel="next"/rel="prev" links so clients can follow older or newer entries.​

• JSON Feed (when json-feed = true):

  • feed.json, feed2.json, feed3.json, mirror the RSS pages.

  • Each JSON feed page includes a next_url pointing to the next page of older items, as defined in JSON Feed 1.1.

To paginate correctly, ensure most chapters have date: in frontmatter (RFC3339 like 2025-12-02T12:00:00Z or simple 2025-12-02). Without dates, sorting uses file timestamps, which may not reflect publish order.

When switching back to an un-paginated feed, use paginated = false, with max-items = 0, delete any rss2.xml, rss3.xml, atom2.xml, atom3.xml, feed2.json, etc. files in your src/ directory, and run mdbook clean before rebuilding.

<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>privacy-book</title><link>https://mako088.github.io/</link><description>An mdBook-generated site</description><generator>mdbook-rss-feed 1.0.0</generator><item><title>index</title><link>https://mako088.github.io/index.html</link><description><![CDATA[]]></description><guid>https://mako088.github.io/index.html</guid><pubDate>Wed, 3 Dec 2025 00:05:27 +0000</pubDate></item><item><title>Encrypted DNS on Arch</title><link>https://mako088.github.io/arch/enc_dns.html</link><description><![CDATA[<p>❗ NOTE: There are many other ways for someone monitoring your traffic to see
what domain you looked up via DNS that it’s effectiveness is questionable
without also using Tor or a VPN. Encrypted DNS will not help you hide any of
your browsing activity.</p><pre><code class="language-bash">sudo pacman -S dnscrypt-proxy
</code></pre>
<blockquote>

Truncated example for brevity

<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>privacy-book</title><id>https://mako088.github.io/atom.xml</id><updated>1970-01-01T00:00:00+00:00</updated><link href="https://mako088.github.io/atom.xml" rel="self"/><subtitle>An mdBook-generated site</subtitle><entry><title>index</title><id>https://mako088.github.io/index.html</id><updated>2025-12-03T00:05:27+00:00</updated><link href="https://mako088.github.io/index.html" rel="alternate"/><content type="html"></content></entry><entry><title>Encrypted DNS on Arch</title><id>https://mako088.github.io/arch/enc_dns.html</id><updated>2025-11-28T00:00:00+00:00</updated><link href="https://mako088.github.io/arch/enc_dns.html" rel="alternate"/><content type="html">&lt;p&gt;❗ NOTE: There are many other ways for someone monitoring your traffic to see
what domain you looked up via DNS that it’s effectiveness is questionable
without also using Tor or a VPN. Encrypted DNS will not help you hide any of
your browsing activity.&lt;/p&gt;&lt;pre&gt;&lt;code class=&quot;language-bash&quot;&gt;sudo pacman -S dnscrypt-proxy
&lt;/code&gt;&lt;/pre&gt;
&lt;blockquote&gt;
&lt;p&gt;NOTE: udp is required for dnscrypt protocol, keep this in mind when

Truncated example for brevity

{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "privacy-book",
  "home_page_url": "https://mako088.github.io/",
  "feed_url": "https://mako088.github.io/feed.json",
  "description": "An mdBook-generated site",
  "items": [
    {
      "id": "https://mako088.github.io/index.html",
      "url": "https://mako088.github.io/index.html",
      "title": "index",
      "content_html": "",
      "date_published": "2025-12-03T00:05:27+00:00"
    },
    {
      "id": "https://mako088.github.io/arch/enc_dns.html",
      "url": "https://mako088.github.io/arch/enc_dns.html",
      "title": "Encrypted DNS on Arch",
      "content_html": "<p>❗ NOTE: There are many other ways for someone monitoring your traffic to see\nwhat domain you looked up via DNS that it’s effectiveness is questionable\nwithout also using Tor or a VPN. Encrypted DNS will not help you hide any of\nyour browsing activity.</p><pre><code class=\"language-bash\">sudo pacman -S dnscrypt-proxy\n</code></pre>\n<blockquote>\n<p>NOTE: udp is required for dnscrypt protocol, keep this in mind when\nconfiguring your servers if your output chain is a default drop.</p><p><a href=\"https://wiki.archlinux.org/title/Dnscrypt-proxy\">Arch Wiki dnscrypt-proxy</a></p>",
      "date_published": "2025-11-28T00:00:00+00:00",
      "author": {
        "name": "saylesss88"
      }
    },

Truncated example shown for brevity

• If you use preprocessors like mdbook-content-loader, and mdbook-content-collections to inject intro snippets into your chapters, those snippets are treated just like normal Markdown.

• Because mdbook-rss-feed renders the final chapter Markdown and then finds the first real <p>…</p> blocks, injected paragraphs at the top of the chapter will become the preview text automatically.

• This allows you to maintain small, reusable intro snippets (or per-section summaries) and have them appear in both the book and the RSS feed without any extra configuration.

• mdbook-content-loader can enforce typed frontmatter and custom sorting (for example, by a typed date field or other metadata).​

mdbook-rss-feed reads the resulting Markdown files and sorts feed items by the date in frontmatter (falling back to file modification time when missing).

• Combined, you get:

  • Strongly-typed frontmatter (less chance of bad dates or missing fields).

  • Consistent ordering between your book’s index pages and the RSS feed.

  • Cleaner previews when your loader injects well-structured intro snippets at the top of each chapter.

Your book.toml can accept additional css and js:

additional-css = [ "theme/rss-button.css" ]
additional-js = [ "theme/rss-buttons.js" ]

In your books theme/ directory, place these two files:

1. theme/rss-button.css

/* Simple RSS header button */
.rss-btn {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 32px;
  height: 32px;
  margin-left: 8px;
  color: var(--sidebar-fg, #333);
  opacity: 0.7;
  transition: opacity 0.2s;
}

.rss-btn:hover {
  opacity: 1;
  color: var(--sidebar-fg, #333);
}

/* Optional: orange hover like classic RSS */
.rss-btn:hover svg {
  stroke: #f26522;
}

2. theme/rss-button.js

document.addEventListener("DOMContentLoaded", () => {
  const menuBar =
    document.querySelector(".menu-bar .right-buttons") ||
    document.querySelector(".menu-bar");
  if (!menuBar) return;

  const rssLink = document.createElement("a");
  rssLink.href = "https://your-user.github.io/rss.xml"; // set to your feed URL
  rssLink.target = "_blank";
  rssLink.rel = "noopener";
  rssLink.title = "Subscribe to RSS feed";
  rssLink.className = "rss-btn";

  rssLink.innerHTML = `
    <svg xmlns="http://www.w3.org/2000/svg"
         width="16" height="16" viewBox="0 0 24 24"
         fill="none" stroke="currentColor" stroke-width="2"
         stroke-linecap="round" stroke-linejoin="round"
         style="margin-bottom:-3px">
      <circle cx="6" cy="18" r="3"></circle>
      <path d="M6 6c6.627 0 12 5.373 12 12"></path>
      <path d="M6 12c3.314 0 6 2.686 6 6"></path>
    </svg>
  `;

  const printButton = menuBar.querySelector(".print-btn, #print-button");
  if (printButton && printButton.parentNode === menuBar) {
    printButton.before(rssLink);
  } else {
    menuBar.appendChild(rssLink);
  }
});

Now you should have a small logo pinned to the top right of your book that leads to https://your-site/rss.xml