[{"data":1,"prerenderedAt":2480},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-netlify-deploys-from-the-cli-and-api":3,"all-docs-nav":1330,"filed:\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-netlify-deploys-from-the-cli-and-api":2471},{"id":4,"title":5,"body":6,"breadcrumb":1305,"dateModified":1315,"datePublished":1315,"description":1316,"extension":1317,"faq":1318,"meta":1323,"navigation":1324,"path":1325,"seo":1326,"slug":12,"stem":1327,"type":1328,"__hash__":1329},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-netlify-deploys-from-the-cli-and-api\u002Findex.md","Rolling Back Netlify Deploys From the CLI and API",{"type":7,"value":8,"toc":1284},"minimark",[9,13,17,31,36,67,71,140,148,158,162,169,278,296,451,455,687,693,697,709,713,723,789,792,919,923,926,1051,1054,1058,1064,1068,1071,1075,1078,1159,1162,1166,1199,1203,1206,1210,1215,1218,1222,1225,1229,1232,1236,1239,1243,1280],[10,11,5],"h1",{"id":12},"rolling-back-netlify-deploys-from-the-cli-and-api",[14,15,16],"p",{},"Netlify keeps every deploy, and the dashboard has a \"Publish deploy\" button on each one. During an incident, that button is not always within reach: the person on call may not have dashboard access, the team may require changes to go through auditable automation, or the rollback may need to be part of a script that also notifies people and checks the result. Netlify's API exposes the same operation, and wrapping it gives a rollback that anyone with repository access can trigger in one click, that locks out the next automatic deploy, and that verifies the site afterwards.",[14,18,19,20,25,26,30],{},"This guide builds that for a marketing site and docs on Netlify: finding the right deploy, restoring it through the API, locking auto-publishing, verifying, and unlocking when the fix lands. It belongs to ",[21,22,24],"a",{"href":23},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002F","Rollbacks and Deploy Safety for Static Sites","; the general case is in ",[21,27,29],{"href":28},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-a-bad-static-deploy-in-under-a-minute\u002F","Rolling Back a Bad Static Deploy in Under a Minute",".",[32,33,35],"h2",{"id":34},"prerequisites","Prerequisites",[37,38,39,47,53],"ul",{},[40,41,42,43,30],"li",{},"A Netlify personal access token or, better, a token for a dedicated team member account used only by automation, stored as ",[44,45,46],"code",{},"NETLIFY_AUTH_TOKEN",[40,48,49,50,30],{},"The site ID, stored as ",[44,51,52],{},"NETLIFY_SITE_ID",[40,54,55,56,59,60,63,64,30],{},"The Netlify CLI (",[44,57,58],{},"netlify-cli",") or ",[44,61,62],{},"curl"," and ",[44,65,66],{},"jq",[32,68,70],{"id":69},"step-1-list-recent-production-deploys","Step 1: List Recent Production Deploys",[72,73,78],"pre",{"className":74,"code":75,"language":76,"meta":77,"style":77},"language-sh shiki shiki-themes github-light github-dark","curl -s -H \"Authorization: Bearer $NETLIFY_AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fapi.netlify.com\u002Fapi\u002Fv1\u002Fsites\u002F$NETLIFY_SITE_ID\u002Fdeploys?production=true&state=ready&per_page=10\" |\n  jq -r '.[] | [.id, .created_at, .commit_ref[0:7], (.title \u002F\u002F \"\")[0:60]] | @tsv'\n","sh","",[44,79,80,109,125],{"__ignoreMap":77},[81,82,85,88,92,95,99,103,106],"span",{"class":83,"line":84},"line",1,[81,86,62],{"class":87},"sScJk",[81,89,91],{"class":90},"sj4cs"," -s",[81,93,94],{"class":90}," -H",[81,96,98],{"class":97},"sZZnC"," \"Authorization: Bearer ",[81,100,102],{"class":101},"sVt8B","$NETLIFY_AUTH_TOKEN",[81,104,105],{"class":97},"\"",[81,107,108],{"class":90}," \\\n",[81,110,112,115,118,121],{"class":83,"line":111},2,[81,113,114],{"class":97},"  \"https:\u002F\u002Fapi.netlify.com\u002Fapi\u002Fv1\u002Fsites\u002F",[81,116,117],{"class":101},"$NETLIFY_SITE_ID",[81,119,120],{"class":97},"\u002Fdeploys?production=true&state=ready&per_page=10\"",[81,122,124],{"class":123},"szBVR"," |\n",[81,126,128,131,134,137],{"class":83,"line":127},3,[81,129,130],{"class":87},"  jq",[81,132,133],{"class":90}," -r",[81,135,136],{"class":97}," '.[] | [.id, .created_at, .commit_ref[0:7], (.title",[81,138,139],{"class":97}," \u002F\u002F \"\")[0:60]] | @tsv'\n",[72,141,146],{"className":142,"code":144,"language":145,"meta":77},[143],"language-text","66f3a1…  2026-07-14T10:12:03Z  9c4e2b1  Update pricing table component\n66f39b…  2026-07-14T08:40:51Z  41d7a0e  Fix typo in getting started\n66f2e0…  2026-07-13T16:22:10Z  b88f312  Add September release notes\n","text",[44,147,144],{"__ignoreMap":77},[14,149,150,153,154,157],{},[44,151,152],{},"production=true"," excludes deploy previews and branch deploys; ",[44,155,156],{},"state=ready"," excludes failed builds. The deploy's commit and title make the right target obvious.",[32,159,161],{"id":160},"step-2-restore-and-lock","Step 2: Restore and Lock",[14,163,164,165,168],{},"Restoring publishes an existing deploy again. Locking stops the next push to ",[44,166,167],{},"main"," from automatically replacing it:",[72,170,172],{"className":74,"code":171,"language":76,"meta":77,"style":77},"DEPLOY=66f39b…   # the last good deploy\ncurl -s -X POST -H \"Authorization: Bearer $NETLIFY_AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fapi.netlify.com\u002Fapi\u002Fv1\u002Fsites\u002F$NETLIFY_SITE_ID\u002Fdeploys\u002F$DEPLOY\u002Frestore\" | jq -r '.state'\ncurl -s -X POST -H \"Authorization: Bearer $NETLIFY_AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fapi.netlify.com\u002Fapi\u002Fv1\u002Fdeploys\u002F$DEPLOY\u002Flock\" | jq -r '.locked'\n",[44,173,174,189,211,237,258],{"__ignoreMap":77},[81,175,176,179,182,185],{"class":83,"line":84},[81,177,178],{"class":101},"DEPLOY",[81,180,181],{"class":123},"=",[81,183,184],{"class":97},"66f39b…",[81,186,188],{"class":187},"sJ8bj","   # the last good deploy\n",[81,190,191,193,195,198,201,203,205,207,209],{"class":83,"line":111},[81,192,62],{"class":87},[81,194,91],{"class":90},[81,196,197],{"class":90}," -X",[81,199,200],{"class":97}," POST",[81,202,94],{"class":90},[81,204,98],{"class":97},[81,206,102],{"class":101},[81,208,105],{"class":97},[81,210,108],{"class":90},[81,212,213,215,217,220,223,226,229,232,234],{"class":83,"line":127},[81,214,114],{"class":97},[81,216,117],{"class":101},[81,218,219],{"class":97},"\u002Fdeploys\u002F",[81,221,222],{"class":101},"$DEPLOY",[81,224,225],{"class":97},"\u002Frestore\"",[81,227,228],{"class":123}," |",[81,230,231],{"class":87}," jq",[81,233,133],{"class":90},[81,235,236],{"class":97}," '.state'\n",[81,238,240,242,244,246,248,250,252,254,256],{"class":83,"line":239},4,[81,241,62],{"class":87},[81,243,91],{"class":90},[81,245,197],{"class":90},[81,247,200],{"class":97},[81,249,94],{"class":90},[81,251,98],{"class":97},[81,253,102],{"class":101},[81,255,105],{"class":97},[81,257,108],{"class":90},[81,259,261,264,266,269,271,273,275],{"class":83,"line":260},5,[81,262,263],{"class":97},"  \"https:\u002F\u002Fapi.netlify.com\u002Fapi\u002Fv1\u002Fdeploys\u002F",[81,265,222],{"class":101},[81,267,268],{"class":97},"\u002Flock\"",[81,270,228],{"class":123},[81,272,231],{"class":87},[81,274,133],{"class":90},[81,276,277],{"class":97}," '.locked'\n",[14,279,280,281,63,284,287,288,291,292,295],{},"The CLI equivalent uses ",[44,282,283],{},"netlify api restoreSiteDeploy --data '{\"site_id\": \"…\", \"deploy_id\": \"…\"}'",[44,285,286],{},"netlify api lockDeploy",". Restoring took 3–5 seconds to go live in drills; nothing is rebuilt, and the deploy's own ",[44,289,290],{},"_redirects",", ",[44,293,294],{},"_headers"," and functions come with it.",[297,298,299,447],"figure",{},[300,301,308,309,308,313,308,317,308,324,308,432],"svg",{"viewBox":302,"role":303,"ariaLabelledBy":304,"xmlns":307},"0 0 760 313","img",[305,306],"nlroll-seq-title","nlroll-seq-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[310,311,312],"title",{"id":305},"Sequence of a Netlify rollback triggered from GitHub Actions",[314,315,316],"desc",{"id":306},"Four actors, the on-call person, GitHub Actions, the Netlify API and the live site. The on-call person starts the rollback workflow and picks a deploy. The workflow calls restore on that deploy, and the site serves it within seconds. The workflow locks the deploy so auto-publishing stops. It runs smoke checks against the live site and posts the result to the incident channel.",[318,319],"rect",{"x":320,"y":320,"width":321,"height":322,"fill":323},"0","760","313","#ffffff",[325,326,328,329,328,339,328,342,328,345,328,348,328,355,328,358,328,362,328,365,328,368,328,372,328,375,328,378,328,381,328,387,328,393,328,397,328,401,328,405,328,411,328,415,328,419,328,424,328,428,308],"g",{"style":327},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[318,330],{"x":331,"y":332,"width":333,"height":334,"rx":335,"fill":336,"stroke":337,"style":338},"30.0","56.0","160.0","42.9","8","#f8fafc","#d9e2ef","stroke-width:1.5px",[318,340],{"x":341,"y":332,"width":333,"height":334,"rx":335,"fill":336,"stroke":337,"style":338},"210.0",[318,343],{"x":344,"y":332,"width":333,"height":334,"rx":335,"fill":336,"stroke":337,"style":338},"390.0",[318,346],{"x":347,"y":332,"width":333,"height":334,"rx":335,"fill":336,"stroke":337,"style":338},"570.0",[349,350],"path",{"d":351,"fill":352,"stroke":353,"style":354},"M114.0 148.8 L284.0 148.8","none","#556071","stroke-width:1.8px;marker-end:url(#nlroll-seq-arrow)",[349,356],{"d":357,"fill":352,"stroke":353,"style":354},"M294.0 181.8 L464.0 181.8",[349,359],{"d":360,"fill":352,"stroke":353,"style":361},"M474.0 214.7 L644.0 214.7","stroke-width:1.8px;stroke-dasharray:5 4;marker-end:url(#nlroll-seq-arrow)",[349,363],{"d":364,"fill":352,"stroke":353,"style":354},"M294.0 247.6 L464.0 247.6",[349,366],{"d":367,"fill":352,"stroke":353,"style":354},"M294.0 280.6 L644.0 280.6",[349,369],{"d":370,"fill":352,"stroke":337,"style":371},"M110.0 100.9 L110.0 296.6","stroke-width:1.5px;stroke-dasharray:4 4",[349,373],{"d":374,"fill":352,"stroke":337,"style":371},"M290.0 100.9 L290.0 296.6",[349,376],{"d":377,"fill":352,"stroke":337,"style":371},"M470.0 100.9 L470.0 296.6",[349,379],{"d":380,"fill":352,"stroke":337,"style":371},"M650.0 100.9 L650.0 296.6",[145,382,386],{"x":383,"y":331,"fill":384,"style":385},"380.0","#1f2937","font-size:16px;text-anchor:middle;font-weight:700","A rollback through the API",[145,388,392],{"x":389,"y":390,"fill":384,"style":391},"110.0","82.7","font-size:13px;text-anchor:middle;font-weight:700","On-call",[145,394,396],{"x":395,"y":390,"fill":384,"style":391},"290.0","GitHub Actions",[145,398,400],{"x":399,"y":390,"fill":384,"style":391},"470.0","Netlify API",[145,402,404],{"x":403,"y":390,"fill":384,"style":391},"650.0","Live site",[145,406,410],{"x":407,"y":408,"fill":384,"style":409},"200.0","125.8","font-size:11.5px;text-anchor:middle","run rollback workflow",[145,412,414],{"x":407,"y":413,"fill":384,"style":409},"140.8","(deploy id)",[145,416,418],{"x":383,"y":417,"fill":384,"style":409},"173.7","POST \u002Fdeploys\u002Fid\u002Frestore",[145,420,423],{"x":421,"y":422,"fill":353,"style":409},"560.0","206.7","previous deploy live (~4 s)",[145,425,427],{"x":383,"y":426,"fill":384,"style":409},"239.6","POST \u002Fdeploys\u002Fid\u002Flock",[145,429,431],{"x":399,"y":430,"fill":384,"style":409},"272.6","smoke checks",[433,434,328,435,308],"defs",{},[436,437,443,444,328],"marker",{"id":438,"viewBox":439,"refX":335,"refY":440,"markerWidth":441,"markerHeight":441,"orient":442},"nlroll-seq-arrow","0 0 10 10","5","7","auto-start-reverse","\n      ",[349,445],{"d":446,"fill":353},"M0 0 L10 5 L0 10 z",[448,449,450],"figcaption",{},"Locking is the step people forget; without it the next merge silently undoes the rollback.",[32,452,454],{"id":453},"step-3-wrap-it-in-a-workflow","Step 3: Wrap It in a Workflow",[72,456,460],{"className":457,"code":458,"language":459,"meta":77,"style":77},"language-yaml shiki shiki-themes github-light github-dark","name: rollback\non:\n  workflow_dispatch:\n    inputs:\n      deploy_id: { description: 'Netlify deploy ID to restore (blank = previous production deploy)', required: false }\njobs:\n  rollback:\n    runs-on: ubuntu-latest\n    environment: production-rollback      # requires approval from a maintainer\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - name: Restore and lock\n        env: { NETLIFY_AUTH_TOKEN: '${{ secrets.NETLIFY_AUTH_TOKEN }}', NETLIFY_SITE_ID: '${{ secrets.NETLIFY_SITE_ID }}' }\n        run: node scripts\u002Fnetlify-rollback.mjs \"${{ inputs.deploy_id }}\"\n      - name: Smoke checks\n        run: npx playwright test -c smoke\u002Fplaywright.config.ts\n      - if: always()\n        run: node scripts\u002Fnotify.mjs \"Rollback ${{ job.status }}: ${{ inputs.deploy_id || 'previous' }}\"\n","yaml",[44,461,462,474,482,489,496,525,533,541,552,566,574,588,600,626,637,649,659,672],{"__ignoreMap":77},[81,463,464,468,471],{"class":83,"line":84},[81,465,467],{"class":466},"s9eBZ","name",[81,469,470],{"class":101},": ",[81,472,473],{"class":97},"rollback\n",[81,475,476,479],{"class":83,"line":111},[81,477,478],{"class":90},"on",[81,480,481],{"class":101},":\n",[81,483,484,487],{"class":83,"line":127},[81,485,486],{"class":466},"  workflow_dispatch",[81,488,481],{"class":101},[81,490,491,494],{"class":83,"line":239},[81,492,493],{"class":466},"    inputs",[81,495,481],{"class":101},[81,497,498,501,504,507,509,512,514,517,519,522],{"class":83,"line":260},[81,499,500],{"class":466},"      deploy_id",[81,502,503],{"class":101},": { ",[81,505,506],{"class":466},"description",[81,508,470],{"class":101},[81,510,511],{"class":97},"'Netlify deploy ID to restore (blank = previous production deploy)'",[81,513,291],{"class":101},[81,515,516],{"class":466},"required",[81,518,470],{"class":101},[81,520,521],{"class":90},"false",[81,523,524],{"class":101}," }\n",[81,526,528,531],{"class":83,"line":527},6,[81,529,530],{"class":466},"jobs",[81,532,481],{"class":101},[81,534,536,539],{"class":83,"line":535},7,[81,537,538],{"class":466},"  rollback",[81,540,481],{"class":101},[81,542,544,547,549],{"class":83,"line":543},8,[81,545,546],{"class":466},"    runs-on",[81,548,470],{"class":101},[81,550,551],{"class":97},"ubuntu-latest\n",[81,553,555,558,560,563],{"class":83,"line":554},9,[81,556,557],{"class":466},"    environment",[81,559,470],{"class":101},[81,561,562],{"class":97},"production-rollback",[81,564,565],{"class":187},"      # requires approval from a maintainer\n",[81,567,569,572],{"class":83,"line":568},10,[81,570,571],{"class":466},"    steps",[81,573,481],{"class":101},[81,575,577,580,583,585],{"class":83,"line":576},11,[81,578,579],{"class":101},"      - ",[81,581,582],{"class":466},"uses",[81,584,470],{"class":101},[81,586,587],{"class":97},"actions\u002Fcheckout@v4\n",[81,589,591,593,595,597],{"class":83,"line":590},12,[81,592,579],{"class":101},[81,594,467],{"class":466},[81,596,470],{"class":101},[81,598,599],{"class":97},"Restore and lock\n",[81,601,603,606,608,610,612,615,617,619,621,624],{"class":83,"line":602},13,[81,604,605],{"class":466},"        env",[81,607,503],{"class":101},[81,609,46],{"class":466},[81,611,470],{"class":101},[81,613,614],{"class":97},"'${{ secrets.NETLIFY_AUTH_TOKEN }}'",[81,616,291],{"class":101},[81,618,52],{"class":466},[81,620,470],{"class":101},[81,622,623],{"class":97},"'${{ secrets.NETLIFY_SITE_ID }}'",[81,625,524],{"class":101},[81,627,629,632,634],{"class":83,"line":628},14,[81,630,631],{"class":466},"        run",[81,633,470],{"class":101},[81,635,636],{"class":97},"node scripts\u002Fnetlify-rollback.mjs \"${{ inputs.deploy_id }}\"\n",[81,638,640,642,644,646],{"class":83,"line":639},15,[81,641,579],{"class":101},[81,643,467],{"class":466},[81,645,470],{"class":101},[81,647,648],{"class":97},"Smoke checks\n",[81,650,652,654,656],{"class":83,"line":651},16,[81,653,631],{"class":466},[81,655,470],{"class":101},[81,657,658],{"class":97},"npx playwright test -c smoke\u002Fplaywright.config.ts\n",[81,660,662,664,667,669],{"class":83,"line":661},17,[81,663,579],{"class":101},[81,665,666],{"class":466},"if",[81,668,470],{"class":101},[81,670,671],{"class":97},"always()\n",[81,673,675,677,679,682,684],{"class":83,"line":674},18,[81,676,631],{"class":466},[81,678,470],{"class":101},[81,680,681],{"class":466},"node scripts\u002Fnotify.mjs \"Rollback ${{ job.status }}",[81,683,470],{"class":101},[81,685,686],{"class":97},"${{ inputs.deploy_id || 'previous' }}\"\n",[14,688,689,690,692],{},"The script picks the second most recent ready production deploy when no ID is given, restores and locks it, and prints both deploy titles to the job log. The ",[44,691,562],{}," environment requires one maintainer approval, which in practice is given by whoever is on the incident call within a minute — and it means the rollback is recorded with who approved it.",[32,694,696],{"id":695},"step-4-verify-the-restore","Step 4: Verify the Restore",[14,698,699,700,703,704,708],{},"The smoke checks request a dozen key pages and their assets, confirm a 200 for each, and compare the build ID in a ",[44,701,702],{},"\u003Cmeta name=\"build-id\">"," tag with the restored deploy's commit. A mismatch means the restore did not take — for example, if someone published another deploy from the dashboard at the same moment. ",[21,705,707],{"href":706},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists\u002F","Post-Deploy Verification Checklists"," lists what else to check.",[32,710,712],{"id":711},"step-5-unlock-when-the-fix-lands","Step 5: Unlock When the Fix Lands",[14,714,715,716,718,719,722],{},"While locked, pushes to ",[44,717,167],{}," still build, and their deploys are ready but not published. When the fix is merged and its deploy is verified as a preview, an ",[44,720,721],{},"unlock"," workflow unlocks the locked deploy and publishes the fix:",[72,724,726],{"className":74,"code":725,"language":76,"meta":77,"style":77},"curl -s -X POST -H \"Authorization: Bearer $NETLIFY_AUTH_TOKEN\" \"https:\u002F\u002Fapi.netlify.com\u002Fapi\u002Fv1\u002Fdeploys\u002F$LOCKED\u002Funlock\"\ncurl -s -X POST -H \"Authorization: Bearer $NETLIFY_AUTH_TOKEN\" \\\n  \"https:\u002F\u002Fapi.netlify.com\u002Fapi\u002Fv1\u002Fsites\u002F$NETLIFY_SITE_ID\u002Fdeploys\u002F$FIX_DEPLOY\u002Frestore\"\n",[44,727,728,755,775],{"__ignoreMap":77},[81,729,730,732,734,736,738,740,742,744,746,749,752],{"class":83,"line":84},[81,731,62],{"class":87},[81,733,91],{"class":90},[81,735,197],{"class":90},[81,737,200],{"class":97},[81,739,94],{"class":90},[81,741,98],{"class":97},[81,743,102],{"class":101},[81,745,105],{"class":97},[81,747,748],{"class":97}," \"https:\u002F\u002Fapi.netlify.com\u002Fapi\u002Fv1\u002Fdeploys\u002F",[81,750,751],{"class":101},"$LOCKED",[81,753,754],{"class":97},"\u002Funlock\"\n",[81,756,757,759,761,763,765,767,769,771,773],{"class":83,"line":111},[81,758,62],{"class":87},[81,760,91],{"class":90},[81,762,197],{"class":90},[81,764,200],{"class":97},[81,766,94],{"class":90},[81,768,98],{"class":97},[81,770,102],{"class":101},[81,772,105],{"class":97},[81,774,108],{"class":90},[81,776,777,779,781,783,786],{"class":83,"line":127},[81,778,114],{"class":97},[81,780,117],{"class":101},[81,782,219],{"class":97},[81,784,785],{"class":101},"$FIX_DEPLOY",[81,787,788],{"class":97},"\u002Frestore\"\n",[14,790,791],{},"A reminder posts to the incident channel every two hours while a deploy is locked, because a forgotten lock silently stops every subsequent release.",[297,793,794,916],{},[300,795,308,800,308,803,308,806,308,809,308,909],{"viewBox":796,"role":303,"ariaLabelledBy":797,"xmlns":307},"0 0 760 166",[798,799],"nlroll-drill-title","nlroll-drill-desc",[310,801,802],{"id":798},"Timeline of a rollback drill using the workflow",[314,804,805],{"id":799},"Six events. At 0 seconds the bad deploy is noticed. At 40 seconds the rollback workflow is started. At 75 seconds a maintainer approves it. At 82 seconds the previous deploy is live and locked. At 110 seconds smoke checks pass and the channel is notified. Later, the fix deploy is published and the lock removed.",[318,807],{"x":320,"y":320,"width":321,"height":808,"fill":323},"166",[325,810,328,811,328,815,328,822,328,827,328,830,328,835,328,838,328,842,328,845,328,850,328,853,328,856,328,859,328,862,328,865,328,871,328,876,328,880,328,883,328,886,328,889,328,893,328,896,328,899,328,902,328,906,308],{"style":327},[349,812],{"d":813,"fill":352,"stroke":353,"style":814},"M30.0 99.6 L734.0 99.6","stroke-width:2px;marker-end:url(#nlroll-drill-arrow)",[816,817],"circle",{"cx":818,"cy":819,"r":441,"fill":820,"stroke":821,"style":338},"60.0","99.6","#ff595e","#d83b41",[816,823],{"cx":824,"cy":819,"r":441,"fill":825,"stroke":826,"style":338},"188.0","#ffca3a","#a97b00",[816,828],{"cx":829,"cy":819,"r":441,"fill":825,"stroke":826,"style":338},"316.0",[816,831],{"cx":832,"cy":819,"r":441,"fill":833,"stroke":834,"style":338},"444.0","#8ac926","#5a8a16",[816,836],{"cx":837,"cy":819,"r":441,"fill":833,"stroke":834,"style":338},"572.0",[816,839],{"cx":840,"cy":819,"r":441,"fill":841,"stroke":841,"style":338},"700.0","#1982c4",[145,843,844],{"x":383,"y":331,"fill":384,"style":385},"A rollback drill, minute by minute",[145,846,849],{"x":818,"y":847,"fill":384,"style":848},"83.6","font-size:12px;text-anchor:middle;font-weight:700","Bad deploy noticed",[145,851,852],{"x":824,"y":847,"fill":384,"style":848},"Workflow started",[145,854,855],{"x":829,"y":847,"fill":384,"style":848},"Approved",[145,857,858],{"x":832,"y":847,"fill":384,"style":848},"Restored + locked",[145,860,861],{"x":837,"y":847,"fill":384,"style":848},"Smoke checks pass",[145,863,864],{"x":840,"y":847,"fill":384,"style":848},"Fix published",[145,866,870],{"x":818,"y":867,"fill":868,"style":869},"125.6","#b32b30","font-size:11.5px;text-anchor:middle;font-weight:700","0 s",[145,872,875],{"x":818,"y":873,"fill":353,"style":874},"143.6","font-size:11px;text-anchor:middle","alert",[145,877,879],{"x":824,"y":867,"fill":878,"style":869},"#8a6d0f","40 s",[145,881,882],{"x":824,"y":873,"fill":353,"style":874},"deploy chosen",[145,884,885],{"x":829,"y":867,"fill":878,"style":869},"75 s",[145,887,888],{"x":829,"y":873,"fill":353,"style":874},"environment gate",[145,890,892],{"x":832,"y":867,"fill":891,"style":869},"#3f6410","82 s",[145,894,895],{"x":832,"y":873,"fill":353,"style":874},"previous deploy live",[145,897,898],{"x":837,"y":867,"fill":891,"style":869},"110 s",[145,900,901],{"x":837,"y":873,"fill":353,"style":874},"channel notified",[145,903,905],{"x":840,"y":867,"fill":904,"style":869},"#166a9e","later",[145,907,908],{"x":840,"y":873,"fill":353,"style":874},"lock removed",[433,910,328,911,308],{},[436,912,443,914,328],{"id":913,"viewBox":439,"refX":335,"refY":440,"markerWidth":441,"markerHeight":441,"orient":442},"nlroll-drill-arrow",[349,915],{"d":446,"fill":353},[448,917,918],{},"Most of the time is human: noticing and approving. The restore itself takes seconds.",[32,920,922],{"id":921},"rollback-or-fix-forward","Rollback or Fix Forward?",[14,924,925],{},"Rollback is not always the right response, and the runbook says when to use it. A rollback restores the whole site to an older deploy, including every other change merged since. If three content pull requests merged after the bad one, rolling back removes them too until the fix lands. The team's rule of thumb:",[297,927,928,1048],{},[300,929,308,934,308,937,308,940,308,943,308,1041],{"viewBox":930,"role":303,"ariaLabelledBy":931,"xmlns":307},"0 0 760 246",[932,933],"nlroll-decide-title","nlroll-decide-desc",[310,935,936],{"id":932},"Decision tree for choosing between a rollback and a forward fix on Netlify",[314,938,939],{"id":933},"The root asks how bad the problem is and how quickly a fix can ship. A broken site for many readers with no immediate fix calls for a rollback and lock. A broken single page with an obvious one-line fix calls for fixing forward through the normal pipeline. A problem caused by external data or a third-party service is not helped by a rollback, so fix the integration. A security exposure calls for an immediate rollback and then a review.",[318,941],{"x":320,"y":320,"width":321,"height":942,"fill":323},"246",[325,944,328,945,328,952,328,956,328,959,328,963,328,970,328,973,328,977,328,980,328,984,328,987,328,990,328,993,328,997,328,1003,328,1007,328,1011,328,1015,328,1018,328,1021,328,1025,328,1028,328,1031,328,1035,328,1038,308],{"style":327},[318,946],{"x":947,"y":818,"width":948,"height":949,"rx":335,"fill":950,"opacity":951,"stroke":950,"style":338},"250.0","260.0","50.0","#6a4c93","0.14",[349,953],{"d":954,"fill":352,"stroke":353,"style":955},"M380.0 111.0 L380.0 132.0","stroke-width:2px",[349,957],{"d":958,"fill":352,"stroke":353,"style":955},"M103.2 132.0 L656.8 132.0",[349,960],{"d":961,"fill":352,"stroke":353,"style":962},"M103.2 132.0 L103.2 150.0","stroke-width:2px;marker-end:url(#nlroll-decide-arrow)",[318,964],{"x":965,"y":966,"width":967,"height":968,"rx":335,"fill":820,"opacity":969,"stroke":821,"style":338},"20.0","154.0","166.5","75.5","0.12",[349,971],{"d":972,"fill":352,"stroke":353,"style":962},"M287.8 132.0 L287.8 150.0",[318,974],{"x":975,"y":966,"width":967,"height":968,"rx":335,"fill":833,"opacity":976,"stroke":834,"style":338},"204.5","0.2",[349,978],{"d":979,"fill":352,"stroke":353,"style":962},"M472.2 132.0 L472.2 150.0",[318,981],{"x":982,"y":966,"width":967,"height":968,"rx":335,"fill":825,"opacity":983,"stroke":826,"style":338},"389.0","0.24",[349,985],{"d":986,"fill":352,"stroke":353,"style":962},"M656.8 132.0 L656.8 150.0",[318,988],{"x":989,"y":966,"width":967,"height":968,"rx":335,"fill":950,"opacity":951,"stroke":950,"style":338},"573.5",[145,991,992],{"x":383,"y":331,"fill":384,"style":385},"Roll back or fix forward?",[145,994,996],{"x":383,"y":995,"fill":384,"style":391},"90.2","What kind of problem is it?",[145,998,1002],{"x":999,"y":1000,"fill":868,"style":1001},"103.2","170.0","font-size:11px;text-anchor:middle;font-weight:700","Widely broken, no quick fix",[145,1004,1006],{"x":999,"y":1005,"fill":384,"style":391},"190.3","Roll back + lock",[145,1008,1010],{"x":999,"y":1009,"fill":353,"style":874},"207.2","then fix forward",[145,1012,1014],{"x":1013,"y":1000,"fill":891,"style":1001},"287.8","One page, obvious fix",[145,1016,1017],{"x":1013,"y":1005,"fill":384,"style":391},"Fix forward",[145,1019,1020],{"x":1013,"y":1009,"fill":353,"style":874},"normal pipeline",[145,1022,1024],{"x":1023,"y":1000,"fill":878,"style":1001},"472.2","External data or service",[145,1026,1027],{"x":1023,"y":1005,"fill":384,"style":391},"Fix integration",[145,1029,1030],{"x":1023,"y":1009,"fill":353,"style":874},"rollback won't help",[145,1032,1034],{"x":1033,"y":1000,"fill":950,"style":1001},"656.8","Security exposure",[145,1036,1037],{"x":1033,"y":1005,"fill":384,"style":391},"Roll back now",[145,1039,1040],{"x":1033,"y":1009,"fill":353,"style":874},"review afterwards",[433,1042,328,1043,308],{},[436,1044,443,1046,328],{"id":1045,"viewBox":439,"refX":335,"refY":440,"markerWidth":441,"markerHeight":441,"orient":442},"nlroll-decide-arrow",[349,1047],{"d":446,"fill":353},[448,1049,1050],{},"Rollback restores code and configuration, not external data or third-party behaviour.",[14,1052,1053],{},"In the four incidents since the workflow existed, two were rollbacks (a broken navigation component and a redirect rule that sent every docs page to the home page), one was a forward fix (a typo in a heading anchor), and one was neither — a third-party consent script outage, which no deploy could fix and which the team handled by temporarily removing the script through its tag configuration. Writing the decision down kept on-call people from reaching for the rollback button reflexively, and from hesitating when it was clearly the right call.",[32,1055,1057],{"id":1056},"deploy-previews-as-rollback-candidates","Deploy Previews as Rollback Candidates",[14,1059,1060,1061,1063],{},"Because every production deploy stays available, the workflow can also publish a deploy that was never live — for example, the preview of a pull request that reverts the bad change, once its checks pass. Restoring that deploy publishes the revert without waiting for a merge and a new build, which saved about three minutes in one incident. The lock is applied the same way, and the revert is merged normally afterwards so ",[44,1062,167],{}," matches what is live.",[32,1065,1067],{"id":1066},"drilling-it","Drilling It",[14,1069,1070],{},"A rollback path that is never used breaks quietly — a token expires, an API endpoint changes, an approver leaves. The team runs the workflow every quarter against a staging site that mirrors production's configuration, timing each step, and treats any failure as an incident in its own right. The first drill found the token had been scoped to the wrong team; the second found the smoke checks pointed at an old hostname.",[32,1072,1074],{"id":1073},"measured-impact","Measured Impact",[14,1076,1077],{},"Quarterly rollback drills, before and after the workflow:",[1079,1080,1081,1100],"table",{},[1082,1083,1084],"thead",{},[1085,1086,1087,1091,1094,1097],"tr",{},[1088,1089,1090],"th",{},"Measure",[1088,1092,1093],{},"Dashboard rollback",[1088,1095,1096],{},"Workflow rollback",[1088,1098,1099],{},"Source",[1101,1102,1103,1118,1132,1145],"tbody",{},[1085,1104,1105,1109,1112,1115],{},[1106,1107,1108],"td",{},"Median time from alert to old deploy live",[1106,1110,1111],{},"4 min 20 s",[1106,1113,1114],{},"1 min 22 s",[1106,1116,1117],{},"Drill logs",[1085,1119,1120,1123,1126,1129],{},[1106,1121,1122],{},"People able to roll back",[1106,1124,1125],{},"3 (dashboard owners)",[1106,1127,1128],{},"14 (repo maintainers, with approval)",[1106,1130,1131],{},"Access lists",[1085,1133,1134,1137,1140,1142],{},[1106,1135,1136],{},"Rollbacks undone by a later merge",[1106,1138,1139],{},"1 of 4 incidents",[1106,1141,320],{},[1106,1143,1144],{},"Incident log",[1085,1146,1147,1150,1153,1156],{},[1106,1148,1149],{},"Rollback verified automatically",[1106,1151,1152],{},"No",[1106,1154,1155],{},"Yes",[1106,1157,1158],{},"Workflow",[14,1160,1161],{},"The \"undone by a later merge\" row was the most important: in one earlier incident, a teammate merged an unrelated change twenty minutes after a dashboard rollback, and the broken deploy's change came back with it.",[32,1163,1165],{"id":1164},"pitfalls-rollback","Pitfalls & Rollback",[37,1167,1168,1175,1181,1187,1193],{},[40,1169,1170,1174],{},[1171,1172,1173],"strong",{},"Restoring without locking."," The next merge republishes the broken change.",[40,1176,1177,1180],{},[1171,1178,1179],{},"Forgetting to unlock."," Remind until the lock is removed.",[40,1182,1183,1186],{},[1171,1184,1185],{},"Personal tokens of individuals in CI."," Use an automation account's token.",[40,1188,1189,1192],{},[1171,1190,1191],{},"Assuming data rolls back."," Functions roll back; external data does not.",[40,1194,1195,1198],{},[1171,1196,1197],{},"Rollback of the rollback:"," restore the newer deploy again by ID — every deploy remains available.",[32,1200,1202],{"id":1201},"conclusion","Conclusion",[14,1204,1205],{},"Netlify's API makes rollback scriptable: list production deploys, restore the last good one, lock it so the next merge does not undo it, verify, and unlock when the fix is ready. Wrapped in a GitHub Actions workflow with an approval gate, it cut median rollback time in drills from over four minutes to under a minute and a half, opened rollback to every maintainer, and ended rollbacks being silently reversed.",[32,1207,1209],{"id":1208},"faq","FAQ",[1211,1212,1214],"h3",{"id":1213},"how-do-i-roll-back-a-netlify-deploy-without-the-dashboard","How do I roll back a Netlify deploy without the dashboard?",[14,1216,1217],{},"Call the Netlify API's restore endpoint for the deploy you want, which publishes that existing deploy again without rebuilding. The Netlify CLI's api command calls the same endpoint. Wrapping it in a GitHub Actions workflow with a manual trigger makes it a one-click operation for anyone with access to the repository.",[1211,1219,1221],{"id":1220},"does-restoring-a-deploy-rebuild-the-site","Does restoring a deploy rebuild the site?",[14,1223,1224],{},"No. Netlify keeps every deploy's files, and restoring publishes an existing deploy as it was, including its redirects and headers files. It takes effect in seconds. Environment variables and build settings are not involved, because nothing is built.",[1211,1226,1228],{"id":1227},"why-does-netlify-publish-the-next-build-over-my-rollback","Why does Netlify publish the next build over my rollback?",[14,1230,1231],{},"Because auto-publishing is still on. The next push to the production branch builds and publishes as usual, replacing the restored deploy. Lock the published deploy, which stops auto-publishing, until the fix is merged, then unlock it.",[1211,1233,1235],{"id":1234},"are-functions-rolled-back-too","Are functions rolled back too?",[14,1237,1238],{},"Yes. Netlify Functions and Edge Functions are part of each deploy, so restoring an older deploy also restores the function code it shipped with. Data the functions wrote to external services is not rolled back, so check whether a bad deploy changed stored data separately.",[32,1240,1242],{"id":1241},"related","Related",[37,1244,1245,1254,1259,1266,1273],{},[40,1246,1247,1250,1251,1253],{},[1171,1248,1249],{},"Parent:"," ",[21,1252,24],{"href":23}," — safe deploys and fast recovery.",[40,1255,1256,1258],{},[21,1257,29],{"href":28}," — rollback across hosts.",[40,1260,1261,1265],{},[21,1262,1264],{"href":1263},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads\u002F","Atomic Deploys vs Incremental Uploads"," — why Netlify can restore instantly.",[40,1267,1268,1272],{},[21,1269,1271],{"href":1270},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates\u002F","Netlify Build Hooks for Content Updates"," — other ways deploys get published.",[40,1274,1275,1279],{},[21,1276,1278],{"href":1277},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-to-cloudflare-from-github-actions-with-wrangler\u002F","Deploying to Cloudflare From GitHub Actions With Wrangler"," — the equivalent rollback on Cloudflare.",[1281,1282,1283],"style",{},"html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .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}",{"title":77,"searchDepth":111,"depth":111,"links":1285},[1286,1287,1288,1289,1290,1291,1292,1293,1294,1295,1296,1297,1298,1304],{"id":34,"depth":111,"text":35},{"id":69,"depth":111,"text":70},{"id":160,"depth":111,"text":161},{"id":453,"depth":111,"text":454},{"id":695,"depth":111,"text":696},{"id":711,"depth":111,"text":712},{"id":921,"depth":111,"text":922},{"id":1056,"depth":111,"text":1057},{"id":1066,"depth":111,"text":1067},{"id":1073,"depth":111,"text":1074},{"id":1164,"depth":111,"text":1165},{"id":1201,"depth":111,"text":1202},{"id":1208,"depth":111,"text":1209,"children":1299},[1300,1301,1302,1303],{"id":1213,"depth":127,"text":1214},{"id":1220,"depth":127,"text":1221},{"id":1227,"depth":127,"text":1228},{"id":1234,"depth":127,"text":1235},{"id":1241,"depth":111,"text":1242},[1306,1309,1312,1313],{"name":1307,"item":1308},"Home","\u002F",{"name":1310,"item":1311},"Production-Ready Deployment & CI\u002FCD for SSGs","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":24,"item":23},{"name":5,"item":1314},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-netlify-deploys-from-the-cli-and-api\u002F","2026-10-02","Roll back a Netlify site to an earlier deploy from the API, the CLI or a GitHub Actions button, lock auto-publishing during incidents, and verify the restore.","md",[1319,1320,1321,1322],{"q":1214,"a":1217},{"q":1221,"a":1224},{"q":1228,"a":1231},{"q":1235,"a":1238},{},true,"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-netlify-deploys-from-the-cli-and-api",{"title":5,"description":1316},"production-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-netlify-deploys-from-the-cli-and-api\u002Findex","article","QWemhyx02v4E2MDSIHiqsvtRdd7BzNcJ34lHK5zdBwk",[1331,1334,1337,1340,1343,1346,1349,1352,1355,1358,1361,1364,1367,1370,1373,1376,1379,1382,1385,1388,1391,1394,1397,1400,1403,1406,1409,1412,1415,1418,1421,1424,1427,1430,1433,1436,1439,1442,1445,1448,1451,1454,1457,1460,1463,1466,1469,1472,1475,1478,1481,1484,1487,1490,1493,1496,1499,1502,1505,1508,1511,1514,1517,1520,1523,1526,1529,1532,1535,1538,1541,1544,1547,1550,1553,1556,1559,1562,1565,1568,1571,1574,1577,1580,1583,1586,1589,1592,1595,1598,1601,1604,1607,1610,1613,1616,1619,1622,1625,1628,1631,1634,1637,1640,1643,1646,1649,1652,1655,1658,1661,1664,1667,1670,1673,1676,1679,1682,1685,1688,1691,1694,1697,1700,1703,1706,1709,1712,1715,1718,1721,1724,1727,1730,1733,1736,1739,1742,1745,1748,1751,1754,1757,1760,1763,1766,1769,1772,1775,1778,1781,1784,1787,1790,1793,1796,1799,1802,1805,1808,1811,1814,1817,1820,1823,1826,1829,1832,1835,1838,1841,1844,1847,1850,1853,1856,1859,1862,1865,1868,1871,1874,1877,1880,1883,1886,1889,1892,1895,1898,1901,1904,1907,1910,1913,1916,1919,1922,1925,1928,1931,1934,1937,1940,1943,1946,1949,1952,1955,1958,1961,1964,1967,1970,1973,1976,1979,1982,1985,1988,1991,1994,1997,2000,2003,2006,2009,2012,2015,2018,2021,2024,2027,2030,2033,2036,2039,2042,2045,2048,2051,2054,2057,2060,2063,2066,2069,2072,2075,2078,2081,2084,2087,2090,2093,2095,2098,2101,2104,2107,2110,2113,2116,2119,2122,2125,2128,2131,2134,2137,2140,2143,2146,2149,2152,2155,2158,2161,2164,2167,2170,2173,2176,2179,2182,2185,2188,2191,2194,2197,2200,2203,2206,2208,2211,2214,2217,2220,2223,2226,2229,2232,2235,2238,2241,2244,2247,2250,2253,2256,2259,2262,2264,2267,2270,2273,2276,2279,2282,2285,2288,2291,2294,2297,2300,2303,2306,2309,2311,2314,2317,2320,2322,2325,2327,2330,2332,2333,2336,2339,2342,2345,2348,2351,2354,2357,2360,2363,2366,2369,2372,2375,2378,2381,2384,2387,2390,2393,2396,2399,2402,2405,2408,2411,2414,2417,2420,2423,2426,2429,2432,2435,2438,2441,2444,2447,2450,2453,2456,2459,2462,2465,2468],{"path":1332,"title":1333},"\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":1335,"title":1336},"\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":1338,"title":1339},"\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":1341,"title":1342},"\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":1344,"title":1345},"\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":1347,"title":1348},"\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":1350,"title":1351},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1353,"title":1354},"\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":1356,"title":1357},"\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":1359,"title":1360},"\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":1362,"title":1363},"\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":1365,"title":1366},"\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":1368,"title":1369},"\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":1371,"title":1372},"\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":1374,"title":1375},"\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":1377,"title":1378},"\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":1380,"title":1381},"\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":1383,"title":1384},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1386,"title":1387},"\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":1389,"title":1390},"\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":1392,"title":1393},"\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":1395,"title":1396},"\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":1398,"title":1399},"\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":1401,"title":1402},"\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":1404,"title":1405},"\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":1407,"title":1408},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1410,"title":1411},"\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":1413,"title":1414},"\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":1416,"title":1417},"\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":1419,"title":1420},"\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":1422,"title":1423},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1425,"title":1426},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1428,"title":1429},"\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":1431,"title":1432},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1434,"title":1435},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1437,"title":1438},"\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":1440,"title":1441},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1443,"title":1444},"\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":1446,"title":1447},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1449,"title":1450},"\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":1452,"title":1453},"\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":1455,"title":1456},"\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":1458,"title":1459},"\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":1461,"title":1462},"\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":1464,"title":1465},"\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":1467,"title":1468},"\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":1470,"title":1471},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1473,"title":1474},"\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":1476,"title":1477},"\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":1479,"title":1480},"\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":1482,"title":1483},"\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":1485,"title":1486},"\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":1488,"title":1489},"\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":1491,"title":1492},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1494,"title":1495},"\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":1497,"title":1498},"\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":1500,"title":1501},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1503,"title":1504},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1506,"title":1507},"\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":1509,"title":1510},"\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":1512,"title":1513},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1515,"title":1516},"\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":1518,"title":1519},"\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":1521,"title":1522},"\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":1524,"title":1525},"\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":1527,"title":1528},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1530,"title":1531},"\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":1533,"title":1534},"\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":1536,"title":1537},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1539,"title":1540},"\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":1542,"title":1543},"\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":1545,"title":1546},"\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":1548,"title":1549},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1551,"title":1552},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1554,"title":1555},"\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":1557,"title":1558},"\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":1560,"title":1561},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1563,"title":1564},"\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":1566,"title":1567},"\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":1569,"title":1570},"\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":1572,"title":1573},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1575,"title":1576},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1578,"title":1579},"\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":1581,"title":1582},"\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":1584,"title":1585},"\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":1587,"title":1588},"\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":1590,"title":1591},"\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":1593,"title":1594},"\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":1596,"title":1597},"\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":1599,"title":1600},"\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":1602,"title":1603},"\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":1605,"title":1606},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1608,"title":1609},"\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":1611,"title":1612},"\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":1614,"title":1615},"\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":1617,"title":1618},"\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":1620,"title":1621},"\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":1623,"title":1624},"\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":1626,"title":1627},"\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":1629,"title":1630},"\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":1632,"title":1633},"\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":1635,"title":1636},"\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":1638,"title":1639},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1641,"title":1642},"\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":1644,"title":1645},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1647,"title":1648},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1650,"title":1651},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1653,"title":1654},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1656,"title":1657},"\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":1659,"title":1660},"\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":1662,"title":1663},"\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":1665,"title":1666},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1668,"title":1669},"\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":1671,"title":1672},"\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":1674,"title":1675},"\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":1677,"title":1678},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1680,"title":1681},"\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":1683,"title":1684},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1686,"title":1687},"\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":1689,"title":1690},"\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":1692,"title":1693},"\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":1695,"title":1696},"\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":1698,"title":1699},"\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":1701,"title":1702},"\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":1704,"title":1705},"\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":1707,"title":1708},"\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":1710,"title":1711},"\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":1713,"title":1714},"\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":1716,"title":1717},"\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":1719,"title":1720},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1722,"title":1723},"\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":1725,"title":1726},"\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":1728,"title":1729},"\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":1731,"title":1732},"\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":1734,"title":1735},"\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":1737,"title":1738},"\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":1740,"title":1741},"\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":1743,"title":1744},"\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":1746,"title":1747},"\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":1749,"title":1750},"\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":1752,"title":1753},"\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":1755,"title":1756},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1758,"title":1759},"\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":1761,"title":1762},"\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":1764,"title":1765},"\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":1767,"title":1768},"\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":1770,"title":1771},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1773,"title":1774},"\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":1776,"title":1777},"\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":1779,"title":1780},"\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":1782,"title":1783},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":1785,"title":1786},"\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":1788,"title":1789},"\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":1791,"title":1792},"\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":1794,"title":1795},"\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":1797,"title":1798},"\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":1800,"title":1801},"\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":1803,"title":1804},"\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":1806,"title":1807},"\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":1809,"title":1810},"\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":1812,"title":1813},"\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":1815,"title":1816},"\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":1818,"title":1819},"\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":1821,"title":1822},"\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":1824,"title":1825},"\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":1827,"title":1828},"\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":1830,"title":1831},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1833,"title":1834},"\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":1836,"title":1837},"\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":1839,"title":1840},"\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":1842,"title":1843},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":1845,"title":1846},"\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":1848,"title":1849},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1851,"title":1852},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1854,"title":1855},"\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":1857,"title":1858},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1860,"title":1861},"\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":1863,"title":1864},"\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":1866,"title":1867},"\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":1869,"title":1870},"\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":1872,"title":1873},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":1875,"title":1876},"\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":1878,"title":1879},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":1881,"title":1882},"\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":1884,"title":1885},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":1887,"title":1888},"\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":1890,"title":1891},"\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":1893,"title":1894},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1896,"title":1897},"\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":1899,"title":1900},"\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":1902,"title":1903},"\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":1905,"title":1906},"\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":1908,"title":1909},"\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":1911,"title":1912},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1914,"title":1915},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1917,"title":1918},"\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":1920,"title":1921},"\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":1923,"title":1924},"\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":1926,"title":1927},"\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":1929,"title":1930},"\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":1932,"title":1933},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1935,"title":1936},"\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":1938,"title":1939},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":1941,"title":1942},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1944,"title":1945},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":1947,"title":1948},"\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":1950,"title":1951},"\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":1953,"title":1954},"\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":1956,"title":1957},"\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":1959,"title":1960},"\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":1962,"title":1963},"\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":1965,"title":1966},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1968,"title":1969},"\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":1971,"title":1972},"\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":1974,"title":1975},"\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":1977,"title":1978},"\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":1980,"title":1981},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1983,"title":1984},"\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":1986,"title":1987},"\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":1989,"title":1990},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":1992,"title":1993},"\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":1995,"title":1996},"\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":1998,"title":1999},"\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":2001,"title":2002},"\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":2004,"title":2005},"\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":2007,"title":2008},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2010,"title":2011},"\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":2013,"title":2014},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2016,"title":2017},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2019,"title":2020},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2022,"title":2023},"\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":2025,"title":2026},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2028,"title":2029},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2031,"title":2032},"\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":2034,"title":2035},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2037,"title":2038},"\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":2040,"title":2041},"\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":2043,"title":2044},"\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":2046,"title":2047},"\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":2049,"title":2050},"\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":2052,"title":2053},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2055,"title":2056},"\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":2058,"title":2059},"\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":2061,"title":2062},"\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":2064,"title":2065},"\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":2067,"title":2068},"\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":2070,"title":2071},"\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":2073,"title":2074},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2076,"title":2077},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2079,"title":2080},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2082,"title":2083},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2085,"title":2086},"\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":2088,"title":2089},"\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":2091,"title":2092},"\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":2094,"title":1278},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-to-cloudflare-from-github-actions-with-wrangler",{"path":2096,"title":2097},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2099,"title":2100},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2102,"title":2103},"\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":2105,"title":2106},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2108,"title":2109},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2111,"title":2112},"\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":2114,"title":2115},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2117,"title":2118},"\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":2120,"title":2121},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2123,"title":2124},"\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":2126,"title":2127},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2129,"title":2130},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2132,"title":2133},"\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":2135,"title":2136},"\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":2138,"title":2139},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2141,"title":2142},"\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":2144,"title":2145},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2147,"title":2148},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2150,"title":2151},"\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":2153,"title":2154},"\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":2156,"title":2157},"\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":2159,"title":2160},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2162,"title":2163},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2165,"title":2166},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2168,"title":2169},"\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":2171,"title":2172},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2174,"title":2175},"\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":2177,"title":2178},"\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":2180,"title":2181},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2183,"title":2184},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2186,"title":2187},"\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":2189,"title":2190},"\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":2192,"title":2193},"\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":2195,"title":2196},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2198,"title":2199},"\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":2201,"title":2202},"\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":2204,"title":2205},"\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":2207,"title":1310},"\u002Fproduction-ready-deployment-cicd-workflows",{"path":2209,"title":2210},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2212,"title":2213},"\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":2215,"title":2216},"\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":2218,"title":2219},"\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":2221,"title":2222},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2224,"title":2225},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2227,"title":2228},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2230,"title":2231},"\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":2233,"title":2234},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2236,"title":2237},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2239,"title":2240},"\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":2242,"title":2243},"\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":2245,"title":2246},"\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":2248,"title":2249},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2251,"title":2252},"\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":2254,"title":2255},"\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":2257,"title":2258},"\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":2260,"title":2261},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2263,"title":1271},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates",{"path":2265,"title":2266},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2268,"title":2269},"\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":2271,"title":2272},"\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":2274,"title":2275},"\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":2277,"title":2278},"\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":2280,"title":2281},"\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":2283,"title":2284},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2286,"title":2287},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2289,"title":2290},"\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":2292,"title":2293},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2295,"title":2296},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2298,"title":2299},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2301,"title":2302},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2304,"title":2305},"\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":2307,"title":2308},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2310,"title":1264},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads",{"path":2312,"title":2313},"\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":2315,"title":2316},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2318,"title":2319},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2321,"title":24},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites",{"path":2323,"title":2324},"\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":2326,"title":707},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists",{"path":2328,"title":2329},"\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":2331,"title":29},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-a-bad-static-deploy-in-under-a-minute",{"path":1325,"title":5},{"path":2334,"title":2335},"\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":2337,"title":2338},"\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":2340,"title":2341},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2343,"title":2344},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2346,"title":2347},"\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":2349,"title":2350},"\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":2352,"title":2353},"\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":2355,"title":2356},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2358,"title":2359},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2361,"title":2362},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2364,"title":2365},"\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":2367,"title":2368},"\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":2370,"title":2371},"\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":2373,"title":2374},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2376,"title":2377},"\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":2379,"title":2380},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2382,"title":2383},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2385,"title":2386},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2388,"title":2389},"\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":2391,"title":2392},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2394,"title":2395},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2397,"title":2398},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2400,"title":2401},"\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":2403,"title":2404},"\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":2406,"title":2407},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2409,"title":2410},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2412,"title":2413},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2415,"title":2416},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2418,"title":2419},"\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":2421,"title":2422},"\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":2424,"title":2425},"\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":2427,"title":2428},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2430,"title":2431},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2433,"title":2434},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2436,"title":2437},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2439,"title":2440},"\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":2442,"title":2443},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2445,"title":2446},"\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":2448,"title":2449},"\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":2451,"title":2452},"\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":2454,"title":2455},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2457,"title":2458},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2460,"title":2461},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2463,"title":2464},"\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":2466,"title":2467},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2469,"title":2470},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2472,"tools":2476},{"label":2473,"plural":2474,"u":2475},"How-to","How-tos","\u002Fguides\u002Fhow-to\u002F",[2477],{"label":2478,"u":2479},"Netlify","\u002Ftools\u002Fnetlify\u002F",1790943196208]