[{"data":1,"prerenderedAt":1662},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fremote-caching-with-turborepo-for-ssg-monorepos":3,"all-docs-nav":1120},{"id":4,"title":5,"body":6,"breadcrumb":1095,"dateModified":1105,"datePublished":1105,"description":1106,"extension":1107,"faq":1108,"meta":1113,"navigation":1114,"path":1115,"seo":1116,"slug":12,"stem":1117,"type":1118,"__hash__":1119},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fremote-caching-with-turborepo-for-ssg-monorepos\u002Findex.md","Remote Caching with Turborepo for SSG Monorepos",{"type":7,"value":8,"toc":1076},"minimark",[9,13,17,26,31,52,56,71,244,248,259,478,513,520,524,535,653,668,678,682,698,786,790,800,803,806,810,813,831,834,858,919,923,934,938,991,995,998,1002,1007,1010,1014,1017,1021,1024,1028,1031,1035,1072],[10,11,5],"h1",{"id":12},"remote-caching-with-turborepo-for-ssg-monorepos",[14,15,16],"p",{},"A monorepo with several static sites and shared packages builds the same things over and over. The design-token package is compiled on every CI run even though it changed last month. The blog is rebuilt on a colleague's laptop after they pulled a change that only touched the docs. Two pull requests that differ only in a README both rebuild all three sites.",[14,18,19,20,25],{},"Turborepo removes that repetition. It hashes each task's inputs, stores the outputs under that hash, and replays them instantly the next time any machine runs the same task with the same inputs. With a remote cache, a build done once in CI is reused by every other run and every developer. This guide sets it up for a static-site monorepo, configures inputs and outputs correctly for site builds, and debugs cache misses. It is part of ",[21,22,24],"a",{"href":23},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002F","Incremental Builds and Build Caching for SSGs",".",[27,28,30],"h2",{"id":29},"prerequisites","Prerequisites",[32,33,34,46,49],"ul",{},[35,36,37,38,42,43,25],"li",{},"A workspace monorepo (npm, pnpm, Yarn or Bun) with sites under ",[39,40,41],"code",{},"sites\u002F"," and shared code under ",[39,44,45],{},"packages\u002F",[35,47,48],{},"Node.js 20 or later.",[35,50,51],{},"A remote cache: Vercel's hosted cache, or a self-hosted server on S3, R2 or similar storage.",[27,53,55],{"id":54},"how-task-hashing-works","How Task Hashing Works",[14,57,58,59,62,63,66,67,70],{},"Turborepo treats each ",[39,60,61],{},"package#task"," pair — ",[39,64,65],{},"docs#build",", ",[39,68,69],{},"ui#build"," — as a unit. Before running it, Turborepo computes a hash from everything that could affect its output. If the hash is in the local or remote cache, it restores the recorded outputs and logs and skips the task.",[72,73,74,240],"figure",{},[75,76,83,84,83,88,83,92,83,99,83,117],"svg",{"viewBox":77,"role":78,"ariaLabelledBy":79,"xmlns":82},"0 0 760 280","img",[80,81],"trc-hash-title","trc-hash-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[85,86,87],"title",{"id":80},"Inputs to a Turborepo task hash and the cache lookup",[89,90,91],"desc",{"id":81},"The hash for docs#build combines the docs source files, the hash of ui#build, lockfile entries for its dependencies, declared environment variables and the turbo.json task definition. The hash is looked up in the local cache, then the remote cache. A hit restores dist and logs; a miss runs the build and uploads the result.",[93,94],"rect",{"x":95,"y":95,"width":96,"height":97,"fill":98},"0","760","280","#ffffff",[100,101,102,103,83],"defs",{},"\n    ",[104,105,112],"marker",{"id":106,"viewBox":107,"refX":108,"refY":109,"markerWidth":110,"markerHeight":110,"orient":111},"trc-hash-arrow","0 0 10 10","9","5","7","auto-start-reverse",[113,114],"path",{"d":115,"fill":116},"M0,0 L10,5 L0,10 z","#556071",[118,119,102,121,102,129,102,138,102,144,102,149,102,153,102,157,102,161,102,165,102,170,102,177,102,183,102,188,102,195,102,201,102,206,102,209,102,213,102,218,102,223,102,226,102,230,102,236,83],"g",{"style":120},"font-family:system-ui, sans-serif;font-size:12px",[122,123,128],"text",{"x":124,"y":125,"fill":126,"style":127},"380","26","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","docs#build: hash, then look up",[93,130],{"x":131,"y":132,"width":133,"height":134,"rx":135,"fill":136,"style":137,"stroke":136},"20","46","230","200","8","#166a9e","fill-opacity:0.06",[122,139,143],{"x":140,"y":141,"fill":136,"style":142},"135","68","font-weight:700;text-anchor:middle","hash inputs",[122,145,148],{"x":146,"y":147,"fill":126},"36","96","sites\u002Fdocs source files",[122,150,152],{"x":146,"y":151,"fill":126},"120","hash of ui#build, tokens#build",[122,154,156],{"x":146,"y":155,"fill":126},"144","lockfile entries used",[122,158,160],{"x":146,"y":159,"fill":126},"168","env: SITE_URL, CMS_ENV",[122,162,164],{"x":146,"y":163,"fill":126},"192","turbo.json task config",[122,166,169],{"x":146,"y":167,"fill":116,"style":168},"224","font-size:11px","not the date, not the machine",[93,171],{"x":172,"y":173,"width":151,"height":174,"rx":135,"fill":175,"style":176,"stroke":175},"290","112","50","#6a4c93","fill-opacity:0.12",[122,178,182],{"x":179,"y":180,"fill":126,"style":181},"350","134","text-anchor:middle","hash",[122,184,187],{"x":179,"y":185,"fill":116,"style":186},"151","font-size:11px;text-anchor:middle","9f3c…e1",[189,190],"line",{"x1":191,"y1":192,"x2":193,"y2":192,"stroke":116,"style":194},"250","137","286","stroke-width:1.5px;marker-end:url(#trc-hash-arrow)",[93,196],{"x":197,"y":132,"width":172,"height":198,"rx":135,"fill":199,"style":200,"stroke":199},"450","80","#3f6410","fill-opacity:0.1",[122,202,205],{"x":203,"y":204,"fill":199,"style":142},"595","72","hit (local or remote)",[122,207,208],{"x":203,"y":147,"fill":126,"style":181},"restore dist\u002F and logs",[122,210,212],{"x":203,"y":211,"fill":116,"style":186},"114","seconds",[93,214],{"x":197,"y":215,"width":172,"height":198,"rx":135,"fill":216,"style":217,"stroke":216},"150","#d83b41","fill-opacity:0.08",[122,219,222],{"x":203,"y":220,"fill":221,"style":142},"176","#b32b30","miss",[122,224,225],{"x":203,"y":134,"fill":126,"style":181},"run build, save, upload",[122,227,229],{"x":203,"y":228,"fill":116,"style":186},"218","minutes, once",[189,231],{"x1":232,"y1":233,"x2":234,"y2":235,"stroke":116,"style":194},"410","128","446","90",[189,237],{"x1":232,"y1":238,"x2":234,"y2":239,"stroke":116,"style":194},"146","186",[241,242,243],"figcaption",{},"Because dependency hashes feed into the site's hash, a change to a shared package invalidates exactly the sites that use it.",[27,245,247],{"id":246},"configuring-turbojson","Configuring turbo.json",[14,249,250,251,254,255,258],{},"Install Turborepo at the root (",[39,252,253],{},"npm install -D turbo",") and add a ",[39,256,257],{},"turbo.json",":",[260,261,266],"pre",{"className":262,"code":263,"language":264,"meta":265,"style":265},"language-json shiki shiki-themes github-light github-dark","{\n  \"$schema\": \"https:\u002F\u002Fturborepo.com\u002Fschema.json\",\n  \"tasks\": {\n    \"build\": {\n      \"dependsOn\": [\"^build\"],\n      \"inputs\": [\"$TURBO_DEFAULT$\", \"!README.md\", \"!**\u002F*.test.*\"],\n      \"outputs\": [\"dist\u002F**\", \".output\u002Fpublic\u002F**\"],\n      \"env\": [\"SITE_URL\", \"CMS_ENV\", \"PUBLIC_*\"]\n    },\n    \"check\": {\n      \"dependsOn\": [\"^build\"],\n      \"outputs\": []\n    },\n    \"dev\": {\n      \"cache\": false,\n      \"persistent\": true\n    }\n  }\n}\n","json","",[39,267,268,276,293,302,310,325,348,366,390,396,404,415,423,428,436,449,460,466,472],{"__ignoreMap":265},[269,270,272],"span",{"class":189,"line":271},1,[269,273,275],{"class":274},"sVt8B","{\n",[269,277,279,283,286,290],{"class":189,"line":278},2,[269,280,282],{"class":281},"sj4cs","  \"$schema\"",[269,284,285],{"class":274},": ",[269,287,289],{"class":288},"sZZnC","\"https:\u002F\u002Fturborepo.com\u002Fschema.json\"",[269,291,292],{"class":274},",\n",[269,294,296,299],{"class":189,"line":295},3,[269,297,298],{"class":281},"  \"tasks\"",[269,300,301],{"class":274},": {\n",[269,303,305,308],{"class":189,"line":304},4,[269,306,307],{"class":281},"    \"build\"",[269,309,301],{"class":274},[269,311,313,316,319,322],{"class":189,"line":312},5,[269,314,315],{"class":281},"      \"dependsOn\"",[269,317,318],{"class":274},": [",[269,320,321],{"class":288},"\"^build\"",[269,323,324],{"class":274},"],\n",[269,326,328,331,333,336,338,341,343,346],{"class":189,"line":327},6,[269,329,330],{"class":281},"      \"inputs\"",[269,332,318],{"class":274},[269,334,335],{"class":288},"\"$TURBO_DEFAULT$\"",[269,337,66],{"class":274},[269,339,340],{"class":288},"\"!README.md\"",[269,342,66],{"class":274},[269,344,345],{"class":288},"\"!**\u002F*.test.*\"",[269,347,324],{"class":274},[269,349,351,354,356,359,361,364],{"class":189,"line":350},7,[269,352,353],{"class":281},"      \"outputs\"",[269,355,318],{"class":274},[269,357,358],{"class":288},"\"dist\u002F**\"",[269,360,66],{"class":274},[269,362,363],{"class":288},"\".output\u002Fpublic\u002F**\"",[269,365,324],{"class":274},[269,367,369,372,374,377,379,382,384,387],{"class":189,"line":368},8,[269,370,371],{"class":281},"      \"env\"",[269,373,318],{"class":274},[269,375,376],{"class":288},"\"SITE_URL\"",[269,378,66],{"class":274},[269,380,381],{"class":288},"\"CMS_ENV\"",[269,383,66],{"class":274},[269,385,386],{"class":288},"\"PUBLIC_*\"",[269,388,389],{"class":274},"]\n",[269,391,393],{"class":189,"line":392},9,[269,394,395],{"class":274},"    },\n",[269,397,399,402],{"class":189,"line":398},10,[269,400,401],{"class":281},"    \"check\"",[269,403,301],{"class":274},[269,405,407,409,411,413],{"class":189,"line":406},11,[269,408,315],{"class":281},[269,410,318],{"class":274},[269,412,321],{"class":288},[269,414,324],{"class":274},[269,416,418,420],{"class":189,"line":417},12,[269,419,353],{"class":281},[269,421,422],{"class":274},": []\n",[269,424,426],{"class":189,"line":425},13,[269,427,395],{"class":274},[269,429,431,434],{"class":189,"line":430},14,[269,432,433],{"class":281},"    \"dev\"",[269,435,301],{"class":274},[269,437,439,442,444,447],{"class":189,"line":438},15,[269,440,441],{"class":281},"      \"cache\"",[269,443,285],{"class":274},[269,445,446],{"class":281},"false",[269,448,292],{"class":274},[269,450,452,455,457],{"class":189,"line":451},16,[269,453,454],{"class":281},"      \"persistent\"",[269,456,285],{"class":274},[269,458,459],{"class":281},"true\n",[269,461,463],{"class":189,"line":462},17,[269,464,465],{"class":274},"    }\n",[269,467,469],{"class":189,"line":468},18,[269,470,471],{"class":274},"  }\n",[269,473,475],{"class":189,"line":474},19,[269,476,477],{"class":274},"}\n",[32,479,480,489,497,505],{},[35,481,482,488],{},[483,484,485],"strong",{},[39,486,487],{},"dependsOn: [\"^build\"]"," builds a package's workspace dependencies first and includes their hashes in its own.",[35,490,491,496],{},[483,492,493],{},[39,494,495],{},"inputs"," starts from the default (all files in the package tracked by Git) and removes files that do not affect the build. Excluding READMEs and tests stops documentation edits from invalidating the build.",[35,498,499,504],{},[483,500,501],{},[39,502,503],{},"outputs"," lists what to cache and restore. For static sites, that is the build output folder; list every generator's folder if sites differ.",[35,506,507,512],{},[483,508,509],{},[39,510,511],{},"env"," declares environment variables that change the output. Any variable used at build time but not listed here is a source of wrong cache hits — a production build restored into a preview, for instance.",[14,514,515,516,519],{},"Run ",[39,517,518],{},"npx turbo run build"," from the root. The first run builds everything; the second, with nothing changed, finishes in under a second with \"FULL TURBO\" and every task marked as a cache hit.",[27,521,523],{"id":522},"turning-on-the-remote-cache","Turning On the Remote Cache",[14,525,526,527,530,531,534],{},"Local caching helps one machine. The remote cache shares results across CI runs and developers. With Vercel's hosted cache, run ",[39,528,529],{},"npx turbo login"," and ",[39,532,533],{},"npx turbo link"," locally, and in CI set two variables:",[260,536,540],{"className":537,"code":538,"language":539,"meta":265,"style":265},"language-yaml shiki shiki-themes github-light github-dark","env:\n  TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}\n  TURBO_TEAM: ${{ vars.TURBO_TEAM }}\nsteps:\n  - uses: actions\u002Fcheckout@v4\n  - uses: actions\u002Fsetup-node@v4\n    with: { node-version-file: .nvmrc, cache: npm }\n  - run: npm ci\n  - run: npx turbo run build check --affected\n","yaml",[39,541,542,550,560,570,577,590,601,630,642],{"__ignoreMap":265},[269,543,544,547],{"class":189,"line":271},[269,545,511],{"class":546},"s9eBZ",[269,548,549],{"class":274},":\n",[269,551,552,555,557],{"class":189,"line":278},[269,553,554],{"class":546},"  TURBO_TOKEN",[269,556,285],{"class":274},[269,558,559],{"class":288},"${{ secrets.TURBO_TOKEN }}\n",[269,561,562,565,567],{"class":189,"line":295},[269,563,564],{"class":546},"  TURBO_TEAM",[269,566,285],{"class":274},[269,568,569],{"class":288},"${{ vars.TURBO_TEAM }}\n",[269,571,572,575],{"class":189,"line":304},[269,573,574],{"class":546},"steps",[269,576,549],{"class":274},[269,578,579,582,585,587],{"class":189,"line":312},[269,580,581],{"class":274},"  - ",[269,583,584],{"class":546},"uses",[269,586,285],{"class":274},[269,588,589],{"class":288},"actions\u002Fcheckout@v4\n",[269,591,592,594,596,598],{"class":189,"line":327},[269,593,581],{"class":274},[269,595,584],{"class":546},[269,597,285],{"class":274},[269,599,600],{"class":288},"actions\u002Fsetup-node@v4\n",[269,602,603,606,609,612,614,617,619,622,624,627],{"class":189,"line":350},[269,604,605],{"class":546},"    with",[269,607,608],{"class":274},": { ",[269,610,611],{"class":546},"node-version-file",[269,613,285],{"class":274},[269,615,616],{"class":288},".nvmrc",[269,618,66],{"class":274},[269,620,621],{"class":546},"cache",[269,623,285],{"class":274},[269,625,626],{"class":288},"npm",[269,628,629],{"class":274}," }\n",[269,631,632,634,637,639],{"class":189,"line":368},[269,633,581],{"class":274},[269,635,636],{"class":546},"run",[269,638,285],{"class":274},[269,640,641],{"class":288},"npm ci\n",[269,643,644,646,648,650],{"class":189,"line":392},[269,645,581],{"class":274},[269,647,636],{"class":546},[269,649,285],{"class":274},[269,651,652],{"class":288},"npx turbo run build check --affected\n",[14,654,655,656,659,660,663,664,667],{},"To self-host, run one of the open-source cache servers that implement Turborepo's HTTP API in front of an S3 or Cloudflare R2 bucket, and set ",[39,657,658],{},"TURBO_API"," to its URL along with a token. Keep artifact signing on (",[39,661,662],{},"\"remoteCache\": { \"signature\": true }"," with ",[39,665,666],{},"TURBO_REMOTE_CACHE_SIGNATURE_KEY",") so a compromised cache cannot inject build output.",[14,669,670,673,674,25],{},[39,671,672],{},"--affected"," limits the run to packages changed compared with the base branch and their dependents, which pairs naturally with the per-site deploys in ",[21,675,677],{"href":676},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos\u002F","Matrix Builds for Multi-Site Monorepos",[27,679,681],{"id":680},"what-stays-outside-the-turborepo-cache","What Stays Outside the Turborepo Cache",[14,683,684,685,688,689,692,693,697],{},"Turborepo caches a task's declared outputs. It does not know about generator-internal caches like Astro's ",[39,686,687],{},"node_modules\u002F.astro"," or Hugo's ",[39,690,691],{},"resources\u002F_gen",". A cache hit makes those irrelevant, because the build does not run. A miss, though, runs the build from scratch unless those caches are also restored. Keep the generator cache step from ",[21,694,696],{"href":695},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions\u002F","Building Astro Sites with GitHub Actions"," alongside Turborepo: the remote cache handles \"nothing changed in this site\", the generator cache makes \"one page changed\" fast.",[72,699,700,783],{},[75,701,83,706,83,709,83,712,83,715],{"viewBox":702,"role":78,"ariaLabelledBy":703,"xmlns":82},"0 0 760 260",[704,705],"trc-res-title","trc-res-desc",[85,707,708],{"id":704},"CI build step time by kind of change",[89,710,711],{"id":705},"Without Turborepo, every change took 11 minutes to build three sites. With a remote cache: a README-only change took 20 seconds, a change to one site took 3 minutes 10 seconds, and a change to the shared ui package took 6 minutes 40 seconds because two sites rebuilt.",[93,713],{"x":95,"y":95,"width":96,"height":714,"fill":98},"260",[118,716,102,717,102,721,102,726,102,732,102,738,102,742,102,747,102,752,102,757,102,760,102,765,102,770,102,774,102,779,83],{"style":120},[122,718,720],{"x":124,"y":719,"fill":126,"style":127},"28","Build step duration by kind of change",[122,722,725],{"x":723,"y":724,"fill":126},"131","74","before: any change",[93,727],{"x":728,"y":729,"width":730,"height":131,"fill":216,"style":731},"240","62","440","fill-opacity:0.45",[122,733,737],{"x":734,"y":735,"fill":126,"style":736},"672","77","text-anchor:end","11:00",[122,739,741],{"x":133,"y":740,"fill":126,"style":736},"118","README only",[93,743],{"x":728,"y":744,"width":745,"height":131,"fill":199,"style":746},"106","14","fill-opacity:0.6",[122,748,751],{"x":749,"y":750,"fill":126},"262","121","0:20",[122,753,756],{"x":754,"y":755,"fill":126},"138","162","one site's content",[93,758],{"x":728,"y":215,"width":759,"height":131,"fill":199,"style":731},"127",[122,761,764],{"x":762,"y":763,"fill":126},"375","165","3:10",[122,766,769],{"x":767,"y":768,"fill":126},"136","206","shared ui package",[93,771],{"x":728,"y":772,"width":773,"height":131,"fill":136,"style":731},"194","267",[122,775,778],{"x":776,"y":777,"fill":126},"515","209","6:40",[122,780,782],{"x":124,"y":781,"fill":116,"style":186},"246","three sites, two shared packages; remote cache on Cloudflare R2",[241,784,785],{},"Build time now follows the size of the change rather than the size of the repository.",[27,787,789],{"id":788},"deploying-from-cache-hits","Deploying From Cache Hits",[14,791,792,793,796,797,799],{},"A cache hit restores the site's ",[39,794,795],{},"dist"," folder exactly as the original build produced it, so the deploy step does not need to know whether the build ran. That is convenient, and it raises one question: should an unchanged site be redeployed at all? Usually not. Combine ",[39,798,672],{}," or a per-site change check with the deploy step, and skip deploying sites whose build was a cache hit from a previous commit already in production. The site's output is byte-for-byte what is live, and redeploying it only adds noise to the deploy history and purges CDN caches for nothing.",[14,801,802],{},"Where a platform requires a deploy on every commit — some preview systems do — the restored output makes that deploy fast, because the upload step sends only changed files and nothing changed.",[14,804,805],{},"Treat remote cache storage like any other build infrastructure. Set a retention policy on the bucket so old artifacts expire after a few weeks, restrict write access to CI, and give developers a read-only token so a local experiment cannot poison the shared cache.",[27,807,809],{"id":808},"debugging-cache-misses","Debugging Cache Misses",[14,811,812],{},"A cache that misses when it should hit wastes time; one that hits when it should miss ships wrong output. Both come from the hash inputs. Turborepo shows what went into every hash:",[32,814,815,821],{},[35,816,817,820],{},[39,818,819],{},"npx turbo run build --dry=json"," prints each task's hash and its inputs without running anything.",[35,822,823,826,827,830],{},[39,824,825],{},"npx turbo run build --summarize"," writes a run summary to ",[39,828,829],{},".turbo\u002Fruns\u002F"," listing hashes, cache status and the environment variables that were included.",[14,832,833],{},"Compare two summaries from runs that should have matched. Typical culprits:",[835,836,837,846,852],"ol",{},[35,838,839,842,843,845],{},[483,840,841],{},"Undeclared environment variables."," A variable read by the build but missing from ",[39,844,511],{}," is ignored in the hash. Turborepo's strict environment mode (the default) removes undeclared variables from the task's environment, which surfaces these as build errors rather than wrong hits.",[35,847,848,851],{},[483,849,850],{},"Generated files in inputs."," A build that writes a timestamp or a sitemap into the source tree changes its own inputs; exclude generated paths or write them to the output folder.",[35,853,854,857],{},[483,855,856],{},"Lockfile churn."," Reinstalling with a different package manager version can rewrite lockfile entries and invalidate everything.",[72,859,860,916],{},[75,861,83,866,83,869,83,872,83,874],{"viewBox":862,"role":78,"ariaLabelledBy":863,"xmlns":82},"0 0 760 230",[864,865],"trc-miss-title","trc-miss-desc",[85,867,868],{"id":864},"Causes of unexpected cache misses found in run summaries",[89,870,871],{"id":865},"In the first month, unexpected misses were caused by a build timestamp written into a source file in 9 cases, by an undeclared environment variable in 5 cases, and by lockfile changes from a different npm version in 3 cases.",[93,873],{"x":95,"y":95,"width":96,"height":133,"fill":98},[118,875,102,876,102,879,102,883,102,888,102,891,102,895,102,897,102,900,102,905,102,907,102,912,83],{"style":120},[122,877,878],{"x":124,"y":719,"fill":126,"style":127},"Unexpected misses in the first month, by cause",[122,880,882],{"x":881,"y":724,"fill":126},"126","timestamp in a source file",[93,884],{"x":885,"y":729,"width":886,"height":131,"fill":887,"style":731},"270","360","#8a6d0f",[122,889,108],{"x":890,"y":735,"fill":126},"638",[122,892,894],{"x":192,"y":893,"fill":126},"124","undeclared env variable",[93,896],{"x":885,"y":173,"width":134,"height":131,"fill":175,"style":731},[122,898,109],{"x":899,"y":759,"fill":126},"478",[122,901,904],{"x":902,"y":903,"fill":126},"173","174","lockfile rewritten",[93,906],{"x":885,"y":755,"width":151,"height":131,"fill":136,"style":731},[122,908,911],{"x":909,"y":910,"fill":126},"398","177","3",[122,913,915],{"x":124,"y":914,"fill":116,"style":186},"214","each found by diffing two --summarize outputs",[241,917,918],{},"Every miss had a concrete cause in the hash inputs; none was random.",[27,920,922],{"id":921},"measured-impact","Measured Impact",[14,924,925,926,929,930,933],{},"A monorepo with an Astro docs site, an Eleventy blog, an Astro marketing site and two shared packages added Turborepo with a self-hosted remote cache on Cloudflare R2. Before, every CI run built all three sites in about eleven minutes. Afterwards, README and configuration-only changes finished in about 20 seconds, single-site content changes in about three minutes, and shared UI changes in under seven. Developers pulling ",[39,927,928],{},"main"," got cached builds for sites they had not touched, cutting local ",[39,931,932],{},"turbo run build"," from minutes to seconds. Monthly CI minutes fell by 58%.",[27,935,937],{"id":936},"pitfalls-rollback","Pitfalls & Rollback",[32,939,940,948,965,971,977],{},[35,941,942,947],{},[483,943,944,945,25],{},"Missing ",[39,946,503],{}," A hit restores nothing and the deploy step finds an empty folder; list every output directory.",[35,949,950,961,962,25],{},[483,951,952,953,956,957,960],{},"Caching ",[39,954,955],{},"dev"," or ",[39,958,959],{},"deploy"," tasks."," Only cache pure build and check tasks; mark others ",[39,963,964],{},"cache: false",[35,966,967,970],{},[483,968,969],{},"Unsigned remote artifacts."," Turn on signatures so the cache cannot be used to inject output.",[35,972,973,976],{},[483,974,975],{},"Secrets in logs."," Cached logs are replayed on hits; keep secrets out of build output.",[35,978,979,982,983,986,987,990],{},[483,980,981],{},"Rollback:"," run tasks with ",[39,984,985],{},"--force"," to bypass the cache, or remove ",[39,988,989],{},"TURBO_TOKEN"," to fall back to local caching.",[27,992,994],{"id":993},"conclusion","Conclusion",[14,996,997],{},"Turborepo makes a static-site monorepo build only what changed: each task is hashed from its files, dependencies, lockfile entries and declared environment, and outputs are restored from a local or remote cache on a match. Declare inputs, outputs and environment variables carefully, share a signed remote cache between CI and developers, keep generator caches for the builds that do run, and use run summaries to explain every miss.",[27,999,1001],{"id":1000},"faq","FAQ",[1003,1004,1006],"h3",{"id":1005},"what-does-turborepos-remote-cache-store","What does Turborepo's remote cache store?",[14,1008,1009],{},"The outputs of each task - such as a site's dist folder - and its terminal logs, keyed by a hash of the task's inputs. When any machine runs the same task with the same inputs, Turborepo downloads the outputs instead of running the task.",[1003,1011,1013],{"id":1012},"what-goes-into-a-turborepo-task-hash","What goes into a Turborepo task hash?",[14,1015,1016],{},"The files in the package that the task's inputs setting covers, the hashes of its internal dependencies' tasks, the lockfile entries for its external dependencies, declared environment variables and the task configuration itself. Change any of them and the hash changes.",[1003,1018,1020],{"id":1019},"can-i-self-host-a-turborepo-remote-cache","Can I self-host a Turborepo remote cache?",[14,1022,1023],{},"Yes. Turborepo speaks a documented HTTP API, and open-source servers implement it on top of S3, Cloudflare R2, Google Cloud Storage or a local disk. Point turbo at it with the API URL, team and token settings.",[1003,1025,1027],{"id":1026},"why-does-my-turborepo-cache-miss-when-nothing-changed","Why does my Turborepo cache miss when nothing changed?",[14,1029,1030],{},"Usually because an input outside the declared ones varies between runs - an environment variable not listed in env, a timestamp written into a generated file, or build output accidentally included in inputs. The --summarize flag and turbo run --dry show exactly what went into each hash.",[27,1032,1034],{"id":1033},"related","Related",[32,1036,1037,1046,1053,1058,1065],{},[35,1038,1039,1042,1043,1045],{},[483,1040,1041],{},"Parent:"," ",[21,1044,24],{"href":23}," — caching across generators.",[35,1047,1048,1052],{},[21,1049,1051],{"href":1050},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fsharing-build-cache-across-ci-runners\u002F","Sharing Build Cache Across CI Runners"," — generator caches between runners.",[35,1054,1055,1057],{},[21,1056,677],{"href":676}," — deploying only affected sites.",[35,1059,1060,1064],{},[21,1061,1063],{"href":1062},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fincremental-builds-in-astro-with-the-content-layer\u002F","Incremental Builds in Astro with the Content Layer"," — making cache misses cheaper.",[35,1066,1067,1071],{},[21,1068,1070],{"href":1069},"\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"," — tracking hit rates over time.",[1073,1074,1075],"style",{},"html pre.shiki code .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .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 .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}",{"title":265,"searchDepth":278,"depth":278,"links":1077},[1078,1079,1080,1081,1082,1083,1084,1085,1086,1087,1088,1094],{"id":29,"depth":278,"text":30},{"id":54,"depth":278,"text":55},{"id":246,"depth":278,"text":247},{"id":522,"depth":278,"text":523},{"id":680,"depth":278,"text":681},{"id":788,"depth":278,"text":789},{"id":808,"depth":278,"text":809},{"id":921,"depth":278,"text":922},{"id":936,"depth":278,"text":937},{"id":993,"depth":278,"text":994},{"id":1000,"depth":278,"text":1001,"children":1089},[1090,1091,1092,1093],{"id":1005,"depth":295,"text":1006},{"id":1012,"depth":295,"text":1013},{"id":1019,"depth":295,"text":1020},{"id":1026,"depth":295,"text":1027},{"id":1033,"depth":278,"text":1034},[1096,1099,1102,1103],{"name":1097,"item":1098},"Home","\u002F",{"name":1100,"item":1101},"Production-Ready Deployment & CI\u002FCD Workflows","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":24,"item":23},{"name":5,"item":1104},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fremote-caching-with-turborepo-for-ssg-monorepos\u002F","2026-09-18","Use Turborepo task hashing and a remote cache to skip rebuilding unchanged sites and packages in a static site monorepo, locally and in CI.","md",[1109,1110,1111,1112],{"q":1006,"a":1009},{"q":1013,"a":1016},{"q":1020,"a":1023},{"q":1027,"a":1030},{},true,"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fremote-caching-with-turborepo-for-ssg-monorepos",{"title":5,"description":1106},"production-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fremote-caching-with-turborepo-for-ssg-monorepos\u002Findex","article","njaTXVaTam0kWf7ur_4mSmio5q3g6ckM7d7HN2XTHTI",[1121,1124,1127,1130,1133,1136,1139,1142,1145,1148,1151,1154,1157,1160,1163,1166,1169,1172,1175,1178,1181,1184,1187,1190,1193,1196,1199,1202,1205,1208,1211,1214,1217,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,1382,1385,1388,1391,1394,1397,1400,1403,1406,1409,1412,1415,1418,1421,1424,1427,1430,1433,1436,1439,1442,1445,1448,1451,1454,1457,1460,1463,1466,1469,1472,1475,1478,1481,1484,1487,1490,1493,1495,1498,1501,1504,1507,1510,1512,1515,1518,1520,1522,1524,1525,1527,1530,1533,1536,1539,1542,1545,1548,1551,1554,1557,1560,1563,1566,1569,1572,1575,1578,1581,1584,1587,1590,1593,1596,1599,1602,1605,1608,1611,1614,1617,1620,1623,1626,1629,1632,1635,1638,1641,1644,1647,1650,1653,1656,1659],{"path":1122,"title":1123},"\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":1125,"title":1126},"\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":1128,"title":1129},"\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":1131,"title":1132},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1134,"title":1135},"\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":1137,"title":1138},"\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":1140,"title":1141},"\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":1143,"title":1144},"\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":1146,"title":1147},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1149,"title":1150},"\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":1152,"title":1153},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1155,"title":1156},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1158,"title":1159},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1161,"title":1162},"\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":1164,"title":1165},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-partialcached-for-faster-builds","Hugo partialCached for Faster Builds",{"path":1167,"title":1168},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1170,"title":1171},"\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":1173,"title":1174},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Freducing-hugo-memory-usage-on-ci-runners","Reducing Hugo Memory Usage on CI Runners",{"path":1176,"title":1177},"\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":1179,"title":1180},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1182,"title":1183},"\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":1185,"title":1186},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1188,"title":1189},"\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":1191,"title":1192},"\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":1194,"title":1195},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1197,"title":1198},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1200,"title":1201},"\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":1203,"title":1204},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1206,"title":1207},"\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":1209,"title":1210},"\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":1212,"title":1213},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1215,"title":1216},"\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":1218,"title":1219},"\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":1221,"title":1222},"\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":1224,"title":1225},"\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":1227,"title":1228},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1230,"title":1231},"\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":1233,"title":1234},"\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":1236,"title":1237},"\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":1239,"title":1240},"\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":1242,"title":1243},"\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":1245,"title":1246},"\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":1248,"title":1249},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1251,"title":1252},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1254,"title":1255},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1257,"title":1258},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1260,"title":1261},"\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":1263,"title":1264},"\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":1266,"title":1267},"\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":1269,"title":1270},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1272,"title":1273},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1275,"title":1276},"\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":1278,"title":1279},"\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":1281,"title":1282},"\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":1284,"title":1285},"\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":1287,"title":1288},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1290,"title":1291},"\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":1293,"title":1294},"\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":1296,"title":1297},"\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":1299,"title":1300},"\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":1302,"title":1303},"\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":1305,"title":1306},"\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":1308,"title":1309},"\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":1311,"title":1312},"\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":1314,"title":1315},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1317,"title":1318},"\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":1320,"title":1321},"\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":1323,"title":1324},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1326,"title":1327},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1329,"title":1330},"\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":1332,"title":1333},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1335,"title":1336},"\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":1338,"title":1339},"\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":1341,"title":1342},"\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":1344,"title":1345},"\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":1347,"title":1348},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1350,"title":1351},"\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":1353,"title":1354},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Foptimizing-webp-images-in-hugo-without-plugins","Optimizing WebP Images in Hugo Without Plugins",{"path":1356,"title":1357},"\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":1359,"title":1360},"\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":1362,"title":1363},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1365,"title":1366},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1368,"title":1369},"\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":1371,"title":1372},"\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":1374,"title":1375},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1377,"title":1378},"\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":1380,"title":1381},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1383,"title":1384},"\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":1386,"title":1387},"\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":1389,"title":1390},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1392,"title":1393},"\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":1395,"title":1396},"\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":1398,"title":1399},"\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":1401,"title":1402},"\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":1404,"title":1405},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1407,"title":1408},"\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":1410,"title":1411},"\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":1413,"title":1414},"\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":1416,"title":1417},"\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":1419,"title":1420},"\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":1422,"title":1423},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1425,"title":1426},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1428,"title":1429},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1431,"title":1432},"\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":1434,"title":1435},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1437,"title":1438},"\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":1440,"title":1441},"\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":1443,"title":1444},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1446,"title":1447},"\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":1449,"title":1450},"\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":1452,"title":1453},"\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":1455,"title":1456},"\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":1458,"title":1459},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1461,"title":1462},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1464,"title":1465},"\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":1467,"title":1468},"\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":1470,"title":1471},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1473,"title":1474},"\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":1476,"title":1477},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1479,"title":1480},"\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":1482,"title":1483},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1485,"title":1486},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1488,"title":1489},"\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":1491,"title":1492},"\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":1494,"title":696},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions",{"path":1496,"title":1497},"\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":1499,"title":1500},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1502,"title":1503},"\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":1505,"title":1506},"\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":1508,"title":1509},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1511,"title":677},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos",{"path":1513,"title":1514},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fcaching-hugo-builds-in-github-actions","Caching Hugo Builds in GitHub Actions",{"path":1516,"title":1517},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1519,"title":1063},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fincremental-builds-in-astro-with-the-content-layer",{"path":1521,"title":24},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs",{"path":1523,"title":1070},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fmeasuring-build-time-regressions-in-ci",{"path":1115,"title":5},{"path":1526,"title":1051},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fsharing-build-cache-across-ci-runners",{"path":1528,"title":1529},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1531,"title":1532},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1534,"title":1535},"\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":1537,"title":1538},"\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":1540,"title":1541},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1543,"title":1544},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1546,"title":1547},"\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":1549,"title":1550},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1552,"title":1553},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1555,"title":1556},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1558,"title":1559},"\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":1561,"title":1562},"\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":1564,"title":1565},"\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":1567,"title":1568},"\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":1570,"title":1571},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1573,"title":1574},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":1576,"title":1577},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1579,"title":1580},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1582,"title":1583},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1585,"title":1586},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1588,"title":1589},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":1591,"title":1592},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1594,"title":1595},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1597,"title":1598},"\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":1600,"title":1601},"\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":1603,"title":1604},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1606,"title":1607},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1609,"title":1610},"\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":1612,"title":1613},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1615,"title":1616},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1618,"title":1619},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1621,"title":1622},"\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":1624,"title":1625},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1627,"title":1628},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1630,"title":1631},"\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":1633,"title":1634},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1636,"title":1637},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1639,"title":1640},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1642,"title":1643},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1645,"title":1646},"\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":1648,"title":1649},"\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":1651,"title":1652},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1654,"title":1655},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1657,"title":1658},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1660,"title":1661},"\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",1789722848109]