[{"data":1,"prerenderedAt":2568},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy":3,"all-docs-nav":1416,"filed:\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy":2555},{"id":4,"title":5,"body":6,"breadcrumb":1391,"dateModified":1401,"datePublished":1401,"description":1402,"extension":1403,"faq":1404,"meta":1409,"navigation":1410,"path":1411,"seo":1412,"slug":12,"stem":1413,"type":1414,"__hash__":1415},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy\u002Findex.md","Configuring Vercel for Hugo and Eleventy",{"type":7,"value":8,"toc":1371},"minimark",[9,13,17,31,36,52,56,62,188,191,257,275,397,401,423,458,499,581,604,608,619,836,854,858,868,990,1011,1118,1122,1148,1152,1167,1171,1199,1203,1225,1229,1278,1282,1291,1295,1300,1303,1307,1310,1314,1317,1321,1324,1328,1367],[10,11,5],"h1",{"id":12},"configuring-vercel-for-hugo-and-eleventy",[14,15,16],"p",{},"Vercel is best known for Next.js, but it deploys any static site generator, and Hugo and Eleventy work well there with a little configuration. The defaults get a site online quickly, yet they differ from what these generators expect in a few places — the Hugo version on the build image, trailing slash handling, where redirects and headers live — and those differences show up as broken themes, duplicate URLs or missing security headers after launch.",[14,18,19,20,24,25,30],{},"This guide configures a Hugo site and an Eleventy site on Vercel for production: pinned versions, build commands and output directories, clean URLs and trailing slashes, headers, redirects and caching, all in ",[21,22,23],"code",{},"vercel.json"," so the setup is versioned with the code. It is part of ",[26,27,29],"a",{"href":28},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002F","Netlify vs Vercel Deployment Strategies",".",[32,33,35],"h2",{"id":34},"prerequisites","Prerequisites",[37,38,39,43,49],"ul",{},[40,41,42],"li",{},"A Hugo or Eleventy site in a Git repository connected to a Vercel project.",[40,44,45,46,30],{},"The Vercel CLI for local checks: ",[21,47,48],{},"npm install -D vercel",[40,50,51],{},"Knowledge of the canonical URL form your site uses — with or without trailing slashes.",[32,53,55],{"id":54},"build-settings","Build Settings",[14,57,58,59,61],{},"Vercel detects both generators and applies a framework preset. Make the important settings explicit in ",[21,60,23],{}," so they do not depend on dashboard state:",[63,64,69],"pre",{"className":65,"code":66,"language":67,"meta":68,"style":68},"language-json shiki shiki-themes github-light github-dark","{\n  \"$schema\": \"https:\u002F\u002Fopenapi.vercel.sh\u002Fvercel.json\",\n  \"framework\": \"hugo\",\n  \"buildCommand\": \"hugo --gc --minify\",\n  \"outputDirectory\": \"public\",\n  \"build\": {\n    \"env\": { \"HUGO_VERSION\": \"0.134.0\", \"HUGO_ENV\": \"production\" }\n  }\n}\n","json","",[21,70,71,80,97,110,123,136,145,176,182],{"__ignoreMap":68},[72,73,76],"span",{"class":74,"line":75},"line",1,[72,77,79],{"class":78},"sVt8B","{\n",[72,81,83,87,90,94],{"class":74,"line":82},2,[72,84,86],{"class":85},"sj4cs","  \"$schema\"",[72,88,89],{"class":78},": ",[72,91,93],{"class":92},"sZZnC","\"https:\u002F\u002Fopenapi.vercel.sh\u002Fvercel.json\"",[72,95,96],{"class":78},",\n",[72,98,100,103,105,108],{"class":74,"line":99},3,[72,101,102],{"class":85},"  \"framework\"",[72,104,89],{"class":78},[72,106,107],{"class":92},"\"hugo\"",[72,109,96],{"class":78},[72,111,113,116,118,121],{"class":74,"line":112},4,[72,114,115],{"class":85},"  \"buildCommand\"",[72,117,89],{"class":78},[72,119,120],{"class":92},"\"hugo --gc --minify\"",[72,122,96],{"class":78},[72,124,126,129,131,134],{"class":74,"line":125},5,[72,127,128],{"class":85},"  \"outputDirectory\"",[72,130,89],{"class":78},[72,132,133],{"class":92},"\"public\"",[72,135,96],{"class":78},[72,137,139,142],{"class":74,"line":138},6,[72,140,141],{"class":85},"  \"build\"",[72,143,144],{"class":78},": {\n",[72,146,148,151,154,157,159,162,165,168,170,173],{"class":74,"line":147},7,[72,149,150],{"class":85},"    \"env\"",[72,152,153],{"class":78},": { ",[72,155,156],{"class":85},"\"HUGO_VERSION\"",[72,158,89],{"class":78},[72,160,161],{"class":92},"\"0.134.0\"",[72,163,164],{"class":78},", ",[72,166,167],{"class":85},"\"HUGO_ENV\"",[72,169,89],{"class":78},[72,171,172],{"class":92},"\"production\"",[72,174,175],{"class":78}," }\n",[72,177,179],{"class":74,"line":178},8,[72,180,181],{"class":78},"  }\n",[72,183,185],{"class":74,"line":184},9,[72,186,187],{"class":78},"}\n",[14,189,190],{},"For Eleventy:",[63,192,194],{"className":65,"code":193,"language":67,"meta":68,"style":68},"{\n  \"$schema\": \"https:\u002F\u002Fopenapi.vercel.sh\u002Fvercel.json\",\n  \"framework\": \"eleventy\",\n  \"installCommand\": \"npm ci\",\n  \"buildCommand\": \"npx @11ty\u002Feleventy\",\n  \"outputDirectory\": \"_site\"\n}\n",[21,195,196,200,210,221,233,244,253],{"__ignoreMap":68},[72,197,198],{"class":74,"line":75},[72,199,79],{"class":78},[72,201,202,204,206,208],{"class":74,"line":82},[72,203,86],{"class":85},[72,205,89],{"class":78},[72,207,93],{"class":92},[72,209,96],{"class":78},[72,211,212,214,216,219],{"class":74,"line":99},[72,213,102],{"class":85},[72,215,89],{"class":78},[72,217,218],{"class":92},"\"eleventy\"",[72,220,96],{"class":78},[72,222,223,226,228,231],{"class":74,"line":112},[72,224,225],{"class":85},"  \"installCommand\"",[72,227,89],{"class":78},[72,229,230],{"class":92},"\"npm ci\"",[72,232,96],{"class":78},[72,234,235,237,239,242],{"class":74,"line":125},[72,236,115],{"class":85},[72,238,89],{"class":78},[72,240,241],{"class":92},"\"npx @11ty\u002Feleventy\"",[72,243,96],{"class":78},[72,245,246,248,250],{"class":74,"line":138},[72,247,128],{"class":85},[72,249,89],{"class":78},[72,251,252],{"class":92},"\"_site\"\n",[72,254,255],{"class":74,"line":147},[72,256,187],{"class":78},[14,258,259,260,263,264,267,268,271,272,30],{},"The single most important line for Hugo is ",[21,261,262],{},"HUGO_VERSION",". Vercel's build image ships an older Hugo by default, and many themes require recent features; an unpinned build can fail or, worse, succeed with different output than your local machine. Use the extended edition if your theme compiles Sass. For Eleventy, pin Node with an ",[21,265,266],{},"engines"," field in ",[21,269,270],{},"package.json"," or ",[21,273,274],{},".nvmrc",[276,277,278,393],"figure",{},[279,280,287,288,287,292,287,296,287,303],"svg",{"viewBox":281,"role":282,"ariaLabelledBy":283,"xmlns":286},"0 0 760 270","img",[284,285],"vhe-cfg-title","vhe-cfg-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[289,290,291],"title",{"id":284},"Where each setting lives for Hugo and Eleventy on Vercel",[293,294,295],"desc",{"id":285},"A table. Build command: hugo --gc --minify, or npx @11ty\u002Feleventy. Output directory: public, or _site. Version pin: HUGO_VERSION env var, or Node engines field. Clean URLs and trailing slash: vercel.json for both. Headers and redirects: vercel.json for both, not _headers or _redirects files.",[297,298],"rect",{"x":299,"y":299,"width":300,"height":301,"fill":302},"0","760","270","#ffffff",[304,305,307,308,307,316,307,322,307,328,307,333,307,340,307,344,307,348,307,351,307,355,307,358,307,361,307,365,307,368,307,371,307,375,307,378,307,380,307,384,307,386,307,388,287],"g",{"style":306},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[309,310,315],"text",{"x":311,"y":312,"fill":313,"style":314},"380","26","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Settings to make explicit",[309,317,321],{"x":318,"y":319,"fill":313,"style":320},"40","58","font-weight:700","setting",[309,323,327],{"x":324,"y":319,"fill":325,"style":326},"300","#6a4c93","font-weight:700;text-anchor:middle","Hugo",[309,329,332],{"x":330,"y":319,"fill":331,"style":326},"560","#166a9e","Eleventy",[74,334],{"x1":335,"y1":336,"x2":337,"y2":336,"stroke":338,"style":339},"30","68","730","#556071","stroke-width:1px",[309,341,343],{"x":318,"y":342,"fill":313},"96","build command",[309,345,347],{"x":324,"y":342,"fill":313,"style":346},"text-anchor:middle","hugo --gc --minify",[309,349,350],{"x":330,"y":342,"fill":313,"style":346},"npx @11ty\u002Feleventy",[309,352,354],{"x":318,"y":353,"fill":313},"126","output directory",[309,356,357],{"x":324,"y":353,"fill":313,"style":346},"public",[309,359,360],{"x":330,"y":353,"fill":313,"style":346},"_site",[309,362,364],{"x":318,"y":363,"fill":313},"156","version pin",[309,366,367],{"x":324,"y":363,"fill":313,"style":346},"HUGO_VERSION env",[309,369,370],{"x":330,"y":363,"fill":313,"style":346},"Node via engines \u002F .nvmrc",[309,372,374],{"x":318,"y":373,"fill":313},"186","trailing slash",[309,376,377],{"x":324,"y":373,"fill":313,"style":346},"vercel.json: true",[309,379,377],{"x":330,"y":373,"fill":313,"style":346},[309,381,383],{"x":318,"y":382,"fill":313},"216","headers, redirects",[309,385,23],{"x":324,"y":382,"fill":313,"style":346},[309,387,23],{"x":330,"y":382,"fill":313,"style":346},[309,389,392],{"x":311,"y":390,"fill":338,"style":391},"254","font-size:11px;text-anchor:middle","_headers and _redirects files from other hosts are ignored on Vercel",[394,395,396],"figcaption",{},"Put every setting in vercel.json so a new project or a teammate gets the same result.",[32,398,400],{"id":399},"clean-urls-and-trailing-slashes","Clean URLs and Trailing Slashes",[14,402,403,404,407,408,411,412,415,416,418,419,422],{},"Hugo and Eleventy both write pages as ",[21,405,406],{},"folder\u002Findex.html"," and link to them as ",[21,409,410],{},"\u002Ffolder\u002F",". Vercel's defaults serve ",[21,413,414],{},"\u002Ffolder\u002Findex.html"," at ",[21,417,410],{}," but also at ",[21,420,421],{},"\u002Ffolder",", creating two URLs for each page. Tell Vercel which form is canonical:",[63,424,426],{"className":65,"code":425,"language":67,"meta":68,"style":68},"{\n  \"cleanUrls\": true,\n  \"trailingSlash\": true\n}\n",[21,427,428,432,444,454],{"__ignoreMap":68},[72,429,430],{"class":74,"line":75},[72,431,79],{"class":78},[72,433,434,437,439,442],{"class":74,"line":82},[72,435,436],{"class":85},"  \"cleanUrls\"",[72,438,89],{"class":78},[72,440,441],{"class":85},"true",[72,443,96],{"class":78},[72,445,446,449,451],{"class":74,"line":99},[72,447,448],{"class":85},"  \"trailingSlash\"",[72,450,89],{"class":78},[72,452,453],{"class":85},"true\n",[72,455,456],{"class":74,"line":112},[72,457,187],{"class":78},[14,459,460,461,164,464,467,468,471,472,475,476,479,480,483,484,487,488,491,492,494,495,498],{},"With ",[21,462,463],{},"trailingSlash: true",[21,465,466],{},"\u002Fdocs\u002Finstall"," redirects with a 308 to ",[21,469,470],{},"\u002Fdocs\u002Finstall\u002F",", matching the generator's links and canonical tags. ",[21,473,474],{},"cleanUrls: true"," removes ",[21,477,478],{},".html"," from any flat files and redirects ",[21,481,482],{},"\u002Fabout.html"," to ",[21,485,486],{},"\u002Fabout\u002F",". If your Hugo config uses ",[21,489,490],{},"uglyURLs"," or your Eleventy permalinks end in ",[21,493,478],{},", set ",[21,496,497],{},"trailingSlash: false"," instead and be consistent. Mismatched settings are a common source of duplicate URLs in Search Console.",[276,500,501,578],{},[279,502,287,507,287,510,287,513,287,516],{"viewBox":503,"role":282,"ariaLabelledBy":504,"xmlns":286},"0 0 760 230",[505,506],"vhe-slash-title","vhe-slash-desc",[289,508,509],{"id":505},"Responses for a page with and without trailingSlash set",[293,511,512],{"id":506},"With default settings, both \u002Fdocs\u002Finstall and \u002Fdocs\u002Finstall\u002F return 200 with the same content, creating a duplicate. With trailingSlash true, \u002Fdocs\u002Finstall returns a 308 redirect to \u002Fdocs\u002Finstall\u002F, which returns 200, leaving one canonical URL.",[297,514],{"x":299,"y":299,"width":300,"height":515,"fill":302},"230",[304,517,307,518,307,521,307,529,307,535,307,539,307,544,307,547,307,549,307,553,307,557,307,560,307,563,307,567,307,569,307,571,307,574,287],{"style":306},[309,519,520],{"x":311,"y":312,"fill":313,"style":314},"One page, two request forms",[297,522],{"x":335,"y":523,"width":524,"height":525,"rx":526,"fill":527,"style":528,"stroke":527},"46","330","150","8","#d83b41","fill-opacity:0.06",[309,530,534],{"x":531,"y":532,"fill":533,"style":326},"195","70","#b32b30","default settings",[309,536,466],{"x":537,"y":538,"fill":313},"48","102",[309,540,543],{"x":541,"y":538,"fill":313,"style":542},"340","text-anchor:end","200",[309,545,470],{"x":537,"y":546,"fill":313},"130",[309,548,543],{"x":541,"y":546,"fill":313,"style":542},[309,550,552],{"x":537,"y":551,"fill":533,"style":320},"172","two indexable URLs, same content",[297,554],{"x":555,"y":523,"width":524,"height":525,"rx":526,"fill":556,"style":528,"stroke":556},"400","#3f6410",[309,558,463],{"x":559,"y":532,"fill":556,"style":326},"565",[309,561,466],{"x":562,"y":538,"fill":313},"418",[309,564,566],{"x":565,"y":538,"fill":313,"style":542},"710","308 → \u002Fdocs\u002Finstall\u002F",[309,568,470],{"x":562,"y":546,"fill":313},[309,570,543],{"x":565,"y":546,"fill":313,"style":542},[309,572,573],{"x":562,"y":551,"fill":556,"style":320},"one canonical URL",[309,575,577],{"x":311,"y":576,"fill":338,"style":391},"220","match the form your generator uses in links, canonical tags and the sitemap",[394,579,580],{},"A one-line setting turns every page's duplicate into a redirect.",[14,582,583,584,587,588,591,592,595,596,599,600,603],{},"After changing the setting, check three things on a preview deployment: that internal links in the HTML already use the canonical form (so readers never hit the redirect), that ",[21,585,586],{},"\u003Clink rel=\"canonical\">"," matches it, and that the sitemap lists only canonical URLs. Hugo's ",[21,589,590],{},"canonifyURLs"," and ",[21,593,594],{},"relativeURLs"," settings, and Eleventy's ",[21,597,598],{},"url"," filter with a correctly set ",[21,601,602],{},"pathPrefix",", produce consistent links if they are configured once at the site level rather than per template.",[32,605,607],{"id":606},"headers-and-caching","Headers and Caching",[14,609,610,611,614,615,618],{},"Vercel serves static files with ",[21,612,613],{},"Cache-Control: public, max-age=0, must-revalidate"," by default, relying on its CDN to cache them. For fingerprinted assets — Hugo Pipes with ",[21,616,617],{},"fingerprint",", or an Eleventy asset pipeline that adds hashes — tell browsers to keep them for a year:",[63,620,622],{"className":65,"code":621,"language":67,"meta":68,"style":68},"{\n  \"headers\": [\n    {\n      \"source\": \"\u002F(.*)\\\\.([a-f0-9]{8,})\\\\.(css|js|woff2|avif|webp)\",\n      \"headers\": [{ \"key\": \"Cache-Control\", \"value\": \"public, max-age=31536000, immutable\" }]\n    },\n    {\n      \"source\": \"\u002F(.*)\",\n      \"headers\": [\n        { \"key\": \"Strict-Transport-Security\", \"value\": \"max-age=63072000; includeSubDomains\" },\n        { \"key\": \"X-Content-Type-Options\", \"value\": \"nosniff\" },\n        { \"key\": \"Referrer-Policy\", \"value\": \"strict-origin-when-cross-origin\" },\n        { \"key\": \"Content-Security-Policy\", \"value\": \"default-src 'self'; img-src 'self' data:\" }\n      ]\n    }\n  ]\n}\n",[21,623,624,628,636,641,664,693,698,702,713,719,744,767,790,813,819,825,831],{"__ignoreMap":68},[72,625,626],{"class":74,"line":75},[72,627,79],{"class":78},[72,629,630,633],{"class":74,"line":82},[72,631,632],{"class":85},"  \"headers\"",[72,634,635],{"class":78},": [\n",[72,637,638],{"class":74,"line":99},[72,639,640],{"class":78},"    {\n",[72,642,643,646,648,651,654,657,659,662],{"class":74,"line":112},[72,644,645],{"class":85},"      \"source\"",[72,647,89],{"class":78},[72,649,650],{"class":92},"\"\u002F(.*)",[72,652,653],{"class":85},"\\\\",[72,655,656],{"class":92},".([a-f0-9]{8,})",[72,658,653],{"class":85},[72,660,661],{"class":92},".(css|js|woff2|avif|webp)\"",[72,663,96],{"class":78},[72,665,666,669,672,675,677,680,682,685,687,690],{"class":74,"line":125},[72,667,668],{"class":85},"      \"headers\"",[72,670,671],{"class":78},": [{ ",[72,673,674],{"class":85},"\"key\"",[72,676,89],{"class":78},[72,678,679],{"class":92},"\"Cache-Control\"",[72,681,164],{"class":78},[72,683,684],{"class":85},"\"value\"",[72,686,89],{"class":78},[72,688,689],{"class":92},"\"public, max-age=31536000, immutable\"",[72,691,692],{"class":78}," }]\n",[72,694,695],{"class":74,"line":138},[72,696,697],{"class":78},"    },\n",[72,699,700],{"class":74,"line":147},[72,701,640],{"class":78},[72,703,704,706,708,711],{"class":74,"line":178},[72,705,645],{"class":85},[72,707,89],{"class":78},[72,709,710],{"class":92},"\"\u002F(.*)\"",[72,712,96],{"class":78},[72,714,715,717],{"class":74,"line":184},[72,716,668],{"class":85},[72,718,635],{"class":78},[72,720,722,725,727,729,732,734,736,738,741],{"class":74,"line":721},10,[72,723,724],{"class":78},"        { ",[72,726,674],{"class":85},[72,728,89],{"class":78},[72,730,731],{"class":92},"\"Strict-Transport-Security\"",[72,733,164],{"class":78},[72,735,684],{"class":85},[72,737,89],{"class":78},[72,739,740],{"class":92},"\"max-age=63072000; includeSubDomains\"",[72,742,743],{"class":78}," },\n",[72,745,747,749,751,753,756,758,760,762,765],{"class":74,"line":746},11,[72,748,724],{"class":78},[72,750,674],{"class":85},[72,752,89],{"class":78},[72,754,755],{"class":92},"\"X-Content-Type-Options\"",[72,757,164],{"class":78},[72,759,684],{"class":85},[72,761,89],{"class":78},[72,763,764],{"class":92},"\"nosniff\"",[72,766,743],{"class":78},[72,768,770,772,774,776,779,781,783,785,788],{"class":74,"line":769},12,[72,771,724],{"class":78},[72,773,674],{"class":85},[72,775,89],{"class":78},[72,777,778],{"class":92},"\"Referrer-Policy\"",[72,780,164],{"class":78},[72,782,684],{"class":85},[72,784,89],{"class":78},[72,786,787],{"class":92},"\"strict-origin-when-cross-origin\"",[72,789,743],{"class":78},[72,791,793,795,797,799,802,804,806,808,811],{"class":74,"line":792},13,[72,794,724],{"class":78},[72,796,674],{"class":85},[72,798,89],{"class":78},[72,800,801],{"class":92},"\"Content-Security-Policy\"",[72,803,164],{"class":78},[72,805,684],{"class":85},[72,807,89],{"class":78},[72,809,810],{"class":92},"\"default-src 'self'; img-src 'self' data:\"",[72,812,175],{"class":78},[72,814,816],{"class":74,"line":815},14,[72,817,818],{"class":78},"      ]\n",[72,820,822],{"class":74,"line":821},15,[72,823,824],{"class":78},"    }\n",[72,826,828],{"class":74,"line":827},16,[72,829,830],{"class":78},"  ]\n",[72,832,834],{"class":74,"line":833},17,[72,835,187],{"class":78},[14,837,838,841,842,845,846,591,850,30],{},[21,839,840],{},"source"," patterns use path-to-regexp syntax, so test them carefully; a pattern that does not match silently applies nothing. Check headers on a preview deployment with ",[21,843,844],{},"curl -I"," before promoting. Background on the values is in ",[26,847,849],{"href":848},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-busting-with-content-hashed-filenames\u002F","Cache Busting with Content-Hashed Filenames",[26,851,853],{"href":852},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fwriting-a-content-security-policy-for-a-static-site\u002F","Writing a Content Security Policy for a Static Site",[32,855,857],{"id":856},"redirects-and-rewrites","Redirects and Rewrites",[14,859,860,861,864,865,867],{},"Redirects move from ",[21,862,863],{},"_redirects"," files, which Vercel ignores, into ",[21,866,23],{},":",[63,869,871],{"className":65,"code":870,"language":67,"meta":68,"style":68},"{\n  \"redirects\": [\n    { \"source\": \"\u002Fblog\u002F:year\u002F:month\u002F:slug\u002F\", \"destination\": \"\u002Fposts\u002F:slug\u002F\", \"permanent\": true },\n    { \"source\": \"\u002Fold-docs\u002F:path*\", \"destination\": \"\u002Fdocs\u002F:path*\", \"permanent\": true }\n  ],\n  \"rewrites\": [\n    { \"source\": \"\u002Fapi\u002F:path*\", \"destination\": \"https:\u002F\u002Fapi.example.com\u002F:path*\" }\n  ]\n}\n",[21,872,873,877,884,918,948,953,960,982,986],{"__ignoreMap":68},[72,874,875],{"class":74,"line":75},[72,876,79],{"class":78},[72,878,879,882],{"class":74,"line":82},[72,880,881],{"class":85},"  \"redirects\"",[72,883,635],{"class":78},[72,885,886,889,892,894,897,899,902,904,907,909,912,914,916],{"class":74,"line":99},[72,887,888],{"class":78},"    { ",[72,890,891],{"class":85},"\"source\"",[72,893,89],{"class":78},[72,895,896],{"class":92},"\"\u002Fblog\u002F:year\u002F:month\u002F:slug\u002F\"",[72,898,164],{"class":78},[72,900,901],{"class":85},"\"destination\"",[72,903,89],{"class":78},[72,905,906],{"class":92},"\"\u002Fposts\u002F:slug\u002F\"",[72,908,164],{"class":78},[72,910,911],{"class":85},"\"permanent\"",[72,913,89],{"class":78},[72,915,441],{"class":85},[72,917,743],{"class":78},[72,919,920,922,924,926,929,931,933,935,938,940,942,944,946],{"class":74,"line":112},[72,921,888],{"class":78},[72,923,891],{"class":85},[72,925,89],{"class":78},[72,927,928],{"class":92},"\"\u002Fold-docs\u002F:path*\"",[72,930,164],{"class":78},[72,932,901],{"class":85},[72,934,89],{"class":78},[72,936,937],{"class":92},"\"\u002Fdocs\u002F:path*\"",[72,939,164],{"class":78},[72,941,911],{"class":85},[72,943,89],{"class":78},[72,945,441],{"class":85},[72,947,175],{"class":78},[72,949,950],{"class":74,"line":125},[72,951,952],{"class":78},"  ],\n",[72,954,955,958],{"class":74,"line":138},[72,956,957],{"class":85},"  \"rewrites\"",[72,959,635],{"class":78},[72,961,962,964,966,968,971,973,975,977,980],{"class":74,"line":147},[72,963,888],{"class":78},[72,965,891],{"class":85},[72,967,89],{"class":78},[72,969,970],{"class":92},"\"\u002Fapi\u002F:path*\"",[72,972,164],{"class":78},[72,974,901],{"class":85},[72,976,89],{"class":78},[72,978,979],{"class":92},"\"https:\u002F\u002Fapi.example.com\u002F:path*\"",[72,981,175],{"class":78},[72,983,984],{"class":74,"line":178},[72,985,830],{"class":78},[72,987,988],{"class":74,"line":184},[72,989,187],{"class":78},[14,991,992,995,996,999,1000,1002,1003,1006,1007,1010],{},[21,993,994],{},"permanent: true"," sends a 308; ",[21,997,998],{},"false"," sends a 307. Vercel limits a project to 2,048 redirects in ",[21,1001,23],{},". Beyond that, use a single rewrite to an edge function that looks paths up in a JSON map, or Vercel's bulk redirects where available. Hugo's ",[21,1004,1005],{},"aliases"," front matter generates meta-refresh HTML pages for moved content; on Vercel, prefer real redirects for better behaviour with search engines and set ",[21,1008,1009],{},"disableAliases = true"," once they are in place.",[276,1012,1013,1115],{},[279,1014,287,1019,287,1022,287,1025,287,1028,287,1044],{"viewBox":1015,"role":282,"ariaLabelledBy":1016,"xmlns":286},"0 0 760 250",[1017,1018],"vhe-mig-title","vhe-mig-desc",[289,1020,1021],{"id":1017},"Moving Netlify-style files to vercel.json",[293,1023,1024],{"id":1018},"A _headers file maps to the headers array in vercel.json. A _redirects file with 301 rules maps to redirects with permanent true. 200 proxy rules map to rewrites. Hugo aliases meta-refresh pages are replaced by redirects entries.",[297,1026],{"x":299,"y":299,"width":300,"height":1027,"fill":302},"250",[1029,1030,307,1031,287],"defs",{},[1032,1033,1040],"marker",{"id":1034,"viewBox":1035,"refX":1036,"refY":1037,"markerWidth":1038,"markerHeight":1038,"orient":1039},"vhe-mig-arrow","0 0 10 10","9","5","7","auto-start-reverse",[1041,1042],"path",{"d":1043,"fill":338},"M0,0 L10,5 L0,10 z",[304,1045,307,1046,307,1049,307,1057,307,1061,307,1064,307,1068,307,1070,307,1074,307,1076,307,1080,307,1083,307,1087,307,1089,307,1092,307,1094,307,1097,307,1099,307,1102,307,1106,307,1109,307,1112,287],{"style":306},[309,1047,1048],{"x":311,"y":312,"fill":313,"style":314},"Where each rule moves",[297,1050],{"x":335,"y":1051,"width":1052,"height":1053,"rx":1054,"fill":1055,"style":1056,"stroke":1055},"50","240","36","6","#8a6d0f","fill-opacity:0.1",[309,1058,1060],{"x":525,"y":1059,"fill":313,"style":346},"73","_headers",[297,1062],{"x":335,"y":1063,"width":1052,"height":1053,"rx":1054,"fill":1055,"style":1056,"stroke":1055},"100",[309,1065,1067],{"x":525,"y":1066,"fill":313,"style":346},"123","_redirects: 301 \u002F 302 rules",[297,1069],{"x":335,"y":525,"width":1052,"height":1053,"rx":1054,"fill":1055,"style":1056,"stroke":1055},[309,1071,1073],{"x":525,"y":1072,"fill":313,"style":346},"173","_redirects: 200 proxy rules",[297,1075],{"x":335,"y":543,"width":1052,"height":1053,"rx":1054,"fill":1055,"style":1056,"stroke":1055},[309,1077,1079],{"x":525,"y":1078,"fill":313,"style":346},"223","Hugo aliases (meta refresh)",[297,1081],{"x":1082,"y":1051,"width":1052,"height":1053,"rx":1054,"fill":556,"style":1056,"stroke":556},"490",[309,1084,1086],{"x":1085,"y":1059,"fill":313,"style":346},"610","vercel.json headers[]",[297,1088],{"x":1082,"y":1063,"width":1052,"height":1053,"rx":1054,"fill":556,"style":1056,"stroke":556},[309,1090,1091],{"x":1085,"y":1066,"fill":313,"style":346},"redirects[] (permanent)",[297,1093],{"x":1082,"y":525,"width":1052,"height":1053,"rx":1054,"fill":556,"style":1056,"stroke":556},[309,1095,1096],{"x":1085,"y":1072,"fill":313,"style":346},"rewrites[]",[297,1098],{"x":1082,"y":543,"width":1052,"height":1053,"rx":1054,"fill":556,"style":1056,"stroke":556},[309,1100,1101],{"x":1085,"y":1078,"fill":313,"style":346},"redirects[] (real 308s)",[74,1103],{"x1":301,"y1":336,"x2":1104,"y2":336,"stroke":338,"style":1105},"486","stroke-width:1.5px;marker-end:url(#vhe-mig-arrow)",[74,1107],{"x1":301,"y1":1108,"x2":1104,"y2":1108,"stroke":338,"style":1105},"118",[74,1110],{"x1":301,"y1":1111,"x2":1104,"y2":1111,"stroke":338,"style":1105},"168",[74,1113],{"x1":301,"y1":1114,"x2":1104,"y2":1114,"stroke":338,"style":1105},"218",[394,1116,1117],{},"A small script can translate an existing _redirects file into vercel.json entries.",[32,1119,1121],{"id":1120},"previews-and-environment-specific-output","Previews and Environment-Specific Output",[14,1123,1124,1125,591,1128,1131,1132,1135,1136,1139,1140,1143,1144,30],{},"Every push to a non-production branch gets a preview URL. Use Vercel's system environment variables to change build output per environment: Hugo can read ",[21,1126,1127],{},"VERCEL_ENV",[21,1129,1130],{},"VERCEL_URL"," through ",[21,1133,1134],{},"os.Getenv"," in templates or be given ",[21,1137,1138],{},"--baseURL \"https:\u002F\u002F$VERCEL_URL\u002F\""," in the build command for previews, so absolute links and canonical tags point at the preview instead of production. Eleventy can read the same variables in a global data file. Add ",[21,1141,1142],{},"X-Robots-Tag: noindex"," for previews with a header rule conditioned on the host, or with Vercel's default preview protection. More on preview workflows in ",[26,1145,1147],{"href":1146},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002F","Preview Environments for Pull Requests",[32,1149,1151],{"id":1150},"deploying-from-ci-instead-of-the-git-integration","Deploying From CI Instead of the Git Integration",[14,1153,1154,1155,1158,1159,1162,1163,1166],{},"The Git integration builds on Vercel's infrastructure, which is simple but means your build runs in an image you do not control. For stricter setups, build in your own CI and upload only the output: ",[21,1156,1157],{},"vercel pull --environment=production"," fetches project settings, ",[21,1160,1161],{},"vercel build --prod"," produces the Build Output API folder locally, and ",[21,1164,1165],{},"vercel deploy --prebuilt --prod"," uploads it. The same checks that run on pull requests — link checks, Lighthouse, HTML validation — then run against exactly the files that are deployed, and the Hugo or Node version is whatever your CI pins. Disable automatic Git deployments in the project settings so the two paths do not race each other.",[32,1168,1170],{"id":1169},"build-caching","Build Caching",[14,1172,1173,1174,1177,1178,1181,1182,1185,1186,1189,1190,1193,1194,1198],{},"Vercel caches ",[21,1175,1176],{},"node_modules"," between builds automatically for Eleventy. For Hugo, it caches the build image but not Hugo's own ",[21,1179,1180],{},"resources\u002F_gen"," folder, so image processing reruns every build unless ",[21,1183,1184],{},"resources\u002F"," is committed to the repository — which many Hugo sites do for exactly this reason. For Eleventy image processing, point ",[21,1187,1188],{},"@11ty\u002Feleventy-img","'s cache at ",[21,1191,1192],{},".cache",", which Vercel preserves between builds. See ",[26,1195,1197],{"href":1196},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fcaching-hugo-builds-in-github-actions\u002F","Caching Hugo Builds in GitHub Actions"," for the equivalent outside Vercel.",[32,1200,1202],{"id":1201},"measured-impact","Measured Impact",[14,1204,1205,1206,1208,1209,1211,1212,1214,1215,1217,1218,1220,1221,1224],{},"A 900-page Hugo documentation site moved from Netlify to Vercel. The first build failed because the default Hugo version predated the theme's minimum; pinning ",[21,1207,262],{}," fixed it. A header and redirect conversion script translated 410 ",[21,1210,863],{}," lines and 12 ",[21,1213,1060],{}," rules into ",[21,1216,23],{},". Setting ",[21,1219,463],{}," removed 900 duplicate URL pairs that the first deploy had exposed. After cutover, TTFB and cache hit rates were within a few percent of the previous host, and preview URLs with ",[21,1222,1223],{},"noindex"," replaced the old deploy previews.",[32,1226,1228],{"id":1227},"pitfalls-rollback","Pitfalls & Rollback",[37,1230,1231,1241,1251,1260,1269],{},[40,1232,1233,1237,1238,1240],{},[1234,1235,1236],"strong",{},"Unpinned Hugo."," Always set ",[21,1239,262],{},", and the extended edition if needed.",[40,1242,1243,1250],{},[1234,1244,1245,1246,591,1248,30],{},"Leftover ",[21,1247,1060],{},[21,1249,863],{}," They are ignored; convert them or the rules silently disappear.",[40,1252,1253,1259],{},[1234,1254,1255,1258],{},[21,1256,1257],{},"trailingSlash"," mismatch with generator URLs."," Produces redirect loops or duplicates; match your canonical form.",[40,1261,1262,1265,1266,1268],{},[1234,1263,1264],{},"Headers pattern syntax."," Test each ",[21,1267,840],{}," on a preview; an unmatched pattern applies nothing.",[40,1270,1271,1274,1275,30],{},[1234,1272,1273],{},"Rollback:"," Vercel keeps previous deployments; promote the last good one from the dashboard or with ",[21,1276,1277],{},"vercel promote",[32,1279,1281],{"id":1280},"conclusion","Conclusion",[14,1283,1284,1285,1287,1288,1290],{},"Hugo and Eleventy run well on Vercel once the defaults are made explicit. Pin the generator and Node versions, set the build command and output directory in ",[21,1286,23],{},", choose trailing slash and clean URL behaviour that matches your canonical URLs, and move headers and redirects from host-specific files into ",[21,1289,23],{},". Use preview environment variables for correct base URLs, keep image caches between builds, and the site behaves the same on Vercel as it did locally.",[32,1292,1294],{"id":1293},"faq","FAQ",[1296,1297,1299],"h3",{"id":1298},"how-do-i-set-the-hugo-version-on-vercel","How do I set the Hugo version on Vercel?",[14,1301,1302],{},"Set the HUGO_VERSION environment variable in the project settings or in vercel.json build env, for example 0.134.0. Without it, Vercel's build image may use an old Hugo release that lacks features your theme needs, and builds can break or differ from local ones.",[1296,1304,1306],{"id":1305},"what-output-directory-does-vercel-need-for-eleventy","What output directory does Vercel need for Eleventy?",[14,1308,1309],{},"Eleventy writes to _site by default, which Vercel's Eleventy preset expects. If you change Eleventy's output directory, set outputDirectory in vercel.json or the project settings to match.",[1296,1311,1313],{"id":1312},"how-do-i-get-trailing-slashes-on-vercel-for-a-hugo-site","How do I get trailing slashes on Vercel for a Hugo site?",[14,1315,1316],{},"Set trailingSlash to true in vercel.json. Hugo generates folder\u002Findex.html files, and with trailingSlash true Vercel serves them at \u002Ffolder\u002F and redirects \u002Ffolder to it, which matches Hugo's canonical URLs.",[1296,1318,1320],{"id":1319},"can-i-use-_redirects-or-_headers-files-on-vercel","Can I use _redirects or _headers files on Vercel?",[14,1322,1323],{},"No. Vercel ignores those files. Redirects, rewrites and headers are configured in vercel.json, or in a generated configuration using the Build Output API for advanced cases.",[32,1325,1327],{"id":1326},"related","Related",[37,1329,1330,1339,1346,1353,1360],{},[40,1331,1332,1335,1336,1338],{},[1234,1333,1334],{},"Parent:"," ",[26,1337,29],{"href":28}," — choosing and configuring a platform.",[40,1340,1341,1345],{},[26,1342,1344],{"href":1343},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites\u002F","Netlify Redirects and Rewrites for Static Sites"," — the rules you may be converting.",[40,1347,1348,1352],{},[26,1349,1351],{"href":1350},"\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 output is not enough.",[40,1354,1355,1359],{},[26,1356,1358],{"href":1357},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002F","Hugo Build Times for Large Repositories"," — keeping Hugo builds fast.",[40,1361,1362,1366],{},[26,1363,1365],{"href":1364},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy\u002F","Enabling Incremental Builds in Eleventy"," — faster Eleventy builds.",[1368,1369,1370],"style",{},"html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":68,"searchDepth":82,"depth":82,"links":1372},[1373,1374,1375,1376,1377,1378,1379,1380,1381,1382,1383,1384,1390],{"id":34,"depth":82,"text":35},{"id":54,"depth":82,"text":55},{"id":399,"depth":82,"text":400},{"id":606,"depth":82,"text":607},{"id":856,"depth":82,"text":857},{"id":1120,"depth":82,"text":1121},{"id":1150,"depth":82,"text":1151},{"id":1169,"depth":82,"text":1170},{"id":1201,"depth":82,"text":1202},{"id":1227,"depth":82,"text":1228},{"id":1280,"depth":82,"text":1281},{"id":1293,"depth":82,"text":1294,"children":1385},[1386,1387,1388,1389],{"id":1298,"depth":99,"text":1299},{"id":1305,"depth":99,"text":1306},{"id":1312,"depth":99,"text":1313},{"id":1319,"depth":99,"text":1320},{"id":1326,"depth":82,"text":1327},[1392,1395,1398,1399],{"name":1393,"item":1394},"Home","\u002F",{"name":1396,"item":1397},"Production-Ready Deployment & CI\u002FCD Workflows","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":29,"item":28},{"name":5,"item":1400},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy\u002F","2026-09-18","Deploy Hugo and Eleventy sites on Vercel with pinned versions, the right output directory, clean URLs, trailing slashes, headers and redirects in vercel.json.","md",[1405,1406,1407,1408],{"q":1299,"a":1302},{"q":1306,"a":1309},{"q":1313,"a":1316},{"q":1320,"a":1323},{},true,"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy",{"title":5,"description":1402},"production-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy\u002Findex","article","7AFNwK9vSYc3I2u8LeRJcP6_Nnu5cfxu4BECxs5aChg",[1417,1420,1423,1426,1429,1432,1435,1438,1441,1444,1447,1450,1453,1456,1459,1462,1465,1468,1471,1474,1477,1480,1483,1486,1489,1492,1495,1498,1501,1504,1507,1510,1513,1516,1519,1522,1525,1528,1531,1534,1537,1540,1543,1546,1549,1552,1555,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,1731,1734,1737,1740,1743,1746,1749,1752,1755,1758,1761,1764,1767,1770,1773,1776,1779,1782,1785,1788,1791,1794,1797,1800,1803,1806,1809,1812,1815,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,1934,1937,1940,1943,1946,1949,1952,1955,1958,1961,1964,1967,1970,1973,1976,1979,1982,1985,1988,1991,1994,1997,2000,2003,2006,2009,2012,2015,2018,2021,2024,2027,2030,2033,2036,2039,2042,2045,2048,2051,2054,2057,2060,2063,2066,2069,2072,2075,2078,2081,2084,2087,2090,2093,2096,2099,2102,2105,2108,2111,2114,2117,2120,2123,2126,2129,2132,2135,2138,2141,2144,2147,2150,2153,2156,2159,2162,2165,2168,2171,2174,2177,2180,2183,2186,2189,2192,2195,2198,2201,2204,2207,2210,2213,2216,2219,2222,2225,2228,2231,2234,2237,2240,2243,2246,2249,2252,2255,2258,2261,2263,2266,2268,2271,2274,2277,2280,2283,2286,2289,2292,2295,2298,2301,2304,2307,2310,2313,2316,2319,2322,2325,2328,2331,2332,2335,2338,2341,2343,2346,2349,2351,2354,2357,2359,2362,2365,2368,2371,2373,2376,2379,2382,2385,2388,2391,2394,2397,2400,2403,2406,2409,2412,2415,2418,2421,2424,2427,2430,2433,2436,2439,2442,2445,2448,2451,2454,2457,2460,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],{"path":1418,"title":1419},"\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":1421,"title":1422},"\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":1424,"title":1425},"\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":1427,"title":1428},"\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":1430,"title":1431},"\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":1433,"title":1434},"\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":1436,"title":1437},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1439,"title":1440},"\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":1442,"title":1443},"\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":1445,"title":1446},"\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":1448,"title":1449},"\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":1451,"title":1452},"\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":1454,"title":1455},"\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":1457,"title":1458},"\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":1460,"title":1461},"\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":1463,"title":1464},"\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":1466,"title":1467},"\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":1469,"title":1470},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1472,"title":1473},"\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":1475,"title":1476},"\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":1478,"title":1479},"\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":1481,"title":1482},"\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":1484,"title":1485},"\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":1487,"title":1488},"\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":1490,"title":1491},"\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":1493,"title":1494},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1496,"title":1497},"\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":1499,"title":1500},"\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":1502,"title":1503},"\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":1505,"title":1506},"\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":1508,"title":1509},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1511,"title":1512},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1514,"title":1515},"\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":1517,"title":1518},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1520,"title":1521},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1523,"title":1524},"\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":1526,"title":1527},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1529,"title":1530},"\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":1532,"title":1533},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1535,"title":1536},"\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":1538,"title":1539},"\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":1541,"title":1542},"\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":1544,"title":1545},"\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":1547,"title":1548},"\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":1550,"title":1551},"\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":1553,"title":1554},"\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":1556,"title":1358},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories",{"path":1558,"title":1559},"\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":1561,"title":1562},"\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":1564,"title":1565},"\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":1567,"title":1568},"\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":1570,"title":1571},"\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":1573,"title":1574},"\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":1576,"title":1577},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1579,"title":1580},"\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":1582,"title":1583},"\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":1585,"title":1586},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1588,"title":1589},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1591,"title":1592},"\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":1594,"title":1595},"\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":1597,"title":1598},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1600,"title":1601},"\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":1603,"title":1604},"\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":1606,"title":1607},"\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":1609,"title":1610},"\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":1612,"title":1613},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1615,"title":1616},"\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":1618,"title":1619},"\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":1621,"title":1622},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1624,"title":1625},"\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":1627,"title":1628},"\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":1630,"title":1631},"\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":1633,"title":1634},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1636,"title":1637},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1639,"title":1640},"\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":1642,"title":1643},"\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":1645,"title":1646},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1648,"title":1649},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fkeeping-redirects-working-after-an-ssg-migration","Keeping Redirects Working After an SSG Migration",{"path":1651,"title":1652},"\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":1654,"title":1655},"\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":1657,"title":1658},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1660,"title":1661},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1663,"title":1664},"\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":1666,"title":1667},"\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":1669,"title":1670},"\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":1672,"title":1673},"\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":1675,"title":1676},"\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":1678,"title":1679},"\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":1681,"title":1682},"\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":1684,"title":1685},"\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":1687,"title":1688},"\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":1690,"title":1691},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1693,"title":1694},"\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":1696,"title":1697},"\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":1699,"title":1700},"\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":1702,"title":1703},"\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":1705,"title":1706},"\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":1708,"title":1709},"\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":1711,"title":1712},"\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":1714,"title":1715},"\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":1717,"title":1718},"\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":1720,"title":1721},"\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":1723,"title":1724},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1726,"title":1727},"\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":1729,"title":1730},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1732,"title":1733},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1735,"title":1736},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1738,"title":1739},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1741,"title":1742},"\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":1744,"title":1745},"\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":1747,"title":1748},"\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":1750,"title":1751},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1753,"title":1754},"\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":1756,"title":1757},"\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":1759,"title":1760},"\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":1762,"title":1763},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1765,"title":1766},"\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":1768,"title":1769},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1771,"title":1772},"\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":1774,"title":1775},"\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":1777,"title":1778},"\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":1780,"title":1781},"\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":1783,"title":1784},"\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":1786,"title":1787},"\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":1789,"title":1790},"\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":1792,"title":1793},"\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":1795,"title":1796},"\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":1798,"title":1799},"\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":1801,"title":1802},"\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":1804,"title":1805},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1807,"title":1808},"\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":1810,"title":1811},"\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":1813,"title":1814},"\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":1816,"title":849},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-busting-with-content-hashed-filenames",{"path":1818,"title":1819},"\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":1821,"title":1822},"\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":1824,"title":1825},"\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":1827,"title":1828},"\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":1830,"title":1831},"\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":1833,"title":1834},"\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":1836,"title":1837},"\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":1839,"title":1840},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1842,"title":1843},"\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":1845,"title":1846},"\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":1848,"title":1849},"\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":1851,"title":1852},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fstale-while-revalidate-for-static-html","Stale-While-Revalidate for Static HTML",{"path":1854,"title":1855},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1857,"title":1858},"\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":1860,"title":1861},"\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":1863,"title":1864},"\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":1866,"title":1867},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":1869,"title":1870},"\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":1872,"title":1873},"\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":1875,"title":1876},"\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":1878,"title":1879},"\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":1881,"title":1882},"\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":1884,"title":1885},"\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":1887,"title":1888},"\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":1890,"title":1891},"\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":1893,"title":1894},"\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":1896,"title":1897},"\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":1899,"title":1900},"\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":1902,"title":1903},"\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":1905,"title":1906},"\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":1908,"title":1909},"\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":1911,"title":1912},"\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":1914,"title":1915},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1917,"title":1918},"\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":1920,"title":1921},"\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":1923,"title":1924},"\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":1926,"title":1927},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":1929,"title":1930},"\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":1932,"title":1933},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1935,"title":1936},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1938,"title":1939},"\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":1941,"title":1942},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1944,"title":1945},"\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":1947,"title":1948},"\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":1950,"title":1951},"\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":1953,"title":1954},"\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":1956,"title":1957},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":1959,"title":1960},"\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":1962,"title":1963},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":1965,"title":1966},"\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":1968,"title":1969},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":1971,"title":1972},"\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":1974,"title":1975},"\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":1977,"title":1978},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1980,"title":1981},"\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":1983,"title":1984},"\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":1986,"title":1987},"\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":1989,"title":1990},"\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":1992,"title":1993},"\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":1995,"title":1996},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1998,"title":1999},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":2001,"title":2002},"\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":2004,"title":2005},"\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":2007,"title":2008},"\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":2010,"title":2011},"\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":2013,"title":2014},"\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":2016,"title":2017},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":2019,"title":2020},"\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":2022,"title":2023},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":2025,"title":2026},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":2028,"title":2029},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":2031,"title":2032},"\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":2034,"title":2035},"\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":2037,"title":2038},"\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":2040,"title":2041},"\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":2043,"title":2044},"\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":2046,"title":2047},"\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":2049,"title":2050},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":2052,"title":2053},"\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":2055,"title":2056},"\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":2058,"title":2059},"\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":2061,"title":2062},"\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":2064,"title":2065},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":2067,"title":2068},"\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":2070,"title":2071},"\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":2073,"title":2074},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":2076,"title":2077},"\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":2079,"title":2080},"\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":2082,"title":2083},"\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":2085,"title":2086},"\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":2088,"title":2089},"\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":2091,"title":2092},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2094,"title":2095},"\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":2097,"title":2098},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2100,"title":2101},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2103,"title":2104},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2106,"title":2107},"\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":2109,"title":2110},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2112,"title":2113},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2115,"title":2116},"\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":2118,"title":2119},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2121,"title":2122},"\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":2124,"title":2125},"\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":2127,"title":2128},"\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":2130,"title":2131},"\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":2133,"title":2134},"\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":2136,"title":2137},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2139,"title":2140},"\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":2142,"title":2143},"\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":2145,"title":2146},"\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":2148,"title":2149},"\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":2151,"title":2152},"\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":2154,"title":2155},"\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":2157,"title":2158},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2160,"title":2161},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2163,"title":2164},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2166,"title":2167},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2169,"title":2170},"\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":2172,"title":2173},"\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":2175,"title":2176},"\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":2178,"title":2179},"\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":2181,"title":2182},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2184,"title":2185},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2187,"title":2188},"\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":2190,"title":2191},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2193,"title":2194},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2196,"title":2197},"\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":2199,"title":2200},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2202,"title":2203},"\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":2205,"title":2206},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2208,"title":2209},"\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":2211,"title":2212},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2214,"title":2215},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2217,"title":2218},"\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":2220,"title":2221},"\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":2223,"title":2224},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2226,"title":2227},"\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":2229,"title":2230},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2232,"title":2233},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2235,"title":2236},"\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":2238,"title":2239},"\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":2241,"title":2242},"\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":2244,"title":2245},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2247,"title":2248},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2250,"title":2251},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2253,"title":2254},"\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":2256,"title":2257},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2259,"title":2260},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fbuild-caching-on-netlify-and-vercel","Build Caching on Netlify and Vercel",{"path":2262,"title":1197},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fcaching-hugo-builds-in-github-actions",{"path":2264,"title":2265},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2267,"title":1365},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy",{"path":2269,"title":2270},"\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":2272,"title":2273},"\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":2275,"title":2276},"\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":2278,"title":2279},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2281,"title":2282},"\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":2284,"title":2285},"\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":2287,"title":2288},"\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":2290,"title":2291},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":2293,"title":2294},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2296,"title":2297},"\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":2299,"title":2300},"\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":2302,"title":2303},"\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":2305,"title":2306},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2308,"title":2309},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2311,"title":2312},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2314,"title":2315},"\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":2317,"title":2318},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2320,"title":2321},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2323,"title":2324},"\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":2326,"title":2327},"\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":2329,"title":2330},"\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":1411,"title":5},{"path":2333,"title":2334},"\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":2336,"title":2337},"\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":2339,"title":2340},"\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":2342,"title":29},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies",{"path":2344,"title":2345},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2347,"title":2348},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2350,"title":1344},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites",{"path":2352,"title":2353},"\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":2355,"title":2356},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-build-output-api-for-custom-ssgs","Vercel Build Output API for Custom SSGs",{"path":2358,"title":1351},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-isr-vs-static-generation-for-ssgs",{"path":2360,"title":2361},"\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":2363,"title":2364},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2366,"title":2367},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2369,"title":2370},"\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":2372,"title":1147},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests",{"path":2374,"title":2375},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2377,"title":2378},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2380,"title":2381},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2383,"title":2384},"\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":2386,"title":2387},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2389,"title":2390},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2392,"title":2393},"\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":2395,"title":2396},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2398,"title":2399},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2401,"title":2402},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2404,"title":2405},"\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":2407,"title":2408},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2410,"title":2411},"\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":2413,"title":2414},"\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":2416,"title":2417},"\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":2419,"title":2420},"\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":2422,"title":2423},"\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":2425,"title":2426},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2428,"title":2429},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2431,"title":2432},"\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":2434,"title":2435},"\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":2437,"title":2438},"\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":2440,"title":2441},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2443,"title":2444},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2446,"title":2447},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2449,"title":2450},"\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":2452,"title":2453},"\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":2455,"title":2456},"\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":2458,"title":2459},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2461,"title":853},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fwriting-a-content-security-policy-for-a-static-site",{"path":2463,"title":2464},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2466,"title":2467},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2469,"title":2470},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2472,"title":2473},"\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":2475,"title":2476},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2478,"title":2479},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2481,"title":2482},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2484,"title":2485},"\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":2487,"title":2488},"\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":2490,"title":2491},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2493,"title":2494},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2496,"title":2497},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2499,"title":2500},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2502,"title":2503},"\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":2505,"title":2506},"\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":2508,"title":2509},"\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":2511,"title":2512},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2514,"title":2515},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2517,"title":2518},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2520,"title":2521},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2523,"title":2524},"\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":2526,"title":2527},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2529,"title":2530},"\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":2532,"title":2533},"\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":2535,"title":2536},"\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":2538,"title":2539},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2541,"title":2542},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2544,"title":2545},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2547,"title":2548},"\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":2550,"title":2551},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2553,"title":2554},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2556,"tools":2560},{"label":2557,"plural":2558,"u":2559},"How-to","How-tos","\u002Fguides\u002Fhow-to\u002F",[2561,2563,2565],{"label":332,"u":2562},"\u002Ftools\u002Feleventy\u002F",{"label":327,"u":2564},"\u002Ftools\u002Fhugo\u002F",{"label":2566,"u":2567},"Vercel","\u002Ftools\u002Fvercel\u002F",1790943192440]