[{"data":1,"prerenderedAt":1534},["ShallowReactive",2],{"page:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners":3,"all-docs-nav":993},{"id":4,"title":5,"body":6,"breadcrumb":968,"dateModified":978,"datePublished":978,"description":979,"extension":980,"faq":981,"meta":986,"navigation":987,"path":988,"seo":989,"slug":12,"stem":990,"type":991,"__hash__":992},"content\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners\u002Findex.md","Reducing Hugo Memory Usage on CI Runners",{"type":7,"value":8,"toc":950},"minimark",[9,13,22,31,36,49,53,56,122,129,239,242,246,249,334,429,433,448,463,480,490,500,551,597,601,680,779,782,786,816,820,827,831,863,867,873,877,882,885,889,892,896,899,903,906,910,946],[10,11,5],"h1",{"id":12},"reducing-hugo-memory-usage-on-ci-runners",[14,15,16,17,21],"p",{},"Hugo's speed comes partly from keeping the whole site in memory: every page, its front matter, its rendered content and its output are held until the build finishes. On a laptop with 32 GB nobody notices. On a hosted CI runner or a static host's build container with 4 GB, a growing docs site one day fails with ",[18,19,20],"code",{},"fatal error: runtime: out of memory"," or is killed silently by the container, and the build that took 40 seconds yesterday does not complete today.",[14,23,24,25,30],{},"This guide measures peak memory on a 30,000-page Hugo site, identifies what drives it, and applies the changes that cut it from 7.8 GB to 3.1 GB so the build fits comfortably in a standard runner again. It is part of ",[26,27,29],"a",{"href":28},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002F","Hugo Build Times for Large Repositories",".",[32,33,35],"h2",{"id":34},"prerequisites","Prerequisites",[37,38,39,43,46],"ul",{},[40,41,42],"li",{},"Hugo extended 0.120 or newer.",[40,44,45],{},"A CI job where you can wrap the build command and read its output.",[40,47,48],{},"The ability to run the build locally with the same content, to iterate faster than CI allows.",[32,50,52],{"id":51},"step-1-measure-peak-memory","Step 1: Measure Peak Memory",[14,54,55],{},"Wall time is logged by every CI system; peak memory is not. Add it:",[57,58,63],"pre",{"className":59,"code":60,"language":61,"meta":62,"style":62},"language-bash shiki shiki-themes github-light github-dark","\u002Fusr\u002Fbin\u002Ftime -v hugo --gc --minify 2> time.txt\ngrep -E 'Maximum resident set size|Elapsed' time.txt\n#   Maximum resident set size (kbytes): 8164320\n#   Elapsed (wall clock) time (h:mm:ss or m:ss): 1:47.21\n","bash","",[18,64,65,95,109,116],{"__ignoreMap":62},[66,67,70,74,78,82,85,88,92],"span",{"class":68,"line":69},"line",1,[66,71,73],{"class":72},"sScJk","\u002Fusr\u002Fbin\u002Ftime",[66,75,77],{"class":76},"sj4cs"," -v",[66,79,81],{"class":80},"sZZnC"," hugo",[66,83,84],{"class":76}," --gc",[66,86,87],{"class":76}," --minify",[66,89,91],{"class":90},"szBVR"," 2>",[66,93,94],{"class":80}," time.txt\n",[66,96,98,101,104,107],{"class":68,"line":97},2,[66,99,100],{"class":72},"grep",[66,102,103],{"class":76}," -E",[66,105,106],{"class":80}," 'Maximum resident set size|Elapsed'",[66,108,94],{"class":80},[66,110,112],{"class":68,"line":111},3,[66,113,115],{"class":114},"sJ8bj","#   Maximum resident set size (kbytes): 8164320\n",[66,117,119],{"class":68,"line":118},4,[66,120,121],{"class":114},"#   Elapsed (wall clock) time (h:mm:ss or m:ss): 1:47.21\n",[14,123,124,125,128],{},"For a timeline rather than a single number, ",[18,126,127],{},"hugo --printMemoryUsage"," logs heap usage every few seconds, which shows whether the peak happens during content loading, rendering or image processing. On this site the peak came late in rendering, when image processing and page output overlapped.",[130,131,132,235],"figure",{},[133,134,141,142,141,146,141,150,141,157],"svg",{"viewBox":135,"role":136,"ariaLabelledBy":137,"xmlns":140},"0 0 760 260","img",[138,139],"hmem-tl-title","hmem-tl-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[143,144,145],"title",{"id":138},"Memory over the course of one build",[147,148,149],"desc",{"id":139},"A line of resident memory over a 107 second build. Memory rises to about 2.5 gigabytes while content loads in the first 20 seconds, climbs to about 4.5 during taxonomy assembly, then peaks at 7.8 gigabytes around 80 seconds when image processing overlaps page rendering, before falling as output is written.",[151,152],"rect",{"x":153,"y":153,"width":154,"height":155,"fill":156},"0","760","260","#ffffff",[158,159,161,162,161,170,161,177,161,180,161,185,161,189,161,193,161,197,161,203,161,210,161,216,161,221,161,227,161,231,141],"g",{"style":160},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[163,164,169],"text",{"x":165,"y":166,"fill":167,"style":168},"380","28","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Resident memory during the build (GB)",[68,171],{"x1":172,"y1":173,"x2":174,"y2":173,"stroke":175,"style":176},"70","210","720","#556071","stroke-width:1.5px",[68,178],{"x1":172,"y1":179,"x2":172,"y2":173,"stroke":175,"style":176},"50",[163,181,153],{"x":182,"y":183,"fill":175,"style":184},"62","214","font-size:11px;text-anchor:end",[163,186,188],{"x":182,"y":187,"fill":175,"style":184},"130","4",[163,190,192],{"x":182,"y":191,"fill":175,"style":184},"54","8",[68,194],{"x1":172,"y1":187,"x2":174,"y2":187,"stroke":195,"style":196},"#d83b41","stroke-width:1px;stroke-dasharray:5 4",[163,198,202],{"x":199,"y":200,"fill":201,"style":184},"716","124","#b32b30","4 GB container",[204,205],"polyline",{"points":206,"fill":207,"stroke":208,"style":209},"70,210 130,160 190,158 260,122 330,118 420,96 520,54 580,70 640,140 700,190","none","#6a4c93","stroke-width:2.5px",[163,211,215],{"x":212,"y":213,"fill":175,"style":214},"150","152","font-size:11px","load content",[163,217,220],{"x":218,"y":219,"fill":175,"style":214},"295","110","taxonomies",[163,222,226],{"x":223,"y":224,"fill":201,"style":225},"520","46","font-size:11px;font-weight:700;text-anchor:middle","peak 7.8: images + render",[163,228,230],{"x":172,"y":229,"fill":175,"style":214},"228","0 s",[163,232,234],{"x":233,"y":229,"fill":175,"style":184},"700","107 s",[236,237,238],"figcaption",{},"The timeline pointed straight at the image-processing phase before any experiment was run.",[14,240,241],{},"Reading the shape is worth a minute before changing anything. A curve that climbs steadily and stays high points at content and data held for the whole build. A late spike that collapses points at a phase — image processing, a large output format, a template that assembles a huge slice on some pages. A sawtooth suggests garbage collection is keeping up and the peak is set by a single moment of overlap, which is often fixable by reducing concurrency during that phase.",[32,243,245],{"id":244},"step-2-find-what-drives-the-peak","Step 2: Find What Drives the Peak",[14,247,248],{},"Build variations of the site with one factor removed at a time and measure each:",[250,251,252,268],"table",{},[253,254,255],"thead",{},[256,257,258,262,265],"tr",{},[259,260,261],"th",{},"Variation",[259,263,264],{},"Peak RSS",[259,266,267],{},"Change",[269,270,271,283,294,309,323],"tbody",{},[256,272,273,277,280],{},[274,275,276],"td",{},"Full build",[274,278,279],{},"7.8 GB",[274,281,282],{},"—",[256,284,285,288,291],{},[274,286,287],{},"Image processing disabled (placeholders)",[274,289,290],{},"4.9 GB",[274,292,293],{},"−2.9 GB",[256,295,296,303,306],{},[274,297,298,299,302],{},"Taxonomy pages disabled (",[18,300,301],{},"disableKinds: [taxonomy, term]",")",[274,304,305],{},"6.6 GB",[274,307,308],{},"−1.2 GB",[256,310,311,317,320],{},[274,312,313,316],{},[18,314,315],{},"data\u002F"," API reference JSON (410 MB) not loaded",[274,318,319],{},"6.9 GB",[274,321,322],{},"−0.9 GB",[256,324,325,328,331],{},[274,326,327],{},"Search JSON output format disabled",[274,329,330],{},"7.1 GB",[274,332,333],{},"−0.7 GB",[130,335,336,426],{},[133,337,141,342,141,345,141,348,141,351],{"viewBox":338,"role":136,"ariaLabelledBy":339,"xmlns":140},"0 0 760 280",[340,341],"hmem-drv-title","hmem-drv-desc",[143,343,344],{"id":340},"What contributes to Hugo's peak memory",[147,346,347],{"id":341},"A stacked bar of 7.8 gigabytes peak memory. Image processing contributes 2.9 gigabytes, taxonomy pages 1.2, a 410 megabyte data file 0.9, the search JSON output 0.7, and the remaining 2.1 gigabytes is the content and pages themselves.",[151,349],{"x":153,"y":153,"width":154,"height":350,"fill":156},"280",[158,352,161,353,161,356,161,364,161,369,161,376,161,380,161,386,161,390,161,394,161,399,161,404,161,408,161,414,161,418,161,422,141],{"style":160},[163,354,355],{"x":165,"y":166,"fill":167,"style":168},"Peak 7.8 GB, attributed by removing one factor at a time",[151,357],{"x":358,"y":359,"width":360,"height":179,"fill":361,"opacity":362,"stroke":195,"style":363},"30","80","251","#ff595e","0.28","stroke-width:1px",[163,365,368],{"x":366,"y":219,"fill":167,"style":367},"155","text-anchor:middle","images 2.9 GB",[151,370],{"x":371,"y":359,"width":372,"height":179,"fill":373,"opacity":374,"stroke":375,"style":363},"281","104","#ffca3a","0.38","#a97b00",[163,377,379],{"x":378,"y":219,"fill":167,"style":367},"333","taxonomies 1.2",[151,381],{"x":382,"y":359,"width":383,"height":179,"fill":384,"opacity":385,"stroke":384,"style":363},"385","78","#1982c4","0.25",[163,387,389],{"x":388,"y":219,"fill":167,"style":367},"424","data 0.9",[151,391],{"x":392,"y":359,"width":393,"height":179,"fill":208,"opacity":385,"stroke":208,"style":363},"463","61",[163,395,398],{"x":396,"y":219,"fill":167,"style":397},"493","font-size:11px;text-anchor:middle","JSON 0.7",[151,400],{"x":401,"y":359,"width":402,"height":179,"fill":403,"stroke":175,"style":363},"524","182","#f8fafc",[163,405,407],{"x":406,"y":219,"fill":167,"style":367},"615","content + pages 2.1",[68,409],{"x1":410,"y1":411,"x2":410,"y2":412,"stroke":195,"style":413},"377","60","160","stroke-width:2px;stroke-dasharray:5 4",[163,415,417],{"x":410,"y":416,"fill":201,"style":225},"176","4 GB runner limit",[163,419,421],{"x":165,"y":420,"fill":175,"style":397},"226","\u002Fusr\u002Fbin\u002Ftime -v, max RSS, 30,000 pages, median of 3 builds per variation",[163,423,425],{"x":165,"y":424,"fill":175,"style":397},"246","(contributions overlap slightly, so they sum to a little more than the measured peak)",[236,427,428],{},"Image processing alone pushed the build past a 4 GB runner; the content itself needed only about 2 GB.",[32,430,432],{"id":431},"step-3-apply-the-fixes","Step 3: Apply the Fixes",[14,434,435,439,440,443,444,447],{},[436,437,438],"strong",{},"Cap Hugo's caches."," ",[18,441,442],{},"HUGO_MEMORYLIMIT"," tells Hugo how much memory (in GB) to aim for with its internal caches; it evicts more aggressively as it approaches the limit. On a 4 GB runner, ",[18,445,446],{},"HUGO_MEMORYLIMIT=2"," reduced the peak by 1.1 GB at a cost of 6 seconds of build time.",[14,449,450,453,454,457,458,462],{},[436,451,452],{},"Process images once, outside the render."," Most image memory came from resizing thousands of images during rendering while pages were also held in memory. Two changes helped. First, persist Hugo's ",[18,455,456],{},"resources\u002F_gen"," directory between CI runs (see ",[26,459,461],{"href":460},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fcaching-hugo-builds-in-github-actions\u002F","Caching Hugo Builds in GitHub Actions",") so unchanged images are not reprocessed at all. Second, standardise on three widths instead of per-template ad hoc sizes; the site had 11 distinct sizes, most used on one template. With a warm resource cache and fewer variants, image memory fell from 2.9 GB to 0.4 GB.",[14,464,465,468,469,471,472,475,476,479],{},[436,466,467],{},"Stop loading giant data files into every build."," The 410 MB API reference JSON in ",[18,470,315],{}," was parsed at startup and held for the whole build, although only 2,000 reference pages used it. Converting it to a content adapter (",[18,473,474],{},"_content.gotmpl",", available since Hugo 0.126) that creates pages from the data, or splitting it into one file per API group read with ",[18,477,478],{},"resources.Get"," only by the pages that need it, cut 0.9 GB.",[14,481,482,485,486,489],{},[436,483,484],{},"Drop unused page kinds."," The site generated taxonomy and term pages for tags nobody browsed. ",[18,487,488],{},"disableKinds = ['taxonomy', 'term']"," for tags (keeping categories) removed 9,400 pages and 1.2 GB. Check analytics before removing anything readers use.",[14,491,492,495,496,30],{},[436,493,494],{},"Review large output formats."," The search JSON output format built a single file of every page's full content. Replacing it with Pagefind, which indexes the built HTML after Hugo exits, moved that memory out of the Hugo process entirely — see ",[26,497,499],{"href":498},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind\u002F","Indexing Hugo Sites with Pagefind",[57,501,505],{"className":502,"code":503,"language":504,"meta":62,"style":62},"language-toml shiki shiki-themes github-light github-dark","# hugo.toml (excerpt)\ndisableKinds = ['taxonomy', 'term']\n[imaging]\n  quality = 78\n  resampleFilter = 'Lanczos'\n[caches.images]\n  dir = ':resourceDir\u002F_gen'\n  maxAge = -1\n","toml",[18,506,507,512,517,522,527,533,539,545],{"__ignoreMap":62},[66,508,509],{"class":68,"line":69},[66,510,511],{},"# hugo.toml (excerpt)\n",[66,513,514],{"class":68,"line":97},[66,515,516],{},"disableKinds = ['taxonomy', 'term']\n",[66,518,519],{"class":68,"line":111},[66,520,521],{},"[imaging]\n",[66,523,524],{"class":68,"line":118},[66,525,526],{},"  quality = 78\n",[66,528,530],{"class":68,"line":529},5,[66,531,532],{},"  resampleFilter = 'Lanczos'\n",[66,534,536],{"class":68,"line":535},6,[66,537,538],{},"[caches.images]\n",[66,540,542],{"class":68,"line":541},7,[66,543,544],{},"  dir = ':resourceDir\u002F_gen'\n",[66,546,548],{"class":68,"line":547},8,[66,549,550],{},"  maxAge = -1\n",[57,552,556],{"className":553,"code":554,"language":555,"meta":62,"style":62},"language-yaml shiki shiki-themes github-light github-dark","# CI step\n- run: \u002Fusr\u002Fbin\u002Ftime -v hugo --gc --minify 2> time.txt\n  env: { HUGO_MEMORYLIMIT: '2' }\n","yaml",[18,557,558,563,579],{"__ignoreMap":62},[66,559,560],{"class":68,"line":69},[66,561,562],{"class":114},"# CI step\n",[66,564,565,569,573,576],{"class":68,"line":97},[66,566,568],{"class":567},"sVt8B","- ",[66,570,572],{"class":571},"s9eBZ","run",[66,574,575],{"class":567},": ",[66,577,578],{"class":80},"\u002Fusr\u002Fbin\u002Ftime -v hugo --gc --minify 2> time.txt\n",[66,580,581,584,587,589,591,594],{"class":68,"line":111},[66,582,583],{"class":571},"  env",[66,585,586],{"class":567},": { ",[66,588,442],{"class":571},[66,590,575],{"class":567},[66,592,593],{"class":80},"'2'",[66,595,596],{"class":567}," }\n",[32,598,600],{"id":599},"measured-impact","Measured Impact",[250,602,603,616],{},[253,604,605],{},[256,606,607,610,613],{},[259,608,609],{},"Measure",[259,611,612],{},"Before",[259,614,615],{},"After",[269,617,618,627,637,647,658,669],{},[256,619,620,622,624],{},[274,621,264],{},[274,623,279],{},[274,625,626],{},"3.1 GB",[256,628,629,632,634],{},[274,630,631],{},"Build time, warm resource cache",[274,633,234],{},[274,635,636],{},"64 s",[256,638,639,642,644],{},[274,640,641],{},"Build time, cold resource cache",[274,643,234],{},[274,645,646],{},"131 s",[256,648,649,652,655],{},[274,650,651],{},"Pages generated",[274,653,654],{},"39,400",[274,656,657],{},"30,000",[256,659,660,663,666],{},[274,661,662],{},"Runner",[274,664,665],{},"16 GB larger runner (billed)",[274,667,668],{},"standard 4 vCPU \u002F 16 GB, with headroom",[256,670,671,674,677],{},[274,672,673],{},"Hosted-build container (4 GB)",[274,675,676],{},"out of memory",[274,678,679],{},"succeeds",[130,681,682,776],{},[133,683,141,687,141,690,141,693,141,695],{"viewBox":135,"role":136,"ariaLabelledBy":684,"xmlns":140},[685,686],"hmem-res-title","hmem-res-desc",[143,688,689],{"id":685},"Peak memory after each change",[147,691,692],{"id":686},"A descending step chart: 7.8 gigabytes at baseline, 6.7 after setting HUGO_MEMORYLIMIT, 4.2 after caching and standardising images, 3.3 after moving the data file to a content adapter, and 3.1 after disabling unused taxonomies and the JSON output. A dashed line marks the 4 gigabyte container limit, crossed after the image change.",[151,694],{"x":153,"y":153,"width":154,"height":155,"fill":156},[158,696,161,697,161,700,161,702,161,705,161,709,161,713,161,718,161,724,161,728,161,733,161,737,161,745,161,750,161,755,161,761,161,764,161,767,161,770,161,773,141],{"style":160},[163,698,699],{"x":165,"y":166,"fill":167,"style":168},"Peak RSS (GB) after each cumulative change",[68,701],{"x1":411,"y1":173,"x2":174,"y2":173,"stroke":175,"style":176},[68,703],{"x1":411,"y1":187,"x2":174,"y2":187,"stroke":195,"style":704},"stroke-width:1.5px;stroke-dasharray:6 4",[163,706,708],{"x":199,"y":200,"fill":201,"style":707},"font-size:11px;font-weight:700;text-anchor:end","4 GB limit",[151,710],{"x":711,"y":191,"width":711,"height":712,"fill":361,"opacity":362,"stroke":195,"style":363},"90","156",[163,714,717],{"x":715,"y":224,"fill":167,"style":716},"135","font-weight:700;text-anchor:middle","7.8",[151,719],{"x":720,"y":721,"width":711,"height":722,"fill":361,"opacity":723,"stroke":195,"style":363},"215","76","134","0.22",[163,725,727],{"x":155,"y":726,"fill":167,"style":716},"68","6.7",[151,729],{"x":730,"y":731,"width":711,"height":732,"fill":373,"opacity":374,"stroke":375,"style":363},"340","126","84",[163,734,736],{"x":382,"y":735,"fill":167,"style":716},"118","4.2",[151,738],{"x":739,"y":740,"width":711,"height":741,"fill":742,"opacity":743,"stroke":744,"style":363},"465","144","66","#8ac926","0.35","#5a8a16",[163,746,749],{"x":747,"y":748,"fill":167,"style":716},"510","138","3.3",[151,751],{"x":752,"y":753,"width":711,"height":182,"fill":742,"opacity":754,"stroke":744,"style":363},"590","148","0.45",[163,756,760],{"x":757,"y":758,"fill":759,"style":716},"635","142","#3f6410","3.1",[163,762,763],{"x":715,"y":229,"fill":175,"style":397},"baseline",[163,765,766],{"x":155,"y":229,"fill":175,"style":397},"MEMORYLIMIT",[163,768,769],{"x":382,"y":229,"fill":175,"style":397},"images",[163,771,772],{"x":747,"y":229,"fill":175,"style":397},"data adapter",[163,774,775],{"x":757,"y":229,"fill":175,"style":397},"kinds + JSON",[236,777,778],{},"The image change mattered most; together the five changes left 900 MB of headroom under a 4 GB container.",[14,780,781],{},"The cold-cache build is slower than before because processed images are written to a cache directory that is then persisted; the first build pays for it once. Every subsequent build with the cache restored was 43 seconds faster than the original.",[32,783,785],{"id":784},"template-patterns-that-inflate-memory","Template Patterns That Inflate Memory",[14,787,788,789,792,793,796,797,800,801,804,805,808,809,811,812,815],{},"Some memory comes from templates rather than content. Three patterns showed up on this site. A related-pages partial called ",[18,790,791],{},"site.RegularPages.Related"," with a broad index on every page, building a large intermediate slice 30,000 times; restricting the indices to ",[18,794,795],{},"tags"," and ",[18,798,799],{},"section"," and capping results at five cut its allocation sharply. A \"recent updates\" footer sorted all regular pages by date on every page; moving it into a ",[18,802,803],{},"partialCached"," call made it run once. And a shortcode that read an entire JSON file with ",[18,806,807],{},"transform.Unmarshal"," on each use loaded the same 40 MB file hundreds of times; reading it once through ",[18,810,478],{},", which Hugo caches, fixed it. ",[18,813,814],{},"--templateMetrics"," shows these as templates with high cumulative time, and they are usually the same templates that dominate memory.",[32,817,819],{"id":818},"watching-the-trend","Watching the Trend",[14,821,822,823,30],{},"Memory grows with content, so a fix today is not permanent. Record peak RSS on every main-branch build next to build time, and alert when it crosses 70% of the smallest environment the site must build in — the hosted build container, not the CI runner. On this site the growth rate after the fixes was about 90 MB per 1,000 pages, which gives roughly 9,000 pages of headroom before the next intervention; that number is now in the quarterly planning notes rather than discovered by a failed deploy. The same monitoring pattern is described in ",[26,824,826],{"href":825},"\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",[32,828,830],{"id":829},"pitfalls-rollback","Pitfalls & Rollback",[37,832,833,839,845,851,857],{},[40,834,835,838],{},[436,836,837],{},"Measuring only wall time."," Memory problems appear as sudden failures, not gradual slowdowns. Record peak RSS.",[40,840,841,844],{},[436,842,843],{},"Upgrading the runner and stopping there."," The problem returns as content grows; reduce usage too.",[40,846,847,850],{},[436,848,849],{},"Disabling page kinds readers use."," Check analytics before removing taxonomies or outputs.",[40,852,853,856],{},[436,854,855],{},"Forgetting the hosted build."," A site that builds in CI but deploys via the host's own builder must fit the host's limits.",[40,858,859,862],{},[436,860,861],{},"Rollback:"," each change is a config line, a CI environment variable or a template change; revert individually and re-measure.",[32,864,866],{"id":865},"conclusion","Conclusion",[14,868,869,870,872],{},"Hugo's memory usage grows with the site, and the first sign is usually a build that fails outright. Measuring peak RSS, attributing it by removing one factor at a time, and then capping caches, persisting and standardising image processing, moving giant data files out of ",[18,871,315],{},", and dropping unused page kinds took a 30,000-page site from 7.8 GB to 3.1 GB and made warm builds 40% faster in the process.",[32,874,876],{"id":875},"faq","FAQ",[878,879,881],"h3",{"id":880},"why-does-hugo-use-so-much-memory-on-large-sites","Why does Hugo use so much memory on large sites?",[14,883,884],{},"Hugo holds the whole site in memory while building — every page's content, rendered output and metadata — so memory grows with page count and content size. Image processing, large data files and templates that build big slices on every page add to the peak.",[878,886,888],{"id":887},"how-do-i-see-hugos-peak-memory-usage","How do I see Hugo's peak memory usage?",[14,890,891],{},"Wrap the build with \u002Fusr\u002Fbin\u002Ftime -v and read the maximum resident set size, or run hugo with --printMemoryUsage to log memory periodically. Record it in CI alongside build time so growth is visible.",[878,893,895],{"id":894},"does-hugo_memorylimit-help","Does HUGO_MEMORYLIMIT help?",[14,897,898],{},"It sets the memory Hugo aims to stay within for its caches, in gigabytes, and Hugo evicts cached items more aggressively as it approaches the limit. It lowers peak usage at some cost in build time, and is the first setting to try on constrained runners.",[878,900,902],{"id":901},"should-i-just-use-a-bigger-runner","Should I just use a bigger runner?",[14,904,905],{},"It is a valid short-term fix, but memory grows with content, so the problem returns. Reducing peak usage first keeps builds on standard runners and makes the growth rate visible.",[32,907,909],{"id":908},"related","Related",[37,911,912,920,927,932,939],{},[40,913,914,439,917,919],{},[436,915,916],{},"Parent:",[26,918,29],{"href":28}," — build performance on large Hugo sites.",[40,921,922,926],{},[26,923,925],{"href":924},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-partialcached-for-faster-builds\u002F","Hugo partialCached for Faster Builds"," — the time side of template work.",[40,928,929,931],{},[26,930,461],{"href":460}," — persisting the resource cache.",[40,933,934,938],{},[26,935,937],{"href":936},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Foptimizing-webp-images-in-hugo-without-plugins\u002F","Optimizing WebP Images in Hugo Without Plugins"," — standardising image variants.",[40,940,941,945],{},[26,942,944],{"href":943},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fsearch-index-size-budgets-for-large-docs\u002F","Search Index Size Budgets for Large Docs"," — moving search indexing out of the build.",[947,948,949],"style",{},"html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .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 .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}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 .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}",{"title":62,"searchDepth":97,"depth":97,"links":951},[952,953,954,955,956,957,958,959,960,961,967],{"id":34,"depth":97,"text":35},{"id":51,"depth":97,"text":52},{"id":244,"depth":97,"text":245},{"id":431,"depth":97,"text":432},{"id":599,"depth":97,"text":600},{"id":784,"depth":97,"text":785},{"id":818,"depth":97,"text":819},{"id":829,"depth":97,"text":830},{"id":865,"depth":97,"text":866},{"id":875,"depth":97,"text":876,"children":962},[963,964,965,966],{"id":880,"depth":111,"text":881},{"id":887,"depth":111,"text":888},{"id":894,"depth":111,"text":895},{"id":901,"depth":111,"text":902},{"id":908,"depth":97,"text":909},[969,972,975,976],{"name":970,"item":971},"Home","\u002F",{"name":973,"item":974},"Choosing the Right Static Site Generator for Production","\u002Fchoosing-the-right-static-site-generator-for-production\u002F",{"name":29,"item":28},{"name":5,"item":977},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners\u002F","2026-09-18","Why large Hugo builds run out of memory in CI, how to measure peak usage, and the settings, template changes and image strategies that cut it by more than half.","md",[982,983,984,985],{"q":881,"a":884},{"q":888,"a":891},{"q":895,"a":898},{"q":902,"a":905},{},true,"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners",{"title":5,"description":979},"choosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners\u002Findex","article","hO3wfi-e-9Uc_BqcoswiT1SjNwjBTfsRebRd4Ih3SeM",[994,997,1000,1003,1006,1009,1012,1015,1018,1021,1024,1027,1030,1033,1036,1038,1040,1043,1044,1047,1049,1052,1055,1058,1061,1064,1067,1070,1073,1076,1079,1082,1085,1088,1091,1094,1097,1100,1103,1106,1109,1112,1115,1118,1120,1123,1126,1128,1131,1134,1137,1140,1143,1146,1149,1152,1155,1158,1161,1164,1167,1170,1173,1176,1179,1182,1185,1188,1191,1194,1197,1200,1203,1206,1209,1212,1215,1218,1220,1223,1226,1229,1232,1235,1238,1241,1244,1247,1250,1253,1256,1259,1262,1265,1268,1271,1274,1277,1280,1283,1286,1289,1292,1295,1298,1301,1304,1307,1310,1313,1316,1319,1322,1325,1328,1331,1334,1337,1340,1343,1346,1349,1352,1355,1358,1361,1364,1367,1370,1373,1376,1379,1381,1384,1387,1390,1393,1396,1399,1402,1405,1408,1411,1414,1417,1420,1423,1426,1429,1432,1435,1438,1441,1444,1447,1450,1453,1456,1459,1462,1465,1468,1471,1474,1477,1480,1483,1486,1489,1492,1495,1498,1501,1504,1507,1510,1513,1516,1519,1522,1525,1528,1531],{"path":995,"title":996},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fastro-vs-eleventy-build-times-at-10000-pages","Astro vs Eleventy Build Times at 10,000 Pages",{"path":998,"title":999},"\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":1001,"title":1002},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fcontent-collections-vs-eleventy-data-cascade","Content Collections vs the Eleventy Data Cascade",{"path":1004,"title":1005},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1007,"title":1008},"\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":1010,"title":1011},"\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":1013,"title":1014},"\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":1016,"title":1017},"\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":1019,"title":1020},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1022,"title":1023},"\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":1025,"title":1026},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1028,"title":1029},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1031,"title":1032},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1034,"title":1035},"\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":1037,"title":925},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-partialcached-for-faster-builds",{"path":1039,"title":29},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories",{"path":1041,"title":1042},"\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":988,"title":5},{"path":1045,"title":1046},"\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":1048,"title":973},"\u002Fchoosing-the-right-static-site-generator-for-production",{"path":1050,"title":1051},"\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":1053,"title":1054},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1056,"title":1057},"\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":1059,"title":1060},"\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":1062,"title":1063},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1065,"title":1066},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1068,"title":1069},"\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":1071,"title":1072},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1074,"title":1075},"\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":1077,"title":1078},"\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":1080,"title":1081},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1083,"title":1084},"\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":1086,"title":1087},"\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":1089,"title":1090},"\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":1092,"title":1093},"\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":1095,"title":1096},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1098,"title":1099},"\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":1101,"title":1102},"\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":1104,"title":1105},"\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":1107,"title":1108},"\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":1110,"title":1111},"\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":1113,"title":1114},"\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":1116,"title":1117},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1119,"title":499},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind",{"path":1121,"title":1122},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1124,"title":1125},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1127,"title":944},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fsearch-index-size-budgets-for-large-docs",{"path":1129,"title":1130},"\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":1132,"title":1133},"\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":1135,"title":1136},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1138,"title":1139},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1141,"title":1142},"\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":1144,"title":1145},"\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":1147,"title":1148},"\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":1150,"title":1151},"\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":1153,"title":1154},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1156,"title":1157},"\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":1159,"title":1160},"\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":1162,"title":1163},"\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":1165,"title":1166},"\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":1168,"title":1169},"\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":1171,"title":1172},"\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":1174,"title":1175},"\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":1177,"title":1178},"\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":1180,"title":1181},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1183,"title":1184},"\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":1186,"title":1187},"\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":1189,"title":1190},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1192,"title":1193},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1195,"title":1196},"\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":1198,"title":1199},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1201,"title":1202},"\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":1204,"title":1205},"\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":1207,"title":1208},"\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":1210,"title":1211},"\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":1213,"title":1214},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1216,"title":1217},"\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":1219,"title":937},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Foptimizing-webp-images-in-hugo-without-plugins",{"path":1221,"title":1222},"\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":1224,"title":1225},"\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":1227,"title":1228},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1230,"title":1231},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1233,"title":1234},"\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":1236,"title":1237},"\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":1239,"title":1240},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1242,"title":1243},"\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":1245,"title":1246},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1248,"title":1249},"\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":1251,"title":1252},"\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":1254,"title":1255},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1257,"title":1258},"\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":1260,"title":1261},"\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":1263,"title":1264},"\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":1266,"title":1267},"\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":1269,"title":1270},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1272,"title":1273},"\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":1275,"title":1276},"\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":1278,"title":1279},"\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":1281,"title":1282},"\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":1284,"title":1285},"\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":1287,"title":1288},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1290,"title":1291},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1293,"title":1294},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1296,"title":1297},"\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":1299,"title":1300},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1302,"title":1303},"\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":1305,"title":1306},"\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":1308,"title":1309},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1311,"title":1312},"\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":1314,"title":1315},"\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":1317,"title":1318},"\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":1320,"title":1321},"\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":1323,"title":1324},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1326,"title":1327},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1329,"title":1330},"\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":1332,"title":1333},"\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":1335,"title":1336},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1338,"title":1339},"\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":1341,"title":1342},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1344,"title":1345},"\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":1347,"title":1348},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1350,"title":1351},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1353,"title":1354},"\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":1356,"title":1357},"\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":1359,"title":1360},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1362,"title":1363},"\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":1365,"title":1366},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1368,"title":1369},"\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":1371,"title":1372},"\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":1374,"title":1375},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1377,"title":1378},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1380,"title":461},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fcaching-hugo-builds-in-github-actions",{"path":1382,"title":1383},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1385,"title":1386},"\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":1388,"title":1389},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1391,"title":1392},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fmeasuring-build-time-regressions-in-ci","Measuring Build-Time Regressions in CI",{"path":1394,"title":1395},"\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":1397,"title":1398},"\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":1400,"title":1401},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1403,"title":1404},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1406,"title":1407},"\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":1409,"title":1410},"\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":1412,"title":1413},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1415,"title":1416},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1418,"title":1419},"\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":1421,"title":1422},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1424,"title":1425},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1427,"title":1428},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1430,"title":1431},"\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":1433,"title":1434},"\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":1436,"title":1437},"\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":1439,"title":1440},"\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":1442,"title":1443},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1445,"title":1446},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":1448,"title":1449},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1451,"title":1452},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1454,"title":1455},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1457,"title":1458},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1460,"title":1461},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":1463,"title":1464},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1466,"title":1467},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1469,"title":1470},"\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":1472,"title":1473},"\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":1475,"title":1476},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1478,"title":1479},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1481,"title":1482},"\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":1484,"title":1485},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1487,"title":1488},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1490,"title":1491},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1493,"title":1494},"\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":1496,"title":1497},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1499,"title":1500},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1502,"title":1503},"\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":1505,"title":1506},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1508,"title":1509},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1511,"title":1512},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1514,"title":1515},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1517,"title":1518},"\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":1520,"title":1521},"\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":1523,"title":1524},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1526,"title":1527},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1529,"title":1530},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1532,"title":1533},"\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",1789722847995]