WIP: feat: use Sätteri as the MDX processor

astro.config.ts

@@ -1,4 +1,10 @@
 import { defineConfig } from "astro/config";
+import mdx from "@astrojs/mdx";
+import { satteri } from "@astrojs/markdown-satteri";
+import expressiveCode, {
+	type SatteriExpressiveCodeOptions,
+} from "satteri-expressive-code";
+import ecConfig from "./ec.config.mjs";
 import starlight from "@astrojs/starlight";
 import starlightDocSearch from "@astrojs/starlight-docsearch";
 import starlightImageZoom from "starlight-image-zoom";
@@ -253,6 +259,21 @@ export default defineConfig({
 			},
 			serialize: createSitemapLastmodSerializer(),
 		}),
+		mdx({
+			processor: satteri({
+				hastPlugins: [
+					expressiveCode({
+						themes: ecConfig.themes,
+						plugins: ecConfig.plugins,
+						styleOverrides: ecConfig.styleOverrides,
+						frames: ecConfig.frames,
+						shiki: ecConfig.shiki,
+						defaultProps: ecConfig.defaultProps,
+					} as SatteriExpressiveCodeOptions),
+				],
+			}),
+			optimize: true,
+		}),
 		react(),
 		skills(),
 	],

package.json

@@ -45,6 +45,7 @@
 		"@actions/github": "9.1.1",
 		"@apidevtools/swagger-parser": "12.1.0",
 		"@astrojs/check": "0.9.9",
+		"@astrojs/markdown-satteri": "0.2.2",
 		"@astrojs/mdx": "6.0.2",
 		"@astrojs/react": "5.0.7",
 		"@astrojs/rss": "4.0.18",
@@ -143,6 +144,7 @@
 		"remark": "15.0.1",
 		"remark-gfm": "4.0.1",
 		"remark-stringify": "11.0.0",
+		"satteri-expressive-code": "0.1.11",
 		"sharp": "0.34.5",
 		"solarflare-theme": "0.0.6",
 		"space-separated-tokens": "2.0.2",

src/content/changelog/access/2025-07-01-Access-Supports-Customer-Metadata-Boundary.mdx

@@ -1,12 +1,12 @@
 ---
 title: Cloudflare Access Logging supports the Customer Metadata Boundary (CMB)
-description: Access logs will now respect the CMB. 
+description: Access logs will now respect the CMB.
 date: 2025-08-14
 products:
   - access
 ---
 
-Cloudflare Access logs now support the [Customer Metadata Boundary (CMB)](/data-localization/metadata-boundary/). If you have configured the CMB for your account, all Access logging will respect that configuration. 
+Cloudflare Access logs now support the [Customer Metadata Boundary (CMB)](/data-localization/metadata-boundary/). If you have configured the CMB for your account, all Access logging will respect that configuration.
 
 :::note
 For EU CMB customers, the logs will not be stored by Access and will appear as empty in the dashboard. EU CMB customers should utilize [Logpush](/logs/logpush/) to retain their Access logging, if desired.

src/content/changelog/agents/2026-04-15-agentlee-writeops-genui.mdx

@@ -10,7 +10,7 @@ We are excited to announce two major capability upgrades for **Agent Lee**, the
 
 ### Take action with Write Operations
 
-Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask. 
+Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask.
 
 To ensure security and accuracy, every write operation requires **explicit user approval**. Before any change is committed, Agent Lee will present a summary of the proposed action in plain language. No action is taken until you select **Confirm**, and this approval requirement is enforced at the infrastructure level to prevent unauthorized changes.