Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.suki.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Release notes hub RSS (Mintlify)

​
Root cause (why the hub had no <item> elements)

The visual hub (updates/release-notes.mdx) uses mode: frame. On staging we verified:
  • …/updates/release-notes/rss.xml had a <channel> but no <item> elements.
  • …/web-sdk/product-updates/changelog/rss.xml and …/updates/mar2026-release-notes/rss.xml did include items.
So Mintlify’s RSS builder does not pull <Update> entries from frame-mode pages, even if those components appear in the MDX source. It is not caused by CSS hiding; moving <Update> blocks outside the layout did not fix it while mode: frame stayed on that file.

​
Fix: separate RSS source page (no frame)

  1. updates/release-notes-rss-feed.mdx
    • rss: true, hidden: true (sidebar), no mode: frame.
    • Holds the combined monthly <Update> list (newest first).
    • Feed URL: /updates/release-notes-rss-feed/rss.xml
  2. updates/release-notes.mdx
    • Keeps mode: frame and the custom timeline UI.
    • No rss: true on this file (so we do not publish an empty feed at …/release-notes/rss.xml).
    • The RSS control links to /updates/release-notes-rss-feed/rss.xml (the combined XML feed). The human-readable source page is /updates/release-notes-rss-feed (hidden from the nav).

​
When you add a new month

  1. Update the timeline on release-notes.mdx as usual (newest month first under the year heading).
  2. Add a matching <Update> at the top of the list in release-notes-rss-feed.mdx (same pattern as existing entries; see April 2026 / updates/apr2026-release-notes).
  3. Add the page path to docs.json under Release Notes (e.g. updates/apr2026-release-notes before older months).
  4. For the monthly MDX page, include rss: true in frontmatter when that month’s page should participate in per-page RSS (see updates/apr2026-release-notes.mdx).

​
How to test

After deploy, open https://<host>/updates/release-notes-rss-feed/rss.xml and confirm <item> entries.

​
RSS <link> and <guid> (Mintlify behavior)

For each <Update>, Mintlify sets <link> and <guid isPermaLink="true"> to: https://<your-domain>/updates/release-notes-rss-feed#<label-as-kebab-case> For example, label="April 2026" becomes #april-2026. This matches how Mintlify documents changelog RSS (same page URL plus anchor), see Changelogs and the Update component docs. The rss={{ title, description }} object only overrides the item title and item description in the feed. It does not change <link> or <guid>. The markdown link inside the <Update> body (for example [View April 2026…](/updates/apr2026-release-notes)) is what appears in <content:encoded>, not in <link> / <guid>. So https://developer.suki.ai/updates/apr2026-release-notes as the permalink for a combined-feed item is not something this repo can set with current Mintlify MDX alone. Options:
  1. Ask Mintlify for a supported field (for example rss.url or rss.link) on <Update> if you need canonical monthly URLs in <item><link>.
  2. Rely on <content:encoded> for the real article URL (consider absolute https://developer.suki.ai/updates/... links so feed readers resolve them reliably).
  3. Per-month RSS instead of (or in addition to) the combined feed: each page like /updates/apr2026-release-notes/rss.xml uses that page as the item base URL when <Update> blocks live on that page (still page#anchor per item, but the page is already the month URL). A single combined feed with canonical month URLs may require a custom-built RSS outside Mintlify unless the product adds the feature.
Last modified on April 21, 2026