[{"data":1,"prerenderedAt":1624},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites":3,"all-docs-nav":1082},{"id":4,"title":5,"body":6,"breadcrumb":1057,"dateModified":1067,"datePublished":1067,"description":1068,"extension":1069,"faq":1070,"meta":1075,"navigation":1076,"path":1077,"seo":1078,"slug":12,"stem":1079,"type":1080,"__hash__":1081},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites\u002Findex.md","Feature Flags on Static Sites",{"type":7,"value":8,"toc":1039},"minimark",[9,13,17,26,31,48,52,191,195,198,278,315,322,329,333,336,339,376,614,621,628,632,635,638,668,756,760,763,789,907,911,914,918,954,958,961,965,970,973,977,980,984,987,991,994,998,1035],[10,11,5],"h1",{"id":12},"feature-flags-on-static-sites",[14,15,16],"p",{},"Feature flags separate deploying code from releasing features. Code for a new search interface, a redesigned pricing table or an interactive tutorial ships to production switched off, and the team turns it on when they are ready — for everyone, for internal users first, or for a percentage of readers. If something goes wrong, the feature is switched off again without a deploy or a rollback of unrelated changes.",[14,18,19,20,25],{},"On a server-rendered application, flags are evaluated per request. A static site has no request-time server by default, which is why teams often assume flags do not apply. They do, in three forms: build-time flags, flags evaluated at the edge, and flags evaluated in the browser. This guide covers when to use each, how to implement them without flicker or layout shift, and how to keep flags from turning into permanent clutter. It is part of ",[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",".",[27,28,30],"h2",{"id":29},"prerequisites","Prerequisites",[32,33,34,42,45],"ul",{},[35,36,37,38,25],"li",{},"A static site with a deployment pipeline you trust — see ",[21,39,41],{"href":40},"\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",[35,43,44],{},"For edge flags: a host with edge functions (Cloudflare Workers, Netlify Edge Functions, Vercel Middleware).",[35,46,47],{},"Optional: a flag service such as LaunchDarkly, Flagsmith, GrowthBook or Unleash, or a simple JSON file in a key-value store.",[27,49,51],{"id":50},"three-places-to-evaluate-a-flag","Three Places to Evaluate a Flag",[53,54,55,187],"figure",{},[56,57,64,65,64,69,64,73,64,80],"svg",{"viewBox":58,"role":59,"ariaLabelledBy":60,"xmlns":63},"0 0 760 290","img",[61,62],"ffs-where-title","ffs-where-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[66,67,68],"title",{"id":61},"Build-time, edge and client feature flags compared",[70,71,72],"desc",{"id":62},"Build-time flags are evaluated during the build, need a rebuild to change, have no runtime cost and no flicker. Edge flags are evaluated by a CDN function per request, change instantly, can target users, and serve the right HTML without flicker. Client flags are evaluated in the browser, change instantly and target users, but risk flicker and layout shift and add JavaScript.",[74,75],"rect",{"x":76,"y":76,"width":77,"height":78,"fill":79},"0","760","290","#ffffff",[81,82,84,85,84,93,84,102,84,108,84,113,84,117,84,122,84,126,84,130,84,136,84,139,84,142,84,146,84,149,84,151,84,155,84,158,84,161,84,164,84,168,84,171,84,174,84,178,84,181,84,184,64],"g",{"style":83},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[86,87,92],"text",{"x":88,"y":89,"fill":90,"style":91},"380","26","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Where the flag is evaluated decides its trade-offs",[74,94],{"x":95,"y":96,"width":97,"height":98,"rx":99,"fill":100,"style":101,"stroke":100},"20","46","230","220","8","#166a9e","fill-opacity:0.06",[86,103,107],{"x":104,"y":105,"fill":100,"style":106},"135","72","font-weight:700;text-anchor:middle","Build time",[86,109,112],{"x":110,"y":111,"fill":90},"36","102","toggle → rebuild (minutes)",[86,114,116],{"x":110,"y":115,"fill":90},"126","same for every reader",[86,118,121],{"x":110,"y":119,"fill":120},"150","#3f6410","no runtime cost",[86,123,125],{"x":110,"y":124,"fill":120},"174","no flicker",[86,127,129],{"x":110,"y":128,"fill":120},"198","off variant not shipped",[86,131,135],{"x":110,"y":132,"fill":133,"style":134},"244","#556071","font-size:11px","release toggles",[74,137],{"x":138,"y":96,"width":97,"height":98,"rx":99,"fill":120,"style":101,"stroke":120},"265",[86,140,141],{"x":88,"y":105,"fill":120,"style":106},"Edge",[86,143,145],{"x":144,"y":111,"fill":90},"281","toggle → instant",[86,147,148],{"x":144,"y":115,"fill":90},"per user, cookie, country",[86,150,125],{"x":144,"y":119,"fill":120},[86,152,154],{"x":144,"y":124,"fill":153},"#8a6d0f","both variants built",[86,156,157],{"x":144,"y":128,"fill":153},"small edge cost per request",[86,159,160],{"x":144,"y":132,"fill":133,"style":134},"gradual rollouts, kill switches",[74,162],{"x":163,"y":96,"width":97,"height":98,"rx":99,"fill":153,"style":101,"stroke":153},"510",[86,165,167],{"x":166,"y":105,"fill":153,"style":106},"625","Client",[86,169,145],{"x":170,"y":111,"fill":90},"526",[86,172,173],{"x":170,"y":115,"fill":90},"per user in the browser",[86,175,177],{"x":170,"y":119,"fill":176},"#b32b30","flicker, layout shift risk",[86,179,180],{"x":170,"y":124,"fill":176},"extra JavaScript",[86,182,183],{"x":170,"y":128,"fill":153},"both variants shipped",[86,185,186],{"x":170,"y":132,"fill":133,"style":134},"below-the-fold widgets",[188,189,190],"figcaption",{},"Prefer the earliest point that meets the need; move later only when you need instant or per-user toggles.",[27,192,194],{"id":193},"build-time-flags","Build-Time Flags",[14,196,197],{},"The simplest flag is a value read during the build. The generator decides what to output, and the HTML contains only the enabled variant:",[199,200,205],"pre",{"className":201,"code":202,"language":203,"meta":204,"style":204},"language-js shiki shiki-themes github-light github-dark","\u002F\u002F src\u002Fconfig\u002Fflags.js\nexport const flags = {\n  newSearch: process.env.FLAG_NEW_SEARCH === 'true',\n  pricingV2: process.env.FLAG_PRICING_V2 === 'true',\n};\n","js","",[206,207,208,217,238,257,272],"code",{"__ignoreMap":204},[209,210,213],"span",{"class":211,"line":212},"line",1,[209,214,216],{"class":215},"sJ8bj","\u002F\u002F src\u002Fconfig\u002Fflags.js\n",[209,218,220,224,227,231,234],{"class":211,"line":219},2,[209,221,223],{"class":222},"szBVR","export",[209,225,226],{"class":222}," const",[209,228,230],{"class":229},"sj4cs"," flags",[209,232,233],{"class":222}," =",[209,235,237],{"class":236},"sVt8B"," {\n",[209,239,241,244,247,250,254],{"class":211,"line":240},3,[209,242,243],{"class":236},"  newSearch: process.env.",[209,245,246],{"class":229},"FLAG_NEW_SEARCH",[209,248,249],{"class":222}," ===",[209,251,253],{"class":252},"sZZnC"," 'true'",[209,255,256],{"class":236},",\n",[209,258,260,263,266,268,270],{"class":211,"line":259},4,[209,261,262],{"class":236},"  pricingV2: process.env.",[209,264,265],{"class":229},"FLAG_PRICING_V2",[209,267,249],{"class":222},[209,269,253],{"class":252},[209,271,256],{"class":236},[209,273,275],{"class":211,"line":274},5,[209,276,277],{"class":236},"};\n",[199,279,283],{"className":280,"code":281,"language":282,"meta":204,"style":204},"language-astro shiki shiki-themes github-light github-dark","---\nimport { flags } from '..\u002Fconfig\u002Fflags';\nimport SearchV1 from '..\u002Fcomponents\u002FSearchV1.astro';\nimport SearchV2 from '..\u002Fcomponents\u002FSearchV2.astro';\n---\n{flags.newSearch ? \u003CSearchV2 \u002F> : \u003CSearchV1 \u002F>}\n","astro",[206,284,285,290,295,300,305,309],{"__ignoreMap":204},[209,286,287],{"class":211,"line":212},[209,288,289],{},"---\n",[209,291,292],{"class":211,"line":219},[209,293,294],{},"import { flags } from '..\u002Fconfig\u002Fflags';\n",[209,296,297],{"class":211,"line":240},[209,298,299],{},"import SearchV1 from '..\u002Fcomponents\u002FSearchV1.astro';\n",[209,301,302],{"class":211,"line":259},[209,303,304],{},"import SearchV2 from '..\u002Fcomponents\u002FSearchV2.astro';\n",[209,306,307],{"class":211,"line":274},[209,308,289],{},[209,310,312],{"class":211,"line":311},6,[209,313,314],{},"{flags.newSearch ? \u003CSearchV2 \u002F> : \u003CSearchV1 \u002F>}\n",[14,316,317,318,321],{},"Toggle by changing the environment variable in the host's settings and triggering a rebuild. Hugo reads environment variables through ",[206,319,320],{},"getenv"," or site parameters in an environment-specific config file; Eleventy reads them in a global data file.",[14,323,324,325,328],{},"Build-time flags are ideal for release toggles: finish a feature on ",[206,326,327],{},"main"," behind a flag, ship it dark with every deploy, and flip it on for launch. Because the off variant is never in the HTML, unreleased pages and copy stay private, which client flags cannot guarantee. The limitation is speed — turning a feature off means a rebuild, typically a few minutes.",[27,330,332],{"id":331},"edge-flags","Edge Flags",[14,334,335],{},"For instant toggles and per-user targeting without flicker, evaluate flags at the edge. Build both variants into the site, and let an edge function choose which one to serve.",[14,337,338],{},"Two patterns work well:",[340,341,342,366],"ol",{},[35,343,344,348,349,352,353,356,357,359,360,362,363,365],{},[345,346,347],"strong",{},"Route to a variant path."," Build ",[206,350,351],{},"\u002Fpricing\u002F"," and ",[206,354,355],{},"\u002Fpricing-v2\u002F","; the edge function rewrites ",[206,358,351],{}," to ",[206,361,355],{}," when the flag is on for this request. The reader sees ",[206,364,351],{}," in the address bar.",[35,367,368,371,372,375],{},[345,369,370],{},"Rewrite HTML in flight."," Build one page with both variants marked, such as ",[206,373,374],{},"\u003Cdiv data-flag=\"newSearch\" data-variant=\"on\">",", and use an HTML rewriter at the edge to remove the variant that is off.",[199,377,381],{"className":378,"code":379,"language":380,"meta":204,"style":204},"language-ts shiki shiki-themes github-light github-dark","\u002F\u002F Cloudflare Worker: variant routing with a KV-stored flag\nexport default {\n  async fetch(request: Request, env: Env) {\n    const url = new URL(request.url);\n    if (url.pathname === '\u002Fpricing\u002F') {\n      const rollout = Number((await env.FLAGS.get('pricingV2')) ?? 0); \u002F\u002F 0..100\n      const bucket = bucketFor(request.headers.get('Cookie'));          \u002F\u002F stable 0..99 per visitor\n      if (bucket \u003C rollout) url.pathname = '\u002Fpricing-v2\u002F';\n    }\n    return env.ASSETS.fetch(new Request(url, request));\n  },\n};\n","ts",[206,382,383,388,397,433,452,468,518,547,571,577,603,609],{"__ignoreMap":204},[209,384,385],{"class":211,"line":212},[209,386,387],{"class":215},"\u002F\u002F Cloudflare Worker: variant routing with a KV-stored flag\n",[209,389,390,392,395],{"class":211,"line":219},[209,391,223],{"class":222},[209,393,394],{"class":222}," default",[209,396,237],{"class":236},[209,398,399,402,406,409,413,416,419,422,425,427,430],{"class":211,"line":240},[209,400,401],{"class":222},"  async",[209,403,405],{"class":404},"sScJk"," fetch",[209,407,408],{"class":236},"(",[209,410,412],{"class":411},"s4XuR","request",[209,414,415],{"class":222},":",[209,417,418],{"class":404}," Request",[209,420,421],{"class":236},", ",[209,423,424],{"class":411},"env",[209,426,415],{"class":222},[209,428,429],{"class":404}," Env",[209,431,432],{"class":236},") {\n",[209,434,435,438,441,443,446,449],{"class":211,"line":259},[209,436,437],{"class":222},"    const",[209,439,440],{"class":229}," url",[209,442,233],{"class":222},[209,444,445],{"class":222}," new",[209,447,448],{"class":404}," URL",[209,450,451],{"class":236},"(request.url);\n",[209,453,454,457,460,463,466],{"class":211,"line":274},[209,455,456],{"class":222},"    if",[209,458,459],{"class":236}," (url.pathname ",[209,461,462],{"class":222},"===",[209,464,465],{"class":252}," '\u002Fpricing\u002F'",[209,467,432],{"class":236},[209,469,470,473,476,478,481,484,487,490,493,495,498,500,503,506,509,512,515],{"class":211,"line":311},[209,471,472],{"class":222},"      const",[209,474,475],{"class":229}," rollout",[209,477,233],{"class":222},[209,479,480],{"class":404}," Number",[209,482,483],{"class":236},"((",[209,485,486],{"class":222},"await",[209,488,489],{"class":236}," env.",[209,491,492],{"class":229},"FLAGS",[209,494,25],{"class":236},[209,496,497],{"class":404},"get",[209,499,408],{"class":236},[209,501,502],{"class":252},"'pricingV2'",[209,504,505],{"class":236},")) ",[209,507,508],{"class":222},"??",[209,510,511],{"class":229}," 0",[209,513,514],{"class":236},"); ",[209,516,517],{"class":215},"\u002F\u002F 0..100\n",[209,519,521,523,526,528,531,534,536,538,541,544],{"class":211,"line":520},7,[209,522,472],{"class":222},[209,524,525],{"class":229}," bucket",[209,527,233],{"class":222},[209,529,530],{"class":404}," bucketFor",[209,532,533],{"class":236},"(request.headers.",[209,535,497],{"class":404},[209,537,408],{"class":236},[209,539,540],{"class":252},"'Cookie'",[209,542,543],{"class":236},"));          ",[209,545,546],{"class":215},"\u002F\u002F stable 0..99 per visitor\n",[209,548,550,553,556,559,562,565,568],{"class":211,"line":549},8,[209,551,552],{"class":222},"      if",[209,554,555],{"class":236}," (bucket ",[209,557,558],{"class":222},"\u003C",[209,560,561],{"class":236}," rollout) url.pathname ",[209,563,564],{"class":222},"=",[209,566,567],{"class":252}," '\u002Fpricing-v2\u002F'",[209,569,570],{"class":236},";\n",[209,572,574],{"class":211,"line":573},9,[209,575,576],{"class":236},"    }\n",[209,578,580,583,585,588,590,593,595,598,600],{"class":211,"line":579},10,[209,581,582],{"class":222},"    return",[209,584,489],{"class":236},[209,586,587],{"class":229},"ASSETS",[209,589,25],{"class":236},[209,591,592],{"class":404},"fetch",[209,594,408],{"class":236},[209,596,597],{"class":222},"new",[209,599,418],{"class":404},[209,601,602],{"class":236},"(url, request));\n",[209,604,606],{"class":211,"line":605},11,[209,607,608],{"class":236},"  },\n",[209,610,612],{"class":211,"line":611},12,[209,613,277],{"class":236},[14,615,616,617,25],{},"Changing the KV value takes effect within seconds, with no rebuild. The visitor's bucket comes from a cookie set on first visit, so each reader consistently sees the same variant. The HTML served is complete and correct for that reader, so there is no flicker and no layout shift. The same approach powers the traffic split in ",[21,618,620],{"href":619},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites\u002F","Canary Releases for Static Sites",[14,622,623,624,627],{},"When HTML varies per visitor, make sure the CDN does not cache one visitor's variant for another: add ",[206,625,626],{},"Vary: Cookie",", cache by variant path rather than original path, or skip caching flagged HTML.",[27,629,631],{"id":630},"client-flags","Client Flags",[14,633,634],{},"Client-side flags are evaluated by a JavaScript SDK after the page loads. They are the most flexible and the most dangerous for performance: a component that appears, disappears or changes after first paint causes layout shift and a visible flicker.",[14,636,637],{},"Use them for changes that are below the fold, inside interactive widgets, or not visual at all — an analytics event, a different API endpoint for search. When a client flag must affect visible content:",[32,639,640,646,652,662],{},[35,641,642,645],{},[345,643,644],{},"Render the default in the static HTML"," and switch only when the flag is on, so most readers see no change.",[35,647,648,651],{},[345,649,650],{},"Reserve space"," for anything the flag might add, using fixed dimensions.",[35,653,654,657,658,661],{},[345,655,656],{},"Evaluate before paint only for tiny changes",", with a small inline script and flags cached in ",[206,659,660],{},"localStorage"," from the previous visit.",[35,663,664,667],{},[345,665,666],{},"Never block rendering"," waiting for a flag service to respond.",[53,669,670,753],{},[56,671,64,676,64,679,64,682,64,685],{"viewBox":672,"role":59,"ariaLabelledBy":673,"xmlns":63},"0 0 760 240",[674,675],"ffs-cls-title","ffs-cls-desc",[66,677,678],{"id":674},"Layout shift from the same banner flagged three ways",[70,680,681],{"id":675},"A promotional banner above the article controlled by a flag. Evaluated on the client after load, it caused CLS p75 of 0.14. Evaluated on the client with reserved space, CLS was 0.03 but the space was empty for readers without the flag. Evaluated at the edge, CLS was 0.01 and the HTML was correct for every reader.",[74,683],{"x":76,"y":76,"width":77,"height":684,"fill":79},"240",[81,686,84,687,84,691,84,697,84,701,84,707,84,714,84,720,84,724,84,728,84,732,84,735,84,741,84,745,84,748,64],{"style":83},[86,688,690],{"x":88,"y":689,"fill":90,"style":91},"28","CLS p75 for a flagged banner above the article",[211,692],{"x1":693,"y1":694,"x2":695,"y2":694,"stroke":133,"style":696},"60","190","700","stroke-width:1.5px",[211,698],{"x1":693,"y1":699,"x2":695,"y2":699,"stroke":120,"style":700},"104","stroke-width:1px;stroke-dasharray:5 4",[86,702,706],{"x":703,"y":704,"fill":120,"style":705},"696","98","font-size:11px;text-anchor:end","0.1 good threshold",[74,708],{"x":709,"y":710,"width":711,"height":709,"fill":712,"style":713},"120","70","100","#d83b41","fill-opacity:0.45",[86,715,719],{"x":716,"y":717,"fill":90,"style":718},"170","64","text-anchor:middle","0.14",[86,721,723],{"x":716,"y":722,"fill":133,"style":718},"208","client, after load",[74,725],{"x":726,"y":727,"width":711,"height":89,"fill":153,"style":713},"330","164",[86,729,731],{"x":88,"y":730,"fill":90,"style":718},"158","0.03",[86,733,734],{"x":88,"y":722,"fill":133,"style":718},"client, space reserved",[74,736],{"x":737,"y":738,"width":711,"height":739,"fill":120,"style":740},"540","181","9","fill-opacity:0.6",[86,742,744],{"x":743,"y":124,"fill":90,"style":718},"590","0.01",[86,746,747],{"x":743,"y":722,"fill":133,"style":718},"edge-evaluated",[86,749,752],{"x":88,"y":750,"fill":133,"style":751},"232","font-size:11px;text-anchor:middle","reserved space avoided the shift but left an empty band for readers without the flag",[188,754,755],{},"Anything visible above the fold should be flagged at build time or at the edge.",[27,757,759],{"id":758},"keeping-flags-under-control","Keeping Flags Under Control",[14,761,762],{},"Flags are temporary by design and permanent by default. Each one adds a code path to test, and old flags make templates hard to read. A few habits keep the number down:",[32,764,765,771,777,783],{},[35,766,767,770],{},[345,768,769],{},"Register every flag"," in one file or service with an owner, a purpose and an expiry date.",[35,772,773,776],{},[345,774,775],{},"Fail CI on expired flags."," A script that reads the registry and fails when a flag is past its date forces a decision: remove it or extend it deliberately.",[35,778,779,782],{},[345,780,781],{},"Remove flags after launch."," Once a feature has been on for everyone for a release or two, delete the flag and the old code path in one pull request.",[35,784,785,788],{},[345,786,787],{},"Test both states."," Run the build and key checks with each release flag on and off, at least before the launch, so flipping it is not the first time the combination is exercised.",[53,790,791,904],{},[56,792,64,797,64,800,64,803,64,805,64,820],{"viewBox":793,"role":59,"ariaLabelledBy":794,"xmlns":63},"0 0 760 220",[795,796],"ffs-life-title","ffs-life-desc",[66,798,799],{"id":795},"Lifecycle of a release flag",[70,801,802],{"id":796},"A flag is created with an owner and expiry, code ships dark behind it, the feature is rolled out, the flag stays fully on for a release or two, and then the flag and the old code path are removed. A CI check fails if the flag passes its expiry date before removal.",[74,804],{"x":76,"y":76,"width":77,"height":98,"fill":79},[806,807,84,808,64],"defs",{},[809,810,816],"marker",{"id":811,"viewBox":812,"refX":739,"refY":813,"markerWidth":814,"markerHeight":814,"orient":815},"ffs-life-arrow","0 0 10 10","5","7","auto-start-reverse",[817,818],"path",{"d":819,"fill":133},"M0,0 L10,5 L0,10 z",[81,821,84,822,84,825,84,829,84,834,84,838,84,841,84,845,84,848,84,851,84,855,84,858,84,861,84,865,84,868,84,874,84,878,84,881,84,885,84,889,84,893,84,897,84,900,64],{"style":83},[86,823,824],{"x":88,"y":89,"fill":90,"style":91},"Every flag has an end",[74,826],{"x":95,"y":710,"width":709,"height":827,"rx":99,"fill":100,"style":828,"stroke":100},"56","fill-opacity:0.1",[86,830,833],{"x":831,"y":832,"fill":90,"style":718},"80","94","create",[86,835,837],{"x":831,"y":836,"fill":133,"style":751},"112","owner + expiry",[74,839],{"x":840,"y":710,"width":709,"height":827,"rx":99,"fill":133,"style":828,"stroke":133},"165",[86,842,844],{"x":843,"y":832,"fill":90,"style":718},"225","ship dark",[86,846,847],{"x":843,"y":836,"fill":133,"style":751},"flag off",[74,849],{"x":850,"y":710,"width":709,"height":827,"rx":99,"fill":153,"style":828,"stroke":153},"310",[86,852,854],{"x":853,"y":832,"fill":90,"style":718},"370","roll out",[86,856,857],{"x":853,"y":836,"fill":133,"style":751},"10 → 50 → 100%",[74,859],{"x":860,"y":710,"width":709,"height":827,"rx":99,"fill":120,"style":828,"stroke":120},"455",[86,862,864],{"x":863,"y":832,"fill":90,"style":718},"515","fully on",[86,866,867],{"x":863,"y":836,"fill":133,"style":751},"1–2 releases",[74,869],{"x":870,"y":710,"width":871,"height":827,"rx":99,"fill":872,"style":873,"stroke":872},"600","140","#6a4c93","fill-opacity:0.12",[86,875,877],{"x":876,"y":832,"fill":90,"style":718},"670","remove",[86,879,880],{"x":876,"y":836,"fill":133,"style":751},"flag + old path",[211,882],{"x1":871,"y1":704,"x2":883,"y2":704,"stroke":133,"style":884},"161","stroke-width:1.5px;marker-end:url(#ffs-life-arrow)",[211,886],{"x1":887,"y1":704,"x2":888,"y2":704,"stroke":133,"style":884},"285","306",[211,890],{"x1":891,"y1":704,"x2":892,"y2":704,"stroke":133,"style":884},"430","451",[211,894],{"x1":895,"y1":704,"x2":896,"y2":704,"stroke":133,"style":884},"575","596",[86,898,899],{"x":88,"y":716,"fill":176,"style":718},"CI fails if the expiry date passes before the \"remove\" step",[86,901,903],{"x":88,"y":902,"fill":133,"style":751},"200","kill switches for risky integrations are the exception: long-lived by design, still registered",[188,905,906],{},"The removal step is part of the feature, not an optional clean-up.",[27,908,910],{"id":909},"measured-impact","Measured Impact",[14,912,913],{},"A SaaS documentation and marketing site built with Astro on Cloudflare adopted build-time flags for release toggles and edge flags for gradual rollouts. A redesigned pricing page was rolled out through 10%, 50% and 100% over a week with a KV-stored rollout value, while conversion was compared between groups; a checkout link bug found at 10% was fixed before wider rollout. A client-flagged banner that had caused a CLS regression was moved to the edge, bringing the homepage's CLS p75 from 0.14 back to 0.01. A CI check on flag expiry kept the registry below ten active flags.",[27,915,917],{"id":916},"pitfalls-rollback","Pitfalls & Rollback",[32,919,920,926,936,942,948],{},[35,921,922,925],{},[345,923,924],{},"Unreleased content in client bundles."," Client flags ship both variants; use build-time flags for anything confidential.",[35,927,928,931,932,935],{},[345,929,930],{},"Cached variants."," Per-visitor HTML cached without a ",[206,933,934],{},"Vary"," or variant key leaks one reader's variant to others.",[35,937,938,941],{},[345,939,940],{},"Flag service outages."," Default to the safe variant when the flag source is unreachable, at the edge and on the client.",[35,943,944,947],{},[345,945,946],{},"Nested flags."," Features that depend on other flags multiply test combinations; keep flags independent.",[35,949,950,953],{},[345,951,952],{},"Rollback:"," set the flag off; for build-time flags, rebuild or redeploy the previous build.",[27,955,957],{"id":956},"conclusion","Conclusion",[14,959,960],{},"Static sites can use feature flags as effectively as server-rendered ones by choosing where to evaluate them. Build-time flags suit release toggles and keep unreleased content private; edge flags give instant, per-reader toggles and gradual rollouts without flicker; client flags suit below-the-fold and non-visual changes. Register every flag with an owner and expiry, test both states, and remove flags once the feature has shipped.",[27,962,964],{"id":963},"faq","FAQ",[966,967,969],"h3",{"id":968},"can-a-static-site-use-feature-flags","Can a static site use feature flags?",[14,971,972],{},"Yes, in three ways. Build-time flags decide what is generated and need a rebuild to change. Edge flags are evaluated by a CDN function per request and can switch features instantly. Client flags are evaluated in JavaScript in the browser, which is flexible but can cause flicker and layout shift.",[966,974,976],{"id":975},"how-do-i-avoid-flicker-with-client-side-feature-flags","How do I avoid flicker with client-side feature flags?",[14,978,979],{},"Render the default state in the static HTML and only enhance it when the flag is on, reserve space for any element the flag might show, and evaluate flags before first paint only for small, above-the-fold changes. For larger changes, evaluate at the edge and serve the right HTML directly.",[966,981,983],{"id":982},"when-should-i-use-build-time-flags","When should I use build-time flags?",[14,985,986],{},"For features tied to a release, such as a new section or navigation change, where a rebuild on toggle is acceptable. Build-time flags add no runtime cost and no flicker, and the output contains only the enabled variant, which keeps unreleased content out of the public HTML.",[966,988,990],{"id":989},"how-do-i-stop-feature-flags-from-piling-up","How do I stop feature flags from piling up?",[14,992,993],{},"Give every flag an owner and an expiry date when it is created, list flags in one configuration file or service, and remove the flag and the dead code path once a feature has been fully on for a release or two. A CI check can fail when a flag is past its expiry.",[27,995,997],{"id":996},"related","Related",[32,999,1000,1009,1014,1021,1028],{},[35,1001,1002,1005,1006,1008],{},[345,1003,1004],{},"Parent:"," ",[21,1007,24],{"href":23}," — every deploy safety technique.",[35,1010,1011,1013],{},[21,1012,620],{"href":619}," — rolling out whole builds gradually.",[35,1015,1016,1020],{},[21,1017,1019],{"href":1018},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frunning-smoke-tests-against-a-preview-url\u002F","Running Smoke Tests Against a Preview URL"," — testing both flag states.",[35,1022,1023,1027],{},[21,1024,1026],{"href":1025},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-cookie-banners\u002F","Fixing CLS from Cookie Banners"," — the same layout-shift trap.",[35,1029,1030,1034],{},[21,1031,1033],{"href":1032},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers\u002F","Netlify Functions vs Cloudflare Workers"," — choosing where edge flags run.",[1036,1037,1038],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}",{"title":204,"searchDepth":219,"depth":219,"links":1040},[1041,1042,1043,1044,1045,1046,1047,1048,1049,1050,1056],{"id":29,"depth":219,"text":30},{"id":50,"depth":219,"text":51},{"id":193,"depth":219,"text":194},{"id":331,"depth":219,"text":332},{"id":630,"depth":219,"text":631},{"id":758,"depth":219,"text":759},{"id":909,"depth":219,"text":910},{"id":916,"depth":219,"text":917},{"id":956,"depth":219,"text":957},{"id":963,"depth":219,"text":964,"children":1051},[1052,1053,1054,1055],{"id":968,"depth":240,"text":969},{"id":975,"depth":240,"text":976},{"id":982,"depth":240,"text":983},{"id":989,"depth":240,"text":990},{"id":996,"depth":219,"text":997},[1058,1061,1064,1065],{"name":1059,"item":1060},"Home","\u002F",{"name":1062,"item":1063},"Production-Ready Deployment & CI\u002FCD Workflows","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":24,"item":23},{"name":5,"item":1066},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites\u002F","2026-09-18","Ship code dark and turn features on without a rebuild: build-time flags, edge-evaluated flags and client flags on static sites, and how to avoid flicker.","md",[1071,1072,1073,1074],{"q":969,"a":972},{"q":976,"a":979},{"q":983,"a":986},{"q":990,"a":993},{},true,"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites",{"title":5,"description":1068},"production-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites\u002Findex","article","zs2EfFRAQ_IzEvLenRyFAOQJyxMJ6OEwg2J55HflQ3k",[1083,1086,1089,1092,1095,1098,1101,1104,1107,1110,1113,1116,1119,1122,1125,1128,1131,1134,1137,1140,1143,1146,1149,1152,1155,1158,1161,1164,1167,1170,1173,1176,1179,1182,1185,1188,1191,1194,1197,1200,1203,1206,1209,1212,1215,1218,1221,1224,1227,1230,1233,1236,1239,1242,1245,1248,1251,1254,1257,1260,1263,1266,1268,1271,1274,1277,1280,1283,1286,1289,1292,1295,1298,1301,1304,1307,1310,1313,1316,1319,1322,1325,1328,1331,1334,1337,1340,1343,1346,1349,1352,1355,1358,1361,1364,1367,1370,1373,1376,1379,1382,1385,1388,1391,1394,1397,1400,1403,1406,1409,1412,1415,1418,1421,1424,1427,1430,1433,1436,1439,1442,1445,1448,1451,1454,1457,1460,1463,1466,1469,1472,1475,1478,1481,1484,1487,1490,1493,1496,1499,1502,1505,1508,1511,1514,1517,1520,1523,1526,1529,1532,1535,1538,1541,1544,1547,1550,1553,1556,1558,1559,1561,1563,1565,1568,1571,1574,1577,1580,1583,1586,1589,1592,1595,1598,1601,1604,1607,1610,1613,1616,1618,1621],{"path":1084,"title":1085},"\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":1087,"title":1088},"\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":1090,"title":1091},"\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":1093,"title":1094},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1096,"title":1097},"\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":1099,"title":1100},"\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":1102,"title":1103},"\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":1105,"title":1106},"\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":1108,"title":1109},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1111,"title":1112},"\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":1114,"title":1115},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1117,"title":1118},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1120,"title":1121},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1123,"title":1124},"\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":1126,"title":1127},"\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":1129,"title":1130},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1132,"title":1133},"\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":1135,"title":1136},"\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":1138,"title":1139},"\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":1141,"title":1142},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1144,"title":1145},"\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":1147,"title":1148},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1150,"title":1151},"\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":1153,"title":1154},"\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":1156,"title":1157},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1159,"title":1160},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1162,"title":1163},"\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":1165,"title":1166},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1168,"title":1169},"\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":1171,"title":1172},"\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":1174,"title":1175},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1177,"title":1178},"\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":1180,"title":1181},"\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":1183,"title":1184},"\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":1186,"title":1187},"\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":1189,"title":1190},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1192,"title":1193},"\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":1195,"title":1196},"\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":1198,"title":1199},"\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":1201,"title":1202},"\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":1204,"title":1205},"\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":1207,"title":1208},"\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":1210,"title":1211},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1213,"title":1214},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1216,"title":1217},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1219,"title":1220},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1222,"title":1223},"\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":1225,"title":1226},"\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":1228,"title":1229},"\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":1231,"title":1232},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1234,"title":1235},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1237,"title":1238},"\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":1240,"title":1241},"\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":1243,"title":1244},"\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":1246,"title":1247},"\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":1249,"title":1250},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1252,"title":1253},"\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":1255,"title":1256},"\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":1258,"title":1259},"\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":1261,"title":1262},"\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":1264,"title":1265},"\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":1267,"title":1026},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-cookie-banners",{"path":1269,"title":1270},"\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":1272,"title":1273},"\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":1275,"title":1276},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1278,"title":1279},"\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":1281,"title":1282},"\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":1284,"title":1285},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1287,"title":1288},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1290,"title":1291},"\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":1293,"title":1294},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1296,"title":1297},"\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":1299,"title":1300},"\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":1302,"title":1303},"\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":1305,"title":1306},"\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":1308,"title":1309},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1311,"title":1312},"\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":1314,"title":1315},"\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":1317,"title":1318},"\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":1320,"title":1321},"\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":1323,"title":1324},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1326,"title":1327},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1329,"title":1330},"\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":1332,"title":1333},"\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":1335,"title":1336},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1338,"title":1339},"\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":1341,"title":1342},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1344,"title":1345},"\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":1347,"title":1348},"\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":1350,"title":1351},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1353,"title":1354},"\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":1356,"title":1357},"\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":1359,"title":1360},"\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":1362,"title":1363},"\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":1365,"title":1366},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1368,"title":1369},"\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":1371,"title":1372},"\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":1374,"title":1375},"\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":1377,"title":1378},"\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":1380,"title":1381},"\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":1383,"title":1384},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1386,"title":1387},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1389,"title":1390},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1392,"title":1393},"\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":1395,"title":1396},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1398,"title":1399},"\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":1401,"title":1402},"\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":1404,"title":1405},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1407,"title":1408},"\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":1410,"title":1411},"\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":1413,"title":1414},"\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":1416,"title":1417},"\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":1419,"title":1420},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1422,"title":1423},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1425,"title":1426},"\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":1428,"title":1429},"\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":1431,"title":1432},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1434,"title":1435},"\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":1437,"title":1438},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1440,"title":1441},"\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":1443,"title":1444},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1446,"title":1447},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1449,"title":1450},"\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":1452,"title":1453},"\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":1455,"title":1456},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1458,"title":1459},"\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":1461,"title":1462},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1464,"title":1465},"\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":1467,"title":1468},"\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":1470,"title":1471},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1473,"title":1474},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1476,"title":1477},"\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":1479,"title":1480},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1482,"title":1483},"\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":1485,"title":1486},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1488,"title":1489},"\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":1491,"title":1492},"\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":1494,"title":1495},"\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":1497,"title":1498},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1500,"title":1501},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1503,"title":1504},"\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":1506,"title":1507},"\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":1509,"title":1510},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1512,"title":1513},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1515,"title":1516},"\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":1518,"title":1519},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1521,"title":1522},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1524,"title":1525},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1527,"title":1528},"\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":1530,"title":1531},"\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":1533,"title":1534},"\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":1536,"title":1537},"\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":1539,"title":1540},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1542,"title":1543},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":1545,"title":1546},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1548,"title":1549},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1551,"title":1552},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1554,"title":1555},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1557,"title":620},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites",{"path":1077,"title":5},{"path":1560,"title":24},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites",{"path":1562,"title":41},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frolling-back-a-bad-static-deploy-in-under-a-minute",{"path":1564,"title":1019},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frunning-smoke-tests-against-a-preview-url",{"path":1566,"title":1567},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1569,"title":1570},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1572,"title":1573},"\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":1575,"title":1576},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1578,"title":1579},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1581,"title":1582},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1584,"title":1585},"\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":1587,"title":1588},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1590,"title":1591},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1593,"title":1594},"\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":1596,"title":1597},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1599,"title":1600},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1602,"title":1603},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1605,"title":1606},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1608,"title":1609},"\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":1611,"title":1612},"\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":1614,"title":1615},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1617,"title":1033},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers",{"path":1619,"title":1620},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1622,"title":1623},"\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",1789722848253]