[{"data":1,"prerenderedAt":1520},["ShallowReactive",2],{"page:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content":3,"all-docs-nav":979},{"id":4,"title":5,"body":6,"breadcrumb":956,"dateModified":966,"datePublished":966,"description":967,"extension":105,"faq":968,"meta":973,"navigation":130,"path":974,"seo":975,"slug":12,"stem":976,"type":977,"__hash__":978},"content\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content\u002Findex.md","MDX vs Markdoc for Docs Content",{"type":7,"value":8,"toc":939},"minimark",[9,13,31,40,45,66,70,75,100,212,388,392,395,481,492,601,605,612,660,729,737,741,753,756,767,770,774,777,794,810,814,852,856,859,863,868,871,875,878,882,885,889,892,896,935],[10,11,5],"h1",{"id":12},"mdx-vs-markdoc-for-docs-content",[14,15,16,17,21,22,25,26,30],"p",{},"Plain Markdown runs out quickly in documentation. Writers need tabs for per-language samples, callouts, cards, embedded diagrams and version badges, and every docs framework offers a way to put components into prose. The two serious options are ",[18,19,20],"strong",{},"MDX",", which turns Markdown into JavaScript and lets you write JSX inline, and ",[18,23,24],{},"Markdoc",", Stripe's format, which adds a small tag syntax (",[27,28,29],"code",{},"{% tabs %}",") that is parsed, validated against a schema and rendered — but never executed.",[14,32,33,34,39],{},"The choice shapes three things for years: how often contributors break the build, what a malicious or careless pull request can do, and how long every build takes. This guide compares them on a real docs corpus in Astro and Starlight, where both are first-class. It belongs to ",[35,36,38],"a",{"href":37},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002F","Docs Frameworks: Docusaurus, Starlight and VitePress",".",[41,42,44],"h2",{"id":43},"prerequisites","Prerequisites",[46,47,48,60,63],"ul",{},[49,50,51,52,55,56,59],"li",{},"An Astro or Starlight project (",[27,53,54],{},"@astrojs\u002Fmdx"," and ",[27,57,58],{},"@astrojs\u002Fmarkdoc"," integrations installed), or a Docusaurus site if you are evaluating MDX alone.",[49,61,62],{},"A list of the components your writers actually use — usually fewer than ten.",[49,64,65],{},"Build timing in CI, so you can measure the difference on your own corpus rather than trusting ours.",[41,67,69],{"id":68},"how-each-format-works","How Each Format Works",[14,71,72,74],{},[18,73,20],{}," compiles each file through remark and rehype into a JavaScript module. Components are imported at the top of the file and used as JSX. Curly braces evaluate JavaScript expressions. The result is enormously flexible — a page can compute a table from imported data — and any syntax error in the JSX is a compile error for the whole page.",[14,76,77,79,80,83,84,87,88,91,92,95,96,99],{},[18,78,24],{}," parses each file into an abstract syntax tree, validates tags and attributes against a schema you define (",[27,81,82],{},"tabs"," requires ",[27,85,86],{},"items",", ",[27,89,90],{},"callout"," accepts ",[27,93,94],{},"type"," of ",[27,97,98],{},"note|warning","), transforms the tree, then renders it with your components. Tags cannot contain expressions beyond variables and functions you explicitly register, so content is data, not code.",[101,102,107],"pre",{"className":103,"code":104,"language":105,"meta":106,"style":106},"language-md shiki shiki-themes github-light github-dark","\u003C!-- MDX -->\nimport { Tabs, TabItem } from '@astrojs\u002Fstarlight\u002Fcomponents';\n\n\u003CTabs>\n  \u003CTabItem label=\"npm\">`npm i acme`\u003C\u002FTabItem>\n  \u003CTabItem label=\"pnpm\">`pnpm add acme`\u003C\u002FTabItem>\n\u003C\u002FTabs>\n\n\u003C!-- Markdoc -->\n{% tabs %}\n{% tabitem label=\"npm\" %}`npm i acme`{% \u002Ftabitem %}\n{% tabitem label=\"pnpm\" %}`pnpm add acme`{% \u002Ftabitem %}\n{% \u002Ftabs %}\n","md","",[27,108,109,118,125,132,138,151,162,168,173,179,185,196,206],{"__ignoreMap":106},[110,111,114],"span",{"class":112,"line":113},"line",1,[110,115,117],{"class":116},"sJ8bj","\u003C!-- MDX -->\n",[110,119,121],{"class":112,"line":120},2,[110,122,124],{"class":123},"sVt8B","import { Tabs, TabItem } from '@astrojs\u002Fstarlight\u002Fcomponents';\n",[110,126,128],{"class":112,"line":127},3,[110,129,131],{"emptyLinePlaceholder":130},true,"\n",[110,133,135],{"class":112,"line":134},4,[110,136,137],{"class":123},"\u003CTabs>\n",[110,139,141,144,148],{"class":112,"line":140},5,[110,142,143],{"class":123},"  \u003CTabItem label=\"npm\">",[110,145,147],{"class":146},"sj4cs","`npm i acme`",[110,149,150],{"class":123},"\u003C\u002FTabItem>\n",[110,152,154,157,160],{"class":112,"line":153},6,[110,155,156],{"class":123},"  \u003CTabItem label=\"pnpm\">",[110,158,159],{"class":146},"`pnpm add acme`",[110,161,150],{"class":123},[110,163,165],{"class":112,"line":164},7,[110,166,167],{"class":123},"\u003C\u002FTabs>\n",[110,169,171],{"class":112,"line":170},8,[110,172,131],{"emptyLinePlaceholder":130},[110,174,176],{"class":112,"line":175},9,[110,177,178],{"class":116},"\u003C!-- Markdoc -->\n",[110,180,182],{"class":112,"line":181},10,[110,183,184],{"class":123},"{% tabs %}\n",[110,186,188,191,193],{"class":112,"line":187},11,[110,189,190],{"class":123},"{% tabitem label=\"npm\" %}",[110,192,147],{"class":146},[110,194,195],{"class":123},"{% \u002Ftabitem %}\n",[110,197,199,202,204],{"class":112,"line":198},12,[110,200,201],{"class":123},"{% tabitem label=\"pnpm\" %}",[110,203,159],{"class":146},[110,205,195],{"class":123},[110,207,209],{"class":112,"line":208},13,[110,210,211],{"class":123},"{% \u002Ftabs %}\n",[213,214,215,384],"figure",{},[216,217,224,225,224,229,224,233,224,240,224,370],"svg",{"viewBox":218,"role":219,"ariaLabelledBy":220,"xmlns":223},"0 0 760 290","img",[221,222],"mxm-pipe-title","mxm-pipe-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[226,227,228],"title",{"id":221},"Compile pipelines of MDX and Markdoc",[230,231,232],"desc",{"id":222},"Two pipelines. MDX goes from source to a remark and rehype tree to a compiled JavaScript module that is executed to produce HTML, so imports and expressions run. Markdoc goes from source to a parsed tree, is validated against a schema that reports errors with line numbers, is transformed and then rendered to HTML without executing content.",[234,235],"rect",{"x":236,"y":236,"width":237,"height":238,"fill":239},"0","760","290","#ffffff",[241,242,244,245,244,253,244,258,244,268,244,274,244,278,244,282,244,289,244,293,244,297,244,301,244,304,244,307,244,311,244,313,244,316,244,321,244,324,244,326,244,329,244,355,244,361,244,366,224],"g",{"style":243},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[246,247,252],"text",{"x":248,"y":249,"fill":250,"style":251},"380","28","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Content as code vs content as data",[246,254,20],{"x":255,"y":256,"fill":250,"style":257},"30","92","font-weight:700",[234,259],{"x":260,"y":261,"width":262,"height":263,"rx":264,"fill":265,"stroke":266,"style":267},"100","70","120","40","8","#f8fafc","#d9e2ef","stroke-width:1.5px",[246,269,273],{"x":270,"y":271,"fill":250,"style":272},"160","95","text-anchor:middle",".mdx source",[234,275],{"x":276,"y":261,"width":277,"height":263,"rx":264,"fill":265,"stroke":266,"style":267},"250","130",[246,279,281],{"x":280,"y":271,"fill":250,"style":272},"315","remark \u002F rehype",[234,283],{"x":284,"y":261,"width":285,"height":263,"rx":264,"fill":286,"opacity":287,"stroke":288,"style":267},"410","140","#ff595e","0.14","#d83b41",[246,290,292],{"x":291,"y":271,"fill":250,"style":272},"480","JS module (runs)",[234,294],{"x":295,"y":261,"width":296,"height":263,"rx":264,"fill":265,"stroke":266,"style":267},"580","150",[246,298,300],{"x":299,"y":271,"fill":250,"style":272},"655","HTML",[246,302,24],{"x":255,"y":303,"fill":250,"style":257},"192",[234,305],{"x":260,"y":306,"width":262,"height":263,"rx":264,"fill":265,"stroke":266,"style":267},"170",[246,308,310],{"x":270,"y":309,"fill":250,"style":272},"195",".mdoc source",[234,312],{"x":276,"y":306,"width":277,"height":263,"rx":264,"fill":265,"stroke":266,"style":267},[246,314,315],{"x":280,"y":309,"fill":250,"style":272},"parse → AST",[234,317],{"x":284,"y":306,"width":285,"height":263,"rx":264,"fill":318,"opacity":319,"stroke":320,"style":267},"#8ac926","0.18","#5a8a16",[246,322,323],{"x":291,"y":309,"fill":250,"style":272},"validate schema",[234,325],{"x":295,"y":306,"width":296,"height":263,"rx":264,"fill":265,"stroke":266,"style":267},[246,327,328],{"x":299,"y":309,"fill":250,"style":272},"render → HTML",[241,330,334,335,334,340,334,343,334,346,334,349,334,352,244],{"stroke":331,"fill":332,"style":333},"#556071","none","stroke-width:2px","\n      ",[336,337],"path",{"d":338,"style":339},"M222 90 L246 90","marker-end:url(#mxm-arrow)",[336,341],{"d":342,"style":339},"M382 90 L406 90",[336,344],{"d":345,"style":339},"M552 90 L576 90",[336,347],{"d":348,"style":339},"M222 190 L246 190",[336,350],{"d":351,"style":339},"M382 190 L406 190",[336,353],{"d":354,"style":339},"M552 190 L576 190",[246,356,360],{"x":291,"y":357,"fill":358,"style":359},"132","#b32b30","font-size:11px;text-anchor:middle","imports + expressions execute",[246,362,365],{"x":291,"y":363,"fill":364,"style":359},"232","#3f6410","errors name file, line and tag",[246,367,369],{"x":248,"y":368,"fill":331,"style":359},"272","Both end as static HTML; they differ in what the content is allowed to do on the way",[371,372,244,373,224],"defs",{},[374,375,334,381,244],"marker",{"id":376,"viewBox":377,"refX":264,"refY":378,"markerWidth":379,"markerHeight":379,"orient":380},"mxm-arrow","0 0 10 10","5","7","auto-start-reverse",[336,382],{"d":383,"fill":331},"M0 0 L10 5 L0 10 z",[385,386,387],"figcaption",{},"MDX's execution step is where its flexibility and its failure modes both come from.",[41,389,391],{"id":390},"authoring-errors-in-practice","Authoring Errors in Practice",[14,393,394],{},"The format decision is mostly felt through error messages. Over one quarter, a 1,200-page docs repository with 38 regular contributors logged every failed build:",[396,397,398,414],"table",{},[399,400,401],"thead",{},[402,403,404,408,411],"tr",{},[405,406,407],"th",{},"Failure cause",[405,409,410],{},"MDX pages (320)",[405,412,413],{},"Markdoc pages (880)",[415,416,417,437,448,459,470],"tbody",{},[402,418,419,431,434],{},[420,421,422,423,426,427,430],"td",{},"Unescaped ",[27,424,425],{},"\u003C"," or ",[27,428,429],{},"{"," in prose",[420,432,433],{},"27",[420,435,436],{},"0 (not special in Markdoc)",[402,438,439,442,445],{},[420,440,441],{},"Unclosed or mismatched component tag",[420,443,444],{},"11",[420,446,447],{},"6",[402,449,450,453,456],{},[420,451,452],{},"Unknown component or attribute",[420,454,455],{},"4 (runtime error)",[420,457,458],{},"9 (caught by schema)",[402,460,461,464,467],{},[420,462,463],{},"Wrong attribute value",[420,465,466],{},"0 detected",[420,468,469],{},"5 (caught by schema)",[402,471,472,475,478],{},[420,473,474],{},"Failed builds per 100 edits",[420,476,477],{},"4.1",[420,479,480],{},"0.9",[14,482,483,484,487,488,491],{},"Two patterns stand out. First, most MDX failures had nothing to do with components: a writer typed ",[27,485,486],{},"latency \u003C 200ms"," or pasted JSON outside a code fence, and the JSX parser rejected it. Second, Markdoc's schema caught mistakes MDX let through silently — an attribute typo like ",[27,489,490],{},"lable=\"npm\""," renders an unlabeled tab in MDX but fails validation in Markdoc with a message naming the file, line and attribute.",[213,493,494,598],{},[216,495,224,500,224,503,224,506,224,509],{"viewBox":496,"role":219,"ariaLabelledBy":497,"xmlns":223},"0 0 760 260",[498,499],"mxm-err-title","mxm-err-desc",[226,501,502],{"id":498},"Failed builds per 100 edits by format",[230,504,505],{"id":499},"Stacked bars. MDX pages failed 4.1 times per 100 edits, mostly from unescaped characters in prose. Markdoc pages failed 0.9 times per 100 edits, from unclosed tags and schema validation errors.",[234,507],{"x":236,"y":236,"width":237,"height":508,"fill":239},"260",[241,510,244,511,244,514,244,517,244,524,244,529,244,536,244,540,244,546,244,549,244,552,244,556,244,560,244,564,244,568,244,574,244,576,244,580,244,583,244,587,244,590,244,594,224],{"style":243},[246,512,513],{"x":248,"y":249,"fill":250,"style":251},"Failed builds per 100 edits, one quarter, 38 contributors",[246,515,20],{"x":255,"y":516,"fill":250,"style":257},"88",[234,518],{"x":277,"y":519,"width":520,"height":521,"fill":286,"opacity":522,"stroke":288,"style":523},"68","327","32","0.28","stroke-width:1px",[246,525,528],{"x":526,"y":527,"fill":250,"style":272},"293","89","unescaped \u003C or { in prose",[234,530],{"x":531,"y":519,"width":532,"height":521,"fill":533,"opacity":534,"stroke":535,"style":523},"457","133","#ffca3a","0.35","#a97b00",[246,537,539],{"x":538,"y":527,"fill":250,"style":272},"523","tags",[234,541],{"x":542,"y":519,"width":543,"height":521,"fill":544,"opacity":545,"stroke":544,"style":523},"590","48","#1982c4","0.25",[246,547,477],{"x":548,"y":527,"fill":358,"style":257},"650",[246,550,24],{"x":255,"y":551,"fill":250,"style":257},"158",[234,553],{"x":277,"y":554,"width":555,"height":521,"fill":533,"opacity":534,"stroke":535,"style":523},"138","62",[234,557],{"x":303,"y":554,"width":558,"height":521,"fill":318,"opacity":559,"stroke":320,"style":523},"80","0.3",[246,561,480],{"x":562,"y":563,"fill":364,"style":257},"284","159",[234,565],{"x":277,"y":566,"width":567,"height":567,"fill":286,"opacity":522,"stroke":288,"style":523},"200","12",[246,569,573],{"x":570,"y":571,"fill":331,"style":572},"148","210","font-size:11px","prose parsing",[234,575],{"x":508,"y":566,"width":567,"height":567,"fill":533,"opacity":534,"stroke":535,"style":523},[246,577,579],{"x":578,"y":571,"fill":331,"style":572},"278","tag structure",[234,581],{"x":582,"y":566,"width":567,"height":567,"fill":544,"opacity":545,"stroke":544,"style":523},"390",[246,584,586],{"x":585,"y":571,"fill":331,"style":572},"408","unknown component",[234,588],{"x":589,"y":566,"width":567,"height":567,"fill":318,"opacity":559,"stroke":320,"style":523},"540",[246,591,593],{"x":592,"y":571,"fill":331,"style":572},"558","schema validation",[246,595,597],{"x":248,"y":596,"fill":331,"style":359},"244","From CI logs; a schema error is a good failure, because it names the exact mistake",[385,599,600],{},"The largest MDX error category disappears entirely in Markdoc, and Markdoc's own failures are mostly its schema doing its job.",[41,602,604],{"id":603},"build-speed","Build Speed",[14,606,607,608,611],{},"The same 1,200 pages were built three ways in Astro 5 on a GitHub Actions runner, timed with ",[27,609,610],{},"hyperfine"," over five runs:",[396,613,614,627],{},[399,615,616],{},[402,617,618,621,624],{},[405,619,620],{},"Content format",[405,622,623],{},"Cold build",[405,625,626],{},"Peak memory",[415,628,629,640,650],{},[402,630,631,634,637],{},[420,632,633],{},"Plain Markdown (components stripped)",[420,635,636],{},"29 s",[420,638,639],{},"1.1 GB",[402,641,642,644,647],{},[420,643,24],{},[420,645,646],{},"34 s",[420,648,649],{},"1.2 GB",[402,651,652,654,657],{},[420,653,20],{},[420,655,656],{},"49 s",[420,658,659],{},"1.6 GB",[213,661,662,726],{},[216,663,224,668,224,671,224,674,224,677],{"viewBox":664,"role":219,"ariaLabelledBy":665,"xmlns":223},"0 0 760 240",[666,667],"mxm-speed-title","mxm-speed-desc",[226,669,670],{"id":666},"Build time and memory for the same 1,200 pages in three formats",[230,672,673],{"id":667},"Bars of cold build time. Plain Markdown took 29 seconds using 1.1 gigabytes, Markdoc 34 seconds using 1.2 gigabytes, and MDX 49 seconds using 1.6 gigabytes.",[234,675],{"x":236,"y":236,"width":237,"height":676,"fill":239},"240",[241,678,244,679,244,682,244,686,244,690,244,695,244,699,244,702,244,707,244,711,244,714,244,718,244,722,224],{"style":243},[246,680,681],{"x":248,"y":249,"fill":250,"style":251},"Same content, three formats, Astro 5",[112,683],{"x1":306,"y1":684,"x2":306,"y2":685,"stroke":266,"style":267},"46","196",[246,687,689],{"x":255,"y":688,"fill":250,"style":257},"78","Plain Markdown",[234,691],{"x":306,"y":692,"width":238,"height":693,"rx":694,"fill":318,"opacity":559,"stroke":320,"style":523},"60","26","4",[246,696,698],{"x":697,"y":688,"fill":250},"470","29 s · 1.1 GB",[246,700,24],{"x":255,"y":701,"fill":250,"style":257},"126",[234,703],{"x":306,"y":704,"width":705,"height":693,"rx":694,"fill":706,"opacity":545,"stroke":706,"style":523},"108","340","#6a4c93",[246,708,710],{"x":709,"y":701,"fill":250},"520","34 s · 1.2 GB",[246,712,20],{"x":255,"y":713,"fill":250,"style":257},"174",[234,715],{"x":306,"y":716,"width":717,"height":693,"rx":694,"fill":286,"opacity":545,"stroke":288,"style":523},"156","490",[246,719,721],{"x":720,"y":713,"fill":250},"670","49 s · 1.6 GB",[246,723,725],{"x":248,"y":724,"fill":331,"style":359},"222","hyperfine, 5 runs, GitHub Actions ubuntu-latest; bar length proportional to seconds",[385,727,728],{},"Markdoc costs about five seconds over plain Markdown; MDX costs twenty, most of it in per-file JavaScript compilation.",[14,730,731,732,736],{},"MDX's extra fifteen seconds comes from compiling each page to a JavaScript module and bundling it. On a 10,000-page site that difference scales to minutes, which matters for preview deploys; see ",[35,733,735],{"href":734},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fastro-vs-eleventy-build-times-at-10000-pages\u002F","Astro vs Eleventy Build Times at 10,000 Pages"," for the scaling behaviour.",[41,738,740],{"id":739},"security-and-review","Security and Review",[14,742,743,744,747,748,752],{},"An MDX file is a program. It can ",[27,745,746],{},"import fs from 'node:fs'"," and read environment variables at build time, and a build that has deploy credentials in its environment will happily run it. For internal docs written by employees that is a manageable risk; for an open-source repository accepting pull requests from strangers, it means every content pull request needs code review, and preview builds of forks must run without secrets — the setup in ",[35,749,751],{"href":750},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc\u002F","Securing Deploy Credentials with GitHub OIDC"," helps here.",[14,754,755],{},"Markdoc content cannot import anything. Tags map only to components you registered, and functions available in content are only those you declared. A malicious Markdoc file can produce ugly output, but it cannot exfiltrate secrets.",[14,757,758,759,762,763,766],{},"The review burden follows directly. On the repository measured above, content pull requests that touched only ",[27,760,761],{},".mdoc"," files were approved by a writer alone, with a median review time of 3 hours. Pull requests touching ",[27,764,765],{},".mdx"," files required an engineer's approval under the repository's CODEOWNERS rules, and their median review time was 19 hours, largely spent waiting for an engineer to become available. Routing by file extension turned the security boundary into a workflow boundary: writers could move quickly on the content that could not hurt anything, and engineering attention went to the small set of files that could.",[14,768,769],{},"A schema also documents itself. The Markdoc config lists every tag, every attribute, its type and whether it is required, and that list can be rendered into a contributor guide automatically. With MDX, the equivalent documentation is whatever the component authors remembered to write, and the only complete reference is the component source.",[41,771,773],{"id":772},"choosing-and-mixing","Choosing and Mixing",[14,775,776],{},"Use this split, which several large docs teams have converged on:",[46,778,779,784,789],{},[49,780,781,783],{},[18,782,24],{}," for the bulk of pages edited by writers, support staff and outside contributors. Define a schema of eight to twelve tags and treat it as the content API.",[49,785,786,788],{},[18,787,20],{}," for the handful of engineer-owned pages that genuinely need code: an interactive configuration generator, a page computed from imported data.",[49,790,791,793],{},[18,792,689],{}," wherever no component is needed — which, in most docs repositories, is the majority of files.",[14,795,796,797,799,800,426,803,805,806,39],{},"Starlight and Astro allow all three in one content collection, so the split can be per file. Pair it with a lint rule that fails CI when a ",[27,798,765],{}," file has no import or JSX, forcing it back to ",[27,801,802],{},".md",[27,804,761],{},". The same \"smallest capable format\" idea shows up in ",[35,807,809],{"href":808},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors\u002F","Shortcodes vs Components for Docs Authors",[41,811,813],{"id":812},"pitfalls-rollback","Pitfalls & Rollback",[46,815,816,822,828,834,840,846],{},[49,817,818,821],{},[18,819,820],{},"Converting everything to MDX \"for consistency\"."," It imports MDX's error modes into files that never needed components. Keep plain pages plain.",[49,823,824,827],{},[18,825,826],{},"An unbounded Markdoc schema."," Adding a tag for every one-off layout recreates MDX's flexibility with worse ergonomics. Review new tags like API changes.",[49,829,830,833],{},[18,831,832],{},"Forgetting editor support."," Install the Markdoc language server or VS Code extension so writers see schema errors as they type, not only in CI.",[49,835,836,839],{},[18,837,838],{},"Migrating in one pass."," Convert the highest-traffic, most-edited pages first and measure failed-build rates before committing to a full conversion.",[49,841,842,845],{},[18,843,844],{},"Duplicated components."," Markdoc tags and MDX components should render through the same underlying Astro component, so a design change lands once and both formats stay visually identical.",[49,847,848,851],{},[18,849,850],{},"Rollback:"," formats coexist per file, so converting back is a per-file rename plus rewriting tag syntax. Keep the conversion script reversible and the change set small enough to revert.",[41,853,855],{"id":854},"conclusion","Conclusion",[14,857,858],{},"MDX gives engineers maximum power and gives writers a JavaScript compiler's error messages. Markdoc gives writers a small, validated vocabulary and gives security reviewers content that cannot execute. On a 1,200-page, 38-contributor repository, Markdoc cut failed builds per hundred edits from 4.1 to 0.9 and built 30% faster. Default to plain Markdown, use Markdoc when writers need components, and reserve MDX for the few pages where content genuinely has to be code.",[41,860,862],{"id":861},"faq","FAQ",[864,865,867],"h3",{"id":866},"what-is-the-core-difference-between-mdx-and-markdoc","What is the core difference between MDX and Markdoc?",[14,869,870],{},"MDX compiles Markdown into JavaScript, so any JSX expression or import is executable code. Markdoc parses Markdown with a fixed tag syntax into a data tree that is validated against a schema and then rendered, so content cannot run arbitrary code.",[864,872,874],{"id":873},"which-is-faster-to-build","Which is faster to build?",[14,876,877],{},"Markdoc, in our measurements. On 1,200 pages in Astro, Markdoc content built in 34 seconds against 49 seconds for the same content as MDX, because Markdoc skips the JavaScript compilation step for each file.",[864,879,881],{"id":880},"can-i-use-both-in-one-site","Can I use both in one site?",[14,883,884],{},"Yes. Astro and Starlight accept Markdown, MDX and Markdoc side by side. A common split is Markdoc for contributor-edited pages and MDX for a few engineer-owned pages that need custom interactive components.",[864,886,888],{"id":887},"is-mdx-unsafe-for-open-source-docs","Is MDX unsafe for open-source docs?",[14,890,891],{},"It is a risk to manage rather than a reason to avoid it. An MDX file can import and execute code at build time, so pull requests from outside contributors need the same review as code changes. Markdoc removes that class of risk.",[41,893,895],{"id":894},"related","Related",[46,897,898,907,914,921,928],{},[49,899,900,903,904,906],{},[18,901,902],{},"Parent:"," ",[35,905,38],{"href":37}," — where content format fits the framework choice.",[49,908,909,913],{},[35,910,912],{"href":911},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fcontent-collections-vs-eleventy-data-cascade\u002F","Content Collections vs Eleventy Data Cascade"," — schema validation for front matter.",[49,915,916,920],{},[35,917,919],{"href":918},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fbest-ssg-for-technical-writers-without-coding-experience\u002F","Best SSG for Technical Writers Without Coding Experience"," — authoring ergonomics across generators.",[49,922,923,927],{},[35,924,926],{"href":925},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci\u002F","Editorial Checks with Vale in CI"," — linting prose alongside markup.",[49,929,930,934],{},[35,931,933],{"href":932},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight\u002F","Migrating from MkDocs to Starlight"," — where MDX was needed only for tabs.",[936,937,938],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":106,"searchDepth":120,"depth":120,"links":940},[941,942,943,944,945,946,947,948,949,955],{"id":43,"depth":120,"text":44},{"id":68,"depth":120,"text":69},{"id":390,"depth":120,"text":391},{"id":603,"depth":120,"text":604},{"id":739,"depth":120,"text":740},{"id":772,"depth":120,"text":773},{"id":812,"depth":120,"text":813},{"id":854,"depth":120,"text":855},{"id":861,"depth":120,"text":862,"children":950},[951,952,953,954],{"id":866,"depth":127,"text":867},{"id":873,"depth":127,"text":874},{"id":880,"depth":127,"text":881},{"id":887,"depth":127,"text":888},{"id":894,"depth":120,"text":895},[957,960,963,964],{"name":958,"item":959},"Home","\u002F",{"name":961,"item":962},"Choosing the Right Static Site Generator for Production","\u002Fchoosing-the-right-static-site-generator-for-production\u002F",{"name":38,"item":37},{"name":5,"item":965},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content\u002F","2026-09-18","Choose between MDX and Markdoc for documentation components: authoring errors, validation, build speed and safety for contributor-heavy docs repos.",[969,970,971,972],{"q":867,"a":870},{"q":874,"a":877},{"q":881,"a":884},{"q":888,"a":891},{},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content",{"title":5,"description":967},"choosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content\u002Findex","article","QukQ9Mp1PGPNcCGqFIouTKXmnv3rIxPopK1oZtwO7zA",[980,982,985,988,991,993,996,999,1002,1004,1005,1007,1010,1013,1016,1019,1022,1025,1028,1031,1033,1036,1039,1042,1045,1048,1051,1054,1057,1060,1063,1066,1069,1072,1075,1078,1081,1084,1087,1090,1093,1096,1099,1102,1105,1108,1111,1114,1117,1120,1123,1126,1129,1132,1135,1138,1141,1144,1147,1150,1153,1156,1159,1162,1165,1168,1171,1174,1177,1180,1183,1186,1189,1192,1195,1198,1201,1204,1207,1210,1213,1216,1219,1222,1225,1228,1231,1234,1237,1240,1243,1246,1249,1252,1255,1258,1261,1264,1267,1270,1273,1276,1279,1282,1285,1288,1291,1294,1297,1300,1303,1306,1309,1312,1315,1318,1321,1324,1327,1330,1333,1335,1338,1341,1344,1347,1350,1353,1356,1359,1362,1365,1368,1371,1374,1377,1380,1383,1386,1389,1392,1395,1398,1401,1404,1407,1410,1413,1416,1419,1422,1425,1428,1431,1434,1437,1440,1443,1446,1449,1452,1455,1458,1461,1464,1467,1470,1473,1475,1478,1481,1484,1487,1490,1493,1496,1499,1502,1505,1508,1511,1514,1517],{"path":981,"title":735},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fastro-vs-eleventy-build-times-at-10000-pages",{"path":983,"title":984},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fchoosing-between-astro-and-eleventy-for-large-docs","Astro vs Eleventy for Large Docs (1000+ Pages)",{"path":986,"title":987},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fcontent-collections-vs-eleventy-data-cascade","Content Collections vs the Eleventy Data Cascade",{"path":989,"title":990},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":992,"title":809},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors",{"path":994,"title":995},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fsidebar-navigation-in-astro-and-eleventy","Sidebar Navigation in Astro and Eleventy",{"path":997,"title":998},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcustomizing-starlight-without-forking-the-theme","Customizing Starlight Without Forking the Theme",{"path":1000,"title":1001},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fdocusaurus-vs-starlight-for-product-documentation","Docusaurus vs Starlight for Product Documentation",{"path":1003,"title":38},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress",{"path":974,"title":5},{"path":1006,"title":933},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight",{"path":1008,"title":1009},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1011,"title":1012},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1014,"title":1015},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhow-to-benchmark-hugo-vs-astro-build-speeds","How to Benchmark Hugo vs Astro Build Speeds",{"path":1017,"title":1018},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-partialcached-for-faster-builds","Hugo partialCached for Faster Builds",{"path":1020,"title":1021},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1023,"title":1024},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fprofiling-hugo-templates-with-template-metrics","Profiling Hugo Templates With Template Metrics",{"path":1026,"title":1027},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners","Reducing Hugo Memory Usage on CI Runners",{"path":1029,"title":1030},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fspeeding-up-hugo-builds-with-render-hooks-and-caching","Speeding Up Hugo Builds with Render Hooks & Caching",{"path":1032,"title":961},"\u002Fchoosing-the-right-static-site-generator-for-production",{"path":1034,"title":1035},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Feleventy-vs-jekyll-for-markdown-heavy-blogs","Eleventy vs Jekyll for Markdown-Heavy Blogs",{"path":1037,"title":1038},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1040,"title":1041},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Freplacing-jekyll-plugins-when-migrating-to-eleventy","Replacing Jekyll Plugins When Migrating to Eleventy",{"path":1043,"title":1044},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-on-github-pages-without-plugins","Running Jekyll on GitHub Pages Without Plugins",{"path":1046,"title":1047},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1049,"title":1050},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1052,"title":1053},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fconverting-front-matter-at-scale-during-migration","Converting Front Matter at Scale During Migration",{"path":1055,"title":1056},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1058,"title":1059},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fkeeping-redirects-working-after-an-ssg-migration","Keeping Redirects Working After an SSG Migration",{"path":1061,"title":1062},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-a-docs-site-from-jekyll-to-hugo","Migrating a Docs Site From Jekyll to Hugo",{"path":1064,"title":1065},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1067,"title":1068},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-hugo-to-astro-without-breaking-urls","Migrating From Hugo to Astro Without Breaking URLs",{"path":1070,"title":1071},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-wordpress-to-a-static-site-generator","Migrating WordPress to a Static Site Generator",{"path":1073,"title":1074},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fporting-shortcodes-and-includes-between-generators","Porting Shortcodes and Includes Between Generators",{"path":1076,"title":1077},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fhandling-dynamic-routes-in-nextjs-static-export","Handling Dynamic Routes in Next.js Static Export",{"path":1079,"title":1080},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1082,"title":1083},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fmigrating-from-gatsby-to-nextjs-static-export","Migrating from Gatsby to Next.js Static Export",{"path":1085,"title":1086},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fnextjs-app-router-static-export-limitations","Next.js App Router Static Export Limitations",{"path":1088,"title":1089},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fnextjs-static-export-vs-astro-for-marketing-sites","Next.js Static Export vs Astro for Marketing",{"path":1091,"title":1092},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Foptimizing-images-in-nextjs-static-export","Optimizing Images in Next.js Static Export",{"path":1094,"title":1095},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fadding-pagefind-to-an-astro-site","Adding Pagefind to an Astro Site",{"path":1097,"title":1098},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fbuilding-a-lunr-index-at-build-time-in-eleventy","Building a Lunr Index at Build Time in Eleventy",{"path":1100,"title":1101},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1103,"title":1104},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1106,"title":1107},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1109,"title":1110},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1112,"title":1113},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fsearch-index-size-budgets-for-large-docs","Search Index Size Budgets for Large Docs",{"path":1115,"title":1116},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fbest-ssg-for-technical-writers-without-coding-experience","Best SSG for Non-Developer Technical Writers",{"path":1118,"title":1119},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fchoosing-an-ssg-for-api-reference-documentation","Choosing an SSG for API Reference Documentation",{"path":1121,"title":1122},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1124,"title":1125},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1127,"title":1128},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fpicking-an-ssg-for-a-multi-language-documentation-site","Picking an SSG for a Multi-Language Docs Site",{"path":1130,"title":1131},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fssg-selection-checklist-for-engineering-teams","SSG Selection Checklist for Engineering Teams",{"path":1133,"title":1134},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Ftotal-cost-of-ownership-for-static-site-generators","Total Cost of Ownership for Static Site Generators",{"path":1136,"title":1137},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-busting-with-content-hashed-filenames","Cache Busting with Content-Hashed Filenames",{"path":1139,"title":1140},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1142,"title":1143},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fpurging-the-cdn-cache-after-a-static-deploy","Purging the CDN Cache After a Static Deploy",{"path":1145,"title":1146},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fsetting-cache-control-headers-on-cloudflare-pages","Cache-Control Headers on Cloudflare Pages",{"path":1148,"title":1149},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fsetting-up-proper-cache-headers-on-netlify","Proper Cache Headers on Netlify for SSGs",{"path":1151,"title":1152},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fstale-while-revalidate-for-static-html","Stale-While-Revalidate for Static HTML",{"path":1154,"title":1155},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Feliminating-layout-shift-from-web-fonts","Eliminating Layout Shift From Web Fonts",{"path":1157,"title":1158},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-cookie-banners","Fixing CLS from Cookie Banners",{"path":1160,"title":1161},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-late-loading-embeds","Fixing CLS From Late-Loading Embeds",{"path":1163,"title":1164},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-sticky-headers-and-anchor-links","Fixing CLS from Sticky Headers and Anchor Links",{"path":1166,"title":1167},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1169,"title":1170},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Fmeasuring-cls-in-the-field-with-web-vitals-js","Measuring CLS in the Field With web-vitals.js",{"path":1172,"title":1173},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Freserving-space-for-images-and-embeds-to-stop-layout-shift","Reserving Space for Images and Embeds",{"path":1175,"title":1176},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1178,"title":1179},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1181,"title":1182},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fmetric-matched-fallback-fonts-with-size-adjust","Metric-Matched Fallback Fonts with size-adjust",{"path":1184,"title":1185},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1187,"title":1188},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fself-hosting-google-fonts-to-eliminate-layout-shift","Self-Host Google Fonts to Eliminate Layout Shift",{"path":1190,"title":1191},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fsubsetting-variable-fonts-for-faster-first-render","Subsetting Variable Fonts for Faster First Render",{"path":1193,"title":1194},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fbuilding-an-image-cdn-pipeline-for-static-sites","Building an Image CDN Pipeline for Static Sites",{"path":1196,"title":1197},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fgenerating-open-graph-images-at-build-time","Generating Open Graph Images at Build Time",{"path":1199,"title":1200},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1202,"title":1203},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Flazy-loading-images-without-hurting-lcp","Lazy-Loading Images Without Hurting LCP",{"path":1205,"title":1206},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Foptimizing-webp-images-in-hugo-without-plugins","Optimizing WebP Images in Hugo Without Plugins",{"path":1208,"title":1209},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fresponsive-images-with-srcset-in-eleventy","Responsive Images with srcset in Eleventy",{"path":1211,"title":1212},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fserving-avif-with-fallbacks-on-static-sites","Serving AVIF With Fallbacks on Static Sites",{"path":1214,"title":1215},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1217,"title":1218},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1220,"title":1221},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fdeferring-hydration-with-client-visible-in-astro","Deferring Hydration with client:visible in Astro",{"path":1223,"title":1224},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fhow-to-reduce-bundle-size-in-eleventy-builds","How to Reduce Bundle Size in Eleventy Builds",{"path":1226,"title":1227},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1229,"title":1230},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fmeasuring-inp-on-static-sites-with-real-user-monitoring","Measuring INP on Static Sites with RUM",{"path":1232,"title":1233},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1235,"title":1236},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Feliminating-render-blocking-css-on-static-sites","Eliminating Render-Blocking CSS on Static Sites",{"path":1238,"title":1239},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-lcp-on-text-heavy-documentation-pages","Fixing LCP on Text-Heavy Documentation Pages",{"path":1241,"title":1242},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1244,"title":1245},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Fmeasuring-lcp-subparts-with-devtools","Measuring LCP Subparts with DevTools",{"path":1247,"title":1248},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Foptimizing-lcp-on-astro-with-priority-hints","Optimizing LCP on Astro with Priority Hints",{"path":1250,"title":1251},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Freducing-lcp-from-hero-images-on-static-sites","Reducing LCP from Hero Images on Static Sites",{"path":1253,"title":1254},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fcomparing-lab-and-field-data-with-crux","Comparing Lab and Field Data with CrUX",{"path":1256,"title":1257},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1259,"title":1260},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Freducing-lighthouse-score-variance-in-ci","Reducing Lighthouse Score Variance in CI",{"path":1262,"title":1263},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Frunning-webpagetest-scripts-against-preview-deploys","Running WebPageTest Scripts Against Preview Deploys",{"path":1265,"title":1266},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fsetting-up-lighthouse-ci-for-a-static-site","Setting Up Lighthouse CI for a Static Site",{"path":1268,"title":1269},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-bundle-size-per-pull-request","Tracking Bundle Size per Pull Request",{"path":1271,"title":1272},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fwriting-a-performance-budget-that-fails-builds","Writing a Performance Budget That Fails Builds",{"path":1274,"title":1275},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1277,"title":1278},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1280,"title":1281},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1283,"title":1284},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fpreconnect-vs-dns-prefetch-on-static-sites","Preconnect vs DNS-Prefetch on Static Sites",{"path":1286,"title":1287},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1289,"title":1290},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fview-transitions-on-multi-page-static-sites","View Transitions on Multi-Page Static Sites",{"path":1292,"title":1293},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fauditing-third-party-scripts-with-lighthouse","Auditing Third-Party Scripts With Lighthouse",{"path":1295,"title":1296},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1298,"title":1299},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Flazy-loading-youtube-embeds-on-static-sites","Lazy-Loading YouTube Embeds on Static Sites",{"path":1301,"title":1302},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Floading-google-tag-manager-without-hurting-inp","Loading Google Tag Manager Without Hurting INP",{"path":1304,"title":1305},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Frunning-third-party-scripts-in-a-web-worker-with-partytown","Running Third-Party Scripts in a Web Worker with Partytown",{"path":1307,"title":1308},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fself-hosting-analytics-to-cut-third-party-requests","Self-Hosting Analytics to Cut Third-Party Requests",{"path":1310,"title":1311},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1313,"title":1314},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1316,"title":1317},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcustom-domains-and-tls-on-cloudflare-pages","Custom Domains and TLS on Cloudflare Pages",{"path":1319,"title":1320},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-hugo-to-cloudflare-pages-and-workers","Deploying Hugo to Cloudflare Pages and Workers",{"path":1322,"title":1323},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1325,"title":1326},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fmigrating-from-cloudflare-pages-to-workers-static-assets","Migrating from Cloudflare Pages to Workers Static Assets",{"path":1328,"title":1329},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1331,"title":1332},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fdocs-as-code-review-workflow-for-writers","Docs-as-Code Review Workflow for Writers",{"path":1334,"title":926},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci",{"path":1336,"title":1337},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1339,"title":1340},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduling-content-publication-with-cron-triggered-builds","Scheduling Content Publication With Cron-Triggered Builds",{"path":1342,"title":1343},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fwiring-a-headless-cms-to-a-static-build","Wiring a Headless CMS to a Static Build",{"path":1345,"title":1346},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1348,"title":1349},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fcaching-node-modules-in-github-actions-for-faster-ssg-builds","Caching node_modules in GitHub Actions",{"path":1351,"title":1352},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1354,"title":1355},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-multiple-environments-from-one-workflow","Deploying to Multiple Environments From One Workflow",{"path":1357,"title":1358},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fhow-to-set-up-github-actions-for-hugo-deployments","GitHub Actions for Hugo Deployments",{"path":1360,"title":1361},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1363,"title":1364},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1366,"title":1367},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fcaching-hugo-builds-in-github-actions","Caching Hugo Builds in GitHub Actions",{"path":1369,"title":1370},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1372,"title":1373},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fincremental-builds-in-astro-with-the-content-layer","Incremental Builds in Astro with the Content Layer",{"path":1375,"title":1376},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1378,"title":1379},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fmeasuring-build-time-regressions-in-ci","Measuring Build-Time Regressions in CI",{"path":1381,"title":1382},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fremote-caching-with-turborepo-for-ssg-monorepos","Remote Caching with Turborepo for SSG Monorepos",{"path":1384,"title":1385},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fsharing-build-cache-across-ci-runners","Sharing Build Cache Across CI Runners",{"path":1387,"title":1388},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1390,"title":1391},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1393,"title":1394},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fbuilding-a-core-web-vitals-dashboard-from-rum-data","Building a Core Web Vitals Dashboard from RUM Data",{"path":1396,"title":1397},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fcrawling-for-broken-links-on-a-schedule","Crawling for Broken Links on a Schedule",{"path":1399,"title":1400},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1402,"title":1403},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1405,"title":1406},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fuptime-and-synthetic-checks-for-static-sites","Uptime and Synthetic Checks for Static Sites",{"path":1408,"title":1409},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1411,"title":1412},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1414,"title":1415},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1417,"title":1418},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites","Netlify Redirects and Rewrites for Static Sites",{"path":1420,"title":1421},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fsetting-up-deploy-previews-on-netlify-for-every-pull-request","Netlify Deploy Previews for Every Pull Request",{"path":1423,"title":1424},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-isr-vs-static-generation-for-ssgs","Vercel ISR vs Static Generation for SSGs",{"path":1426,"title":1427},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fautomating-preview-deploy-pipelines-with-github-actions","Automating Preview Deploy Pipelines with GitHub Actions",{"path":1429,"title":1430},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1432,"title":1433},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":1435,"title":1436},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1438,"title":1439},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1441,"title":1442},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1444,"title":1445},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1447,"title":1448},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":1450,"title":1451},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1453,"title":1454},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1456,"title":1457},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-a-bad-static-deploy-in-under-a-minute","Rolling Back a Bad Static Deploy in Under a Minute",{"path":1459,"title":1460},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frunning-smoke-tests-against-a-preview-url","Running Smoke Tests Against a Preview URL",{"path":1462,"title":1463},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1465,"title":1466},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1468,"title":1469},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fhash-based-csp-for-inline-scripts-in-astro","Hash-Based CSP for Inline Scripts in Astro",{"path":1471,"title":1472},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1474,"title":751},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc",{"path":1476,"title":1477},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1479,"title":1480},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fwriting-a-content-security-policy-for-a-static-site","Writing a Content Security Policy for a Static Site",{"path":1482,"title":1483},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1485,"title":1486},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1488,"title":1489},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fdeploying-a-static-site-to-s3-and-cloudfront","Deploying a Static Site to S3 and CloudFront",{"path":1491,"title":1492},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1494,"title":1495},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1497,"title":1498},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1500,"title":1501},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1503,"title":1504},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fadding-a-contact-form-with-cloudflare-workers","Adding a Contact Form with Cloudflare Workers",{"path":1506,"title":1507},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fhandling-form-submissions-on-a-static-site","Handling Form Submissions on a Static Site",{"path":1509,"title":1510},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1512,"title":1513},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1515,"title":1516},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1518,"title":1519},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fproxying-third-party-apis-from-an-edge-function","Proxying Third-Party APIs from an Edge Function",1789722847271]