[{"data":1,"prerenderedAt":2707},["ShallowReactive",2],{"page:\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites":3,"all-docs-nav":1570,"filed:\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites":2706},{"id":4,"title":5,"body":6,"breadcrumb":1547,"dateModified":1554,"datePublished":1554,"description":1555,"extension":1556,"faq":1557,"meta":1563,"navigation":1564,"path":1565,"seo":1566,"slug":12,"stem":1567,"type":1568,"__hash__":1569},"content\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Findex.md","Accessibility for Static Sites",{"type":7,"value":8,"toc":1526},"minimark",[9,13,22,36,39,44,47,116,268,272,275,394,397,401,428,441,573,645,649,655,661,821,825,832,842,912,916,922,940,1063,1067,1074,1099,1103,1106,1129,1223,1226,1230,1233,1332,1335,1339,1388,1392,1418,1422,1427,1430,1434,1437,1441,1444,1448,1451,1455,1458,1462,1522],[10,11,5],"h1",{"id":12},"accessibility-for-static-sites",[14,15,16,17,21],"p",{},"A static site gets a head start on accessibility. Its content is in the HTML the server returns, so a screen reader can read it before any JavaScript runs; there is no client-side router losing focus between pages and no skeleton screen announcing nothing. That head start is easy to waste. A theme ships with a skip link that points at an ID nobody renders. A Markdown author writes ",[18,19,20],"code",{},"#### Options"," straight after an H2 because the smaller font looked right. A code block scrolls horizontally but cannot be reached with the keyboard. A dark theme is added, the brand blue drops to 3.1:1 against the new background, and nobody checks.",[14,23,24,25,30,31,35],{},"This topic covers accessibility for sites built with Astro, Eleventy, Hugo, Jekyll, Docusaurus, Starlight and VitePress: what the generators give you, where the templates and the content let readers down, and how to keep it from regressing once it is fixed. It is written for the people who own those layers — frontend developers who maintain the theme, technical writers who produce the Markdown, and whoever owns the CI pipeline. It sits in ",[26,27,29],"a",{"href":28},"\u002Fchoosing-the-right-static-site-generator-for-production\u002F","Choosing the Right Static Site Generator for Production"," because accessibility defaults are a real selection criterion, compared in ",[26,32,34],{"href":33},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults\u002F","Evaluating SSG Accessibility Defaults",", and because most of the fixes belong in the theme you choose or build.",[14,37,38],{},"The numbers in this topic come from one reference site, audited and fixed over six weeks: a 1,140-page product documentation site built with Astro and Starlight, with a custom marketing section in plain Astro, about 2,600 code blocks and 410 diagrams. Audits used axe-core 4.10 through Playwright, Lighthouse 12, and manual passes with NVDA 2025.3 on Firefox, VoiceOver on Safari and keyboard-only navigation.",[40,41,43],"h2",{"id":42},"what-you-will-learn","What You Will Learn",[14,45,46],{},"The guides in this topic split along the layers where accessibility problems come from:",[48,49,50,68,81,103],"ul",{},[51,52,53,57,58,62,63,67],"li",{},[54,55,56],"strong",{},"Layout and navigation:"," ",[26,59,61],{"href":60},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fskip-links-and-landmarks-in-ssg-layouts\u002F","Skip Links and Landmarks in SSG Layouts"," and ",[26,64,66],{"href":65},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fkeyboard-navigation-and-focus-order-on-static-sites\u002F","Keyboard Navigation and Focus Order on Static Sites",".",[51,69,70,57,73,62,77,67],{},[54,71,72],{},"Visual design:",[26,74,76],{"href":75},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-low-color-contrast-flagged-by-lighthouse\u002F","Fixing Low Color Contrast Flagged by Lighthouse",[26,78,80],{"href":79},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-dark-mode-toggles-for-static-sites\u002F","Accessible Dark Mode Toggles for Static Sites",[51,82,83,57,86,90,91,90,95,62,99,67],{},[54,84,85],{},"Content:",[26,87,89],{"href":88},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content\u002F","Fixing Heading Order Problems in Markdown Content",", ",[26,92,94],{"href":93},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fenforcing-alt-text-for-markdown-images-at-build-time\u002F","Enforcing Alt Text for Markdown Images at Build Time",[26,96,98],{"href":97},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-code-blocks-in-documentation-sites\u002F","Accessible Code Blocks in Documentation Sites",[26,100,102],{"href":101},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-svg-diagrams-on-static-sites\u002F","Accessible SVG Diagrams on Static Sites",[51,104,105,57,108,62,112,67],{},[54,106,107],{},"Interactive widgets and testing:",[26,109,111],{"href":110},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Faccessible-search-ui-for-static-sites\u002F","Accessible Search UI for Static Sites",[26,113,115],{"href":114},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Faccessibility-testing-with-axe-and-pa11y-in-ci\u002F","Accessibility Testing with axe and pa11y in CI",[117,118,119,264],"figure",{},[120,121,128,129,128,133,128,137,128,144,128,249],"svg",{"viewBox":122,"role":123,"ariaLabelledBy":124,"xmlns":127},"0 0 760 383","img",[125,126],"a11y-layers-title","a11y-layers-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[130,131,132],"title",{"id":125},"The four layers of a static site that accessibility problems come from",[134,135,136],"desc",{"id":126},"Four stacked layers. The theme layout supplies landmarks, skip links, focus styles and the colour palette. Markdown content supplies headings, alt text, link text and tables. Build output adds code highlighting, diagrams and generated IDs. Client-side widgets add search, theme toggles, tabs and dialogs. On the reference site the issues split 31, 44, 15 and 10 percent across the four.",[138,139],"rect",{"x":140,"y":140,"width":141,"height":142,"fill":143},"0","760","383","#ffffff",[145,146,148,149,148,159,148,166,148,170,148,173,148,179,148,182,148,188,148,196,148,202,148,207,148,213,148,217,148,221,148,225,148,229,148,233,148,237,148,241,148,245,128],"g",{"style":147},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[138,150],{"x":151,"y":152,"width":153,"height":154,"rx":155,"fill":156,"opacity":157,"stroke":156,"style":158},"40.0","60.0","440.0","57.2","8","#6a4c93","0.14","stroke-width:1.5px",[160,161],"path",{"d":162,"fill":163,"stroke":164,"style":165},"M260.0 119.2 L260.0 139.2","none","#556071","stroke-width:2px;marker-end:url(#a11y-layers-arrow)",[138,167],{"x":151,"y":168,"width":153,"height":154,"rx":155,"fill":169,"opacity":157,"stroke":169,"style":158},"143.2","#1982c4",[160,171],{"d":172,"fill":163,"stroke":164,"style":165},"M260.0 202.4 L260.0 222.4",[138,174],{"x":151,"y":175,"width":153,"height":154,"rx":155,"fill":176,"opacity":177,"stroke":178,"style":158},"226.4","#ffca3a","0.24","#a97b00",[160,180],{"d":181,"fill":163,"stroke":164,"style":165},"M260.0 285.6 L260.0 305.6",[138,183],{"x":151,"y":184,"width":153,"height":154,"rx":155,"fill":185,"opacity":186,"stroke":187,"style":158},"309.6","#ff595e","0.12","#d83b41",[189,190,195],"text",{"x":191,"y":192,"fill":193,"style":194},"380.0","30.0","#1f2937","font-size:16px;text-anchor:middle;font-weight:700","Where accessibility problems come from on a static site",[189,197,201],{"x":198,"y":199,"fill":193,"style":200},"260.0","86.4","font-size:13px;text-anchor:middle;font-weight:700","Theme layout",[189,203,206],{"x":198,"y":204,"fill":164,"style":205},"103.3","font-size:11px;text-anchor:middle","landmarks, skip link, focus, palette",[189,208,212],{"x":209,"y":210,"fill":164,"style":211},"504.0","92.6","font-size:11.5px;text-anchor:start","31% of issues found",[189,214,216],{"x":198,"y":215,"fill":193,"style":200},"169.5","Markdown content",[189,218,220],{"x":198,"y":219,"fill":164,"style":205},"186.4","headings, alt text, link text, tables",[189,222,224],{"x":209,"y":223,"fill":164,"style":211},"175.8","44% of issues found",[189,226,228],{"x":198,"y":227,"fill":193,"style":200},"252.7","Build output",[189,230,232],{"x":198,"y":231,"fill":164,"style":205},"269.6","code highlighting, diagrams, IDs",[189,234,236],{"x":209,"y":235,"fill":164,"style":211},"259.0","15% of issues found",[189,238,240],{"x":198,"y":239,"fill":193,"style":200},"335.9","Client-side widgets",[189,242,244],{"x":198,"y":243,"fill":164,"style":205},"352.8","search, theme toggle, tabs, dialogs",[189,246,248],{"x":209,"y":247,"fill":164,"style":211},"342.2","10% of issues found",[250,251,148,252,128],"defs",{},[253,254,260,261,148],"marker",{"id":255,"viewBox":256,"refX":155,"refY":257,"markerWidth":258,"markerHeight":258,"orient":259},"a11y-layers-arrow","0 0 10 10","5","7","auto-start-reverse","\n      ",[160,262],{"d":263,"fill":164},"M0 0 L10 5 L0 10 z",[265,266,267],"figcaption",{},"Content produced the largest share of issues, and it is the layer most often left out of automated checks.",[40,269,271],{"id":270},"what-the-generators-give-you","What the Generators Give You",[14,273,274],{},"No generator makes a site accessible, but some ship far better starting points than others. The differences show up in the default theme rather than the generator core: Hugo and Eleventy have no default theme at all, so whatever you build is what you get, while the documentation frameworks ship complete layouts with navigation, search and theme switching.",[276,277,278,303],"table",{},[279,280,281],"thead",{},[282,283,284,288,291,294,297,300],"tr",{},[285,286,287],"th",{},"Default theme",[285,289,290],{},"Skip link",[285,292,293],{},"Landmarks",[285,295,296],{},"Visible focus",[285,298,299],{},"Theme toggle labelled",[285,301,302],{},"axe violations, 20 sample pages",[304,305,306,324,340,356,376],"tbody",{},[282,307,308,312,315,318,320,322],{},[309,310,311],"td",{},"Starlight 0.30",[309,313,314],{},"Yes",[309,316,317],{},"Complete",[309,319,314],{},[309,321,314],{},[309,323,140],{},[282,325,326,329,331,333,335,337],{},[309,327,328],{},"VitePress 1.5",[309,330,314],{},[309,332,317],{},[309,334,314],{},[309,336,314],{},[309,338,339],{},"2 (contrast on badges)",[282,341,342,345,347,349,351,353],{},[309,343,344],{},"Docusaurus 3.6",[309,346,314],{},[309,348,317],{},[309,350,314],{},[309,352,314],{},[309,354,355],{},"3 (contrast, nested interactive)",[282,357,358,361,364,367,370,373],{},[309,359,360],{},"Jekyll Minima 2.5",[309,362,363],{},"No",[309,365,366],{},"Partial",[309,368,369],{},"Browser default",[309,371,372],{},"No toggle",[309,374,375],{},"6",[282,377,378,381,383,385,388,391],{},[309,379,380],{},"Hugo PaperMod 7",[309,382,363],{},[309,384,366],{},[309,386,387],{},"Removed on links",[309,389,390],{},"Unlabelled icon",[309,392,393],{},"11",[14,395,396],{},"Each theme was installed fresh with its sample content and scanned with axe-core on 20 pages. The counts are violations by rule, not by element. The point is not that one theme wins; it is that the starting point varies from zero issues to eleven, and a team that picks a theme without checking inherits whatever it ships. Customisation is where the documentation frameworks regress: on the reference site, Starlight's defaults were clean, and every one of the 31 layout issues came from custom components added on top.",[40,398,400],{"id":399},"layout-landmarks-skip-links-and-focus","Layout: Landmarks, Skip Links and Focus",[14,402,403,404,90,407,90,410,90,413,62,416,419,420,423,424,427],{},"Screen reader users navigate by landmarks and headings far more than by tabbing through links. A layout with ",[18,405,406],{},"\u003Cheader>",[18,408,409],{},"\u003Cnav aria-label=\"Main\">",[18,411,412],{},"\u003Cmain>",[18,414,415],{},"\u003Caside>",[18,417,418],{},"\u003Cfooter>"," gives them a map of the page; a layout made of ",[18,421,422],{},"\u003Cdiv class=\"wrapper\">"," gives them nothing. A skip link — the first focusable element, pointing at ",[18,425,426],{},"\u003Cmain id=\"content\">"," — lets keyboard users jump past a documentation sidebar that can hold two hundred links. The reference site's sidebar held 187 links on its largest section; without a working skip link, reaching the article took 190 presses of Tab.",[14,429,430,431,434,435,437,438,440],{},"Focus visibility is the other half. Themes routinely remove the focus outline because a designer disliked it on mouse click. ",[18,432,433],{},":focus-visible"," solves the original complaint, showing the ring for keyboard focus and not for clicks, so there is no reason left to remove it. ",[26,436,66],{"href":65}," covers focus styles, tab order and the widgets that break it, and ",[26,439,61],{"href":60}," shows the layout markup for each generator.",[442,443,448],"pre",{"className":444,"code":445,"language":446,"meta":447,"style":447},"language-css shiki shiki-themes github-light github-dark",":where(a, button, input, select, textarea, summary, [tabindex]):focus-visible {\n  outline: 3px solid var(--focus-ring);\n  outline-offset: 2px;\n  border-radius: 2px;\n}\n","css","",[18,449,450,505,537,553,567],{"__ignoreMap":447},[451,452,455,459,463,466,468,471,473,476,478,481,483,486,488,491,494,497,500,502],"span",{"class":453,"line":454},"line",1,[451,456,458],{"class":457},"sScJk",":where",[451,460,462],{"class":461},"sVt8B","(",[451,464,26],{"class":465},"s9eBZ",[451,467,90],{"class":461},[451,469,470],{"class":465},"button",[451,472,90],{"class":461},[451,474,475],{"class":465},"input",[451,477,90],{"class":461},[451,479,480],{"class":465},"select",[451,482,90],{"class":461},[451,484,485],{"class":465},"textarea",[451,487,90],{"class":461},[451,489,490],{"class":465},"summary",[451,492,493],{"class":461},", [",[451,495,496],{"class":457},"tabindex",[451,498,499],{"class":461},"])",[451,501,433],{"class":457},[451,503,504],{"class":461}," {\n",[451,506,508,512,515,518,522,525,528,530,534],{"class":453,"line":507},2,[451,509,511],{"class":510},"sj4cs","  outline",[451,513,514],{"class":461},": ",[451,516,517],{"class":510},"3",[451,519,521],{"class":520},"szBVR","px",[451,523,524],{"class":510}," solid",[451,526,527],{"class":510}," var",[451,529,462],{"class":461},[451,531,533],{"class":532},"s4XuR","--focus-ring",[451,535,536],{"class":461},");\n",[451,538,540,543,545,548,550],{"class":453,"line":539},3,[451,541,542],{"class":510},"  outline-offset",[451,544,514],{"class":461},[451,546,547],{"class":510},"2",[451,549,521],{"class":520},[451,551,552],{"class":461},";\n",[451,554,556,559,561,563,565],{"class":453,"line":555},4,[451,557,558],{"class":510},"  border-radius",[451,560,514],{"class":461},[451,562,547],{"class":510},[451,564,521],{"class":520},[451,566,552],{"class":461},[451,568,570],{"class":453,"line":569},5,[451,571,572],{"class":461},"}\n",[117,574,575,642],{},[120,576,128,581,128,584,128,587,128,590],{"viewBox":577,"role":123,"ariaLabelledBy":578,"xmlns":127},"0 0 760 295",[579,580],"a11y-tabs-title","a11y-tabs-desc",[130,582,583],{"id":579},"Tab presses needed to reach the main content on the largest docs section",[134,585,586],{"id":580},"Vertical bars. Before fixes it took 190 Tab presses to reach the first link in the article, because the sidebar held 187 links. With a working skip link it took 2 presses. Using the main landmark shortcut in NVDA it took 1 key press.",[138,588],{"x":140,"y":140,"width":141,"height":589,"fill":143},"295",[145,591,148,592,148,600,148,608,148,611,148,614,148,617,148,624,148,629,148,633,148,635,148,639,128],{"style":147},[138,593],{"x":594,"y":595,"width":596,"height":597,"rx":517,"fill":185,"opacity":598,"stroke":187,"style":599},"108.3","76.0","90.0","170.0","0.3","stroke-width:1px",[138,601],{"x":602,"y":603,"width":596,"height":604,"rx":517,"fill":605,"opacity":606,"stroke":607,"style":599},"335.0","243.0","3.0","#8ac926","0.4","#5a8a16",[138,609],{"x":610,"y":603,"width":596,"height":604,"rx":517,"fill":605,"opacity":606,"stroke":607,"style":599},"561.7",[160,612],{"d":613,"fill":163,"stroke":164,"style":158},"M30.0 246.0 L730.0 246.0",[189,615,616],{"x":191,"y":192,"fill":193,"style":194},"Key presses to reach the article from the top of the page",[189,618,623],{"x":619,"y":620,"fill":621,"style":622},"153.3","69.0","#b32b30","font-size:12px;text-anchor:middle;font-weight:700","190",[189,625,628],{"x":619,"y":626,"fill":164,"style":627},"264.0","font-size:11.5px;text-anchor:middle","No skip link",[189,630,547],{"x":191,"y":631,"fill":632,"style":622},"236.0","#3f6410",[189,634,290],{"x":191,"y":626,"fill":164,"style":627},[189,636,638],{"x":637,"y":631,"fill":632,"style":622},"606.7","1",[189,640,641],{"x":637,"y":626,"fill":164,"style":627},"Landmark shortcut",[265,643,644],{},"Measured on the reference site's API section, keyboard only, Firefox with NVDA running.",[40,646,648],{"id":647},"visual-design-contrast-and-themes","Visual Design: Contrast and Themes",[14,650,651,652,654],{},"Contrast failures were the single most common automated finding on the reference site: 212 elements across 1,140 pages, almost all from five design tokens. Muted grey text for dates and captions sat at 3.9:1, inline code used a pale pink at 3.4:1, and the dark theme's link blue dropped to 3.6:1 against the near-black background. Because a static site's colours come from a handful of CSS custom properties, contrast is fixed at the token level, not per page: change five values, rebuild, and all 212 failures go at once. ",[26,653,76],{"href":75}," walks through finding the tokens behind a failure and choosing replacements that keep the brand.",[14,656,657,658,660],{},"A dark theme doubles the surface to check. Every token has to pass in both themes, and the toggle that switches between them has its own requirements: a real button with an accessible name, a state that assistive technology can read, and no flash of the wrong theme on load. ",[26,659,80],{"href":79}," builds one in under 1 KB.",[117,662,663,818],{},[120,664,128,669,128,672,128,675,128,678],{"viewBox":665,"role":123,"ariaLabelledBy":666,"xmlns":127},"0 0 760 352",[667,668],"a11y-contrast-title","a11y-contrast-desc",[130,670,671],{"id":667},"Contrast ratio per design token before and after the fix",[134,673,674],{"id":668},"Paired bars. Muted text went from 3.9 to 5.1 to 1. Inline code from 3.4 to 5.6. Dark theme links from 3.6 to 6.2. Badge text from 2.8 to 4.8. Placeholder text from 2.6 to 4.6. The AA threshold for normal text is 4.5 to 1.",[138,676],{"x":140,"y":140,"width":141,"height":677,"fill":143},"352",[145,679,148,680,148,686,148,689,148,695,148,699,148,703,148,707,148,711,148,715,148,719,148,723,148,727,148,731,148,734,148,737,148,742,148,746,148,751,148,757,148,762,148,766,148,771,148,776,148,780,148,785,148,790,148,794,148,799,148,804,148,808,148,813,128],{"style":147},[138,681],{"x":682,"y":683,"width":684,"height":685,"rx":547,"fill":185,"opacity":598,"stroke":187,"style":599},"306.8","50.0","14.0","12.0",[138,687],{"x":688,"y":683,"width":684,"height":685,"rx":547,"fill":605,"opacity":606,"stroke":607,"style":599},"398.4",[138,690],{"x":691,"y":692,"width":693,"height":694,"rx":517,"fill":185,"opacity":598,"stroke":187,"style":599},"230.0","82.0","292.2","16.0",[138,696],{"x":691,"y":697,"width":698,"height":694,"rx":517,"fill":605,"opacity":606,"stroke":607,"style":599},"102.0","382.1",[138,700],{"x":691,"y":701,"width":702,"height":694,"rx":517,"fill":185,"opacity":598,"stroke":187,"style":599},"134.0","254.8",[138,704],{"x":691,"y":705,"width":706,"height":694,"rx":517,"fill":605,"opacity":606,"stroke":607,"style":599},"154.0","419.6",[138,708],{"x":691,"y":709,"width":710,"height":694,"rx":517,"fill":185,"opacity":598,"stroke":187,"style":599},"186.0","269.7",[138,712],{"x":691,"y":713,"width":714,"height":694,"rx":517,"fill":605,"opacity":606,"stroke":607,"style":599},"206.0","464.5",[138,716],{"x":691,"y":717,"width":718,"height":694,"rx":517,"fill":185,"opacity":598,"stroke":187,"style":599},"238.0","209.8",[138,720],{"x":691,"y":721,"width":722,"height":694,"rx":517,"fill":605,"opacity":606,"stroke":607,"style":599},"258.0","359.7",[138,724],{"x":691,"y":725,"width":726,"height":694,"rx":517,"fill":185,"opacity":598,"stroke":187,"style":599},"290.0","194.8",[138,728],{"x":691,"y":729,"width":730,"height":694,"rx":517,"fill":605,"opacity":606,"stroke":607,"style":599},"310.0","344.7",[160,732],{"d":733,"fill":163,"stroke":164,"style":158},"M230.0 78.0 L230.0 332.0",[189,735,736],{"x":191,"y":192,"fill":193,"style":194},"Contrast ratios of the five failing tokens, before and after",[189,738,741],{"x":739,"y":152,"fill":164,"style":740},"326.8","font-size:12px;text-anchor:start","Before",[189,743,745],{"x":744,"y":152,"fill":164,"style":740},"418.4","After",[189,747,750],{"x":748,"y":749,"fill":193,"style":740},"20.0","105.2","Muted text (light)",[189,752,756],{"x":753,"y":754,"fill":621,"style":755},"529.2","94.5","font-size:11.5px;text-anchor:start;font-weight:700","3.9:1",[189,758,761],{"x":759,"y":760,"fill":632,"style":755},"619.1","114.5","5.1:1",[189,763,765],{"x":748,"y":764,"fill":193,"style":740},"157.2","Inline code (light)",[189,767,770],{"x":768,"y":769,"fill":621,"style":755},"491.8","146.5","3.4:1",[189,772,775],{"x":773,"y":774,"fill":632,"style":755},"656.6","166.5","5.6:1",[189,777,779],{"x":748,"y":778,"fill":193,"style":740},"209.2","Links (dark)",[189,781,784],{"x":782,"y":783,"fill":621,"style":755},"506.7","198.5","3.6:1",[189,786,789],{"x":787,"y":788,"fill":632,"style":755},"701.5","218.5","6.2:1",[189,791,793],{"x":748,"y":792,"fill":193,"style":740},"261.2","Badge text",[189,795,798],{"x":796,"y":797,"fill":621,"style":755},"446.8","250.5","2.8:1",[189,800,803],{"x":801,"y":802,"fill":632,"style":755},"596.7","270.5","4.8:1",[189,805,807],{"x":748,"y":806,"fill":193,"style":740},"313.2","Input placeholder",[189,809,812],{"x":810,"y":811,"fill":621,"style":755},"431.8","302.5","2.6:1",[189,814,817],{"x":815,"y":816,"fill":632,"style":755},"581.7","322.5","4.6:1",[265,819,820],{},"Ratios computed with the WCAG 2 formula against each token's background; every replacement stays within the brand hue.",[40,822,824],{"id":823},"content-headings-alt-text-and-links","Content: Headings, Alt Text and Links",[14,826,827,828,831],{},"Content produced 44% of the issues on the reference site, and it is the layer most sites never check. Writers choose heading levels by size, not structure; they paste screenshots with ",[18,829,830],{},"![](image.png)"," or with alt text that repeats the file name; they write \"click here\" and \"this page\". None of these are template bugs, so fixing the theme does not fix them, and an axe run only catches the mechanical ones — a missing alt attribute, not an alt text of \"screenshot\".",[14,833,834,835,62,838,841],{},"The fix is to treat content like code: lint it before the build. Markdown is easy to parse, and a remark or markdown-it plugin can fail the build on an image with no alt text, a heading that skips a level, or a link whose text is on a list of meaningless phrases. On the reference site, a lint step added to CI found 486 issues in the existing content on its first run and has blocked 37 since, all in pull requests from writers who had not seen the rule before. The guides on ",[26,836,837],{"href":88},"heading order",[26,839,840],{"href":93},"alt text"," contain both plugins.",[276,843,844,857],{},[279,845,846],{},[282,847,848,851,854],{},[285,849,850],{},"Content issue",[285,852,853],{},"Found on first lint",[285,855,856],{},"Caught by axe?",[304,858,859,870,880,891,902],{},[282,860,861,864,867],{},[309,862,863],{},"Image with empty or missing alt",[309,865,866],{},"141",[309,868,869],{},"Missing only",[282,871,872,875,878],{},[309,873,874],{},"Alt text is a file name or \"image\"",[309,876,877],{},"96",[309,879,363],{},[282,881,882,885,888],{},[309,883,884],{},"Skipped heading level",[309,886,887],{},"173",[309,889,890],{},"Partly (heading-order is a best-practice rule)",[282,892,893,896,899],{},[309,894,895],{},"More than one H1",[309,897,898],{},"22",[309,900,901],{},"Partly",[282,903,904,907,910],{},[309,905,906],{},"Vague link text (\"here\", \"this\")",[309,908,909],{},"54",[309,911,363],{},[40,913,915],{"id":914},"build-output-code-blocks-and-diagrams","Build Output: Code Blocks and Diagrams",[14,917,918,919,921],{},"Documentation sites are dense with two kinds of content that assistive technology handles badly by default. Code blocks scroll horizontally, so a keyboard user must be able to focus them; they are coloured by a syntax theme whose token colours are often below 4.5:1; and their copy button is frequently an unlabelled icon. On the reference site, 2,600 code blocks produced three distinct issues, each fixed once in the highlighter configuration. ",[26,920,98],{"href":97}," covers Shiki, Prism and Chroma.",[14,923,924,925,928,929,932,933,936,937,939],{},"Diagrams are the harder case, because the information is in the picture. An inline SVG needs ",[18,926,927],{},"role=\"img\"",", a ",[18,930,931],{},"\u003Ctitle>"," and a ",[18,934,935],{},"\u003Cdesc>"," that says what the diagram shows rather than what it looks like; a complex diagram needs a text alternative nearby, such as a table of the same data. ",[26,938,102],{"href":101}," covers writing those descriptions and checking them in the build.",[117,941,942,1060],{},[120,943,128,948,128,951,128,954,128,957],{"viewBox":944,"role":123,"ariaLabelledBy":945,"xmlns":127},"0 0 760 184",[946,947],"a11y-build-title","a11y-build-desc",[130,949,950],{"id":946},"Accessibility requirements for generated code blocks and diagrams",[134,952,953],{"id":947},"A matrix of two generated content types against four requirements. Code blocks need keyboard focus for horizontal scrolling, token colours at 4.5 to 1, a labelled copy button, and a language label. Inline SVG diagrams need role img with a title, a desc stating what it shows, contrast for labels in both themes, and a nearby text alternative for complex data.",[138,955],{"x":140,"y":140,"width":141,"height":956,"fill":143},"184",[145,958,148,959,148,962,148,968,148,971,148,974,148,977,148,981,148,985,148,987,148,989,148,991,148,994,148,997,148,1002,148,1006,148,1010,148,1014,148,1018,148,1022,148,1026,148,1029,148,1032,148,1035,148,1039,148,1043,148,1047,148,1051,148,1054,148,1057,128],{"style":147},[160,960],{"d":961,"fill":163,"stroke":164,"style":158},"M20.0 86.0 L740.0 86.0",[138,963],{"x":964,"y":596,"width":965,"height":966,"rx":257,"fill":605,"opacity":967,"stroke":607,"style":599},"214.0","124.5","25.6","0.2",[138,969],{"x":970,"y":596,"width":965,"height":966,"rx":257,"fill":176,"opacity":177,"stroke":178,"style":599},"346.5",[138,972],{"x":973,"y":596,"width":965,"height":966,"rx":257,"fill":605,"opacity":967,"stroke":607,"style":599},"479.0",[138,975],{"x":976,"y":596,"width":965,"height":966,"rx":257,"fill":169,"opacity":157,"stroke":169,"style":599},"611.5",[160,978],{"d":979,"fill":163,"stroke":980,"style":599},"M20.0 119.6 L740.0 119.6","#d9e2ef",[138,982],{"x":964,"y":983,"width":965,"height":984,"rx":257,"fill":169,"opacity":157,"stroke":169,"style":599},"123.6","39.9",[138,986],{"x":970,"y":983,"width":965,"height":984,"rx":257,"fill":176,"opacity":177,"stroke":178,"style":599},[138,988],{"x":973,"y":983,"width":965,"height":984,"rx":257,"fill":605,"opacity":967,"stroke":607,"style":599},[138,990],{"x":976,"y":983,"width":965,"height":984,"rx":257,"fill":605,"opacity":967,"stroke":607,"style":599},[160,992],{"d":993,"fill":163,"stroke":980,"style":599},"M20.0 167.5 L740.0 167.5",[189,995,996],{"x":191,"y":192,"fill":193,"style":194},"Generated content and what it needs",[189,998,1001],{"x":192,"y":999,"fill":193,"style":1000},"75.2","font-size:12px;text-anchor:start;font-weight:700","Content",[189,1003,1005],{"x":1004,"y":999,"fill":193,"style":622},"276.2","Reach",[189,1007,1009],{"x":1008,"y":999,"fill":193,"style":622},"408.8","Contrast",[189,1011,1013],{"x":1012,"y":999,"fill":193,"style":622},"541.2","Name",[189,1015,1017],{"x":1016,"y":999,"fill":193,"style":622},"673.8","Alternative",[189,1019,1021],{"x":192,"y":1020,"fill":193,"style":1000},"106.4","Code blocks",[189,1023,1025],{"x":1004,"y":1024,"fill":193,"style":627},"106.2","tabindex on scroll",[189,1027,1028],{"x":1008,"y":1024,"fill":193,"style":627},"token colours 4.5:1",[189,1030,1031],{"x":1012,"y":1024,"fill":193,"style":627},"labelled copy button",[189,1033,1034],{"x":1016,"y":1024,"fill":193,"style":627},"language label",[189,1036,1038],{"x":192,"y":1037,"fill":193,"style":1000},"147.2","SVG diagrams",[189,1040,1042],{"x":1004,"y":1041,"fill":193,"style":627},"147.0","role img",[189,1044,1046],{"x":1008,"y":1045,"fill":193,"style":627},"139.5","labels in both",[189,1048,1050],{"x":1008,"y":1049,"fill":193,"style":627},"154.5","themes",[189,1052,1053],{"x":1012,"y":1041,"fill":193,"style":627},"title and desc",[189,1055,1056],{"x":1016,"y":1045,"fill":193,"style":627},"table for complex",[189,1058,1059],{"x":1016,"y":1049,"fill":193,"style":627},"data",[265,1061,1062],{},"Both are fixed once in the build configuration, not page by page.",[40,1064,1066],{"id":1065},"interactive-widgets","Interactive Widgets",[14,1068,1069,1070,1073],{},"Static sites have few interactive widgets, but the ones they have are the most visible: search, theme toggles, tabs for package managers, disclosure menus on mobile, and copy buttons. Each one is a small application with keyboard and screen reader behaviour to get right. The reference site's ten widget issues included a search dialog that did not return focus on close, tabs built from ",[18,1071,1072],{},"\u003Cdiv>"," elements that could not be reached with the keyboard, and a mobile menu button that did not expose whether it was open.",[14,1075,1076,1077,62,1080,1083,1084,1087,1088,1091,1092,1095,1096,1098],{},"The rule that kept these under control was to use the native element whenever one exists. A ",[18,1078,1079],{},"\u003Cdetails>",[18,1081,1082],{},"\u003Csummary>"," pair is a disclosure widget with correct semantics and keyboard behaviour for free. A ",[18,1085,1086],{},"\u003Cdialog>"," opened with ",[18,1089,1090],{},"showModal()"," traps focus and closes on Escape without a library. A ",[18,1093,1094],{},"\u003Cbutton aria-pressed>"," is a toggle. Each replacement removed script as well as issues: the three custom widgets that became native elements shed 6.8 KB of JavaScript between them. ",[26,1097,111],{"href":110}," applies the same approach to the most complex widget on most documentation sites.",[40,1100,1102],{"id":1101},"testing-and-keeping-it-fixed","Testing and Keeping It Fixed",[14,1104,1105],{},"Accessibility regresses quietly. A new component, a new colour, a page written by someone new — none of them break the build unless something checks. The reference site runs three layers of checks:",[1107,1108,1109,1115,1123],"ol",{},[51,1110,1111,1114],{},[54,1112,1113],{},"Content lint"," on every pull request that touches Markdown: alt text, heading order and link text. It runs in about 4 seconds.",[51,1116,1117,1120,1121,67],{},[54,1118,1119],{},"axe-core against the built site"," on every pull request, scanning a sample of 60 pages chosen to cover every layout plus the pages that changed. It runs in about 70 seconds with Playwright, as in ",[26,1122,115],{"href":114},[51,1124,1125,1128],{},[54,1126,1127],{},"A manual pass"," when a layout or interactive component changes: keyboard only, then NVDA and VoiceOver, following a ten-minute script.",[117,1130,1131,1220],{},[120,1132,128,1137,128,1140,128,1143,128,1146,128,1213],{"viewBox":1133,"role":123,"ariaLabelledBy":1134,"xmlns":127},"0 0 760 152",[1135,1136],"a11y-ci-title","a11y-ci-desc",[130,1138,1139],{"id":1135},"Where each accessibility check runs and what it catches",[134,1141,1142],{"id":1136},"Four steps in order. Content lint on Markdown in about 4 seconds catches alt text, headings and link text. The build produces HTML. axe-core on 60 sampled pages in about 70 seconds catches contrast, names, IDs and landmarks. A manual pass with keyboard and screen readers, run on template changes, catches focus order, announcements and the quality of descriptions.",[138,1144],{"x":140,"y":140,"width":141,"height":1145,"fill":143},"152",[145,1147,148,1148,148,1152,148,1156,148,1160,148,1163,148,1166,148,1169,148,1172,148,1175,148,1179,148,1183,148,1187,148,1190,148,1195,148,1199,148,1203,148,1207,148,1210,128],{"style":147},[138,1149],{"x":748,"y":1150,"width":1049,"height":1151,"rx":155,"fill":169,"opacity":157,"stroke":169,"style":158},"64.0","71.5",[138,1153],{"x":1154,"y":1150,"width":1049,"height":1151,"rx":155,"fill":1155,"stroke":980,"style":158},"208.5","#f8fafc",[160,1157],{"d":1158,"fill":163,"stroke":164,"style":1159},"M176.5 99.8 L204.5 99.8","stroke-width:2px;marker-end:url(#a11y-ci-arrow)",[138,1161],{"x":1162,"y":1150,"width":1049,"height":1151,"rx":155,"fill":156,"opacity":157,"stroke":156,"style":158},"397.0",[160,1164],{"d":1165,"fill":163,"stroke":164,"style":1159},"M365.0 99.8 L393.0 99.8",[138,1167],{"x":1168,"y":1150,"width":1049,"height":1151,"rx":155,"fill":605,"opacity":967,"stroke":607,"style":158},"585.5",[160,1170],{"d":1171,"fill":163,"stroke":164,"style":1159},"M553.5 99.8 L581.5 99.8",[189,1173,1174],{"x":191,"y":192,"fill":193,"style":194},"Three layers of accessibility checks",[189,1176,1113],{"x":1177,"y":1178,"fill":193,"style":200},"97.2","97.5",[189,1180,1182],{"x":1177,"y":1181,"fill":164,"style":205},"114.4","alt, headings, links · 4 s",[189,1184,1186],{"x":1185,"y":1178,"fill":193,"style":200},"285.8","Build",[189,1188,1189],{"x":1185,"y":1181,"fill":164,"style":205},"static HTML",[189,1191,1194],{"x":1192,"y":1193,"fill":193,"style":200},"474.2","90.4","axe on 60 pages",[189,1196,1198],{"x":1192,"y":1197,"fill":164,"style":205},"107.3","contrast, names, IDs ·",[189,1200,1202],{"x":1192,"y":1201,"fill":164,"style":205},"121.6","70 s",[189,1204,1206],{"x":1205,"y":1193,"fill":193,"style":200},"662.8","Manual pass",[189,1208,1209],{"x":1205,"y":1197,"fill":164,"style":205},"keyboard, NVDA,",[189,1211,1212],{"x":1205,"y":1201,"fill":164,"style":205},"VoiceOver",[250,1214,148,1215,128],{},[253,1216,260,1218,148],{"id":1217,"viewBox":256,"refX":155,"refY":257,"markerWidth":258,"markerHeight":258,"orient":259},"a11y-ci-arrow",[160,1219],{"d":263,"fill":164},[265,1221,1222],{},"The cheap checks run on every pull request; the manual pass runs only when templates or widgets change.",[14,1224,1225],{},"The manual pass matters because automated tools find only part of the problem. Of the 94 distinct issues found on the reference site, axe found 41. The rest — focus order, announcement wording, alt text quality, a dialog that trapped focus but did not return it — needed a person.",[40,1227,1229],{"id":1228},"measured-results-on-the-reference-site","Measured Results on the Reference Site",[14,1231,1232],{},"Six weeks of fixes, with two people spending about a third of their time on it:",[276,1234,1235,1249],{},[279,1236,1237],{},[282,1238,1239,1242,1244,1246],{},[285,1240,1241],{},"Measure",[285,1243,741],{},[285,1245,745],{},[285,1247,1248],{},"Tool",[304,1250,1251,1264,1278,1292,1305,1319],{},[282,1252,1253,1256,1259,1261],{},[309,1254,1255],{},"axe violations, 60-page sample",[309,1257,1258],{},"318 elements",[309,1260,140],{},[309,1262,1263],{},"axe-core 4.10 via Playwright",[282,1265,1266,1269,1272,1275],{},[309,1267,1268],{},"Lighthouse accessibility score, median",[309,1270,1271],{},"84",[309,1273,1274],{},"100",[309,1276,1277],{},"Lighthouse 12",[282,1279,1280,1283,1286,1289],{},[309,1281,1282],{},"Distinct issues from manual audit",[309,1284,1285],{},"53",[309,1287,1288],{},"4 (logged, low impact)",[309,1290,1291],{},"NVDA, VoiceOver, keyboard",[282,1293,1294,1297,1300,1302],{},[309,1295,1296],{},"Content lint findings",[309,1298,1299],{},"486",[309,1301,140],{},[309,1303,1304],{},"remark-lint custom rules",[282,1306,1307,1310,1313,1316],{},[309,1308,1309],{},"JavaScript added by fixes",[309,1311,1312],{},"—",[309,1314,1315],{},"1.4 KB",[309,1317,1318],{},"build output",[282,1320,1321,1324,1327,1329],{},[309,1322,1323],{},"Mobile LCP p75",[309,1325,1326],{},"1.6 s",[309,1328,1326],{},[309,1330,1331],{},"CrUX",[14,1333,1334],{},"The four remaining manual issues are in a third-party API explorer embedded on twelve pages, tracked with the vendor. The LCP line is the one sceptics ask about: none of the work affected performance, because nearly all of it was markup and CSS.",[40,1336,1338],{"id":1337},"common-pitfalls","Common Pitfalls",[48,1340,1341,1347,1353,1362,1368,1382],{},[51,1342,1343,1346],{},[54,1344,1345],{},"Trusting the default theme after customising it."," Every custom component needs the same checks the theme passed.",[51,1348,1349,1352],{},[54,1350,1351],{},"Fixing contrast per element."," Find the token; the same colour is failing on hundreds of pages.",[51,1354,1355,1358,1359,1361],{},[54,1356,1357],{},"Removing focus outlines for mouse users."," Use ",[18,1360,433],{}," instead of removing the ring.",[51,1363,1364,1367],{},[54,1365,1366],{},"Writing alt text that describes the image's appearance."," Describe what the reader needs from it: \"Build time fell from 4 minutes to 70 seconds\" beats \"bar chart\".",[51,1369,1370,1373,1374,1377,1378,1381],{},[54,1371,1372],{},"Using ARIA instead of HTML."," A ",[18,1375,1376],{},"\u003Cdiv role=\"button\">"," needs script for keyboard support that a ",[18,1379,1380],{},"\u003Cbutton>"," has for free.",[51,1383,1384,1387],{},[54,1385,1386],{},"Running only automated checks."," They find less than half of real issues.",[40,1389,1391],{"id":1390},"key-takeaways","Key Takeaways",[48,1393,1394,1397,1400,1403,1406,1415],{},[51,1395,1396],{},"Static sites start ahead because content is in the HTML, but themes, Markdown habits and a few widgets erase the advantage.",[51,1398,1399],{},"Check the default theme before choosing it; violation counts ranged from 0 to 11 rules across five popular themes.",[51,1401,1402],{},"Fix contrast at the token level, in both themes.",[51,1404,1405],{},"Lint Markdown for alt text, heading order and link text; content caused 44% of issues on the reference site.",[51,1407,1408,1409,90,1411,90,1413,67],{},"Prefer native elements for widgets: ",[18,1410,1380],{},[18,1412,1079],{},[18,1414,1086],{},[51,1416,1417],{},"Automate what can be automated and keep a short manual pass for template changes.",[40,1419,1421],{"id":1420},"faq","FAQ",[1423,1424,1426],"h3",{"id":1425},"are-static-sites-more-accessible-than-dynamic-ones-by-default","Are static sites more accessible than dynamic ones by default?",[14,1428,1429],{},"They start from a better position, because the content is in the HTML before any script runs and there is less client-side state to get wrong. They do not become accessible automatically. Theme templates, Markdown habits and client-side widgets such as search dialogs, theme toggles and tabbed code blocks are where static sites fail audits.",[1423,1431,1433],{"id":1432},"which-accessibility-problems-do-automated-tools-miss","Which accessibility problems do automated tools miss?",[14,1435,1436],{},"Automated checkers such as axe and Lighthouse find roughly a third to a half of real issues. They catch missing alt attributes, contrast failures, duplicate IDs and missing labels. They cannot judge whether alt text is useful, whether focus order makes sense, whether a dialog traps focus correctly, or whether a diagram has an adequate text alternative. Manual keyboard and screen reader passes are still required.",[1423,1438,1440],{"id":1439},"where-should-accessibility-checks-run-in-a-static-site-pipeline","Where should accessibility checks run in a static site pipeline?",[14,1442,1443],{},"In three places. Lint the Markdown source for missing alt text and heading jumps before the build, run axe against the built HTML on every pull request, and do a manual keyboard and screen reader pass when a template or interactive component changes. Content checks are cheap and catch most regressions introduced by writers.",[1423,1445,1447],{"id":1446},"which-wcag-level-should-a-documentation-site-target","Which WCAG level should a documentation site target?",[14,1449,1450],{},"WCAG 2.2 level AA is the usual target and the one most procurement and legal requirements reference. It covers contrast of 4.5 to 1 for body text, visible focus, keyboard operability, text alternatives and consistent navigation. Level AAA is rarely achievable across a whole site, but individual criteria such as enhanced contrast are worth adopting where they cost little.",[1423,1452,1454],{"id":1453},"does-accessibility-work-slow-down-a-static-site","Does accessibility work slow down a static site?",[14,1456,1457],{},"Almost never. Most fixes are markup and CSS: landmarks, headings, labels, focus styles and contrast. The few that add script, such as a theme toggle or a focus-trapping dialog, add well under 2 KB when written without a framework. On the reference documentation site in this topic, the full set of fixes added 1.4 KB of JavaScript and no measurable change to LCP.",[40,1459,1461],{"id":1460},"related","Related",[48,1463,1464,1472,1477,1482,1487,1492,1497,1502,1507,1512,1517],{},[51,1465,1466,57,1469,1471],{},[54,1467,1468],{},"Up:",[26,1470,29],{"href":28}," — accessibility as a selection criterion.",[51,1473,1474,1476],{},[26,1475,66],{"href":65}," — focus styles, tab order and keyboard traps.",[51,1478,1479,1481],{},[26,1480,61],{"href":60}," — layout markup for every generator.",[51,1483,1484,1486],{},[26,1485,76],{"href":75}," — trace failures to tokens and fix them once.",[51,1488,1489,1491],{},[26,1490,80],{"href":79}," — a labelled toggle with no flash.",[51,1493,1494,1496],{},[26,1495,89],{"href":88}," — lint and repair heading levels.",[51,1498,1499,1501],{},[26,1500,94],{"href":93}," — fail the build on missing or useless alt text.",[51,1503,1504,1506],{},[26,1505,98],{"href":97}," — focusable, readable, labelled code.",[51,1508,1509,1511],{},[26,1510,102],{"href":101}," — titles, descriptions and text alternatives.",[51,1513,1514,1516],{},[26,1515,34],{"href":33}," — comparing generators before you choose.",[51,1518,1519,1521],{},[26,1520,115],{"href":114}," — the automated checks in the pipeline.",[1523,1524,1525],"style",{},"html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}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 .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":447,"searchDepth":507,"depth":507,"links":1527},[1528,1529,1530,1531,1532,1533,1534,1535,1536,1537,1538,1539,1546],{"id":42,"depth":507,"text":43},{"id":270,"depth":507,"text":271},{"id":399,"depth":507,"text":400},{"id":647,"depth":507,"text":648},{"id":823,"depth":507,"text":824},{"id":914,"depth":507,"text":915},{"id":1065,"depth":507,"text":1066},{"id":1101,"depth":507,"text":1102},{"id":1228,"depth":507,"text":1229},{"id":1337,"depth":507,"text":1338},{"id":1390,"depth":507,"text":1391},{"id":1420,"depth":507,"text":1421,"children":1540},[1541,1542,1543,1544,1545],{"id":1425,"depth":539,"text":1426},{"id":1432,"depth":539,"text":1433},{"id":1439,"depth":539,"text":1440},{"id":1446,"depth":539,"text":1447},{"id":1453,"depth":539,"text":1454},{"id":1460,"depth":507,"text":1461},[1548,1551,1552],{"name":1549,"item":1550},"Home","\u002F",{"name":29,"item":28},{"name":5,"item":1553},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002F","2026-10-02","Make a static site usable by keyboard, screen reader and low-vision readers: themes, headings, focus, contrast, code blocks, diagrams and CI checks.","md",[1558,1559,1560,1561,1562],{"q":1426,"a":1429},{"q":1433,"a":1436},{"q":1440,"a":1443},{"q":1447,"a":1450},{"q":1454,"a":1457},{},true,"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites",{"title":5,"description":1555},"choosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Findex","guide","CDz3M1_QD7pamBab1gmCxgqozijWCkN7Rl6eji7jhHs",[1571,1573,1575,1577,1579,1581,1583,1584,1586,1588,1591,1594,1597,1600,1603,1606,1609,1612,1615,1618,1621,1624,1627,1630,1633,1636,1639,1642,1645,1648,1651,1654,1657,1660,1663,1666,1669,1672,1675,1678,1681,1684,1687,1690,1693,1696,1699,1702,1705,1708,1711,1714,1717,1720,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,1859,1862,1865,1868,1871,1874,1877,1880,1883,1886,1889,1892,1895,1898,1901,1904,1906,1909,1912,1915,1918,1921,1924,1927,1930,1933,1936,1939,1942,1945,1948,1951,1954,1957,1960,1963,1966,1969,1972,1975,1978,1981,1984,1987,1990,1993,1996,1999,2002,2005,2008,2011,2014,2017,2020,2023,2026,2029,2032,2035,2038,2041,2044,2047,2050,2053,2056,2059,2062,2065,2068,2071,2074,2077,2080,2083,2086,2089,2092,2095,2098,2101,2104,2107,2110,2113,2116,2119,2122,2125,2128,2131,2134,2137,2140,2143,2146,2149,2152,2155,2158,2161,2164,2167,2170,2173,2176,2179,2182,2185,2188,2191,2194,2197,2200,2203,2206,2209,2212,2215,2218,2221,2224,2227,2230,2233,2236,2239,2242,2245,2248,2251,2254,2257,2260,2263,2266,2269,2272,2275,2278,2281,2284,2287,2290,2293,2296,2299,2302,2305,2308,2311,2314,2317,2320,2323,2326,2329,2332,2335,2338,2341,2344,2347,2350,2353,2356,2359,2362,2365,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,2500,2503,2506,2509,2512,2515,2518,2521,2524,2527,2530,2533,2536,2539,2542,2545,2548,2551,2554,2557,2560,2563,2566,2569,2572,2575,2578,2581,2584,2587,2590,2593,2596,2599,2602,2605,2608,2611,2614,2617,2620,2623,2626,2629,2632,2635,2638,2641,2644,2647,2650,2653,2656,2659,2662,2665,2668,2671,2674,2677,2680,2682,2685,2688,2691,2694,2697,2700,2703],{"path":1572,"title":98},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-code-blocks-in-documentation-sites",{"path":1574,"title":80},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-dark-mode-toggles-for-static-sites",{"path":1576,"title":102},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-svg-diagrams-on-static-sites",{"path":1578,"title":94},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fenforcing-alt-text-for-markdown-images-at-build-time",{"path":1580,"title":89},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content",{"path":1582,"title":76},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-low-color-contrast-flagged-by-lighthouse",{"path":1565,"title":5},{"path":1585,"title":66},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fkeyboard-navigation-and-focus-order-on-static-sites",{"path":1587,"title":61},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fskip-links-and-landmarks-in-ssg-layouts",{"path":1589,"title":1590},"\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":1592,"title":1593},"\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":1595,"title":1596},"\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":1598,"title":1599},"\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":1601,"title":1602},"\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":1604,"title":1605},"\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":1607,"title":1608},"\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":1610,"title":1611},"\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":1613,"title":1614},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1616,"title":1617},"\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":1619,"title":1620},"\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":1622,"title":1623},"\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":1625,"title":1626},"\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":1628,"title":1629},"\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":1631,"title":1632},"\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":1634,"title":1635},"\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":1637,"title":1638},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1640,"title":1641},"\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":1643,"title":1644},"\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":1646,"title":1647},"\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":1649,"title":1650},"\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":1652,"title":1653},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1655,"title":1656},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1658,"title":1659},"\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":1661,"title":1662},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1664,"title":1665},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1667,"title":1668},"\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":1670,"title":1671},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1673,"title":1674},"\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":1676,"title":1677},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1679,"title":1680},"\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":1682,"title":1683},"\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":1685,"title":1686},"\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":1688,"title":1689},"\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":1691,"title":1692},"\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":1694,"title":1695},"\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":1697,"title":1698},"\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":1700,"title":1701},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1703,"title":1704},"\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":1706,"title":1707},"\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":1709,"title":1710},"\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":1712,"title":1713},"\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":1715,"title":1716},"\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":1718,"title":1719},"\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":1721,"title":29},"\u002Fchoosing-the-right-static-site-generator-for-production",{"path":1723,"title":1724},"\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":1726,"title":1727},"\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":1729,"title":1730},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1732,"title":1733},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1735,"title":1736},"\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":1738,"title":1739},"\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":1741,"title":1742},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1744,"title":1745},"\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":1747,"title":1748},"\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":1750,"title":1751},"\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":1753,"title":1754},"\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":1756,"title":1757},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1759,"title":1760},"\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":1762,"title":1763},"\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":1765,"title":1766},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1768,"title":1769},"\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":1771,"title":1772},"\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":1774,"title":1775},"\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":1777,"title":1778},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1780,"title":1781},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1783,"title":1784},"\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":1786,"title":1787},"\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":1789,"title":1790},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1792,"title":1793},"\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":1795,"title":1796},"\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":1798,"title":1799},"\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":1801,"title":1802},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1804,"title":1805},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1807,"title":1808},"\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":1810,"title":1811},"\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":1813,"title":1814},"\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":1816,"title":1817},"\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":1819,"title":1820},"\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":1822,"title":1823},"\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":1825,"title":1826},"\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":1828,"title":1829},"\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":1831,"title":1832},"\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":1834,"title":1835},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1837,"title":1838},"\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":1840,"title":1841},"\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":1843,"title":1844},"\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":1846,"title":1847},"\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":1849,"title":1850},"\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":1852,"title":1853},"\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":1855,"title":1856},"\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":1858,"title":111},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Faccessible-search-ui-for-static-sites",{"path":1860,"title":1861},"\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":1863,"title":1864},"\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":1866,"title":1867},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1869,"title":1870},"\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":1872,"title":1873},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1875,"title":1876},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1878,"title":1879},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1881,"title":1882},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1884,"title":1885},"\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":1887,"title":1888},"\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":1890,"title":1891},"\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":1893,"title":1894},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1896,"title":1897},"\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":1899,"title":1900},"\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":1902,"title":1903},"\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":1905,"title":34},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults",{"path":1907,"title":1908},"\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":1910,"title":1911},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1913,"title":1914},"\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":1916,"title":1917},"\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":1919,"title":1920},"\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":1922,"title":1923},"\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":1925,"title":1926},"\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":1928,"title":1929},"\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":1931,"title":1932},"\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":1934,"title":1935},"\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":1937,"title":1938},"\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":1940,"title":1941},"\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":1943,"title":1944},"\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":1946,"title":1947},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1949,"title":1950},"\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":1952,"title":1953},"\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":1955,"title":1956},"\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":1958,"title":1959},"\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":1961,"title":1962},"\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":1964,"title":1965},"\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":1967,"title":1968},"\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":1970,"title":1971},"\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":1973,"title":1974},"\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":1976,"title":1977},"\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":1979,"title":1980},"\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":1982,"title":1983},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1985,"title":1986},"\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":1988,"title":1989},"\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":1991,"title":1992},"\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":1994,"title":1995},"\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":1997,"title":1998},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":2000,"title":2001},"\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":2003,"title":2004},"\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":2006,"title":2007},"\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":2009,"title":2010},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":2012,"title":2013},"\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":2015,"title":2016},"\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":2018,"title":2019},"\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":2021,"title":2022},"\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":2024,"title":2025},"\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":2027,"title":2028},"\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":2030,"title":2031},"\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":2033,"title":2034},"\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":2036,"title":2037},"\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":2039,"title":2040},"\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":2042,"title":2043},"\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":2045,"title":2046},"\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":2048,"title":2049},"\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":2051,"title":2052},"\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":2054,"title":2055},"\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":2057,"title":2058},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":2060,"title":2061},"\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":2063,"title":2064},"\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":2066,"title":2067},"\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":2069,"title":2070},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":2072,"title":2073},"\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":2075,"title":2076},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":2078,"title":2079},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":2081,"title":2082},"\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":2084,"title":2085},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":2087,"title":2088},"\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":2090,"title":2091},"\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":2093,"title":2094},"\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":2096,"title":2097},"\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":2099,"title":2100},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":2102,"title":2103},"\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":2105,"title":2106},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":2108,"title":2109},"\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":2111,"title":2112},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":2114,"title":2115},"\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":2117,"title":2118},"\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":2120,"title":2121},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":2123,"title":2124},"\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":2126,"title":2127},"\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":2129,"title":2130},"\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":2132,"title":2133},"\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":2135,"title":2136},"\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":2138,"title":2139},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":2141,"title":2142},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":2144,"title":2145},"\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":2147,"title":2148},"\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":2150,"title":2151},"\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":2153,"title":2154},"\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":2156,"title":2157},"\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":2159,"title":2160},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":2162,"title":2163},"\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":2165,"title":2166},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":2168,"title":2169},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":2171,"title":2172},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":2174,"title":2175},"\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":2177,"title":2178},"\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":2180,"title":2181},"\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":2183,"title":2184},"\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":2186,"title":2187},"\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":2189,"title":2190},"\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":2192,"title":2193},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":2195,"title":2196},"\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":2198,"title":2199},"\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":2201,"title":2202},"\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":2204,"title":2205},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fcomparing-lab-and-field-data-with-crux","Comparing Lab and Field Data with CrUX",{"path":2207,"title":2208},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":2210,"title":2211},"\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":2213,"title":2214},"\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":2216,"title":2217},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":2219,"title":2220},"\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":2222,"title":2223},"\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":2225,"title":2226},"\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":2228,"title":2229},"\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":2231,"title":2232},"\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":2234,"title":2235},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2237,"title":2238},"\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":2240,"title":2241},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2243,"title":2244},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2246,"title":2247},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2249,"title":2250},"\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":2252,"title":2253},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2255,"title":2256},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2258,"title":2259},"\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":2261,"title":2262},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2264,"title":2265},"\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":2267,"title":2268},"\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":2270,"title":2271},"\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":2273,"title":2274},"\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":2276,"title":2277},"\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":2279,"title":2280},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2282,"title":2283},"\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":2285,"title":2286},"\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":2288,"title":2289},"\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":2291,"title":2292},"\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":2294,"title":2295},"\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":2297,"title":2298},"\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":2300,"title":2301},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2303,"title":2304},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2306,"title":2307},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2309,"title":2310},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2312,"title":2313},"\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":2315,"title":2316},"\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":2318,"title":2319},"\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":2321,"title":2322},"\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":2324,"title":2325},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2327,"title":2328},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2330,"title":2331},"\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":2333,"title":2334},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2336,"title":2337},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2339,"title":2340},"\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":2342,"title":2343},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2345,"title":2346},"\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":2348,"title":2349},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2351,"title":2352},"\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":2354,"title":2355},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2357,"title":2358},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2360,"title":2361},"\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":2363,"title":2364},"\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":2366,"title":2367},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2369,"title":2370},"\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":2372,"title":2373},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2375,"title":2376},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2378,"title":2379},"\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":2381,"title":2382},"\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":2384,"title":2385},"\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":2387,"title":2388},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2390,"title":2391},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2393,"title":2394},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2396,"title":2397},"\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":2399,"title":2400},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2402,"title":2403},"\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":2405,"title":2406},"\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":2408,"title":2409},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2411,"title":2412},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2414,"title":2415},"\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":2417,"title":2418},"\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":2420,"title":2421},"\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":2423,"title":2424},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2426,"title":2427},"\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":2429,"title":2430},"\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":2432,"title":2433},"\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":2435,"title":2436},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":2438,"title":2439},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2441,"title":2442},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fbuilding-a-core-web-vitals-dashboard-from-rum-data","Building a Core Web Vitals Dashboard from RUM Data",{"path":2444,"title":2445},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fcrawling-for-broken-links-on-a-schedule","Crawling for Broken Links on a Schedule",{"path":2447,"title":2448},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ffinding-the-cause-of-a-sudden-field-lcp-drop","Finding the Cause of a Sudden Field LCP Drop",{"path":2450,"title":2451},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2453,"title":2454},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2456,"title":2457},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2459,"title":2460},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Freal-user-error-tracking-on-static-sites","Real-User Error Tracking on Static Sites",{"path":2462,"title":2463},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2465,"title":2466},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2468,"title":2469},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fuptime-and-synthetic-checks-for-static-sites","Uptime and Synthetic Checks for Static Sites",{"path":2471,"title":2472},"\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":2474,"title":2475},"\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":2477,"title":2478},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2480,"title":2481},"\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":2483,"title":2484},"\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":2486,"title":2487},"\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":2489,"title":2490},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2492,"title":2493},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2495,"title":2496},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2498,"title":2499},"\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":2501,"title":2502},"\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":2504,"title":2505},"\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":2507,"title":2508},"\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":2510,"title":2511},"\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":2513,"title":2514},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2516,"title":2517},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2519,"title":2520},"\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":2522,"title":2523},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2525,"title":2526},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2528,"title":2529},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2531,"title":2532},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2534,"title":2535},"\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":2537,"title":2538},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2540,"title":2541},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2543,"title":2544},"\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":2546,"title":2547},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2549,"title":2550},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2552,"title":2553},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2555,"title":2556},"\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":2558,"title":2559},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2561,"title":2562},"\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":2564,"title":2565},"\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":2567,"title":2568},"\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":2570,"title":2571},"\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":2573,"title":2574},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Frunning-smoke-tests-against-a-preview-url","Running Smoke Tests Against a Preview URL",{"path":2576,"title":2577},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2579,"title":2580},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2582,"title":2583},"\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":2585,"title":2586},"\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":2588,"title":2589},"\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":2591,"title":2592},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2594,"title":2595},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2597,"title":2598},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2600,"title":2601},"\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":2603,"title":2604},"\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":2606,"title":2607},"\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":2609,"title":2610},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2612,"title":2613},"\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":2615,"title":2616},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2618,"title":2619},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2621,"title":2622},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2624,"title":2625},"\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":2627,"title":2628},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2630,"title":2631},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2633,"title":2634},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2636,"title":2637},"\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":2639,"title":2640},"\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":2642,"title":2643},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2645,"title":2646},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2648,"title":2649},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2651,"title":2652},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2654,"title":2655},"\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":2657,"title":2658},"\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":2660,"title":2661},"\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":2663,"title":2664},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2666,"title":2667},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2669,"title":2670},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2672,"title":2673},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2675,"title":2676},"\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":2678,"title":2679},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2681,"title":115},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Faccessibility-testing-with-axe-and-pa11y-in-ci",{"path":2683,"title":2684},"\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":2686,"title":2687},"\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":2689,"title":2690},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2692,"title":2693},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2695,"title":2696},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2698,"title":2699},"\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":2701,"title":2702},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2704,"title":2705},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",null,1790943190976]