[{"data":1,"prerenderedAt":1503},["ShallowReactive",2],{"page:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-partialcached-for-faster-builds":3,"all-docs-nav":960},{"id":4,"title":5,"body":6,"breadcrumb":935,"dateModified":945,"datePublished":945,"description":946,"extension":947,"faq":948,"meta":953,"navigation":954,"path":955,"seo":956,"slug":12,"stem":957,"type":958,"__hash__":959},"content\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-partialcached-for-faster-builds\u002Findex.md","Hugo partialCached for Faster Builds",{"type":7,"value":8,"toc":916},"minimark",[9,13,22,36,41,62,66,113,121,128,259,263,266,289,295,299,307,316,322,329,425,429,435,501,515,519,526,595,598,686,690,738,742,768,772,828,832,838,842,847,850,854,857,861,864,868,871,875,912],[10,11,5],"h1",{"id":12},"hugo-partialcached-for-faster-builds",[14,15,16,17,21],"p",{},"Hugo is fast, but a large site can still spend most of its build rendering the same thing thousands of times. A site header with a navigation menu, a footer with a sitemap of sections, a sidebar listing every page in a section — each is a partial called from the base template on every page, and on a 12,000-page site each call walks menus or page collections again. ",[18,19,20],"code",{},"partialCached"," renders a partial once per build (or once per variant you specify) and reuses the output, which on the site measured here removed more than half the build time.",[14,23,24,25,30,31,35],{},"The catch is correctness. A cached partial whose output depends on the current page, but whose cache key does not include it, reuses the first page's output everywhere. This guide finds the expensive partials with template metrics, caches them with the right keys, and shows how to verify nothing went stale. 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"," and follows the profiling approach in ",[26,32,34],{"href":33},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fprofiling-hugo-templates-with-template-metrics\u002F","Profiling Hugo Templates with Template Metrics",".",[37,38,40],"h2",{"id":39},"prerequisites","Prerequisites",[42,43,44,48,51],"ul",{},[45,46,47],"li",{},"Hugo extended 0.120 or newer.",[45,49,50],{},"A site large enough for template time to matter — a few thousand pages.",[45,52,53,54,57,58,61],{},"A way to diff two builds' output (",[18,55,56],{},"diff -r"," or ",[18,59,60],{},"git diff --no-index",").",[37,63,65],{"id":64},"step-1-measure-where-time-goes","Step 1: Measure Where Time Goes",[67,68,73],"pre",{"className":69,"code":70,"language":71,"meta":72,"style":72},"language-bash shiki shiki-themes github-light github-dark","hugo --gc --templateMetrics --templateMetricsHints > metrics.txt\nhead -20 metrics.txt\n","bash","",[18,74,75,102],{"__ignoreMap":72},[76,77,80,84,88,91,94,98],"span",{"class":78,"line":79},"line",1,[76,81,83],{"class":82},"sScJk","hugo",[76,85,87],{"class":86},"sj4cs"," --gc",[76,89,90],{"class":86}," --templateMetrics",[76,92,93],{"class":86}," --templateMetricsHints",[76,95,97],{"class":96},"szBVR"," >",[76,99,101],{"class":100},"sZZnC"," metrics.txt\n",[76,103,105,108,111],{"class":78,"line":104},2,[76,106,107],{"class":82},"head",[76,109,110],{"class":86}," -20",[76,112,101],{"class":100},[67,114,119],{"className":115,"code":117,"language":118,"meta":72},[116],"language-text","     cumulative       average       maximum      cache  percent  cached  total\n       duration      duration      duration  potential   cached   count  count  template\n     ----------      --------      --------  ---------  -------  ------  -----  --------\n    18.412s        1.534ms      21.8ms          100        0       0  12004  partials\u002Ffooter-sitemap.html\n    11.907s          992µs      14.1ms          100        0       0  12004  partials\u002Fheader-nav.html\n     6.221s          519µs       9.3ms            0        0       0  12004  partials\u002Fsidebar.html\n     4.884s          407µs       7.6ms          100        0       0  12004  partials\u002Fhead\u002Fschema-org.html\n     3.106s          259µs       4.4ms            0        0       0  12004  _default\u002Fsingle.html\n","text",[18,120,117],{"__ignoreMap":72},[14,122,123,124,127],{},"The ",[18,125,126],{},"cache potential"," column is Hugo's estimate, from observing actual outputs, of how often the partial produced identical output. 100 means every call returned the same HTML — a perfect candidate. 0 means output varied every time. Here the footer sitemap and header nav were rendered 12,004 times each while producing identical HTML every time: 30 seconds of pure repetition.",[129,130,131,255],"figure",{},[132,133,140,141,140,145,140,149,140,156],"svg",{"viewBox":134,"role":135,"ariaLabelledBy":136,"xmlns":139},"0 0 760 290","img",[137,138],"hpc-met-title","hpc-met-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[142,143,144],"title",{"id":137},"Cumulative template time by partial",[146,147,148],"desc",{"id":138},"Horizontal bars of cumulative render time. Footer sitemap 18.4 seconds with cache potential 100. Header navigation 11.9 seconds, potential 100. Sidebar 6.2 seconds, potential 0. Schema.org head partial 4.9 seconds, potential 100. Single page template 3.1 seconds, potential 0. Three partials with full potential account for 35 seconds.",[150,151],"rect",{"x":152,"y":152,"width":153,"height":154,"fill":155},"0","760","290","#ffffff",[157,158,160,161,160,168,160,175,160,180,160,190,160,196,160,200,160,204,160,209,160,213,160,219,160,224,160,228,160,232,160,237,160,241,160,244,160,249,140],"g",{"style":159},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[118,162,167],{"x":163,"y":164,"fill":165,"style":166},"380","28","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Template time on a 12,000-page build (seconds)",[78,169],{"x1":170,"y1":171,"x2":170,"y2":172,"stroke":173,"style":174},"230","46","246","#d9e2ef","stroke-width:1.5px",[118,176,179],{"x":177,"y":178,"fill":165},"40","74","footer-sitemap",[150,181],{"x":170,"y":182,"width":183,"height":184,"rx":185,"fill":186,"opacity":187,"stroke":188,"style":189},"58","442","24","4","#ff595e","0.28","#d83b41","stroke-width:1px",[118,191,195],{"x":192,"y":193,"fill":165,"style":194},"680","75","font-weight:700","18.4 · cacheable",[118,197,199],{"x":177,"y":198,"fill":165},"112","header-nav",[150,201],{"x":170,"y":202,"width":203,"height":184,"rx":185,"fill":186,"opacity":187,"stroke":188,"style":189},"96","286",[118,205,208],{"x":206,"y":207,"fill":165,"style":194},"524","113","11.9 · cacheable",[118,210,212],{"x":177,"y":211,"fill":165},"150","sidebar",[150,214],{"x":170,"y":215,"width":216,"height":184,"rx":185,"fill":217,"opacity":218,"stroke":217,"style":189},"134","149","#1982c4","0.22",[118,220,223],{"x":221,"y":222,"fill":165,"style":194},"387","151","6.2 · varies",[118,225,227],{"x":177,"y":226,"fill":165},"188","head\u002Fschema-org",[150,229],{"x":170,"y":230,"width":231,"height":184,"rx":185,"fill":186,"opacity":187,"stroke":188,"style":189},"172","117",[118,233,236],{"x":234,"y":235,"fill":165,"style":194},"355","189","4.9 · cacheable",[118,238,240],{"x":177,"y":239,"fill":165},"226","_default\u002Fsingle",[150,242],{"x":170,"y":243,"width":178,"height":184,"rx":185,"fill":217,"opacity":218,"stroke":217,"style":189},"210",[118,245,248],{"x":246,"y":247,"fill":165,"style":194},"312","227","3.1 · varies",[118,250,254],{"x":163,"y":251,"fill":252,"style":253},"272","#556071","font-size:11px;text-anchor:middle","hugo --templateMetrics --templateMetricsHints; red = cache potential 100",[256,257,258],"figcaption",{},"Three partials that produced identical output on every page accounted for 35 seconds of a 58-second build.",[37,260,262],{"id":261},"step-2-cache-the-invariant-partials","Step 2: Cache the Invariant Partials",[14,264,265],{},"Partials whose output never varies need no key:",[67,267,271],{"className":268,"code":269,"language":270,"meta":72,"style":72},"language-go-html-template shiki shiki-themes github-light github-dark","{{\u002F* layouts\u002F_default\u002Fbaseof.html *\u002F}}\n{{ partialCached \"footer-sitemap.html\" . }}\n{{ partialCached \"head\u002Fschema-org.html\" . }}\n","go-html-template",[18,272,273,278,283],{"__ignoreMap":72},[76,274,275],{"class":78,"line":79},[76,276,277],{},"{{\u002F* layouts\u002F_default\u002Fbaseof.html *\u002F}}\n",[76,279,280],{"class":78,"line":104},[76,281,282],{},"{{ partialCached \"footer-sitemap.html\" . }}\n",[76,284,286],{"class":78,"line":285},3,[76,287,288],{},"{{ partialCached \"head\u002Fschema-org.html\" . }}\n",[14,290,291,292,294],{},"The context (",[18,293,35],{},") is still passed so the partial can read site data, but only the first call's context is used. That is exactly why the partial must not depend on the page.",[37,296,298],{"id":297},"step-3-cache-partials-that-vary-by-a-few-values","Step 3: Cache Partials That Vary by a Few Values",[14,300,301,302,306],{},"The header navigation ",[303,304,305],"em",{},"looked"," invariant in metrics because the active-menu highlight was done with client-side JavaScript. After moving the highlight into the template (so it works without JavaScript), its output varied by section. That is still cacheable — once per section rather than once per page — by passing the section as a variant key:",[67,308,310],{"className":268,"code":309,"language":270,"meta":72,"style":72},"{{ partialCached \"header-nav.html\" . .Section }}\n",[18,311,312],{"__ignoreMap":72},[76,313,314],{"class":78,"line":79},[76,315,309],{},[14,317,318,319,35],{},"With 14 top-level sections, the partial now renders 14 times instead of 12,004. Variant keys can be any values that determine the output: section, language, a version for versioned docs. Multiple keys are allowed: ",[18,320,321],{},"{{ partialCached \"nav.html\" . .Section .Lang }}",[14,323,324,325,328],{},"The sidebar, with cache potential 0, lists the pages in the current subsection with the current page highlighted. Caching it per subsection plus moving the highlight out of the cached part (render the list cached, then mark the active item with a tiny inline script, or with CSS using a per-page ",[18,326,327],{},"data-path"," attribute) reduced it from 6.2 s to 1.4 s, but that is a trade-off worth measuring rather than assuming.",[129,330,331,422],{},[132,332,140,337,140,340,140,343,140,346],{"viewBox":333,"role":135,"ariaLabelledBy":334,"xmlns":139},"0 0 760 270",[335,336],"hpc-key-title","hpc-key-desc",[142,338,339],{"id":335},"Choosing the variant key",[146,341,342],{"id":336},"Three rows. A footer with no page-dependent output uses no key and renders once. A header with an active section uses the section as key and renders 14 times. A sidebar with a per-page highlight either stays uncached at 12,004 renders or is split: the list is cached per subsection with 212 renders and the highlight is applied separately per page.",[150,344],{"x":152,"y":152,"width":153,"height":345,"fill":155},"270",[157,347,160,348,160,351,160,357,160,361,160,365,160,370,160,373,160,377,160,380,160,384,160,387,160,390,160,393,160,396,160,399,160,402,160,405,160,409,160,412,160,415,160,419,140],{"style":159},[118,349,350],{"x":163,"y":164,"fill":165,"style":166},"The key must contain everything the output depends on",[118,352,356],{"x":353,"y":354,"fill":165,"style":355},"250","62","font-weight:700;text-anchor:middle","depends on",[118,358,360],{"x":359,"y":354,"fill":165,"style":355},"440","key",[118,362,364],{"x":363,"y":354,"fill":165,"style":355},"630","renders per build",[78,366],{"x1":367,"y1":368,"x2":369,"y2":368,"stroke":173,"style":174},"30","72","730",[118,371,179],{"x":177,"y":372,"fill":165,"style":194},"104",[118,374,376],{"x":353,"y":372,"fill":165,"style":375},"text-anchor:middle","site only",[118,378,379],{"x":359,"y":372,"fill":165,"style":375},"(none)",[118,381,383],{"x":363,"y":372,"fill":382,"style":355},"#3f6410","1",[118,385,199],{"x":177,"y":386,"fill":165,"style":194},"146",[118,388,389],{"x":353,"y":386,"fill":165,"style":375},"active section",[118,391,392],{"x":359,"y":386,"fill":165,"style":375},".Section",[118,394,395],{"x":363,"y":386,"fill":382,"style":355},"14",[118,397,398],{"x":177,"y":226,"fill":165,"style":194},"sidebar list",[118,400,401],{"x":353,"y":226,"fill":165,"style":375},"subsection",[118,403,404],{"x":359,"y":226,"fill":165,"style":375},".CurrentSection.Path",[118,406,408],{"x":363,"y":226,"fill":407,"style":355},"#8a6d0f","212",[118,410,411],{"x":177,"y":170,"fill":165,"style":194},"sidebar highlight",[118,413,414],{"x":353,"y":170,"fill":165,"style":375},"current page",[118,416,418],{"x":359,"y":170,"fill":417,"style":375},"#b32b30","do not cache",[118,420,421],{"x":363,"y":170,"fill":165,"style":355},"12,004 (tiny)",[256,423,424],{},"Splitting a partial into a cacheable body and a small per-page part is often the real win.",[37,426,428],{"id":427},"step-4-prove-nothing-went-stale","Step 4: Prove Nothing Went Stale",[14,430,431,432,434],{},"The failure mode of ",[18,433,20],{}," is silent: the build succeeds and some pages show another page's content. Diff the output of the uncached and cached builds before merging:",[67,436,438],{"className":69,"code":437,"language":71,"meta":72,"style":72},"git stash && hugo --gc -d \u002Ftmp\u002Fbefore && git stash pop\nhugo --gc -d \u002Ftmp\u002Fafter\ndiff -rq \u002Ftmp\u002Fbefore \u002Ftmp\u002Fafter | head\n",[18,439,440,471,482],{"__ignoreMap":72},[76,441,442,445,448,452,454,456,459,462,464,466,468],{"class":78,"line":79},[76,443,444],{"class":82},"git",[76,446,447],{"class":100}," stash",[76,449,451],{"class":450},"sVt8B"," && ",[76,453,83],{"class":82},[76,455,87],{"class":86},[76,457,458],{"class":86}," -d",[76,460,461],{"class":100}," \u002Ftmp\u002Fbefore",[76,463,451],{"class":450},[76,465,444],{"class":82},[76,467,447],{"class":100},[76,469,470],{"class":100}," pop\n",[76,472,473,475,477,479],{"class":78,"line":104},[76,474,83],{"class":82},[76,476,87],{"class":86},[76,478,458],{"class":86},[76,480,481],{"class":100}," \u002Ftmp\u002Fafter\n",[76,483,484,487,490,492,495,498],{"class":78,"line":285},[76,485,486],{"class":82},"diff",[76,488,489],{"class":86}," -rq",[76,491,461],{"class":100},[76,493,494],{"class":100}," \u002Ftmp\u002Fafter",[76,496,497],{"class":96}," |",[76,499,500],{"class":82}," head\n",[14,502,503,504,507,508,510,511,35],{},"An empty diff (apart from timestamps if your templates emit them) proves the cache keys are complete. The first attempt on this site produced 11,990 differing files: the header had been cached without a key while still containing ",[18,505,506],{},"aria-current"," on the active section. Adding ",[18,509,392],{}," as the key brought the diff to zero. Keep the diff as a CI check whenever templates change, as part of the build gates in ",[26,512,514],{"href":513},"\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",[37,516,518],{"id":517},"measured-impact","Measured Impact",[14,520,521,522,525],{},"The 12,004-page site, ",[18,523,524],{},"hugo --gc --minify"," on a GitHub Actions runner, median of five runs:",[527,528,529,545],"table",{},[530,531,532],"thead",{},[533,534,535,539,542],"tr",{},[536,537,538],"th",{},"Change",[536,540,541],{},"Build time",[536,543,544],{},"Template time for changed partials",[546,547,548,560,571,584],"tbody",{},[533,549,550,554,557],{},[551,552,553],"td",{},"Baseline",[551,555,556],{},"58.1 s",[551,558,559],{},"40.4 s",[533,561,562,565,568],{},[551,563,564],{},"Footer + schema cached (no key)",[551,566,567],{},"35.3 s",[551,569,570],{},"18.0 s",[533,572,573,578,581],{},[551,574,575,576],{},"+ header cached by ",[18,577,392],{},[551,579,580],{},"23.9 s",[551,582,583],{},"6.6 s",[533,585,586,589,592],{},[551,587,588],{},"+ sidebar split: list cached by subsection",[551,590,591],{},"19.1 s",[551,593,594],{},"1.8 s",[14,596,597],{},"A 67% reduction in build time from four template lines and one split partial, with byte-identical output.",[129,599,600,683],{},[132,601,140,606,140,609,140,612,140,614],{"viewBox":602,"role":135,"ariaLabelledBy":603,"xmlns":139},"0 0 760 250",[604,605],"hpc-step-title","hpc-step-desc",[142,607,608],{"id":604},"Build time after each caching step",[146,610,611],{"id":605},"Four bars of total build time: baseline 58.1 seconds, after caching footer and schema 35.3 seconds, after caching the header by section 23.9 seconds, and after splitting the sidebar 19.1 seconds.",[150,613],{"x":152,"y":152,"width":153,"height":353,"fill":155},[157,615,160,616,160,619,160,624,160,629,160,633,160,640,160,644,160,649,160,654,160,662,160,666,160,670,160,673,160,676,160,679,140],{"style":159},[118,617,618],{"x":163,"y":164,"fill":165,"style":166},"Build seconds, cumulative changes",[78,620],{"x1":621,"y1":622,"x2":623,"y2":622,"stroke":252,"style":174},"60","200","720",[150,625],{"x":626,"y":627,"width":626,"height":628,"fill":186,"opacity":187,"stroke":188,"style":189},"100","55","145",[118,630,632],{"x":211,"y":631,"fill":165,"style":355},"47","58.1",[150,634],{"x":635,"y":198,"width":626,"height":636,"fill":637,"opacity":638,"stroke":639,"style":189},"260","88","#ffca3a","0.38","#a97b00",[118,641,643],{"x":642,"y":372,"fill":165,"style":355},"310","35.3",[150,645],{"x":646,"y":647,"width":626,"height":621,"fill":217,"opacity":648,"stroke":217,"style":189},"420","140","0.25",[118,650,653],{"x":651,"y":652,"fill":165,"style":355},"470","132","23.9",[150,655],{"x":656,"y":657,"width":626,"height":658,"fill":659,"opacity":660,"stroke":661,"style":189},"580","152","48","#8ac926","0.4","#5a8a16",[118,663,665],{"x":363,"y":664,"fill":382,"style":355},"144","19.1",[118,667,669],{"x":211,"y":668,"fill":252,"style":253},"218","baseline",[118,671,672],{"x":642,"y":668,"fill":252,"style":253},"footer + schema",[118,674,675],{"x":651,"y":668,"fill":252,"style":253},"+ header by section",[118,677,678],{"x":363,"y":668,"fill":252,"style":253},"+ sidebar split",[118,680,682],{"x":163,"y":681,"fill":252,"style":253},"242","hugo --gc --minify, 12,004 pages, median of 5 on GitHub Actions ubuntu-latest",[256,684,685],{},"The first two lines of change bought the most; the sidebar split was worth doing but required the most care.",[37,687,689],{"id":688},"beyond-partialcached","Beyond partialCached",[14,691,692,693,697,698,701,702,705,706,709,710,713,714,717,718,721,722,726,727,713,730,733,734,737],{},"Template caching removes repeated rendering. Three other kinds of repetition often remain in large Hugo builds and respond to different tools. ",[694,695,696],"strong",{},"Repeated page queries",": a partial that calls ",[18,699,700],{},"where site.RegularPages \"Section\" \"guides\""," on every page walks all pages each time; storing the result once in ",[18,703,704],{},"site.Store"," from a partial called early in the base template, or computing it in a cached partial that returns a slice with ",[18,707,708],{},"return",", avoids the walk. ",[694,711,712],{},"Repeated resource processing",": ",[18,715,716],{},"resources.Get | fingerprint | minify"," on the same stylesheet in every page is cached by Hugo already, but image processing with changing parameters per page is not — standardise sizes so the resources cache in ",[18,719,720],{},"resources\u002F_gen"," can do its job, as described in ",[26,723,725],{"href":724},"\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",". ",[694,728,729],{},"Repeated remote data",[18,731,732],{},"resources.GetRemote"," calls cache to disk and can persist across builds when the cache directory is restored in CI. Template metrics show the first; ",[18,735,736],{},"--logLevel info"," output and build timings show the other two.",[37,739,741],{"id":740},"multilingual-and-multi-output-sites","Multilingual and Multi-Output Sites",[14,743,744,745,748,749,752,753,756,757,760,761,764,765,767],{},"Two Hugo features change what a correct key looks like. On a ",[694,746,747],{},"multilingual"," site, nearly every navigation partial differs by language — labels, links and order all change — so ",[18,750,751],{},".Lang"," (or ",[18,754,755],{},"site.Language.Lang",") belongs in the key of any cached partial that renders text or URLs. Forgetting it produces English navigation on German pages, which the output diff catches immediately because thousands of files change. On sites with ",[694,758,759],{},"multiple output formats"," (HTML plus AMP, or HTML plus a JSON search output), a partial called from both formats may need the output format in its key too; ",[18,762,763],{},".OutputFormats.Get"," or a separate partial per format keeps them apart. On this site's German and Japanese variants, adding ",[18,766,751],{}," to three keys raised render counts from 14 to 42 for the header — still a rounding error against 36,000 page renders across all languages.",[37,769,771],{"id":770},"pitfalls-rollback","Pitfalls & Rollback",[42,773,774,780,790,799,815],{},[45,775,776,779],{},[694,777,778],{},"Caching page-dependent output without a key."," The most common bug; always diff before and after.",[45,781,782,785,786,789],{},[694,783,784],{},"Keys that are too fine."," Passing ",[18,787,788],{},".RelPermalink"," as a key caches per page, which saves nothing.",[45,791,792,798],{},[694,793,794,795,797],{},"Relying on ",[18,796,126],{}," alone."," It reflects the pages Hugo rendered during that run; a template change can alter it. Re-run metrics after edits.",[45,800,801,807,808,57,811,814],{},[694,802,803,804,806],{},"Using ",[18,805,20],{}," for side effects."," Partials that call ",[18,809,810],{},".Scratch.Set",[18,812,813],{},".Store.Set"," on the page run only once when cached; move side effects out.",[45,816,817,820,821,823,824,827],{},[694,818,819],{},"Rollback:"," replacing ",[18,822,20],{}," with ",[18,825,826],{},"partial"," restores per-page rendering exactly; the change is local to each call.",[37,829,831],{"id":830},"conclusion","Conclusion",[14,833,834,835,837],{},"On large Hugo sites, a handful of partials rendered on every page often dominate the build. Template metrics with hints identify them, ",[18,836,20],{}," with the right variant keys renders them once per distinct output, and a before\u002Fafter output diff proves correctness. On a 12,000-page site that took the build from 58 to 19 seconds without changing a single byte of output.",[37,839,841],{"id":840},"faq","FAQ",[843,844,846],"h3",{"id":845},"what-does-partialcached-do","What does partialCached do?",[14,848,849],{},"It renders a partial once per unique combination of the partial name and any variant keys you pass, and reuses the output for every later call in the same build. A partial called on 12,000 pages with no variant renders once instead of 12,000 times.",[843,851,853],{"id":852},"when-is-partialcached-unsafe","When is partialCached unsafe?",[14,855,856],{},"When the partial's output depends on something that differs between calls but is not part of the cache key, such as the current page. The cached output from the first page is then reused on every page, producing wrong active states, titles or links.",[843,858,860],{"id":859},"how-do-i-find-which-partials-to-cache","How do I find which partials to cache?",[14,862,863],{},"Run hugo --templateMetrics --templateMetricsHints. It lists every template with its cumulative time and call count, and the hints column estimates how cacheable each partial is based on whether its output varied between calls.",[843,865,867],{"id":866},"does-partialcached-persist-between-builds","Does partialCached persist between builds?",[14,869,870],{},"No. The cache lives for a single build. For work that should persist across builds, such as processed images or remote data, Hugo's resources cache and file cache are the right tools.",[37,872,874],{"id":873},"related","Related",[42,876,877,886,891,898,905],{},[45,878,879,882,883,885],{},[694,880,881],{},"Parent:"," ",[26,884,29],{"href":28}," — the wider build-speed picture.",[45,887,888,890],{},[26,889,34],{"href":33}," — reading the metrics in depth.",[45,892,893,897],{},[26,894,896],{"href":895},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fspeeding-up-hugo-builds-with-render-hooks-and-caching\u002F","Speeding Up Hugo Builds with Render Hooks and Caching"," — the other caching layers.",[45,899,900,904],{},[26,901,903],{"href":902},"\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 memory side of large builds.",[45,906,907,911],{},[26,908,910],{"href":909},"\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"," — persisting caches between builds.",[913,914,915],"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 .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}",{"title":72,"searchDepth":104,"depth":104,"links":917},[918,919,920,921,922,923,924,925,926,927,928,934],{"id":39,"depth":104,"text":40},{"id":64,"depth":104,"text":65},{"id":261,"depth":104,"text":262},{"id":297,"depth":104,"text":298},{"id":427,"depth":104,"text":428},{"id":517,"depth":104,"text":518},{"id":688,"depth":104,"text":689},{"id":740,"depth":104,"text":741},{"id":770,"depth":104,"text":771},{"id":830,"depth":104,"text":831},{"id":840,"depth":104,"text":841,"children":929},[930,931,932,933],{"id":845,"depth":285,"text":846},{"id":852,"depth":285,"text":853},{"id":859,"depth":285,"text":860},{"id":866,"depth":285,"text":867},{"id":873,"depth":104,"text":874},[936,939,942,943],{"name":937,"item":938},"Home","\u002F",{"name":940,"item":941},"Choosing the Right Static Site Generator for Production","\u002Fchoosing-the-right-static-site-generator-for-production\u002F",{"name":29,"item":28},{"name":5,"item":944},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-partialcached-for-faster-builds\u002F","2026-09-18","Find the partials that dominate a Hugo build with template metrics, cache them with partialCached and the right variant keys, and avoid stale output.","md",[949,950,951,952],{"q":846,"a":849},{"q":853,"a":856},{"q":860,"a":863},{"q":867,"a":870},{},true,"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-partialcached-for-faster-builds",{"title":5,"description":946},"choosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-partialcached-for-faster-builds\u002Findex","article","WWrBuMztWYsdb-ZsDEDxY6FUy-6H84MLEeqnNn_y4oM",[961,964,967,970,973,976,979,982,985,988,991,994,997,1000,1003,1004,1006,1009,1011,1014,1016,1019,1022,1025,1028,1031,1034,1037,1040,1043,1046,1049,1052,1055,1058,1061,1064,1067,1070,1073,1076,1079,1082,1085,1088,1091,1094,1097,1100,1103,1106,1109,1112,1115,1118,1121,1124,1127,1130,1133,1136,1139,1142,1145,1148,1151,1154,1157,1160,1163,1166,1169,1172,1175,1178,1181,1184,1187,1189,1192,1195,1198,1201,1204,1207,1210,1213,1216,1219,1222,1225,1228,1231,1234,1237,1240,1243,1246,1249,1252,1255,1258,1261,1264,1267,1270,1273,1276,1279,1282,1285,1288,1291,1294,1297,1300,1303,1306,1309,1312,1315,1318,1321,1324,1327,1330,1333,1336,1339,1342,1345,1348,1350,1353,1356,1359,1362,1365,1368,1371,1374,1377,1380,1383,1386,1389,1392,1395,1398,1401,1404,1407,1410,1413,1416,1419,1422,1425,1428,1431,1434,1437,1440,1443,1446,1449,1452,1455,1458,1461,1464,1467,1470,1473,1476,1479,1482,1485,1488,1491,1494,1497,1500],{"path":962,"title":963},"\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":965,"title":966},"\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":968,"title":969},"\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":971,"title":972},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":974,"title":975},"\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":977,"title":978},"\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":980,"title":981},"\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":983,"title":984},"\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":986,"title":987},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":989,"title":990},"\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":992,"title":993},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":995,"title":996},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":998,"title":999},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1001,"title":1002},"\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":955,"title":5},{"path":1005,"title":29},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories",{"path":1007,"title":1008},"\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":1010,"title":903},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners",{"path":1012,"title":1013},"\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":1015,"title":940},"\u002Fchoosing-the-right-static-site-generator-for-production",{"path":1017,"title":1018},"\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":1020,"title":1021},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1023,"title":1024},"\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":1026,"title":1027},"\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":1029,"title":1030},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1032,"title":1033},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1035,"title":1036},"\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":1038,"title":1039},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1041,"title":1042},"\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":1044,"title":1045},"\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":1047,"title":1048},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1050,"title":1051},"\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":1053,"title":1054},"\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":1056,"title":1057},"\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":1059,"title":1060},"\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":1062,"title":1063},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1065,"title":1066},"\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":1068,"title":1069},"\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":1071,"title":1072},"\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":1074,"title":1075},"\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":1077,"title":1078},"\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":1080,"title":1081},"\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":1083,"title":1084},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1086,"title":1087},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1089,"title":1090},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1092,"title":1093},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1095,"title":1096},"\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":1098,"title":1099},"\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":1101,"title":1102},"\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":1104,"title":1105},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1107,"title":1108},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1110,"title":1111},"\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":1113,"title":1114},"\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":1116,"title":1117},"\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":1119,"title":1120},"\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":1122,"title":1123},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1125,"title":1126},"\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":1128,"title":1129},"\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":1131,"title":1132},"\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":1134,"title":1135},"\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":1137,"title":1138},"\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":1140,"title":1141},"\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":1143,"title":1144},"\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":1146,"title":1147},"\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":1149,"title":1150},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1152,"title":1153},"\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":1155,"title":1156},"\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":1158,"title":1159},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1161,"title":1162},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1164,"title":1165},"\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":1167,"title":1168},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1170,"title":1171},"\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":1173,"title":1174},"\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":1176,"title":1177},"\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":1179,"title":1180},"\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":1182,"title":1183},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1185,"title":1186},"\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":1188,"title":725},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Foptimizing-webp-images-in-hugo-without-plugins",{"path":1190,"title":1191},"\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":1193,"title":1194},"\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":1196,"title":1197},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1199,"title":1200},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1202,"title":1203},"\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":1205,"title":1206},"\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":1208,"title":1209},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1211,"title":1212},"\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":1214,"title":1215},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1217,"title":1218},"\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":1220,"title":1221},"\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":1223,"title":1224},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1226,"title":1227},"\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":1229,"title":1230},"\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":1232,"title":1233},"\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":1235,"title":1236},"\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":1238,"title":1239},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1241,"title":1242},"\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":1244,"title":1245},"\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":1247,"title":1248},"\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":1250,"title":1251},"\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":1253,"title":1254},"\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":1256,"title":1257},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1259,"title":1260},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1262,"title":1263},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1265,"title":1266},"\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":1268,"title":1269},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1271,"title":1272},"\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":1274,"title":1275},"\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":1277,"title":1278},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1280,"title":1281},"\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":1283,"title":1284},"\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":1286,"title":1287},"\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":1289,"title":1290},"\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":1292,"title":1293},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1295,"title":1296},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1298,"title":1299},"\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":1301,"title":1302},"\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":1304,"title":1305},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1307,"title":1308},"\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":1310,"title":1311},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1313,"title":1314},"\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":1316,"title":1317},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1319,"title":1320},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1322,"title":1323},"\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":1325,"title":1326},"\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":1328,"title":1329},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1331,"title":1332},"\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":1334,"title":1335},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1337,"title":1338},"\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":1340,"title":1341},"\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":1343,"title":1344},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1346,"title":1347},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1349,"title":910},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fcaching-hugo-builds-in-github-actions",{"path":1351,"title":1352},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1354,"title":1355},"\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":1357,"title":1358},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1360,"title":1361},"\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":1363,"title":1364},"\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":1366,"title":1367},"\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":1369,"title":1370},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1372,"title":1373},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1375,"title":1376},"\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":1378,"title":1379},"\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":1381,"title":1382},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1384,"title":1385},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1387,"title":1388},"\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":1390,"title":1391},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1393,"title":1394},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1396,"title":1397},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1399,"title":1400},"\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":1402,"title":1403},"\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":1405,"title":1406},"\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":1408,"title":1409},"\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":1411,"title":1412},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1414,"title":1415},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":1417,"title":1418},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1420,"title":1421},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1423,"title":1424},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1426,"title":1427},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1429,"title":1430},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":1432,"title":1433},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1435,"title":1436},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1438,"title":1439},"\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":1441,"title":1442},"\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":1444,"title":1445},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1447,"title":1448},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1450,"title":1451},"\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":1453,"title":1454},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1456,"title":1457},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1459,"title":1460},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1462,"title":1463},"\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":1465,"title":1466},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1468,"title":1469},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1471,"title":1472},"\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":1474,"title":1475},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1477,"title":1478},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1480,"title":1481},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1483,"title":1484},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1486,"title":1487},"\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":1489,"title":1490},"\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":1492,"title":1493},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1495,"title":1496},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1498,"title":1499},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1501,"title":1502},"\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",1789722847993]