[{"data":1,"prerenderedAt":2490},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos":3,"all-docs-nav":1338,"filed:\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos":2481},{"id":4,"title":5,"body":6,"breadcrumb":1313,"dateModified":1323,"datePublished":1323,"description":1324,"extension":1325,"faq":1326,"meta":1331,"navigation":1332,"path":1333,"seo":1334,"slug":12,"stem":1335,"type":1336,"__hash__":1337},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos\u002Findex.md","Matrix Builds for Multi-Site Monorepos",{"type":7,"value":8,"toc":1294},"minimark",[9,13,17,26,31,59,63,66,76,210,214,221,425,444,448,451,687,690,720,724,734,806,815,911,914,918,929,1055,1058,1130,1134,1140,1159,1163,1166,1170,1209,1213,1216,1220,1225,1228,1232,1235,1239,1242,1246,1249,1253,1290],[10,11,5],"h1",{"id":12},"matrix-builds-for-multi-site-monorepos",[14,15,16],"p",{},"Teams that run several static sites — a marketing site, product docs, a blog, an API reference — often keep them in one repository with shared components, design tokens and configuration. The monorepo makes shared changes easy, but a naive CI workflow builds every site on every push. Fixing a typo in the blog rebuilds and redeploys the docs, the marketing site and the API reference, wasting minutes and creating deploys nobody asked for.",[14,18,19,20,25],{},"A dynamic matrix fixes that. One small job works out which sites a change affects, and a matrix build job creates one parallel job per affected site. This guide builds that workflow in GitHub Actions, including shared-package detection, per-site caching and a single required status check. It is part of ",[21,22,24],"a",{"href":23},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002F","GitHub Actions for Automated SSG Builds",".",[27,28,30],"h2",{"id":29},"prerequisites","Prerequisites",[32,33,34,53,56],"ul",{},[35,36,37,38,42,43,42,46,49,50,25],"li",{},"A monorepo with sites in separate folders, for example ",[39,40,41],"code",{},"sites\u002Fdocs",", ",[39,44,45],{},"sites\u002Fblog",[39,47,48],{},"sites\u002Fmarketing",", and shared code in ",[39,51,52],{},"packages\u002F",[35,54,55],{},"A package manager with workspaces (npm, pnpm or Yarn).",[35,57,58],{},"Each site buildable with a single command from its folder.",[27,60,62],{"id":61},"the-layout","The Layout",[14,64,65],{},"The workflow depends on being able to map paths to sites, so a predictable layout helps:",[67,68,74],"pre",{"className":69,"code":71,"language":72,"meta":73},[70],"language-text","repo\u002F\n├── packages\u002F\n│   ├── ui\u002F            # shared components, used by docs and marketing\n│   └── tokens\u002F        # design tokens, used by every site\n├── sites\u002F\n│   ├── docs\u002F          # Astro\n│   ├── blog\u002F          # Eleventy\n│   └── marketing\u002F     # Astro\n└── package-lock.json\n","text","",[39,75,71],{"__ignoreMap":73},[77,78,79,206],"figure",{},[80,81,88,89,88,93,88,97,88,104,88,122],"svg",{"viewBox":82,"role":83,"ariaLabelledBy":84,"xmlns":87},"0 0 760 280","img",[85,86],"mxb-dep-title","mxb-dep-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[90,91,92],"title",{"id":85},"Which sites a change affects",[94,95,96],"desc",{"id":86},"Three sites and two shared packages. The tokens package is used by docs, blog and marketing. The ui package is used by docs and marketing. A change in sites\u002Fblog affects only blog. A change in packages\u002Fui affects docs and marketing. A change in tokens or the lockfile affects all three.",[98,99],"rect",{"x":100,"y":100,"width":101,"height":102,"fill":103},"0","760","280","#ffffff",[105,106,107,108,88],"defs",{},"\n    ",[109,110,117],"marker",{"id":111,"viewBox":112,"refX":113,"refY":114,"markerWidth":115,"markerHeight":115,"orient":116},"mxb-dep-arrow","0 0 10 10","9","5","7","auto-start-reverse",[118,119],"path",{"d":120,"fill":121},"M0,0 L10,5 L0,10 z","#556071",[123,124,107,126,107,133,107,142,107,147,107,150,107,154,107,160,107,164,107,167,107,170,107,173,107,176,107,184,107,188,107,192,107,197,107,201,88],"g",{"style":125},"font-family:system-ui, sans-serif;font-size:12px",[72,127,132],{"x":128,"y":129,"fill":130,"style":131},"380","26","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Dependency map used to pick the matrix",[98,134],{"x":135,"y":136,"width":137,"height":138,"rx":139,"fill":140,"style":141,"stroke":140},"80","60","160","44","8","#6a4c93","fill-opacity:0.12",[72,143,146],{"x":137,"y":144,"fill":130,"style":145},"87","text-anchor:middle","packages\u002Ftokens",[98,148],{"x":135,"y":149,"width":137,"height":138,"rx":139,"fill":140,"style":141,"stroke":140},"170",[72,151,153],{"x":137,"y":152,"fill":130,"style":145},"197","packages\u002Fui",[98,155],{"x":156,"y":157,"width":158,"height":138,"rx":139,"fill":159,"style":141,"stroke":159},"500","46","180","#166a9e",[72,161,41],{"x":162,"y":163,"fill":130,"style":145},"590","73",[98,165],{"x":156,"y":166,"width":158,"height":138,"rx":139,"fill":159,"style":141,"stroke":159},"118",[72,168,45],{"x":162,"y":169,"fill":130,"style":145},"145",[98,171],{"x":156,"y":172,"width":158,"height":138,"rx":139,"fill":159,"style":141,"stroke":159},"190",[72,174,48],{"x":162,"y":175,"fill":130,"style":145},"217",[177,178],"line",{"x1":179,"y1":180,"x2":181,"y2":182,"stroke":121,"style":183},"240","78","496","68","stroke-width:1.5px;marker-end:url(#mxb-dep-arrow)",[177,185],{"x1":179,"y1":186,"x2":181,"y2":187,"stroke":121,"style":183},"84","138",[177,189],{"x1":179,"y1":190,"x2":181,"y2":191,"stroke":121,"style":183},"90","206",[177,193],{"x1":179,"y1":194,"x2":181,"y2":195,"stroke":140,"style":196},"186","76","stroke-width:1.5px;stroke-dasharray:5 4;marker-end:url(#mxb-dep-arrow)",[177,198],{"x1":179,"y1":199,"x2":181,"y2":200,"stroke":140,"style":196},"200","212",[72,202,205],{"x":128,"y":203,"fill":121,"style":204},"262","font-size:11px;text-anchor:middle","solid: tokens → all sites · dashed: ui → docs and marketing · lockfile changes → all sites",[207,208,209],"figcaption",{},"A change to a shared package fans out to the sites that use it, and no further.",[27,211,213],{"id":212},"step-1-detect-affected-sites","Step 1: Detect Affected Sites",[14,215,216,217,220],{},"The first job outputs a JSON list of affected sites. ",[39,218,219],{},"dorny\u002Fpaths-filter"," evaluates named path filters against the pull request or push diff:",[67,222,226],{"className":223,"code":224,"language":225,"meta":73,"style":73},"language-yaml shiki shiki-themes github-light github-dark","jobs:\n  changes:\n    runs-on: ubuntu-latest\n    outputs:\n      sites: ${{ steps.filter.outputs.changes }}\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - id: filter\n        uses: dorny\u002Fpaths-filter@v3\n        with:\n          filters: |\n            docs:\n              - 'sites\u002Fdocs\u002F**'\n              - 'packages\u002Fui\u002F**'\n              - 'packages\u002Ftokens\u002F**'\n              - 'package-lock.json'\n            blog:\n              - 'sites\u002Fblog\u002F**'\n              - 'packages\u002Ftokens\u002F**'\n              - 'package-lock.json'\n            marketing:\n              - 'sites\u002Fmarketing\u002F**'\n              - 'packages\u002Fui\u002F**'\n              - 'packages\u002Ftokens\u002F**'\n              - 'package-lock.json'\n","yaml",[39,227,228,240,248,261,269,280,288,302,315,326,334,346,352,358,364,370,376,382,388,393,398,404,410,415,420],{"__ignoreMap":73},[229,230,232,236],"span",{"class":177,"line":231},1,[229,233,235],{"class":234},"s9eBZ","jobs",[229,237,239],{"class":238},"sVt8B",":\n",[229,241,243,246],{"class":177,"line":242},2,[229,244,245],{"class":234},"  changes",[229,247,239],{"class":238},[229,249,251,254,257],{"class":177,"line":250},3,[229,252,253],{"class":234},"    runs-on",[229,255,256],{"class":238},": ",[229,258,260],{"class":259},"sZZnC","ubuntu-latest\n",[229,262,264,267],{"class":177,"line":263},4,[229,265,266],{"class":234},"    outputs",[229,268,239],{"class":238},[229,270,272,275,277],{"class":177,"line":271},5,[229,273,274],{"class":234},"      sites",[229,276,256],{"class":238},[229,278,279],{"class":259},"${{ steps.filter.outputs.changes }}\n",[229,281,283,286],{"class":177,"line":282},6,[229,284,285],{"class":234},"    steps",[229,287,239],{"class":238},[229,289,291,294,297,299],{"class":177,"line":290},7,[229,292,293],{"class":238},"      - ",[229,295,296],{"class":234},"uses",[229,298,256],{"class":238},[229,300,301],{"class":259},"actions\u002Fcheckout@v4\n",[229,303,305,307,310,312],{"class":177,"line":304},8,[229,306,293],{"class":238},[229,308,309],{"class":234},"id",[229,311,256],{"class":238},[229,313,314],{"class":259},"filter\n",[229,316,318,321,323],{"class":177,"line":317},9,[229,319,320],{"class":234},"        uses",[229,322,256],{"class":238},[229,324,325],{"class":259},"dorny\u002Fpaths-filter@v3\n",[229,327,329,332],{"class":177,"line":328},10,[229,330,331],{"class":234},"        with",[229,333,239],{"class":238},[229,335,337,340,342],{"class":177,"line":336},11,[229,338,339],{"class":234},"          filters",[229,341,256],{"class":238},[229,343,345],{"class":344},"szBVR","|\n",[229,347,349],{"class":177,"line":348},12,[229,350,351],{"class":259},"            docs:\n",[229,353,355],{"class":177,"line":354},13,[229,356,357],{"class":259},"              - 'sites\u002Fdocs\u002F**'\n",[229,359,361],{"class":177,"line":360},14,[229,362,363],{"class":259},"              - 'packages\u002Fui\u002F**'\n",[229,365,367],{"class":177,"line":366},15,[229,368,369],{"class":259},"              - 'packages\u002Ftokens\u002F**'\n",[229,371,373],{"class":177,"line":372},16,[229,374,375],{"class":259},"              - 'package-lock.json'\n",[229,377,379],{"class":177,"line":378},17,[229,380,381],{"class":259},"            blog:\n",[229,383,385],{"class":177,"line":384},18,[229,386,387],{"class":259},"              - 'sites\u002Fblog\u002F**'\n",[229,389,391],{"class":177,"line":390},19,[229,392,369],{"class":259},[229,394,396],{"class":177,"line":395},20,[229,397,375],{"class":259},[229,399,401],{"class":177,"line":400},21,[229,402,403],{"class":259},"            marketing:\n",[229,405,407],{"class":177,"line":406},22,[229,408,409],{"class":259},"              - 'sites\u002Fmarketing\u002F**'\n",[229,411,413],{"class":177,"line":412},23,[229,414,363],{"class":259},[229,416,418],{"class":177,"line":417},24,[229,419,369],{"class":259},[229,421,423],{"class":177,"line":422},25,[229,424,375],{"class":259},[14,426,427,428,431,432,435,436,439,440,443],{},"The ",[39,429,430],{},"changes"," output is a JSON array of filter names that matched, such as ",[39,433,434],{},"[\"docs\",\"marketing\"]",". Keeping the filters in the workflow file makes the dependency map explicit and reviewable. For larger monorepos, a workspace tool's own \"affected\" command — ",[39,437,438],{},"turbo ls --affected"," or ",[39,441,442],{},"nx show projects --affected"," — derives the same list from the package graph automatically.",[27,445,447],{"id":446},"step-2-build-each-affected-site","Step 2: Build Each Affected Site",[14,449,450],{},"The build job turns that list into a matrix:",[67,452,454],{"className":223,"code":453,"language":225,"meta":73,"style":73},"  build:\n    needs: changes\n    if: needs.changes.outputs.sites != '[]'\n    runs-on: ubuntu-latest\n    strategy:\n      fail-fast: false\n      matrix:\n        site: ${{ fromJSON(needs.changes.outputs.sites) }}\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with: { node-version-file: .nvmrc, cache: npm }\n      - uses: actions\u002Fcache@v4\n        with:\n          path: sites\u002F${{ matrix.site }}\u002Fnode_modules\u002F.astro\n          key: ${{ matrix.site }}-assets-${{ github.sha }}\n          restore-keys: ${{ matrix.site }}-assets-\n      - run: npm ci\n      - run: npm run build --workspace sites\u002F${{ matrix.site }}\n      - uses: actions\u002Fupload-artifact@v4\n        with:\n          name: site-${{ matrix.site }}\n          path: sites\u002F${{ matrix.site }}\u002Fdist\n",[39,455,456,463,473,483,491,498,509,516,526,532,542,553,581,592,598,608,618,628,640,651,662,668,678],{"__ignoreMap":73},[229,457,458,461],{"class":177,"line":231},[229,459,460],{"class":234},"  build",[229,462,239],{"class":238},[229,464,465,468,470],{"class":177,"line":242},[229,466,467],{"class":234},"    needs",[229,469,256],{"class":238},[229,471,472],{"class":259},"changes\n",[229,474,475,478,480],{"class":177,"line":250},[229,476,477],{"class":234},"    if",[229,479,256],{"class":238},[229,481,482],{"class":259},"needs.changes.outputs.sites != '[]'\n",[229,484,485,487,489],{"class":177,"line":263},[229,486,253],{"class":234},[229,488,256],{"class":238},[229,490,260],{"class":259},[229,492,493,496],{"class":177,"line":271},[229,494,495],{"class":234},"    strategy",[229,497,239],{"class":238},[229,499,500,503,505],{"class":177,"line":282},[229,501,502],{"class":234},"      fail-fast",[229,504,256],{"class":238},[229,506,508],{"class":507},"sj4cs","false\n",[229,510,511,514],{"class":177,"line":290},[229,512,513],{"class":234},"      matrix",[229,515,239],{"class":238},[229,517,518,521,523],{"class":177,"line":304},[229,519,520],{"class":234},"        site",[229,522,256],{"class":238},[229,524,525],{"class":259},"${{ fromJSON(needs.changes.outputs.sites) }}\n",[229,527,528,530],{"class":177,"line":317},[229,529,285],{"class":234},[229,531,239],{"class":238},[229,533,534,536,538,540],{"class":177,"line":328},[229,535,293],{"class":238},[229,537,296],{"class":234},[229,539,256],{"class":238},[229,541,301],{"class":259},[229,543,544,546,548,550],{"class":177,"line":336},[229,545,293],{"class":238},[229,547,296],{"class":234},[229,549,256],{"class":238},[229,551,552],{"class":259},"actions\u002Fsetup-node@v4\n",[229,554,555,557,560,563,565,568,570,573,575,578],{"class":177,"line":348},[229,556,331],{"class":234},[229,558,559],{"class":238},": { ",[229,561,562],{"class":234},"node-version-file",[229,564,256],{"class":238},[229,566,567],{"class":259},".nvmrc",[229,569,42],{"class":238},[229,571,572],{"class":234},"cache",[229,574,256],{"class":238},[229,576,577],{"class":259},"npm",[229,579,580],{"class":238}," }\n",[229,582,583,585,587,589],{"class":177,"line":354},[229,584,293],{"class":238},[229,586,296],{"class":234},[229,588,256],{"class":238},[229,590,591],{"class":259},"actions\u002Fcache@v4\n",[229,593,594,596],{"class":177,"line":360},[229,595,331],{"class":234},[229,597,239],{"class":238},[229,599,600,603,605],{"class":177,"line":366},[229,601,602],{"class":234},"          path",[229,604,256],{"class":238},[229,606,607],{"class":259},"sites\u002F${{ matrix.site }}\u002Fnode_modules\u002F.astro\n",[229,609,610,613,615],{"class":177,"line":372},[229,611,612],{"class":234},"          key",[229,614,256],{"class":238},[229,616,617],{"class":259},"${{ matrix.site }}-assets-${{ github.sha }}\n",[229,619,620,623,625],{"class":177,"line":378},[229,621,622],{"class":234},"          restore-keys",[229,624,256],{"class":238},[229,626,627],{"class":259},"${{ matrix.site }}-assets-\n",[229,629,630,632,635,637],{"class":177,"line":384},[229,631,293],{"class":238},[229,633,634],{"class":234},"run",[229,636,256],{"class":238},[229,638,639],{"class":259},"npm ci\n",[229,641,642,644,646,648],{"class":177,"line":390},[229,643,293],{"class":238},[229,645,634],{"class":234},[229,647,256],{"class":238},[229,649,650],{"class":259},"npm run build --workspace sites\u002F${{ matrix.site }}\n",[229,652,653,655,657,659],{"class":177,"line":395},[229,654,293],{"class":238},[229,656,296],{"class":234},[229,658,256],{"class":238},[229,660,661],{"class":259},"actions\u002Fupload-artifact@v4\n",[229,663,664,666],{"class":177,"line":400},[229,665,331],{"class":234},[229,667,239],{"class":238},[229,669,670,673,675],{"class":177,"line":406},[229,671,672],{"class":234},"          name",[229,674,256],{"class":238},[229,676,677],{"class":259},"site-${{ matrix.site }}\n",[229,679,680,682,684],{"class":177,"line":412},[229,681,602],{"class":234},[229,683,256],{"class":238},[229,685,686],{"class":259},"sites\u002F${{ matrix.site }}\u002Fdist\n",[14,688,689],{},"Three details make this work well:",[32,691,692,706,714],{},[35,693,694,701,702,705],{},[695,696,427,697,700],"strong",{},[39,698,699],{},"if"," guard."," A matrix built from an empty list is an error in GitHub Actions. When a change touches only the README, the list is ",[39,703,704],{},"[]"," and the build job is skipped instead of failing.",[35,707,708,713],{},[695,709,710,25],{},[39,711,712],{},"fail-fast: false"," A broken blog build should not cancel the docs build; each site reports its own result.",[35,715,716,719],{},[695,717,718],{},"Per-site cache keys."," Each site gets its own asset cache, so the docs site's image cache is never overwritten by the blog's.",[27,721,723],{"id":722},"step-3-one-required-check","Step 3: One Required Check",[14,725,726,727,42,730,733],{},"Branch protection needs stable check names, but matrix jobs are named ",[39,728,729],{},"build (docs)",[39,731,732],{},"build (blog)"," and so on, and a skipped matrix produces no jobs at all. Add a summary job and make it the only required check:",[67,735,737],{"className":223,"code":736,"language":225,"meta":73,"style":73},"  ci-ok:\n    needs: [changes, build]\n    if: always()\n    runs-on: ubuntu-latest\n    steps:\n      - run: |\n          result=\"${{ needs.build.result }}\"\n          if [ \"$result\" = \"failure\" ] || [ \"$result\" = \"cancelled\" ]; then exit 1; fi\n",[39,738,739,746,763,772,780,786,796,801],{"__ignoreMap":73},[229,740,741,744],{"class":177,"line":231},[229,742,743],{"class":234},"  ci-ok",[229,745,239],{"class":238},[229,747,748,750,753,755,757,760],{"class":177,"line":242},[229,749,467],{"class":234},[229,751,752],{"class":238},": [",[229,754,430],{"class":259},[229,756,42],{"class":238},[229,758,759],{"class":259},"build",[229,761,762],{"class":238},"]\n",[229,764,765,767,769],{"class":177,"line":250},[229,766,477],{"class":234},[229,768,256],{"class":238},[229,770,771],{"class":259},"always()\n",[229,773,774,776,778],{"class":177,"line":263},[229,775,253],{"class":234},[229,777,256],{"class":238},[229,779,260],{"class":259},[229,781,782,784],{"class":177,"line":271},[229,783,285],{"class":234},[229,785,239],{"class":238},[229,787,788,790,792,794],{"class":177,"line":282},[229,789,293],{"class":238},[229,791,634],{"class":234},[229,793,256],{"class":238},[229,795,345],{"class":344},[229,797,798],{"class":177,"line":290},[229,799,800],{"class":259},"          result=\"${{ needs.build.result }}\"\n",[229,802,803],{"class":177,"line":304},[229,804,805],{"class":259},"          if [ \"$result\" = \"failure\" ] || [ \"$result\" = \"cancelled\" ]; then exit 1; fi\n",[14,807,808,811,812,814],{},[39,809,810],{},"if: always()"," makes it run even when ",[39,813,759],{}," was skipped or failed. It passes when every affected site built, or when no site was affected, and fails otherwise.",[77,816,817,908],{},[80,818,88,823,88,826,88,829,88,831,88,838],{"viewBox":819,"role":83,"ariaLabelledBy":820,"xmlns":87},"0 0 760 240",[821,822],"mxb-graph-title","mxb-graph-desc",[90,824,825],{"id":821},"Job graph for a pull request that touches docs and marketing",[94,827,828],{"id":822},"The changes job outputs docs and marketing. The build matrix creates two parallel jobs, build docs and build marketing; blog is not built. The ci-ok summary job waits for both and is the only required status check.",[98,830],{"x":100,"y":100,"width":101,"height":179,"fill":103},[105,832,107,833,88],{},[109,834,836],{"id":835,"viewBox":112,"refX":113,"refY":114,"markerWidth":115,"markerHeight":115,"orient":116},"mxb-graph-arrow",[118,837],{"d":120,"fill":121},[123,839,107,840,107,843,107,849,107,852,107,855,107,858,107,861,107,864,107,868,107,873,107,877,107,881,107,885,107,888,107,894,107,898,107,902,107,904,88],{"style":125},[72,841,842],{"x":128,"y":129,"fill":130,"style":131},"One pull request, two affected sites",[98,844],{"x":845,"y":846,"width":847,"height":848,"rx":139,"fill":140,"style":141,"stroke":140},"30","96","150","50",[72,850,430],{"x":851,"y":166,"fill":130,"style":145},"105",[72,853,434],{"x":851,"y":854,"fill":121,"style":204},"136",[98,856],{"x":857,"y":848,"width":158,"height":138,"rx":139,"fill":159,"style":141,"stroke":159},"290",[72,859,729],{"x":128,"y":860,"fill":130,"style":145},"77",[98,862],{"x":857,"y":863,"width":158,"height":138,"rx":139,"fill":159,"style":141,"stroke":159},"148",[72,865,867],{"x":128,"y":866,"fill":130,"style":145},"175","build (marketing)",[98,869],{"x":857,"y":870,"width":158,"height":871,"rx":139,"fill":103,"stroke":121,"style":872},"102","36","stroke-dasharray:4 3",[72,874,876],{"x":128,"y":875,"fill":121,"style":145},"125","blog: not built",[98,878],{"x":879,"y":846,"width":847,"height":848,"rx":139,"fill":880,"style":141,"stroke":880},"580","#3f6410",[72,882,884],{"x":883,"y":166,"fill":130,"style":145},"655","ci-ok",[72,886,887],{"x":883,"y":854,"fill":880,"style":204},"required check",[177,889],{"x1":158,"y1":890,"x2":891,"y2":892,"stroke":121,"style":893},"112","286","74","stroke-width:1.5px;marker-end:url(#mxb-graph-arrow)",[177,895],{"x1":158,"y1":896,"x2":891,"y2":897,"stroke":121,"style":893},"130","168",[177,899],{"x1":900,"y1":892,"x2":901,"y2":890,"stroke":121,"style":893},"470","576",[177,903],{"x1":900,"y1":897,"x2":901,"y2":896,"stroke":121,"style":893},[72,905,907],{"x":128,"y":906,"fill":121,"style":204},"226","branch protection sees one stable check name whatever the matrix contains",[207,909,910],{},"The summary job turns a variable set of matrix jobs into one stable status.",[14,912,913],{},"The same pattern works for any number of sites. When a fourth site is added to the repository, it needs a filter entry and a deploy environment; the required check, branch protection and the rest of the workflow stay as they are. That is the main reason to avoid listing matrix job names in branch protection: every new site or rename would otherwise need an administrator to update the repository settings, and a forgotten update either blocks all merges or silently stops requiring the new site's build.",[27,915,917],{"id":916},"step-4-deploy-what-changed","Step 4: Deploy What Changed",[14,919,920,921,924,925,928],{},"Deployment follows the same matrix. A deploy job with the same ",[39,922,923],{},"matrix.site"," and ",[39,926,927],{},"needs: build"," downloads the matching artifact and deploys it to that site's target, using an environment per site so each has its own secrets and protection rules:",[67,930,932],{"className":223,"code":931,"language":225,"meta":73,"style":73},"  deploy:\n    needs: [changes, build]\n    if: github.ref == 'refs\u002Fheads\u002Fmain' && needs.changes.outputs.sites != '[]'\n    strategy:\n      matrix:\n        site: ${{ fromJSON(needs.changes.outputs.sites) }}\n    environment: ${{ matrix.site }}-production\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fdownload-artifact@v4\n        with: { name: 'site-${{ matrix.site }}', path: dist }\n      - run: .\u002Fscripts\u002Fdeploy.sh ${{ matrix.site }} dist\n",[39,933,934,941,955,964,970,976,984,994,1002,1008,1019,1044],{"__ignoreMap":73},[229,935,936,939],{"class":177,"line":231},[229,937,938],{"class":234},"  deploy",[229,940,239],{"class":238},[229,942,943,945,947,949,951,953],{"class":177,"line":242},[229,944,467],{"class":234},[229,946,752],{"class":238},[229,948,430],{"class":259},[229,950,42],{"class":238},[229,952,759],{"class":259},[229,954,762],{"class":238},[229,956,957,959,961],{"class":177,"line":250},[229,958,477],{"class":234},[229,960,256],{"class":238},[229,962,963],{"class":259},"github.ref == 'refs\u002Fheads\u002Fmain' && needs.changes.outputs.sites != '[]'\n",[229,965,966,968],{"class":177,"line":263},[229,967,495],{"class":234},[229,969,239],{"class":238},[229,971,972,974],{"class":177,"line":271},[229,973,513],{"class":234},[229,975,239],{"class":238},[229,977,978,980,982],{"class":177,"line":282},[229,979,520],{"class":234},[229,981,256],{"class":238},[229,983,525],{"class":259},[229,985,986,989,991],{"class":177,"line":290},[229,987,988],{"class":234},"    environment",[229,990,256],{"class":238},[229,992,993],{"class":259},"${{ matrix.site }}-production\n",[229,995,996,998,1000],{"class":177,"line":304},[229,997,253],{"class":234},[229,999,256],{"class":238},[229,1001,260],{"class":259},[229,1003,1004,1006],{"class":177,"line":317},[229,1005,285],{"class":234},[229,1007,239],{"class":238},[229,1009,1010,1012,1014,1016],{"class":177,"line":328},[229,1011,293],{"class":238},[229,1013,296],{"class":234},[229,1015,256],{"class":238},[229,1017,1018],{"class":259},"actions\u002Fdownload-artifact@v4\n",[229,1020,1021,1023,1025,1028,1030,1033,1035,1037,1039,1042],{"class":177,"line":336},[229,1022,331],{"class":234},[229,1024,559],{"class":238},[229,1026,1027],{"class":234},"name",[229,1029,256],{"class":238},[229,1031,1032],{"class":259},"'site-${{ matrix.site }}'",[229,1034,42],{"class":238},[229,1036,118],{"class":234},[229,1038,256],{"class":238},[229,1040,1041],{"class":259},"dist",[229,1043,580],{"class":238},[229,1045,1046,1048,1050,1052],{"class":177,"line":348},[229,1047,293],{"class":238},[229,1049,634],{"class":234},[229,1051,256],{"class":238},[229,1053,1054],{"class":259},".\u002Fscripts\u002Fdeploy.sh ${{ matrix.site }} dist\n",[14,1056,1057],{},"Sites that did not change are not redeployed, so their CDN caches stay warm and their deploy history stays meaningful. It also makes rollbacks simpler: when the blog breaks, its deploy history contains only blog changes, and rolling it back cannot accidentally revert an unrelated docs release that went out in the same merge. Give each site's environment its own protection rules, so a marketing launch can require approval from the marketing lead without slowing down documentation fixes.",[77,1059,1060,1127],{},[80,1061,88,1066,88,1069,88,1072,88,1075],{"viewBox":1062,"role":83,"ariaLabelledBy":1063,"xmlns":87},"0 0 760 250",[1064,1065],"mxb-time-title","mxb-time-desc",[90,1067,1068],{"id":1064},"CI minutes per pull request before and after the dynamic matrix",[94,1070,1071],{"id":1065},"Before, every pull request built all three sites sequentially for 14 minutes of runner time and 14 minutes wall clock. After, a typical single-site pull request used 4 minutes of runner time and 4.5 minutes wall clock; a shared package change used 11 minutes of runner time but only 5 minutes wall clock because sites built in parallel.",[98,1073],{"x":100,"y":100,"width":101,"height":1074,"fill":103},"250",[123,1076,107,1077,107,1081,107,1085,107,1092,107,1097,107,1102,107,1106,107,1111,107,1115,107,1118,107,1123,88],{"style":125},[72,1078,1080],{"x":128,"y":1079,"fill":130,"style":131},"28","Wall-clock time per pull request (minutes)",[72,1082,1084],{"x":1083,"y":892,"fill":130},"117","before: all sites, one job",[98,1086],{"x":1074,"y":1087,"width":1088,"height":1089,"fill":1090,"style":1091},"62","420","20","#d83b41","fill-opacity:0.45",[72,1093,1096],{"x":1094,"y":860,"fill":130,"style":1095},"662","text-anchor:end","14",[72,1098,1101],{"x":1099,"y":1100,"fill":130},"121","124","after: one site changed",[98,1103],{"x":1074,"y":890,"width":1104,"height":1089,"fill":880,"style":1105},"135","fill-opacity:0.5",[72,1107,1110],{"x":1108,"y":1109,"fill":130},"393","127","4.5",[72,1112,1114],{"x":135,"y":1113,"fill":130},"174","after: shared package changed",[98,1116],{"x":1074,"y":1117,"width":847,"height":1089,"fill":159,"style":1091},"162",[72,1119,1122],{"x":1120,"y":1121,"fill":130},"408","177","5 (3 sites in parallel)",[72,1124,1126],{"x":128,"y":1125,"fill":121,"style":204},"222","82% of pull requests touched a single site",[207,1128,1129],{},"Most pull requests only pay for one site; shared changes pay for several, in parallel.",[27,1131,1133],{"id":1132},"keeping-the-map-honest","Keeping the Map Honest",[14,1135,1136,1137,1139],{},"The path filters are a dependency map written by hand, and hand-written maps drift. A site starts importing ",[39,1138,153],{}," and nobody adds the path to its filter, so a UI change silently skips that site's build. Two safeguards help:",[1141,1142,1143,1149],"ol",{},[35,1144,1145,1148],{},[695,1146,1147],{},"A nightly full build."," A scheduled workflow that builds every site regardless of changes catches anything the filters missed within a day.",[35,1150,1151,1154,1155,25],{},[695,1152,1153],{},"Derive filters from the workspace graph."," Tools such as Turborepo and Nx know which packages each site depends on; using their affected commands removes the hand-written map entirely. See ",[21,1156,1158],{"href":1157},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fremote-caching-with-turborepo-for-ssg-monorepos\u002F","Remote Caching with Turborepo for SSG Monorepos",[27,1160,1162],{"id":1161},"measured-impact","Measured Impact",[14,1164,1165],{},"A company with three sites — Astro docs, an Eleventy blog and an Astro marketing site — in one repository moved from a single job that built everything to the dynamic matrix. With 82% of pull requests touching one site, median wall-clock CI time fell from 14 to 4.5 minutes and monthly runner minutes fell by 61%. Shared package changes built all three sites in parallel in about five minutes. Unnecessary production deploys, previously three per merge, dropped to the one site that changed.",[27,1167,1169],{"id":1168},"pitfalls-rollback","Pitfalls & Rollback",[32,1171,1172,1181,1191,1197,1203],{},[35,1173,1174,1177,1178,1180],{},[695,1175,1176],{},"Empty matrix."," Always guard with an ",[39,1179,699],{}," on the list.",[35,1182,1183,1186,1187,1190],{},[695,1184,1185],{},"Push events with no base."," On the first push of a new branch, path filters may compare against the default branch; check ",[39,1188,1189],{},"base"," settings for push events.",[35,1192,1193,1196],{},[695,1194,1195],{},"Drifted filters."," Add the nightly full build.",[35,1198,1199,1202],{},[695,1200,1201],{},"Required matrix jobs."," Require the summary job, never the individual matrix entries.",[35,1204,1205,1208],{},[695,1206,1207],{},"Rollback:"," replace the matrix with a static list of all sites; everything builds again, correctly if slowly.",[27,1210,1212],{"id":1211},"conclusion","Conclusion",[14,1214,1215],{},"In a multi-site monorepo, building everything on every change wastes time and produces deploys nobody needs. Compute the affected sites from changed paths, build and deploy them with a dynamic matrix, keep per-site caches and environments, and gate merges on a single summary check. Back the path map with a nightly full build or derive it from the workspace graph, and CI time tracks the size of the change rather than the size of the repository.",[27,1217,1219],{"id":1218},"faq","FAQ",[1221,1222,1224],"h3",{"id":1223},"what-is-a-dynamic-matrix-in-github-actions","What is a dynamic matrix in GitHub Actions?",[14,1226,1227],{},"A matrix whose values are produced at run time by an earlier job instead of written in the workflow file. A first job outputs a JSON list, for example the sites affected by a change, and the build job uses fromJSON on that output as its matrix, creating one job per list entry.",[1221,1229,1231],{"id":1230},"how-do-i-detect-which-sites-a-change-affects","How do I detect which sites a change affects?",[14,1233,1234],{},"Compare the changed files against each site's directory and against shared directories. A change inside sites\u002Fdocs affects only docs; a change to packages\u002Fui or the lockfile affects every site that depends on them. dorny\u002Fpaths-filter or a workspace tool's affected command can compute this.",[1221,1236,1238],{"id":1237},"what-happens-when-no-site-is-affected","What happens when no site is affected?",[14,1240,1241],{},"The matrix would be empty, and GitHub Actions fails a job whose matrix is empty. Guard the build job with an if condition that checks the list is not empty, so the workflow succeeds without building anything.",[1221,1243,1245],{"id":1244},"how-do-i-make-a-matrix-build-a-required-status-check","How do I make a matrix build a required status check?",[14,1247,1248],{},"Matrix job names change with their values, which makes them awkward as required checks. Add a final summary job that needs the matrix job and always runs, fails if any matrix entry failed, and make that single job the required check.",[27,1250,1252],{"id":1251},"related","Related",[32,1254,1255,1264,1271,1276,1283],{},[35,1256,1257,1260,1261,1263],{},[695,1258,1259],{},"Parent:"," ",[21,1262,24],{"href":23}," — every workflow pattern.",[35,1265,1266,1270],{},[21,1267,1269],{"href":1268},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions\u002F","Building Astro Sites with GitHub Actions"," — the single-site workflow each matrix entry runs.",[35,1272,1273,1275],{},[21,1274,1158],{"href":1157}," — graph-aware affected detection.",[35,1277,1278,1282],{},[21,1279,1281],{"href":1280},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-multiple-environments-from-one-workflow\u002F","Deploying to Multiple Environments From One Workflow"," — environments and approvals.",[35,1284,1285,1289],{},[21,1286,1288],{"href":1287},"\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"," — keeping per-site caches warm.",[1291,1292,1293],"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 pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}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":73,"searchDepth":242,"depth":242,"links":1295},[1296,1297,1298,1299,1300,1301,1302,1303,1304,1305,1306,1312],{"id":29,"depth":242,"text":30},{"id":61,"depth":242,"text":62},{"id":212,"depth":242,"text":213},{"id":446,"depth":242,"text":447},{"id":722,"depth":242,"text":723},{"id":916,"depth":242,"text":917},{"id":1132,"depth":242,"text":1133},{"id":1161,"depth":242,"text":1162},{"id":1168,"depth":242,"text":1169},{"id":1211,"depth":242,"text":1212},{"id":1218,"depth":242,"text":1219,"children":1307},[1308,1309,1310,1311],{"id":1223,"depth":250,"text":1224},{"id":1230,"depth":250,"text":1231},{"id":1237,"depth":250,"text":1238},{"id":1244,"depth":250,"text":1245},{"id":1251,"depth":242,"text":1252},[1314,1317,1320,1321],{"name":1315,"item":1316},"Home","\u002F",{"name":1318,"item":1319},"Production-Ready Deployment & CI\u002FCD Workflows","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":24,"item":23},{"name":5,"item":1322},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos\u002F","2026-09-18","Build and deploy only the sites a change affects in a monorepo, using a dynamic GitHub Actions matrix generated from changed paths, with per-site caches.","md",[1327,1328,1329,1330],{"q":1224,"a":1227},{"q":1231,"a":1234},{"q":1238,"a":1241},{"q":1245,"a":1248},{},true,"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos",{"title":5,"description":1324},"production-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos\u002Findex","article","6qL_4r9SKegXhKcXpIz6pKqUQk_1xctBy8uw2wNtlcY",[1339,1342,1345,1348,1351,1354,1357,1360,1363,1366,1369,1372,1375,1378,1381,1384,1387,1390,1393,1396,1399,1402,1405,1408,1411,1414,1417,1420,1423,1426,1429,1432,1435,1438,1441,1444,1447,1450,1453,1456,1459,1462,1465,1468,1471,1474,1477,1480,1483,1486,1489,1492,1495,1498,1501,1504,1507,1510,1513,1516,1519,1522,1525,1528,1531,1534,1537,1540,1543,1546,1549,1552,1555,1558,1561,1564,1567,1570,1573,1576,1579,1582,1585,1588,1591,1594,1597,1600,1603,1606,1609,1612,1615,1618,1621,1624,1627,1630,1633,1636,1639,1642,1645,1648,1651,1654,1657,1660,1663,1666,1669,1672,1675,1678,1681,1684,1687,1690,1693,1696,1699,1702,1705,1708,1711,1714,1717,1720,1723,1726,1729,1732,1735,1738,1741,1744,1747,1750,1753,1756,1759,1762,1765,1768,1771,1774,1777,1780,1783,1786,1789,1792,1795,1798,1801,1804,1807,1810,1813,1816,1819,1822,1825,1828,1831,1834,1837,1840,1843,1846,1849,1852,1855,1858,1861,1864,1867,1870,1873,1876,1879,1882,1885,1888,1891,1894,1897,1900,1903,1906,1909,1912,1915,1918,1921,1924,1927,1930,1933,1936,1939,1942,1945,1948,1951,1954,1957,1960,1963,1966,1969,1972,1975,1978,1981,1984,1987,1990,1993,1996,1999,2002,2005,2008,2011,2014,2017,2020,2023,2026,2029,2032,2035,2038,2041,2044,2047,2050,2053,2056,2059,2062,2065,2068,2071,2074,2077,2080,2083,2086,2089,2092,2095,2098,2101,2104,2107,2110,2113,2116,2119,2122,2125,2128,2131,2134,2137,2140,2143,2146,2148,2151,2154,2157,2159,2162,2165,2167,2168,2171,2174,2177,2180,2183,2186,2189,2192,2195,2198,2201,2204,2206,2208,2211,2214,2217,2220,2223,2226,2229,2232,2235,2238,2241,2244,2247,2250,2253,2256,2259,2262,2265,2268,2271,2274,2277,2280,2283,2286,2289,2292,2295,2298,2301,2304,2307,2310,2313,2316,2319,2322,2325,2328,2331,2334,2337,2340,2343,2346,2349,2352,2355,2358,2361,2364,2367,2370,2373,2376,2379,2382,2385,2388,2391,2394,2397,2400,2403,2406,2409,2412,2415,2418,2421,2424,2427,2430,2433,2436,2439,2442,2445,2448,2451,2454,2457,2460,2463,2466,2469,2472,2475,2478],{"path":1340,"title":1341},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-code-blocks-in-documentation-sites","Accessible Code Blocks in Documentation Sites",{"path":1343,"title":1344},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-dark-mode-toggles-for-static-sites","Accessible Dark Mode Toggles for Static Sites",{"path":1346,"title":1347},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-svg-diagrams-on-static-sites","Accessible SVG Diagrams on Static Sites",{"path":1349,"title":1350},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fenforcing-alt-text-for-markdown-images-at-build-time","Enforcing Alt Text for Markdown Images at Build Time",{"path":1352,"title":1353},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content","Fixing Heading Order Problems in Markdown Content",{"path":1355,"title":1356},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-low-color-contrast-flagged-by-lighthouse","Fixing Low Color Contrast Flagged by Lighthouse",{"path":1358,"title":1359},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1361,"title":1362},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fkeyboard-navigation-and-focus-order-on-static-sites","Keyboard Navigation and Focus Order on Static Sites",{"path":1364,"title":1365},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fskip-links-and-landmarks-in-ssg-layouts","Skip Links and Landmarks in SSG Layouts",{"path":1367,"title":1368},"\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":1370,"title":1371},"\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":1373,"title":1374},"\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":1376,"title":1377},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fdev-server-performance-astro-vs-eleventy","Dev Server Performance: Astro vs Eleventy",{"path":1379,"title":1380},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-astro-build-errors-after-upgrading-to-astro-5","Fixing Astro Build Errors After Upgrading to Astro 5",{"path":1382,"title":1383},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-duplicate-permalink-errors-in-eleventy","Fixing Duplicate Permalink Errors in Eleventy",{"path":1385,"title":1386},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-eleventy-out-of-memory-errors-on-large-collections","Fixing Eleventy Out-of-Memory Errors on Large Collections",{"path":1388,"title":1389},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Ffixing-slow-astro-builds-caused-by-large-mdx-collections","Fixing Slow Astro Builds Caused by Large MDX Collections",{"path":1391,"title":1392},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1394,"title":1395},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Floading-remote-content-with-astro-content-layer-loaders","Loading Remote Content With Astro Content Layer Loaders",{"path":1397,"title":1398},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fmarkdown-pipelines-remark-vs-markdown-it","Markdown Pipelines: remark vs markdown-it",{"path":1400,"title":1401},"\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":1403,"title":1404},"\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":1406,"title":1407},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fsyntax-highlighting-with-shiki-in-astro-and-eleventy","Syntax Highlighting with Shiki in Astro and Eleventy",{"path":1409,"title":1410},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fupgrading-eleventy-2-to-3-with-esm-configuration","Upgrading Eleventy 2 to 3 With ESM Configuration",{"path":1412,"title":1413},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fadding-local-search-to-a-vitepress-site","Adding Local Search to a VitePress Site",{"path":1415,"title":1416},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1418,"title":1419},"\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":1421,"title":1422},"\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":1424,"title":1425},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Ffixing-broken-links-reported-by-docusaurus-builds","Fixing Broken Links Reported by Docusaurus Builds",{"path":1427,"title":1428},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fgenerating-api-reference-pages-in-starlight-from-openapi","Generating API Reference Pages in Starlight From OpenAPI",{"path":1430,"title":1431},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1433,"title":1434},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1436,"title":1437},"\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":1439,"title":1440},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1442,"title":1443},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1445,"title":1446},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fspeeding-up-docusaurus-builds-with-rspack","Speeding Up Docusaurus Builds With Rspack",{"path":1448,"title":1449},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1451,"title":1452},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioning-vitepress-documentation-without-a-plugin","Versioning VitePress Documentation Without a Plugin",{"path":1454,"title":1455},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1457,"title":1458},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-vs-starlight-for-vue-and-astro-teams","VitePress vs Starlight for Vue and Astro Teams",{"path":1460,"title":1461},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Ffixing-hugo-builds-that-fail-after-a-version-upgrade","Fixing Hugo Builds That Fail After a Version Upgrade",{"path":1463,"title":1464},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Ffixing-hugo-builds-that-slow-down-after-adding-taxonomies","Fixing Hugo Builds That Slow Down After Adding Taxonomies",{"path":1466,"title":1467},"\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":1469,"title":1470},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-image-processing-cache-in-ci","Hugo Image Processing Cache in CI",{"path":1472,"title":1473},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fhugo-modules-and-dependency-caching","Hugo Modules and Dependency Caching",{"path":1475,"title":1476},"\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":1478,"title":1479},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1481,"title":1482},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fparallel-hugo-builds-across-ci-jobs","Parallel Hugo Builds Across CI Jobs",{"path":1484,"title":1485},"\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":1487,"title":1488},"\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":1490,"title":1491},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fsharing-a-theme-across-hugo-sites-with-modules","Sharing a Theme Across Hugo Sites With Modules",{"path":1493,"title":1494},"\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":1496,"title":1497},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories\u002Fsplitting-large-hugo-sites-with-segments","Splitting Large Hugo Sites with Segments",{"path":1499,"title":1500},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1502,"title":1503},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Ffixing-hreflang-errors-reported-in-search-console","Fixing Hreflang Errors Reported in Search Console",{"path":1505,"title":1506},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fhreflang-and-language-alternates-on-static-sites","hreflang and Language Alternates on Static Sites",{"path":1508,"title":1509},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1511,"title":1512},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1514,"title":1515},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Flanguage-detection-and-redirects-at-the-edge","Language Detection and Redirects at the Edge",{"path":1517,"title":1518},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-eleventy-sites-with-the-i18n-plugin","Multilingual Eleventy Sites With the i18n Plugin",{"path":1520,"title":1521},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1523,"title":1524},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fright-to-left-layouts-on-static-sites","Right-to-Left Layouts on Static Sites",{"path":1526,"title":1527},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fsubdirectories-vs-subdomains-for-translated-static-sites","Subdirectories vs Subdomains for Translated Static Sites",{"path":1529,"title":1530},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Ftranslation-workflows-with-git-and-crowdin","Translation Workflows with Git and Crowdin",{"path":1532,"title":1533},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fcustom-domains-and-https-for-jekyll-on-github-pages","Custom Domains and HTTPS for Jekyll on GitHub Pages",{"path":1535,"title":1536},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1538,"title":1539},"\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":1541,"title":1542},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Ffixing-jekyll-builds-that-break-after-a-ruby-upgrade","Fixing Jekyll Builds That Break After a Ruby Upgrade",{"path":1544,"title":1545},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1547,"title":1548},"\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":1550,"title":1551},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-in-docker-for-reproducible-builds","Running Jekyll in Docker for Reproducible Builds",{"path":1553,"title":1554},"\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":1556,"title":1557},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1559,"title":1560},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1562,"title":1563},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fauditing-content-parity-after-a-migration","Auditing Content Parity After a Migration",{"path":1565,"title":1566},"\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":1568,"title":1569},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1571,"title":1572},"\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":1574,"title":1575},"\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":1577,"title":1578},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-a-wordpress-export-to-eleventy","Migrating a WordPress Export to Eleventy",{"path":1580,"title":1581},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1583,"title":1584},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1586,"title":1587},"\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":1589,"title":1590},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-nextjs-pages-router-to-astro","Migrating from Next.js Pages Router to Astro",{"path":1592,"title":1593},"\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":1595,"title":1596},"\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":1598,"title":1599},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Frecovering-search-traffic-lost-after-a-generator-migration","Recovering Search Traffic Lost After a Generator Migration",{"path":1601,"title":1602},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Freplacing-gatsby-graphql-queries-during-a-migration","Replacing Gatsby GraphQL Queries During a Migration",{"path":1604,"title":1605},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ffixing-404s-on-refresh-in-nextjs-static-export","Fixing 404s on Refresh in Next.js Static Export",{"path":1607,"title":1608},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fgenerating-sitemaps-and-rss-in-nextjs-static-export","Generating Sitemaps and RSS in Next.js Static Export",{"path":1610,"title":1611},"\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":1613,"title":1614},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1616,"title":1617},"\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":1619,"title":1620},"\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":1622,"title":1623},"\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":1625,"title":1626},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fnextjs-static-export-vs-gatsby-for-existing-react-sites","Next.js Static Export vs Gatsby for Existing React Sites",{"path":1628,"title":1629},"\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":1631,"title":1632},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Ftrailing-slash-and-basepath-in-nextjs-static-export","Trailing Slash and basePath in Next.js Static Export",{"path":1634,"title":1635},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites\u002Fusing-mdx-in-nextjs-static-export","Using MDX in Next.js Static Export",{"path":1637,"title":1638},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Faccessible-search-ui-for-static-sites","Accessible Search UI for Static Sites",{"path":1640,"title":1641},"\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":1643,"title":1644},"\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":1646,"title":1647},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1649,"title":1650},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ffixing-missing-results-in-pagefind-indexes","Fixing Missing Results in Pagefind Indexes",{"path":1652,"title":1653},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1655,"title":1656},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1658,"title":1659},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1661,"title":1662},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1664,"title":1665},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-lunr-for-small-documentation-sites","Pagefind vs Lunr for Small Documentation Sites",{"path":1667,"title":1668},"\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":1670,"title":1671},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fself-hosting-typesense-for-a-static-site","Self-Hosting Typesense for a Static Site",{"path":1673,"title":1674},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1676,"title":1677},"\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":1679,"title":1680},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fchoosing-an-ssg-for-a-marketing-site-with-non-technical-editors","Choosing an SSG for a Marketing Site with Non-Technical Editors",{"path":1682,"title":1683},"\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":1685,"title":1686},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1688,"title":1689},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fgatsby-vs-astro-for-content-sites-in-2026","Gatsby vs Astro for Content Sites in 2026",{"path":1691,"title":1692},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1694,"title":1695},"\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":1697,"title":1698},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fscoring-ssg-long-term-maintenance-risk","Scoring SSG Long-Term Maintenance Risk",{"path":1700,"title":1701},"\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":1703,"title":1704},"\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":1706,"title":1707},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fwhen-a-static-site-generator-is-the-wrong-choice","When a Static Site Generator Is the Wrong Choice",{"path":1709,"title":1710},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fadding-json-ld-structured-data-at-build-time","Adding JSON-LD Structured Data at Build Time",{"path":1712,"title":1713},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fcanonical-urls-and-duplicate-content-on-static-sites","Canonical URLs and Duplicate Content on Static Sites",{"path":1715,"title":1716},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Ffixing-pages-crawled-but-not-indexed-on-static-sites","Fixing Pages Crawled but Not Indexed on Static Sites",{"path":1718,"title":1719},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Ffixing-soft-404s-on-static-hosts","Fixing Soft 404s on Static Hosts",{"path":1721,"title":1722},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fgenerating-breadcrumb-structured-data-in-astro","Generating Breadcrumb Structured Data in Astro",{"path":1724,"title":1725},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fgenerating-sitemaps-for-large-static-sites","Generating Sitemaps for Large Static Sites",{"path":1727,"title":1728},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1730,"title":1731},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Frobots-txt-and-noindex-for-preview-and-staging","robots.txt and noindex for Preview and Staging",{"path":1733,"title":1734},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Frss-and-atom-feeds-for-static-blogs","RSS and Atom Feeds for Static Blogs",{"path":1736,"title":1737},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites\u002Fseo-safe-pagination-and-tag-pages","SEO-Safe Pagination and Tag Pages",{"path":1739,"title":1740},"\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":1742,"title":1743},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-for-static-sites-in-nginx","Cache-Control Headers for Static Sites in Nginx",{"path":1745,"title":1746},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-on-s3-and-cloudfront","Cache-Control Headers on S3 and CloudFront",{"path":1748,"title":1749},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-on-vercel-for-static-sites","Cache-Control Headers on Vercel for Static Sites",{"path":1751,"title":1752},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-keys-and-query-strings-on-cdns","Cache Keys and Query Strings on CDNs",{"path":1754,"title":1755},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcaching-404s-and-redirects-at-the-edge","Caching 404s and Redirects at the Edge",{"path":1757,"title":1758},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcloudflare-vs-cloudfront-cache-hit-ratios-for-static-sites","Cloudflare vs CloudFront Cache Hit Ratios for Static Sites",{"path":1760,"title":1761},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ffixing-stale-html-after-deploys-on-cloudflare","Fixing Stale HTML After Deploys on Cloudflare",{"path":1763,"title":1764},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1766,"title":1767},"\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":1769,"title":1770},"\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":1772,"title":1773},"\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":1775,"title":1776},"\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":1778,"title":1779},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1781,"title":1782},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fcode-splitting-and-module-preload-in-vite-based-ssgs","Code Splitting and Module Preload in Vite-Based SSGs",{"path":1784,"title":1785},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ffixing-missing-tailwind-classes-in-production-builds","Fixing Missing Tailwind Classes in Production Builds",{"path":1787,"title":1788},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ffixing-unused-javascript-warnings-on-static-pages","Fixing Unused JavaScript Warnings on Static Pages",{"path":1790,"title":1791},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":1793,"title":1794},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Finlining-critical-css-on-static-sites","Inlining Critical CSS on Static Sites",{"path":1796,"title":1797},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fkeeping-tailwind-css-output-small-on-static-sites","Keeping Tailwind CSS Output Small on Static Sites",{"path":1799,"title":1800},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fminifying-html-css-and-js-in-eleventy","Minifying HTML, CSS and JS in Eleventy",{"path":1802,"title":1803},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fprecompressing-assets-with-brotli-and-zstd","Precompressing Assets with Brotli and Zstd",{"path":1805,"title":1806},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fpurging-unused-css-with-tailwind-and-lightningcss","Purging Unused CSS with Tailwind and Lightning CSS",{"path":1808,"title":1809},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fsvg-icon-sprites-vs-inline-icons","SVG Icon Sprites vs Inline Icons",{"path":1811,"title":1812},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ftailwind-v4-in-astro-without-postcss-plugins","Tailwind v4 in Astro Without PostCSS Plugins",{"path":1814,"title":1815},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Fcls-from-client-side-rendered-components","CLS from Client-Side Rendered Components",{"path":1817,"title":1818},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Fdebugging-cls-with-the-layout-instability-api","Debugging CLS with the Layout Instability API",{"path":1820,"title":1821},"\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":1823,"title":1824},"\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":1826,"title":1827},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-dynamic-table-of-contents-widgets","Fixing CLS From Dynamic Table of Contents Widgets",{"path":1829,"title":1830},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-images-without-dimensions-in-markdown","Fixing CLS From Images Without Dimensions in Markdown",{"path":1832,"title":1833},"\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":1835,"title":1836},"\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":1838,"title":1839},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1841,"title":1842},"\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":1844,"title":1845},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Freserving-space-for-ad-and-promo-slots","Reserving Space for Ad and Promo Slots",{"path":1847,"title":1848},"\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":1850,"title":1851},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":1853,"title":1854},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffixing-invisible-text-while-web-fonts-load","Fixing Invisible Text While Web Fonts Load",{"path":1856,"title":1857},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1859,"title":1860},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1862,"title":1863},"\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":1865,"title":1866},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1868,"title":1869},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fself-hosted-fonts-vs-google-fonts-for-static-sites","Self-Hosted Fonts vs Google Fonts for Static Sites",{"path":1871,"title":1872},"\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":1874,"title":1875},"\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":1877,"title":1878},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fusing-system-font-stacks-to-skip-webfonts","Using System Font Stacks to Skip Web Fonts",{"path":1880,"title":1881},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":1883,"title":1884},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fart-direction-with-the-picture-element","Art Direction with the Picture Element",{"path":1886,"title":1887},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":1889,"title":1890},"\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":1892,"title":1893},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":1895,"title":1896},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Ffixing-blurry-images-from-astro-assets-resizing","Fixing Blurry Images From astro:assets Resizing",{"path":1898,"title":1899},"\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":1901,"title":1902},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1904,"title":1905},"\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":1907,"title":1908},"\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":1910,"title":1911},"\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":1913,"title":1914},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fserving-astro-images-through-cloudflare-image-resizing","Serving Astro Images Through Cloudflare Image Resizing",{"path":1916,"title":1917},"\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":1919,"title":1920},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1922,"title":1923},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1925,"title":1926},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fbreaking-up-long-tasks-on-static-sites","Breaking Up Long Tasks on Static Sites",{"path":1928,"title":1929},"\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":1931,"title":1932},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Ffixing-hydration-mismatch-errors-in-astro-islands","Fixing Hydration Mismatch Errors in Astro Islands",{"path":1934,"title":1935},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Ffixing-poor-inp-on-static-pages-with-heavy-widgets","Fixing Poor INP on Static Pages With Heavy Widgets",{"path":1937,"title":1938},"\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":1940,"title":1941},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1943,"title":1944},"\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":1946,"title":1947},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":1949,"title":1950},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1952,"title":1953},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":1955,"title":1956},"\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":1958,"title":1959},"\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":1961,"title":1962},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-lcp-regressions-caused-by-cookie-consent-tools","Fixing LCP Regressions Caused by Cookie Consent Tools",{"path":1964,"title":1965},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-lcp-when-the-hero-is-a-background-image","Fixing LCP When the Hero Is a Background Image",{"path":1967,"title":1968},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Ffixing-slow-lcp-on-pages-with-embedded-video","Fixing Slow LCP on Pages With Embedded Video",{"path":1970,"title":1971},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites\u002Fimproving-ttfb-for-static-html","Improving TTFB for Static HTML",{"path":1973,"title":1974},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1976,"title":1977},"\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":1979,"title":1980},"\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":1982,"title":1983},"\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":1985,"title":1986},"\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":1988,"title":1989},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1991,"title":1992},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Flighthouse-ci-vs-webpagetest-for-regression-gates","Lighthouse CI vs WebPageTest for Regression Gates",{"path":1994,"title":1995},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fmeasuring-web-vitals-in-playwright-tests","Measuring Web Vitals in Playwright Tests",{"path":1997,"title":1998},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":2000,"title":2001},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fperformance-testing-on-throttled-mobile-profiles","Performance Testing on Throttled Mobile Profiles",{"path":2003,"title":2004},"\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":2006,"title":2007},"\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":2009,"title":2010},"\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":2012,"title":2013},"\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":2015,"title":2016},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2018,"title":2019},"\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":2021,"title":2022},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2024,"title":2025},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2027,"title":2028},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2030,"title":2031},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffixing-wasted-preloads-flagged-by-chrome","Fixing Wasted Preloads Flagged by Chrome",{"path":2033,"title":2034},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2036,"title":2037},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2039,"title":2040},"\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":2042,"title":2043},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2045,"title":2046},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fview-transitions-in-astro-without-hurting-vitals","View Transitions in Astro Without Hurting Vitals",{"path":2048,"title":2049},"\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":2051,"title":2052},"\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":2054,"title":2055},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Ffacades-for-chat-widgets-and-maps","Facades for Chat Widgets and Maps",{"path":2057,"title":2058},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Ffixing-main-thread-blocking-from-chat-widgets","Fixing Main-Thread Blocking From Chat Widgets",{"path":2060,"title":2061},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2063,"title":2064},"\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":2066,"title":2067},"\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":2069,"title":2070},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fmeasuring-third-party-cost-with-request-blocking","Measuring Third-Party Cost with Request Blocking",{"path":2072,"title":2073},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites\u002Fprivacy-friendly-analytics-compared-by-page-weight","Privacy-Friendly Analytics Compared by Page Weight",{"path":2075,"title":2076},"\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":2078,"title":2079},"\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":2081,"title":2082},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2084,"title":2085},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2087,"title":2088},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2090,"title":2091},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2093,"title":2094},"\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":2096,"title":2097},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-astro-to-cloudflare-workers-static-assets","Deploying Astro to Cloudflare Workers Static Assets",{"path":2099,"title":2100},"\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":2102,"title":2103},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-to-cloudflare-from-github-actions-with-wrangler","Deploying to Cloudflare From GitHub Actions With Wrangler",{"path":2105,"title":2106},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2108,"title":2109},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2111,"title":2112},"\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":2114,"title":2115},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2117,"title":2118},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2120,"title":2121},"\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":2123,"title":2124},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2126,"title":2127},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fgit-based-cms-options-for-static-sites-compared","Git-Based CMS Options for Static Sites Compared",{"path":2129,"title":2130},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2132,"title":2133},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fmanaging-images-in-docs-as-code-repos","Managing Images in Docs-as-Code Repos",{"path":2135,"title":2136},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2138,"title":2139},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2141,"title":2142},"\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":2144,"title":2145},"\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":2147,"title":1269},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions",{"path":2149,"title":2150},"\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":2152,"title":2153},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2155,"title":2156},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2158,"title":1281},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-multiple-environments-from-one-workflow",{"path":2160,"title":2161},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Ffixing-flaky-static-site-builds-in-github-actions","Fixing Flaky Static Site Builds in GitHub Actions",{"path":2163,"title":2164},"\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":2166,"title":24},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds",{"path":1333,"title":5},{"path":2169,"title":2170},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2172,"title":2173},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpublishing-any-generator-to-github-pages-with-actions","Publishing Any Generator to GitHub Pages With Actions",{"path":2175,"title":2176},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2178,"title":2179},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fbuild-caching-on-netlify-and-vercel","Build Caching on Netlify and Vercel",{"path":2181,"title":2182},"\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":2184,"title":2185},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2187,"title":2188},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2190,"title":2191},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Ffixing-stale-pages-from-incremental-builds","Fixing Stale Pages From Incremental Builds",{"path":2193,"title":2194},"\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":2196,"title":2197},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fincremental-rebuild-times-across-astro-eleventy-and-hugo","Incremental Rebuild Times Across Astro, Eleventy and Hugo",{"path":2199,"title":2200},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2202,"title":2203},"\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":2205,"title":1158},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fremote-caching-with-turborepo-for-ssg-monorepos",{"path":2207,"title":1288},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fsharing-build-cache-across-ci-runners",{"path":2209,"title":2210},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":2212,"title":2213},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2215,"title":2216},"\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":2218,"title":2219},"\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":2221,"title":2222},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ffinding-the-cause-of-a-sudden-field-lcp-drop","Finding the Cause of a Sudden Field LCP Drop",{"path":2224,"title":2225},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2227,"title":2228},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2230,"title":2231},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2233,"title":2234},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Freal-user-error-tracking-on-static-sites","Real-User Error Tracking on Static Sites",{"path":2236,"title":2237},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2239,"title":2240},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2242,"title":2243},"\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":2245,"title":2246},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fbandwidth-pricing-for-static-sites-across-netlify-vercel-and-cloudflare","Static Site Bandwidth Pricing: Netlify, Vercel, Cloudflare",{"path":2248,"title":2249},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-redirects-on-vercel-for-static-sites","Configuring Redirects on Vercel for Static Sites",{"path":2251,"title":2252},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2254,"title":2255},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fdeploying-astro-to-vercel-as-a-fully-static-site","Deploying Astro to Vercel as a Fully Static Site",{"path":2257,"title":2258},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Ffixing-netlify-builds-that-exceed-the-time-limit","Fixing Netlify Builds That Exceed the Time Limit",{"path":2260,"title":2261},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Ffixing-vercel-builds-that-run-out-of-memory","Fixing Vercel Builds That Run Out of Memory",{"path":2263,"title":2264},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2266,"title":2267},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2269,"title":2270},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2272,"title":2273},"\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":2275,"title":2276},"\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":2278,"title":2279},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fvercel-build-output-api-for-custom-ssgs","Vercel Build Output API for Custom SSGs",{"path":2281,"title":2282},"\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":2284,"title":2285},"\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":2287,"title":2288},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2290,"title":2291},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2293,"title":2294},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Ffixing-preview-deploys-leaking-into-search-results","Fixing Preview Deploys Leaking Into Search Results",{"path":2296,"title":2297},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2299,"title":2300},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2302,"title":2303},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2305,"title":2306},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2308,"title":2309},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpull-request-previews-for-github-pages-sites","Pull Request Previews for GitHub Pages Sites",{"path":2311,"title":2312},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2314,"title":2315},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2317,"title":2318},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fblue-green-deploys-for-static-sites","Blue-Green Deploys for Static Sites",{"path":2320,"title":2321},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2323,"title":2324},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2326,"title":2327},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2329,"title":2330},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fkeeping-old-assets-alive-after-deploy","Keeping Old Assets Alive After Deploy",{"path":2332,"title":2333},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2335,"title":2336},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frecovering-from-a-deploy-that-deleted-live-assets","Recovering From a Deploy That Deleted Live Assets",{"path":2338,"title":2339},"\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":2341,"title":2342},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-netlify-deploys-from-the-cli-and-api","Rolling Back Netlify Deploys From the CLI and API",{"path":2344,"title":2345},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-s3-and-cloudfront-deploys-with-versioned-prefixes","Rolling Back S3 and CloudFront Deploys With Versioned Prefixes",{"path":2347,"title":2348},"\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":2350,"title":2351},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2353,"title":2354},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2356,"title":2357},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Ffixing-content-security-policy-violations-from-inline-scripts","Fixing Content Security Policy Violations From Inline Scripts",{"path":2359,"title":2360},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Ffixing-mixed-content-warnings-after-moving-to-https","Fixing Mixed Content Warnings After Moving to HTTPS",{"path":2362,"title":2363},"\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":2365,"title":2366},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2368,"title":2369},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2371,"title":2372},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2374,"title":2375},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecurity-headers-for-static-sites-served-by-caddy","Security Headers for Static Sites Served by Caddy",{"path":2377,"title":2378},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecurity-headers-on-vercel-for-static-sites","Security Headers on Vercel for Static Sites",{"path":2380,"title":2381},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecurity-txt-and-disclosure-for-static-sites","security.txt and Disclosure for Static Sites",{"path":2383,"title":2384},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2386,"title":2387},"\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":2389,"title":2390},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2392,"title":2393},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2395,"title":2396},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2398,"title":2399},"\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":2401,"title":2402},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2404,"title":2405},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2407,"title":2408},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2410,"title":2411},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-from-a-docker-container-with-nginx","Serving a Static Site From a Docker Container With Nginx",{"path":2413,"title":2414},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy-and-automatic-https","Serving a Static Site With Caddy and Automatic HTTPS",{"path":2416,"title":2417},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2419,"title":2420},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2422,"title":2423},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2425,"title":2426},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2428,"title":2429},"\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":2431,"title":2432},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Ffixing-cold-starts-in-netlify-functions-for-forms","Fixing Cold Starts in Netlify Functions for Forms",{"path":2434,"title":2435},"\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":2437,"title":2438},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2440,"title":2441},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2443,"title":2444},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2446,"title":2447},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2449,"title":2450},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fproxying-third-party-apis-from-an-edge-function","Proxying Third-Party APIs from an Edge Function",{"path":2452,"title":2453},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2455,"title":2456},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Faccessibility-testing-with-axe-and-pa11y-in-ci","Accessibility Testing with axe and pa11y in CI",{"path":2458,"title":2459},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fend-to-end-tests-for-static-sites-with-playwright","End-to-End Tests for Static Sites with Playwright",{"path":2461,"title":2462},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ffixing-flaky-playwright-tests-against-preview-deploys","Fixing Flaky Playwright Tests Against Preview Deploys",{"path":2464,"title":2465},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2467,"title":2468},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2470,"title":2471},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2473,"title":2474},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-search-and-navigation-flows-with-playwright","Testing Search and Navigation Flows With Playwright",{"path":2476,"title":2477},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2479,"title":2480},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2482,"tools":2486},{"label":2483,"plural":2484,"u":2485},"How-to","How-tos","\u002Fguides\u002Fhow-to\u002F",[2487],{"label":2488,"u":2489},"GitHub Actions","\u002Ftools\u002Fgithub-actions\u002F",1790943195790]