[{"data":1,"prerenderedAt":2647},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-build-output-api-for-custom-ssgs":3,"all-docs-nav":1496,"filed:\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-build-output-api-for-custom-ssgs":2635},{"id":4,"title":5,"body":6,"breadcrumb":1471,"dateModified":1481,"datePublished":1481,"description":1482,"extension":1483,"faq":1484,"meta":1489,"navigation":1490,"path":1491,"seo":1492,"slug":12,"stem":1493,"type":1494,"__hash__":1495},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-build-output-api-for-custom-ssgs\u002Findex.md","Vercel Build Output API for Custom SSGs",{"type":7,"value":8,"toc":1451},"minimark",[9,13,26,40,45,66,70,80,95,223,227,236,630,641,645,653,697,704,708,711,747,866,873,984,988,994,1074,1081,1085,1114,1118,1132,1135,1139,1227,1289,1293,1358,1362,1371,1375,1380,1383,1387,1390,1394,1397,1401,1404,1408,1447],[10,11,5],"h1",{"id":12},"vercel-build-output-api-for-custom-ssgs",[14,15,16,17,21,22,25],"p",{},"Vercel is best known for Next.js, and its framework detection makes deploying popular generators almost automatic. The layer underneath the detection is less known and more useful for static sites: the Build Output API, a documented directory format (",[18,19,20],"code",{},".vercel\u002Foutput\u002F",") that describes exactly what to deploy — static files, routes, headers, redirects, caching and optional functions. Any build process that writes that format can be deployed with ",[18,23,24],{},"vercel deploy --prebuilt",", whether the site is built with Zola, a custom Python script, Hugo with an unusual pipeline, or an Eleventy setup that Vercel's preset gets slightly wrong.",[14,27,28,29,34,35,39],{},"This guide writes a Build Output directory for a static documentation site built with a custom pipeline (Eleventy plus a Python API reference generator), defines headers, redirects and caching precisely, adds one edge function, builds in GitHub Actions and deploys the result. It is part of ",[30,31,33],"a",{"href":32},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002F","Netlify vs Vercel Deployment Strategies",", and complements ",[30,36,38],{"href":37},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy\u002F","Configuring Vercel for Hugo and Eleventy",".",[41,42,44],"h2",{"id":43},"prerequisites","Prerequisites",[46,47,48,56,63],"ul",{},[49,50,51,52,55],"li",{},"A static build that produces a directory of files (here ",[18,53,54],{},"_site\u002F",").",[49,57,58,59,62],{},"The Vercel CLI and a project linked with ",[18,60,61],{},"vercel link",", plus a token for CI.",[49,64,65],{},"The site's redirect and header rules in a data file.",[41,67,69],{"id":68},"the-directory-structure","The Directory Structure",[71,72,78],"pre",{"className":73,"code":75,"language":76,"meta":77},[74],"language-text",".vercel\u002Foutput\u002F\n  config.json            # version, routes (headers, redirects, rewrites), overrides\n  static\u002F                # every static file, served as-is\n    index.html\n    guide\u002Finstall\u002Findex.html\n    assets\u002Fapp.3f9a1c2e.js\n  functions\u002F             # optional\n    api\u002Fregion.func\u002F\n      .vc-config.json\n      index.js\n","text","",[18,79,75],{"__ignoreMap":77},[14,81,82,83,86,87,90,91,94],{},"Everything in ",[18,84,85],{},"static\u002F"," is served from Vercel's edge; ",[18,88,89],{},"config.json"," decides how requests map to files and functions and what headers they get. There is no ",[18,92,93],{},"vercel.json"," involved and no framework detection.",[96,97,98,219],"figure",{},[99,100,107,108,107,112,107,116,107,123,107,204],"svg",{"viewBox":101,"role":102,"ariaLabelledBy":103,"xmlns":106},"0 0 760 300","img",[104,105],"vbo-dir-title","vbo-dir-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[109,110,111],"title",{"id":104},"Structure of a Vercel Build Output directory for a static site",[113,114,115],"desc",{"id":105},"Three parts. config.json holds the version and an ordered routes array with headers, redirects, rewrites and handle phases. The static directory holds every file of the built site, served from the edge. The functions directory optionally holds edge or serverless functions, each with a vc-config file and an entrypoint.",[117,118],"rect",{"x":119,"y":119,"width":120,"height":121,"fill":122},"0","760","300","#ffffff",[124,125,127,128,127,138,127,145,127,151,127,154,127,158,127,165,127,170,127,175,127,181,127,184,127,188,127,192,127,196,127,200,107],"g",{"style":126},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[117,129],{"x":130,"y":131,"width":132,"height":133,"rx":134,"fill":135,"opacity":136,"stroke":135,"style":137},"40.0","60.0","440.0","57.2","8","#6a4c93","0.14","stroke-width:1.5px",[139,140],"path",{"d":141,"fill":142,"stroke":143,"style":144},"M260.0 119.2 L260.0 139.2","none","#556071","stroke-width:2px;marker-end:url(#vbo-dir-arrow)",[117,146],{"x":130,"y":147,"width":132,"height":133,"rx":134,"fill":148,"opacity":149,"stroke":150,"style":137},"143.2","#8ac926","0.2","#5a8a16",[139,152],{"d":153,"fill":142,"stroke":143,"style":144},"M260.0 202.4 L260.0 222.4",[117,155],{"x":130,"y":156,"width":132,"height":133,"rx":134,"fill":157,"opacity":136,"stroke":157,"style":137},"226.4","#1982c4",[76,159,164],{"x":160,"y":161,"fill":162,"style":163},"380.0","30.0","#1f2937","font-size:16px;text-anchor:middle;font-weight:700","What the Build Output directory describes",[76,166,89],{"x":167,"y":168,"fill":162,"style":169},"260.0","86.4","font-size:13px;text-anchor:middle;font-weight:700",[76,171,174],{"x":167,"y":172,"fill":143,"style":173},"103.3","font-size:11px;text-anchor:middle","routes, headers, redirects, phases",[76,176,180],{"x":177,"y":178,"fill":143,"style":179},"504.0","92.6","font-size:11.5px;text-anchor:start","evaluated in order",[76,182,85],{"x":167,"y":183,"fill":162,"style":169},"169.5",[76,185,187],{"x":167,"y":186,"fill":143,"style":173},"186.4","the built site",[76,189,191],{"x":177,"y":190,"fill":143,"style":179},"175.8","served from the edge",[76,193,195],{"x":167,"y":194,"fill":162,"style":169},"252.7","functions\u002F",[76,197,199],{"x":167,"y":198,"fill":143,"style":173},"269.6","optional edge function",[76,201,203],{"x":177,"y":202,"fill":143,"style":179},"259.0","only routed paths invoke it",[205,206,127,207,107],"defs",{},[208,209,215,216,127],"marker",{"id":210,"viewBox":211,"refX":134,"refY":212,"markerWidth":213,"markerHeight":213,"orient":214},"vbo-dir-arrow","0 0 10 10","5","7","auto-start-reverse","\n      ",[139,217],{"d":218,"fill":143},"M0 0 L10 5 L0 10 z",[220,221,222],"figcaption",{},"Vercel deploys what the directory says; nothing is inferred from the generator.",[41,224,226],{"id":225},"step-1-write-static-files-and-config-from-the-build","Step 1: Write Static Files and Config From the Build",[14,228,229,230,232,233,235],{},"A post-build script copies the site into ",[18,231,85],{}," and generates ",[18,234,89],{}," from the redirect and header data used by every host:",[71,237,241],{"className":238,"code":239,"language":240,"meta":77,"style":77},"language-js shiki shiki-themes github-light github-dark","\u002F\u002F scripts\u002Fvercel-output.mjs\nimport { cp, mkdir, writeFile, readFile } from 'node:fs\u002Fpromises';\nimport yaml from 'yaml';\nawait mkdir('.vercel\u002Foutput\u002Fstatic', { recursive: true });\nawait cp('_site', '.vercel\u002Foutput\u002Fstatic', { recursive: true });\nconst redirects = yaml.parse(await readFile('data\u002Fredirects.yaml', 'utf8'));\nconst routes = [\n  \u002F\u002F 1. redirects first, so old URLs never touch the filesystem\n  ...redirects.map((r) => ({ src: toRegex(r.from), status: r.status, headers: { Location: r.to } })),\n  \u002F\u002F 2. headers for everything, continue matching\n  { src: '\u002Fassets\u002F(.*)', headers: { 'Cache-Control': 'public, max-age=31536000, immutable' }, continue: true },\n  { src: '\u002F(.*)', headers: { 'X-Content-Type-Options': 'nosniff', 'Referrer-Policy': 'strict-origin-when-cross-origin',\n      'Strict-Transport-Security': 'max-age=31536000; includeSubDomains' }, continue: true },\n  \u002F\u002F 3. serve static files\n  { handle: 'filesystem' },\n  \u002F\u002F 4. edge function for one API path\n  { src: '\u002Fapi\u002Fregion', dest: '\u002Fapi\u002Fregion' },\n  \u002F\u002F 5. anything else: the 404 page with a 404 status\n  { src: '\u002F(.*)', status: 404, dest: '\u002F404.html' }\n];\nawait writeFile('.vercel\u002Foutput\u002Fconfig.json', JSON.stringify({ version: 3, routes, trailingSlash: true }, null, 2));\n","js",[18,242,243,252,273,288,314,338,376,389,395,429,435,464,495,512,518,529,535,550,556,577,583],{"__ignoreMap":77},[244,245,248],"span",{"class":246,"line":247},"line",1,[244,249,251],{"class":250},"sJ8bj","\u002F\u002F scripts\u002Fvercel-output.mjs\n",[244,253,255,259,263,266,270],{"class":246,"line":254},2,[244,256,258],{"class":257},"szBVR","import",[244,260,262],{"class":261},"sVt8B"," { cp, mkdir, writeFile, readFile } ",[244,264,265],{"class":257},"from",[244,267,269],{"class":268},"sZZnC"," 'node:fs\u002Fpromises'",[244,271,272],{"class":261},";\n",[244,274,276,278,281,283,286],{"class":246,"line":275},3,[244,277,258],{"class":257},[244,279,280],{"class":261}," yaml ",[244,282,265],{"class":257},[244,284,285],{"class":268}," 'yaml'",[244,287,272],{"class":261},[244,289,291,294,298,301,304,307,311],{"class":246,"line":290},4,[244,292,293],{"class":257},"await",[244,295,297],{"class":296},"sScJk"," mkdir",[244,299,300],{"class":261},"(",[244,302,303],{"class":268},"'.vercel\u002Foutput\u002Fstatic'",[244,305,306],{"class":261},", { recursive: ",[244,308,310],{"class":309},"sj4cs","true",[244,312,313],{"class":261}," });\n",[244,315,317,319,322,324,327,330,332,334,336],{"class":246,"line":316},5,[244,318,293],{"class":257},[244,320,321],{"class":296}," cp",[244,323,300],{"class":261},[244,325,326],{"class":268},"'_site'",[244,328,329],{"class":261},", ",[244,331,303],{"class":268},[244,333,306],{"class":261},[244,335,310],{"class":309},[244,337,313],{"class":261},[244,339,341,344,347,350,353,356,358,360,363,365,368,370,373],{"class":246,"line":340},6,[244,342,343],{"class":257},"const",[244,345,346],{"class":309}," redirects",[244,348,349],{"class":257}," =",[244,351,352],{"class":261}," yaml.",[244,354,355],{"class":296},"parse",[244,357,300],{"class":261},[244,359,293],{"class":257},[244,361,362],{"class":296}," readFile",[244,364,300],{"class":261},[244,366,367],{"class":268},"'data\u002Fredirects.yaml'",[244,369,329],{"class":261},[244,371,372],{"class":268},"'utf8'",[244,374,375],{"class":261},"));\n",[244,377,379,381,384,386],{"class":246,"line":378},7,[244,380,343],{"class":257},[244,382,383],{"class":309}," routes",[244,385,349],{"class":257},[244,387,388],{"class":261}," [\n",[244,390,392],{"class":246,"line":391},8,[244,393,394],{"class":250},"  \u002F\u002F 1. redirects first, so old URLs never touch the filesystem\n",[244,396,398,401,404,407,410,414,417,420,423,426],{"class":246,"line":397},9,[244,399,400],{"class":257},"  ...",[244,402,403],{"class":261},"redirects.",[244,405,406],{"class":296},"map",[244,408,409],{"class":261},"((",[244,411,413],{"class":412},"s4XuR","r",[244,415,416],{"class":261},") ",[244,418,419],{"class":257},"=>",[244,421,422],{"class":261}," ({ src: ",[244,424,425],{"class":296},"toRegex",[244,427,428],{"class":261},"(r.from), status: r.status, headers: { Location: r.to } })),\n",[244,430,432],{"class":246,"line":431},10,[244,433,434],{"class":250},"  \u002F\u002F 2. headers for everything, continue matching\n",[244,436,438,441,444,447,450,453,456,459,461],{"class":246,"line":437},11,[244,439,440],{"class":261},"  { src: ",[244,442,443],{"class":268},"'\u002Fassets\u002F(.*)'",[244,445,446],{"class":261},", headers: { ",[244,448,449],{"class":268},"'Cache-Control'",[244,451,452],{"class":261},": ",[244,454,455],{"class":268},"'public, max-age=31536000, immutable'",[244,457,458],{"class":261}," }, continue: ",[244,460,310],{"class":309},[244,462,463],{"class":261}," },\n",[244,465,467,469,472,474,477,479,482,484,487,489,492],{"class":246,"line":466},12,[244,468,440],{"class":261},[244,470,471],{"class":268},"'\u002F(.*)'",[244,473,446],{"class":261},[244,475,476],{"class":268},"'X-Content-Type-Options'",[244,478,452],{"class":261},[244,480,481],{"class":268},"'nosniff'",[244,483,329],{"class":261},[244,485,486],{"class":268},"'Referrer-Policy'",[244,488,452],{"class":261},[244,490,491],{"class":268},"'strict-origin-when-cross-origin'",[244,493,494],{"class":261},",\n",[244,496,498,501,503,506,508,510],{"class":246,"line":497},13,[244,499,500],{"class":268},"      'Strict-Transport-Security'",[244,502,452],{"class":261},[244,504,505],{"class":268},"'max-age=31536000; includeSubDomains'",[244,507,458],{"class":261},[244,509,310],{"class":309},[244,511,463],{"class":261},[244,513,515],{"class":246,"line":514},14,[244,516,517],{"class":250},"  \u002F\u002F 3. serve static files\n",[244,519,521,524,527],{"class":246,"line":520},15,[244,522,523],{"class":261},"  { handle: ",[244,525,526],{"class":268},"'filesystem'",[244,528,463],{"class":261},[244,530,532],{"class":246,"line":531},16,[244,533,534],{"class":250},"  \u002F\u002F 4. edge function for one API path\n",[244,536,538,540,543,546,548],{"class":246,"line":537},17,[244,539,440],{"class":261},[244,541,542],{"class":268},"'\u002Fapi\u002Fregion'",[244,544,545],{"class":261},", dest: ",[244,547,542],{"class":268},[244,549,463],{"class":261},[244,551,553],{"class":246,"line":552},18,[244,554,555],{"class":250},"  \u002F\u002F 5. anything else: the 404 page with a 404 status\n",[244,557,559,561,563,566,569,571,574],{"class":246,"line":558},19,[244,560,440],{"class":261},[244,562,471],{"class":268},[244,564,565],{"class":261},", status: ",[244,567,568],{"class":309},"404",[244,570,545],{"class":261},[244,572,573],{"class":268},"'\u002F404.html'",[244,575,576],{"class":261}," }\n",[244,578,580],{"class":246,"line":579},20,[244,581,582],{"class":261},"];\n",[244,584,586,588,591,593,596,598,601,603,606,609,612,615,617,620,623,625,628],{"class":246,"line":585},21,[244,587,293],{"class":257},[244,589,590],{"class":296}," writeFile",[244,592,300],{"class":261},[244,594,595],{"class":268},"'.vercel\u002Foutput\u002Fconfig.json'",[244,597,329],{"class":261},[244,599,600],{"class":309},"JSON",[244,602,39],{"class":261},[244,604,605],{"class":296},"stringify",[244,607,608],{"class":261},"({ version: ",[244,610,611],{"class":309},"3",[244,613,614],{"class":261},", routes, trailingSlash: ",[244,616,310],{"class":309},[244,618,619],{"class":261}," }, ",[244,621,622],{"class":309},"null",[244,624,329],{"class":261},[244,626,627],{"class":309},"2",[244,629,375],{"class":261},[14,631,632,633,636,637,640],{},"Route order is explicit: redirects run before the filesystem check, headers apply with ",[18,634,635],{},"continue: true"," so matching continues, ",[18,638,639],{},"handle: 'filesystem'"," serves any matching static file, and the final route turns misses into a real 404. That last route fixed a bug from the preset-based deploy, where missing pages returned the 404 page with a 200 status.",[41,642,644],{"id":643},"step-2-cache-control-for-html","Step 2: Cache Control for HTML",[14,646,647,648,652],{},"Vercel's edge caches static files and serves HTML with a default that revalidates. For documentation, HTML was given a short shared cache with stale-while-revalidate, as in ",[30,649,651],{"href":650},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fstale-while-revalidate-for-static-html\u002F","Stale-While-Revalidate for Static HTML",":",[71,654,656],{"className":238,"code":655,"language":240,"meta":77,"style":77},"{ src: '\u002F(.*)\u002F', headers: { 'Cache-Control': 'public, max-age=0, s-maxage=300, stale-while-revalidate=86400' }, continue: true }\n",[18,657,658],{"__ignoreMap":77},[244,659,660,663,666,668,671,673,676,679,681,683,686,688,691,693,695],{"class":246,"line":247},[244,661,662],{"class":261},"{ ",[244,664,665],{"class":296},"src",[244,667,452],{"class":261},[244,669,670],{"class":268},"'\u002F(.*)\u002F'",[244,672,329],{"class":261},[244,674,675],{"class":296},"headers",[244,677,678],{"class":261},": { ",[244,680,449],{"class":268},[244,682,452],{"class":261},[244,684,685],{"class":268},"'public, max-age=0, s-maxage=300, stale-while-revalidate=86400'",[244,687,619],{"class":261},[244,689,690],{"class":257},"continue",[244,692,452],{"class":261},[244,694,310],{"class":309},[244,696,576],{"class":261},[14,698,699,700,703],{},"Vercel purges its edge cache for a project on every production deploy, so the short ",[18,701,702],{},"s-maxage"," never serves old HTML after a deploy.",[41,705,707],{"id":706},"step-3-one-edge-function","Step 3: One Edge Function",[14,709,710],{},"The site needed a tiny endpoint returning the reader's region for a data-residency notice. An edge function in the Build Output format:",[71,712,716],{"className":713,"code":714,"language":715,"meta":77,"style":77},"language-json shiki shiki-themes github-light github-dark","\u002F\u002F .vercel\u002Foutput\u002Ffunctions\u002Fapi\u002Fregion.func\u002F.vc-config.json\n{ \"runtime\": \"edge\", \"entrypoint\": \"index.js\" }\n","json",[18,717,718,723],{"__ignoreMap":77},[244,719,720],{"class":246,"line":247},[244,721,722],{"class":250},"\u002F\u002F .vercel\u002Foutput\u002Ffunctions\u002Fapi\u002Fregion.func\u002F.vc-config.json\n",[244,724,725,727,730,732,735,737,740,742,745],{"class":246,"line":254},[244,726,662],{"class":261},[244,728,729],{"class":309},"\"runtime\"",[244,731,452],{"class":261},[244,733,734],{"class":268},"\"edge\"",[244,736,329],{"class":261},[244,738,739],{"class":309},"\"entrypoint\"",[244,741,452],{"class":261},[244,743,744],{"class":268},"\"index.js\"",[244,746,576],{"class":261},[71,748,750],{"className":238,"code":749,"language":240,"meta":77,"style":77},"\u002F\u002F .vercel\u002Foutput\u002Ffunctions\u002Fapi\u002Fregion.func\u002Findex.js\nexport default function handler(request) {\n  const country = request.headers.get('x-vercel-ip-country') ?? 'unknown';\n  return new Response(JSON.stringify({ country }), {\n    headers: { 'Content-Type': 'application\u002Fjson', 'Cache-Control': 'private, no-store' }\n  });\n}\n",[18,751,752,757,779,810,832,856,861],{"__ignoreMap":77},[244,753,754],{"class":246,"line":247},[244,755,756],{"class":250},"\u002F\u002F .vercel\u002Foutput\u002Ffunctions\u002Fapi\u002Fregion.func\u002Findex.js\n",[244,758,759,762,765,768,771,773,776],{"class":246,"line":254},[244,760,761],{"class":257},"export",[244,763,764],{"class":257}," default",[244,766,767],{"class":257}," function",[244,769,770],{"class":296}," handler",[244,772,300],{"class":261},[244,774,775],{"class":412},"request",[244,777,778],{"class":261},") {\n",[244,780,781,784,787,789,792,795,797,800,802,805,808],{"class":246,"line":275},[244,782,783],{"class":257},"  const",[244,785,786],{"class":309}," country",[244,788,349],{"class":257},[244,790,791],{"class":261}," request.headers.",[244,793,794],{"class":296},"get",[244,796,300],{"class":261},[244,798,799],{"class":268},"'x-vercel-ip-country'",[244,801,416],{"class":261},[244,803,804],{"class":257},"??",[244,806,807],{"class":268}," 'unknown'",[244,809,272],{"class":261},[244,811,812,815,818,821,823,825,827,829],{"class":246,"line":290},[244,813,814],{"class":257},"  return",[244,816,817],{"class":257}," new",[244,819,820],{"class":296}," Response",[244,822,300],{"class":261},[244,824,600],{"class":309},[244,826,39],{"class":261},[244,828,605],{"class":296},[244,830,831],{"class":261},"({ country }), {\n",[244,833,834,837,840,842,845,847,849,851,854],{"class":246,"line":316},[244,835,836],{"class":261},"    headers: { ",[244,838,839],{"class":268},"'Content-Type'",[244,841,452],{"class":261},[244,843,844],{"class":268},"'application\u002Fjson'",[244,846,329],{"class":261},[244,848,449],{"class":268},[244,850,452],{"class":261},[244,852,853],{"class":268},"'private, no-store'",[244,855,576],{"class":261},[244,857,858],{"class":246,"line":340},[244,859,860],{"class":261},"  });\n",[244,862,863],{"class":246,"line":378},[244,864,865],{"class":261},"}\n",[14,867,868,869,872],{},"Only ",[18,870,871],{},"\u002Fapi\u002Fregion"," invokes it, because only that route points at it. Every page remains a static file.",[96,874,875,981],{},[99,876,107,881,107,884,107,887,107,890,107,974],{"viewBox":877,"role":102,"ariaLabelledBy":878,"xmlns":106},"0 0 760 152",[879,880],"vbo-routes-title","vbo-routes-desc",[109,882,883],{"id":879},"Route evaluation order in the Build Output config",[113,885,886],{"id":880},"A request is checked against redirect routes first and redirected if one matches. Header routes then add cache and security headers and continue. The filesystem phase serves any matching static file. The API route sends \u002Fapi\u002Fregion to the edge function. Any remaining request gets the 404 page with a 404 status.",[117,888],{"x":119,"y":119,"width":120,"height":889,"fill":122},"152",[124,891,127,892,127,901,127,904,127,908,127,911,127,914,127,917,127,920,127,926,127,929,127,932,127,937,127,940,127,944,127,949,127,952,127,955,127,958,127,962,127,965,127,969,127,972,107],{"style":126},[117,893],{"x":894,"y":895,"width":896,"height":897,"rx":134,"fill":898,"opacity":899,"stroke":900,"style":137},"20.0","64.0","116.8","71.5","#ffca3a","0.24","#a97b00",[117,902],{"x":903,"y":895,"width":896,"height":897,"rx":134,"fill":135,"opacity":136,"stroke":135,"style":137},"170.8",[139,905],{"d":906,"fill":142,"stroke":143,"style":907},"M138.8 99.8 L166.8 99.8","stroke-width:2px;marker-end:url(#vbo-routes-arrow)",[117,909],{"x":910,"y":895,"width":896,"height":897,"rx":134,"fill":148,"opacity":149,"stroke":150,"style":137},"321.6",[139,912],{"d":913,"fill":142,"stroke":143,"style":907},"M289.6 99.8 L317.6 99.8",[117,915],{"x":916,"y":895,"width":896,"height":897,"rx":134,"fill":157,"opacity":136,"stroke":157,"style":137},"472.4",[139,918],{"d":919,"fill":142,"stroke":143,"style":907},"M440.4 99.8 L468.4 99.8",[117,921],{"x":922,"y":895,"width":896,"height":897,"rx":134,"fill":923,"opacity":924,"stroke":925,"style":137},"623.2","#ff595e","0.12","#d83b41",[139,927],{"d":928,"fill":142,"stroke":143,"style":907},"M591.2 99.8 L619.2 99.8",[76,930,931],{"x":160,"y":161,"fill":162,"style":163},"How one request walks the routes",[76,933,936],{"x":934,"y":935,"fill":162,"style":169},"78.4","90.4","Redirects",[76,938,265],{"x":934,"y":939,"fill":143,"style":173},"107.3",[76,941,943],{"x":934,"y":942,"fill":143,"style":173},"121.6","redirects.yaml",[76,945,948],{"x":946,"y":947,"fill":162,"style":169},"229.2","97.5","Headers",[76,950,635],{"x":946,"y":951,"fill":143,"style":173},"114.4",[76,953,954],{"x":160,"y":947,"fill":162,"style":169},"Filesystem",[76,956,957],{"x":160,"y":951,"fill":143,"style":173},"static files",[76,959,961],{"x":960,"y":947,"fill":162,"style":169},"530.8","API route",[76,963,964],{"x":960,"y":951,"fill":143,"style":173},"edge function",[76,966,968],{"x":967,"y":935,"fill":162,"style":169},"681.6","Fallback",[76,970,971],{"x":967,"y":939,"fill":143,"style":173},"404.html, status",[76,973,568],{"x":967,"y":942,"fill":143,"style":173},[205,975,127,976,107],{},[208,977,215,979,127],{"id":978,"viewBox":211,"refX":134,"refY":212,"markerWidth":213,"markerHeight":213,"orient":214},"vbo-routes-arrow",[139,980],{"d":218,"fill":143},[220,982,983],{},"The same five steps replaced about 40 lines of vercel.json and fixed a 200-status 404 page.",[41,985,987],{"id":986},"step-4-build-in-ci-deploy-the-output","Step 4: Build in CI, Deploy the Output",[14,989,990,991,993],{},"Building in GitHub Actions gives full control of the build environment and caching, and ",[18,992,24],{}," uploads the finished output:",[71,995,999],{"className":996,"code":997,"language":998,"meta":77,"style":77},"language-yaml shiki shiki-themes github-light github-dark","- run: npm ci && npm run build && python3 tools\u002Fapi_ref.py && node scripts\u002Fvercel-output.mjs\n- run: npx vercel pull --yes --environment=${{ github.ref == 'refs\u002Fheads\u002Fmain' && 'production' || 'preview' }} --token=$VERCEL_TOKEN\n- run: npx vercel deploy --prebuilt ${{ github.ref == 'refs\u002Fheads\u002Fmain' && '--prod' || '' }} --token=$VERCEL_TOKEN > url.txt\n  env: { VERCEL_TOKEN: '${{ secrets.VERCEL_TOKEN }}', VERCEL_ORG_ID: '${{ secrets.VERCEL_ORG_ID }}', VERCEL_PROJECT_ID: '${{ secrets.VERCEL_PROJECT_ID }}' }\n","yaml",[18,1000,1001,1015,1026,1037],{"__ignoreMap":77},[244,1002,1003,1006,1010,1012],{"class":246,"line":247},[244,1004,1005],{"class":261},"- ",[244,1007,1009],{"class":1008},"s9eBZ","run",[244,1011,452],{"class":261},[244,1013,1014],{"class":268},"npm ci && npm run build && python3 tools\u002Fapi_ref.py && node scripts\u002Fvercel-output.mjs\n",[244,1016,1017,1019,1021,1023],{"class":246,"line":254},[244,1018,1005],{"class":261},[244,1020,1009],{"class":1008},[244,1022,452],{"class":261},[244,1024,1025],{"class":268},"npx vercel pull --yes --environment=${{ github.ref == 'refs\u002Fheads\u002Fmain' && 'production' || 'preview' }} --token=$VERCEL_TOKEN\n",[244,1027,1028,1030,1032,1034],{"class":246,"line":275},[244,1029,1005],{"class":261},[244,1031,1009],{"class":1008},[244,1033,452],{"class":261},[244,1035,1036],{"class":268},"npx vercel deploy --prebuilt ${{ github.ref == 'refs\u002Fheads\u002Fmain' && '--prod' || '' }} --token=$VERCEL_TOKEN > url.txt\n",[244,1038,1039,1042,1044,1047,1049,1052,1054,1057,1059,1062,1064,1067,1069,1072],{"class":246,"line":290},[244,1040,1041],{"class":1008},"  env",[244,1043,678],{"class":261},[244,1045,1046],{"class":1008},"VERCEL_TOKEN",[244,1048,452],{"class":261},[244,1050,1051],{"class":268},"'${{ secrets.VERCEL_TOKEN }}'",[244,1053,329],{"class":261},[244,1055,1056],{"class":1008},"VERCEL_ORG_ID",[244,1058,452],{"class":261},[244,1060,1061],{"class":268},"'${{ secrets.VERCEL_ORG_ID }}'",[244,1063,329],{"class":261},[244,1065,1066],{"class":1008},"VERCEL_PROJECT_ID",[244,1068,452],{"class":261},[244,1070,1071],{"class":268},"'${{ secrets.VERCEL_PROJECT_ID }}'",[244,1073,576],{"class":261},[14,1075,1076,1077,1080],{},"Pull requests get preview deployments with their own URLs, exactly as with Vercel's Git integration; the URL in ",[18,1078,1079],{},"url.txt"," is commented on the pull request. The Python API reference generator, which Vercel's build image did not support at the needed version, now runs in the Actions environment.",[41,1082,1084],{"id":1083},"testing-the-output-before-deploy","Testing the Output Before Deploy",[14,1086,1087,1088,1091,1092,1095,1096,1098,1099,1102,1103,1105,1106,1108,1109,1113],{},"Because the whole deployment is described by files, it can be tested before upload. ",[18,1089,1090],{},"vercel dev"," does not use ",[18,1093,1094],{},".vercel\u002Foutput"," directly, so the team tests two ways. A unit test loads ",[18,1097,89],{}," and checks invariants: every redirect source is unique, no redirect target is itself a redirect source (no chains), every ",[18,1100,1101],{},"dest"," in a route exists in ",[18,1104,85],{}," or ",[18,1107,195],{},", and the final route is the 404 fallback. And the header and redirect table from ",[30,1110,1112],{"href":1111},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy\u002F","Testing Redirects and Headers Before Deploy"," runs against each preview deployment URL. The unit test caught a redirect loop introduced by a data-file edit before it was ever deployed.",[41,1115,1117],{"id":1116},"portability-across-hosts","Portability Across Hosts",[14,1119,1120,1121,1123,1124,1127,1128,1131],{},"Generating host configuration from shared data pays off beyond Vercel. The same ",[18,1122,943],{}," and header definitions also produce a ",[18,1125,1126],{},"_redirects"," and ",[18,1129,1130],{},"_headers"," pair for a Netlify mirror and a Caddy import file for the self-hosted internal copy of the docs, each from a small writer function. When the team evaluated moving the site between hosts, the build already emitted every format; switching was a change to the deploy step, not a rewrite of routing rules. It also made differences between hosts visible: Vercel's route patterns are regular expressions while Netlify's use splats and placeholders, and the writer functions are where those differences are handled — once, with tests — rather than in hand-edited files that drift apart.",[14,1133,1134],{},"The Build Output API also makes it easy to inspect exactly what will be deployed. Before each production deploy, the workflow prints a summary of the output — number of static files, total size, route count, functions — into the job summary, which is where an unexpected change (a doubled file count, a missing redirect block) shows up before it goes live.",[41,1136,1138],{"id":1137},"measured-impact","Measured Impact",[1140,1141,1142,1158],"table",{},[1143,1144,1145],"thead",{},[1146,1147,1148,1152,1155],"tr",{},[1149,1150,1151],"th",{},"Measure",[1149,1153,1154],{},"Vercel preset + vercel.json",[1149,1156,1157],{},"Build Output API",[1159,1160,1161,1173,1183,1194,1205,1216],"tbody",{},[1146,1162,1163,1167,1170],{},[1164,1165,1166],"td",{},"Build environment",[1164,1168,1169],{},"Vercel image, Python 3.9",[1164,1171,1172],{},"Actions runner, Python 3.12",[1146,1174,1175,1178,1181],{},[1164,1176,1177],{},"Status code for missing pages",[1164,1179,1180],{},"200 (404 page)",[1164,1182,568],{},[1146,1184,1185,1188,1191],{},[1164,1186,1187],{},"Configuration",[1164,1189,1190],{},"40 lines vercel.json + implicit preset behaviour",[1164,1192,1193],{},"generated config.json, tested",[1146,1195,1196,1199,1202],{},[1164,1197,1198],{},"Redirects kept in sync with other hosts",[1164,1200,1201],{},"manual",[1164,1203,1204],{},"generated from one data file",[1146,1206,1207,1210,1213],{},[1164,1208,1209],{},"Build + deploy time, typical PR",[1164,1211,1212],{},"3 min 20 s",[1164,1214,1215],{},"2 min 05 s (cached in Actions)",[1146,1217,1218,1221,1224],{},[1164,1219,1220],{},"Soft-404 URLs in Search Console",[1164,1222,1223],{},"63",[1164,1225,1226],{},"0 after recrawl",[96,1228,1229,1286],{},[99,1230,107,1235,107,1238,107,1241,107,1244],{"viewBox":1231,"role":102,"ariaLabelledBy":1232,"xmlns":106},"0 0 760 295",[1233,1234],"vbo-imp-title","vbo-imp-desc",[109,1236,1237],{"id":1233},"Pull request build and deploy time before and after using the Build Output API",[113,1239,1240],{"id":1234},"Vertical bars. With the Vercel preset building on Vercel, a typical pull request took 200 seconds to a ready preview. Building in GitHub Actions with caches and deploying the prebuilt output took 125 seconds.",[117,1242],{"x":119,"y":119,"width":120,"height":1243,"fill":122},"295",[124,1245,127,1246,127,1254,127,1260,127,1263,127,1266,127,1272,127,1277,127,1283,107],{"style":126},[117,1247],{"x":1248,"y":1249,"width":1250,"height":1251,"rx":611,"fill":898,"opacity":1252,"stroke":900,"style":1253},"165.0","76.0","90.0","170.0","0.45","stroke-width:1px",[117,1255],{"x":1256,"y":1257,"width":1250,"height":1258,"rx":611,"fill":148,"opacity":1259,"stroke":150,"style":1253},"505.0","139.8","106.2","0.4",[139,1261],{"d":1262,"fill":142,"stroke":143,"style":137},"M30.0 246.0 L730.0 246.0",[76,1264,1265],{"x":160,"y":161,"fill":162,"style":163},"Build and deploy time for a typical pull request",[76,1267,1271],{"x":1268,"y":1269,"fill":162,"style":1270},"210.0","69.0","font-size:12px;text-anchor:middle;font-weight:700","200 s",[76,1273,1276],{"x":1268,"y":1274,"fill":143,"style":1275},"264.0","font-size:11.5px;text-anchor:middle","Vercel preset build",[76,1278,1282],{"x":1279,"y":1280,"fill":1281,"style":1270},"550.0","132.8","#3f6410","125 s",[76,1284,1285],{"x":1279,"y":1274,"fill":143,"style":1275},"Actions build + prebuilt deploy",[220,1287,1288],{},"Median of 30 pull requests per setup, measured from push to preview URL available.",[41,1290,1292],{"id":1291},"pitfalls-rollback","Pitfalls & Rollback",[46,1294,1295,1309,1323,1339,1348],{},[49,1296,1297,1301,1302,1304,1305,1308],{},[1298,1299,1300],"strong",{},"Route order mistakes."," Headers without ",[18,1303,635],{}," stop matching; redirects after ",[18,1306,1307],{},"filesystem"," never run for existing paths.",[49,1310,1311,1314,1315,1318,1319,1322],{},[1298,1312,1313],{},"Forgetting the 404 status."," A catch-all rewrite to ",[18,1316,1317],{},"404.html"," without ",[18,1320,1321],{},"status: 404"," creates soft 404s.",[49,1324,1325,1331,1332,1335,1336,1338],{},[1298,1326,1327,1328,1330],{},"Mixing ",[18,1329,93],{}," and prebuilt output."," With ",[18,1333,1334],{},"--prebuilt",", the output's ",[18,1337,89],{}," is authoritative; keep one source.",[49,1340,1341,1347],{},[1298,1342,1343,1344,39],{},"Missing ",[18,1345,1346],{},"vercel pull"," Prebuilt deploys need the project settings pulled first.",[49,1349,1350,1353,1354,1357],{},[1298,1351,1352],{},"Rollback:"," Vercel keeps previous deployments; ",[18,1355,1356],{},"vercel rollback"," or promoting an older deployment restores the previous version instantly.",[41,1359,1361],{"id":1360},"conclusion","Conclusion",[14,1363,1364,1365,1367,1368,1370],{},"The Build Output API turns Vercel into a precise static host for any generator: write the files to ",[18,1366,85],{},", describe routing, headers and caching in ",[18,1369,89],{},", add a function only where needed, and deploy the prebuilt directory from your own CI. For this site it replaced implicit preset behaviour with a generated, tested configuration, fixed soft 404s and let the build use tools Vercel's image did not provide.",[41,1372,1374],{"id":1373},"faq","FAQ",[1376,1377,1379],"h3",{"id":1378},"what-is-the-vercel-build-output-api","What is the Vercel Build Output API?",[14,1381,1382],{},"A documented directory structure, .vercel\u002Foutput, that describes a deployment: static files, routing configuration, and optional serverless or edge functions. Anything that writes this structure can be deployed to Vercel with vercel deploy --prebuilt, without Vercel knowing the generator.",[1376,1384,1386],{"id":1385},"when-do-i-need-it-instead-of-vercels-framework-presets","When do I need it instead of Vercel's framework presets?",[14,1388,1389],{},"When the generator has no preset, such as a custom build script, Zola or a less common SSG, or when you want exact control over routes, headers and caching that presets configure implicitly. It is also useful for building in your own CI and uploading only the result.",[1376,1391,1393],{"id":1392},"how-are-headers-and-redirects-defined","How are headers and redirects defined?",[14,1395,1396],{},"In the routes array of .vercel\u002Foutput\u002Fconfig.json, with src patterns, headers, status codes and destinations, processed in order. There are also handle phases such as filesystem to control whether routes run before or after static files are matched.",[1376,1398,1400],{"id":1399},"can-i-add-an-edge-function-without-a-framework","Can I add an edge function without a framework?",[14,1402,1403],{},"Yes. Create a directory under .vercel\u002Foutput\u002Ffunctions with a .vc-config.json declaring the edge runtime and an entrypoint file, and route requests to it from config.json. The function receives standard Request objects and returns Responses.",[41,1405,1407],{"id":1406},"related","Related",[46,1409,1410,1419,1426,1433,1440],{},[49,1411,1412,1415,1416,1418],{},[1298,1413,1414],{},"Parent:"," ",[30,1417,33],{"href":32}," — the two platforms compared.",[49,1420,1421,1425],{},[30,1422,1424],{"href":1423},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-isr-vs-static-generation-for-ssgs\u002F","Vercel ISR vs Static Generation for SSGs"," — when static is the right choice.",[49,1427,1428,1432],{},[30,1429,1431],{"href":1430},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites\u002F","Netlify Edge Functions for Static Sites"," — the Netlify equivalent of edge logic.",[49,1434,1435,1439],{},[30,1436,1438],{"href":1437},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fbuild-caching-on-netlify-and-vercel\u002F","Build Caching on Netlify and Vercel"," — caching when building on the platform.",[49,1441,1442,1446],{},[30,1443,1445],{"href":1444},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fkeeping-redirects-working-after-an-ssg-migration\u002F","Keeping Redirects Working After an SSG Migration"," — the redirect data file.",[1448,1449,1450],"style",{},"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 .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}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 .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}",{"title":77,"searchDepth":254,"depth":254,"links":1452},[1453,1454,1455,1456,1457,1458,1459,1460,1461,1462,1463,1464,1470],{"id":43,"depth":254,"text":44},{"id":68,"depth":254,"text":69},{"id":225,"depth":254,"text":226},{"id":643,"depth":254,"text":644},{"id":706,"depth":254,"text":707},{"id":986,"depth":254,"text":987},{"id":1083,"depth":254,"text":1084},{"id":1116,"depth":254,"text":1117},{"id":1137,"depth":254,"text":1138},{"id":1291,"depth":254,"text":1292},{"id":1360,"depth":254,"text":1361},{"id":1373,"depth":254,"text":1374,"children":1465},[1466,1467,1468,1469],{"id":1378,"depth":275,"text":1379},{"id":1385,"depth":275,"text":1386},{"id":1392,"depth":275,"text":1393},{"id":1399,"depth":275,"text":1400},{"id":1406,"depth":254,"text":1407},[1472,1475,1478,1479],{"name":1473,"item":1474},"Home","\u002F",{"name":1476,"item":1477},"Production-Ready Deployment & CI\u002FCD for SSGs","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":33,"item":32},{"name":5,"item":1480},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-build-output-api-for-custom-ssgs\u002F","2026-09-25","Deploy any static site generator to Vercel with the Build Output API: static files, headers, redirects, cache rules and an optional edge function.","md",[1485,1486,1487,1488],{"q":1379,"a":1382},{"q":1386,"a":1389},{"q":1393,"a":1396},{"q":1400,"a":1403},{},true,"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-build-output-api-for-custom-ssgs",{"title":5,"description":1482},"production-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-build-output-api-for-custom-ssgs\u002Findex","article","PSm8A7UlCTnhH4rCRFdqG2aTY4IWUoTb_qURYru3yZo",[1497,1500,1503,1506,1509,1512,1515,1518,1521,1524,1527,1530,1533,1536,1539,1542,1545,1548,1551,1554,1557,1560,1563,1566,1569,1572,1575,1578,1581,1584,1587,1590,1593,1596,1599,1602,1605,1608,1611,1614,1617,1620,1623,1626,1629,1632,1635,1638,1641,1644,1647,1650,1653,1656,1659,1662,1665,1668,1671,1674,1677,1680,1683,1686,1689,1692,1695,1698,1701,1704,1707,1710,1713,1716,1719,1722,1725,1728,1730,1733,1736,1739,1742,1745,1748,1751,1754,1757,1760,1763,1766,1769,1772,1775,1778,1781,1784,1787,1790,1793,1796,1799,1802,1805,1808,1811,1814,1817,1820,1823,1826,1829,1832,1835,1838,1841,1844,1847,1850,1853,1856,1859,1862,1865,1868,1871,1874,1877,1880,1883,1886,1889,1892,1895,1898,1901,1904,1907,1910,1913,1916,1919,1922,1925,1928,1931,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,2340,2343,2346,2349,2352,2355,2358,2361,2364,2367,2370,2372,2375,2378,2381,2384,2387,2390,2393,2396,2399,2402,2405,2408,2411,2413,2416,2419,2422,2424,2427,2429,2432,2435,2436,2438,2441,2444,2447,2450,2453,2456,2459,2462,2465,2468,2471,2474,2477,2480,2483,2486,2489,2492,2495,2498,2501,2504,2507,2510,2513,2516,2519,2522,2525,2528,2531,2534,2537,2540,2543,2546,2549,2552,2555,2558,2561,2564,2567,2570,2573,2576,2579,2582,2585,2588,2591,2594,2597,2600,2603,2606,2609,2612,2615,2618,2621,2624,2626,2629,2632],{"path":1498,"title":1499},"\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":1501,"title":1502},"\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":1504,"title":1505},"\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":1507,"title":1508},"\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":1510,"title":1511},"\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":1513,"title":1514},"\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":1516,"title":1517},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1519,"title":1520},"\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":1522,"title":1523},"\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":1525,"title":1526},"\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":1528,"title":1529},"\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":1531,"title":1532},"\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":1534,"title":1535},"\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":1537,"title":1538},"\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":1540,"title":1541},"\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":1543,"title":1544},"\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":1546,"title":1547},"\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":1549,"title":1550},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1552,"title":1553},"\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":1555,"title":1556},"\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":1558,"title":1559},"\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":1561,"title":1562},"\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":1564,"title":1565},"\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":1567,"title":1568},"\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":1570,"title":1571},"\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":1573,"title":1574},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1576,"title":1577},"\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":1579,"title":1580},"\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":1582,"title":1583},"\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":1585,"title":1586},"\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":1588,"title":1589},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1591,"title":1592},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1594,"title":1595},"\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":1597,"title":1598},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1600,"title":1601},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1603,"title":1604},"\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":1606,"title":1607},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1609,"title":1610},"\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":1612,"title":1613},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1615,"title":1616},"\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":1618,"title":1619},"\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":1621,"title":1622},"\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":1624,"title":1625},"\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":1627,"title":1628},"\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":1630,"title":1631},"\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":1633,"title":1634},"\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":1636,"title":1637},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1639,"title":1640},"\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":1642,"title":1643},"\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":1645,"title":1646},"\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":1648,"title":1649},"\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":1651,"title":1652},"\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":1654,"title":1655},"\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":1657,"title":1658},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1660,"title":1661},"\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":1663,"title":1664},"\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":1666,"title":1667},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1669,"title":1670},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1672,"title":1673},"\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":1675,"title":1676},"\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":1678,"title":1679},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1681,"title":1682},"\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":1684,"title":1685},"\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":1687,"title":1688},"\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":1690,"title":1691},"\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":1693,"title":1694},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1696,"title":1697},"\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":1699,"title":1700},"\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":1702,"title":1703},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1705,"title":1706},"\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":1708,"title":1709},"\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":1711,"title":1712},"\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":1714,"title":1715},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1717,"title":1718},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1720,"title":1721},"\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":1723,"title":1724},"\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":1726,"title":1727},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1729,"title":1445},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fkeeping-redirects-working-after-an-ssg-migration",{"path":1731,"title":1732},"\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":1734,"title":1735},"\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":1737,"title":1738},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1740,"title":1741},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1743,"title":1744},"\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":1746,"title":1747},"\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":1749,"title":1750},"\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":1752,"title":1753},"\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":1755,"title":1756},"\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":1758,"title":1759},"\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":1761,"title":1762},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ffixing-404s-on-refresh-in-nextjs-static-export","Fixing 404s on Refresh in Next.js Static Export",{"path":1764,"title":1765},"\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":1767,"title":1768},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fhandling-dynamic-routes-in-nextjs-static-export","Handling Dynamic Routes in Next.js Static Export",{"path":1770,"title":1771},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1773,"title":1774},"\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":1776,"title":1777},"\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":1779,"title":1780},"\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":1782,"title":1783},"\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":1785,"title":1786},"\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":1788,"title":1789},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ftrailing-slash-and-basepath-in-nextjs-static-export","Trailing Slash and basePath in Next.js Static Export",{"path":1791,"title":1792},"\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":1794,"title":1795},"\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":1797,"title":1798},"\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":1800,"title":1801},"\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":1803,"title":1804},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1806,"title":1807},"\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":1809,"title":1810},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1812,"title":1813},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1815,"title":1816},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1818,"title":1819},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1821,"title":1822},"\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":1824,"title":1825},"\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":1827,"title":1828},"\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":1830,"title":1831},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1833,"title":1834},"\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":1836,"title":1837},"\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":1839,"title":1840},"\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":1842,"title":1843},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1845,"title":1846},"\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":1848,"title":1849},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1851,"title":1852},"\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":1854,"title":1855},"\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":1857,"title":1858},"\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":1860,"title":1861},"\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":1863,"title":1864},"\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":1866,"title":1867},"\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":1869,"title":1870},"\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":1872,"title":1873},"\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":1875,"title":1876},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Ffixing-soft-404s-on-static-hosts","Fixing Soft 404s on Static Hosts",{"path":1878,"title":1879},"\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":1881,"title":1882},"\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":1884,"title":1885},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1887,"title":1888},"\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":1890,"title":1891},"\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":1893,"title":1894},"\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":1896,"title":1897},"\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":1899,"title":1900},"\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":1902,"title":1903},"\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":1905,"title":1906},"\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":1908,"title":1909},"\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":1911,"title":1912},"\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":1914,"title":1915},"\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":1917,"title":1918},"\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":1920,"title":1921},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1923,"title":1924},"\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":1926,"title":1927},"\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":1929,"title":1930},"\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":1932,"title":651},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fstale-while-revalidate-for-static-html",{"path":1934,"title":1935},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1937,"title":1938},"\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":1940,"title":1941},"\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":1943,"title":1944},"\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":1946,"title":1947},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":1949,"title":1950},"\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":1952,"title":1953},"\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":1955,"title":1956},"\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":1958,"title":1959},"\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":1961,"title":1962},"\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":1964,"title":1965},"\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":1967,"title":1968},"\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":1970,"title":1971},"\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":1973,"title":1974},"\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":1976,"title":1977},"\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":1979,"title":1980},"\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":1982,"title":1983},"\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":1985,"title":1986},"\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":1988,"title":1989},"\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":1991,"title":1992},"\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":1994,"title":1995},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1997,"title":1998},"\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":2000,"title":2001},"\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":2003,"title":2004},"\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":2006,"title":2007},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":2009,"title":2010},"\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":2012,"title":2013},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":2015,"title":2016},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":2018,"title":2019},"\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":2021,"title":2022},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":2024,"title":2025},"\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":2027,"title":2028},"\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":2030,"title":2031},"\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":2033,"title":2034},"\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":2036,"title":2037},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":2039,"title":2040},"\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":2042,"title":2043},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":2045,"title":2046},"\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":2048,"title":2049},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":2051,"title":2052},"\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":2054,"title":2055},"\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":2057,"title":2058},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":2060,"title":2061},"\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":2063,"title":2064},"\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":2066,"title":2067},"\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":2069,"title":2070},"\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":2072,"title":2073},"\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":2075,"title":2076},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":2078,"title":2079},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":2081,"title":2082},"\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":2084,"title":2085},"\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":2087,"title":2088},"\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":2090,"title":2091},"\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":2093,"title":2094},"\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":2096,"title":2097},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":2099,"title":2100},"\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":2102,"title":2103},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":2105,"title":2106},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":2108,"title":2109},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":2111,"title":2112},"\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":2114,"title":2115},"\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":2117,"title":2118},"\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":2120,"title":2121},"\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":2123,"title":2124},"\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":2126,"title":2127},"\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":2129,"title":2130},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":2132,"title":2133},"\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":2135,"title":2136},"\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":2138,"title":2139},"\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":2141,"title":2142},"\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":2144,"title":2145},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":2147,"title":2148},"\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":2150,"title":2151},"\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":2153,"title":2154},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":2156,"title":2157},"\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":2159,"title":2160},"\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":2162,"title":2163},"\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":2165,"title":2166},"\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":2168,"title":2169},"\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":2171,"title":2172},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2174,"title":2175},"\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":2177,"title":2178},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2180,"title":2181},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2183,"title":2184},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2186,"title":2187},"\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":2189,"title":2190},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2192,"title":2193},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2195,"title":2196},"\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":2198,"title":2199},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2201,"title":2202},"\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":2204,"title":2205},"\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":2207,"title":2208},"\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":2210,"title":2211},"\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":2213,"title":2214},"\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":2216,"title":2217},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2219,"title":2220},"\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":2222,"title":2223},"\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":2225,"title":2226},"\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":2228,"title":2229},"\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":2231,"title":2232},"\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":2234,"title":2235},"\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":2237,"title":2238},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2240,"title":2241},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2243,"title":2244},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2246,"title":2247},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2249,"title":2250},"\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":2252,"title":2253},"\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":2255,"title":2256},"\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":2258,"title":2259},"\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":2261,"title":2262},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2264,"title":2265},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2267,"title":2268},"\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":2270,"title":2271},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2273,"title":2274},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2276,"title":2277},"\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":2279,"title":2280},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2282,"title":2283},"\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":2285,"title":2286},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2288,"title":2289},"\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":2291,"title":2292},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2294,"title":2295},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2297,"title":2298},"\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":2300,"title":2301},"\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":2303,"title":2304},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2306,"title":2307},"\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":2309,"title":2310},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2312,"title":2313},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2315,"title":2316},"\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":2318,"title":2319},"\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":2321,"title":2322},"\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":2324,"title":2325},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2327,"title":2328},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2330,"title":2331},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2333,"title":2334},"\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":2336,"title":2337},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2339,"title":1438},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fbuild-caching-on-netlify-and-vercel",{"path":2341,"title":2342},"\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":2344,"title":2345},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2347,"title":2348},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2350,"title":2351},"\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":2353,"title":2354},"\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":2356,"title":2357},"\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":2359,"title":2360},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2362,"title":2363},"\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":2365,"title":2366},"\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":2368,"title":2369},"\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":2371,"title":1476},"\u002Fproduction-ready-deployment-cicd-workflows",{"path":2373,"title":2374},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2376,"title":2377},"\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":2379,"title":2380},"\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":2382,"title":2383},"\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":2385,"title":2386},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2388,"title":2389},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2391,"title":2392},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2394,"title":2395},"\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":2397,"title":2398},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2400,"title":2401},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2403,"title":2404},"\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":2406,"title":2407},"\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":2409,"title":2410},"\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":2412,"title":38},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy",{"path":2414,"title":2415},"\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":2417,"title":2418},"\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":2420,"title":2421},"\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":2423,"title":33},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies",{"path":2425,"title":2426},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2428,"title":1431},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites",{"path":2430,"title":2431},"\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":2433,"title":2434},"\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":1491,"title":5},{"path":2437,"title":1424},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-isr-vs-static-generation-for-ssgs",{"path":2439,"title":2440},"\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":2442,"title":2443},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2445,"title":2446},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2448,"title":2449},"\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":2451,"title":2452},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2454,"title":2455},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2457,"title":2458},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2460,"title":2461},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2463,"title":2464},"\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":2466,"title":2467},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2469,"title":2470},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2472,"title":2473},"\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":2475,"title":2476},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2478,"title":2479},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2481,"title":2482},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2484,"title":2485},"\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":2487,"title":2488},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2490,"title":2491},"\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":2493,"title":2494},"\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":2496,"title":2497},"\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":2499,"title":2500},"\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":2502,"title":2503},"\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":2505,"title":2506},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2508,"title":2509},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2511,"title":2512},"\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":2514,"title":2515},"\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":2517,"title":2518},"\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":2520,"title":2521},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2523,"title":2524},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2526,"title":2527},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2529,"title":2530},"\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":2532,"title":2533},"\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":2535,"title":2536},"\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":2538,"title":2539},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2541,"title":2542},"\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":2544,"title":2545},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2547,"title":2548},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2550,"title":2551},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2553,"title":2554},"\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":2556,"title":2557},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2559,"title":2560},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2562,"title":2563},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2565,"title":2566},"\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":2568,"title":2569},"\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":2571,"title":2572},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2574,"title":2575},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2577,"title":2578},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2580,"title":2581},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2583,"title":2584},"\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":2586,"title":2587},"\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":2589,"title":2590},"\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":2592,"title":2593},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2595,"title":2596},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2598,"title":2599},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2601,"title":2602},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2604,"title":2605},"\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":2607,"title":2608},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2610,"title":2611},"\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":2613,"title":2614},"\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":2616,"title":2617},"\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":2619,"title":2620},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2622,"title":2623},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2625,"title":1112},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy",{"path":2627,"title":2628},"\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":2630,"title":2631},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2633,"title":2634},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2636,"tools":2640},{"label":2637,"plural":2638,"u":2639},"How-to","How-tos","\u002Fguides\u002Fhow-to\u002F",[2641,2644],{"label":2642,"u":2643},"Netlify","\u002Ftools\u002Fnetlify\u002F",{"label":2645,"u":2646},"Vercel","\u002Ftools\u002Fvercel\u002F",1790943196062]