fix(website): render GFM tables in .mdx pages

website/astro.config.mjs

@@ -8,6 +8,7 @@ import starlightOpenAPI, { openAPISidebarGroups } from 'starlight-openapi';
 import { readFileSync } from 'node:fs';
 import { join } from 'node:path';
 import { execSync } from 'node:child_process';
+import remarkGfm from 'remark-gfm';
 import remarkBasePath from './src/plugins/remark-base-path.mjs';
 import remarkHttpSnippets from './src/plugins/remark-http-snippets.mjs';
 
@@ -56,7 +57,13 @@ export default defineConfig({
 	output: 'static',
 	server: { port: docPort },
 	markdown: {
-		remarkPlugins: [[remarkBasePath, { base }], remarkHttpSnippets],
+		// remarkGfm is listed explicitly because Astro applies its built-in GFM
+		// support to .md only. MDX inherits `remarkPlugins` but not that built-in,
+		// so without this every table in a .mdx page renders as literal pipe
+		// characters. Splitting content between the two extensions is not an
+		// option here: the HTTP snippet plugin below emits JSX, which only .mdx
+		// renders, and several guides need both tables and snippets.
+		remarkPlugins: [remarkGfm, [remarkBasePath, { base }], remarkHttpSnippets],
 	},
 	integrations: [
 		starlight({

website/package.json

@@ -20,8 +20,9 @@
   "devDependencies": {
     "acorn": "^8.16.0",
     "httpsnippet-lite": "^3.0.5",
+    "remark-gfm": "^4.0.1",
     "starlight-openapi": "^0.25.1",
     "unist-util-visit": "^5.1.0",
     "worktree-env": "^0.1.0"
   }
-}
+}