[{"data":1,"prerenderedAt":1656},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fmigrating-from-cloudflare-pages-to-workers-static-assets":3,"all-docs-nav":1117},{"id":4,"title":5,"body":6,"breadcrumb":1092,"dateModified":1102,"datePublished":1102,"description":1103,"extension":1104,"faq":1105,"meta":1110,"navigation":1111,"path":1112,"seo":1113,"slug":12,"stem":1114,"type":1115,"__hash__":1116},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fmigrating-from-cloudflare-pages-to-workers-static-assets\u002Findex.md","Migrating from Cloudflare Pages to Workers Static Assets",{"type":7,"value":8,"toc":1071},"minimark",[9,13,17,35,40,57,61,64,208,212,219,283,329,348,352,360,382,393,397,400,431,438,570,574,581,643,654,658,661,688,782,789,793,810,835,839,855,922,926,929,933,978,982,996,1000,1005,1008,1012,1015,1019,1022,1026,1029,1033,1067],[10,11,5],"h1",{"id":12},"migrating-from-cloudflare-pages-to-workers-static-assets",[14,15,16],"p",{},"Cloudflare Pages was, for years, the default home for static sites on Cloudflare. Workers can now serve static assets directly, with the same free, unlimited static requests, and Cloudflare is putting new capabilities there first: observability, Durable Objects, Cron Triggers, and a single configuration file for static and dynamic parts of a project. For a purely static site the move is mostly configuration, and it can be done without downtime.",[14,18,19,20,24,25,28,29,34],{},"This guide migrates a static site from Pages to a Worker with static assets, covering the Wrangler configuration, ",[21,22,23],"code",{},"_headers"," and ",[21,26,27],{},"_redirects",", trailing slashes and 404 handling, preview deployments, CI, and the custom domain cutover. It is part of ",[30,31,33],"a",{"href":32},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002F","Cloudflare Pages Edge Caching Setup",".",[36,37,39],"h2",{"id":38},"prerequisites","Prerequisites",[41,42,43,47,54],"ul",{},[44,45,46],"li",{},"A static site currently deployed on Cloudflare Pages.",[44,48,49,50,53],{},"Wrangler 3.90 or later (",[21,51,52],{},"npm install -D wrangler",") and a Cloudflare API token with Workers edit permissions.",[44,55,56],{},"Access to the custom domain's DNS zone in the same Cloudflare account.",[36,58,60],{"id":59},"what-changes-and-what-does-not","What Changes and What Does Not",[14,62,63],{},"The build does not change: the generator still writes a folder of HTML, CSS and assets. What changes is how that folder is deployed and configured.",[65,66,67,204],"figure",{},[68,69,76,77,76,81,76,85,76,92,76,110],"svg",{"viewBox":70,"role":71,"ariaLabelledBy":72,"xmlns":75},"0 0 760 280","img",[73,74],"pwm-map-title","pwm-map-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[78,79,80],"title",{"id":73},"Pages concepts and their Workers equivalents",[82,83,84],"desc",{"id":74},"Pages build output directory maps to assets.directory in wrangler config. _headers and _redirects stay the same. Pages Functions map to the Worker script. Preview deployments map to Worker versions with preview URLs. Git integration maps to Workers Builds or a CI workflow. Custom domains map to Worker custom domains.",[86,87],"rect",{"x":88,"y":88,"width":89,"height":90,"fill":91},"0","760","280","#ffffff",[93,94,95,96,76],"defs",{},"\n    ",[97,98,105],"marker",{"id":99,"viewBox":100,"refX":101,"refY":102,"markerWidth":103,"markerHeight":103,"orient":104},"pwm-map-arrow","0 0 10 10","9","5","7","auto-start-reverse",[106,107],"path",{"d":108,"fill":109},"M0,0 L10,5 L0,10 z","#556071",[111,112,95,114,95,122,95,129,95,134,95,139,95,142,95,146,95,149,95,153,95,156,95,160,95,163,95,167,95,170,95,174,95,177,95,184,95,187,95,190,95,193,95,196,95,199,76],"g",{"style":113},"font-family:system-ui, sans-serif;font-size:12px",[115,116,121],"text",{"x":117,"y":118,"fill":119,"style":120},"380","26","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Pages → Workers static assets",[115,123,128],{"x":124,"y":125,"fill":126,"style":127},"190","52","#166a9e","font-weight:700;text-anchor:middle","Pages",[115,130,133],{"x":131,"y":125,"fill":132,"style":127},"570","#3f6410","Workers",[115,135,138],{"x":124,"y":136,"fill":119,"style":137},"80","text-anchor:middle","build output directory",[115,140,141],{"x":131,"y":136,"fill":119,"style":137},"assets.directory in wrangler config",[115,143,145],{"x":124,"y":144,"fill":119,"style":137},"112","_headers, _redirects",[115,147,148],{"x":131,"y":144,"fill":132,"style":137},"unchanged",[115,150,152],{"x":124,"y":151,"fill":119,"style":137},"144","Pages Functions (\u002Ffunctions)",[115,154,155],{"x":131,"y":151,"fill":119,"style":137},"Worker script (main)",[115,157,159],{"x":124,"y":158,"fill":119,"style":137},"176","preview deployments",[115,161,162],{"x":131,"y":158,"fill":119,"style":137},"versions with preview URLs",[115,164,166],{"x":124,"y":165,"fill":119,"style":137},"208","Git integration",[115,168,169],{"x":131,"y":165,"fill":119,"style":137},"Workers Builds or CI + wrangler deploy",[115,171,173],{"x":124,"y":172,"fill":119,"style":137},"240","custom domains",[115,175,176],{"x":131,"y":172,"fill":119,"style":137},"Worker custom domains",[178,179],"line",{"x1":180,"y1":181,"x2":182,"y2":181,"stroke":109,"style":183},"320","76","400","stroke-width:1.5px;marker-end:url(#pwm-map-arrow)",[178,185],{"x1":180,"y1":186,"x2":182,"y2":186,"stroke":109,"style":183},"108",[178,188],{"x1":180,"y1":189,"x2":182,"y2":189,"stroke":109,"style":183},"140",[178,191],{"x1":180,"y1":192,"x2":182,"y2":192,"stroke":109,"style":183},"172",[178,194],{"x1":180,"y1":195,"x2":182,"y2":195,"stroke":109,"style":183},"204",[178,197],{"x1":180,"y1":198,"x2":182,"y2":198,"stroke":109,"style":183},"236",[115,200,203],{"x":117,"y":201,"fill":109,"style":202},"270","font-size:11px;text-anchor:middle","static requests remain free on both; you pay only for requests that run Worker code",[205,206,207],"figcaption",{},"For a static site, the migration is mostly a new config file and a domain switch.",[36,209,211],{"id":210},"step-1-write-the-wrangler-configuration","Step 1: Write the Wrangler Configuration",[14,213,214,215,218],{},"Create ",[21,216,217],{},"wrangler.jsonc"," at the repository root. A purely static site needs no script at all:",[220,221,226],"pre",{"className":222,"code":223,"language":224,"meta":225,"style":225},"language-jsonc shiki shiki-themes github-light github-dark","{\n  \"name\": \"docs-site\",\n  \"compatibility_date\": \"2026-09-01\",\n  \"assets\": {\n    \"directory\": \".\u002Fdist\",\n    \"html_handling\": \"auto-trailing-slash\",\n    \"not_found_handling\": \"404-page\"\n  }\n}\n","jsonc","",[21,227,228,235,241,247,253,259,265,271,277],{"__ignoreMap":225},[229,230,232],"span",{"class":178,"line":231},1,[229,233,234],{},"{\n",[229,236,238],{"class":178,"line":237},2,[229,239,240],{},"  \"name\": \"docs-site\",\n",[229,242,244],{"class":178,"line":243},3,[229,245,246],{},"  \"compatibility_date\": \"2026-09-01\",\n",[229,248,250],{"class":178,"line":249},4,[229,251,252],{},"  \"assets\": {\n",[229,254,256],{"class":178,"line":255},5,[229,257,258],{},"    \"directory\": \".\u002Fdist\",\n",[229,260,262],{"class":178,"line":261},6,[229,263,264],{},"    \"html_handling\": \"auto-trailing-slash\",\n",[229,266,268],{"class":178,"line":267},7,[229,269,270],{},"    \"not_found_handling\": \"404-page\"\n",[229,272,274],{"class":178,"line":273},8,[229,275,276],{},"  }\n",[229,278,280],{"class":178,"line":279},9,[229,281,282],{},"}\n",[14,284,285,288,289,292,293,296,297,300,301,304,305,308,309,312,313,316,317,320,321,324,325,328],{},[21,286,287],{},"html_handling"," controls clean URLs. ",[21,290,291],{},"auto-trailing-slash",", the default, serves ",[21,294,295],{},"\u002Fabout\u002Findex.html"," at ",[21,298,299],{},"\u002Fabout\u002F"," and redirects ",[21,302,303],{},"\u002Fabout"," to it, matching Pages' behaviour. Use ",[21,306,307],{},"force-trailing-slash"," or ",[21,310,311],{},"drop-trailing-slash"," if your site's canonical URLs require one form. ",[21,314,315],{},"not_found_handling"," set to ",[21,318,319],{},"404-page"," serves the nearest ",[21,322,323],{},"404.html"," with a 404 status; use ",[21,326,327],{},"single-page-application"," only for client-routed apps.",[14,330,331,332,335,336,339,340,343,344,347],{},"If the site had Pages Functions, add ",[21,333,334],{},"\"main\": \"src\u002Fworker.ts\""," and move the function code into a Worker, calling ",[21,337,338],{},"env.ASSETS.fetch(request)"," to fall through to static files. Declare the binding with ",[21,341,342],{},"\"binding\": \"ASSETS\""," inside the ",[21,345,346],{},"assets"," block.",[36,349,351],{"id":350},"step-2-keep-_headers-and-_redirects","Step 2: Keep _headers and _redirects",[14,353,354,355,24,357,359],{},"Workers static assets read ",[21,356,23],{},[21,358,27],{}," from the assets directory with the same syntax as Pages. Leave them where they are. Two differences to check:",[41,361,362,372],{},[44,363,364,368,369,371],{},[365,366,367],"strong",{},"Headers on Worker responses."," ",[21,370,23],{}," applies only to responses served from static assets. If a Worker script generates a response, set headers in code.",[44,373,374,377,378,381],{},[365,375,376],{},"Run order."," By default, a request that matches a static file is served without invoking the Worker script. If you need the script to run first — for authentication, for example — set ",[21,379,380],{},"\"run_worker_first\": true"," or a list of path patterns, and remember each such request is billed.",[14,383,384,385,24,389,34],{},"Security headers and cache rules carry over unchanged; see ",[30,386,388],{"href":387},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fwriting-a-content-security-policy-for-a-static-site\u002F","Writing a Content Security Policy for a Static Site",[30,390,392],{"href":391},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages\u002F","Configuring Redirects on Cloudflare Pages",[36,394,396],{"id":395},"step-3-deploy-and-test-on-workersdev","Step 3: Deploy and Test on workers.dev",[14,398,399],{},"Build and deploy:",[220,401,405],{"className":402,"code":403,"language":404,"meta":225,"style":225},"language-bash shiki shiki-themes github-light github-dark","npm run build\nnpx wrangler deploy\n","bash",[21,406,407,420],{"__ignoreMap":225},[229,408,409,413,417],{"class":178,"line":231},[229,410,412],{"class":411},"sScJk","npm",[229,414,416],{"class":415},"sZZnC"," run",[229,418,419],{"class":415}," build\n",[229,421,422,425,428],{"class":178,"line":237},[229,423,424],{"class":411},"npx",[229,426,427],{"class":415}," wrangler",[229,429,430],{"class":415}," deploy\n",[14,432,433,434,437],{},"Wrangler uploads only changed files, prints the Worker's ",[21,435,436],{},"workers.dev"," URL, and the new site is live there while production traffic still goes to Pages. Test it as you would a preview: a crawl for broken links, a check of redirects and response headers, and a spot check of the 404 page. A header comparison between the two hosts catches most regressions:",[220,439,441],{"className":402,"code":440,"language":404,"meta":225,"style":225},"for p in \u002F \u002Fdocs\u002F \u002Fdocs\u002Finstall\u002F \u002Fassets\u002Fapp.css \u002Fmissing\u002F; do\n  diff \u003C(curl -sI \"https:\u002F\u002Fdocs.example.com$p\" | sort) \\\n       \u003C(curl -sI \"https:\u002F\u002Fdocs-site.acct.workers.dev$p\" | sort) \\\n    | grep -Ev '^[\u003C>] (date|cf-ray|age|server-timing):' && echo \"differs: $p\"\ndone\n",[21,442,443,477,513,537,565],{"__ignoreMap":225},[229,444,445,449,453,456,459,462,465,468,471,474],{"class":178,"line":231},[229,446,448],{"class":447},"szBVR","for",[229,450,452],{"class":451},"sVt8B"," p ",[229,454,455],{"class":447},"in",[229,457,458],{"class":415}," \u002F",[229,460,461],{"class":415}," \u002Fdocs\u002F",[229,463,464],{"class":415}," \u002Fdocs\u002Finstall\u002F",[229,466,467],{"class":415}," \u002Fassets\u002Fapp.css",[229,469,470],{"class":415}," \u002Fmissing\u002F",[229,472,473],{"class":451},"; ",[229,475,476],{"class":447},"do\n",[229,478,479,482,485,488,492,495,498,501,504,507,510],{"class":178,"line":237},[229,480,481],{"class":411},"  diff",[229,483,484],{"class":415}," \u003C(",[229,486,487],{"class":411},"curl",[229,489,491],{"class":490},"sj4cs"," -sI",[229,493,494],{"class":415}," \"https:\u002F\u002Fdocs.example.com",[229,496,497],{"class":451},"$p",[229,499,500],{"class":415},"\" ",[229,502,503],{"class":447},"|",[229,505,506],{"class":411}," sort",[229,508,509],{"class":415},")",[229,511,512],{"class":490}," \\\n",[229,514,515,518,520,522,525,527,529,531,533,535],{"class":178,"line":243},[229,516,517],{"class":415},"       \u003C(",[229,519,487],{"class":411},[229,521,491],{"class":490},[229,523,524],{"class":415}," \"https:\u002F\u002Fdocs-site.acct.workers.dev",[229,526,497],{"class":451},[229,528,500],{"class":415},[229,530,503],{"class":447},[229,532,506],{"class":411},[229,534,509],{"class":415},[229,536,512],{"class":490},[229,538,539,542,545,548,551,554,557,560,562],{"class":178,"line":249},[229,540,541],{"class":447},"    |",[229,543,544],{"class":411}," grep",[229,546,547],{"class":490}," -Ev",[229,549,550],{"class":415}," '^[\u003C>] (date|cf-ray|age|server-timing):'",[229,552,553],{"class":451}," && ",[229,555,556],{"class":490},"echo",[229,558,559],{"class":415}," \"differs: ",[229,561,497],{"class":451},[229,563,564],{"class":415},"\"\n",[229,566,567],{"class":178,"line":255},[229,568,569],{"class":447},"done\n",[36,571,573],{"id":572},"step-4-move-ci","Step 4: Move CI",[14,575,576,577,580],{},"On Pages, the Git integration built and deployed each push. For Workers, either connect the repository to ",[365,578,579],{},"Workers Builds"," in the dashboard, which works the same way, or deploy from your existing CI:",[220,582,586],{"className":583,"code":584,"language":585,"meta":225,"style":225},"language-yaml shiki shiki-themes github-light github-dark","- run: npm ci && npm run build\n- uses: cloudflare\u002Fwrangler-action@v3\n  with:\n    apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}\n    command: deploy\n","yaml",[21,587,588,603,615,623,633],{"__ignoreMap":225},[229,589,590,593,597,600],{"class":178,"line":231},[229,591,592],{"class":451},"- ",[229,594,596],{"class":595},"s9eBZ","run",[229,598,599],{"class":451},": ",[229,601,602],{"class":415},"npm ci && npm run build\n",[229,604,605,607,610,612],{"class":178,"line":237},[229,606,592],{"class":451},[229,608,609],{"class":595},"uses",[229,611,599],{"class":451},[229,613,614],{"class":415},"cloudflare\u002Fwrangler-action@v3\n",[229,616,617,620],{"class":178,"line":243},[229,618,619],{"class":595},"  with",[229,621,622],{"class":451},":\n",[229,624,625,628,630],{"class":178,"line":249},[229,626,627],{"class":595},"    apiToken",[229,629,599],{"class":451},[229,631,632],{"class":415},"${{ secrets.CLOUDFLARE_API_TOKEN }}\n",[229,634,635,638,640],{"class":178,"line":255},[229,636,637],{"class":595},"    command",[229,639,599],{"class":451},[229,641,642],{"class":415},"deploy\n",[14,644,645,646,649,650,34],{},"For pull requests, ",[21,647,648],{},"wrangler versions upload"," creates a new version without sending traffic to it and returns a preview URL, which replaces Pages' per-branch preview deployments. Wire that URL into the pull request comment the same way; see ",[30,651,653],{"href":652},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fautomating-preview-deploy-pipelines-with-github-actions\u002F","Automating Preview Deploy Pipelines with GitHub Actions",[36,655,657],{"id":656},"step-5-switch-the-custom-domain","Step 5: Switch the Custom Domain",[14,659,660],{},"The cutover takes seconds and is reversible:",[662,663,664,667,685],"ol",{},[44,665,666],{},"In the Pages project, remove the custom domain.",[44,668,669,670,672,673,676,677,680,681,684],{},"Immediately add it to the Worker: in ",[21,671,217],{},", add ",[21,674,675],{},"\"routes\": [{ \"pattern\": \"docs.example.com\", \"custom_domain\": true }]"," and run ",[21,678,679],{},"wrangler deploy",", or add it under the Worker's ",[365,682,683],{},"Domains & Routes"," in the dashboard.",[44,686,687],{},"Cloudflare creates the DNS record and certificate for the Worker. Requests in flight during the switch may see one error; most readers see nothing.",[65,689,690,779],{},[68,691,76,696,76,699,76,702,76,704],{"viewBox":692,"role":71,"ariaLabelledBy":693,"xmlns":75},"0 0 760 240",[694,695],"pwm-cut-title","pwm-cut-desc",[78,697,698],{"id":694},"Custom domain cutover timeline",[82,700,701],{"id":695},"Traffic goes to Pages until the domain is removed. Within about ten seconds the domain is added to the Worker and traffic flows there. The Pages project remains deployed for two weeks as a rollback target, then it is deleted.",[86,703],{"x":88,"y":88,"width":89,"height":172,"fill":91},[111,705,95,706,95,709,95,713,95,719,95,723,95,728,95,733,95,737,95,741,95,746,95,750,95,756,95,758,95,764,95,768,95,772,95,775,76],{"style":113},[115,707,708],{"x":117,"y":118,"fill":119,"style":120},"Cutover without downtime",[115,710,128],{"x":711,"y":712,"fill":119},"77","74",[86,714],{"x":715,"y":716,"width":172,"height":717,"fill":126,"style":718},"120","60","22","fill-opacity:0.45",[86,720],{"x":721,"y":716,"width":721,"height":717,"fill":126,"stroke":126,"style":722},"360","fill-opacity:0.12;stroke-dasharray:4 3",[115,724,727],{"x":725,"y":726,"fill":126,"style":137},"540","75","kept as rollback target (2 weeks)",[115,729,732],{"x":730,"y":731,"fill":119},"73","124","Worker",[86,734],{"x":715,"y":735,"width":172,"height":717,"fill":132,"style":736},"110","fill-opacity:0.15",[115,738,740],{"x":172,"y":739,"fill":132,"style":137},"125","tested on workers.dev",[86,742],{"x":743,"y":735,"width":744,"height":717,"fill":132,"style":745},"370","350","fill-opacity:0.5",[115,747,749],{"x":748,"y":739,"fill":119,"style":137},"545","serves production traffic",[178,751],{"x1":721,"y1":752,"x2":721,"y2":753,"stroke":754,"style":755},"48","150","#d83b41","stroke-width:1.5px",[178,757],{"x1":743,"y1":752,"x2":743,"y2":753,"stroke":754,"style":755},[115,759,763],{"x":760,"y":761,"fill":762,"style":137},"365","170","#b32b30","domain switch ≈ 10 s",[178,765],{"x1":715,"y1":124,"x2":766,"y2":124,"stroke":109,"style":767},"720","stroke-width:1px",[115,769,771],{"x":715,"y":165,"fill":109,"style":770},"font-size:11px","day 0",[115,773,774],{"x":760,"y":165,"fill":109,"style":202},"cutover",[115,776,778],{"x":766,"y":165,"fill":109,"style":777},"font-size:11px;text-anchor:end","day 14: delete Pages project",[205,780,781],{},"Reversing the two domain steps is the rollback plan until the Pages project is deleted.",[14,783,784,785,34],{},"Afterwards, purge the zone cache once if cache rules depended on the old hostname, and watch error rates and 404 counts for a day. Keep the Pages project deployed for a couple of weeks so rollback is just the same two steps in reverse. For a whole-site safety net, see ",[30,786,788],{"href":787},"\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",[36,790,792],{"id":791},"porting-pages-functions","Porting Pages Functions",[14,794,795,796,799,800,803,804,807,808,34],{},"Many \"static\" Pages projects carry one or two functions: a contact form handler, an authentication check for a private section, or an API proxy. Pages routed them by file path under ",[21,797,798],{},"\u002Ffunctions",". In a Worker, routing is up to you. For a handful of routes, a small ",[21,801,802],{},"switch"," on ",[21,805,806],{},"url.pathname"," is enough; for more, a router such as Hono keeps the code readable. Anything that does not match falls through to ",[21,809,338],{},[14,811,812,813,815,816,819,820,823,824,827,828,830,831,34],{},"Bindings move to ",[21,814,217],{},": KV namespaces, D1 databases, R2 buckets and secrets declared in the Pages dashboard need matching entries in the config, and secrets are set with ",[21,817,818],{},"wrangler secret put",". Middleware written as ",[21,821,822],{},"_middleware.ts"," becomes ordinary code at the top of the Worker's ",[21,825,826],{},"fetch"," handler. Test each ported route on the ",[21,829,436],{}," URL before cutover; the header comparison script only covers static responses. For form handling specifically, see ",[30,832,834],{"href":833},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fadding-a-contact-form-with-cloudflare-workers\u002F","Adding a Contact Form with Cloudflare Workers",[36,836,838],{"id":837},"rollbacks-on-workers","Rollbacks on Workers",[14,840,841,842,845,846,850,851,854],{},"Workers keep a history of deployed versions. ",[21,843,844],{},"wrangler rollback"," returns production to the previous version in seconds, and the dashboard lists versions with their messages. Versions also support gradual deployments — sending, say, 10% of traffic to a new version before promoting it — which Pages did not offer; see ",[30,847,849],{"href":848},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites\u002F","Canary Releases for Static Sites",". Pass ",[21,852,853],{},"--message \"$(git log -1 --format=%s)\""," on deploy so each version is identifiable later.",[65,856,857,919],{},[68,858,76,863,76,866,76,869,76,872],{"viewBox":859,"role":71,"ariaLabelledBy":860,"xmlns":75},"0 0 760 220",[861,862],"pwm-dep-title","pwm-dep-desc",[78,864,865],{"id":861},"Deploy times before and after the migration",[82,867,868],{"id":862},"For a 2,400-page site, the Pages Git integration took 3 minutes 40 seconds from push to live. The Worker deployed from GitHub Actions with cached dependencies took 2 minutes 10 seconds, with the upload step taking 14 seconds because only changed files are sent.",[86,870],{"x":88,"y":88,"width":89,"height":871,"fill":91},"220",[111,873,95,874,95,878,95,882,95,888,95,892,95,896,95,899,95,905,95,910,95,915,76],{"style":113},[115,875,877],{"x":117,"y":876,"fill":119,"style":120},"28","Push to live, 2,400-page docs site",[115,879,881],{"x":880,"y":712,"fill":119},"91","Pages Git integration",[86,883],{"x":884,"y":885,"width":886,"height":887,"fill":126,"style":718},"210","62","440","20",[115,889,891],{"x":890,"y":711,"fill":119},"658","3 min 40 s",[115,893,895],{"x":894,"y":731,"fill":119},"65","Actions + wrangler deploy",[86,897],{"x":884,"y":144,"width":898,"height":887,"fill":132,"style":718},"244",[86,900],{"x":901,"y":144,"width":902,"height":887,"fill":903,"style":904},"454","16","#6a4c93","fill-opacity:0.6",[115,906,909],{"x":907,"y":908,"fill":119},"478","127","2 min 10 s",[115,911,914],{"x":912,"y":913,"fill":903,"style":137},"462","152","upload 14 s",[115,916,918],{"x":117,"y":917,"fill":109,"style":202},"196","most of the gain came from dependency and build caching in CI, not from the platform",[205,920,921],{},"Only changed assets are uploaded, so the deploy step stays short as the site grows.",[36,923,925],{"id":924},"measured-impact","Measured Impact",[14,927,928],{},"A 2,400-page documentation site moved from Pages to a Worker with static assets and no script. Response headers, redirects and 404 behaviour were identical in the comparison script. TTFB at the edge was unchanged within measurement noise. Push-to-live time fell from 3 minutes 40 seconds to 2 minutes 10 seconds, mainly because the move to GitHub Actions added dependency caching. The cutover produced no errors in the zone's analytics, and the Pages project was deleted after 14 days.",[36,930,932],{"id":931},"pitfalls-rollback","Pitfalls & Rollback",[41,934,935,944,953,962,972],{},[44,936,937,940,941,943],{},[365,938,939],{},"Trailing slash mode."," A different ",[21,942,287],{}," from Pages' behaviour changes canonical URLs; compare redirects before cutover.",[44,945,946,952],{},[365,947,948,951],{},[21,949,950],{},"run_worker_first"," left on."," Every request then invokes the script and is billed; enable it only for paths that need it.",[44,954,955,958,959,961],{},[365,956,957],{},"Functions directory ignored."," Workers do not read ",[21,960,798],{},"; port the code to the Worker script.",[44,963,964,967,968,971],{},[365,965,966],{},"Environment variables."," Pages project variables do not move automatically; add them under ",[21,969,970],{},"vars"," or as secrets.",[44,973,974,977],{},[365,975,976],{},"Rollback:"," move the custom domain back to the Pages project.",[36,979,981],{"id":980},"conclusion","Conclusion",[14,983,984,985,987,988,24,990,992,993,995],{},"For a static site, moving from Cloudflare Pages to Workers static assets is a configuration change: a ",[21,986,217],{}," with an assets directory, the same ",[21,989,23],{},[21,991,27],{},", a new deploy step in CI, and a ten-second domain switch. Test on the ",[21,994,436],{}," URL first, keep the Pages project as a rollback target for a couple of weeks, and the site gains versioned deploys, gradual rollouts and room to add server code later without changing platforms.",[36,997,999],{"id":998},"faq","FAQ",[1001,1002,1004],"h3",{"id":1003},"why-move-a-static-site-from-cloudflare-pages-to-workers","Why move a static site from Cloudflare Pages to Workers?",[14,1006,1007],{},"Cloudflare now directs new features to Workers, which can serve static assets directly and add code only where needed. Workers also give you Durable Objects, Cron Triggers, observability features and one deployment model for static and dynamic parts of a site.",[1001,1009,1011],{"id":1010},"do-_headers-and-_redirects-files-still-work-on-workers","Do _headers and _redirects files still work on Workers?",[14,1013,1014],{},"Yes. Workers static assets read _headers and _redirects from the assets directory with the same syntax and limits as Pages, so most static sites can move without rewriting those files.",[1001,1016,1018],{"id":1017},"does-a-worker-serving-static-assets-cost-more-than-pages","Does a Worker serving static assets cost more than Pages?",[14,1020,1021],{},"Requests that are served purely from static assets are free and unlimited, as on Pages. You pay only when a request invokes your Worker script, so a site with no script, or with run_worker_first disabled, costs the same.",[1001,1023,1025],{"id":1024},"how-do-i-avoid-downtime-when-switching-the-custom-domain","How do I avoid downtime when switching the custom domain?",[14,1027,1028],{},"Deploy the Worker and test it on its workers.dev URL first. Then remove the custom domain from the Pages project and immediately add it to the Worker; the switch takes seconds, and keeping the Pages project for a while lets you roll back by reversing the step.",[36,1030,1032],{"id":1031},"related","Related",[41,1034,1035,1043,1050,1057,1062],{},[44,1036,1037,368,1040,1042],{},[365,1038,1039],{},"Parent:",[30,1041,33],{"href":32}," — the full Cloudflare setup.",[44,1044,1045,1049],{},[30,1046,1048],{"href":1047},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-hugo-to-cloudflare-pages-and-workers\u002F","Deploying Hugo to Cloudflare Pages and Workers"," — a generator-specific walkthrough.",[44,1051,1052,1056],{},[30,1053,1055],{"href":1054},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcustom-domains-and-tls-on-cloudflare-pages\u002F","Custom Domains and TLS on Cloudflare Pages"," — domains and certificates in detail.",[44,1058,1059,1061],{},[30,1060,392],{"href":391}," — the _redirects file you keep.",[44,1063,1064,1066],{},[30,1065,849],{"href":848}," — using Worker versions for gradual rollouts.",[1068,1069,1070],"style",{},"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 .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}",{"title":225,"searchDepth":237,"depth":237,"links":1072},[1073,1074,1075,1076,1077,1078,1079,1080,1081,1082,1083,1084,1085,1091],{"id":38,"depth":237,"text":39},{"id":59,"depth":237,"text":60},{"id":210,"depth":237,"text":211},{"id":350,"depth":237,"text":351},{"id":395,"depth":237,"text":396},{"id":572,"depth":237,"text":573},{"id":656,"depth":237,"text":657},{"id":791,"depth":237,"text":792},{"id":837,"depth":237,"text":838},{"id":924,"depth":237,"text":925},{"id":931,"depth":237,"text":932},{"id":980,"depth":237,"text":981},{"id":998,"depth":237,"text":999,"children":1086},[1087,1088,1089,1090],{"id":1003,"depth":243,"text":1004},{"id":1010,"depth":243,"text":1011},{"id":1017,"depth":243,"text":1018},{"id":1024,"depth":243,"text":1025},{"id":1031,"depth":237,"text":1032},[1093,1096,1099,1100],{"name":1094,"item":1095},"Home","\u002F",{"name":1097,"item":1098},"Production-Ready Deployment & CI\u002FCD Workflows","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":33,"item":32},{"name":5,"item":1101},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fmigrating-from-cloudflare-pages-to-workers-static-assets\u002F","2026-09-18","Move a static site from Cloudflare Pages to Workers static assets: wrangler config, _headers and _redirects, previews and a zero-downtime domain cutover.","md",[1106,1107,1108,1109],{"q":1004,"a":1007},{"q":1011,"a":1014},{"q":1018,"a":1021},{"q":1025,"a":1028},{},true,"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fmigrating-from-cloudflare-pages-to-workers-static-assets",{"title":5,"description":1103},"production-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fmigrating-from-cloudflare-pages-to-workers-static-assets\u002Findex","article","Bwbwe5nchoYVf1EYVGWv2Yy9nqxj6EhKKoceX_3kHOg",[1118,1121,1124,1127,1130,1133,1136,1139,1142,1145,1148,1151,1154,1157,1160,1163,1166,1169,1172,1175,1178,1181,1184,1187,1190,1193,1196,1199,1202,1205,1208,1211,1214,1217,1220,1223,1226,1229,1232,1235,1238,1241,1244,1247,1250,1253,1256,1259,1262,1265,1268,1271,1274,1277,1280,1283,1286,1289,1292,1295,1298,1301,1304,1307,1310,1313,1316,1319,1322,1325,1328,1331,1334,1337,1340,1343,1346,1349,1352,1355,1358,1361,1364,1367,1370,1373,1376,1379,1382,1385,1388,1391,1394,1397,1400,1403,1406,1409,1412,1415,1418,1421,1424,1427,1430,1433,1436,1439,1442,1445,1448,1451,1454,1457,1459,1461,1463,1465,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,1567,1570,1573,1576,1579,1582,1585,1587,1590,1593,1595,1598,1601,1604,1607,1610,1613,1616,1618,1621,1624,1627,1630,1633,1636,1639,1641,1644,1647,1650,1653],{"path":1119,"title":1120},"\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":1122,"title":1123},"\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":1125,"title":1126},"\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":1128,"title":1129},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1131,"title":1132},"\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":1134,"title":1135},"\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":1137,"title":1138},"\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":1140,"title":1141},"\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":1143,"title":1144},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1146,"title":1147},"\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":1149,"title":1150},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1152,"title":1153},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1155,"title":1156},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1158,"title":1159},"\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":1161,"title":1162},"\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":1164,"title":1165},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1167,"title":1168},"\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":1170,"title":1171},"\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":1173,"title":1174},"\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":1176,"title":1177},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1179,"title":1180},"\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":1182,"title":1183},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1185,"title":1186},"\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":1188,"title":1189},"\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":1191,"title":1192},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1194,"title":1195},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1197,"title":1198},"\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":1200,"title":1201},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1203,"title":1204},"\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":1206,"title":1207},"\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":1209,"title":1210},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1212,"title":1213},"\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":1215,"title":1216},"\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":1218,"title":1219},"\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":1221,"title":1222},"\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":1224,"title":1225},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1227,"title":1228},"\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":1230,"title":1231},"\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":1233,"title":1234},"\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":1236,"title":1237},"\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":1239,"title":1240},"\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":1242,"title":1243},"\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":1245,"title":1246},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1248,"title":1249},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1251,"title":1252},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1254,"title":1255},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1257,"title":1258},"\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":1260,"title":1261},"\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":1263,"title":1264},"\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":1266,"title":1267},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1269,"title":1270},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1272,"title":1273},"\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":1275,"title":1276},"\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":1278,"title":1279},"\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":1281,"title":1282},"\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":1284,"title":1285},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1287,"title":1288},"\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":1290,"title":1291},"\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":1293,"title":1294},"\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":1296,"title":1297},"\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":1299,"title":1300},"\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":1302,"title":1303},"\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":1305,"title":1306},"\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":1308,"title":1309},"\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":1311,"title":1312},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1314,"title":1315},"\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":1317,"title":1318},"\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":1320,"title":1321},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1323,"title":1324},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1326,"title":1327},"\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":1329,"title":1330},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1332,"title":1333},"\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":1335,"title":1336},"\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":1338,"title":1339},"\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":1341,"title":1342},"\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":1344,"title":1345},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1347,"title":1348},"\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":1350,"title":1351},"\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":1353,"title":1354},"\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":1356,"title":1357},"\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":1359,"title":1360},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1362,"title":1363},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1365,"title":1366},"\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":1368,"title":1369},"\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":1371,"title":1372},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1374,"title":1375},"\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":1377,"title":1378},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1380,"title":1381},"\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":1383,"title":1384},"\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":1386,"title":1387},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1389,"title":1390},"\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":1392,"title":1393},"\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":1395,"title":1396},"\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":1398,"title":1399},"\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":1401,"title":1402},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1404,"title":1405},"\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":1407,"title":1408},"\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":1410,"title":1411},"\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":1413,"title":1414},"\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":1416,"title":1417},"\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":1419,"title":1420},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1422,"title":1423},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1425,"title":1426},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1428,"title":1429},"\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":1431,"title":1432},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1434,"title":1435},"\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":1437,"title":1438},"\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":1440,"title":1441},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1443,"title":1444},"\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":1446,"title":1447},"\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":1449,"title":1450},"\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":1452,"title":1453},"\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":1455,"title":1456},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1458,"title":392},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages",{"path":1460,"title":1055},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcustom-domains-and-tls-on-cloudflare-pages",{"path":1462,"title":1048},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fdeploying-hugo-to-cloudflare-pages-and-workers",{"path":1464,"title":33},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup",{"path":1112,"title":5},{"path":1467,"title":1468},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1470,"title":1471},"\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":1473,"title":1474},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1476,"title":1477},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1479,"title":1480},"\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":1482,"title":1483},"\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":1485,"title":1486},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1488,"title":1489},"\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":1491,"title":1492},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1494,"title":1495},"\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":1497,"title":1498},"\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":1500,"title":1501},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1503,"title":1504},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1506,"title":1507},"\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":1509,"title":1510},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1512,"title":1513},"\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":1515,"title":1516},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1518,"title":1519},"\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":1521,"title":1522},"\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":1524,"title":1525},"\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":1527,"title":1528},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1530,"title":1531},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1533,"title":1534},"\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":1536,"title":1537},"\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":1539,"title":1540},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1542,"title":1543},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1545,"title":1546},"\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":1548,"title":1549},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1551,"title":1552},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1554,"title":1555},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1557,"title":1558},"\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":1560,"title":1561},"\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":1563,"title":1564},"\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":1566,"title":653},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fautomating-preview-deploy-pipelines-with-github-actions",{"path":1568,"title":1569},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1571,"title":1572},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":1574,"title":1575},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1577,"title":1578},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1580,"title":1581},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1583,"title":1584},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1586,"title":849},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites",{"path":1588,"title":1589},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1591,"title":1592},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1594,"title":788},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-a-bad-static-deploy-in-under-a-minute",{"path":1596,"title":1597},"\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":1599,"title":1600},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1602,"title":1603},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1605,"title":1606},"\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":1608,"title":1609},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1611,"title":1612},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1614,"title":1615},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1617,"title":388},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fwriting-a-content-security-policy-for-a-static-site",{"path":1619,"title":1620},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1622,"title":1623},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1625,"title":1626},"\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":1628,"title":1629},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1631,"title":1632},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1634,"title":1635},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1637,"title":1638},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1640,"title":834},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fadding-a-contact-form-with-cloudflare-workers",{"path":1642,"title":1643},"\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":1645,"title":1646},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1648,"title":1649},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1651,"title":1652},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1654,"title":1655},"\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",1789722847254]