[{"data":1,"prerenderedAt":2509},["ShallowReactive",2],{"page:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-eleventy-out-of-memory-errors-on-large-collections":3,"all-docs-nav":1359,"filed:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-eleventy-out-of-memory-errors-on-large-collections":2500},{"id":4,"title":5,"body":6,"breadcrumb":1334,"dateModified":1344,"datePublished":1344,"description":1345,"extension":1346,"faq":1347,"meta":1352,"navigation":1353,"path":1354,"seo":1355,"slug":12,"stem":1356,"type":1357,"__hash__":1358},"content\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-eleventy-out-of-memory-errors-on-large-collections\u002Findex.md","Fixing Eleventy Out-of-Memory Errors on Large Collections",{"type":7,"value":8,"toc":1316},"minimark",[9,13,17,28,31,40,45,48,118,121,251,255,258,272,287,304,308,311,347,600,605,609,616,635,750,867,871,890,894,897,936,943,947,1042,1045,1182,1186,1229,1233,1236,1240,1245,1248,1252,1255,1259,1262,1266,1269,1273,1312],[10,11,5],"h1",{"id":12},"fixing-eleventy-out-of-memory-errors-on-large-collections",[14,15,16],"p",{},"The error arrives without warning on a site that built fine yesterday:",[18,19,25],"pre",{"className":20,"code":22,"language":23,"meta":24},[21],"language-text","\u003C--- Last few GCs --->\n[2841:0x5d3a1c0]   148213 ms: Mark-Compact 4041.2 (4134.6) -> 4027.9 (4136.3) MB, 2210.4 \u002F 0.0 ms\nFATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory\n","text","",[26,27,22],"code",{"__ignoreMap":24},[14,29,30],{},"On large Eleventy sites this usually happens when a collection crosses some size, or when someone adds a feature that reads every page's rendered content — a related-posts list, a search index, a full-content RSS feed. Eleventy keeps everything it knows about every page in memory for the whole build, so anything that multiplies per-page data by the number of pages grows quadratically in the worst case.",[14,32,33,34,39],{},"This guide fixes the error on a 12,400-page knowledge base built with Eleventy 3.0 on GitHub Actions' standard 7 GB runner. It shows how to confirm what is holding memory, the four changes that took peak heap from over 4 GB to 1.6 GB, and how to size the Node heap afterwards. It belongs to ",[35,36,38],"a",{"href":37},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002F","Astro vs Eleventy for Documentation Sites",", where memory behaviour at scale is one of the selection criteria.",[41,42,44],"h2",{"id":43},"symptoms-and-first-checks","Symptoms and First Checks",[14,46,47],{},"The build failed after about 2.5 minutes, consistently, with the default Node 20 heap limit of about 4 GB on a 64-bit runner. Before changing anything, three measurements set the baseline:",[49,50,51,67],"table",{},[52,53,54],"thead",{},[55,56,57,61,64],"tr",{},[58,59,60],"th",{},"Check",[58,62,63],{},"Command",[58,65,66],{},"Result",[68,69,70,84,105],"tbody",{},[55,71,72,76,81],{},[73,74,75],"td",{},"Peak heap with a raised limit",[73,77,78],{},[26,79,80],{},"NODE_OPTIONS=--max-old-space-size=8192 \u002Fusr\u002Fbin\u002Ftime -v npx @11ty\u002Feleventy",[73,82,83],{},"5.3 GB resident, build 3 min 41 s",[55,85,86,89,98],{},[73,87,88],{},"Pages and collection sizes",[73,90,91,94,95],{},[26,92,93],{},"npx @11ty\u002Feleventy --dryrun"," with a log in ",[26,96,97],{},"eleventy.after",[73,99,100,101,104],{},"12,400 pages, ",[26,102,103],{},"articles"," 11,900 items",[55,106,107,110,115],{},[73,108,109],{},"Global data size",[73,111,112],{},[26,113,114],{},"du -sh _data",[73,116,117],{},"186 MB of JSON",[14,119,120],{},"The 186 MB of JSON was the first surprise: a product catalogue exported nightly, loaded as global data, and available to every template.",[122,123,124,247],"figure",{},[125,126,133,134,133,138,133,142,133,149],"svg",{"viewBox":127,"role":128,"ariaLabelledBy":129,"xmlns":132},"0 0 760 244","img",[130,131],"e11oom-heap-title","e11oom-heap-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[135,136,137],"title",{"id":130},"Retained heap by category in a snapshot taken at 90 percent of the build",[139,140,141],"desc",{"id":131},"Horizontal bars of retained memory. Rendered templateContent strings held by collections 1.9 gigabytes. Global data from the product catalogue JSON 1.4 gigabytes. Eleventy's own page and data cascade objects 0.9 gigabytes. Search index array built in a template 0.7 gigabytes. Other 0.4 gigabytes.",[143,144],"rect",{"x":145,"y":145,"width":146,"height":147,"fill":148},"0","760","244","#ffffff",[150,151,153,154,153,165,153,169,153,175,153,182,153,186,153,192,153,199,153,204,153,211,153,215,153,220,153,224,153,229,153,233,153,238,153,242,133],"g",{"style":152},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[143,155],{"x":156,"y":157,"width":158,"height":159,"rx":160,"fill":161,"opacity":162,"stroke":163,"style":164},"240.0","65.0","442.8","20.0","3","#ff595e","0.3","#d83b41","stroke-width:1px",[143,166],{"x":156,"y":167,"width":168,"height":159,"rx":160,"fill":161,"opacity":162,"stroke":163,"style":164},"99.0","326.3",[143,170],{"x":156,"y":171,"width":172,"height":159,"rx":160,"fill":173,"stroke":174,"style":164},"133.0","209.7","#d9e2ef","#556071",[143,176],{"x":156,"y":177,"width":178,"height":159,"rx":160,"fill":179,"opacity":180,"stroke":181,"style":164},"167.0","163.1","#ffca3a","0.45","#a97b00",[143,183],{"x":156,"y":184,"width":185,"height":159,"rx":160,"fill":173,"stroke":174,"style":164},"201.0","93.2",[187,188],"path",{"d":189,"fill":190,"stroke":174,"style":191},"M240.0 60.0 L240.0 226.0","none","stroke-width:1.5px",[23,193,198],{"x":194,"y":195,"fill":196,"style":197},"380.0","30.0","#1f2937","font-size:16px;text-anchor:middle;font-weight:700","Where the heap went",[23,200,203],{"x":159,"y":201,"fill":196,"style":202},"79.2","font-size:12px;text-anchor:start","templateContent in collections",[23,205,210],{"x":206,"y":207,"fill":208,"style":209},"690.8","79.5","#b32b30","font-size:12px;text-anchor:start;font-weight:700","1.9 GB",[23,212,214],{"x":159,"y":213,"fill":196,"style":202},"113.2","Catalogue global data",[23,216,219],{"x":217,"y":218,"fill":208,"style":209},"574.3","113.5","1.4 GB",[23,221,223],{"x":159,"y":222,"fill":196,"style":202},"147.2","Eleventy page objects",[23,225,228],{"x":226,"y":227,"fill":196,"style":209},"457.7","147.5","0.9 GB",[23,230,232],{"x":159,"y":231,"fill":196,"style":202},"181.2","Search index array",[23,234,237],{"x":235,"y":236,"fill":196,"style":209},"411.1","181.5","0.7 GB",[23,239,241],{"x":159,"y":240,"fill":196,"style":202},"215.2","Other",[23,243,246],{"x":244,"y":245,"fill":196,"style":209},"341.2","215.5","0.4 GB",[248,249,250],"figcaption",{},"Heap snapshot via node --inspect-brk and Chrome DevTools, grouped by retainer; total about 5.3 GB.",[41,252,254],{"id":253},"step-1-find-the-retainers-with-a-heap-snapshot","Step 1: Find the Retainers With a Heap Snapshot",[14,256,257],{},"Run the build under the inspector with a raised limit so it completes, and take a snapshot near the end:",[18,259,263],{"className":260,"code":261,"language":262,"meta":24,"style":24},"language-sh shiki shiki-themes github-light github-dark","NODE_OPTIONS=--max-old-space-size=8192 node --inspect-brk node_modules\u002F@11ty\u002Feleventy\u002Fcmd.cjs\n","sh",[26,264,265],{"__ignoreMap":24},[266,267,270],"span",{"class":268,"line":269},"line",1,[266,271,261],{},[14,273,274,275,278,279,282,283,286],{},"Open ",[26,276,277],{},"chrome:\u002F\u002Finspect",", continue execution, and take a heap snapshot from the Memory panel when the console shows writing has started. Sort by retained size. Two patterns stood out: thousands of large strings retained by ",[26,280,281],{},"templateContent"," on collection items, and one huge object retained by the data cascade under ",[26,284,285],{},"catalogue",".",[14,288,289,290,292,293,296,297,300,301,303],{},"The ",[26,291,281],{}," strings came from three templates — a related-articles block, the full-content RSS feed and a search index template — each of which looped over ",[26,294,295],{},"collections.articles"," and read ",[26,298,299],{},"item.templateContent",". Reading ",[26,302,281],{}," forces Eleventy to render and retain each item's output, and three templates doing so kept every article's HTML alive for the whole build.",[41,305,307],{"id":306},"step-2-stop-reading-templatecontent-across-collections","Step 2: Stop Reading templateContent Across Collections",[14,309,310],{},"Each of the three templates needed far less than the full HTML:",[312,313,314,329,338],"ul",{},[315,316,317,321,322,325,326,328],"li",{},[318,319,320],"strong",{},"Related articles"," needed titles, URLs and tags. They are in ",[26,323,324],{},"item.data","; the loop stopped touching ",[26,327,281],{}," at all.",[315,330,331,334,335,286],{},[318,332,333],{},"RSS"," needed full content for the 20 newest items only. The feed template now slices first, then reads content: ",[26,336,337],{},"collections.articles | reverse | head(20)",[315,339,340,343,344,346],{},[318,341,342],{},"The search index"," needed plain text, truncated to 2,000 characters. It moved out of a template and into an ",[26,345,97],{}," event that reads the written HTML files from disk one at a time, so nothing is held in memory longer than one file.",[18,348,352],{"className":349,"code":350,"language":351,"meta":24,"style":24},"language-js shiki shiki-themes github-light github-dark","\u002F\u002F eleventy.config.js\neleventyConfig.on('eleventy.after', async ({ results }) => {\n  const out = fs.createWriteStream('_site\u002Fsearch.json');\n  out.write('[');\n  results.forEach((r, i) => {\n    if (!r.url.startsWith('\u002Fkb\u002F')) return;\n    const text = stripHtml(r.content).slice(0, 2000);\n    out.write((i ? ',' : '') + JSON.stringify({ url: r.url, text }));\n  });\n  out.end(']');\n});\n","js",[26,353,354,360,401,428,444,471,503,534,573,579,594],{"__ignoreMap":24},[266,355,356],{"class":268,"line":269},[266,357,359],{"class":358},"sJ8bj","\u002F\u002F eleventy.config.js\n",[266,361,363,367,371,374,378,381,385,388,392,395,398],{"class":268,"line":362},2,[266,364,366],{"class":365},"sVt8B","eleventyConfig.",[266,368,370],{"class":369},"sScJk","on",[266,372,373],{"class":365},"(",[266,375,377],{"class":376},"sZZnC","'eleventy.after'",[266,379,380],{"class":365},", ",[266,382,384],{"class":383},"szBVR","async",[266,386,387],{"class":365}," ({ ",[266,389,391],{"class":390},"s4XuR","results",[266,393,394],{"class":365}," }) ",[266,396,397],{"class":383},"=>",[266,399,400],{"class":365}," {\n",[266,402,404,407,411,414,417,420,422,425],{"class":268,"line":403},3,[266,405,406],{"class":383},"  const",[266,408,410],{"class":409},"sj4cs"," out",[266,412,413],{"class":383}," =",[266,415,416],{"class":365}," fs.",[266,418,419],{"class":369},"createWriteStream",[266,421,373],{"class":365},[266,423,424],{"class":376},"'_site\u002Fsearch.json'",[266,426,427],{"class":365},");\n",[266,429,431,434,437,439,442],{"class":268,"line":430},4,[266,432,433],{"class":365},"  out.",[266,435,436],{"class":369},"write",[266,438,373],{"class":365},[266,440,441],{"class":376},"'['",[266,443,427],{"class":365},[266,445,447,450,453,456,459,461,464,467,469],{"class":268,"line":446},5,[266,448,449],{"class":365},"  results.",[266,451,452],{"class":369},"forEach",[266,454,455],{"class":365},"((",[266,457,458],{"class":390},"r",[266,460,380],{"class":365},[266,462,463],{"class":390},"i",[266,465,466],{"class":365},") ",[266,468,397],{"class":383},[266,470,400],{"class":365},[266,472,474,477,480,483,486,489,491,494,497,500],{"class":268,"line":473},6,[266,475,476],{"class":383},"    if",[266,478,479],{"class":365}," (",[266,481,482],{"class":383},"!",[266,484,485],{"class":365},"r.url.",[266,487,488],{"class":369},"startsWith",[266,490,373],{"class":365},[266,492,493],{"class":376},"'\u002Fkb\u002F'",[266,495,496],{"class":365},")) ",[266,498,499],{"class":383},"return",[266,501,502],{"class":365},";\n",[266,504,506,509,512,514,517,520,523,525,527,529,532],{"class":268,"line":505},7,[266,507,508],{"class":383},"    const",[266,510,511],{"class":409}," text",[266,513,413],{"class":383},[266,515,516],{"class":369}," stripHtml",[266,518,519],{"class":365},"(r.content).",[266,521,522],{"class":369},"slice",[266,524,373],{"class":365},[266,526,145],{"class":409},[266,528,380],{"class":365},[266,530,531],{"class":409},"2000",[266,533,427],{"class":365},[266,535,537,540,542,545,548,551,554,557,559,562,565,567,570],{"class":268,"line":536},8,[266,538,539],{"class":365},"    out.",[266,541,436],{"class":369},[266,543,544],{"class":365},"((i ",[266,546,547],{"class":383},"?",[266,549,550],{"class":376}," ','",[266,552,553],{"class":383}," :",[266,555,556],{"class":376}," ''",[266,558,466],{"class":365},[266,560,561],{"class":383},"+",[266,563,564],{"class":409}," JSON",[266,566,286],{"class":365},[266,568,569],{"class":369},"stringify",[266,571,572],{"class":365},"({ url: r.url, text }));\n",[266,574,576],{"class":268,"line":575},9,[266,577,578],{"class":365},"  });\n",[266,580,582,584,587,589,592],{"class":268,"line":581},10,[266,583,433],{"class":365},[266,585,586],{"class":369},"end",[266,588,373],{"class":365},[266,590,591],{"class":376},"']'",[266,593,427],{"class":365},[266,595,597],{"class":268,"line":596},11,[266,598,599],{"class":365},"});\n",[14,601,602,604],{},[26,603,391],{}," contains each page's output once; streaming it to a file avoids building a 700 MB array in memory. This change alone cut peak heap by 2.4 GB.",[41,606,608],{"id":607},"step-3-shrink-global-data","Step 3: Shrink Global Data",[14,610,611,612,615],{},"The 186 MB catalogue was loaded by ",[26,613,614],{},"_data\u002Fcatalogue.json"," and used by 140 product pages, each of which needed one product. Global data is in the cascade for every template, so it was retained and merged into the data of all 12,400 pages' contexts lazily but still held as one huge object. Two fixes:",[617,618,619,629],"ol",{},[315,620,621,624,625,628],{},[318,622,623],{},"Pre-split the data."," A prebuild script splits the export into one small JSON file per product under ",[26,626,627],{},"_data\u002Fproducts\u002F",", and a paginated template generates the 140 pages from a lightweight index file containing only IDs, names and slugs (310 KB).",[315,630,631,634],{},[318,632,633],{},"Load per page."," Each product page loads its own file in a JavaScript data file keyed by the pagination item, so only 140 small objects are ever read.",[18,636,638],{"className":349,"code":637,"language":351,"meta":24,"style":24},"\u002F\u002F products\u002Fproduct.11tydata.js\nimport fs from 'node:fs\u002Fpromises';\nexport default {\n  eleventyComputed: {\n    product: async (data) => JSON.parse(await fs.readFile(`data\u002Fproducts\u002F${data.item.slug}.json`, 'utf8')),\n  },\n};\n",[26,639,640,645,661,671,676,740,745],{"__ignoreMap":24},[266,641,642],{"class":268,"line":269},[266,643,644],{"class":358},"\u002F\u002F products\u002Fproduct.11tydata.js\n",[266,646,647,650,653,656,659],{"class":268,"line":362},[266,648,649],{"class":383},"import",[266,651,652],{"class":365}," fs ",[266,654,655],{"class":383},"from",[266,657,658],{"class":376}," 'node:fs\u002Fpromises'",[266,660,502],{"class":365},[266,662,663,666,669],{"class":268,"line":403},[266,664,665],{"class":383},"export",[266,667,668],{"class":383}," default",[266,670,400],{"class":365},[266,672,673],{"class":268,"line":430},[266,674,675],{"class":365},"  eleventyComputed: {\n",[266,677,678,681,684,686,688,691,693,695,697,699,702,704,707,709,712,714,717,719,721,724,726,729,732,734,737],{"class":268,"line":446},[266,679,680],{"class":369},"    product",[266,682,683],{"class":365},": ",[266,685,384],{"class":383},[266,687,479],{"class":365},[266,689,690],{"class":390},"data",[266,692,466],{"class":365},[266,694,397],{"class":383},[266,696,564],{"class":409},[266,698,286],{"class":365},[266,700,701],{"class":369},"parse",[266,703,373],{"class":365},[266,705,706],{"class":383},"await",[266,708,416],{"class":365},[266,710,711],{"class":369},"readFile",[266,713,373],{"class":365},[266,715,716],{"class":376},"`data\u002Fproducts\u002F${",[266,718,690],{"class":365},[266,720,286],{"class":376},[266,722,723],{"class":365},"item",[266,725,286],{"class":376},[266,727,728],{"class":365},"slug",[266,730,731],{"class":376},"}.json`",[266,733,380],{"class":365},[266,735,736],{"class":376},"'utf8'",[266,738,739],{"class":365},")),\n",[266,741,742],{"class":268,"line":473},[266,743,744],{"class":365},"  },\n",[266,746,747],{"class":268,"line":505},[266,748,749],{"class":365},"};\n",[122,751,752,864],{},[125,753,133,758,133,761,133,764,133,767],{"viewBox":754,"role":128,"ariaLabelledBy":755,"xmlns":132},"0 0 760 248",[756,757],"e11oom-steps-title","e11oom-steps-desc",[135,759,760],{"id":756},"Peak resident memory of the Eleventy build after each change",[139,762,763],{"id":757},"Paired bars comparing peak resident memory before and after each change. Stop reading templateContent across collections, 5.3 to 2.9 gigabytes. Split global catalogue data, 2.9 to 1.8. Stream the search index, already counted. Upgrade from Eleventy 2.0 to 3.0, 1.8 to 1.6.",[143,765],{"x":145,"y":145,"width":146,"height":766,"fill":148},"248",[150,768,153,769,153,776,153,782,153,788,153,792,153,795,153,799,153,802,153,806,153,809,153,812,153,817,153,821,153,825,153,828,153,834,153,840,153,844,153,847,153,852,153,856,153,859,133],{"style":152},[143,770],{"x":771,"y":772,"width":773,"height":774,"rx":775,"fill":161,"opacity":162,"stroke":163,"style":164},"262.9","50.0","14.0","12.0","2",[143,777],{"x":778,"y":772,"width":773,"height":774,"rx":775,"fill":779,"opacity":780,"stroke":781,"style":164},"398.4","#8ac926","0.4","#5a8a16",[143,783],{"x":784,"y":785,"width":786,"height":787,"rx":160,"fill":161,"opacity":162,"stroke":163,"style":164},"230.0","82.0","456.5","16.0",[143,789],{"x":784,"y":790,"width":791,"height":787,"rx":160,"fill":779,"opacity":780,"stroke":781,"style":164},"102.0","249.8",[143,793],{"x":784,"y":794,"width":791,"height":787,"rx":160,"fill":161,"opacity":162,"stroke":163,"style":164},"134.0",[143,796],{"x":784,"y":797,"width":798,"height":787,"rx":160,"fill":779,"opacity":780,"stroke":781,"style":164},"154.0","155.0",[143,800],{"x":784,"y":801,"width":798,"height":787,"rx":160,"fill":161,"opacity":162,"stroke":163,"style":164},"186.0",[143,803],{"x":784,"y":804,"width":805,"height":787,"rx":160,"fill":779,"opacity":780,"stroke":781,"style":164},"206.0","137.8",[187,807],{"d":808,"fill":190,"stroke":174,"style":191},"M230.0 78.0 L230.0 228.0",[23,810,811],{"x":194,"y":195,"fill":196,"style":197},"Peak memory after each change",[23,813,816],{"x":814,"y":815,"fill":174,"style":202},"282.9","60.0","Before change",[23,818,820],{"x":819,"y":815,"fill":174,"style":202},"418.4","After change",[23,822,824],{"x":159,"y":823,"fill":196,"style":202},"97.4","No cross-collection",[23,826,281],{"x":159,"y":827,"fill":196,"style":202},"113.0",[23,829,833],{"x":830,"y":831,"fill":208,"style":832},"693.5","94.5","font-size:11.5px;text-anchor:start;font-weight:700","5.3 GB",[23,835,839],{"x":836,"y":837,"fill":838,"style":832},"486.8","114.5","#3f6410","2.9 GB",[23,841,843],{"x":159,"y":842,"fill":196,"style":202},"157.2","Split catalogue data",[23,845,839],{"x":836,"y":846,"fill":208,"style":832},"146.5",[23,848,851],{"x":849,"y":850,"fill":838,"style":832},"392.0","166.5","1.8 GB",[23,853,855],{"x":159,"y":854,"fill":196,"style":202},"209.2","Eleventy 2.0 to 3.0",[23,857,851],{"x":849,"y":858,"fill":208,"style":832},"198.5",[23,860,863],{"x":861,"y":862,"fill":838,"style":832},"374.8","218.5","1.6 GB",[248,865,866],{},"Each row is cumulative; measured with \u002Fusr\u002Fbin\u002Ftime -v as maximum resident set size on the CI runner.",[41,868,870],{"id":869},"step-4-watch-out-for-computed-data-and-filters-that-cache","Step 4: Watch Out for Computed Data and Filters That Cache",[14,872,873,874,877,878,881,882,885,886,889],{},"Two smaller leaks turned up after the big ones were gone. A custom ",[26,875,876],{},"excerpt"," filter memoised its results in a module-level ",[26,879,880],{},"Map"," keyed by the input string, so every article's full content stayed referenced by the cache — the fix was to key by ",[26,883,884],{},"page.inputPath"," and store only the 300-character excerpt. And an ",[26,887,888],{},"eleventyComputed"," property that built a table of contents parsed the content with a full DOM library for every page, creating short-lived garbage that pushed peak memory up during rendering bursts; switching to a regex-based heading extractor on the Markdown source removed about 150 MB of peak.",[41,891,893],{"id":892},"step-5-size-the-heap-for-headroom-not-survival","Step 5: Size the Heap for Headroom, Not Survival",[14,895,896],{},"With peak memory at 1.6 GB, the default heap is enough, but the build still sets an explicit limit so failures are deterministic and well below the runner's physical memory:",[18,898,902],{"className":899,"code":900,"language":901,"meta":24,"style":24},"language-yaml shiki shiki-themes github-light github-dark","- run: npx @11ty\u002Feleventy\n  env:\n    NODE_OPTIONS: --max-old-space-size=3072\n","yaml",[26,903,904,918,926],{"__ignoreMap":24},[266,905,906,909,913,915],{"class":268,"line":269},[266,907,908],{"class":365},"- ",[266,910,912],{"class":911},"s9eBZ","run",[266,914,683],{"class":365},[266,916,917],{"class":376},"npx @11ty\u002Feleventy\n",[266,919,920,923],{"class":268,"line":362},[266,921,922],{"class":911},"  env",[266,924,925],{"class":365},":\n",[266,927,928,931,933],{"class":268,"line":403},[266,929,930],{"class":911},"    NODE_OPTIONS",[266,932,683],{"class":365},[266,934,935],{"class":376},"--max-old-space-size=3072\n",[14,937,938,939,286],{},"3 GB gives almost 2× headroom over the measured peak while leaving 4 GB of the runner for the OS, file cache and any parallel steps. A build-time regression check records peak RSS on every main-branch build and warns when it grows more than 20% week over week, as in ",[35,940,942],{"href":941},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fmeasuring-build-time-regressions-in-ci\u002F","Measuring Build-Time Regressions in CI",[41,944,946],{"id":945},"measured-impact","Measured Impact",[49,948,949,965],{},[52,950,951],{},[55,952,953,956,959,962],{},[58,954,955],{},"Measure",[58,957,958],{},"Before",[58,960,961],{},"After",[58,963,964],{},"Tool",[68,966,967,982,996,1010,1026],{},[55,968,969,972,975,977],{},[73,970,971],{},"Peak resident memory",[73,973,974],{},"5.3 GB (with 8 GB heap)",[73,976,863],{},[73,978,979],{},[26,980,981],{},"\u002Fusr\u002Fbin\u002Ftime -v",[55,983,984,987,990,993],{},[73,985,986],{},"Build with default heap",[73,988,989],{},"Fails at ~2.5 min",[73,991,992],{},"Succeeds",[73,994,995],{},"GitHub Actions",[55,997,998,1001,1004,1007],{},[73,999,1000],{},"Full build time",[73,1002,1003],{},"3 min 41 s",[73,1005,1006],{},"2 min 06 s",[73,1008,1009],{},"CI logs",[55,1011,1012,1015,1018,1021],{},[73,1013,1014],{},"Search index file",[73,1016,1017],{},"41 MB",[73,1019,1020],{},"22 MB",[73,1022,1023],{},[26,1024,1025],{},"ls -l",[55,1027,1028,1031,1034,1037],{},[73,1029,1030],{},"Global data in cascade",[73,1032,1033],{},"186 MB",[73,1035,1036],{},"0.3 MB index",[73,1038,1039],{},[26,1040,1041],{},"du -sh",[14,1043,1044],{},"Build time fell as a side effect: less memory meant far fewer full garbage collections, which had been consuming about 35 seconds of the old build.",[122,1046,1047,1179],{},[125,1048,133,1053,133,1056,133,1059,133,1062,133,1164],{"viewBox":1049,"role":128,"ariaLabelledBy":1050,"xmlns":132},"0 0 760 168",[1051,1052],"e11oom-flow-title","e11oom-flow-desc",[135,1054,1055],{"id":1051},"Diagnosis steps from out-of-memory error to fix",[139,1057,1058],{"id":1052},"Five steps. Raise the heap temporarily so the build completes. Take a heap snapshot near the end of the build. Group retained memory by retainer. Fix the largest retainer, usually templateContent loops or large global data. Measure peak resident memory again and repeat until there is headroom.",[143,1060],{"x":145,"y":145,"width":146,"height":1061,"fill":148},"168",[150,1063,153,1064,153,1071,153,1076,153,1080,153,1083,153,1086,153,1090,153,1093,153,1096,153,1099,153,1102,153,1108,153,1112,153,1117,153,1121,153,1124,153,1127,153,1130,153,1133,153,1136,153,1141,153,1144,153,1148,153,1152,153,1155,153,1158,153,1161,133],{"style":152},[143,1065],{"x":159,"y":1066,"width":1067,"height":1068,"rx":1069,"fill":179,"opacity":1070,"stroke":181,"style":191},"64.0","116.8","88.4","8","0.24",[143,1072],{"x":1073,"y":1066,"width":1067,"height":1068,"rx":1069,"fill":1074,"opacity":1075,"stroke":1074,"style":191},"170.8","#1982c4","0.14",[187,1077],{"d":1078,"fill":190,"stroke":174,"style":1079},"M138.8 108.2 L166.8 108.2","stroke-width:2px;marker-end:url(#e11oom-flow-arrow)",[143,1081],{"x":1082,"y":1066,"width":1067,"height":1068,"rx":1069,"fill":1074,"opacity":1075,"stroke":1074,"style":191},"321.6",[187,1084],{"d":1085,"fill":190,"stroke":174,"style":1079},"M289.6 108.2 L317.6 108.2",[143,1087],{"x":1088,"y":1066,"width":1067,"height":1068,"rx":1069,"fill":779,"opacity":1089,"stroke":781,"style":191},"472.4","0.2",[187,1091],{"d":1092,"fill":190,"stroke":174,"style":1079},"M440.4 108.2 L468.4 108.2",[143,1094],{"x":1095,"y":1066,"width":1067,"height":1068,"rx":1069,"fill":779,"opacity":1089,"stroke":781,"style":191},"623.2",[187,1097],{"d":1098,"fill":190,"stroke":174,"style":1079},"M591.2 108.2 L619.2 108.2",[23,1100,1101],{"x":194,"y":195,"fill":196,"style":197},"Diagnosing an Eleventy out-of-memory error",[23,1103,1107],{"x":1104,"y":1105,"fill":196,"style":1106},"78.4","97.5","font-size:13px;text-anchor:middle;font-weight:700","Raise heap",[23,1109,1111],{"x":1104,"y":1110,"fill":196,"style":1106},"114.4","temporarily",[23,1113,1116],{"x":1104,"y":1114,"fill":174,"style":1115},"131.3","font-size:11px;text-anchor:middle","build completes",[23,1118,1120],{"x":1119,"y":1105,"fill":196,"style":1106},"229.2","Heap",[23,1122,1123],{"x":1119,"y":1110,"fill":196,"style":1106},"snapshot",[23,1125,1126],{"x":1119,"y":1114,"fill":174,"style":1115},"near end of build",[23,1128,1129],{"x":194,"y":1105,"fill":196,"style":1106},"Group by",[23,1131,1132],{"x":194,"y":1110,"fill":196,"style":1106},"retainer",[23,1134,1135],{"x":194,"y":1114,"fill":174,"style":1115},"largest first",[23,1137,1140],{"x":1138,"y":1139,"fill":196,"style":1106},"530.8","90.4","Fix the",[23,1142,1132],{"x":1138,"y":1143,"fill":196,"style":1106},"107.3",[23,1145,1147],{"x":1138,"y":1146,"fill":174,"style":1115},"124.2","templateContent,",[23,1149,1151],{"x":1138,"y":1150,"fill":174,"style":1115},"138.5","global data",[23,1153,955],{"x":1154,"y":1139,"fill":196,"style":1106},"681.6",[23,1156,1157],{"x":1154,"y":1143,"fill":196,"style":1106},"again",[23,1159,1160],{"x":1154,"y":1146,"fill":174,"style":1115},"repeat to",[23,1162,1163],{"x":1154,"y":1150,"fill":174,"style":1115},"headroom",[1165,1166,153,1167,133],"defs",{},[1168,1169,1175,1176,153],"marker",{"id":1170,"viewBox":1171,"refX":1069,"refY":1172,"markerWidth":1173,"markerHeight":1173,"orient":1174},"e11oom-flow-arrow","0 0 10 10","5","7","auto-start-reverse","\n      ",[187,1177],{"d":1178,"fill":174},"M0 0 L10 5 L0 10 z",[248,1180,1181],{},"Raising the heap is step one of the diagnosis, not the fix.",[41,1183,1185],{"id":1184},"pitfalls-rollback","Pitfalls & Rollback",[312,1187,1188,1197,1211,1217,1223],{},[315,1189,1190,1196],{},[318,1191,1192,1193,286],{},"Only raising ",[26,1194,1195],{},"max-old-space-size"," The next 10% of content growth breaks the build again, or the runner swaps and builds take three times as long.",[315,1198,1199,1205,1206,1208,1209,286],{},[318,1200,1201,1202,1204],{},"Reading ",[26,1203,281],{}," in loops over large collections."," Use ",[26,1207,690],{}," fields, or read output in ",[26,1210,97],{},[315,1212,1213,1216],{},[318,1214,1215],{},"Huge global data files."," Split them and load per page.",[315,1218,1219,1222],{},[318,1220,1221],{},"Module-level caches in filters."," Key them narrowly and store only what is needed.",[315,1224,1225,1228],{},[318,1226,1227],{},"Rollback:"," each change is independent. The search index can return to a template and the catalogue to global data at any time; the memory cost returns with them.",[41,1230,1232],{"id":1231},"conclusion","Conclusion",[14,1234,1235],{},"Eleventy holds the whole site in memory, so out-of-memory errors come from anything that multiplies per-page data across the site: templates that read every item's rendered content, global data used by a fraction of pages, and caches that keep content alive. On the 12,400-page knowledge base, removing those took peak memory from 5.3 GB to 1.6 GB and the build from 3 minutes 41 seconds to 2 minutes 6 seconds, on the default heap.",[41,1237,1239],{"id":1238},"faq","FAQ",[1241,1242,1244],"h3",{"id":1243},"is-raising-max-old-space-size-enough-to-fix-an-eleventy-out-of-memory-error","Is raising max-old-space-size enough to fix an Eleventy out-of-memory error?",[14,1246,1247],{},"It buys time, but it does not fix the cause. Memory use on a growing site keeps rising until it hits the new limit or the CI runner's physical memory, at which point the build fails again or the runner starts swapping. Raise the heap to unblock the build, then find what is holding memory, which is usually collections that store full rendered content or global data loaded into every template.",[1241,1249,1251],{"id":1250},"why-does-eleventy-use-so-much-memory-on-large-sites","Why does Eleventy use so much memory on large sites?",[14,1253,1254],{},"Eleventy keeps the data cascade and every collection item in memory for the whole build, because any template can reference any collection. Each item holds its front matter, its raw input, and after rendering its output content. On a 12,000-page site with templates that read templateContent from collections, that output is held several times over.",[1241,1256,1258],{"id":1257},"does-eleventy-3-use-less-memory-than-eleventy-2","Does Eleventy 3 use less memory than Eleventy 2?",[14,1260,1261],{},"In the measurements in this guide, Eleventy 3.0 used about 12 percent less peak heap on the same site, mostly from leaner internal structures and ESM loading. The larger savings came from changing templates and data, which apply to both versions.",[1241,1263,1265],{"id":1264},"how-do-i-find-which-template-is-using-the-memory","How do I find which template is using the memory?",[14,1267,1268],{},"Take a heap snapshot during the build with node inspect-brk and Chrome DevTools, or run the build with sampling heap profiler flags, and look at retained size by constructor. Strings holding rendered HTML and large arrays from global data files are the usual culprits. Building a subset of the site with a smaller input directory and comparing peak memory also narrows it down quickly.",[41,1270,1272],{"id":1271},"related","Related",[312,1274,1275,1284,1291,1298,1305],{},[315,1276,1277,1280,1281,1283],{},[318,1278,1279],{},"Parent:"," ",[35,1282,38],{"href":37}," — memory and build behaviour at scale.",[315,1285,1286,1290],{},[35,1287,1289],{"href":1288},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fastro-vs-eleventy-build-times-at-10000-pages\u002F","Astro vs Eleventy Build Times at 10,000 Pages"," — how both generators scale.",[315,1292,1293,1297],{},[35,1294,1296],{"href":1295},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fcontent-collections-vs-eleventy-data-cascade\u002F","Content Collections vs the Eleventy Data Cascade"," — where data lives during a build.",[315,1299,1300,1304],{},[35,1301,1303],{"href":1302},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fupgrading-eleventy-2-to-3-with-esm-configuration\u002F","Upgrading Eleventy 2 to 3 With ESM Configuration"," — the upgrade that saved the last 200 MB.",[315,1306,1307,1311],{},[35,1308,1310],{"href":1309},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners\u002F","Reducing Hugo Memory Usage on CI Runners"," — the same problem in Hugo.",[1313,1314,1315],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}",{"title":24,"searchDepth":362,"depth":362,"links":1317},[1318,1319,1320,1321,1322,1323,1324,1325,1326,1327,1333],{"id":43,"depth":362,"text":44},{"id":253,"depth":362,"text":254},{"id":306,"depth":362,"text":307},{"id":607,"depth":362,"text":608},{"id":869,"depth":362,"text":870},{"id":892,"depth":362,"text":893},{"id":945,"depth":362,"text":946},{"id":1184,"depth":362,"text":1185},{"id":1231,"depth":362,"text":1232},{"id":1238,"depth":362,"text":1239,"children":1328},[1329,1330,1331,1332],{"id":1243,"depth":403,"text":1244},{"id":1250,"depth":403,"text":1251},{"id":1257,"depth":403,"text":1258},{"id":1264,"depth":403,"text":1265},{"id":1271,"depth":362,"text":1272},[1335,1338,1341,1342],{"name":1336,"item":1337},"Home","\u002F",{"name":1339,"item":1340},"Choosing the Right Static Site Generator for Production","\u002Fchoosing-the-right-static-site-generator-for-production\u002F",{"name":38,"item":37},{"name":5,"item":1343},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-eleventy-out-of-memory-errors-on-large-collections\u002F","2026-10-02","Diagnose \"JavaScript heap out of memory\" in Eleventy builds of large collections, cut peak memory with data and template fixes, and size the Node heap safely.","md",[1348,1349,1350,1351],{"q":1244,"a":1247},{"q":1251,"a":1254},{"q":1258,"a":1261},{"q":1265,"a":1268},{},true,"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-eleventy-out-of-memory-errors-on-large-collections",{"title":5,"description":1345},"choosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-eleventy-out-of-memory-errors-on-large-collections\u002Findex","article","9cFy5_crU4ixtTo2lAv_11YX3pKo2OikNEcpMnsuo1s",[1360,1363,1366,1369,1372,1375,1378,1381,1384,1387,1389,1392,1394,1397,1400,1403,1404,1407,1409,1412,1415,1418,1421,1424,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,1503,1506,1509,1512,1514,1517,1520,1523,1526,1529,1532,1535,1538,1541,1544,1547,1550,1553,1556,1559,1562,1565,1568,1571,1574,1577,1580,1583,1586,1589,1592,1595,1598,1601,1604,1607,1610,1613,1616,1619,1622,1625,1628,1631,1634,1637,1640,1643,1646,1649,1652,1655,1658,1661,1664,1667,1670,1673,1676,1679,1682,1685,1688,1691,1694,1697,1700,1703,1706,1709,1712,1715,1718,1721,1724,1727,1730,1733,1736,1739,1742,1745,1748,1751,1754,1757,1760,1763,1766,1769,1772,1775,1778,1781,1784,1787,1790,1793,1796,1799,1802,1805,1808,1811,1814,1817,1820,1823,1826,1829,1832,1835,1838,1841,1844,1847,1850,1853,1856,1859,1862,1865,1868,1871,1874,1877,1880,1883,1886,1889,1892,1895,1898,1901,1904,1907,1910,1913,1916,1919,1922,1925,1928,1931,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,2221,2224,2227,2230,2233,2236,2239,2242,2245,2248,2251,2254,2257,2260,2263,2266,2269,2272,2275,2278,2281,2284,2287,2290,2293,2296,2299,2302,2305,2308,2311,2314,2317,2320,2323,2326,2329,2332,2335,2338,2341,2344,2347,2350,2353,2356,2359,2362,2365,2368,2371,2374,2377,2380,2383,2386,2389,2392,2395,2398,2401,2404,2407,2410,2413,2416,2419,2422,2425,2428,2431,2434,2437,2440,2443,2446,2449,2452,2455,2458,2461,2464,2467,2470,2473,2476,2479,2482,2485,2488,2491,2494,2497],{"path":1361,"title":1362},"\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":1364,"title":1365},"\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":1367,"title":1368},"\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":1370,"title":1371},"\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":1373,"title":1374},"\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":1376,"title":1377},"\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":1379,"title":1380},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1382,"title":1383},"\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":1385,"title":1386},"\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":1388,"title":1289},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fastro-vs-eleventy-build-times-at-10000-pages",{"path":1390,"title":1391},"\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":1393,"title":1296},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fcontent-collections-vs-eleventy-data-cascade",{"path":1395,"title":1396},"\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":1398,"title":1399},"\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":1401,"title":1402},"\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":1354,"title":5},{"path":1405,"title":1406},"\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":1408,"title":38},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites",{"path":1410,"title":1411},"\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":1413,"title":1414},"\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":1416,"title":1417},"\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":1419,"title":1420},"\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":1422,"title":1423},"\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":1425,"title":1303},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fupgrading-eleventy-2-to-3-with-esm-configuration",{"path":1427,"title":1428},"\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":1430,"title":1431},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1433,"title":1434},"\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":1436,"title":1437},"\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":1439,"title":1440},"\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":1442,"title":1443},"\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":1445,"title":1446},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1448,"title":1449},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1451,"title":1452},"\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":1454,"title":1455},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1457,"title":1458},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1460,"title":1461},"\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":1463,"title":1464},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1466,"title":1467},"\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":1469,"title":1470},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1472,"title":1473},"\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":1475,"title":1476},"\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":1478,"title":1479},"\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":1481,"title":1482},"\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":1484,"title":1485},"\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":1487,"title":1488},"\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":1490,"title":1491},"\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":1493,"title":1494},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1496,"title":1497},"\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":1499,"title":1500},"\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":1502,"title":1310},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners",{"path":1504,"title":1505},"\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":1507,"title":1508},"\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":1510,"title":1511},"\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":1513,"title":1339},"\u002Fchoosing-the-right-static-site-generator-for-production",{"path":1515,"title":1516},"\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":1518,"title":1519},"\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":1521,"title":1522},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1524,"title":1525},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1527,"title":1528},"\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":1530,"title":1531},"\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":1533,"title":1534},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1536,"title":1537},"\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":1539,"title":1540},"\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":1542,"title":1543},"\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":1545,"title":1546},"\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":1548,"title":1549},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1551,"title":1552},"\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":1554,"title":1555},"\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":1557,"title":1558},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1560,"title":1561},"\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":1563,"title":1564},"\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":1566,"title":1567},"\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":1569,"title":1570},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1572,"title":1573},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1575,"title":1576},"\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":1578,"title":1579},"\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":1581,"title":1582},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1584,"title":1585},"\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":1587,"title":1588},"\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":1590,"title":1591},"\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":1593,"title":1594},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1596,"title":1597},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1599,"title":1600},"\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":1602,"title":1603},"\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":1605,"title":1606},"\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":1608,"title":1609},"\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":1611,"title":1612},"\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":1614,"title":1615},"\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":1617,"title":1618},"\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":1620,"title":1621},"\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":1623,"title":1624},"\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":1626,"title":1627},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1629,"title":1630},"\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":1632,"title":1633},"\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":1635,"title":1636},"\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":1638,"title":1639},"\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":1641,"title":1642},"\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":1644,"title":1645},"\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":1647,"title":1648},"\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":1650,"title":1651},"\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":1653,"title":1654},"\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":1656,"title":1657},"\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":1659,"title":1660},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1662,"title":1663},"\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":1665,"title":1666},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1668,"title":1669},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1671,"title":1672},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1674,"title":1675},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1677,"title":1678},"\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":1680,"title":1681},"\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":1683,"title":1684},"\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":1686,"title":1687},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1689,"title":1690},"\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":1692,"title":1693},"\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":1695,"title":1696},"\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":1698,"title":1699},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1701,"title":1702},"\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":1704,"title":1705},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1707,"title":1708},"\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":1710,"title":1711},"\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":1713,"title":1714},"\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":1716,"title":1717},"\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":1719,"title":1720},"\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":1722,"title":1723},"\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":1725,"title":1726},"\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":1728,"title":1729},"\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":1731,"title":1732},"\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":1734,"title":1735},"\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":1737,"title":1738},"\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":1740,"title":1741},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1743,"title":1744},"\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":1746,"title":1747},"\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":1749,"title":1750},"\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":1752,"title":1753},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-busting-with-content-hashed-filenames","Cache Busting with Content-Hashed Filenames",{"path":1755,"title":1756},"\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":1758,"title":1759},"\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":1761,"title":1762},"\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":1764,"title":1765},"\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":1767,"title":1768},"\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":1770,"title":1771},"\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":1773,"title":1774},"\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":1776,"title":1777},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1779,"title":1780},"\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":1782,"title":1783},"\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":1785,"title":1786},"\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":1788,"title":1789},"\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":1791,"title":1792},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1794,"title":1795},"\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":1797,"title":1798},"\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":1800,"title":1801},"\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":1803,"title":1804},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":1806,"title":1807},"\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":1809,"title":1810},"\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":1812,"title":1813},"\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":1815,"title":1816},"\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":1818,"title":1819},"\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":1821,"title":1822},"\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":1824,"title":1825},"\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":1827,"title":1828},"\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":1830,"title":1831},"\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":1833,"title":1834},"\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":1836,"title":1837},"\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":1839,"title":1840},"\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":1842,"title":1843},"\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":1845,"title":1846},"\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":1848,"title":1849},"\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":1851,"title":1852},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1854,"title":1855},"\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":1857,"title":1858},"\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":1860,"title":1861},"\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":1863,"title":1864},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":1866,"title":1867},"\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":1869,"title":1870},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1872,"title":1873},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1875,"title":1876},"\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":1878,"title":1879},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1881,"title":1882},"\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":1884,"title":1885},"\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":1887,"title":1888},"\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":1890,"title":1891},"\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":1893,"title":1894},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":1896,"title":1897},"\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":1899,"title":1900},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":1902,"title":1903},"\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":1905,"title":1906},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":1908,"title":1909},"\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":1911,"title":1912},"\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":1914,"title":1915},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1917,"title":1918},"\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":1920,"title":1921},"\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":1923,"title":1924},"\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":1926,"title":1927},"\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":1929,"title":1930},"\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":1932,"title":1933},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1935,"title":1936},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1938,"title":1939},"\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":1941,"title":1942},"\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":1944,"title":1945},"\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":1947,"title":1948},"\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":1950,"title":1951},"\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":1953,"title":1954},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1956,"title":1957},"\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":1959,"title":1960},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":1962,"title":1963},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1965,"title":1966},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":1968,"title":1969},"\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":1971,"title":1972},"\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":1974,"title":1975},"\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":1977,"title":1978},"\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":1980,"title":1981},"\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":1983,"title":1984},"\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":1986,"title":1987},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1989,"title":1990},"\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":1992,"title":1993},"\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":1995,"title":1996},"\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":1998,"title":1999},"\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":2001,"title":2002},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":2004,"title":2005},"\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":2007,"title":2008},"\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":2010,"title":2011},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":2013,"title":2014},"\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":2016,"title":2017},"\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":2019,"title":2020},"\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":2022,"title":2023},"\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":2025,"title":2026},"\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":2028,"title":2029},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2031,"title":2032},"\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":2034,"title":2035},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2037,"title":2038},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2040,"title":2041},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2043,"title":2044},"\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":2046,"title":2047},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2049,"title":2050},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2052,"title":2053},"\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":2055,"title":2056},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2058,"title":2059},"\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":2061,"title":2062},"\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":2064,"title":2065},"\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":2067,"title":2068},"\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":2070,"title":2071},"\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":2073,"title":2074},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2076,"title":2077},"\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":2079,"title":2080},"\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":2082,"title":2083},"\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":2085,"title":2086},"\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":2088,"title":2089},"\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":2091,"title":2092},"\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":2094,"title":2095},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2097,"title":2098},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2100,"title":2101},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2103,"title":2104},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2106,"title":2107},"\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":2109,"title":2110},"\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":2112,"title":2113},"\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":2115,"title":2116},"\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":2118,"title":2119},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2121,"title":2122},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2124,"title":2125},"\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":2127,"title":2128},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2130,"title":2131},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2133,"title":2134},"\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":2136,"title":2137},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2139,"title":2140},"\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":2142,"title":2143},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2145,"title":2146},"\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":2148,"title":2149},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2151,"title":2152},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2154,"title":2155},"\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":2157,"title":2158},"\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":2160,"title":2161},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2163,"title":2164},"\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":2166,"title":2167},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2169,"title":2170},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2172,"title":2173},"\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":2175,"title":2176},"\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":2178,"title":2179},"\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":2181,"title":2182},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2184,"title":2185},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2187,"title":2188},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2190,"title":2191},"\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":2193,"title":2194},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2196,"title":2197},"\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":2199,"title":2200},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fcaching-hugo-builds-in-github-actions","Caching Hugo Builds in GitHub Actions",{"path":2202,"title":2203},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2205,"title":2206},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2208,"title":2209},"\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":2211,"title":2212},"\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":2214,"title":2215},"\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":2217,"title":2218},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2220,"title":942},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fmeasuring-build-time-regressions-in-ci",{"path":2222,"title":2223},"\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":2225,"title":2226},"\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":2228,"title":2229},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":2231,"title":2232},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2234,"title":2235},"\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":2237,"title":2238},"\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":2240,"title":2241},"\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":2243,"title":2244},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2246,"title":2247},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2249,"title":2250},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2252,"title":2253},"\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":2255,"title":2256},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2258,"title":2259},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2261,"title":2262},"\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":2264,"title":2265},"\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":2267,"title":2268},"\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":2270,"title":2271},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2273,"title":2274},"\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":2276,"title":2277},"\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":2279,"title":2280},"\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":2282,"title":2283},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2285,"title":2286},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2288,"title":2289},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2291,"title":2292},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-redirects-and-rewrites-for-static-sites","Netlify Redirects and Rewrites for Static Sites",{"path":2294,"title":2295},"\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":2297,"title":2298},"\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":2300,"title":2301},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-isr-vs-static-generation-for-ssgs","Vercel ISR vs Static Generation for SSGs",{"path":2303,"title":2304},"\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":2306,"title":2307},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2309,"title":2310},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2312,"title":2313},"\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":2315,"title":2316},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2318,"title":2319},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2321,"title":2322},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2324,"title":2325},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2327,"title":2328},"\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":2330,"title":2331},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2333,"title":2334},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2336,"title":2337},"\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":2339,"title":2340},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2342,"title":2343},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2345,"title":2346},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2348,"title":2349},"\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":2351,"title":2352},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2354,"title":2355},"\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":2357,"title":2358},"\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":2360,"title":2361},"\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":2363,"title":2364},"\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":2366,"title":2367},"\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":2369,"title":2370},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2372,"title":2373},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2375,"title":2376},"\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":2378,"title":2379},"\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":2381,"title":2382},"\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":2384,"title":2385},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2387,"title":2388},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2390,"title":2391},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2393,"title":2394},"\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":2396,"title":2397},"\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":2399,"title":2400},"\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":2402,"title":2403},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2405,"title":2406},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fwriting-a-content-security-policy-for-a-static-site","Writing a Content Security Policy for a Static Site",{"path":2408,"title":2409},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2411,"title":2412},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2414,"title":2415},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2417,"title":2418},"\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":2420,"title":2421},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2423,"title":2424},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2426,"title":2427},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2429,"title":2430},"\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":2432,"title":2433},"\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":2435,"title":2436},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2438,"title":2439},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2441,"title":2442},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2444,"title":2445},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2447,"title":2448},"\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":2450,"title":2451},"\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":2453,"title":2454},"\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":2456,"title":2457},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2459,"title":2460},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2462,"title":2463},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2465,"title":2466},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2468,"title":2469},"\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":2471,"title":2472},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2474,"title":2475},"\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":2477,"title":2478},"\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":2480,"title":2481},"\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":2483,"title":2484},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2486,"title":2487},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2489,"title":2490},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2492,"title":2493},"\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":2495,"title":2496},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2498,"title":2499},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2501,"tools":2505},{"label":2502,"plural":2503,"u":2504},"Fix","Fixes","\u002Fguides\u002Ffixes\u002F",[2506],{"label":2507,"u":2508},"Eleventy","\u002Ftools\u002Feleventy\u002F",1790943191176]