Merge branch 'main' into chore/docsdev-60-ilf-developers-dep-upgrade

Author: Infi-Knight

.github/workflows/sync-mdx-to-strapi.yml

@@ -25,6 +25,8 @@ Inside this project, you'll see the following folders and files:
 
 Starlight looks for `.md` or `.mdx` files in the `src/content/docs/` directory. Each file is exposed as a route based on its file name.
 
+RFC pages under `src/content/docs/rfcs/` are a small exception. Those route files wrap the upstream markdown from the `interledger/rfcs` repository via `src/components/Rfc.astro`. Internal RFC-to-RFC links are rewritten in `src/utils/rewriteRfcLinks.ts` so the rendered docs point at local Starlight routes instead of upstream `.md` source paths.
+
 Static assets, like favicons or images, can be placed in the `public/` directory. When referencing these assets in your markdown, you do not have to include `public/` in the file path, so an image would have a path like:
 
 ```md

README.md

@@ -4,6 +4,7 @@ import starlightLinksValidator from 'starlight-links-validator'
 import starlightFullViewMode from 'starlight-fullview-mode'
 
 import mdx from '@astrojs/mdx'
+import { PUBLISHED_RFC_SIDEBAR_ITEMS } from './src/data/rfcs.ts'
 
 // https://astro.build/config
 export default defineConfig({
@@ -76,50 +77,7 @@ export default defineConfig({
         {
           label: 'Specifications',
           items: [
-            {
-              label: 'Interledger Protocol V4 (ILPv4)',
-              link: '/rfcs/interledger-protocol'
-            },
-            {
-              label: 'Interledger Architecture',
-              link: '/rfcs/interledger-architecture'
-            },
-            {
-              label: 'Interledger Addresses',
-              link: '/rfcs/ilp-addresses'
-            },
-            {
-              label: 'STREAM Protocol',
-              link: '/rfcs/stream-protocol'
-            },
-            {
-              label: 'Simple Payment Setup Protocol (SPSP)',
-              link: '/rfcs/simple-payment-setup-protocol'
-            },
-            {
-              label: 'Peering, Clearing and Settling',
-              link: '/rfcs/peering-clearing-settling'
-            },
-            {
-              label: 'Settlement Engines',
-              link: '/rfcs/settlement-engines'
-            },
-            {
-              label: 'ILP Over HTTP',
-              link: '/rfcs/ilp-over-http'
-            },
-            {
-              label: 'Bilateral Transfer Protocol',
-              link: '/rfcs/bilateral-transfer-protocol'
-            },
-            {
-              label: 'STREAM Receipts',
-              link: '/rfcs/stream-receipts'
-            },
-            {
-              label: 'Hashed-Timelock Agreements',
-              link: '/rfcs/hashed-timelock-agreements'
-            },
+            ...PUBLISHED_RFC_SIDEBAR_ITEMS,
             {
               label: 'Payment Pointers',
               link: 'https://paymentpointers.org',

astro.config.mjs

@@ -1,23 +1,38 @@
 ---
-import { parse } from 'node-html-parser'
 import showdown from 'showdown'
+import { rewriteRfcLinks } from '../utils/rewriteRfcLinks'
 
-const { source } = Astro.props
+interface Props {
+  source: string
+  docsBasePath?: string
+}
+
+const { source, docsBasePath = '/developers' } = Astro.props
 
-const getApiData = async () => {
-  const data = await fetch(source).then((response) => response.text())
-  const frontMatterPos = data.indexOf('---', 1) + 3
-  const specBody = data.slice(frontMatterPos)
-  return specBody
+const response = await fetch(source)
+
+if (!response.ok) {
+  throw new Error(
+    `Failed to fetch RFC markdown from ${source}: ${response.status} ${response.statusText}`
+  )
 }
 
-const specBody = await getApiData()
+const markdown = await response.text()
+
+const frontMatterPos = markdown.indexOf('---', 1) + 3
+const specBody = markdown.slice(frontMatterPos)
+
 const converter = new showdown.Converter({
   tables: true,
   ghCompatibleHeaderId: true
 })
-const html = converter.makeHtml(specBody)
-const output = parse(html)
+
+const renderedHtml = converter.makeHtml(specBody)
+
+const html = rewriteRfcLinks(renderedHtml, {
+  sourceUrl: source,
+  docsBasePath
+})
 ---
 
-{output}
+<div set:html={html} />

public/img/blog/2026-03-26/responsibilites.png

@@ -102,19 +102,34 @@ import FoundationLogo from '../logos/FoundationLogo.astro'
           <ul class="menu--level-2">
             <li class="menu-item menu-item--level-2">
               <a
-                href="/financial-services"
+                href="/grant/financial-services"
                 data-umami-event="Site Nav - Financial Services"
                 >Digital Financial Services</a
               >
             </li>
             <li class="menu-item menu-item--level-2">
-              <a href="/education" data-umami-event="Site Nav - Education"
+              <a href="/grant/education" data-umami-event="Site Nav - Education"
                 >NextGen Higher Education</a
               >
             </li>
             <li class="menu-item menu-item--level-2">
-              <a href="/ambassadors" data-umami-event="Site Nav - Ambassadors"
-                >Ambassadors</a
+              <a
+                href="/grant/ambassadors"
+                data-umami-event="Site Nav - Ambassadors">Fellowship Program</a
+              >
+            </li>
+            <li class="menu-item menu-item--level-2">
+              <a
+                href="/grant/grant-web"
+                data-umami-event="Site Nav - Grant for the Web"
+                >Grant for the Web</a
+              >
+            </li>
+            <li class="menu-item menu-item--level-2">
+              <a
+                href="/grant/open-payments-sdk"
+                data-umami-event="Site Nav - Open Payments SDK"
+                >Open Payments SDK</a
               >
             </li>
           </ul>

public/img/blog/2026-03-26/sequence-diagram.png

@@ -123,4 +123,4 @@ The incoming payment serves as a dedicated "bucket" into which we can stream mic
 
 ## Sending money
 
-This article is already long enough, so let's dive into the fun part — actually executing a payment — in the next article!
+This article is already long enough, so let's dive into the fun part — actually executing a payment — in the [next article](https://interledger.org/developers/blog/web-monetization-open-payments-part-3-sending-money)!