[{"data":1,"prerenderedAt":2923},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds":3,"all-docs-nav":1775,"filed:\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds":2914},{"id":4,"title":5,"body":6,"breadcrumb":1751,"dateModified":1761,"datePublished":1761,"description":1762,"extension":1763,"faq":1764,"meta":1769,"navigation":533,"path":1770,"seo":1771,"slug":12,"stem":1772,"type":1773,"__hash__":1774},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds\u002Findex.md","Reusable Workflows for SSG Builds",{"type":7,"value":8,"toc":1731},"minimark",[9,13,17,26,31,49,53,56,154,157,279,283,935,938,1048,1178,1182,1185,1308,1323,1327,1338,1346,1350,1368,1493,1497,1500,1504,1511,1518,1521,1525,1604,1608,1647,1651,1654,1658,1663,1666,1670,1673,1677,1680,1684,1687,1691,1727],[10,11,5],"h1",{"id":12},"reusable-workflows-for-ssg-builds",[14,15,16],"p",{},"Organisations rarely have one static site. They have the product docs, the marketing site, the engineering blog, an API reference, a status page, three microsites for events — each built with a static generator, each with a GitHub Actions workflow that someone copied from the previous one and adjusted. Two years later there are fourteen slightly different pipelines: some cache dependencies and some do not, some run link checks, one still deploys with a long-lived API token, and a security fix to the deploy step has to be made fourteen times.",[14,18,19,20,25],{},"GitHub Actions reusable workflows turn that into one pipeline definition, versioned and called by each site with a few inputs. This guide builds a shared build-test-deploy workflow for static sites, packages smaller pieces as composite actions, versions it with tags, and migrates fourteen sites onto it. 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,38,46],"ul",{},[35,36,37],"li",{},"A GitHub organization with several static site repositories.",[35,39,40,41,45],{},"A central repository for shared CI (here ",[42,43,44],"code",{},"example\u002Fssg-ci","), with access granted to the organization's repositories under Settings → Actions → Access.",[35,47,48],{},"A common deploy target, or a small set of them (here Cloudflare Workers static assets and GitHub Pages).",[27,50,52],{"id":51},"what-the-fourteen-pipelines-had-in-common","What the Fourteen Pipelines Had in Common",[14,54,55],{},"Diffing the workflows showed the same shape everywhere, with drift in the details:",[57,58,59,75],"table",{},[60,61,62],"thead",{},[63,64,65,69,72],"tr",{},[66,67,68],"th",{},"Step",[66,70,71],{},"Sites doing it",[66,73,74],{},"Variations",[76,77,78,90,101,111,122,133,144],"tbody",{},[63,79,80,84,87],{},[81,82,83],"td",{},"Checkout, setup Node or Hugo",[81,85,86],{},"14",[81,88,89],{},"5 Node versions, 3 Hugo versions",[63,91,92,95,98],{},[81,93,94],{},"Dependency caching",[81,96,97],{},"9",[81,99,100],{},"4 different cache keys",[63,102,103,106,108],{},[81,104,105],{},"Build",[81,107,86],{},[81,109,110],{},"4 generators",[63,112,113,116,119],{},[81,114,115],{},"Link check",[81,117,118],{},"6",[81,120,121],{},"3 different tools",[63,123,124,127,130],{},[81,125,126],{},"HTML validation",[81,128,129],{},"2",[81,131,132],{},"—",[63,134,135,138,141],{},[81,136,137],{},"Preview deploy per PR",[81,139,140],{},"8",[81,142,143],{},"3 hosts",[63,145,146,149,151],{},[81,147,148],{},"Production deploy",[81,150,86],{},[81,152,153],{},"5 used long-lived tokens",[14,155,156],{},"A shared workflow could standardize the common path and expose the real differences — generator, build command, output directory, deploy target — as inputs.",[158,159,160,275],"figure",{},[161,162,169,170,169,174,169,178,169,185],"svg",{"viewBox":163,"role":164,"ariaLabelledBy":165,"xmlns":168},"0 0 760 244","img",[166,167],"rw-drift-title","rw-drift-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[171,172,173],"title",{"id":166},"Number of sites performing each pipeline step before consolidation",[175,176,177],"desc",{"id":167},"Horizontal bars of how many of the 14 sites performed each step. Build and production deploy 14. Dependency caching 9. Preview deploys 8. Link checks 6. HTML validation 2. Five of the fourteen production deploys used long-lived API tokens.",[179,180],"rect",{"x":181,"y":181,"width":182,"height":183,"fill":184},"0","760","244","#ffffff",[186,187,189,190,189,200,189,207,189,211,189,217,189,221,189,228,189,236,189,241,189,246,189,249,189,253,189,256,189,260,189,263,189,268,189,271,169],"g",{"style":188},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[179,191],{"x":192,"y":193,"width":194,"height":195,"rx":196,"fill":197,"opacity":198,"stroke":197,"style":199},"240.0","65.0","467.2","20.0","3","#1982c4","0.3","stroke-width:1px",[179,201],{"x":192,"y":202,"width":203,"height":195,"rx":196,"fill":204,"opacity":205,"stroke":206,"style":199},"99.0","300.3","#ffca3a","0.45","#a97b00",[179,208],{"x":192,"y":209,"width":210,"height":195,"rx":196,"fill":204,"opacity":205,"stroke":206,"style":199},"133.0","267.0",[179,212],{"x":192,"y":213,"width":214,"height":195,"rx":196,"fill":215,"opacity":198,"stroke":216,"style":199},"167.0","200.2","#ff595e","#d83b41",[179,218],{"x":192,"y":219,"width":220,"height":195,"rx":196,"fill":215,"opacity":198,"stroke":216,"style":199},"201.0","66.7",[222,223],"path",{"d":224,"fill":225,"stroke":226,"style":227},"M240.0 60.0 L240.0 226.0","none","#556071","stroke-width:1.5px",[229,230,235],"text",{"x":231,"y":232,"fill":233,"style":234},"380.0","30.0","#1f2937","font-size:16px;text-anchor:middle;font-weight:700","How consistently each step was done across 14 sites",[229,237,240],{"x":195,"y":238,"fill":233,"style":239},"79.2","font-size:12px;text-anchor:start","Build + production deploy",[229,242,86],{"x":243,"y":244,"fill":233,"style":245},"715.2","79.5","font-size:12px;text-anchor:start;font-weight:700",[229,247,94],{"x":195,"y":248,"fill":233,"style":239},"113.2",[229,250,97],{"x":251,"y":252,"fill":233,"style":245},"548.3","113.5",[229,254,137],{"x":195,"y":255,"fill":233,"style":239},"147.2",[229,257,140],{"x":258,"y":259,"fill":233,"style":245},"515.0","147.5",[229,261,115],{"x":195,"y":262,"fill":233,"style":239},"181.2",[229,264,118],{"x":265,"y":266,"fill":267,"style":245},"448.2","181.5","#b32b30",[229,269,126],{"x":195,"y":270,"fill":233,"style":239},"215.2",[229,272,129],{"x":273,"y":274,"fill":267,"style":245},"314.7","215.5",[276,277,278],"figcaption",{},"From a review of each repository's workflow files; variations within each step not shown.",[27,280,282],{"id":281},"step-1-the-reusable-workflow","Step 1: The Reusable Workflow",[284,285,290],"pre",{"className":286,"code":287,"language":288,"meta":289,"style":289},"language-yaml shiki shiki-themes github-light github-dark","# example\u002Fssg-ci\u002F.github\u002Fworkflows\u002Fssg.yml\nname: SSG build and deploy\non:\n  workflow_call:\n    inputs:\n      node-version: { type: string, default: '22' }\n      build-command: { type: string, default: 'npm run build' }\n      output-dir: { type: string, default: 'dist' }\n      deploy-target: { type: string, required: true }        # 'workers' | 'gh-pages'\n      worker-name: { type: string, default: '' }\n      run-link-check: { type: boolean, default: true }\n    secrets:\n      CLOUDFLARE_API_TOKEN: { required: false }\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with: { fetch-depth: 0 }\n      - uses: example\u002Fssg-ci\u002Factions\u002Fsetup-node-cached@v3\n        with: { node-version: '${{ inputs.node-version }}' }\n      - run: ${{ inputs.build-command }}\n      - if: inputs.run-link-check\n        uses: example\u002Fssg-ci\u002Factions\u002Fcheck-output@v3\n        with: { dir: '${{ inputs.output-dir }}' }\n      - uses: actions\u002Fupload-artifact@v4\n        with: { name: site, path: '${{ inputs.output-dir }}' }\n\n  deploy:\n    needs: build\n    runs-on: ubuntu-latest\n    permissions: { contents: read, deployments: write, pull-requests: write, pages: write, id-token: write }\n    steps:\n      - uses: actions\u002Fdownload-artifact@v4\n        with: { name: site, path: site }\n      - if: inputs.deploy-target == 'workers'\n        uses: example\u002Fssg-ci\u002Factions\u002Fdeploy-workers@v3\n        with: { dir: site, worker-name: '${{ inputs.worker-name }}', preview: '${{ github.event_name == ''pull_request'' }}' }\n        env: { CLOUDFLARE_API_TOKEN: '${{ secrets.CLOUDFLARE_API_TOKEN }}' }\n","yaml","",[42,291,292,301,316,326,334,342,373,398,423,453,478,503,511,528,535,543,551,562,570,584,601,613,630,643,656,667,684,696,720,725,733,744,753,808,815,827,850,862,872,917],{"__ignoreMap":289},[293,294,297],"span",{"class":295,"line":296},"line",1,[293,298,300],{"class":299},"sJ8bj","# example\u002Fssg-ci\u002F.github\u002Fworkflows\u002Fssg.yml\n",[293,302,304,308,312],{"class":295,"line":303},2,[293,305,307],{"class":306},"s9eBZ","name",[293,309,311],{"class":310},"sVt8B",": ",[293,313,315],{"class":314},"sZZnC","SSG build and deploy\n",[293,317,319,323],{"class":295,"line":318},3,[293,320,322],{"class":321},"sj4cs","on",[293,324,325],{"class":310},":\n",[293,327,329,332],{"class":295,"line":328},4,[293,330,331],{"class":306},"  workflow_call",[293,333,325],{"class":310},[293,335,337,340],{"class":295,"line":336},5,[293,338,339],{"class":306},"    inputs",[293,341,325],{"class":310},[293,343,345,348,351,354,356,359,362,365,367,370],{"class":295,"line":344},6,[293,346,347],{"class":306},"      node-version",[293,349,350],{"class":310},": { ",[293,352,353],{"class":306},"type",[293,355,311],{"class":310},[293,357,358],{"class":314},"string",[293,360,361],{"class":310},", ",[293,363,364],{"class":306},"default",[293,366,311],{"class":310},[293,368,369],{"class":314},"'22'",[293,371,372],{"class":310}," }\n",[293,374,376,379,381,383,385,387,389,391,393,396],{"class":295,"line":375},7,[293,377,378],{"class":306},"      build-command",[293,380,350],{"class":310},[293,382,353],{"class":306},[293,384,311],{"class":310},[293,386,358],{"class":314},[293,388,361],{"class":310},[293,390,364],{"class":306},[293,392,311],{"class":310},[293,394,395],{"class":314},"'npm run build'",[293,397,372],{"class":310},[293,399,401,404,406,408,410,412,414,416,418,421],{"class":295,"line":400},8,[293,402,403],{"class":306},"      output-dir",[293,405,350],{"class":310},[293,407,353],{"class":306},[293,409,311],{"class":310},[293,411,358],{"class":314},[293,413,361],{"class":310},[293,415,364],{"class":306},[293,417,311],{"class":310},[293,419,420],{"class":314},"'dist'",[293,422,372],{"class":310},[293,424,426,429,431,433,435,437,439,442,444,447,450],{"class":295,"line":425},9,[293,427,428],{"class":306},"      deploy-target",[293,430,350],{"class":310},[293,432,353],{"class":306},[293,434,311],{"class":310},[293,436,358],{"class":314},[293,438,361],{"class":310},[293,440,441],{"class":306},"required",[293,443,311],{"class":310},[293,445,446],{"class":321},"true",[293,448,449],{"class":310}," }        ",[293,451,452],{"class":299},"# 'workers' | 'gh-pages'\n",[293,454,456,459,461,463,465,467,469,471,473,476],{"class":295,"line":455},10,[293,457,458],{"class":306},"      worker-name",[293,460,350],{"class":310},[293,462,353],{"class":306},[293,464,311],{"class":310},[293,466,358],{"class":314},[293,468,361],{"class":310},[293,470,364],{"class":306},[293,472,311],{"class":310},[293,474,475],{"class":314},"''",[293,477,372],{"class":310},[293,479,481,484,486,488,490,493,495,497,499,501],{"class":295,"line":480},11,[293,482,483],{"class":306},"      run-link-check",[293,485,350],{"class":310},[293,487,353],{"class":306},[293,489,311],{"class":310},[293,491,492],{"class":314},"boolean",[293,494,361],{"class":310},[293,496,364],{"class":306},[293,498,311],{"class":310},[293,500,446],{"class":321},[293,502,372],{"class":310},[293,504,506,509],{"class":295,"line":505},12,[293,507,508],{"class":306},"    secrets",[293,510,325],{"class":310},[293,512,514,517,519,521,523,526],{"class":295,"line":513},13,[293,515,516],{"class":306},"      CLOUDFLARE_API_TOKEN",[293,518,350],{"class":310},[293,520,441],{"class":306},[293,522,311],{"class":310},[293,524,525],{"class":321},"false",[293,527,372],{"class":310},[293,529,531],{"class":295,"line":530},14,[293,532,534],{"emptyLinePlaceholder":533},true,"\n",[293,536,538,541],{"class":295,"line":537},15,[293,539,540],{"class":306},"jobs",[293,542,325],{"class":310},[293,544,546,549],{"class":295,"line":545},16,[293,547,548],{"class":306},"  build",[293,550,325],{"class":310},[293,552,554,557,559],{"class":295,"line":553},17,[293,555,556],{"class":306},"    runs-on",[293,558,311],{"class":310},[293,560,561],{"class":314},"ubuntu-latest\n",[293,563,565,568],{"class":295,"line":564},18,[293,566,567],{"class":306},"    steps",[293,569,325],{"class":310},[293,571,573,576,579,581],{"class":295,"line":572},19,[293,574,575],{"class":310},"      - ",[293,577,578],{"class":306},"uses",[293,580,311],{"class":310},[293,582,583],{"class":314},"actions\u002Fcheckout@v4\n",[293,585,587,590,592,595,597,599],{"class":295,"line":586},20,[293,588,589],{"class":306},"        with",[293,591,350],{"class":310},[293,593,594],{"class":306},"fetch-depth",[293,596,311],{"class":310},[293,598,181],{"class":321},[293,600,372],{"class":310},[293,602,604,606,608,610],{"class":295,"line":603},21,[293,605,575],{"class":310},[293,607,578],{"class":306},[293,609,311],{"class":310},[293,611,612],{"class":314},"example\u002Fssg-ci\u002Factions\u002Fsetup-node-cached@v3\n",[293,614,616,618,620,623,625,628],{"class":295,"line":615},22,[293,617,589],{"class":306},[293,619,350],{"class":310},[293,621,622],{"class":306},"node-version",[293,624,311],{"class":310},[293,626,627],{"class":314},"'${{ inputs.node-version }}'",[293,629,372],{"class":310},[293,631,633,635,638,640],{"class":295,"line":632},23,[293,634,575],{"class":310},[293,636,637],{"class":306},"run",[293,639,311],{"class":310},[293,641,642],{"class":314},"${{ inputs.build-command }}\n",[293,644,646,648,651,653],{"class":295,"line":645},24,[293,647,575],{"class":310},[293,649,650],{"class":306},"if",[293,652,311],{"class":310},[293,654,655],{"class":314},"inputs.run-link-check\n",[293,657,659,662,664],{"class":295,"line":658},25,[293,660,661],{"class":306},"        uses",[293,663,311],{"class":310},[293,665,666],{"class":314},"example\u002Fssg-ci\u002Factions\u002Fcheck-output@v3\n",[293,668,670,672,674,677,679,682],{"class":295,"line":669},26,[293,671,589],{"class":306},[293,673,350],{"class":310},[293,675,676],{"class":306},"dir",[293,678,311],{"class":310},[293,680,681],{"class":314},"'${{ inputs.output-dir }}'",[293,683,372],{"class":310},[293,685,687,689,691,693],{"class":295,"line":686},27,[293,688,575],{"class":310},[293,690,578],{"class":306},[293,692,311],{"class":310},[293,694,695],{"class":314},"actions\u002Fupload-artifact@v4\n",[293,697,699,701,703,705,707,710,712,714,716,718],{"class":295,"line":698},28,[293,700,589],{"class":306},[293,702,350],{"class":310},[293,704,307],{"class":306},[293,706,311],{"class":310},[293,708,709],{"class":314},"site",[293,711,361],{"class":310},[293,713,222],{"class":306},[293,715,311],{"class":310},[293,717,681],{"class":314},[293,719,372],{"class":310},[293,721,723],{"class":295,"line":722},29,[293,724,534],{"emptyLinePlaceholder":533},[293,726,728,731],{"class":295,"line":727},30,[293,729,730],{"class":306},"  deploy",[293,732,325],{"class":310},[293,734,736,739,741],{"class":295,"line":735},31,[293,737,738],{"class":306},"    needs",[293,740,311],{"class":310},[293,742,743],{"class":314},"build\n",[293,745,747,749,751],{"class":295,"line":746},32,[293,748,556],{"class":306},[293,750,311],{"class":310},[293,752,561],{"class":314},[293,754,756,759,761,764,766,769,771,774,776,779,781,784,786,788,790,793,795,797,799,802,804,806],{"class":295,"line":755},33,[293,757,758],{"class":306},"    permissions",[293,760,350],{"class":310},[293,762,763],{"class":306},"contents",[293,765,311],{"class":310},[293,767,768],{"class":314},"read",[293,770,361],{"class":310},[293,772,773],{"class":306},"deployments",[293,775,311],{"class":310},[293,777,778],{"class":314},"write",[293,780,361],{"class":310},[293,782,783],{"class":306},"pull-requests",[293,785,311],{"class":310},[293,787,778],{"class":314},[293,789,361],{"class":310},[293,791,792],{"class":306},"pages",[293,794,311],{"class":310},[293,796,778],{"class":314},[293,798,361],{"class":310},[293,800,801],{"class":306},"id-token",[293,803,311],{"class":310},[293,805,778],{"class":314},[293,807,372],{"class":310},[293,809,811,813],{"class":295,"line":810},34,[293,812,567],{"class":306},[293,814,325],{"class":310},[293,816,818,820,822,824],{"class":295,"line":817},35,[293,819,575],{"class":310},[293,821,578],{"class":306},[293,823,311],{"class":310},[293,825,826],{"class":314},"actions\u002Fdownload-artifact@v4\n",[293,828,830,832,834,836,838,840,842,844,846,848],{"class":295,"line":829},36,[293,831,589],{"class":306},[293,833,350],{"class":310},[293,835,307],{"class":306},[293,837,311],{"class":310},[293,839,709],{"class":314},[293,841,361],{"class":310},[293,843,222],{"class":306},[293,845,311],{"class":310},[293,847,709],{"class":314},[293,849,372],{"class":310},[293,851,853,855,857,859],{"class":295,"line":852},37,[293,854,575],{"class":310},[293,856,650],{"class":306},[293,858,311],{"class":310},[293,860,861],{"class":314},"inputs.deploy-target == 'workers'\n",[293,863,865,867,869],{"class":295,"line":864},38,[293,866,661],{"class":306},[293,868,311],{"class":310},[293,870,871],{"class":314},"example\u002Fssg-ci\u002Factions\u002Fdeploy-workers@v3\n",[293,873,875,877,879,881,883,885,887,890,892,895,897,900,902,905,907,910,912,915],{"class":295,"line":874},39,[293,876,589],{"class":306},[293,878,350],{"class":310},[293,880,676],{"class":306},[293,882,311],{"class":310},[293,884,709],{"class":314},[293,886,361],{"class":310},[293,888,889],{"class":306},"worker-name",[293,891,311],{"class":310},[293,893,894],{"class":314},"'${{ inputs.worker-name }}'",[293,896,361],{"class":310},[293,898,899],{"class":306},"preview",[293,901,311],{"class":310},[293,903,904],{"class":314},"'${{ github.event_name == ",[293,906,475],{"class":321},[293,908,909],{"class":314},"pull_request",[293,911,475],{"class":321},[293,913,914],{"class":314}," }}'",[293,916,372],{"class":310},[293,918,920,923,925,928,930,933],{"class":295,"line":919},40,[293,921,922],{"class":306},"        env",[293,924,350],{"class":310},[293,926,927],{"class":306},"CLOUDFLARE_API_TOKEN",[293,929,311],{"class":310},[293,931,932],{"class":314},"'${{ secrets.CLOUDFLARE_API_TOKEN }}'",[293,934,372],{"class":310},[14,936,937],{},"Each site's workflow becomes a few lines:",[284,939,941],{"className":286,"code":940,"language":288,"meta":289,"style":289},"# docs repo: .github\u002Fworkflows\u002Fsite.yml\non: { push: { branches: [main] }, pull_request: {} }\njobs:\n  site:\n    uses: example\u002Fssg-ci\u002F.github\u002Fworkflows\u002Fssg.yml@v3\n    with: { deploy-target: workers, worker-name: docs-site, build-command: 'npm run build' }\n    secrets: { CLOUDFLARE_API_TOKEN: '${{ secrets.CLOUDFLARE_API_TOKEN }}' }\n",[42,942,943,948,976,982,989,999,1034],{"__ignoreMap":289},[293,944,945],{"class":295,"line":296},[293,946,947],{"class":299},"# docs repo: .github\u002Fworkflows\u002Fsite.yml\n",[293,949,950,952,954,957,959,962,965,968,971,973],{"class":295,"line":303},[293,951,322],{"class":321},[293,953,350],{"class":310},[293,955,956],{"class":306},"push",[293,958,350],{"class":310},[293,960,961],{"class":306},"branches",[293,963,964],{"class":310},": [",[293,966,967],{"class":314},"main",[293,969,970],{"class":310},"] }, ",[293,972,909],{"class":306},[293,974,975],{"class":310},": {} }\n",[293,977,978,980],{"class":295,"line":318},[293,979,540],{"class":306},[293,981,325],{"class":310},[293,983,984,987],{"class":295,"line":328},[293,985,986],{"class":306},"  site",[293,988,325],{"class":310},[293,990,991,994,996],{"class":295,"line":336},[293,992,993],{"class":306},"    uses",[293,995,311],{"class":310},[293,997,998],{"class":314},"example\u002Fssg-ci\u002F.github\u002Fworkflows\u002Fssg.yml@v3\n",[293,1000,1001,1004,1006,1009,1011,1014,1016,1018,1020,1023,1025,1028,1030,1032],{"class":295,"line":344},[293,1002,1003],{"class":306},"    with",[293,1005,350],{"class":310},[293,1007,1008],{"class":306},"deploy-target",[293,1010,311],{"class":310},[293,1012,1013],{"class":314},"workers",[293,1015,361],{"class":310},[293,1017,889],{"class":306},[293,1019,311],{"class":310},[293,1021,1022],{"class":314},"docs-site",[293,1024,361],{"class":310},[293,1026,1027],{"class":306},"build-command",[293,1029,311],{"class":310},[293,1031,395],{"class":314},[293,1033,372],{"class":310},[293,1035,1036,1038,1040,1042,1044,1046],{"class":295,"line":375},[293,1037,508],{"class":306},[293,1039,350],{"class":310},[293,1041,927],{"class":306},[293,1043,311],{"class":310},[293,1045,932],{"class":314},[293,1047,372],{"class":310},[158,1049,1050,1175],{},[161,1051,169,1056,169,1059,169,1062,169,1065,169,1160],{"viewBox":1052,"role":164,"ariaLabelledBy":1053,"xmlns":168},"0 0 760 312",[1054,1055],"rw-call-title","rw-call-desc",[171,1057,1058],{"id":1054},"Call sequence from a site repository to the shared workflow",[175,1060,1061],{"id":1055},"The site repository's workflow calls the shared ssg.yml at tag v3 with inputs and one secret. The shared workflow's build job uses composite actions for Node setup with caching and output checks, builds and uploads the artifact. The deploy job downloads it and deploys with the composite deploy action, as a preview for pull requests or to production on main.",[179,1063],{"x":181,"y":181,"width":182,"height":1064,"fill":184},"312",[186,1066,189,1067,189,1075,189,1080,189,1083,189,1087,189,1090,189,1093,189,1096,189,1100,189,1104,189,1107,189,1110,189,1113,189,1119,189,1124,189,1127,189,1130,189,1134,189,1137,189,1143,189,1148,189,1152,189,1156,169],{"style":188},[179,1068],{"x":1069,"y":1070,"width":1071,"height":1072,"rx":140,"fill":1073,"stroke":1074,"style":227},"55.0","56.0","170.0","57.2","#f8fafc","#d9e2ef",[179,1076],{"x":1077,"y":1070,"width":1071,"height":1072,"rx":140,"fill":1078,"opacity":1079,"stroke":1078,"style":227},"295.0","#6a4c93","0.14",[179,1081],{"x":1082,"y":1070,"width":1071,"height":1072,"rx":140,"fill":197,"opacity":1079,"stroke":197,"style":227},"535.0",[222,1084],{"d":1085,"fill":225,"stroke":226,"style":1086},"M144.0 148.1 L374.0 148.1","stroke-width:1.8px;marker-end:url(#rw-call-arrow)",[222,1088],{"d":1089,"fill":225,"stroke":226,"style":1086},"M384.0 181.1 L614.0 181.1",[222,1091],{"d":1092,"fill":225,"stroke":226,"style":1086},"M384.0 214.0 L614.0 214.0",[222,1094],{"d":1095,"fill":225,"stroke":226,"style":1086},"M384.0 247.0 L614.0 247.0",[222,1097],{"d":1098,"fill":225,"stroke":226,"style":1099},"M376.0 279.9 L146.0 279.9","stroke-width:1.8px;stroke-dasharray:5 4;marker-end:url(#rw-call-arrow)",[222,1101],{"d":1102,"fill":225,"stroke":1074,"style":1103},"M140.0 115.2 L140.0 295.9","stroke-width:1.5px;stroke-dasharray:4 4",[222,1105],{"d":1106,"fill":225,"stroke":1074,"style":1103},"M380.0 115.2 L380.0 295.9",[222,1108],{"d":1109,"fill":225,"stroke":1074,"style":1103},"M620.0 115.2 L620.0 295.9",[229,1111,1112],{"x":231,"y":232,"fill":233,"style":234},"A site calling the shared workflow",[229,1114,1118],{"x":1115,"y":1116,"fill":233,"style":1117},"140.0","82.4","font-size:13px;text-anchor:middle;font-weight:700","Site repo",[229,1120,1123],{"x":1115,"y":1121,"fill":226,"style":1122},"99.3","font-size:11px;text-anchor:middle","site.yml (8 lines)",[229,1125,1126],{"x":231,"y":1116,"fill":233,"style":1117},"ssg.yml@v3",[229,1128,1129],{"x":231,"y":1121,"fill":226,"style":1122},"reusable workflow",[229,1131,1133],{"x":1132,"y":1116,"fill":233,"style":1117},"620.0","Composite actions",[229,1135,1136],{"x":1132,"y":1121,"fill":226,"style":1122},"setup, checks, deploy",[229,1138,1142],{"x":1139,"y":1140,"fill":233,"style":1141},"260.0","140.1","font-size:11.5px;text-anchor:middle","uses ssg.yml@v3 with inputs + secret",[229,1144,1147],{"x":1145,"y":1146,"fill":233,"style":1141},"500.0","173.1","setup-node-cached",[229,1149,1151],{"x":1145,"y":1150,"fill":233,"style":1141},"206.0","check-output (links, HTML)",[229,1153,1155],{"x":1145,"y":1154,"fill":233,"style":1141},"239.0","deploy-workers (preview or prod)",[229,1157,1159],{"x":1139,"y":1158,"fill":226,"style":1141},"271.9","status checks and preview comment",[1161,1162,189,1163,169],"defs",{},[1164,1165,1171,1172,189],"marker",{"id":1166,"viewBox":1167,"refX":140,"refY":1168,"markerWidth":1169,"markerHeight":1169,"orient":1170},"rw-call-arrow","0 0 10 10","5","7","auto-start-reverse","\n      ",[222,1173],{"d":1174,"fill":226},"M0 0 L10 5 L0 10 z",[276,1176,1177],{},"The site repository contains only inputs; all pipeline logic lives in the versioned shared repository.",[27,1179,1181],{"id":1180},"step-2-composite-actions-for-the-pieces","Step 2: Composite Actions for the Pieces",[14,1183,1184],{},"Steps that several workflows share — and that some sites want to use outside the full pipeline — are composite actions in the same repository:",[284,1186,1188],{"className":286,"code":1187,"language":288,"meta":289,"style":289},"# example\u002Fssg-ci\u002Factions\u002Fsetup-node-cached\u002Faction.yml\nname: Setup Node with cache\ninputs:\n  node-version: { default: '22' }\nruns:\n  using: composite\n  steps:\n    - uses: actions\u002Fsetup-node@v4\n      with: { node-version: '${{ inputs.node-version }}', cache: npm }\n    - run: npm ci --prefer-offline --no-audit --fund=false\n      shell: bash\n",[42,1189,1190,1195,1204,1211,1226,1233,1243,1250,1262,1287,1298],{"__ignoreMap":289},[293,1191,1192],{"class":295,"line":296},[293,1193,1194],{"class":299},"# example\u002Fssg-ci\u002Factions\u002Fsetup-node-cached\u002Faction.yml\n",[293,1196,1197,1199,1201],{"class":295,"line":303},[293,1198,307],{"class":306},[293,1200,311],{"class":310},[293,1202,1203],{"class":314},"Setup Node with cache\n",[293,1205,1206,1209],{"class":295,"line":318},[293,1207,1208],{"class":306},"inputs",[293,1210,325],{"class":310},[293,1212,1213,1216,1218,1220,1222,1224],{"class":295,"line":328},[293,1214,1215],{"class":306},"  node-version",[293,1217,350],{"class":310},[293,1219,364],{"class":306},[293,1221,311],{"class":310},[293,1223,369],{"class":314},[293,1225,372],{"class":310},[293,1227,1228,1231],{"class":295,"line":336},[293,1229,1230],{"class":306},"runs",[293,1232,325],{"class":310},[293,1234,1235,1238,1240],{"class":295,"line":344},[293,1236,1237],{"class":306},"  using",[293,1239,311],{"class":310},[293,1241,1242],{"class":314},"composite\n",[293,1244,1245,1248],{"class":295,"line":375},[293,1246,1247],{"class":306},"  steps",[293,1249,325],{"class":310},[293,1251,1252,1255,1257,1259],{"class":295,"line":400},[293,1253,1254],{"class":310},"    - ",[293,1256,578],{"class":306},[293,1258,311],{"class":310},[293,1260,1261],{"class":314},"actions\u002Fsetup-node@v4\n",[293,1263,1264,1267,1269,1271,1273,1275,1277,1280,1282,1285],{"class":295,"line":425},[293,1265,1266],{"class":306},"      with",[293,1268,350],{"class":310},[293,1270,622],{"class":306},[293,1272,311],{"class":310},[293,1274,627],{"class":314},[293,1276,361],{"class":310},[293,1278,1279],{"class":306},"cache",[293,1281,311],{"class":310},[293,1283,1284],{"class":314},"npm",[293,1286,372],{"class":310},[293,1288,1289,1291,1293,1295],{"class":295,"line":455},[293,1290,1254],{"class":310},[293,1292,637],{"class":306},[293,1294,311],{"class":310},[293,1296,1297],{"class":314},"npm ci --prefer-offline --no-audit --fund=false\n",[293,1299,1300,1303,1305],{"class":295,"line":480},[293,1301,1302],{"class":306},"      shell",[293,1304,311],{"class":310},[293,1306,1307],{"class":314},"bash\n",[14,1309,1310,1313,1314,1318,1319,25],{},[42,1311,1312],{},"check-output"," bundles the link check and HTML validation, so the six sites that had link checks and the eight that did not all got both, with the same tools and settings. The practices are those in ",[21,1315,1317],{"href":1316},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests\u002F","Checking Links in Pull Requests"," and ",[21,1320,1322],{"href":1321},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci\u002F","Validating HTML Output in CI",[27,1324,1326],{"id":1325},"step-3-version-and-upgrade-deliberately","Step 3: Version and Upgrade Deliberately",[14,1328,1329,1330,1333,1334,1337],{},"Callers reference the shared workflow by tag (",[42,1331,1332],{},"@v3","). Changes are released as new tags with a changelog; breaking changes to inputs bump the major version. Renovate, configured with the ",[42,1335,1336],{},"github-actions"," manager, opens pull requests in each site repository when a new tag appears, so each site upgrades with a preview build proving the new pipeline works for it.",[14,1339,1340,1341,1345],{},"For security-sensitive consumers, pinning by commit SHA instead of tag prevents a moved tag from changing what runs; the trade-offs are in ",[21,1342,1344],{"href":1343},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha\u002F","Pinning Actions by Commit SHA",". The shared repository itself pins every third-party action it uses by SHA, so callers inherit that protection.",[27,1347,1349],{"id":1348},"step-4-secrets-and-permissions","Step 4: Secrets and Permissions",[14,1351,1352,1353,1355,1356,1359,1360,1363,1364,25],{},"Reusable workflows receive only the secrets passed to them. Passing one named secret (",[42,1354,927],{},") instead of ",[42,1357,1358],{},"secrets: inherit"," keeps each site's other secrets out of the shared pipeline. Permissions are declared per job in the shared workflow, at the minimum each job needs; the caller's ",[42,1361,1362],{},"GITHUB_TOKEN"," is scoped to them. The migration was also the occasion to replace the five long-lived deploy tokens with OIDC-based short-lived credentials where the target supported it, following ",[21,1365,1367],{"href":1366},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc\u002F","Securing Deploy Credentials with GitHub OIDC",[158,1369,1370,1490],{},[161,1371,169,1376,169,1379,169,1382,169,1385],{"viewBox":1372,"role":164,"ariaLabelledBy":1373,"xmlns":168},"0 0 760 252",[1374,1375],"rw-choose-title","rw-choose-desc",[171,1377,1378],{"id":1374},"When to use a reusable workflow versus a composite action",[175,1380,1381],{"id":1375},"A matrix comparing the two. Reusable workflows package whole jobs with their own runners, permissions, secrets and job dependencies, suit complete pipelines, and are called at the job level. Composite actions package steps inside the caller's job, share the caller's runner and permissions, suit small building blocks, and are called at the step level.",[179,1383],{"x":181,"y":181,"width":182,"height":1384,"fill":184},"252",[186,1386,189,1387,189,1390,189,1396,189,1399,189,1402,189,1409,189,1412,189,1415,189,1419,189,1421,189,1424,189,1427,189,1430,189,1434,189,1439,189,1443,189,1447,189,1451,189,1454,189,1457,189,1461,189,1465,189,1468,189,1472,189,1476,189,1479,189,1483,189,1487,169],{"style":188},[222,1388],{"d":1389,"fill":225,"stroke":226,"style":227},"M20.0 86.0 L740.0 86.0",[179,1391],{"x":1392,"y":1393,"width":1394,"height":1395,"rx":1168,"fill":197,"opacity":1079,"stroke":197,"style":199},"214.0","90.0","257.0","25.6",[179,1397],{"x":1398,"y":1393,"width":1394,"height":1395,"rx":1168,"fill":197,"opacity":1079,"stroke":197,"style":199},"479.0",[222,1400],{"d":1401,"fill":225,"stroke":1074,"style":199},"M20.0 119.6 L740.0 119.6",[179,1403],{"x":1392,"y":1404,"width":1394,"height":1405,"rx":1168,"fill":1406,"opacity":1407,"stroke":1408,"style":199},"123.6","41.2","#8ac926","0.2","#5a8a16",[179,1410],{"x":1398,"y":1404,"width":1394,"height":1405,"rx":1168,"fill":215,"opacity":1411,"stroke":216,"style":199},"0.12",[222,1413],{"d":1414,"fill":225,"stroke":1074,"style":199},"M20.0 168.8 L740.0 168.8",[179,1416],{"x":1392,"y":1417,"width":1394,"height":1395,"rx":1168,"fill":204,"opacity":1418,"stroke":206,"style":199},"172.8","0.24",[179,1420],{"x":1398,"y":1417,"width":1394,"height":1395,"rx":1168,"fill":204,"opacity":1418,"stroke":206,"style":199},[222,1422],{"d":1423,"fill":225,"stroke":1074,"style":199},"M20.0 202.4 L740.0 202.4",[222,1425],{"d":1426,"fill":225,"stroke":1074,"style":199},"M20.0 236.0 L740.0 236.0",[229,1428,1429],{"x":231,"y":232,"fill":233,"style":234},"Reusable workflow or composite action?",[229,1431,1433],{"x":232,"y":1432,"fill":233,"style":245},"75.2","Aspect",[229,1435,1438],{"x":1436,"y":1432,"fill":233,"style":1437},"342.5","font-size:12px;text-anchor:middle;font-weight:700","Reusable workflow",[229,1440,1442],{"x":1441,"y":1432,"fill":233,"style":1437},"607.5","Composite action",[229,1444,1446],{"x":232,"y":1445,"fill":233,"style":245},"106.4","Unit of reuse",[229,1448,1450],{"x":1436,"y":1449,"fill":233,"style":1141},"106.2","whole jobs",[229,1452,1453],{"x":1441,"y":1449,"fill":233,"style":1141},"steps in a job",[229,1455,1456],{"x":232,"y":1115,"fill":233,"style":245},"Own runner and",[229,1458,1460],{"x":232,"y":1459,"fill":233,"style":245},"155.6","permissions",[229,1462,1464],{"x":1436,"y":1463,"fill":233,"style":1141},"147.7","yes",[229,1466,1467],{"x":1441,"y":1463,"fill":233,"style":1141},"uses caller's",[229,1469,1471],{"x":232,"y":1470,"fill":233,"style":245},"189.2","Secrets",[229,1473,1475],{"x":1436,"y":1474,"fill":233,"style":1141},"189.1","passed explicitly",[229,1477,1478],{"x":1441,"y":1474,"fill":233,"style":1141},"caller's environment",[229,1480,1482],{"x":232,"y":1481,"fill":233,"style":245},"222.8","Best for",[229,1484,1486],{"x":1436,"y":1485,"fill":233,"style":1141},"222.7","complete pipelines",[229,1488,1489],{"x":1441,"y":1485,"fill":233,"style":1141},"small building blocks",[276,1491,1492],{},"The shared repository uses one reusable workflow built from five composite actions.",[27,1494,1496],{"id":1495},"migrating-fourteen-sites","Migrating Fourteen Sites",[14,1498,1499],{},"The migration took two weeks. The shared workflow was developed against three representative sites (Astro on Workers, Hugo on GitHub Pages, Eleventy on Workers) until it covered their needs with inputs; then each remaining site got a pull request replacing its workflow with the eight-line caller. Preview builds proved each one. Two sites needed an extra input — a Hugo version and a custom pre-build step — which became optional inputs rather than special cases.",[27,1501,1503],{"id":1502},"owning-the-shared-pipeline","Owning the Shared Pipeline",[14,1505,1506,1507,1510],{},"A shared workflow needs an owner, or it becomes the thing nobody dares to change. The platform team owns ",[42,1508,1509],{},"ssg-ci",", with a short CODEOWNERS file, a changelog, and a test matrix: every pull request to the shared repository runs the workflow against three fixture sites — a minimal Astro, Hugo and Eleventy project checked into the repository — so a change that breaks one generator fails before it is tagged. Site teams can propose changes, and the most common request, an additional optional input, is accepted when at least two sites need it. Requests that only one site needs are handled as a pre-build script in that site's repository, which keeps the shared interface small.",[14,1512,1513,1514,1517],{},"Documentation matters as much as code here. The repository's README lists every input with its default and an example caller for each generator, and a short \"how to debug a failing run\" section explains how to reproduce the shared workflow locally with ",[42,1515,1516],{},"act"," or by copying it into the site repository temporarily. Questions from site teams dropped noticeably once that section existed; before it, a failing shared step felt like a black box.",[14,1519,1520],{},"Finally, watch for drift in the other direction. Sites occasionally copy a step out of the shared workflow to customise it, and the copy then misses future fixes. A monthly script lists workflow files in every site repository that are longer than the standard caller, which surfaces those forks early.",[27,1522,1524],{"id":1523},"measured-impact","Measured Impact",[57,1526,1527,1540],{},[60,1528,1529],{},[63,1530,1531,1534,1537],{},[66,1532,1533],{},"Measure",[66,1535,1536],{},"14 separate workflows",[66,1538,1539],{},"Shared workflow",[76,1541,1542,1553,1564,1573,1584,1593],{},[63,1543,1544,1547,1550],{},[81,1545,1546],{},"Lines of workflow YAML across repositories",[81,1548,1549],{},"2,380",[81,1551,1552],{},"112 (callers) + 310 (shared)",[63,1554,1555,1558,1561],{},[81,1556,1557],{},"Sites with link checks and HTML validation",[81,1559,1560],{},"6 and 2",[81,1562,1563],{},"14 and 14",[63,1565,1566,1569,1571],{},[81,1567,1568],{},"Sites with dependency caching",[81,1570,97],{},[81,1572,86],{},[63,1574,1575,1578,1581],{},[81,1576,1577],{},"Median build-and-deploy time",[81,1579,1580],{},"3 min 40 s",[81,1582,1583],{},"2 min 10 s",[63,1585,1586,1589,1591],{},[81,1587,1588],{},"Long-lived deploy tokens",[81,1590,1168],{},[81,1592,181],{},[63,1594,1595,1598,1601],{},[81,1596,1597],{},"Time to roll out a pipeline fix to all sites",[81,1599,1600],{},"~2 days",[81,1602,1603],{},"1 tag + 14 automated PRs (~1 hour)",[27,1605,1607],{"id":1606},"pitfalls-rollback","Pitfalls & Rollback",[32,1609,1610,1621,1629,1635,1641],{},[35,1611,1612,1616,1617,1620],{},[1613,1614,1615],"strong",{},"Calling by branch."," ",[42,1618,1619],{},"@main"," changes under every site at once; call by tag or SHA.",[35,1622,1623,1628],{},[1613,1624,1625,1627],{},[42,1626,1358],{}," everywhere."," Pass only what the workflow needs.",[35,1630,1631,1634],{},[1613,1632,1633],{},"Too many inputs."," A shared workflow with forty inputs is fourteen workflows in disguise; keep special cases in the site repository as a pre-build step.",[35,1636,1637,1640],{},[1613,1638,1639],{},"Forgetting access settings."," Private shared repositories must allow access from the calling repositories.",[35,1642,1643,1646],{},[1613,1644,1645],{},"Rollback:"," each site's caller can pin the previous tag, or restore its old workflow file from Git history.",[27,1648,1650],{"id":1649},"conclusion","Conclusion",[14,1652,1653],{},"When an organisation runs many static sites, their pipelines should be one versioned definition, not many copies. A reusable workflow for the build-test-deploy path, composite actions for the pieces, explicit secrets and permissions, and deliberate upgrades by tag gave fourteen sites the same checks and caching, removed every long-lived deploy token, and turned a pipeline fix from a two-day chore into an hour of automated pull requests.",[27,1655,1657],{"id":1656},"faq","FAQ",[1659,1660,1662],"h3",{"id":1661},"what-is-a-reusable-workflow-in-github-actions","What is a reusable workflow in GitHub Actions?",[14,1664,1665],{},"A workflow file with an on workflow_call trigger that other workflows can call like a function, passing inputs and secrets. The called workflow runs its jobs in the caller's context, so one pipeline definition can serve many repositories.",[1659,1667,1669],{"id":1668},"when-should-i-use-a-composite-action-instead","When should I use a composite action instead?",[14,1671,1672],{},"Composite actions package a sequence of steps that run inside a caller's job, which suits small reusable pieces such as setting up Node with caching or running a link check. Reusable workflows package whole jobs, with their own runners, permissions and dependencies, which suits complete build and deploy pipelines.",[1659,1674,1676],{"id":1675},"how-should-shared-workflows-be-versioned","How should shared workflows be versioned?",[14,1678,1679],{},"Call them by a tag or commit SHA rather than a branch, for example uses org\u002Fci\u002F.github\u002Fworkflows\u002Fssg.yml@v3. Publish changes as new tags and let each site upgrade deliberately, ideally through automated dependency pull requests.",[1659,1681,1683],{"id":1682},"can-a-reusable-workflow-access-the-callers-secrets","Can a reusable workflow access the caller's secrets?",[14,1685,1686],{},"Only secrets passed explicitly, or all of them with secrets inherit when caller and callee are in the same organization. Passing only the secrets a workflow needs keeps the blast radius small.",[27,1688,1690],{"id":1689},"related","Related",[32,1692,1693,1701,1708,1715,1720],{},[35,1694,1695,1616,1698,1700],{},[1613,1696,1697],{},"Parent:",[21,1699,24],{"href":23}," — building static sites in Actions.",[35,1702,1703,1707],{},[21,1704,1706],{"href":1705},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos\u002F","Matrix Builds for Multi-Site Monorepos"," — many sites in one repository instead.",[35,1709,1710,1714],{},[21,1711,1713],{"href":1712},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds\u002F","Concurrency Groups to Cancel Stale Builds"," — a setting worth sharing.",[35,1716,1717,1719],{},[21,1718,1344],{"href":1343}," — versioning third-party actions.",[35,1721,1722,1726],{},[21,1723,1725],{"href":1724},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002F","Testing Static Sites in CI"," — the checks the shared workflow runs.",[1728,1729,1730],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}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 .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}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);}",{"title":289,"searchDepth":303,"depth":303,"links":1732},[1733,1734,1735,1736,1737,1738,1739,1740,1741,1742,1743,1744,1750],{"id":29,"depth":303,"text":30},{"id":51,"depth":303,"text":52},{"id":281,"depth":303,"text":282},{"id":1180,"depth":303,"text":1181},{"id":1325,"depth":303,"text":1326},{"id":1348,"depth":303,"text":1349},{"id":1495,"depth":303,"text":1496},{"id":1502,"depth":303,"text":1503},{"id":1523,"depth":303,"text":1524},{"id":1606,"depth":303,"text":1607},{"id":1649,"depth":303,"text":1650},{"id":1656,"depth":303,"text":1657,"children":1745},[1746,1747,1748,1749],{"id":1661,"depth":318,"text":1662},{"id":1668,"depth":318,"text":1669},{"id":1675,"depth":318,"text":1676},{"id":1682,"depth":318,"text":1683},{"id":1689,"depth":303,"text":1690},[1752,1755,1758,1759],{"name":1753,"item":1754},"Home","\u002F",{"name":1756,"item":1757},"Production-Ready Deployment & CI\u002FCD for SSGs","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":24,"item":23},{"name":5,"item":1760},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds\u002F","2026-09-25","Share one build, test and deploy pipeline across many static sites with GitHub Actions reusable workflows and composite actions, versioned and called by tag.","md",[1765,1766,1767,1768],{"q":1662,"a":1665},{"q":1669,"a":1672},{"q":1676,"a":1679},{"q":1683,"a":1686},{},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds",{"title":5,"description":1762},"production-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds\u002Findex","article","5ZNBkO3lyzP63AMBj9Rjq731_35JUPHrqxKI-znW9fI",[1776,1779,1782,1785,1788,1791,1794,1797,1800,1803,1806,1809,1812,1815,1818,1821,1824,1827,1830,1833,1836,1839,1842,1845,1848,1851,1854,1857,1860,1863,1866,1869,1872,1875,1878,1881,1884,1887,1890,1893,1896,1899,1902,1905,1908,1911,1914,1917,1920,1923,1926,1929,1932,1935,1938,1941,1944,1947,1950,1953,1956,1959,1962,1965,1968,1971,1974,1977,1980,1983,1986,1989,1992,1995,1998,2001,2004,2007,2010,2013,2016,2019,2022,2025,2028,2031,2034,2037,2040,2043,2046,2049,2052,2055,2058,2061,2064,2067,2070,2073,2076,2079,2082,2085,2088,2091,2094,2097,2100,2103,2106,2109,2112,2115,2118,2121,2124,2127,2130,2133,2136,2139,2142,2145,2148,2151,2154,2157,2160,2163,2166,2169,2172,2175,2178,2181,2184,2187,2190,2193,2196,2199,2202,2205,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,2481,2484,2487,2490,2493,2496,2499,2502,2505,2508,2511,2514,2517,2520,2523,2526,2529,2532,2535,2538,2541,2544,2547,2550,2552,2555,2558,2561,2564,2567,2570,2573,2576,2579,2582,2585,2588,2590,2593,2596,2599,2602,2604,2606,2608,2611,2612,2615,2618,2621,2624,2627,2630,2633,2636,2639,2642,2645,2647,2650,2653,2656,2659,2662,2665,2668,2671,2674,2677,2680,2683,2686,2689,2692,2695,2698,2701,2704,2707,2710,2713,2716,2719,2722,2725,2728,2731,2734,2737,2740,2743,2746,2749,2752,2755,2758,2761,2764,2767,2770,2773,2776,2779,2782,2785,2788,2791,2794,2797,2800,2803,2806,2808,2811,2814,2817,2820,2823,2826,2829,2832,2835,2838,2841,2844,2847,2850,2853,2856,2859,2862,2865,2868,2871,2874,2877,2880,2883,2886,2889,2892,2895,2898,2900,2903,2906,2909,2912],{"path":1777,"title":1778},"\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":1780,"title":1781},"\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":1783,"title":1784},"\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":1786,"title":1787},"\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":1789,"title":1790},"\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":1792,"title":1793},"\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":1795,"title":1796},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1798,"title":1799},"\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":1801,"title":1802},"\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":1804,"title":1805},"\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":1807,"title":1808},"\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":1810,"title":1811},"\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":1813,"title":1814},"\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":1816,"title":1817},"\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":1819,"title":1820},"\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":1822,"title":1823},"\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":1825,"title":1826},"\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":1828,"title":1829},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1831,"title":1832},"\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":1834,"title":1835},"\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":1837,"title":1838},"\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":1840,"title":1841},"\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":1843,"title":1844},"\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":1846,"title":1847},"\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":1849,"title":1850},"\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":1852,"title":1853},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1855,"title":1856},"\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":1858,"title":1859},"\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":1861,"title":1862},"\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":1864,"title":1865},"\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":1867,"title":1868},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1870,"title":1871},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1873,"title":1874},"\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":1876,"title":1877},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1879,"title":1880},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1882,"title":1883},"\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":1885,"title":1886},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1888,"title":1889},"\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":1891,"title":1892},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1894,"title":1895},"\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":1897,"title":1898},"\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":1900,"title":1901},"\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":1903,"title":1904},"\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":1906,"title":1907},"\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":1909,"title":1910},"\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":1912,"title":1913},"\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":1915,"title":1916},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1918,"title":1919},"\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":1921,"title":1922},"\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":1924,"title":1925},"\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":1927,"title":1928},"\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":1930,"title":1931},"\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":1933,"title":1934},"\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":1936,"title":1937},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1939,"title":1940},"\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":1942,"title":1943},"\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":1945,"title":1946},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1948,"title":1949},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1951,"title":1952},"\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":1954,"title":1955},"\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":1957,"title":1958},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1960,"title":1961},"\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":1963,"title":1964},"\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":1966,"title":1967},"\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":1969,"title":1970},"\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":1972,"title":1973},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1975,"title":1976},"\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":1978,"title":1979},"\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":1981,"title":1982},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1984,"title":1985},"\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":1987,"title":1988},"\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":1990,"title":1991},"\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":1993,"title":1994},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1996,"title":1997},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1999,"title":2000},"\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":2002,"title":2003},"\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":2005,"title":2006},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":2008,"title":2009},"\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":2011,"title":2012},"\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":2014,"title":2015},"\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":2017,"title":2018},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":2020,"title":2021},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":2023,"title":2024},"\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":2026,"title":2027},"\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":2029,"title":2030},"\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":2032,"title":2033},"\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":2035,"title":2036},"\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":2038,"title":2039},"\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":2041,"title":2042},"\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":2044,"title":2045},"\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":2047,"title":2048},"\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":2050,"title":2051},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":2053,"title":2054},"\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":2056,"title":2057},"\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":2059,"title":2060},"\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":2062,"title":2063},"\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":2065,"title":2066},"\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":2068,"title":2069},"\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":2071,"title":2072},"\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":2074,"title":2075},"\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":2077,"title":2078},"\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":2080,"title":2081},"\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":2083,"title":2084},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":2086,"title":2087},"\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":2089,"title":2090},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":2092,"title":2093},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":2095,"title":2096},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":2098,"title":2099},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":2101,"title":2102},"\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":2104,"title":2105},"\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":2107,"title":2108},"\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":2110,"title":2111},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":2113,"title":2114},"\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":2116,"title":2117},"\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":2119,"title":2120},"\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":2122,"title":2123},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":2125,"title":2126},"\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":2128,"title":2129},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":2131,"title":2132},"\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":2134,"title":2135},"\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":2137,"title":2138},"\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":2140,"title":2141},"\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":2143,"title":2144},"\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":2146,"title":2147},"\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":2149,"title":2150},"\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":2152,"title":2153},"\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":2155,"title":2156},"\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":2158,"title":2159},"\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":2161,"title":2162},"\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":2164,"title":2165},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":2167,"title":2168},"\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":2170,"title":2171},"\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":2173,"title":2174},"\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":2176,"title":2177},"\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":2179,"title":2180},"\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":2182,"title":2183},"\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":2185,"title":2186},"\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":2188,"title":2189},"\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":2191,"title":2192},"\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":2194,"title":2195},"\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":2197,"title":2198},"\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":2200,"title":2201},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":2203,"title":2204},"\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":2206,"title":2207},"\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":2209,"title":2210},"\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":2212,"title":2213},"\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":2215,"title":2216},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":2218,"title":2219},"\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":2221,"title":2222},"\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":2224,"title":2225},"\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":2227,"title":2228},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":2230,"title":2231},"\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":2233,"title":2234},"\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":2236,"title":2237},"\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":2239,"title":2240},"\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":2242,"title":2243},"\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":2245,"title":2246},"\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":2248,"title":2249},"\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":2251,"title":2252},"\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":2254,"title":2255},"\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":2257,"title":2258},"\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":2260,"title":2261},"\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":2263,"title":2264},"\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":2266,"title":2267},"\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":2269,"title":2270},"\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":2272,"title":2273},"\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":2275,"title":2276},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":2278,"title":2279},"\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":2281,"title":2282},"\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":2284,"title":2285},"\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":2287,"title":2288},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":2290,"title":2291},"\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":2293,"title":2294},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":2296,"title":2297},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":2299,"title":2300},"\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":2302,"title":2303},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":2305,"title":2306},"\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":2308,"title":2309},"\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":2311,"title":2312},"\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":2314,"title":2315},"\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":2317,"title":2318},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":2320,"title":2321},"\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":2323,"title":2324},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":2326,"title":2327},"\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":2329,"title":2330},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":2332,"title":2333},"\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":2335,"title":2336},"\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":2338,"title":2339},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":2341,"title":2342},"\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":2344,"title":2345},"\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":2347,"title":2348},"\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":2350,"title":2351},"\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":2353,"title":2354},"\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":2356,"title":2357},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":2359,"title":2360},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":2362,"title":2363},"\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":2365,"title":2366},"\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":2368,"title":2369},"\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":2371,"title":2372},"\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":2374,"title":2375},"\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":2377,"title":2378},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":2380,"title":2381},"\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":2383,"title":2384},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":2386,"title":2387},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":2389,"title":2390},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":2392,"title":2393},"\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":2395,"title":2396},"\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":2398,"title":2399},"\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":2401,"title":2402},"\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":2404,"title":2405},"\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":2407,"title":2408},"\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":2410,"title":2411},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":2413,"title":2414},"\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":2416,"title":2417},"\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":2419,"title":2420},"\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":2422,"title":2423},"\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":2425,"title":2426},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":2428,"title":2429},"\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":2431,"title":2432},"\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":2434,"title":2435},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":2437,"title":2438},"\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":2440,"title":2441},"\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":2443,"title":2444},"\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":2446,"title":2447},"\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":2449,"title":2450},"\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":2452,"title":2453},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2455,"title":2456},"\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":2458,"title":2459},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2461,"title":2462},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2464,"title":2465},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2467,"title":2468},"\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":2470,"title":2471},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2473,"title":2474},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2476,"title":2477},"\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":2479,"title":2480},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2482,"title":2483},"\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":2485,"title":2486},"\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":2488,"title":2489},"\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":2491,"title":2492},"\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":2494,"title":2495},"\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":2497,"title":2498},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2500,"title":2501},"\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":2503,"title":2504},"\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":2506,"title":2507},"\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":2509,"title":2510},"\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":2512,"title":2513},"\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":2515,"title":2516},"\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":2518,"title":2519},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2521,"title":2522},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2524,"title":2525},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2527,"title":2528},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2530,"title":2531},"\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":2533,"title":2534},"\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":2536,"title":2537},"\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":2539,"title":2540},"\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":2542,"title":2543},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2545,"title":2546},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2548,"title":2549},"\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":2551,"title":1317},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests",{"path":2553,"title":2554},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2556,"title":2557},"\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":2559,"title":2560},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2562,"title":2563},"\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":2565,"title":2566},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2568,"title":2569},"\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":2571,"title":2572},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2574,"title":2575},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2577,"title":2578},"\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":2580,"title":2581},"\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":2583,"title":2584},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2586,"title":2587},"\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":2589,"title":1713},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds",{"path":2591,"title":2592},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2594,"title":2595},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-multiple-environments-from-one-workflow","Deploying to Multiple Environments From One Workflow",{"path":2597,"title":2598},"\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":2600,"title":2601},"\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":2603,"title":24},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds",{"path":2605,"title":1706},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos",{"path":2607,"title":1344},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha",{"path":2609,"title":2610},"\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":1770,"title":5},{"path":2613,"title":2614},"\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":2616,"title":2617},"\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":2619,"title":2620},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2622,"title":2623},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2625,"title":2626},"\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":2628,"title":2629},"\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":2631,"title":2632},"\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":2634,"title":2635},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2637,"title":2638},"\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":2640,"title":2641},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fremote-caching-with-turborepo-for-ssg-monorepos","Remote Caching with Turborepo for SSG Monorepos",{"path":2643,"title":2644},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fsharing-build-cache-across-ci-runners","Sharing Build Cache Across CI Runners",{"path":2646,"title":1756},"\u002Fproduction-ready-deployment-cicd-workflows",{"path":2648,"title":2649},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2651,"title":2652},"\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":2654,"title":2655},"\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":2657,"title":2658},"\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":2660,"title":2661},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2663,"title":2664},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2666,"title":2667},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2669,"title":2670},"\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":2672,"title":2673},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2675,"title":2676},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2678,"title":2679},"\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":2681,"title":2682},"\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":2684,"title":2685},"\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":2687,"title":2688},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2690,"title":2691},"\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":2693,"title":2694},"\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":2696,"title":2697},"\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":2699,"title":2700},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2702,"title":2703},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2705,"title":2706},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2708,"title":2709},"\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":2711,"title":2712},"\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":2714,"title":2715},"\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":2717,"title":2718},"\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":2720,"title":2721},"\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":2723,"title":2724},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2726,"title":2727},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2729,"title":2730},"\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":2732,"title":2733},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2735,"title":2736},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2738,"title":2739},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2741,"title":2742},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2744,"title":2745},"\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":2747,"title":2748},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2750,"title":2751},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2753,"title":2754},"\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":2756,"title":2757},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2759,"title":2760},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2762,"title":2763},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2765,"title":2766},"\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":2768,"title":2769},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2771,"title":2772},"\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":2774,"title":2775},"\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":2777,"title":2778},"\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":2780,"title":2781},"\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":2783,"title":2784},"\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":2786,"title":2787},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2789,"title":2790},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2792,"title":2793},"\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":2795,"title":2796},"\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":2798,"title":2799},"\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":2801,"title":2802},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2804,"title":2805},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2807,"title":1367},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc",{"path":2809,"title":2810},"\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":2812,"title":2813},"\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":2815,"title":2816},"\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":2818,"title":2819},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2821,"title":2822},"\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":2824,"title":2825},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2827,"title":2828},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2830,"title":2831},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2833,"title":2834},"\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":2836,"title":2837},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2839,"title":2840},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2842,"title":2843},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2845,"title":2846},"\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":2848,"title":2849},"\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":2851,"title":2852},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2854,"title":2855},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2857,"title":2858},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2860,"title":2861},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2863,"title":2864},"\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":2866,"title":2867},"\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":2869,"title":2870},"\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":2872,"title":2873},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2875,"title":2876},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2878,"title":2879},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2881,"title":2882},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2884,"title":2885},"\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":2887,"title":2888},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2890,"title":2891},"\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":2893,"title":2894},"\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":2896,"title":2897},"\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":2899,"title":1725},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci",{"path":2901,"title":2902},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2904,"title":2905},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2907,"title":2908},"\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":2910,"title":2911},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2913,"title":1322},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci",{"kind":2915,"tools":2919},{"label":2916,"plural":2917,"u":2918},"How-to","How-tos","\u002Fguides\u002Fhow-to\u002F",[2920],{"label":2921,"u":2922},"GitHub Actions","\u002Ftools\u002Fgithub-actions\u002F",1790943195819]