[{"data":1,"prerenderedAt":2428},["ShallowReactive",2],{"page:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus":3,"all-docs-nav":1278,"filed:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus":2419},{"id":4,"title":5,"body":6,"breadcrumb":1253,"dateModified":1263,"datePublished":1263,"description":1264,"extension":1265,"faq":1266,"meta":1271,"navigation":1272,"path":1273,"seo":1274,"slug":12,"stem":1275,"type":1276,"__hash__":1277},"content\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus\u002Findex.md","Versioned Documentation with Docusaurus",{"type":7,"value":8,"toc":1236},"minimark",[9,13,17,26,31,57,61,97,107,270,274,277,388,399,550,557,561,568,656,756,760,765,877,904,1000,1004,1007,1025,1031,1041,1058,1061,1065,1147,1151,1157,1161,1166,1169,1173,1176,1180,1183,1187,1190,1194,1232],[10,11,5],"h1",{"id":12},"versioned-documentation-with-docusaurus",[14,15,16],"p",{},"Versioning is the feature that most often decides a team for Docusaurus: one command snapshots the docs, a dropdown appears, and readers on an older release see instructions that match their software. The cost is quiet and cumulative. Every version you cut is a full copy of the docs that the build compiles on every run, so a site with five versions builds roughly five times the pages it seems to have. This guide covers cutting versions correctly, keeping build time flat as they accumulate, and retiring old versions without breaking a single link.",[14,18,19,20,25],{},"It belongs to ",[21,22,24],"a",{"href":23},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002F","Docs Frameworks: Docusaurus, Starlight and VitePress",", where the versioning trade-off against Starlight and VitePress is summarised.",[27,28,30],"h2",{"id":29},"prerequisites","Prerequisites",[32,33,34,43,46],"ul",{},[35,36,37,38,42],"li",{},"A Docusaurus 3.x site using the classic preset, with docs in ",[39,40,41],"code",{},"docs\u002F",".",[35,44,45],{},"A release process that knows when a version ships, so cutting docs can be scripted into it.",[35,47,48,49,52,53,42],{},"Build timing in CI — at minimum the wall time of ",[39,50,51],{},"docusaurus build",", ideally tracked per run as in ",[21,54,56],{"href":55},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fmeasuring-build-time-regressions-in-ci\u002F","Measuring Build Time Regressions in CI",[27,58,60],{"id":59},"how-docusaurus-stores-versions","How Docusaurus Stores Versions",[14,62,63,64,67,68,70,71,74,75,78,79,70,82,85,86,88,89,93,94,96],{},"Running ",[39,65,66],{},"npx docusaurus docs:version 3.2"," does three things: it copies ",[39,69,41],{}," to ",[39,72,73],{},"versioned_docs\u002Fversion-3.2\u002F",", copies the current sidebar to ",[39,76,77],{},"versioned_sidebars\u002Fversion-3.2-sidebars.json",", and prepends ",[39,80,81],{},"3.2",[39,83,84],{},"versions.json",". From then on, ",[39,87,41],{}," is the unreleased ",[90,91,92],"strong",{},"next"," version, and each entry in ",[39,95,84],{}," is a frozen snapshot.",[98,99,105],"pre",{"className":100,"code":102,"language":103,"meta":104},[101],"language-text","website\u002F\n├── docs\u002F                         # \"next\" — work in progress\n├── versioned_docs\u002F\n│   ├── version-3.2\u002F              # latest release\n│   ├── version-3.1\u002F\n│   └── version-2.9\u002F\n├── versioned_sidebars\u002F\n│   ├── version-3.2-sidebars.json\n│   └── ...\n└── versions.json                 # [\"3.2\", \"3.1\", \"2.9\"]\n","text","",[39,106,102],{"__ignoreMap":104},[108,109,110,266],"figure",{},[111,112,119,120,119,124,119,128,119,135,119,250],"svg",{"viewBox":113,"role":114,"ariaLabelledBy":115,"xmlns":118},"0 0 760 290","img",[116,117],"dver-store-title","dver-store-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[121,122,123],"title",{"id":116},"What docs:version copies and where it serves it",[125,126,127],"desc",{"id":117},"The docs folder is copied into a versioned_docs folder for the new release. The versions.json file lists releases. Next is served under the \u002Fdocs\u002Fnext\u002F path, the latest release at \u002Fdocs\u002F, and older releases at \u002Fdocs\u002F followed by the version number.",[129,130],"rect",{"x":131,"y":131,"width":132,"height":133,"fill":134},"0","760","290","#ffffff",[136,137,139,140,139,147,139,156,139,161,139,167,139,171,139,175,139,178,139,184,139,189,139,195,139,198,139,201,139,204,139,208,139,215,139,220,139,224,139,230,139,233,139,236,139,239,139,243,139,246,119],"g",{"style":138},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[103,141,146],{"x":142,"y":143,"fill":144,"style":145},"380","28","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","One command, a full copy, a new URL space",[129,148],{"x":149,"y":150,"width":151,"height":150,"rx":152,"fill":153,"opacity":154,"stroke":153,"style":155},"30","60","170","10","#1982c4","0.14","stroke-width:1.5px",[103,157,41],{"x":158,"y":159,"fill":144,"style":160},"115","86","font-weight:700;text-anchor:middle",[103,162,166],{"x":158,"y":163,"fill":164,"style":165},"106","#556071","font-size:11px;text-anchor:middle","editable, unreleased",[129,168],{"x":133,"y":150,"width":169,"height":150,"rx":152,"fill":170,"opacity":154,"stroke":170,"style":155},"200","#6a4c93",[103,172,174],{"x":173,"y":159,"fill":144,"style":160},"390","versioned_docs\u002Fversion-3.2",[103,176,177],{"x":173,"y":163,"fill":164,"style":165},"frozen snapshot",[179,180],"path",{"d":181,"stroke":164,"fill":182,"style":183},"M202 90 L286 90","none","stroke-width:2px;marker-end:url(#dver-arrow)",[103,185,188],{"x":186,"y":187,"fill":164,"style":165},"244","80","copy",[129,190],{"x":191,"y":150,"width":192,"height":150,"rx":152,"fill":193,"stroke":194,"style":155},"580","150","#f8fafc","#d9e2ef",[103,196,84],{"x":197,"y":159,"fill":144,"style":160},"655",[103,199,200],{"x":197,"y":163,"fill":164,"style":165},"[\"3.2\", \"3.1\", \"2.9\"]",[179,202],{"d":203,"stroke":164,"fill":182,"style":183},"M492 90 L576 90",[103,205,207],{"x":206,"y":187,"fill":164,"style":165},"534","register",[129,209],{"x":149,"y":151,"width":210,"height":211,"rx":152,"fill":212,"opacity":213,"stroke":214,"style":155},"220","54","#ffca3a","0.26","#a97b00",[103,216,219],{"x":217,"y":218,"fill":144,"style":160},"140","194","\u002Fdocs\u002Fnext\u002F…",[103,221,223],{"x":217,"y":222,"fill":164,"style":165},"212","from docs\u002F",[129,225],{"x":226,"y":151,"width":210,"height":211,"rx":152,"fill":227,"opacity":228,"stroke":229,"style":155},"270","#8ac926","0.18","#5a8a16",[103,231,232],{"x":142,"y":218,"fill":144,"style":160},"\u002Fdocs\u002F…",[103,234,235],{"x":142,"y":222,"fill":164,"style":165},"latest release (3.2)",[129,237],{"x":238,"y":151,"width":210,"height":211,"rx":152,"fill":193,"stroke":194,"style":155},"510",[103,240,242],{"x":241,"y":218,"fill":144,"style":160},"620","\u002Fdocs\u002F3.1\u002F…  \u002Fdocs\u002F2.9\u002F…",[103,244,245],{"x":241,"y":222,"fill":164,"style":165},"older releases",[103,247,249],{"x":142,"y":248,"fill":164,"style":165},"262","Every row in versions.json is compiled on every build unless you tell Docusaurus otherwise",[251,252,139,253,119],"defs",{},[254,255,262,263,139],"marker",{"id":256,"viewBox":257,"refX":258,"refY":259,"markerWidth":260,"markerHeight":260,"orient":261},"dver-arrow","0 0 10 10","8","5","7","auto-start-reverse","\n      ",[179,264],{"d":265,"fill":164},"M0 0 L10 5 L0 10 z",[267,268,269],"figcaption",{},"The latest release owns the clean URL; next and older versions are prefixed. Readers who land from search usually arrive on the clean URL.",[27,271,273],{"id":272},"cutting-a-version-in-the-release-pipeline","Cutting a Version in the Release Pipeline",[14,275,276],{},"Cut docs versions from the same pipeline that tags the software, never by hand. A human-cut version drifts: somebody forgets, or cuts from a branch with unmerged docs.",[98,278,282],{"className":279,"code":280,"language":281,"meta":104,"style":104},"language-yaml shiki shiki-themes github-light github-dark","# .github\u002Fworkflows\u002Frelease.yml (excerpt)\n- name: Cut docs version\n  if: startsWith(github.ref, 'refs\u002Ftags\u002Fv') && !contains(github.ref, '-rc')\n  run: |\n    VERSION=\"${GITHUB_REF_NAME#v}\"          # v3.3.0 -> 3.3.0\n    MINOR=\"${VERSION%.*}\"                   # 3.3.0  -> 3.3\n    cd website\n    if ! jq -e --arg v \"$MINOR\" 'index($v)' versions.json >\u002Fdev\u002Fnull; then\n      npx docusaurus docs:version \"$MINOR\"\n      git add versioned_docs versioned_sidebars versions.json\n      git commit -m \"docs: cut version $MINOR\"\n      git push origin HEAD:main\n    fi\n","yaml",[39,283,284,293,311,322,334,340,346,352,358,364,370,376,382],{"__ignoreMap":104},[285,286,289],"span",{"class":287,"line":288},"line",1,[285,290,292],{"class":291},"sJ8bj","# .github\u002Fworkflows\u002Frelease.yml (excerpt)\n",[285,294,296,300,304,307],{"class":287,"line":295},2,[285,297,299],{"class":298},"sVt8B","- ",[285,301,303],{"class":302},"s9eBZ","name",[285,305,306],{"class":298},": ",[285,308,310],{"class":309},"sZZnC","Cut docs version\n",[285,312,314,317,319],{"class":287,"line":313},3,[285,315,316],{"class":302},"  if",[285,318,306],{"class":298},[285,320,321],{"class":309},"startsWith(github.ref, 'refs\u002Ftags\u002Fv') && !contains(github.ref, '-rc')\n",[285,323,325,328,330],{"class":287,"line":324},4,[285,326,327],{"class":302},"  run",[285,329,306],{"class":298},[285,331,333],{"class":332},"szBVR","|\n",[285,335,337],{"class":287,"line":336},5,[285,338,339],{"class":309},"    VERSION=\"${GITHUB_REF_NAME#v}\"          # v3.3.0 -> 3.3.0\n",[285,341,343],{"class":287,"line":342},6,[285,344,345],{"class":309},"    MINOR=\"${VERSION%.*}\"                   # 3.3.0  -> 3.3\n",[285,347,349],{"class":287,"line":348},7,[285,350,351],{"class":309},"    cd website\n",[285,353,355],{"class":287,"line":354},8,[285,356,357],{"class":309},"    if ! jq -e --arg v \"$MINOR\" 'index($v)' versions.json >\u002Fdev\u002Fnull; then\n",[285,359,361],{"class":287,"line":360},9,[285,362,363],{"class":309},"      npx docusaurus docs:version \"$MINOR\"\n",[285,365,367],{"class":287,"line":366},10,[285,368,369],{"class":309},"      git add versioned_docs versioned_sidebars versions.json\n",[285,371,373],{"class":287,"line":372},11,[285,374,375],{"class":309},"      git commit -m \"docs: cut version $MINOR\"\n",[285,377,379],{"class":287,"line":378},12,[285,380,381],{"class":309},"      git push origin HEAD:main\n",[285,383,385],{"class":287,"line":384},13,[285,386,387],{"class":309},"    fi\n",[14,389,390,391,394,395,398],{},"Version by ",[90,392,393],{},"minor"," release, not patch. Patch releases rarely change documented behaviour, and cutting a snapshot per patch is the fastest route to thirty near-identical copies. Configure the labels and banners in ",[39,396,397],{},"docusaurus.config.js",":",[98,400,404],{"className":401,"code":402,"language":403,"meta":104,"style":104},"language-js shiki shiki-themes github-light github-dark","docs: {\n  lastVersion: '3.3',\n  versions: {\n    current: { label: 'Next 🚧', path: 'next', banner: 'unreleased' },\n    '3.3': { label: '3.3 (latest)' },\n    '3.2': { banner: 'unmaintained' },\n  },\n  onlyIncludeVersions: process.env.DOCS_PREVIEW\n    ? ['current', '3.3']\n    : undefined,\n},\n","js",[39,405,406,415,428,435,474,487,500,505,517,535,545],{"__ignoreMap":104},[285,407,408,412],{"class":287,"line":288},[285,409,411],{"class":410},"sScJk","docs",[285,413,414],{"class":298},": {\n",[285,416,417,420,422,425],{"class":287,"line":295},[285,418,419],{"class":410},"  lastVersion",[285,421,306],{"class":298},[285,423,424],{"class":309},"'3.3'",[285,426,427],{"class":298},",\n",[285,429,430,433],{"class":287,"line":313},[285,431,432],{"class":410},"  versions",[285,434,414],{"class":298},[285,436,437,440,443,446,448,451,454,456,458,461,463,466,468,471],{"class":287,"line":324},[285,438,439],{"class":410},"    current",[285,441,442],{"class":298},": { ",[285,444,445],{"class":410},"label",[285,447,306],{"class":298},[285,449,450],{"class":309},"'Next 🚧'",[285,452,453],{"class":298},", ",[285,455,179],{"class":410},[285,457,306],{"class":298},[285,459,460],{"class":309},"'next'",[285,462,453],{"class":298},[285,464,465],{"class":410},"banner",[285,467,306],{"class":298},[285,469,470],{"class":309},"'unreleased'",[285,472,473],{"class":298}," },\n",[285,475,476,479,482,485],{"class":287,"line":336},[285,477,478],{"class":309},"    '3.3'",[285,480,481],{"class":298},": { label: ",[285,483,484],{"class":309},"'3.3 (latest)'",[285,486,473],{"class":298},[285,488,489,492,495,498],{"class":287,"line":342},[285,490,491],{"class":309},"    '3.2'",[285,493,494],{"class":298},": { banner: ",[285,496,497],{"class":309},"'unmaintained'",[285,499,473],{"class":298},[285,501,502],{"class":287,"line":348},[285,503,504],{"class":298},"  },\n",[285,506,507,510,513],{"class":287,"line":354},[285,508,509],{"class":410},"  onlyIncludeVersions",[285,511,512],{"class":298},": process.env.",[285,514,516],{"class":515},"sj4cs","DOCS_PREVIEW\n",[285,518,519,522,525,528,530,532],{"class":287,"line":360},[285,520,521],{"class":332},"    ?",[285,523,524],{"class":298}," [",[285,526,527],{"class":309},"'current'",[285,529,453],{"class":298},[285,531,424],{"class":309},[285,533,534],{"class":298},"]\n",[285,536,537,540,543],{"class":287,"line":366},[285,538,539],{"class":332},"    :",[285,541,542],{"class":515}," undefined",[285,544,427],{"class":298},[285,546,547],{"class":287,"line":372},[285,548,549],{"class":298},"},\n",[14,551,552,553,556],{},"The ",[39,554,555],{},"onlyIncludeVersions"," line is the single most valuable setting on a versioned site: pull-request previews rarely touch old versions, so they build only next and latest.",[27,558,560],{"id":559},"measured-impact","Measured Impact",[14,562,563,564,567],{},"A 480-page product docs site with five live versions (2,400 pages compiled), built on a GitHub Actions ",[39,565,566],{},"ubuntu-latest"," runner and timed over five runs:",[569,570,571,590],"table",{},[572,573,574],"thead",{},[575,576,577,581,584,587],"tr",{},[578,579,580],"th",{},"Configuration",[578,582,583],{},"Pages built",[578,585,586],{},"Build time",[578,588,589],{},"Peak memory",[591,592,593,608,625,642],"tbody",{},[575,594,595,599,602,605],{},[596,597,598],"td",{},"All five versions, webpack",[596,600,601],{},"2,400",[596,603,604],{},"5 min 40 s",[596,606,607],{},"3.9 GB",[575,609,610,617,619,622],{},[596,611,612,613,616],{},"All five versions, Rspack (",[39,614,615],{},"experimental_faster",")",[596,618,601],{},[596,620,621],{},"2 min 35 s",[596,623,624],{},"2.8 GB",[575,626,627,633,636,639],{},[596,628,629,630,632],{},"Preview: ",[39,631,555],{}," = next + latest, Rspack",[596,634,635],{},"960",[596,637,638],{},"1 min 50 s → 58 s",[596,640,641],{},"1.6 GB",[575,643,644,647,650,653],{},[596,645,646],{},"Two versions archived to snapshots, three live, Rspack",[596,648,649],{},"1,440",[596,651,652],{},"1 min 34 s",[596,654,655],{},"2.1 GB",[108,657,658,753],{},[111,659,119,664,119,667,119,670,119,673],{"viewBox":660,"role":114,"ariaLabelledBy":661,"xmlns":118},"0 0 760 300",[662,663],"dver-time-title","dver-time-desc",[121,665,666],{"id":662},"Build time grows with live versions",[125,668,669],{"id":663},"A line chart of build time against number of live versions. With webpack build time rises from about 70 seconds at one version to 340 seconds at five. With Rspack it rises from about 32 seconds to 155 seconds. A marker shows that archiving to three live versions brings the production build to 94 seconds.",[129,671],{"x":131,"y":131,"width":132,"height":672,"fill":134},"300",[136,674,139,675,139,678,139,683,139,686,139,689,139,693,139,696,139,699,139,702,139,706,139,710,139,714,139,717,139,723,139,726,139,731,139,738,139,744,139,749,119],{"style":138},[103,676,677],{"x":142,"y":143,"fill":144,"style":145},"Build seconds vs live versions (480 pages each)",[287,679],{"x1":680,"y1":681,"x2":682,"y2":681,"stroke":164,"style":155},"90","250","700",[287,684],{"x1":680,"y1":685,"x2":680,"y2":681,"stroke":164,"style":155},"50",[287,687],{"x1":680,"y1":192,"x2":682,"y2":192,"stroke":194,"style":688},"stroke-width:1px",[103,690,131],{"x":187,"y":691,"fill":164,"style":692},"254","font-size:11px;text-anchor:end",[103,694,169],{"x":187,"y":695,"fill":164,"style":692},"154",[103,697,698],{"x":187,"y":211,"fill":164,"style":692},"400",[103,700,701],{"x":192,"y":226,"fill":164,"style":165},"1",[103,703,705],{"x":704,"y":226,"fill":164,"style":165},"280","2",[103,707,709],{"x":708,"y":226,"fill":164,"style":165},"410","3",[103,711,713],{"x":712,"y":226,"fill":164,"style":165},"540","4",[103,715,259],{"x":716,"y":226,"fill":164,"style":165},"670",[718,719],"polyline",{"points":720,"fill":182,"stroke":721,"style":722},"150,215 280,183 410,137 540,113 670,80","#d83b41","stroke-width:2.5px",[718,724],{"points":725,"fill":182,"stroke":153,"style":722},"150,234 280,220 410,203 540,188 670,172",[727,728],"circle",{"cx":708,"cy":729,"r":260,"fill":227,"stroke":229,"style":730},"203","stroke-width:2px",[103,732,737],{"x":733,"y":734,"fill":735,"style":736},"420","226","#3f6410","font-size:11px;font-weight:700","3 live, Rspack: 94 s",[103,739,743],{"x":740,"y":741,"fill":742,"style":736},"600","72","#b32b30","webpack 340 s",[103,745,748],{"x":740,"y":746,"fill":747,"style":736},"164","#166a9e","Rspack 155 s",[103,750,752],{"x":142,"y":751,"fill":164,"style":165},"292","hyperfine, 5 runs per point, GitHub Actions ubuntu-latest",[267,754,755],{},"The slope, not the intercept, is the problem: every version you keep live adds the cost of the whole docs set to every build.",[27,757,759],{"id":758},"archiving-old-versions-to-snapshots","Archiving Old Versions to Snapshots",[14,761,762,763,398],{},"When a version leaves support, stop compiling it. Build it one final time, copy its output to a static archive, and remove it from ",[39,764,84],{},[98,766,770],{"className":767,"code":768,"language":769,"meta":104,"style":104},"language-bash shiki shiki-themes github-light github-dark","# Freeze 2.9 as a static snapshot served from \u002Fdocs\u002F2.9\u002F\nDOCS_ONLY=2.9 npx docusaurus build --out-dir \u002Ftmp\u002Farchive-build\nmkdir -p static\u002Fdocs-archive\u002F2.9\ncp -r \u002Ftmp\u002Farchive-build\u002Fdocs\u002F2.9\u002F. static\u002Fdocs-archive\u002F2.9\u002F\n# Remove it from the live build\njq 'map(select(. != \"2.9\"))' versions.json > v.tmp && mv v.tmp versions.json\ngit rm -r versioned_docs\u002Fversion-2.9 versioned_sidebars\u002Fversion-2.9-sidebars.json\n","bash",[39,771,772,777,803,814,828,833,861],{"__ignoreMap":104},[285,773,774],{"class":287,"line":288},[285,775,776],{"class":291},"# Freeze 2.9 as a static snapshot served from \u002Fdocs\u002F2.9\u002F\n",[285,778,779,782,785,788,791,794,797,800],{"class":287,"line":295},[285,780,781],{"class":298},"DOCS_ONLY",[285,783,784],{"class":332},"=",[285,786,787],{"class":309},"2.9",[285,789,790],{"class":410}," npx",[285,792,793],{"class":309}," docusaurus",[285,795,796],{"class":309}," build",[285,798,799],{"class":515}," --out-dir",[285,801,802],{"class":309}," \u002Ftmp\u002Farchive-build\n",[285,804,805,808,811],{"class":287,"line":313},[285,806,807],{"class":410},"mkdir",[285,809,810],{"class":515}," -p",[285,812,813],{"class":309}," static\u002Fdocs-archive\u002F2.9\n",[285,815,816,819,822,825],{"class":287,"line":324},[285,817,818],{"class":410},"cp",[285,820,821],{"class":515}," -r",[285,823,824],{"class":309}," \u002Ftmp\u002Farchive-build\u002Fdocs\u002F2.9\u002F.",[285,826,827],{"class":309}," static\u002Fdocs-archive\u002F2.9\u002F\n",[285,829,830],{"class":287,"line":336},[285,831,832],{"class":291},"# Remove it from the live build\n",[285,834,835,838,841,844,847,850,853,856,858],{"class":287,"line":342},[285,836,837],{"class":410},"jq",[285,839,840],{"class":309}," 'map(select(. != \"2.9\"))'",[285,842,843],{"class":309}," versions.json",[285,845,846],{"class":332}," >",[285,848,849],{"class":309}," v.tmp",[285,851,852],{"class":298}," && ",[285,854,855],{"class":410},"mv",[285,857,849],{"class":309},[285,859,860],{"class":309}," versions.json\n",[285,862,863,866,869,871,874],{"class":287,"line":348},[285,864,865],{"class":410},"git",[285,867,868],{"class":309}," rm",[285,870,821],{"class":515},[285,872,873],{"class":309}," versioned_docs\u002Fversion-2.9",[285,875,876],{"class":309}," versioned_sidebars\u002Fversion-2.9-sidebars.json\n",[14,878,879,880,883,884,887,888,891,892,895,896,891,900,42],{},"Then add a host-level rewrite so ",[39,881,882],{},"\u002Fdocs\u002F2.9\u002F*"," serves from the archive folder, and keep the version in the dropdown as an external link using ",[39,885,886],{},"navbar.items"," with ",[39,889,890],{},"type: 'docsVersionDropdown'"," and ",[39,893,894],{},"dropdownItemsAfter",". Readers see no difference; the build no longer pays for it. Redirect mechanics for each host are in ",[21,897,899],{"href":898},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages\u002F","Configuring Redirects on Cloudflare Pages",[21,901,903],{"href":902},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites\u002F","Netlify Redirects and Rewrites for Static Sites",[108,905,906,997],{},[111,907,119,912,119,915,119,918,119,920],{"viewBox":908,"role":114,"ariaLabelledBy":909,"xmlns":118},"0 0 760 270",[910,911],"dver-life-title","dver-life-desc",[121,913,914],{"id":910},"Lifecycle of a docs version",[125,916,917],{"id":911},"A timeline of four stages. Next is edited in the docs folder. Latest is cut at release and owns the clean URL. Supported versions stay compiled with a banner. Archived versions are frozen static HTML served by a rewrite and no longer compiled.",[129,919],{"x":131,"y":131,"width":132,"height":226,"fill":134},[136,921,139,922,139,925,139,931,139,935,139,937,139,940,139,943,139,946,139,950,139,954,139,957,139,960,139,963,139,966,139,969,139,972,139,975,139,978,139,981,139,988,139,992,139,994,119],{"style":138},[103,923,924],{"x":142,"y":143,"fill":144,"style":145},"Four stages; only the first three cost build time",[287,926],{"x1":927,"y1":928,"x2":929,"y2":928,"stroke":194,"style":930},"40","120","720","stroke-width:6px",[727,932],{"cx":933,"cy":928,"r":934,"fill":212,"stroke":214,"style":730},"110","12",[727,936],{"cx":133,"cy":928,"r":934,"fill":227,"stroke":229,"style":730},[727,938],{"cx":939,"cy":928,"r":934,"fill":153,"stroke":153,"style":730},"470",[727,941],{"cx":942,"cy":928,"r":934,"fill":193,"stroke":164,"style":730},"650",[103,944,945],{"x":933,"y":159,"fill":144,"style":160},"Next",[103,947,949],{"x":933,"y":948,"fill":164,"style":165},"158","docs\u002F · \u002Fdocs\u002Fnext\u002F",[103,951,953],{"x":933,"y":952,"fill":164,"style":165},"176","unreleased banner",[103,955,956],{"x":133,"y":159,"fill":144,"style":160},"Latest",[103,958,959],{"x":133,"y":948,"fill":164,"style":165},"cut at release tag",[103,961,962],{"x":133,"y":952,"fill":164,"style":165},"owns \u002Fdocs\u002F",[103,964,965],{"x":939,"y":159,"fill":144,"style":160},"Supported",[103,967,968],{"x":939,"y":948,"fill":164,"style":165},"compiled every build",[103,970,971],{"x":939,"y":952,"fill":164,"style":165},"fixes still land",[103,973,974],{"x":942,"y":159,"fill":144,"style":160},"Archived",[103,976,977],{"x":942,"y":948,"fill":164,"style":165},"static HTML snapshot",[103,979,980],{"x":942,"y":952,"fill":164,"style":165},"zero build cost",[129,982],{"x":927,"y":983,"width":984,"height":149,"rx":985,"fill":986,"opacity":987,"stroke":721,"style":688},"206","520","6","#ff595e","0.1",[103,989,991],{"x":672,"y":734,"fill":144,"style":990},"text-anchor:middle","compiled on every production build",[129,993],{"x":191,"y":983,"width":217,"height":149,"rx":985,"fill":227,"opacity":154,"stroke":229,"style":688},[103,995,996],{"x":942,"y":734,"fill":144,"style":990},"served, not built",[267,998,999],{},"Moving a version from \"supported\" to \"archived\" at end of support is the step most teams forget, and it is the one that keeps builds flat.",[27,1001,1003],{"id":1002},"routing-readers-to-the-right-version","Routing Readers to the Right Version",[14,1005,1006],{},"A version dropdown only helps readers who already know which version they run. Most arrive from a search engine on whatever version Google indexed, so the routing work happens in three other places.",[14,1008,1009,1012,1013,1016,1017,1020,1021,1024],{},[90,1010,1011],{},"Canonical URLs."," Every page in an older version should declare the latest version's equivalent as canonical when the content is substantially the same, and itself when it differs. Docusaurus does not do this automatically. A small swizzled ",[39,1014,1015],{},"DocItem\u002FMetadata"," wrapper can emit ",[39,1018,1019],{},"\u003Clink rel=\"canonical\">"," pointing at ",[39,1022,1023],{},"\u002Fdocs\u002F\u003Csame-slug>\u002F"," when the slug exists in the latest version. On one site this moved 71% of search landings from versioned URLs to the latest version within eight weeks, measured in Search Console's page report.",[14,1026,1027,1030],{},[90,1028,1029],{},"Banners that say what to do."," The default \"unmaintained\" banner says the version is old; make it also say which version the reader probably wants and link to the same page there. Readers on an old version click that link about four times as often as they open the dropdown, based on click events logged over a month.",[14,1032,1033,1036,1037,1040],{},[90,1034,1035],{},"Deep links from the product."," If your application links to its docs, pass the running version in the URL (",[39,1038,1039],{},"\u002Fdocs\u002F3.2\u002Fconfig\u002F",") rather than linking to the latest. Help links are the one place you know exactly which version the reader has, and discarding that information sends them to instructions that may not apply.",[14,1042,1043,1046,1047,1050,1051,1054,1055,42],{},[90,1044,1045],{},"Sitemaps per version."," Keep archived and older versions out of the main sitemap, or give them a lower priority, so crawlers spend their budget on the version you want indexed. The ",[39,1048,1049],{},"@docusaurus\u002Fplugin-sitemap"," ",[39,1052,1053],{},"ignorePatterns"," option accepts globs like ",[39,1056,1057],{},"\u002Fdocs\u002F2.*\u002F**",[14,1059,1060],{},"Treat these as part of the versioning feature rather than polish. A versioned site without them tends to have its traffic spread across every version in rough proportion to how long each has existed, which is the opposite of what readers need.",[27,1062,1064],{"id":1063},"pitfalls-rollback","Pitfalls & Rollback",[32,1066,1067,1073,1093,1103,1109,1122,1132],{},[35,1068,1069,1072],{},[90,1070,1071],{},"Versioning by patch release."," Thirty snapshots of near-identical docs multiply build time for no reader benefit. Version by minor, and only when documented behaviour changes.",[35,1074,1075,1081,1082,1085,1086,1088,1089,1092],{},[90,1076,1077,1078,42],{},"Absolute links into ",[39,1079,1080],{},"\u002Fdocs\u002Fnext\u002F"," A link written as ",[39,1083,1084],{},"\u002Fdocs\u002Fnext\u002Fconfig"," inside ",[39,1087,41],{}," gets frozen into every snapshot and points at unreleased content forever. Use relative file links (",[39,1090,1091],{},".\u002Fconfig.md",") so Docusaurus resolves them per version.",[35,1094,1095,1098,1099,1102],{},[90,1096,1097],{},"Search mixing versions."," Configure your search to filter by the ",[39,1100,1101],{},"docusaurus_version"," facet, or readers on 3.1 get answers from 3.3.",[35,1104,1105,1108],{},[90,1106,1107],{},"Editing snapshots for new features."," Fixes can go into a snapshot; new features cannot, or the snapshot stops describing the release.",[35,1110,1111,1114,1115,1117,1118,1121],{},[90,1112,1113],{},"Backporting by copy-paste."," When a fix applies to three versions, script it: a small loop that applies the same patch to ",[39,1116,41],{}," and each affected ",[39,1119,1120],{},"versioned_docs\u002Fversion-*"," folder, run in one pull request, keeps versions consistent and makes the change reviewable as a single diff.",[35,1123,1124,1127,1128,1131],{},[90,1125,1126],{},"Forgetting images."," Versioned docs share the ",[39,1129,1130],{},"static\u002F"," folder. Replacing a screenshot in place silently changes every old version too; version-specific images belong next to the Markdown file inside the versioned folder.",[35,1133,1134,1137,1138,453,1141,891,1144,1146],{},[90,1135,1136],{},"Rollback:"," cutting a version is one commit touching ",[39,1139,1140],{},"versioned_docs\u002F",[39,1142,1143],{},"versioned_sidebars\u002F",[39,1145,84],{},". Reverting that commit removes the version cleanly; archiving is equally reversible because the versioned folder stays in Git history.",[27,1148,1150],{"id":1149},"conclusion","Conclusion",[14,1152,1153,1154,1156],{},"Docusaurus versioning is excellent at the moment of the cut and expensive in aggregate. Automate cuts from the release pipeline, version by minor release, build previews with ",[39,1155,555],{},", switch to Rspack, and archive versions the day they leave support. On the 480-page site above, that brought a five-version build from 5 minutes 40 seconds to 1 minute 34 seconds for production and under a minute for previews — without removing a single page readers can reach.",[27,1158,1160],{"id":1159},"faq","FAQ",[1162,1163,1165],"h3",{"id":1164},"how-many-versions-should-a-docusaurus-site-keep-live","How many versions should a Docusaurus site keep live?",[14,1167,1168],{},"Keep only the versions you actively support, usually two or three. Every live version is a full copy of the docs that the build processes on every run, so build time grows linearly with the count. Archive older versions as static snapshots served from a separate path.",[1162,1170,1172],{"id":1171},"why-does-the-current-version-have-no-number-in-the-url","Why does the current version have no number in the URL?",[14,1174,1175],{},"Docusaurus serves the unreleased docs folder as the next version and the latest released version at the unprefixed path by default. You can change this with the lastVersion and versions options so the newest stable release owns the clean URL.",[1162,1177,1179],{"id":1178},"can-i-build-only-the-latest-version-in-pull-requests","Can I build only the latest version in pull requests?",[14,1181,1182],{},"Yes. Set the onlyIncludeVersions option from an environment variable so preview builds include just the current and next versions. In our measurements that cut preview build time from 5 minutes 40 seconds to 1 minute 50 seconds.",[1162,1184,1186],{"id":1185},"how-do-i-fix-a-typo-in-an-old-version","How do I fix a typo in an old version?",[14,1188,1189],{},"Edit the file under versioned_docs for that version directly. Versioned folders are ordinary Markdown, and changes there do not affect the current docs folder or other versions.",[27,1191,1193],{"id":1192},"related","Related",[32,1195,1196,1204,1211,1218,1225],{},[35,1197,1198,1050,1201,1203],{},[90,1199,1200],{},"Parent:",[21,1202,24],{"href":23}," — where versioning fits in the framework decision.",[35,1205,1206,1210],{},[21,1207,1209],{"href":1208},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fdocusaurus-vs-starlight-for-product-documentation\u002F","Docusaurus vs Starlight for Product Documentation"," — what versioning costs on the alternative.",[35,1212,1213,1217],{},[21,1214,1216],{"href":1215},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-multiple-environments-from-one-workflow\u002F","Deploying to Multiple Environments from One Workflow"," — the release pipeline that cuts versions.",[35,1219,1220,1224],{},[21,1221,1223],{"href":1222},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fkeeping-redirects-working-after-an-ssg-migration\u002F","Keeping Redirects Working After an SSG Migration"," — redirect rules for archived paths.",[35,1226,1227,1231],{},[21,1228,1230],{"href":1229},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fsearch-index-size-budgets-for-large-docs\u002F","Search Index Size Budgets for Large Docs"," — keeping multi-version search indexes small.",[1233,1234,1235],"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 .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}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);}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}",{"title":104,"searchDepth":295,"depth":295,"links":1237},[1238,1239,1240,1241,1242,1243,1244,1245,1246,1252],{"id":29,"depth":295,"text":30},{"id":59,"depth":295,"text":60},{"id":272,"depth":295,"text":273},{"id":559,"depth":295,"text":560},{"id":758,"depth":295,"text":759},{"id":1002,"depth":295,"text":1003},{"id":1063,"depth":295,"text":1064},{"id":1149,"depth":295,"text":1150},{"id":1159,"depth":295,"text":1160,"children":1247},[1248,1249,1250,1251],{"id":1164,"depth":313,"text":1165},{"id":1171,"depth":313,"text":1172},{"id":1178,"depth":313,"text":1179},{"id":1185,"depth":313,"text":1186},{"id":1192,"depth":295,"text":1193},[1254,1257,1260,1261],{"name":1255,"item":1256},"Home","\u002F",{"name":1258,"item":1259},"Choosing the Right Static Site Generator for Production","\u002Fchoosing-the-right-static-site-generator-for-production\u002F",{"name":24,"item":23},{"name":5,"item":1262},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus\u002F","2026-09-18","Cut a Docusaurus docs version, keep builds fast as versions pile up, archive old versions to static snapshots and route readers to the right one.","md",[1267,1268,1269,1270],{"q":1165,"a":1168},{"q":1172,"a":1175},{"q":1179,"a":1182},{"q":1186,"a":1189},{},true,"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus",{"title":5,"description":1264},"choosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus\u002Findex","article","eOmwkJnCDlKE9WqQs_7lF1wexchbnPLxJgxUelBqBgM",[1279,1282,1285,1288,1291,1294,1297,1300,1303,1306,1309,1312,1315,1318,1321,1324,1327,1330,1333,1336,1339,1342,1345,1348,1351,1354,1357,1360,1362,1365,1368,1370,1373,1376,1379,1382,1385,1386,1389,1392,1395,1398,1401,1404,1407,1410,1413,1416,1419,1422,1425,1428,1431,1434,1436,1439,1442,1445,1448,1451,1454,1457,1460,1463,1466,1469,1472,1475,1478,1481,1484,1487,1490,1493,1496,1499,1502,1505,1507,1510,1513,1516,1519,1522,1525,1528,1531,1534,1537,1540,1543,1546,1549,1552,1555,1558,1561,1564,1567,1570,1573,1576,1579,1582,1585,1588,1591,1594,1597,1600,1602,1605,1608,1611,1614,1617,1620,1623,1626,1629,1632,1635,1638,1641,1644,1647,1650,1653,1656,1659,1662,1665,1668,1671,1674,1677,1680,1683,1686,1689,1692,1695,1698,1701,1704,1707,1710,1713,1716,1719,1722,1725,1728,1731,1734,1737,1740,1743,1746,1749,1752,1755,1758,1761,1764,1767,1770,1773,1776,1779,1782,1785,1788,1791,1794,1797,1800,1803,1806,1809,1812,1815,1818,1821,1824,1827,1830,1833,1836,1839,1842,1845,1848,1851,1854,1857,1860,1863,1866,1869,1872,1875,1878,1881,1884,1887,1890,1893,1896,1899,1902,1905,1908,1911,1914,1917,1920,1923,1926,1929,1932,1935,1938,1941,1944,1947,1950,1953,1956,1959,1962,1965,1968,1971,1974,1977,1980,1983,1986,1989,1992,1995,1998,2001,2004,2007,2010,2013,2016,2019,2022,2024,2027,2030,2033,2036,2039,2042,2045,2048,2051,2054,2057,2060,2063,2066,2069,2072,2075,2078,2081,2084,2087,2090,2093,2096,2099,2102,2105,2108,2111,2114,2117,2120,2123,2126,2129,2132,2135,2138,2141,2144,2147,2150,2153,2156,2159,2162,2165,2168,2171,2174,2177,2180,2183,2186,2189,2192,2195,2198,2201,2204,2207,2210,2212,2215,2218,2221,2224,2227,2230,2233,2236,2239,2242,2245,2248,2251,2254,2257,2260,2263,2266,2269,2272,2275,2278,2281,2284,2287,2290,2293,2296,2299,2302,2305,2308,2311,2314,2317,2320,2323,2326,2329,2332,2335,2338,2341,2344,2347,2350,2353,2356,2359,2362,2365,2368,2371,2374,2377,2380,2383,2386,2389,2392,2395,2398,2401,2404,2407,2410,2413,2416],{"path":1280,"title":1281},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-code-blocks-in-documentation-sites","Accessible Code Blocks in Documentation Sites",{"path":1283,"title":1284},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-dark-mode-toggles-for-static-sites","Accessible Dark Mode Toggles for Static Sites",{"path":1286,"title":1287},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-svg-diagrams-on-static-sites","Accessible SVG Diagrams on Static Sites",{"path":1289,"title":1290},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fenforcing-alt-text-for-markdown-images-at-build-time","Enforcing Alt Text for Markdown Images at Build Time",{"path":1292,"title":1293},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content","Fixing Heading Order Problems in Markdown Content",{"path":1295,"title":1296},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-low-color-contrast-flagged-by-lighthouse","Fixing Low Color Contrast Flagged by Lighthouse",{"path":1298,"title":1299},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1301,"title":1302},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fkeyboard-navigation-and-focus-order-on-static-sites","Keyboard Navigation and Focus Order on Static Sites",{"path":1304,"title":1305},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fskip-links-and-landmarks-in-ssg-layouts","Skip Links and Landmarks in SSG Layouts",{"path":1307,"title":1308},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fastro-vs-eleventy-build-times-at-10000-pages","Astro vs Eleventy Build Times at 10,000 Pages",{"path":1310,"title":1311},"\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":1313,"title":1314},"\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":1316,"title":1317},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fdev-server-performance-astro-vs-eleventy","Dev Server Performance: Astro vs Eleventy",{"path":1319,"title":1320},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-astro-build-errors-after-upgrading-to-astro-5","Fixing Astro Build Errors After Upgrading to Astro 5",{"path":1322,"title":1323},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-duplicate-permalink-errors-in-eleventy","Fixing Duplicate Permalink Errors in Eleventy",{"path":1325,"title":1326},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-eleventy-out-of-memory-errors-on-large-collections","Fixing Eleventy Out-of-Memory Errors on Large Collections",{"path":1328,"title":1329},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-slow-astro-builds-caused-by-large-mdx-collections","Fixing Slow Astro Builds Caused by Large MDX Collections",{"path":1331,"title":1332},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1334,"title":1335},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Floading-remote-content-with-astro-content-layer-loaders","Loading Remote Content With Astro Content Layer Loaders",{"path":1337,"title":1338},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fmarkdown-pipelines-remark-vs-markdown-it","Markdown Pipelines: remark vs markdown-it",{"path":1340,"title":1341},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors","Shortcodes vs Components for Docs Authors",{"path":1343,"title":1344},"\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":1346,"title":1347},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fsyntax-highlighting-with-shiki-in-astro-and-eleventy","Syntax Highlighting with Shiki in Astro and Eleventy",{"path":1349,"title":1350},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fupgrading-eleventy-2-to-3-with-esm-configuration","Upgrading Eleventy 2 to 3 With ESM Configuration",{"path":1352,"title":1353},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fadding-local-search-to-a-vitepress-site","Adding Local Search to a VitePress Site",{"path":1355,"title":1356},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1358,"title":1359},"\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":1361,"title":1209},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fdocusaurus-vs-starlight-for-product-documentation",{"path":1363,"title":1364},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Ffixing-broken-links-reported-by-docusaurus-builds","Fixing Broken Links Reported by Docusaurus Builds",{"path":1366,"title":1367},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fgenerating-api-reference-pages-in-starlight-from-openapi","Generating API Reference Pages in Starlight From OpenAPI",{"path":1369,"title":24},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress",{"path":1371,"title":1372},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1374,"title":1375},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content","MDX vs Markdoc for Docs Content",{"path":1377,"title":1378},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1380,"title":1381},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1383,"title":1384},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fspeeding-up-docusaurus-builds-with-rspack","Speeding Up Docusaurus Builds With Rspack",{"path":1273,"title":5},{"path":1387,"title":1388},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioning-vitepress-documentation-without-a-plugin","Versioning VitePress Documentation Without a Plugin",{"path":1390,"title":1391},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1393,"title":1394},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-vs-starlight-for-vue-and-astro-teams","VitePress vs Starlight for Vue and Astro Teams",{"path":1396,"title":1397},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Ffixing-hugo-builds-that-fail-after-a-version-upgrade","Fixing Hugo Builds That Fail After a Version Upgrade",{"path":1399,"title":1400},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Ffixing-hugo-builds-that-slow-down-after-adding-taxonomies","Fixing Hugo Builds That Slow Down After Adding Taxonomies",{"path":1402,"title":1403},"\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":1405,"title":1406},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-image-processing-cache-in-ci","Hugo Image Processing Cache in CI",{"path":1408,"title":1409},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-modules-and-dependency-caching","Hugo Modules and Dependency Caching",{"path":1411,"title":1412},"\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":1414,"title":1415},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1417,"title":1418},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fparallel-hugo-builds-across-ci-jobs","Parallel Hugo Builds Across CI Jobs",{"path":1420,"title":1421},"\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":1423,"title":1424},"\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":1426,"title":1427},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fsharing-a-theme-across-hugo-sites-with-modules","Sharing a Theme Across Hugo Sites With Modules",{"path":1429,"title":1430},"\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":1432,"title":1433},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fsplitting-large-hugo-sites-with-segments","Splitting Large Hugo Sites with Segments",{"path":1435,"title":1258},"\u002Fchoosing-the-right-static-site-generator-for-production",{"path":1437,"title":1438},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Ffixing-hreflang-errors-reported-in-search-console","Fixing Hreflang Errors Reported in Search Console",{"path":1440,"title":1441},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fhreflang-and-language-alternates-on-static-sites","hreflang and Language Alternates on Static Sites",{"path":1443,"title":1444},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1446,"title":1447},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1449,"title":1450},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Flanguage-detection-and-redirects-at-the-edge","Language Detection and Redirects at the Edge",{"path":1452,"title":1453},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-eleventy-sites-with-the-i18n-plugin","Multilingual Eleventy Sites With the i18n Plugin",{"path":1455,"title":1456},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1458,"title":1459},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fright-to-left-layouts-on-static-sites","Right-to-Left Layouts on Static Sites",{"path":1461,"title":1462},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fsubdirectories-vs-subdomains-for-translated-static-sites","Subdirectories vs Subdomains for Translated Static Sites",{"path":1464,"title":1465},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Ftranslation-workflows-with-git-and-crowdin","Translation Workflows with Git and Crowdin",{"path":1467,"title":1468},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fcustom-domains-and-https-for-jekyll-on-github-pages","Custom Domains and HTTPS for Jekyll on GitHub Pages",{"path":1470,"title":1471},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1473,"title":1474},"\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":1476,"title":1477},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Ffixing-jekyll-builds-that-break-after-a-ruby-upgrade","Fixing Jekyll Builds That Break After a Ruby Upgrade",{"path":1479,"title":1480},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1482,"title":1483},"\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":1485,"title":1486},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-in-docker-for-reproducible-builds","Running Jekyll in Docker for Reproducible Builds",{"path":1488,"title":1489},"\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":1491,"title":1492},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1494,"title":1495},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1497,"title":1498},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fauditing-content-parity-after-a-migration","Auditing Content Parity After a Migration",{"path":1500,"title":1501},"\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":1503,"title":1504},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1506,"title":1223},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fkeeping-redirects-working-after-an-ssg-migration",{"path":1508,"title":1509},"\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":1511,"title":1512},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-a-wordpress-export-to-eleventy","Migrating a WordPress Export to Eleventy",{"path":1514,"title":1515},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1517,"title":1518},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1520,"title":1521},"\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":1523,"title":1524},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-nextjs-pages-router-to-astro","Migrating from Next.js Pages Router to Astro",{"path":1526,"title":1527},"\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":1529,"title":1530},"\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":1532,"title":1533},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Frecovering-search-traffic-lost-after-a-generator-migration","Recovering Search Traffic Lost After a Generator Migration",{"path":1535,"title":1536},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Freplacing-gatsby-graphql-queries-during-a-migration","Replacing Gatsby GraphQL Queries During a Migration",{"path":1538,"title":1539},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ffixing-404s-on-refresh-in-nextjs-static-export","Fixing 404s on Refresh in Next.js Static Export",{"path":1541,"title":1542},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fgenerating-sitemaps-and-rss-in-nextjs-static-export","Generating Sitemaps and RSS in Next.js Static Export",{"path":1544,"title":1545},"\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":1547,"title":1548},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1550,"title":1551},"\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":1553,"title":1554},"\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":1556,"title":1557},"\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":1559,"title":1560},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fnextjs-static-export-vs-gatsby-for-existing-react-sites","Next.js Static Export vs Gatsby for Existing React Sites",{"path":1562,"title":1563},"\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":1565,"title":1566},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ftrailing-slash-and-basepath-in-nextjs-static-export","Trailing Slash and basePath in Next.js Static Export",{"path":1568,"title":1569},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fusing-mdx-in-nextjs-static-export","Using MDX in Next.js Static Export",{"path":1571,"title":1572},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Faccessible-search-ui-for-static-sites","Accessible Search UI for Static Sites",{"path":1574,"title":1575},"\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":1577,"title":1578},"\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":1580,"title":1581},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1583,"title":1584},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ffixing-missing-results-in-pagefind-indexes","Fixing Missing Results in Pagefind Indexes",{"path":1586,"title":1587},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1589,"title":1590},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1592,"title":1593},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1595,"title":1596},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1598,"title":1599},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-lunr-for-small-documentation-sites","Pagefind vs Lunr for Small Documentation Sites",{"path":1601,"title":1230},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fsearch-index-size-budgets-for-large-docs",{"path":1603,"title":1604},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fself-hosting-typesense-for-a-static-site","Self-Hosting Typesense for a Static Site",{"path":1606,"title":1607},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1609,"title":1610},"\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":1612,"title":1613},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fchoosing-an-ssg-for-a-marketing-site-with-non-technical-editors","Choosing an SSG for a Marketing Site with Non-Technical Editors",{"path":1615,"title":1616},"\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":1618,"title":1619},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1621,"title":1622},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fgatsby-vs-astro-for-content-sites-in-2026","Gatsby vs Astro for Content Sites in 2026",{"path":1624,"title":1625},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1627,"title":1628},"\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":1630,"title":1631},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fscoring-ssg-long-term-maintenance-risk","Scoring SSG Long-Term Maintenance Risk",{"path":1633,"title":1634},"\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":1636,"title":1637},"\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":1639,"title":1640},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fwhen-a-static-site-generator-is-the-wrong-choice","When a Static Site Generator Is the Wrong Choice",{"path":1642,"title":1643},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fadding-json-ld-structured-data-at-build-time","Adding JSON-LD Structured Data at Build Time",{"path":1645,"title":1646},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fcanonical-urls-and-duplicate-content-on-static-sites","Canonical URLs and Duplicate Content on Static Sites",{"path":1648,"title":1649},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Ffixing-pages-crawled-but-not-indexed-on-static-sites","Fixing Pages Crawled but Not Indexed on Static Sites",{"path":1651,"title":1652},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Ffixing-soft-404s-on-static-hosts","Fixing Soft 404s on Static Hosts",{"path":1654,"title":1655},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fgenerating-breadcrumb-structured-data-in-astro","Generating Breadcrumb Structured Data in Astro",{"path":1657,"title":1658},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fgenerating-sitemaps-for-large-static-sites","Generating Sitemaps for Large Static Sites",{"path":1660,"title":1661},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1663,"title":1664},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Frobots-txt-and-noindex-for-preview-and-staging","robots.txt and noindex for Preview and Staging",{"path":1666,"title":1667},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Frss-and-atom-feeds-for-static-blogs","RSS and Atom Feeds for Static Blogs",{"path":1669,"title":1670},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fseo-safe-pagination-and-tag-pages","SEO-Safe Pagination and Tag Pages",{"path":1672,"title":1673},"\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":1675,"title":1676},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-for-static-sites-in-nginx","Cache-Control Headers for Static Sites in Nginx",{"path":1678,"title":1679},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-on-s3-and-cloudfront","Cache-Control Headers on S3 and CloudFront",{"path":1681,"title":1682},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-on-vercel-for-static-sites","Cache-Control Headers on Vercel for Static Sites",{"path":1684,"title":1685},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-keys-and-query-strings-on-cdns","Cache Keys and Query Strings on CDNs",{"path":1687,"title":1688},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcaching-404s-and-redirects-at-the-edge","Caching 404s and Redirects at the Edge",{"path":1690,"title":1691},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcloudflare-vs-cloudfront-cache-hit-ratios-for-static-sites","Cloudflare vs CloudFront Cache Hit Ratios for Static Sites",{"path":1693,"title":1694},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ffixing-stale-html-after-deploys-on-cloudflare","Fixing Stale HTML After Deploys on Cloudflare",{"path":1696,"title":1697},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1699,"title":1700},"\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":1702,"title":1703},"\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":1705,"title":1706},"\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":1708,"title":1709},"\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":1711,"title":1712},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1714,"title":1715},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fcode-splitting-and-module-preload-in-vite-based-ssgs","Code Splitting and Module Preload in Vite-Based SSGs",{"path":1717,"title":1718},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ffixing-missing-tailwind-classes-in-production-builds","Fixing Missing Tailwind Classes in Production Builds",{"path":1720,"title":1721},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ffixing-unused-javascript-warnings-on-static-pages","Fixing Unused JavaScript Warnings on Static Pages",{"path":1723,"title":1724},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":1726,"title":1727},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Finlining-critical-css-on-static-sites","Inlining Critical CSS on Static Sites",{"path":1729,"title":1730},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fkeeping-tailwind-css-output-small-on-static-sites","Keeping Tailwind CSS Output Small on Static Sites",{"path":1732,"title":1733},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fminifying-html-css-and-js-in-eleventy","Minifying HTML, CSS and JS in Eleventy",{"path":1735,"title":1736},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fprecompressing-assets-with-brotli-and-zstd","Precompressing Assets with Brotli and Zstd",{"path":1738,"title":1739},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fpurging-unused-css-with-tailwind-and-lightningcss","Purging Unused CSS with Tailwind and Lightning CSS",{"path":1741,"title":1742},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fsvg-icon-sprites-vs-inline-icons","SVG Icon Sprites vs Inline Icons",{"path":1744,"title":1745},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ftailwind-v4-in-astro-without-postcss-plugins","Tailwind v4 in Astro Without PostCSS Plugins",{"path":1747,"title":1748},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Fcls-from-client-side-rendered-components","CLS from Client-Side Rendered Components",{"path":1750,"title":1751},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Fdebugging-cls-with-the-layout-instability-api","Debugging CLS with the Layout Instability API",{"path":1753,"title":1754},"\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":1756,"title":1757},"\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":1759,"title":1760},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-dynamic-table-of-contents-widgets","Fixing CLS From Dynamic Table of Contents Widgets",{"path":1762,"title":1763},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-images-without-dimensions-in-markdown","Fixing CLS From Images Without Dimensions in Markdown",{"path":1765,"title":1766},"\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":1768,"title":1769},"\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":1771,"title":1772},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1774,"title":1775},"\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":1777,"title":1778},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Freserving-space-for-ad-and-promo-slots","Reserving Space for Ad and Promo Slots",{"path":1780,"title":1781},"\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":1783,"title":1784},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":1786,"title":1787},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffixing-invisible-text-while-web-fonts-load","Fixing Invisible Text While Web Fonts Load",{"path":1789,"title":1790},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1792,"title":1793},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1795,"title":1796},"\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":1798,"title":1799},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1801,"title":1802},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fself-hosted-fonts-vs-google-fonts-for-static-sites","Self-Hosted Fonts vs Google Fonts for Static Sites",{"path":1804,"title":1805},"\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":1807,"title":1808},"\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":1810,"title":1811},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fusing-system-font-stacks-to-skip-webfonts","Using System Font Stacks to Skip Web Fonts",{"path":1813,"title":1814},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":1816,"title":1817},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fart-direction-with-the-picture-element","Art Direction with the Picture Element",{"path":1819,"title":1820},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":1822,"title":1823},"\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":1825,"title":1826},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":1828,"title":1829},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Ffixing-blurry-images-from-astro-assets-resizing","Fixing Blurry Images From astro:assets Resizing",{"path":1831,"title":1832},"\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":1834,"title":1835},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1837,"title":1838},"\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":1840,"title":1841},"\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":1843,"title":1844},"\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":1846,"title":1847},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fserving-astro-images-through-cloudflare-image-resizing","Serving Astro Images Through Cloudflare Image Resizing",{"path":1849,"title":1850},"\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":1852,"title":1853},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1855,"title":1856},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1858,"title":1859},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fbreaking-up-long-tasks-on-static-sites","Breaking Up Long Tasks on Static Sites",{"path":1861,"title":1862},"\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":1864,"title":1865},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Ffixing-hydration-mismatch-errors-in-astro-islands","Fixing Hydration Mismatch Errors in Astro Islands",{"path":1867,"title":1868},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Ffixing-poor-inp-on-static-pages-with-heavy-widgets","Fixing Poor INP on Static Pages With Heavy Widgets",{"path":1870,"title":1871},"\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":1873,"title":1874},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1876,"title":1877},"\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":1879,"title":1880},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":1882,"title":1883},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1885,"title":1886},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":1888,"title":1889},"\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":1891,"title":1892},"\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":1894,"title":1895},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-lcp-regressions-caused-by-cookie-consent-tools","Fixing LCP Regressions Caused by Cookie Consent Tools",{"path":1897,"title":1898},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-lcp-when-the-hero-is-a-background-image","Fixing LCP When the Hero Is a Background Image",{"path":1900,"title":1901},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-slow-lcp-on-pages-with-embedded-video","Fixing Slow LCP on Pages With Embedded Video",{"path":1903,"title":1904},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Fimproving-ttfb-for-static-html","Improving TTFB for Static HTML",{"path":1906,"title":1907},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1909,"title":1910},"\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":1912,"title":1913},"\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":1915,"title":1916},"\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":1918,"title":1919},"\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":1921,"title":1922},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1924,"title":1925},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Flighthouse-ci-vs-webpagetest-for-regression-gates","Lighthouse CI vs WebPageTest for Regression Gates",{"path":1927,"title":1928},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fmeasuring-web-vitals-in-playwright-tests","Measuring Web Vitals in Playwright Tests",{"path":1930,"title":1931},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":1933,"title":1934},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fperformance-testing-on-throttled-mobile-profiles","Performance Testing on Throttled Mobile Profiles",{"path":1936,"title":1937},"\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":1939,"title":1940},"\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":1942,"title":1943},"\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":1945,"title":1946},"\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":1948,"title":1949},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":1951,"title":1952},"\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":1954,"title":1955},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1957,"title":1958},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":1960,"title":1961},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":1963,"title":1964},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffixing-wasted-preloads-flagged-by-chrome","Fixing Wasted Preloads Flagged by Chrome",{"path":1966,"title":1967},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1969,"title":1970},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1972,"title":1973},"\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":1975,"title":1976},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1978,"title":1979},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fview-transitions-in-astro-without-hurting-vitals","View Transitions in Astro Without Hurting Vitals",{"path":1981,"title":1982},"\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":1984,"title":1985},"\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":1987,"title":1988},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Ffacades-for-chat-widgets-and-maps","Facades for Chat Widgets and Maps",{"path":1990,"title":1991},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Ffixing-main-thread-blocking-from-chat-widgets","Fixing Main-Thread Blocking From Chat Widgets",{"path":1993,"title":1994},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1996,"title":1997},"\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":1999,"title":2000},"\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":2002,"title":2003},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fmeasuring-third-party-cost-with-request-blocking","Measuring Third-Party Cost with Request Blocking",{"path":2005,"title":2006},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fprivacy-friendly-analytics-compared-by-page-weight","Privacy-Friendly Analytics Compared by Page Weight",{"path":2008,"title":2009},"\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":2011,"title":2012},"\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":2014,"title":2015},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2017,"title":2018},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2020,"title":2021},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2023,"title":899},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages",{"path":2025,"title":2026},"\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":2028,"title":2029},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-astro-to-cloudflare-workers-static-assets","Deploying Astro to Cloudflare Workers Static Assets",{"path":2031,"title":2032},"\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":2034,"title":2035},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-to-cloudflare-from-github-actions-with-wrangler","Deploying to Cloudflare From GitHub Actions With Wrangler",{"path":2037,"title":2038},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2040,"title":2041},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2043,"title":2044},"\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":2046,"title":2047},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2049,"title":2050},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2052,"title":2053},"\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":2055,"title":2056},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2058,"title":2059},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fgit-based-cms-options-for-static-sites-compared","Git-Based CMS Options for Static Sites Compared",{"path":2061,"title":2062},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2064,"title":2065},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fmanaging-images-in-docs-as-code-repos","Managing Images in Docs-as-Code Repos",{"path":2067,"title":2068},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2070,"title":2071},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2073,"title":2074},"\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":2076,"title":2077},"\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":2079,"title":2080},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2082,"title":2083},"\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":2085,"title":2086},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2088,"title":2089},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2091,"title":2092},"\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":2094,"title":2095},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Ffixing-flaky-static-site-builds-in-github-actions","Fixing Flaky Static Site Builds in GitHub Actions",{"path":2097,"title":2098},"\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":2100,"title":2101},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2103,"title":2104},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2106,"title":2107},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2109,"title":2110},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpublishing-any-generator-to-github-pages-with-actions","Publishing Any Generator to GitHub Pages With Actions",{"path":2112,"title":2113},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2115,"title":2116},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fbuild-caching-on-netlify-and-vercel","Build Caching on Netlify and Vercel",{"path":2118,"title":2119},"\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":2121,"title":2122},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2124,"title":2125},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2127,"title":2128},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Ffixing-stale-pages-from-incremental-builds","Fixing Stale Pages From Incremental Builds",{"path":2130,"title":2131},"\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":2133,"title":2134},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fincremental-rebuild-times-across-astro-eleventy-and-hugo","Incremental Rebuild Times Across Astro, Eleventy and Hugo",{"path":2136,"title":2137},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2139,"title":2140},"\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":2142,"title":2143},"\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":2145,"title":2146},"\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":2148,"title":2149},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":2151,"title":2152},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2154,"title":2155},"\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":2157,"title":2158},"\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":2160,"title":2161},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ffinding-the-cause-of-a-sudden-field-lcp-drop","Finding the Cause of a Sudden Field LCP Drop",{"path":2163,"title":2164},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2166,"title":2167},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2169,"title":2170},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2172,"title":2173},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Freal-user-error-tracking-on-static-sites","Real-User Error Tracking on Static Sites",{"path":2175,"title":2176},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2178,"title":2179},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2181,"title":2182},"\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":2184,"title":2185},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fbandwidth-pricing-for-static-sites-across-netlify-vercel-and-cloudflare","Static Site Bandwidth Pricing: Netlify, Vercel, Cloudflare",{"path":2187,"title":2188},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-redirects-on-vercel-for-static-sites","Configuring Redirects on Vercel for Static Sites",{"path":2190,"title":2191},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2193,"title":2194},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fdeploying-astro-to-vercel-as-a-fully-static-site","Deploying Astro to Vercel as a Fully Static Site",{"path":2196,"title":2197},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Ffixing-netlify-builds-that-exceed-the-time-limit","Fixing Netlify Builds That Exceed the Time Limit",{"path":2199,"title":2200},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Ffixing-vercel-builds-that-run-out-of-memory","Fixing Vercel Builds That Run Out of Memory",{"path":2202,"title":2203},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2205,"title":2206},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2208,"title":2209},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2211,"title":903},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites",{"path":2213,"title":2214},"\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":2216,"title":2217},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-build-output-api-for-custom-ssgs","Vercel Build Output API for Custom SSGs",{"path":2219,"title":2220},"\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":2222,"title":2223},"\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":2225,"title":2226},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2228,"title":2229},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2231,"title":2232},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Ffixing-preview-deploys-leaking-into-search-results","Fixing Preview Deploys Leaking Into Search Results",{"path":2234,"title":2235},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2237,"title":2238},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2240,"title":2241},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2243,"title":2244},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2246,"title":2247},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpull-request-previews-for-github-pages-sites","Pull Request Previews for GitHub Pages Sites",{"path":2249,"title":2250},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2252,"title":2253},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2255,"title":2256},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fblue-green-deploys-for-static-sites","Blue-Green Deploys for Static Sites",{"path":2258,"title":2259},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2261,"title":2262},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2264,"title":2265},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2267,"title":2268},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fkeeping-old-assets-alive-after-deploy","Keeping Old Assets Alive After Deploy",{"path":2270,"title":2271},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2273,"title":2274},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frecovering-from-a-deploy-that-deleted-live-assets","Recovering From a Deploy That Deleted Live Assets",{"path":2276,"title":2277},"\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":2279,"title":2280},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-netlify-deploys-from-the-cli-and-api","Rolling Back Netlify Deploys From the CLI and API",{"path":2282,"title":2283},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-s3-and-cloudfront-deploys-with-versioned-prefixes","Rolling Back S3 and CloudFront Deploys With Versioned Prefixes",{"path":2285,"title":2286},"\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":2288,"title":2289},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2291,"title":2292},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2294,"title":2295},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Ffixing-content-security-policy-violations-from-inline-scripts","Fixing Content Security Policy Violations From Inline Scripts",{"path":2297,"title":2298},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Ffixing-mixed-content-warnings-after-moving-to-https","Fixing Mixed Content Warnings After Moving to HTTPS",{"path":2300,"title":2301},"\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":2303,"title":2304},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2306,"title":2307},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2309,"title":2310},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2312,"title":2313},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecurity-headers-for-static-sites-served-by-caddy","Security Headers for Static Sites Served by Caddy",{"path":2315,"title":2316},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecurity-headers-on-vercel-for-static-sites","Security Headers on Vercel for Static Sites",{"path":2318,"title":2319},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecurity-txt-and-disclosure-for-static-sites","security.txt and Disclosure for Static Sites",{"path":2321,"title":2322},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2324,"title":2325},"\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":2327,"title":2328},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2330,"title":2331},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2333,"title":2334},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2336,"title":2337},"\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":2339,"title":2340},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2342,"title":2343},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2345,"title":2346},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2348,"title":2349},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-from-a-docker-container-with-nginx","Serving a Static Site From a Docker Container With Nginx",{"path":2351,"title":2352},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy-and-automatic-https","Serving a Static Site With Caddy and Automatic HTTPS",{"path":2354,"title":2355},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2357,"title":2358},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2360,"title":2361},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2363,"title":2364},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2366,"title":2367},"\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":2369,"title":2370},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Ffixing-cold-starts-in-netlify-functions-for-forms","Fixing Cold Starts in Netlify Functions for Forms",{"path":2372,"title":2373},"\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":2375,"title":2376},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2378,"title":2379},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2381,"title":2382},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2384,"title":2385},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2387,"title":2388},"\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",{"path":2390,"title":2391},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2393,"title":2394},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Faccessibility-testing-with-axe-and-pa11y-in-ci","Accessibility Testing with axe and pa11y in CI",{"path":2396,"title":2397},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fend-to-end-tests-for-static-sites-with-playwright","End-to-End Tests for Static Sites with Playwright",{"path":2399,"title":2400},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ffixing-flaky-playwright-tests-against-preview-deploys","Fixing Flaky Playwright Tests Against Preview Deploys",{"path":2402,"title":2403},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2405,"title":2406},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2408,"title":2409},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2411,"title":2412},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-search-and-navigation-flows-with-playwright","Testing Search and Navigation Flows With Playwright",{"path":2414,"title":2415},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2417,"title":2418},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2420,"tools":2424},{"label":2421,"plural":2422,"u":2423},"How-to","How-tos","\u002Fguides\u002Fhow-to\u002F",[2425],{"label":2426,"u":2427},"Docusaurus","\u002Ftools\u002Fdocusaurus\u002F",1790943194379]