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