[{"data":1,"prerenderedAt":2489},["ShallowReactive",2],{"page:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ffixing-404s-on-refresh-in-nextjs-static-export":3,"all-docs-nav":1339,"filed:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ffixing-404s-on-refresh-in-nextjs-static-export":2480},{"id":4,"title":5,"body":6,"breadcrumb":1314,"dateModified":1324,"datePublished":1324,"description":1325,"extension":1326,"faq":1327,"meta":1332,"navigation":1333,"path":1334,"seo":1335,"slug":12,"stem":1336,"type":1337,"__hash__":1338},"content\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ffixing-404s-on-refresh-in-nextjs-static-export\u002Findex.md","Fixing 404s on Refresh in Next.js Static Export",{"type":7,"value":8,"toc":1293},"minimark",[9,13,17,36,41,183,212,216,251,258,262,269,309,323,335,450,454,464,490,497,624,628,639,730,740,744,763,767,770,887,890,986,990,1009,1020,1024,1045,1049,1145,1149,1202,1206,1216,1220,1225,1228,1232,1235,1239,1242,1246,1249,1253,1289],[10,11,5],"h1",{"id":12},"fixing-404s-on-refresh-in-nextjs-static-export",[14,15,16],"p",{},"The symptom is unmistakable: every page on a Next.js static export works when you click through to it from the home page, and then returns 404 when you press refresh, open it in a new tab, or follow a link from another site. Search engines see the 404s too. The cause is that client-side navigation never asks the host for the page's HTML file; a refresh does. If the exported file is not where the host looks for it, the host has nothing to serve.",[14,18,19,20,24,25,30,31,35],{},"This guide fixes the problem on a Next.js 15 App Router site exported with ",[21,22,23],"code",{},"output: 'export'"," and deployed in three places during a hosting change — an S3 bucket behind CloudFront, an Nginx server, and Cloudflare — because the fix depends on the host. It belongs to ",[26,27,29],"a",{"href":28},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002F","Next.js Static Export for Content Sites",", and complements ",[26,32,34],{"href":33},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ftrailing-slash-and-basepath-in-nextjs-static-export\u002F","Trailing Slash and basePath in Next.js Static Export",".",[37,38,40],"h2",{"id":39},"why-it-works-on-click-and-fails-on-refresh","Why It Works on Click and Fails on Refresh",[42,43,44,179],"figure",{},[45,46,53,54,53,58,53,62,53,69,53,164],"svg",{"viewBox":47,"role":48,"ariaLabelledBy":49,"xmlns":52},"0 0 760 298","img",[50,51],"nx404-seq-title","nx404-seq-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[55,56,57],"title",{"id":50},"Client-side navigation compared with a direct load of the same URL",[59,60,61],"desc",{"id":51},"Three actors, the browser, the Next.js router in the page and the static host. On a click, the router intercepts the link, fetches the RSC payload file for docs install from the host, and renders without requesting HTML. On a refresh, the browser requests slash docs slash install from the host directly. The host looks for a file at that path, finds only docs slash install dot html, and returns 404.",[63,64],"rect",{"x":65,"y":65,"width":66,"height":67,"fill":68},"0","760","298","#ffffff",[70,71,73,74,73,84,73,87,73,90,73,97,73,100,73,104,73,107,73,110,73,114,73,117,73,120,73,128,73,134,73,137,73,141,73,147,73,152,73,156,73,160,53],"g",{"style":72},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[63,75],{"x":76,"y":77,"width":78,"height":79,"rx":80,"fill":81,"stroke":82,"style":83},"55.0","56.0","170.0","42.9","8","#f8fafc","#d9e2ef","stroke-width:1.5px",[63,85],{"x":86,"y":77,"width":78,"height":79,"rx":80,"fill":81,"stroke":82,"style":83},"295.0",[63,88],{"x":89,"y":77,"width":78,"height":79,"rx":80,"fill":81,"stroke":82,"style":83},"535.0",[91,92],"path",{"d":93,"fill":94,"stroke":95,"style":96},"M144.0 133.9 L374.0 133.9","none","#556071","stroke-width:1.8px;marker-end:url(#nx404-seq-arrow)",[91,98],{"d":99,"fill":94,"stroke":95,"style":96},"M384.0 166.8 L614.0 166.8",[91,101],{"d":102,"fill":94,"stroke":95,"style":103},"M616.0 199.8 L386.0 199.8","stroke-width:1.8px;stroke-dasharray:5 4;marker-end:url(#nx404-seq-arrow)",[91,105],{"d":106,"fill":94,"stroke":95,"style":96},"M144.0 232.7 L614.0 232.7",[91,108],{"d":109,"fill":94,"stroke":95,"style":103},"M616.0 265.6 L146.0 265.6",[91,111],{"d":112,"fill":94,"stroke":82,"style":113},"M140.0 100.9 L140.0 281.6","stroke-width:1.5px;stroke-dasharray:4 4",[91,115],{"d":116,"fill":94,"stroke":82,"style":113},"M380.0 100.9 L380.0 281.6",[91,118],{"d":119,"fill":94,"stroke":82,"style":113},"M620.0 100.9 L620.0 281.6",[121,122,127],"text",{"x":123,"y":124,"fill":125,"style":126},"380.0","30.0","#1f2937","font-size:16px;text-anchor:middle;font-weight:700","Two ways to reach \u002Fdocs\u002Finstall",[121,129,133],{"x":130,"y":131,"fill":125,"style":132},"140.0","82.7","font-size:13px;text-anchor:middle;font-weight:700","Browser",[121,135,136],{"x":123,"y":131,"fill":125,"style":132},"Next.js router",[121,138,140],{"x":139,"y":131,"fill":125,"style":132},"620.0","Static host",[121,142,146],{"x":143,"y":144,"fill":125,"style":145},"260.0","125.8","font-size:11.5px;text-anchor:middle","click \u003CLink href=\"\u002Fdocs\u002Finstall\">",[121,148,151],{"x":149,"y":150,"fill":125,"style":145},"500.0","158.8","GET \u002Fdocs\u002Finstall.txt (payload)",[121,153,155],{"x":149,"y":154,"fill":95,"style":145},"191.7","200",[121,157,159],{"x":123,"y":158,"fill":125,"style":145},"224.7","refresh: GET \u002Fdocs\u002Finstall",[121,161,163],{"x":123,"y":162,"fill":95,"style":145},"257.6","404: no file at that path",[165,166,73,167,53],"defs",{},[168,169,175,176,73],"marker",{"id":170,"viewBox":171,"refX":80,"refY":172,"markerWidth":173,"markerHeight":173,"orient":174},"nx404-seq-arrow","0 0 10 10","5","7","auto-start-reverse","\n      ",[91,177],{"d":178,"fill":95},"M0 0 L10 5 L0 10 z",[180,181,182],"figcaption",{},"The click path requests docs\u002Finstall.txt; the refresh path requests the HTML at a path the host must map to a file.",[14,184,185,186,189,190,192,193,196,197,200,201,204,205,200,208,211],{},"By default, ",[21,187,188],{},"next build"," with ",[21,191,23],{}," writes ",[21,194,195],{},"out\u002Fdocs\u002Finstall.html",". A host that maps ",[21,198,199],{},"\u002Fdocs\u002Finstall"," to ",[21,202,203],{},"docs\u002Finstall.html"," serves it. A host that only maps ",[21,206,207],{},"\u002Fdocs\u002Finstall\u002F",[21,209,210],{},"docs\u002Finstall\u002Findex.html"," — the convention of plain web servers and object stores — does not.",[37,213,215],{"id":214},"step-1-confirm-which-file-the-export-wrote","Step 1: Confirm Which File the Export Wrote",[217,218,223],"pre",{"className":219,"code":220,"language":221,"meta":222,"style":222},"language-sh shiki shiki-themes github-light github-dark","ls out\u002Fdocs\u002F | head\n# install.html  install.txt  configure.html  configure.txt\ncurl -sI https:\u002F\u002Fstaging.example.com\u002Fdocs\u002Finstall | head -1\ncurl -sI https:\u002F\u002Fstaging.example.com\u002Fdocs\u002Finstall.html | head -1\n","sh","",[21,224,225,233,239,245],{"__ignoreMap":222},[226,227,230],"span",{"class":228,"line":229},"line",1,[226,231,232],{},"ls out\u002Fdocs\u002F | head\n",[226,234,236],{"class":228,"line":235},2,[226,237,238],{},"# install.html  install.txt  configure.html  configure.txt\n",[226,240,242],{"class":228,"line":241},3,[226,243,244],{},"curl -sI https:\u002F\u002Fstaging.example.com\u002Fdocs\u002Finstall | head -1\n",[226,246,248],{"class":228,"line":247},4,[226,249,250],{},"curl -sI https:\u002F\u002Fstaging.example.com\u002Fdocs\u002Finstall.html | head -1\n",[14,252,253,254,257],{},"If the ",[21,255,256],{},".html"," URL returns 200 and the extensionless one 404, the host has no clean-URL mapping. If both 404, the page was not exported at all — see Cause 3.",[37,259,261],{"id":260},"cause-1-the-host-has-no-clean-urls-s3-plain-nginx","Cause 1: The Host Has No Clean URLs (S3, Plain Nginx)",[14,263,264,268],{},[265,266,267],"strong",{},"Fix:"," make the export write directory indexes, which every host understands:",[217,270,274],{"className":271,"code":272,"language":273,"meta":222,"style":222},"language-js shiki shiki-themes github-light github-dark","\u002F\u002F next.config.mjs\nexport default { output: 'export', trailingSlash: true };\n","js",[21,275,276,282],{"__ignoreMap":222},[226,277,278],{"class":228,"line":229},[226,279,281],{"class":280},"sJ8bj","\u002F\u002F next.config.mjs\n",[226,283,284,288,291,295,299,302,306],{"class":228,"line":235},[226,285,287],{"class":286},"szBVR","export",[226,289,290],{"class":286}," default",[226,292,294],{"class":293},"sVt8B"," { output: ",[226,296,298],{"class":297},"sZZnC","'export'",[226,300,301],{"class":293},", trailingSlash: ",[226,303,305],{"class":304},"sj4cs","true",[226,307,308],{"class":293}," };\n",[14,310,311,312,315,316,318,319,322],{},"Now the export writes ",[21,313,314],{},"out\u002Fdocs\u002Finstall\u002Findex.html",", and links render as ",[21,317,207],{},". Plain S3 website hosting and Nginx's default ",[21,320,321],{},"try_files $uri $uri\u002F =404"," both serve it.",[14,324,325,326,329,330,334],{},"For S3 behind CloudFront with the REST endpoint (not the website endpoint), index documents are not resolved for subdirectories. A CloudFront Function appends ",[21,327,328],{},"index.html"," to directory requests, as covered in ",[26,331,333],{"href":332},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3\u002F","Clean URLs and Trailing Slashes on S3",":",[217,336,338],{"className":271,"code":337,"language":273,"meta":222,"style":222},"function handler(event) {\n  var r = event.request;\n  if (r.uri.endsWith('\u002F')) r.uri += 'index.html';\n  else if (!r.uri.includes('.')) r.uri += '\u002Findex.html';\n  return r;\n}\n",[21,339,340,359,373,401,435,444],{"__ignoreMap":222},[226,341,342,345,349,352,356],{"class":228,"line":229},[226,343,344],{"class":286},"function",[226,346,348],{"class":347},"sScJk"," handler",[226,350,351],{"class":293},"(",[226,353,355],{"class":354},"s4XuR","event",[226,357,358],{"class":293},") {\n",[226,360,361,364,367,370],{"class":228,"line":235},[226,362,363],{"class":286},"  var",[226,365,366],{"class":293}," r ",[226,368,369],{"class":286},"=",[226,371,372],{"class":293}," event.request;\n",[226,374,375,378,381,384,386,389,392,395,398],{"class":228,"line":241},[226,376,377],{"class":286},"  if",[226,379,380],{"class":293}," (r.uri.",[226,382,383],{"class":347},"endsWith",[226,385,351],{"class":293},[226,387,388],{"class":297},"'\u002F'",[226,390,391],{"class":293},")) r.uri ",[226,393,394],{"class":286},"+=",[226,396,397],{"class":297}," 'index.html'",[226,399,400],{"class":293},";\n",[226,402,403,406,409,412,415,418,421,423,426,428,430,433],{"class":228,"line":247},[226,404,405],{"class":286},"  else",[226,407,408],{"class":286}," if",[226,410,411],{"class":293}," (",[226,413,414],{"class":286},"!",[226,416,417],{"class":293},"r.uri.",[226,419,420],{"class":347},"includes",[226,422,351],{"class":293},[226,424,425],{"class":297},"'.'",[226,427,391],{"class":293},[226,429,394],{"class":286},[226,431,432],{"class":297}," '\u002Findex.html'",[226,434,400],{"class":293},[226,436,438,441],{"class":228,"line":437},5,[226,439,440],{"class":286},"  return",[226,442,443],{"class":293}," r;\n",[226,445,447],{"class":228,"line":446},6,[226,448,449],{"class":293},"}\n",[37,451,453],{"id":452},"cause-2-nginx-without-the-right-try_files","Cause 2: Nginx Without the Right try_files",[14,455,456,457,460,461,463],{},"Keeping ",[21,458,459],{},"trailingSlash: false"," on Nginx works too, if Nginx tries the ",[21,462,256],{}," file:",[217,465,469],{"className":466,"code":467,"language":468,"meta":222,"style":222},"language-nginx shiki shiki-themes github-light github-dark","location \u002F {\n  try_files $uri $uri.html $uri\u002Findex.html =404;\n}\nerror_page 404 \u002F404.html;\n","nginx",[21,470,471,476,481,485],{"__ignoreMap":222},[226,472,473],{"class":228,"line":229},[226,474,475],{},"location \u002F {\n",[226,477,478],{"class":228,"line":235},[226,479,480],{},"  try_files $uri $uri.html $uri\u002Findex.html =404;\n",[226,482,483],{"class":228,"line":241},[226,484,449],{},[226,486,487],{"class":228,"line":247},[226,488,489],{},"error_page 404 \u002F404.html;\n",[14,491,492,493,496],{},"The original config had ",[21,494,495],{},"try_files $uri $uri\u002F \u002Findex.html;"," copied from a single-page-app tutorial. That caught every unknown URL and served the home page's HTML instead of a 404 — the \"wrong content on refresh\" variant of this bug, where search engines index dozens of URLs with the home page's content.",[42,498,499,621],{},[45,500,53,505,53,508,53,511,53,514],{"viewBox":501,"role":48,"ariaLabelledBy":502,"xmlns":52},"0 0 760 236",[503,504],"nx404-hosts-title","nx404-hosts-desc",[55,506,507],{"id":503},"Configuration needed per host for each trailing slash setting",[59,509,510],{"id":504},"A matrix of four hosts. Cloudflare serves both settings without extra configuration. Netlify serves both without extra configuration. Nginx needs try_files with the html extension for trailingSlash false and works by default for trailingSlash true. S3 with CloudFront needs a CloudFront Function for either setting, simplest with trailingSlash true.",[63,512],{"x":65,"y":65,"width":66,"height":513,"fill":68},"236",[70,515,73,516,73,519,73,529,73,532,73,535,73,538,73,540,73,543,73,549,73,551,73,554,73,560,73,562,73,565,73,568,73,573,73,577,73,581,73,585,73,589,73,591,73,594,73,597,73,599,73,603,73,607,73,610,73,614,73,618,53],{"style":72},[91,517],{"d":518,"fill":94,"stroke":95,"style":83},"M20.0 86.0 L740.0 86.0",[63,520],{"x":521,"y":522,"width":523,"height":524,"rx":172,"fill":525,"opacity":526,"stroke":527,"style":528},"214.0","90.0","257.0","25.6","#8ac926","0.2","#5a8a16","stroke-width:1px",[63,530],{"x":531,"y":522,"width":523,"height":524,"rx":172,"fill":525,"opacity":526,"stroke":527,"style":528},"479.0",[91,533],{"d":534,"fill":94,"stroke":82,"style":528},"M20.0 119.6 L740.0 119.6",[63,536],{"x":521,"y":537,"width":523,"height":524,"rx":172,"fill":525,"opacity":526,"stroke":527,"style":528},"123.6",[63,539],{"x":531,"y":537,"width":523,"height":524,"rx":172,"fill":525,"opacity":526,"stroke":527,"style":528},[91,541],{"d":542,"fill":94,"stroke":82,"style":528},"M20.0 153.2 L740.0 153.2",[63,544],{"x":521,"y":545,"width":523,"height":524,"rx":172,"fill":546,"opacity":547,"stroke":548,"style":528},"157.2","#ffca3a","0.24","#a97b00",[63,550],{"x":531,"y":545,"width":523,"height":524,"rx":172,"fill":525,"opacity":526,"stroke":527,"style":528},[91,552],{"d":553,"fill":94,"stroke":82,"style":528},"M20.0 186.8 L740.0 186.8",[63,555],{"x":521,"y":556,"width":523,"height":524,"rx":172,"fill":557,"opacity":558,"stroke":559,"style":528},"190.8","#ff595e","0.12","#d83b41",[63,561],{"x":531,"y":556,"width":523,"height":524,"rx":172,"fill":546,"opacity":547,"stroke":548,"style":528},[91,563],{"d":564,"fill":94,"stroke":82,"style":528},"M20.0 220.4 L740.0 220.4",[121,566,567],{"x":123,"y":124,"fill":125,"style":126},"What each host needs",[121,569,572],{"x":124,"y":570,"fill":125,"style":571},"75.2","font-size:12px;text-anchor:start;font-weight:700","Host",[121,574,459],{"x":575,"y":570,"fill":125,"style":576},"342.5","font-size:12px;text-anchor:middle;font-weight:700",[121,578,580],{"x":579,"y":570,"fill":125,"style":576},"607.5","trailingSlash: true",[121,582,584],{"x":124,"y":583,"fill":125,"style":571},"106.4","Cloudflare",[121,586,588],{"x":575,"y":587,"fill":125,"style":145},"106.2","works",[121,590,588],{"x":579,"y":587,"fill":125,"style":145},[121,592,593],{"x":124,"y":130,"fill":125,"style":571},"Netlify",[121,595,588],{"x":575,"y":596,"fill":125,"style":145},"139.8",[121,598,588],{"x":579,"y":596,"fill":125,"style":145},[121,600,602],{"x":124,"y":601,"fill":125,"style":571},"173.6","Nginx",[121,604,606],{"x":575,"y":605,"fill":125,"style":145},"173.4","try_files $uri.html",[121,608,609],{"x":579,"y":605,"fill":125,"style":145},"works by default",[121,611,613],{"x":124,"y":612,"fill":125,"style":571},"207.2","S3 + CloudFront",[121,615,617],{"x":575,"y":616,"fill":125,"style":145},"207.0","function needed",[121,619,620],{"x":579,"y":616,"fill":125,"style":145},"function for index.html",[180,622,623],{},"trailingSlash true is the setting that works on the most hosts with the least configuration.",[37,625,627],{"id":626},"cause-3-dynamic-routes-not-generated","Cause 3: Dynamic Routes Not Generated",[14,629,630,631,634,635,638],{},"A refresh on ",[21,632,633],{},"\u002Fblog\u002F2026-release-notes"," 404'd on every host. The file did not exist: the route ",[21,636,637],{},"app\u002Fblog\u002F[slug]\u002Fpage.tsx"," generated its params from a CMS query that returned only the first 100 posts — the CMS API's default page size. Client navigation to the 101st post worked because the link fetched its payload… which also did not exist, but the old client cache from a previous visit masked it during testing.",[217,640,644],{"className":641,"code":642,"language":643,"meta":222,"style":222},"language-tsx shiki shiki-themes github-light github-dark","export async function generateStaticParams() {\n  const posts = await getAllPosts(); \u002F\u002F now paginates through every page of the API\n  return posts.map((p) => ({ slug: p.slug }));\n}\nexport const dynamicParams = false;\n","tsx",[21,645,646,662,685,709,713],{"__ignoreMap":222},[226,647,648,650,653,656,659],{"class":228,"line":229},[226,649,287],{"class":286},[226,651,652],{"class":286}," async",[226,654,655],{"class":286}," function",[226,657,658],{"class":347}," generateStaticParams",[226,660,661],{"class":293},"() {\n",[226,663,664,667,670,673,676,679,682],{"class":228,"line":235},[226,665,666],{"class":286},"  const",[226,668,669],{"class":304}," posts",[226,671,672],{"class":286}," =",[226,674,675],{"class":286}," await",[226,677,678],{"class":347}," getAllPosts",[226,680,681],{"class":293},"(); ",[226,683,684],{"class":280},"\u002F\u002F now paginates through every page of the API\n",[226,686,687,689,692,695,698,700,703,706],{"class":228,"line":241},[226,688,440],{"class":286},[226,690,691],{"class":293}," posts.",[226,693,694],{"class":347},"map",[226,696,697],{"class":293},"((",[226,699,14],{"class":354},[226,701,702],{"class":293},") ",[226,704,705],{"class":286},"=>",[226,707,708],{"class":293}," ({ slug: p.slug }));\n",[226,710,711],{"class":228,"line":247},[226,712,449],{"class":293},[226,714,715,717,720,723,725,728],{"class":228,"line":437},[226,716,287],{"class":286},[226,718,719],{"class":286}," const",[226,721,722],{"class":304}," dynamicParams",[226,724,672],{"class":286},[226,726,727],{"class":304}," false",[226,729,400],{"class":293},[14,731,732,735,736,739],{},[21,733,734],{},"dynamicParams = false"," makes the build fail on routes requested but not generated during development, rather than silently skipping them. A post-build check compares the number of ",[21,737,738],{},"out\u002Fblog\u002F*\u002Findex.html"," files against the CMS's total count.",[37,741,743],{"id":742},"cause-4-a-catch-all-rewrite-on-the-host","Cause 4: A Catch-All Rewrite on the Host",[14,745,746,747,750,751,754,755,758,759,762],{},"Cloudflare served the site correctly except for one pattern: a ",[21,748,749],{},"_redirects"," rule ",[21,752,753],{},"\u002F* \u002Findex.html 200",", added months earlier for a now-removed client-side app section. It rewrote any path without a file to the home page. Removing it fixed the remaining \"wrong content\" reports, and the custom ",[21,756,757],{},"404.html"," exported by Next.js (from ",[21,760,761],{},"app\u002Fnot-found.tsx",") was then served with a real 404 status.",[37,764,766],{"id":765},"step-2-test-direct-loads-in-ci","Step 2: Test Direct Loads in CI",[14,768,769],{},"The bug survives because developers navigate by clicking. A Playwright test now loads a sample of URLs directly, by host configuration, in a fresh browser context:",[217,771,773],{"className":271,"code":772,"language":273,"meta":222,"style":222},"for (const path of samplePaths) {\n  const res = await page.goto(baseURL + path);\n  expect(res.status(), path).toBe(200);\n  await expect(page.locator('h1')).not.toHaveText('Welcome to Acme', { timeout: 1000 });\n}\n",[21,774,775,794,820,844,883],{"__ignoreMap":222},[226,776,777,780,782,785,788,791],{"class":228,"line":229},[226,778,779],{"class":286},"for",[226,781,411],{"class":293},[226,783,784],{"class":286},"const",[226,786,787],{"class":304}," path",[226,789,790],{"class":286}," of",[226,792,793],{"class":293}," samplePaths) {\n",[226,795,796,798,801,803,805,808,811,814,817],{"class":228,"line":235},[226,797,666],{"class":286},[226,799,800],{"class":304}," res",[226,802,672],{"class":286},[226,804,675],{"class":286},[226,806,807],{"class":293}," page.",[226,809,810],{"class":347},"goto",[226,812,813],{"class":293},"(baseURL ",[226,815,816],{"class":286},"+",[226,818,819],{"class":293}," path);\n",[226,821,822,825,828,831,834,837,839,841],{"class":228,"line":241},[226,823,824],{"class":347},"  expect",[226,826,827],{"class":293},"(res.",[226,829,830],{"class":347},"status",[226,832,833],{"class":293},"(), path).",[226,835,836],{"class":347},"toBe",[226,838,351],{"class":293},[226,840,155],{"class":304},[226,842,843],{"class":293},");\n",[226,845,846,849,852,855,858,860,863,866,869,871,874,877,880],{"class":228,"line":247},[226,847,848],{"class":286},"  await",[226,850,851],{"class":347}," expect",[226,853,854],{"class":293},"(page.",[226,856,857],{"class":347},"locator",[226,859,351],{"class":293},[226,861,862],{"class":297},"'h1'",[226,864,865],{"class":293},")).not.",[226,867,868],{"class":347},"toHaveText",[226,870,351],{"class":293},[226,872,873],{"class":297},"'Welcome to Acme'",[226,875,876],{"class":293},", { timeout: ",[226,878,879],{"class":304},"1000",[226,881,882],{"class":293}," });\n",[226,884,885],{"class":228,"line":437},[226,886,449],{"class":293},[14,888,889],{},"The second assertion catches the catch-all rewrite variant, where the status is 200 but the content is the home page. Sample paths include the deepest generated route of each dynamic segment and the last item of each paginated source.",[42,891,892,983],{},[45,893,53,898,53,901,53,904,53,907,53,976],{"viewBox":894,"role":48,"ariaLabelledBy":895,"xmlns":52},"0 0 760 152",[896,897],"nx404-test-title","nx404-test-desc",[55,899,900],{"id":896},"Steps of the direct-load test against a preview deploy",[59,902,903],{"id":897},"Four steps. Build the export and deploy a preview. Pick sample paths including the last item of each dynamic route. Load each path directly in a fresh browser context, not by clicking. Fail on any non-200 status or on content matching the home page.",[63,905],{"x":65,"y":65,"width":66,"height":906,"fill":68},"152",[70,908,73,909,73,915,73,920,73,924,73,927,73,930,73,933,73,936,73,939,73,944,73,949,73,953,73,956,73,960,73,963,73,968,73,972,53],{"style":72},[63,910],{"x":911,"y":912,"width":913,"height":914,"rx":80,"fill":81,"stroke":82,"style":83},"20.0","64.0","154.5","71.5",[63,916],{"x":917,"y":912,"width":913,"height":914,"rx":80,"fill":918,"opacity":919,"stroke":918,"style":83},"208.5","#1982c4","0.14",[91,921],{"d":922,"fill":94,"stroke":95,"style":923},"M176.5 99.8 L204.5 99.8","stroke-width:2px;marker-end:url(#nx404-test-arrow)",[63,925],{"x":926,"y":912,"width":913,"height":914,"rx":80,"fill":918,"opacity":919,"stroke":918,"style":83},"397.0",[91,928],{"d":929,"fill":94,"stroke":95,"style":923},"M365.0 99.8 L393.0 99.8",[63,931],{"x":932,"y":912,"width":913,"height":914,"rx":80,"fill":525,"opacity":526,"stroke":527,"style":83},"585.5",[91,934],{"d":935,"fill":94,"stroke":95,"style":923},"M553.5 99.8 L581.5 99.8",[121,937,938],{"x":123,"y":124,"fill":125,"style":126},"Testing what a refresh sees",[121,940,943],{"x":941,"y":942,"fill":125,"style":132},"97.2","97.5","Preview deploy",[121,945,948],{"x":941,"y":946,"fill":95,"style":947},"114.4","font-size:11px;text-anchor:middle","same host config as prod",[121,950,952],{"x":951,"y":942,"fill":125,"style":132},"285.8","Sample paths",[121,954,955],{"x":951,"y":946,"fill":95,"style":947},"last item per route",[121,957,959],{"x":958,"y":942,"fill":125,"style":132},"474.2","Direct load",[121,961,962],{"x":958,"y":946,"fill":95,"style":947},"fresh context, no clicks",[121,964,967],{"x":965,"y":966,"fill":125,"style":132},"662.8","90.4","Assert",[121,969,971],{"x":965,"y":970,"fill":95,"style":947},"107.3","200 and not home",[121,973,975],{"x":965,"y":974,"fill":95,"style":947},"121.6","content",[165,977,73,978,53],{},[168,979,175,981,73],{"id":980,"viewBox":171,"refX":80,"refY":172,"markerWidth":173,"markerHeight":173,"orient":174},"nx404-test-arrow",[91,982],{"d":178,"fill":95},[180,984,985],{},"Runs in about 20 seconds on 60 sampled paths per deploy.",[37,987,989],{"id":988},"basepath-and-asset-paths-on-subpath-deploys","basePath and Asset Paths on Subpath Deploys",[14,991,992,993,996,997,1000,1001,1004,1005,1008],{},"One more variant appeared when the docs were also deployed under ",[21,994,995],{},"\u002Fdocs-preview\u002F"," on a shared domain for review. Pages loaded on refresh, but every script and stylesheet 404'd, so the page rendered unstyled and never hydrated — which looks like a different bug but has the same root: the host serves files by path, and the paths in the HTML did not match where the files were. Setting ",[21,998,999],{},"basePath: '\u002Fdocs-preview'"," for that build (from an environment variable) prefixed both page links and ",[21,1002,1003],{},"_next\u002F"," asset URLs. ",[21,1006,1007],{},"assetPrefix"," alone, which some guides suggest, prefixes assets but not links, and left client navigation pointing at the root.",[14,1010,1011,1012,1015,1016,1019],{},"The general rule for this whole class of bug: when a static export misbehaves only on direct loads, compare three things for one failing URL — the path the browser requested, the file the export wrote, and the rule the host used to map one to the other. One of the three is always wrong, and ",[21,1013,1014],{},"curl -I"," plus ",[21,1017,1018],{},"ls out\u002F"," usually shows which in under a minute. On this site the investigation notes for all four causes fit in a short table in the repository's README, which has since saved two other developers from rediscovering them after unrelated hosting changes.",[37,1021,1023],{"id":1022},"custom-404-pages","Custom 404 Pages",[14,1025,1026,1027,1030,1031,1033,1034,1036,1037,1040,1041,1044],{},"Once real 404s return 404, the page they show matters. The export writes ",[21,1028,1029],{},"out\u002F404.html"," from ",[21,1032,761],{},"; each host needs pointing at it. Cloudflare and Netlify use ",[21,1035,757],{}," at the root automatically. Nginx needs ",[21,1038,1039],{},"error_page 404 \u002F404.html;"," (shown above). S3 with CloudFront needs a custom error response mapping 404 to ",[21,1042,1043],{},"\u002F404.html"," with status 404 — not 200, which some tutorials use for single-page apps and which recreates the soft-404 problem.",[37,1046,1048],{"id":1047},"measured-impact","Measured Impact",[1050,1051,1052,1071],"table",{},[1053,1054,1055],"thead",{},[1056,1057,1058,1062,1065,1068],"tr",{},[1059,1060,1061],"th",{},"Measure",[1059,1063,1064],{},"Before",[1059,1066,1067],{},"After",[1059,1069,1070],{},"Tool",[1072,1073,1074,1088,1104,1117,1131],"tbody",{},[1056,1075,1076,1080,1083,1085],{},[1077,1078,1079],"td",{},"404s on direct load, 60 sampled paths (S3)",[1077,1081,1082],{},"58",[1077,1084,65],{},[1077,1086,1087],{},"Playwright",[1056,1089,1090,1093,1096,1099],{},[1077,1091,1092],{},"Blog posts exported",[1077,1094,1095],{},"100 of 384",[1077,1097,1098],{},"384",[1077,1100,1101],{},[21,1102,1103],{},"find out\u002Fblog",[1056,1105,1106,1109,1112,1114],{},[1077,1107,1108],{},"URLs serving home page content",[1077,1110,1111],{},"31 (Cloudflare)",[1077,1113,65],{},[1077,1115,1116],{},"Playwright content check",[1056,1118,1119,1122,1125,1128],{},[1077,1120,1121],{},"\"Not found (404)\" in Search Console",[1077,1123,1124],{},"212",[1077,1126,1127],{},"4 (real)",[1077,1129,1130],{},"Coverage report",[1056,1132,1133,1136,1139,1142],{},[1077,1134,1135],{},"Search clicks to deep pages, 4 weeks",[1077,1137,1138],{},"baseline",[1077,1140,1141],{},"+19%",[1077,1143,1144],{},"Search Console",[37,1146,1148],{"id":1147},"pitfalls-rollback","Pitfalls & Rollback",[1150,1151,1152,1159,1165,1176,1193],"ul",{},[1153,1154,1155,1158],"li",{},[265,1156,1157],{},"Testing only by clicking."," Load URLs directly, in a clean context.",[1153,1160,1161,1164],{},[265,1162,1163],{},"Copying SPA rewrite rules."," A static export is a multi-page site; remove catch-all rewrites.",[1153,1166,1167,1173,1174,35],{},[265,1168,1169,1170,35],{},"Unpaginated data sources in ",[21,1171,1172],{},"generateStaticParams"," Fetch every page; set ",[21,1175,734],{},[1153,1177,1178,1185,1186,200,1189,1192],{},[265,1179,1180,1181,1184],{},"Changing ",[21,1182,1183],{},"trailingSlash"," without redirects."," URLs change from ",[21,1187,1188],{},"\u002Fa",[21,1190,1191],{},"\u002Fa\u002F","; most hosts redirect automatically, but check.",[1153,1194,1195,1198,1199,1201],{},[265,1196,1197],{},"Rollback:"," ",[21,1200,1183],{}," and host rules are independent switches; revert either alone.",[37,1203,1205],{"id":1204},"conclusion","Conclusion",[14,1207,1208,1209,1211,1212,1215],{},"A Next.js static export that 404s on refresh is a mismatch between the files the export writes and the files the host looks for, plus, sometimes, routes that were never generated or a leftover catch-all rewrite. Setting ",[21,1210,580],{}," for simple hosts, fixing ",[21,1213,1214],{},"try_files"," or adding a CloudFront Function, generating every dynamic route, and testing direct loads in CI removed 212 Search Console 404s and made every page reachable by URL.",[37,1217,1219],{"id":1218},"faq","FAQ",[1221,1222,1224],"h3",{"id":1223},"why-does-a-nextjs-static-export-page-work-when-clicked-but-404-on-refresh","Why does a Next.js static export page work when clicked but 404 on refresh?",[14,1226,1227],{},"Client-side navigation never asks the server for the page's HTML file; the router fetches data and renders in the browser. A refresh or direct visit asks the host for the URL, and if no file exists at the path the host looks for, it returns 404. The page works in one case and not the other because only the second depends on how files are laid out and how the host maps URLs to files.",[1221,1229,1231],{"id":1230},"should-i-use-trailingslash-true-in-a-static-export","Should I use trailingSlash true in a static export?",[14,1233,1234],{},"It makes the export write about slash index.html instead of about.html, which every static host serves at slash about slash without configuration. It is the safest default for hosts without clean URL support, such as plain S3 or simple Nginx configs. Hosts with clean URLs, like Cloudflare, Netlify and Vercel, work with either setting.",[1221,1236,1238],{"id":1237},"how-do-i-handle-dynamic-routes-that-were-not-generated-at-build-time","How do I handle dynamic routes that were not generated at build time?",[14,1240,1241],{},"They cannot exist in a static export. Every dynamic route must be listed by generateStaticParams. For paths that genuinely cannot be known at build time, render a client-side shell at a fixed path and rewrite the dynamic path to it at the host, accepting that the content loads in the browser.",[1221,1243,1245],{"id":1244},"why-do-refreshed-pages-show-the-wrong-content-instead-of-a-404","Why do refreshed pages show the wrong content instead of a 404?",[14,1247,1248],{},"Usually because the host has a catch-all rewrite to index.html, a single-page-app setting. Every unknown path then serves the home page's HTML, which hydrates and may briefly or permanently show the home page. Remove the catch-all for a multi-page static export and let real 404s return 404.",[37,1250,1252],{"id":1251},"related","Related",[1150,1254,1255,1263,1268,1275,1282],{},[1153,1256,1257,1198,1260,1262],{},[265,1258,1259],{},"Parent:",[26,1261,29],{"href":28}," — running Next.js as a static generator.",[1153,1264,1265,1267],{},[26,1266,34],{"href":33}," — URL settings in depth.",[1153,1269,1270,1274],{},[26,1271,1273],{"href":1272},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fhandling-dynamic-routes-in-nextjs-static-export\u002F","Handling Dynamic Routes in Next.js Static Export"," — generating every route.",[1153,1276,1277,1281],{},[26,1278,1280],{"href":1279},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx\u002F","Serving a Static Site with Nginx"," — the Nginx config used here.",[1153,1283,1284,1288],{},[26,1285,1287],{"href":1286},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Ffixing-soft-404s-on-static-hosts\u002F","Fixing Soft 404s on Static Hosts"," — the catch-all variant from a search perspective.",[1290,1291,1292],"style",{},"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 .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}",{"title":222,"searchDepth":235,"depth":235,"links":1294},[1295,1296,1297,1298,1299,1300,1301,1302,1303,1304,1305,1306,1307,1313],{"id":39,"depth":235,"text":40},{"id":214,"depth":235,"text":215},{"id":260,"depth":235,"text":261},{"id":452,"depth":235,"text":453},{"id":626,"depth":235,"text":627},{"id":742,"depth":235,"text":743},{"id":765,"depth":235,"text":766},{"id":988,"depth":235,"text":989},{"id":1022,"depth":235,"text":1023},{"id":1047,"depth":235,"text":1048},{"id":1147,"depth":235,"text":1148},{"id":1204,"depth":235,"text":1205},{"id":1218,"depth":235,"text":1219,"children":1308},[1309,1310,1311,1312],{"id":1223,"depth":241,"text":1224},{"id":1230,"depth":241,"text":1231},{"id":1237,"depth":241,"text":1238},{"id":1244,"depth":241,"text":1245},{"id":1251,"depth":235,"text":1252},[1315,1318,1321,1322],{"name":1316,"item":1317},"Home","\u002F",{"name":1319,"item":1320},"Choosing the Right Static Site Generator for Production","\u002Fchoosing-the-right-static-site-generator-for-production\u002F",{"name":29,"item":28},{"name":5,"item":1323},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ffixing-404s-on-refresh-in-nextjs-static-export\u002F","2026-10-02","Fix pages that work when navigated to but 404 on refresh or direct load in a Next.js static export, by matching file layout, trailing slashes and host rules.","md",[1328,1329,1330,1331],{"q":1224,"a":1227},{"q":1231,"a":1234},{"q":1238,"a":1241},{"q":1245,"a":1248},{},true,"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ffixing-404s-on-refresh-in-nextjs-static-export",{"title":5,"description":1325},"choosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ffixing-404s-on-refresh-in-nextjs-static-export\u002Findex","article","vHi4x7vMf281qgSmI4i2zwStwrFoC86WwxoTHzIGJLM",[1340,1343,1346,1349,1352,1355,1358,1361,1364,1367,1370,1373,1376,1379,1382,1385,1388,1391,1394,1397,1400,1403,1406,1409,1412,1415,1418,1421,1424,1427,1430,1433,1436,1439,1442,1445,1448,1451,1454,1457,1460,1463,1466,1469,1472,1475,1478,1481,1484,1487,1490,1493,1496,1499,1501,1504,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,1603,1604,1607,1609,1611,1614,1617,1620,1623,1626,1628,1631,1634,1637,1640,1643,1646,1649,1652,1655,1658,1661,1664,1667,1670,1673,1676,1679,1682,1685,1688,1691,1694,1697,1700,1703,1706,1709,1712,1714,1717,1720,1723,1726,1729,1732,1735,1738,1741,1744,1747,1750,1753,1756,1759,1762,1765,1768,1771,1774,1777,1780,1783,1786,1789,1792,1795,1798,1801,1804,1807,1810,1813,1816,1819,1822,1825,1828,1831,1834,1837,1840,1843,1846,1849,1852,1855,1858,1861,1864,1867,1870,1873,1876,1879,1882,1885,1888,1891,1894,1897,1900,1903,1906,1909,1912,1915,1918,1921,1924,1927,1930,1933,1936,1939,1942,1945,1948,1951,1954,1957,1960,1963,1966,1969,1972,1975,1978,1981,1984,1987,1990,1993,1996,1999,2002,2005,2008,2011,2014,2017,2020,2023,2026,2029,2032,2035,2038,2041,2044,2047,2050,2053,2056,2059,2062,2065,2068,2071,2074,2077,2080,2083,2086,2089,2092,2095,2098,2101,2104,2107,2110,2113,2116,2119,2122,2125,2128,2131,2134,2137,2140,2143,2146,2149,2152,2155,2158,2161,2164,2167,2170,2173,2176,2179,2182,2185,2188,2191,2194,2197,2200,2203,2206,2209,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,2394,2397,2400,2403,2406,2409,2412,2415,2418,2420,2423,2426,2429,2432,2435,2438,2441,2444,2447,2450,2453,2456,2459,2462,2465,2468,2471,2474,2477],{"path":1341,"title":1342},"\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":1344,"title":1345},"\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":1347,"title":1348},"\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":1350,"title":1351},"\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":1353,"title":1354},"\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":1356,"title":1357},"\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":1359,"title":1360},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1362,"title":1363},"\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":1365,"title":1366},"\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":1368,"title":1369},"\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":1371,"title":1372},"\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":1374,"title":1375},"\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":1377,"title":1378},"\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":1380,"title":1381},"\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":1383,"title":1384},"\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":1386,"title":1387},"\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":1389,"title":1390},"\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":1392,"title":1393},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1395,"title":1396},"\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":1398,"title":1399},"\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":1401,"title":1402},"\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":1404,"title":1405},"\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":1407,"title":1408},"\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":1410,"title":1411},"\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":1413,"title":1414},"\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":1416,"title":1417},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1419,"title":1420},"\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":1422,"title":1423},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fdocusaurus-vs-starlight-for-product-documentation","Docusaurus vs Starlight for Product Documentation",{"path":1425,"title":1426},"\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":1428,"title":1429},"\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":1431,"title":1432},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1434,"title":1435},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1437,"title":1438},"\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":1440,"title":1441},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1443,"title":1444},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1446,"title":1447},"\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":1449,"title":1450},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1452,"title":1453},"\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":1455,"title":1456},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1458,"title":1459},"\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":1461,"title":1462},"\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":1464,"title":1465},"\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":1467,"title":1468},"\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":1470,"title":1471},"\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":1473,"title":1474},"\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":1476,"title":1477},"\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":1479,"title":1480},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1482,"title":1483},"\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":1485,"title":1486},"\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":1488,"title":1489},"\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":1491,"title":1492},"\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":1494,"title":1495},"\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":1497,"title":1498},"\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":1500,"title":1319},"\u002Fchoosing-the-right-static-site-generator-for-production",{"path":1502,"title":1503},"\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":1505,"title":1506},"\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":1508,"title":1509},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1511,"title":1512},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1514,"title":1515},"\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":1517,"title":1518},"\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":1520,"title":1521},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1523,"title":1524},"\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":1526,"title":1527},"\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":1529,"title":1530},"\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":1532,"title":1533},"\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":1535,"title":1536},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1538,"title":1539},"\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":1541,"title":1542},"\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":1544,"title":1545},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1547,"title":1548},"\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":1550,"title":1551},"\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":1553,"title":1554},"\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":1556,"title":1557},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1559,"title":1560},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1562,"title":1563},"\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":1565,"title":1566},"\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":1568,"title":1569},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1571,"title":1572},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fkeeping-redirects-working-after-an-ssg-migration","Keeping Redirects Working After an SSG Migration",{"path":1574,"title":1575},"\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":1577,"title":1578},"\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":1580,"title":1581},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1583,"title":1584},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1586,"title":1587},"\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":1589,"title":1590},"\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":1592,"title":1593},"\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":1595,"title":1596},"\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":1598,"title":1599},"\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":1601,"title":1602},"\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":1334,"title":5},{"path":1605,"title":1606},"\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":1608,"title":1273},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fhandling-dynamic-routes-in-nextjs-static-export",{"path":1610,"title":29},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites",{"path":1612,"title":1613},"\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":1615,"title":1616},"\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":1618,"title":1619},"\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":1621,"title":1622},"\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":1624,"title":1625},"\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":1627,"title":34},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ftrailing-slash-and-basepath-in-nextjs-static-export",{"path":1629,"title":1630},"\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":1632,"title":1633},"\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":1635,"title":1636},"\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":1638,"title":1639},"\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":1641,"title":1642},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1644,"title":1645},"\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":1647,"title":1648},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1650,"title":1651},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1653,"title":1654},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1656,"title":1657},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1659,"title":1660},"\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":1662,"title":1663},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fsearch-index-size-budgets-for-large-docs","Search Index Size Budgets for Large Docs",{"path":1665,"title":1666},"\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":1668,"title":1669},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1671,"title":1672},"\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":1674,"title":1675},"\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":1677,"title":1678},"\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":1680,"title":1681},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1683,"title":1684},"\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":1686,"title":1687},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1689,"title":1690},"\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":1692,"title":1693},"\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":1695,"title":1696},"\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":1698,"title":1699},"\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":1701,"title":1702},"\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":1704,"title":1705},"\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":1707,"title":1708},"\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":1710,"title":1711},"\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":1713,"title":1287},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Ffixing-soft-404s-on-static-hosts",{"path":1715,"title":1716},"\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":1718,"title":1719},"\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":1721,"title":1722},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1724,"title":1725},"\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":1727,"title":1728},"\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":1730,"title":1731},"\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":1733,"title":1734},"\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":1736,"title":1737},"\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":1739,"title":1740},"\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":1742,"title":1743},"\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":1745,"title":1746},"\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":1748,"title":1749},"\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":1751,"title":1752},"\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":1754,"title":1755},"\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":1757,"title":1758},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1760,"title":1761},"\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":1763,"title":1764},"\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":1766,"title":1767},"\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":1769,"title":1770},"\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":1772,"title":1773},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1775,"title":1776},"\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":1778,"title":1779},"\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":1781,"title":1782},"\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":1784,"title":1785},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":1787,"title":1788},"\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":1790,"title":1791},"\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":1793,"title":1794},"\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":1796,"title":1797},"\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":1799,"title":1800},"\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":1802,"title":1803},"\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":1805,"title":1806},"\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":1808,"title":1809},"\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":1811,"title":1812},"\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":1814,"title":1815},"\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":1817,"title":1818},"\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":1820,"title":1821},"\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":1823,"title":1824},"\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":1826,"title":1827},"\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":1829,"title":1830},"\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":1832,"title":1833},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1835,"title":1836},"\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":1838,"title":1839},"\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":1841,"title":1842},"\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":1844,"title":1845},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":1847,"title":1848},"\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":1850,"title":1851},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1853,"title":1854},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1856,"title":1857},"\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":1859,"title":1860},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1862,"title":1863},"\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":1865,"title":1866},"\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":1868,"title":1869},"\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":1871,"title":1872},"\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":1874,"title":1875},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":1877,"title":1878},"\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":1880,"title":1881},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":1883,"title":1884},"\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":1886,"title":1887},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":1889,"title":1890},"\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":1892,"title":1893},"\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":1895,"title":1896},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1898,"title":1899},"\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":1901,"title":1902},"\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":1904,"title":1905},"\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":1907,"title":1908},"\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":1910,"title":1911},"\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":1913,"title":1914},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1916,"title":1917},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1919,"title":1920},"\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":1922,"title":1923},"\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":1925,"title":1926},"\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":1928,"title":1929},"\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":1931,"title":1932},"\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":1934,"title":1935},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1937,"title":1938},"\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":1940,"title":1941},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":1943,"title":1944},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1946,"title":1947},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":1949,"title":1950},"\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":1952,"title":1953},"\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":1955,"title":1956},"\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":1958,"title":1959},"\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":1961,"title":1962},"\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":1964,"title":1965},"\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":1967,"title":1968},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1970,"title":1971},"\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":1973,"title":1974},"\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":1976,"title":1977},"\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":1979,"title":1980},"\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":1982,"title":1983},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1985,"title":1986},"\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":1988,"title":1989},"\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":1991,"title":1992},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":1994,"title":1995},"\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":1997,"title":1998},"\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":2000,"title":2001},"\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":2003,"title":2004},"\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":2006,"title":2007},"\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":2009,"title":2010},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2012,"title":2013},"\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":2015,"title":2016},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2018,"title":2019},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2021,"title":2022},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2024,"title":2025},"\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":2027,"title":2028},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2030,"title":2031},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2033,"title":2034},"\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":2036,"title":2037},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2039,"title":2040},"\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":2042,"title":2043},"\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":2045,"title":2046},"\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":2048,"title":2049},"\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":2051,"title":2052},"\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":2054,"title":2055},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2057,"title":2058},"\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":2060,"title":2061},"\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":2063,"title":2064},"\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":2066,"title":2067},"\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":2069,"title":2070},"\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":2072,"title":2073},"\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":2075,"title":2076},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2078,"title":2079},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2081,"title":2082},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2084,"title":2085},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2087,"title":2088},"\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":2090,"title":2091},"\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":2093,"title":2094},"\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":2096,"title":2097},"\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":2099,"title":2100},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2102,"title":2103},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2105,"title":2106},"\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":2108,"title":2109},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2111,"title":2112},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2114,"title":2115},"\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":2117,"title":2118},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2120,"title":2121},"\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":2123,"title":2124},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2126,"title":2127},"\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":2129,"title":2130},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2132,"title":2133},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2135,"title":2136},"\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":2138,"title":2139},"\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":2141,"title":2142},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2144,"title":2145},"\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":2147,"title":2148},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2150,"title":2151},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2153,"title":2154},"\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":2156,"title":2157},"\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":2159,"title":2160},"\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":2162,"title":2163},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2165,"title":2166},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2168,"title":2169},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2171,"title":2172},"\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":2174,"title":2175},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2177,"title":2178},"\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":2180,"title":2181},"\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":2183,"title":2184},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2186,"title":2187},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2189,"title":2190},"\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":2192,"title":2193},"\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":2195,"title":2196},"\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":2198,"title":2199},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2201,"title":2202},"\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":2204,"title":2205},"\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":2207,"title":2208},"\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":2210,"title":2211},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":2213,"title":2214},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2216,"title":2217},"\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":2219,"title":2220},"\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":2222,"title":2223},"\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":2225,"title":2226},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2228,"title":2229},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2231,"title":2232},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2234,"title":2235},"\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":2237,"title":2238},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2240,"title":2241},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2243,"title":2244},"\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":2246,"title":2247},"\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":2249,"title":2250},"\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":2252,"title":2253},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2255,"title":2256},"\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":2258,"title":2259},"\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":2261,"title":2262},"\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":2264,"title":2265},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2267,"title":2268},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2270,"title":2271},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2273,"title":2274},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites","Netlify Redirects and Rewrites for Static Sites",{"path":2276,"title":2277},"\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":2279,"title":2280},"\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":2282,"title":2283},"\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":2285,"title":2286},"\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":2288,"title":2289},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2291,"title":2292},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2294,"title":2295},"\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":2297,"title":2298},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2300,"title":2301},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2303,"title":2304},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2306,"title":2307},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2309,"title":2310},"\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":2312,"title":2313},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2315,"title":2316},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2318,"title":2319},"\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":2321,"title":2322},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2324,"title":2325},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2327,"title":2328},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2330,"title":2331},"\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":2333,"title":2334},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2336,"title":2337},"\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":2339,"title":2340},"\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":2342,"title":2343},"\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":2345,"title":2346},"\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":2348,"title":2349},"\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":2351,"title":2352},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2354,"title":2355},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2357,"title":2358},"\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":2360,"title":2361},"\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":2363,"title":2364},"\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":2366,"title":2367},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2369,"title":2370},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2372,"title":2373},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2375,"title":2376},"\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":2378,"title":2379},"\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":2381,"title":2382},"\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":2384,"title":2385},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2387,"title":2388},"\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":2390,"title":2391},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2393,"title":333},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3",{"path":2395,"title":2396},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2398,"title":2399},"\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":2401,"title":2402},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2404,"title":2405},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2407,"title":2408},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2410,"title":2411},"\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":2413,"title":2414},"\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":2416,"title":2417},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2419,"title":1280},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx",{"path":2421,"title":2422},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2424,"title":2425},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2427,"title":2428},"\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":2430,"title":2431},"\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":2433,"title":2434},"\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":2436,"title":2437},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2439,"title":2440},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2442,"title":2443},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2445,"title":2446},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2448,"title":2449},"\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":2451,"title":2452},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2454,"title":2455},"\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":2457,"title":2458},"\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":2460,"title":2461},"\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":2463,"title":2464},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2466,"title":2467},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2469,"title":2470},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2472,"title":2473},"\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":2475,"title":2476},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2478,"title":2479},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2481,"tools":2485},{"label":2482,"plural":2483,"u":2484},"Fix","Fixes","\u002Fguides\u002Ffixes\u002F",[2486],{"label":2487,"u":2488},"Next.js","\u002Ftools\u002Fnextjs\u002F",1790943190980]