[{"data":1,"prerenderedAt":2667},["ShallowReactive",2],{"page:\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content":3,"all-docs-nav":1519,"filed:\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content":2661},{"id":4,"title":5,"body":6,"breadcrumb":1495,"dateModified":1505,"datePublished":1505,"description":1506,"extension":1507,"faq":1508,"meta":1513,"navigation":411,"path":1514,"seo":1515,"slug":12,"stem":1516,"type":1517,"__hash__":1518},"content\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content\u002Findex.md","Fixing Heading Order Problems in Markdown Content",{"type":7,"value":8,"toc":1476},"minimark",[9,13,26,35,40,53,57,60,153,156,282,286,295,336,339,343,346,564,571,705,709,723,727,730,951,964,968,975,1121,1132,1249,1253,1349,1352,1356,1389,1393,1396,1400,1405,1408,1412,1415,1419,1422,1426,1429,1433,1472],[10,11,5],"h1",{"id":12},"fixing-heading-order-problems-in-markdown-content",[14,15,16,17,21,22,25],"p",{},"Screen reader users navigate long pages by headings more than by anything else. NVDA's H key jumps to the next heading, the numbers 1 to 6 jump by level, and the elements list shows the page as an outline. That outline is only as good as the heading levels in the content. When a writer chooses ",[18,19,20],"code",{},"####"," because the H2 looked too large, or starts a file with ",[18,23,24],{},"# Title"," under a layout that already renders the title, the outline lies: a skipped level suggests a missing section, and two H1s suggest two pages.",[14,27,28,29,34],{},"On the reference site from ",[30,31,33],"a",{"href":32},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002F","Accessibility for Static Sites",", the first content lint found 173 skipped levels and 22 pages with two H1s across 1,140 pages. This guide fixes them in bulk with a codemod, adds a lint that blocks new ones, and covers the template and component cases a Markdown lint cannot see.",[36,37,39],"h2",{"id":38},"prerequisites","Prerequisites",[41,42,43,47,50],"ul",{},[44,45,46],"li",{},"A Markdown pipeline that accepts remark or markdown-it plugins, or Hugo render hooks.",[44,48,49],{},"Write access to the content repository and a CI step for pull requests.",[44,51,52],{},"Agreement with writers on the convention: the layout renders the H1; Markdown starts at H2.",[36,54,56],{"id":55},"what-the-audit-found","What the Audit Found",[14,58,59],{},"A remark script listed every heading with its level, file and line, then flagged three patterns:",[61,62,63,79],"table",{},[64,65,66],"thead",{},[67,68,69,73,76],"tr",{},[70,71,72],"th",{},"Pattern",[70,74,75],{},"Example",[70,77,78],{},"Count",[80,81,82,94,108,125,139],"tbody",{},[67,83,84,88,91],{},[85,86,87],"td",{},"Skipped level going deeper",[85,89,90],{},"H2 followed by H4",[85,92,93],{},"173",[67,95,96,99,105],{},[85,97,98],{},"Second H1 from Markdown",[85,100,101,104],{},[18,102,103],{},"# Getting started"," under a layout H1",[85,106,107],{},"22",[67,109,110,113,122],{},[85,111,112],{},"Empty or symbol-only heading",[85,114,115,118,119],{},[18,116,117],{},"## "," or ",[18,120,121],{},"### ---",[85,123,124],{},"9",[67,126,127,130,136],{},[85,128,129],{},"Heading used for a callout",[85,131,132,135],{},[18,133,134],{},"#### Note"," before a paragraph",[85,137,138],{},"61 (subset of the 173)",[67,140,141,144,150],{},[85,142,143],{},"Bold paragraph used as a heading",[85,145,146,149],{},[18,147,148],{},"**Configuration**"," on its own line",[85,151,152],{},"118",[14,154,155],{},"The last row is the opposite problem: text that looks like a heading but is not one, so it is invisible in the outline. It is not a WCAG failure in every case, but on reference pages where the bold lines introduced sections, they were converted to real headings.",[157,158,159,278],"figure",{},[160,161,168,169,168,173,168,177,168,184],"svg",{"viewBox":162,"role":163,"ariaLabelledBy":164,"xmlns":167},"0 0 760 295","img",[165,166],"heading-found-title","heading-found-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[170,171,172],"title",{"id":165},"Number of heading problems found by pattern in the first audit",[174,175,176],"desc",{"id":166},"Vertical bars. Bold paragraphs used as headings 118. Skipped levels 173, of which 61 were headings used as callouts. Second H1 from Markdown 22. Empty headings 9.",[178,179],"rect",{"x":180,"y":180,"width":181,"height":182,"fill":183},"0","760","295","#ffffff",[185,186,188,189,188,200,188,208,188,213,188,218,188,225,188,231,188,239,188,245,188,250,188,254,188,257,188,261,188,264,188,268,188,271,188,275,168],"g",{"style":187},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[178,190],{"x":191,"y":192,"width":193,"height":194,"rx":195,"fill":196,"opacity":197,"stroke":198,"style":199},"67.2","76.0","81.6","170.0","3","#ff595e","0.3","#d83b41","stroke-width:1px",[178,201],{"x":202,"y":203,"width":193,"height":204,"rx":195,"fill":205,"opacity":206,"stroke":207,"style":199},"203.2","130.0","116.0","#ffca3a","0.45","#a97b00",[178,209],{"x":210,"y":211,"width":193,"height":212,"rx":195,"fill":205,"opacity":206,"stroke":207,"style":199},"339.2","186.1","59.9",[178,214],{"x":215,"y":216,"width":193,"height":217,"rx":195,"fill":196,"opacity":197,"stroke":198,"style":199},"475.2","224.4","21.6",[178,219],{"x":220,"y":221,"width":193,"height":222,"rx":195,"fill":223,"stroke":224,"style":199},"611.2","237.2","8.8","#d9e2ef","#556071",[226,227],"path",{"d":228,"fill":229,"stroke":224,"style":230},"M30.0 246.0 L730.0 246.0","none","stroke-width:1.5px",[232,233,238],"text",{"x":234,"y":235,"fill":236,"style":237},"380.0","30.0","#1f2937","font-size:16px;text-anchor:middle;font-weight:700","Heading problems by pattern",[232,240,93],{"x":241,"y":242,"fill":243,"style":244},"108.0","69.0","#b32b30","font-size:12px;text-anchor:middle;font-weight:700",[232,246,249],{"x":241,"y":247,"fill":224,"style":248},"264.0","font-size:11.5px;text-anchor:middle","Skipped level",[232,251,152],{"x":252,"y":253,"fill":236,"style":244},"244.0","123.0",[232,255,256],{"x":252,"y":247,"fill":224,"style":248},"Bold as heading",[232,258,260],{"x":234,"y":259,"fill":236,"style":244},"179.1","61",[232,262,263],{"x":234,"y":247,"fill":224,"style":248},"Heading as callout",[232,265,107],{"x":266,"y":267,"fill":243,"style":244},"516.0","217.4",[232,269,270],{"x":266,"y":247,"fill":224,"style":248},"Second H1",[232,272,124],{"x":273,"y":274,"fill":236,"style":244},"652.0","230.2",[232,276,277],{"x":273,"y":247,"fill":224,"style":248},"Empty heading",[279,280,281],"figcaption",{},"1,140 pages scanned; bold-as-heading lines were reviewed by hand before conversion.",[36,283,285],{"id":284},"step-1-remove-the-duplicate-h1s","Step 1: Remove the Duplicate H1s",[14,287,288,289,291,292,294],{},"Starlight, VitePress and Docusaurus render the frontmatter ",[18,290,170],{}," as the H1. Twenty-two files also started with ",[18,293,24],{},", a habit carried over from a previous generator. A one-line check finds them and a small script removes the first line when it matches the frontmatter title:",[296,297,302],"pre",{"className":298,"code":299,"language":300,"meta":301,"style":301},"language-sh shiki shiki-themes github-light github-dark","grep -rlE '^# ' src\u002Fcontent\u002Fdocs | while read f; do\n  title=$(sed -n 's\u002F^title: *\u002F\u002Fp' \"$f\" | head -1 | tr -d \"'\\\"\")\n  first=$(grep -m1 -E '^# ' \"$f\" | sed 's\u002F^# \u002F\u002F')\n  [ \"$title\" = \"$first\" ] && sed -i \"0,\u002F^# \u002F{\u002F^# \u002Fd}\" \"$f\"\ndone\n","sh","",[18,303,304,312,318,324,330],{"__ignoreMap":301},[305,306,309],"span",{"class":307,"line":308},"line",1,[305,310,311],{},"grep -rlE '^# ' src\u002Fcontent\u002Fdocs | while read f; do\n",[305,313,315],{"class":307,"line":314},2,[305,316,317],{},"  title=$(sed -n 's\u002F^title: *\u002F\u002Fp' \"$f\" | head -1 | tr -d \"'\\\"\")\n",[305,319,321],{"class":307,"line":320},3,[305,322,323],{},"  first=$(grep -m1 -E '^# ' \"$f\" | sed 's\u002F^# \u002F\u002F')\n",[305,325,327],{"class":307,"line":326},4,[305,328,329],{},"  [ \"$title\" = \"$first\" ] && sed -i \"0,\u002F^# \u002F{\u002F^# \u002Fd}\" \"$f\"\n",[305,331,333],{"class":307,"line":332},5,[305,334,335],{},"done\n",[14,337,338],{},"Where the Markdown H1 differed from the title, a writer chose which to keep. Three of those pages had a better H1 in the Markdown than in the frontmatter, and the frontmatter was updated instead.",[36,340,342],{"id":341},"step-2-repair-skipped-levels-with-a-codemod","Step 2: Repair Skipped Levels With a Codemod",[14,344,345],{},"Most skipped levels follow a pattern: an H2 section with H4 subsections, where H3 was skipped because it looked too big. Promoting each heading to at most one level below its parent fixes the outline without changing meaning:",[296,347,351],{"className":348,"code":349,"language":350,"meta":301,"style":301},"language-js shiki shiki-themes github-light github-dark","\u002F\u002F scripts\u002Ffix-heading-levels.mjs\nimport { remark } from 'remark';\nimport { visit } from 'unist-util-visit';\nimport remarkFrontmatter from 'remark-frontmatter';\n\nexport function fixLevels() {\n  return (tree) => {\n    let prev = 1; \u002F\u002F layout renders the H1\n    visit(tree, 'heading', (node) => {\n      if (node.depth > prev + 1) node.depth = prev + 1;\n      prev = node.depth;\n    });\n  };\n}\n\u002F\u002F run over every file with remark().use(remarkFrontmatter).use(fixLevels)\n","js",[18,352,353,359,379,393,407,413,429,451,473,497,529,540,546,552,558],{"__ignoreMap":301},[305,354,355],{"class":307,"line":308},[305,356,358],{"class":357},"sJ8bj","\u002F\u002F scripts\u002Ffix-heading-levels.mjs\n",[305,360,361,365,369,372,376],{"class":307,"line":314},[305,362,364],{"class":363},"szBVR","import",[305,366,368],{"class":367},"sVt8B"," { remark } ",[305,370,371],{"class":363},"from",[305,373,375],{"class":374},"sZZnC"," 'remark'",[305,377,378],{"class":367},";\n",[305,380,381,383,386,388,391],{"class":307,"line":320},[305,382,364],{"class":363},[305,384,385],{"class":367}," { visit } ",[305,387,371],{"class":363},[305,389,390],{"class":374}," 'unist-util-visit'",[305,392,378],{"class":367},[305,394,395,397,400,402,405],{"class":307,"line":326},[305,396,364],{"class":363},[305,398,399],{"class":367}," remarkFrontmatter ",[305,401,371],{"class":363},[305,403,404],{"class":374}," 'remark-frontmatter'",[305,406,378],{"class":367},[305,408,409],{"class":307,"line":332},[305,410,412],{"emptyLinePlaceholder":411},true,"\n",[305,414,416,419,422,426],{"class":307,"line":415},6,[305,417,418],{"class":363},"export",[305,420,421],{"class":363}," function",[305,423,425],{"class":424},"sScJk"," fixLevels",[305,427,428],{"class":367},"() {\n",[305,430,432,435,438,442,445,448],{"class":307,"line":431},7,[305,433,434],{"class":363},"  return",[305,436,437],{"class":367}," (",[305,439,441],{"class":440},"s4XuR","tree",[305,443,444],{"class":367},") ",[305,446,447],{"class":363},"=>",[305,449,450],{"class":367}," {\n",[305,452,454,457,460,463,467,470],{"class":307,"line":453},8,[305,455,456],{"class":363},"    let",[305,458,459],{"class":367}," prev ",[305,461,462],{"class":363},"=",[305,464,466],{"class":465},"sj4cs"," 1",[305,468,469],{"class":367},"; ",[305,471,472],{"class":357},"\u002F\u002F layout renders the H1\n",[305,474,476,479,482,485,488,491,493,495],{"class":307,"line":475},9,[305,477,478],{"class":424},"    visit",[305,480,481],{"class":367},"(tree, ",[305,483,484],{"class":374},"'heading'",[305,486,487],{"class":367},", (",[305,489,490],{"class":440},"node",[305,492,444],{"class":367},[305,494,447],{"class":363},[305,496,450],{"class":367},[305,498,500,503,506,509,511,514,516,519,521,523,525,527],{"class":307,"line":499},10,[305,501,502],{"class":363},"      if",[305,504,505],{"class":367}," (node.depth ",[305,507,508],{"class":363},">",[305,510,459],{"class":367},[305,512,513],{"class":363},"+",[305,515,466],{"class":465},[305,517,518],{"class":367},") node.depth ",[305,520,462],{"class":363},[305,522,459],{"class":367},[305,524,513],{"class":363},[305,526,466],{"class":465},[305,528,378],{"class":367},[305,530,532,535,537],{"class":307,"line":531},11,[305,533,534],{"class":367},"      prev ",[305,536,462],{"class":363},[305,538,539],{"class":367}," node.depth;\n",[305,541,543],{"class":307,"line":542},12,[305,544,545],{"class":367},"    });\n",[305,547,549],{"class":307,"line":548},13,[305,550,551],{"class":367},"  };\n",[305,553,555],{"class":307,"line":554},14,[305,556,557],{"class":367},"}\n",[305,559,561],{"class":307,"line":560},15,[305,562,563],{"class":357},"\u002F\u002F run over every file with remark().use(remarkFrontmatter).use(fixLevels)\n",[14,565,566,567,570],{},"The codemod changed 173 headings in 211 files' worth of diffs. The 61 callout headings were then converted by hand to the site's ",[18,568,569],{},":::note"," aside syntax, because a callout is not a section and should not be in the outline at all. Reviewing the diff took one person about three hours.",[157,572,573,702],{},[160,574,168,579,168,582,168,585,168,588],{"viewBox":575,"role":163,"ariaLabelledBy":576,"xmlns":167},"0 0 760 300",[577,578],"heading-outline-title","heading-outline-desc",[170,580,581],{"id":577},"Number of skipped heading levels per section of the docs before and after",[174,583,584],{"id":578},"Paired bars by docs section. Guides went from 64 skipped levels to 0. API reference from 51 to 0. Tutorials from 38 to 0. Concepts from 20 to 0.",[178,586],{"x":180,"y":180,"width":181,"height":587,"fill":183},"300",[185,589,188,590,188,597,188,603,188,609,188,613,188,617,188,620,188,624,188,627,188,631,188,634,188,637,188,640,188,646,188,650,188,655,188,661,188,666,188,670,188,675,188,678,188,682,188,687,188,690,188,694,188,699,168],{"style":187},[178,591],{"x":592,"y":593,"width":594,"height":595,"rx":596,"fill":196,"opacity":197,"stroke":198,"style":199},"306.8","50.0","14.0","12.0","2",[178,598],{"x":599,"y":593,"width":594,"height":595,"rx":596,"fill":600,"opacity":601,"stroke":602,"style":199},"398.4","#8ac926","0.4","#5a8a16",[178,604],{"x":605,"y":606,"width":607,"height":608,"rx":195,"fill":196,"opacity":197,"stroke":198,"style":199},"230.0","82.0","479.9","16.0",[178,610],{"x":605,"y":611,"width":612,"height":608,"rx":195,"fill":600,"opacity":601,"stroke":602,"style":199},"102.0","3.0",[178,614],{"x":605,"y":615,"width":616,"height":608,"rx":195,"fill":196,"opacity":197,"stroke":198,"style":199},"134.0","382.4",[178,618],{"x":605,"y":619,"width":612,"height":608,"rx":195,"fill":600,"opacity":601,"stroke":602,"style":199},"154.0",[178,621],{"x":605,"y":622,"width":623,"height":608,"rx":195,"fill":196,"opacity":197,"stroke":198,"style":199},"186.0","284.9",[178,625],{"x":605,"y":626,"width":612,"height":608,"rx":195,"fill":600,"opacity":601,"stroke":602,"style":199},"206.0",[178,628],{"x":605,"y":629,"width":630,"height":608,"rx":195,"fill":196,"opacity":197,"stroke":198,"style":199},"238.0","150.0",[178,632],{"x":605,"y":633,"width":612,"height":608,"rx":195,"fill":600,"opacity":601,"stroke":602,"style":199},"258.0",[226,635],{"d":636,"fill":229,"stroke":224,"style":230},"M230.0 78.0 L230.0 280.0",[232,638,639],{"x":234,"y":235,"fill":236,"style":237},"Outline depth jumps before and after the codemod",[232,641,645],{"x":642,"y":643,"fill":224,"style":644},"326.8","60.0","font-size:12px;text-anchor:start","Before",[232,647,649],{"x":648,"y":643,"fill":224,"style":644},"418.4","After",[232,651,654],{"x":652,"y":653,"fill":236,"style":644},"20.0","105.2","Guides",[232,656,660],{"x":657,"y":658,"fill":243,"style":659},"716.9","94.5","font-size:11.5px;text-anchor:start;font-weight:700","64",[232,662,180],{"x":663,"y":664,"fill":665,"style":659},"240.0","114.5","#3f6410",[232,667,669],{"x":652,"y":668,"fill":236,"style":644},"157.2","API reference",[232,671,674],{"x":672,"y":673,"fill":243,"style":659},"619.4","146.5","51",[232,676,180],{"x":663,"y":677,"fill":665,"style":659},"166.5",[232,679,681],{"x":652,"y":680,"fill":236,"style":644},"209.2","Tutorials",[232,683,686],{"x":684,"y":685,"fill":243,"style":659},"521.9","198.5","38",[232,688,180],{"x":663,"y":689,"fill":665,"style":659},"218.5",[232,691,693],{"x":652,"y":692,"fill":236,"style":644},"261.2","Concepts",[232,695,698],{"x":696,"y":697,"fill":243,"style":659},"387.0","250.5","20",[232,700,180],{"x":663,"y":701,"fill":665,"style":659},"270.5",[279,703,704],{},"Counted by the lint over every file in each section; the after column is zero by construction and was confirmed with the HTML check.",[36,706,708],{"id":707},"step-3-make-size-a-styling-decision","Step 3: Make Size a Styling Decision",[14,710,711,712,715,716,718,719,722],{},"Writers picked deeper levels because the default H3 was 1.5 rem and looked heavy inside short sections. The type scale was adjusted so H3 is 1.2 rem and H4 1.05 rem with a heavier weight, which removed the visual reason to skip. For the rare heading that genuinely needs a smaller look, Starlight and Astro Markdown support ",[18,713,714],{},"{.class}"," attributes through a remark plugin, and Hugo supports ",[18,717,714],{}," on headings natively with ",[18,720,721],{},"markup.goldmark.parser.attribute.title = true",".",[36,724,726],{"id":725},"step-4-lint-every-pull-request","Step 4: Lint Every Pull Request",[14,728,729],{},"The lint runs the same depth rule and two others, failing on any violation with a message that names the fix:",[296,731,733],{"className":348,"code":732,"language":350,"meta":301,"style":301},"\u002F\u002F plugins\u002Fremark-heading-lint.mjs\nexport default function headingLint() {\n  return (tree, file) => {\n    let prev = 1;\n    visit(tree, 'heading', (node) => {\n      const text = toString(node).trim();\n      if (node.depth === 1) file.fail('Do not use # in Markdown; the layout renders the page title as H1', node);\n      if (!text) file.fail('Empty heading', node);\n      if (node.depth > prev + 1)\n        file.fail(`Heading jumps from H${prev} to H${node.depth}; use H${prev + 1} and style it with CSS if it looks too large`, node);\n      prev = node.depth;\n    });\n  };\n}\n",[18,734,735,740,754,774,786,804,827,853,874,891,931,939,943,947],{"__ignoreMap":301},[305,736,737],{"class":307,"line":308},[305,738,739],{"class":357},"\u002F\u002F plugins\u002Fremark-heading-lint.mjs\n",[305,741,742,744,747,749,752],{"class":307,"line":314},[305,743,418],{"class":363},[305,745,746],{"class":363}," default",[305,748,421],{"class":363},[305,750,751],{"class":424}," headingLint",[305,753,428],{"class":367},[305,755,756,758,760,762,765,768,770,772],{"class":307,"line":320},[305,757,434],{"class":363},[305,759,437],{"class":367},[305,761,441],{"class":440},[305,763,764],{"class":367},", ",[305,766,767],{"class":440},"file",[305,769,444],{"class":367},[305,771,447],{"class":363},[305,773,450],{"class":367},[305,775,776,778,780,782,784],{"class":307,"line":326},[305,777,456],{"class":363},[305,779,459],{"class":367},[305,781,462],{"class":363},[305,783,466],{"class":465},[305,785,378],{"class":367},[305,787,788,790,792,794,796,798,800,802],{"class":307,"line":332},[305,789,478],{"class":424},[305,791,481],{"class":367},[305,793,484],{"class":374},[305,795,487],{"class":367},[305,797,490],{"class":440},[305,799,444],{"class":367},[305,801,447],{"class":363},[305,803,450],{"class":367},[305,805,806,809,812,815,818,821,824],{"class":307,"line":415},[305,807,808],{"class":363},"      const",[305,810,811],{"class":465}," text",[305,813,814],{"class":363}," =",[305,816,817],{"class":424}," toString",[305,819,820],{"class":367},"(node).",[305,822,823],{"class":424},"trim",[305,825,826],{"class":367},"();\n",[305,828,829,831,833,836,838,841,844,847,850],{"class":307,"line":431},[305,830,502],{"class":363},[305,832,505],{"class":367},[305,834,835],{"class":363},"===",[305,837,466],{"class":465},[305,839,840],{"class":367},") file.",[305,842,843],{"class":424},"fail",[305,845,846],{"class":367},"(",[305,848,849],{"class":374},"'Do not use # in Markdown; the layout renders the page title as H1'",[305,851,852],{"class":367},", node);\n",[305,854,855,857,859,862,865,867,869,872],{"class":307,"line":453},[305,856,502],{"class":363},[305,858,437],{"class":367},[305,860,861],{"class":363},"!",[305,863,864],{"class":367},"text) file.",[305,866,843],{"class":424},[305,868,846],{"class":367},[305,870,871],{"class":374},"'Empty heading'",[305,873,852],{"class":367},[305,875,876,878,880,882,884,886,888],{"class":307,"line":475},[305,877,502],{"class":363},[305,879,505],{"class":367},[305,881,508],{"class":363},[305,883,459],{"class":367},[305,885,513],{"class":363},[305,887,466],{"class":465},[305,889,890],{"class":367},")\n",[305,892,893,896,898,900,903,906,909,911,913,916,919,921,924,926,929],{"class":307,"line":499},[305,894,895],{"class":367},"        file.",[305,897,843],{"class":424},[305,899,846],{"class":367},[305,901,902],{"class":374},"`Heading jumps from H${",[305,904,905],{"class":367},"prev",[305,907,908],{"class":374},"} to H${",[305,910,490],{"class":367},[305,912,722],{"class":374},[305,914,915],{"class":367},"depth",[305,917,918],{"class":374},"}; use H${",[305,920,905],{"class":367},[305,922,923],{"class":363}," +",[305,925,466],{"class":465},[305,927,928],{"class":374},"} and style it with CSS if it looks too large`",[305,930,852],{"class":367},[305,932,933,935,937],{"class":307,"line":531},[305,934,534],{"class":367},[305,936,462],{"class":363},[305,938,539],{"class":367},[305,940,941],{"class":307,"line":542},[305,942,545],{"class":367},[305,944,945],{"class":307,"line":548},[305,946,551],{"class":367},[305,948,949],{"class":307,"line":554},[305,950,557],{"class":367},[14,952,953,956,957,960,961,722],{},[18,954,955],{},"file.fail"," throws, so the build stops with the file and line. For Eleventy, the same logic goes in a markdown-it core rule that walks ",[18,958,959],{},"heading_open"," tokens; for Hugo, a heading render hook can track the previous level in a page scratch variable and call ",[18,962,963],{},"errorf",[36,965,967],{"id":966},"step-5-check-the-rendered-html-too","Step 5: Check the Rendered HTML Too",[14,969,970,971,974],{},"Components can add headings the Markdown lint never sees. The reference site had two: a \"Related\" component that rendered an H4 at the end of every page, after an H2, and an API parameter table component that used H5 for each parameter name. A post-build check walks every page's headings in document order inside ",[18,972,973],{},"\u003Cmain>"," and applies the same rule:",[296,976,978],{"className":348,"code":977,"language":350,"meta":301,"style":301},"const hs = [...main.querySelectorAll('h1,h2,h3,h4,h5,h6')].map(h => +h.tagName[1]);\nhs.reduce((prev, d, i) => { if (d > prev + 1) problems.push(`${file}: H${prev} → H${d} at heading ${i}`); return d; }, 0);\n",[18,979,980,1032],{"__ignoreMap":301},[305,981,982,985,988,990,993,996,999,1002,1004,1007,1010,1013,1015,1018,1021,1023,1026,1029],{"class":307,"line":308},[305,983,984],{"class":363},"const",[305,986,987],{"class":465}," hs",[305,989,814],{"class":363},[305,991,992],{"class":367}," [",[305,994,995],{"class":363},"...",[305,997,998],{"class":367},"main.",[305,1000,1001],{"class":424},"querySelectorAll",[305,1003,846],{"class":367},[305,1005,1006],{"class":374},"'h1,h2,h3,h4,h5,h6'",[305,1008,1009],{"class":367},")].",[305,1011,1012],{"class":424},"map",[305,1014,846],{"class":367},[305,1016,1017],{"class":440},"h",[305,1019,1020],{"class":363}," =>",[305,1022,923],{"class":363},[305,1024,1025],{"class":367},"h.tagName[",[305,1027,1028],{"class":465},"1",[305,1030,1031],{"class":367},"]);\n",[305,1033,1034,1037,1040,1043,1045,1047,1050,1052,1055,1057,1059,1062,1065,1068,1070,1072,1074,1076,1079,1082,1084,1087,1089,1092,1094,1097,1099,1102,1104,1107,1110,1113,1116,1118],{"class":307,"line":314},[305,1035,1036],{"class":367},"hs.",[305,1038,1039],{"class":424},"reduce",[305,1041,1042],{"class":367},"((",[305,1044,905],{"class":440},[305,1046,764],{"class":367},[305,1048,1049],{"class":440},"d",[305,1051,764],{"class":367},[305,1053,1054],{"class":440},"i",[305,1056,444],{"class":367},[305,1058,447],{"class":363},[305,1060,1061],{"class":367}," { ",[305,1063,1064],{"class":363},"if",[305,1066,1067],{"class":367}," (d ",[305,1069,508],{"class":363},[305,1071,459],{"class":367},[305,1073,513],{"class":363},[305,1075,466],{"class":465},[305,1077,1078],{"class":367},") problems.",[305,1080,1081],{"class":424},"push",[305,1083,846],{"class":367},[305,1085,1086],{"class":374},"`${",[305,1088,767],{"class":367},[305,1090,1091],{"class":374},"}: H${",[305,1093,905],{"class":367},[305,1095,1096],{"class":374},"} → H${",[305,1098,1049],{"class":367},[305,1100,1101],{"class":374},"} at heading ${",[305,1103,1054],{"class":367},[305,1105,1106],{"class":374},"}`",[305,1108,1109],{"class":367},"); ",[305,1111,1112],{"class":363},"return",[305,1114,1115],{"class":367}," d; }, ",[305,1117,180],{"class":465},[305,1119,1120],{"class":367},");\n",[14,1122,1123,1124,1127,1128,1131],{},"The Related component became an H2, and the parameter names became ",[18,1125,1126],{},"\u003Cdt>"," elements in a definition list, which is what they were. axe's ",[18,1129,1130],{},"heading-order"," rule covers the same ground on the pages it scans, but this check covers all 1,140 pages in two seconds.",[157,1133,1134,1246],{},[160,1135,168,1140,168,1143,168,1146,168,1149,168,1231],{"viewBox":1136,"role":163,"ariaLabelledBy":1137,"xmlns":167},"0 0 760 168",[1138,1139],"heading-checks-title","heading-checks-desc",[170,1141,1142],{"id":1138},"How Markdown and HTML heading checks cover different sources",[174,1144,1145],{"id":1139},"Four steps. Markdown headings written by authors are checked by the remark lint during the build. Component headings rendered by layouts and MDX components are not visible to the lint. The built HTML is checked for heading order inside main on every page. Both feed a single CI result that fails on any jump.",[178,1147],{"x":180,"y":180,"width":181,"height":1148,"fill":183},"168",[185,1150,188,1151,188,1159,188,1163,188,1167,188,1171,188,1174,188,1178,188,1181,188,1184,188,1190,188,1194,188,1199,188,1203,188,1208,188,1211,188,1215,188,1220,188,1224,188,1228,168],{"style":187},[178,1152],{"x":652,"y":1153,"width":1154,"height":1155,"rx":1156,"fill":1157,"opacity":1158,"stroke":1157,"style":230},"64.0","154.5","88.4","8","#1982c4","0.14",[178,1160],{"x":1161,"y":1153,"width":1154,"height":1155,"rx":1156,"fill":205,"opacity":1162,"stroke":207,"style":230},"208.5","0.24",[226,1164],{"d":1165,"fill":229,"stroke":224,"style":1166},"M176.5 108.2 L204.5 108.2","stroke-width:2px;marker-end:url(#heading-checks-arrow)",[178,1168],{"x":1169,"y":1153,"width":1154,"height":1155,"rx":1156,"fill":1170,"opacity":1158,"stroke":1170,"style":230},"397.0","#6a4c93",[226,1172],{"d":1173,"fill":229,"stroke":224,"style":1166},"M365.0 108.2 L393.0 108.2",[178,1175],{"x":1176,"y":1153,"width":1154,"height":1155,"rx":1156,"fill":600,"opacity":1177,"stroke":602,"style":230},"585.5","0.2",[226,1179],{"d":1180,"fill":229,"stroke":224,"style":1166},"M553.5 108.2 L581.5 108.2",[232,1182,1183],{"x":234,"y":235,"fill":236,"style":237},"Two checks, two sources of headings",[232,1185,1189],{"x":1186,"y":1187,"fill":236,"style":1188},"97.2","90.4","font-size:13px;text-anchor:middle;font-weight:700","Markdown",[232,1191,1193],{"x":1186,"y":1192,"fill":236,"style":1188},"107.3","headings",[232,1195,1198],{"x":1186,"y":1196,"fill":224,"style":1197},"124.2","font-size:11px;text-anchor:middle","remark lint with line",[232,1200,1202],{"x":1186,"y":1201,"fill":224,"style":1197},"138.5","numbers",[232,1204,1207],{"x":1205,"y":1206,"fill":236,"style":1188},"285.8","97.5","Component",[232,1209,1193],{"x":1205,"y":1210,"fill":236,"style":1188},"114.4",[232,1212,1214],{"x":1205,"y":1213,"fill":224,"style":1197},"131.3","invisible to the lint",[232,1216,1219],{"x":1217,"y":1218,"fill":236,"style":1188},"474.2","106.0","HTML check",[232,1221,1223],{"x":1217,"y":1222,"fill":224,"style":1197},"122.9","all pages, inside main",[232,1225,1227],{"x":1226,"y":1218,"fill":236,"style":1188},"662.8","One CI result",[232,1229,1230],{"x":1226,"y":1222,"fill":224,"style":1197},"fail on any jump",[1232,1233,188,1234,168],"defs",{},[1235,1236,1242,1243,188],"marker",{"id":1237,"viewBox":1238,"refX":1156,"refY":1239,"markerWidth":1240,"markerHeight":1240,"orient":1241},"heading-checks-arrow","0 0 10 10","5","7","auto-start-reverse","\n      ",[226,1244],{"d":1245,"fill":224},"M0 0 L10 5 L0 10 z",[279,1247,1248],{},"The Markdown lint gives writers a line number; the HTML check catches component headings.",[36,1250,1252],{"id":1251},"measured-impact","Measured Impact",[61,1254,1255,1269],{},[64,1256,1257],{},[67,1258,1259,1262,1264,1266],{},[70,1260,1261],{},"Measure",[70,1263,645],{},[70,1265,649],{},[70,1267,1268],{},"Tool",[80,1270,1271,1283,1294,1310,1323,1336],{},[67,1272,1273,1276,1278,1280],{},[85,1274,1275],{},"Skipped heading levels",[85,1277,93],{},[85,1279,180],{},[85,1281,1282],{},"remark lint",[67,1284,1285,1288,1290,1292],{},[85,1286,1287],{},"Pages with two H1s",[85,1289,107],{},[85,1291,180],{},[85,1293,1219],{},[67,1295,1296,1302,1305,1307],{},[85,1297,1298,1299,1301],{},"axe ",[18,1300,1130],{}," (60 pages)",[85,1303,1304],{},"47 elements",[85,1306,180],{},[85,1308,1309],{},"axe-core 4.10",[67,1311,1312,1315,1318,1320],{},[85,1313,1314],{},"Bold lines converted to headings",[85,1316,1317],{},"—",[85,1319,152],{},[85,1321,1322],{},"Manual review",[67,1324,1325,1328,1330,1333],{},[85,1326,1327],{},"Lint + HTML check time",[85,1329,1317],{},[85,1331,1332],{},"0.3 s + 2 s",[85,1334,1335],{},"CI logs",[67,1337,1338,1341,1343,1346],{},[85,1339,1340],{},"PRs blocked in 8 weeks",[85,1342,1317],{},[85,1344,1345],{},"16, all fixed in the PR",[85,1347,1348],{},"CI history",[14,1350,1351],{},"A screen reader user who tested the API section before and after described the \"after\" outline as the first time the API reference could be navigated \"by its headings instead of by searching for words\".",[36,1353,1355],{"id":1354},"pitfalls-rollback","Pitfalls & Rollback",[41,1357,1358,1365,1371,1377,1383],{},[44,1359,1360,1364],{},[1361,1362,1363],"strong",{},"Fixing the outline by changing CSS only."," Size and level are separate; fix both.",[44,1366,1367,1370],{},[1361,1368,1369],{},"Turning callouts into deeper headings."," Use an aside component instead.",[44,1372,1373,1376],{},[1361,1374,1375],{},"Linting Markdown but not components."," Run the HTML check too.",[44,1378,1379,1382],{},[1361,1380,1381],{},"Running the codemod without review."," Most changes are mechanical, but some deeper headings were meant to be sections of their own.",[44,1384,1385,1388],{},[1361,1386,1387],{},"Rollback:"," the codemod is a single commit that can be reverted; the lint can be set to warn instead of fail with one option.",[36,1390,1392],{"id":1391},"conclusion","Conclusion",[14,1394,1395],{},"Heading levels are the map screen reader users navigate by, and Markdown makes them easy to choose for size instead of structure. On the reference site a codemod repaired 173 skipped levels, a two-line rule removed 22 duplicate H1s, and a lint plus an HTML check keep new problems out of both content and components.",[36,1397,1399],{"id":1398},"faq","FAQ",[1401,1402,1404],"h3",{"id":1403},"is-a-skipped-heading-level-a-wcag-failure","Is a skipped heading level a WCAG failure?",[14,1406,1407],{},"Not strictly. WCAG 1.3.1 requires that structure conveyed visually is available programmatically, and a skipped level is usually reported by axe as a best-practice issue rather than a violation. In practice it misleads screen reader users, who infer a missing section when a level is skipped, so it is worth fixing everywhere and enforcing for new content.",[1401,1409,1411],{"id":1410},"should-the-markdown-title-be-an-h1-if-the-layout-already-renders-one","Should the Markdown title be an H1 if the layout already renders one?",[14,1413,1414],{},"No. Most documentation layouts render the frontmatter title as the page H1, so a Markdown file that starts with a single hash produces a second H1. Either remove the heading from the Markdown or configure the layout not to render the title, but not both. One H1 per page is the convention screen reader users rely on.",[1401,1416,1418],{"id":1417},"how-do-i-make-a-heading-smaller-without-changing-its-level","How do I make a heading smaller without changing its level?",[14,1420,1421],{},"Use CSS. Heading level is structure and size is presentation, so if a section heading looks too large, style it with a class or adjust the type scale rather than picking a deeper level. In Markdown, most generators support attribute syntax or a component for adding a class when one heading genuinely needs a different look.",[1401,1423,1425],{"id":1424},"do-headings-inside-components-and-mdx-count","Do headings inside components and MDX count?",[14,1427,1428],{},"Yes. Screen readers see the rendered HTML, so a component that renders an H4 inside a page section affects the outline just like a Markdown heading. A check on the built HTML catches these; a Markdown-only lint does not.",[36,1430,1432],{"id":1431},"related","Related",[41,1434,1435,1444,1451,1458,1465],{},[44,1436,1437,1440,1441,1443],{},[1361,1438,1439],{},"Parent:"," ",[30,1442,33],{"href":32}," — content issues and how to lint them.",[44,1445,1446,1450],{},[30,1447,1449],{"href":1448},"\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"," — the companion content lint.",[44,1452,1453,1457],{},[30,1454,1456],{"href":1455},"\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"," — the other structure screen readers navigate by.",[44,1459,1460,1464],{},[30,1461,1463],{"href":1462},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint\u002F","Content Linting with markdownlint"," — where content checks run.",[44,1466,1467,1471],{},[30,1468,1470],{"href":1469},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-dynamic-table-of-contents-widgets\u002F","Fixing CLS From Dynamic Table of Contents Widgets"," — a table of contents built from the same headings.",[1473,1474,1475],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}",{"title":301,"searchDepth":314,"depth":314,"links":1477},[1478,1479,1480,1481,1482,1483,1484,1485,1486,1487,1488,1494],{"id":38,"depth":314,"text":39},{"id":55,"depth":314,"text":56},{"id":284,"depth":314,"text":285},{"id":341,"depth":314,"text":342},{"id":707,"depth":314,"text":708},{"id":725,"depth":314,"text":726},{"id":966,"depth":314,"text":967},{"id":1251,"depth":314,"text":1252},{"id":1354,"depth":314,"text":1355},{"id":1391,"depth":314,"text":1392},{"id":1398,"depth":314,"text":1399,"children":1489},[1490,1491,1492,1493],{"id":1403,"depth":320,"text":1404},{"id":1410,"depth":320,"text":1411},{"id":1417,"depth":320,"text":1418},{"id":1424,"depth":320,"text":1425},{"id":1431,"depth":314,"text":1432},[1496,1499,1502,1503],{"name":1497,"item":1498},"Home","\u002F",{"name":1500,"item":1501},"Choosing the Right Static Site Generator for Production","\u002Fchoosing-the-right-static-site-generator-for-production\u002F",{"name":33,"item":32},{"name":5,"item":1504},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content\u002F","2026-10-02","Find and fix skipped heading levels, duplicate H1s and headings used for styling in Markdown, then lint for them in CI so the page outline stays usable.","md",[1509,1510,1511,1512],{"q":1404,"a":1407},{"q":1411,"a":1414},{"q":1418,"a":1421},{"q":1425,"a":1428},{},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content",{"title":5,"description":1506},"choosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content\u002Findex","article","9odOWUFPbJZPgUkeU6bWDJSfuSJ-2S_GWjZ8YMvYV2Y",[1520,1523,1526,1529,1531,1532,1535,1537,1540,1542,1545,1548,1551,1554,1557,1560,1563,1566,1569,1572,1575,1578,1581,1584,1587,1590,1593,1596,1599,1602,1605,1608,1611,1614,1617,1620,1623,1626,1629,1632,1635,1638,1641,1644,1647,1650,1653,1656,1659,1662,1665,1668,1671,1674,1676,1679,1682,1685,1688,1691,1694,1697,1700,1703,1706,1709,1712,1715,1718,1721,1724,1727,1730,1733,1736,1739,1742,1745,1748,1751,1754,1757,1760,1763,1766,1769,1772,1775,1778,1781,1784,1787,1790,1793,1796,1799,1802,1805,1808,1811,1814,1817,1820,1823,1826,1829,1832,1835,1838,1841,1844,1847,1850,1853,1856,1859,1862,1865,1868,1871,1874,1877,1880,1883,1886,1889,1892,1895,1898,1901,1904,1907,1910,1913,1916,1919,1922,1925,1928,1931,1934,1937,1940,1943,1946,1949,1952,1955,1958,1961,1964,1967,1970,1973,1976,1979,1982,1985,1988,1991,1994,1997,2000,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,2292,2295,2298,2301,2304,2307,2310,2313,2316,2319,2322,2325,2328,2331,2334,2337,2340,2343,2346,2349,2352,2355,2358,2361,2364,2367,2370,2373,2376,2379,2382,2385,2388,2391,2394,2397,2400,2403,2406,2409,2412,2415,2418,2421,2424,2427,2430,2433,2436,2439,2442,2445,2448,2451,2454,2457,2460,2463,2466,2469,2472,2475,2478,2481,2484,2487,2490,2493,2496,2499,2502,2505,2508,2511,2514,2517,2520,2523,2526,2529,2532,2535,2538,2541,2544,2547,2550,2553,2556,2559,2562,2565,2568,2571,2574,2577,2580,2583,2586,2589,2592,2595,2598,2601,2604,2607,2610,2613,2616,2619,2622,2625,2628,2631,2634,2637,2640,2643,2646,2649,2652,2655,2658],{"path":1521,"title":1522},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-code-blocks-in-documentation-sites","Accessible Code Blocks in Documentation Sites",{"path":1524,"title":1525},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-dark-mode-toggles-for-static-sites","Accessible Dark Mode Toggles for Static Sites",{"path":1527,"title":1528},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-svg-diagrams-on-static-sites","Accessible SVG Diagrams on Static Sites",{"path":1530,"title":1449},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fenforcing-alt-text-for-markdown-images-at-build-time",{"path":1514,"title":5},{"path":1533,"title":1534},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-low-color-contrast-flagged-by-lighthouse","Fixing Low Color Contrast Flagged by Lighthouse",{"path":1536,"title":33},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites",{"path":1538,"title":1539},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fkeyboard-navigation-and-focus-order-on-static-sites","Keyboard Navigation and Focus Order on Static Sites",{"path":1541,"title":1456},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fskip-links-and-landmarks-in-ssg-layouts",{"path":1543,"title":1544},"\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":1546,"title":1547},"\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":1549,"title":1550},"\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":1552,"title":1553},"\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":1555,"title":1556},"\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":1558,"title":1559},"\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":1561,"title":1562},"\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":1564,"title":1565},"\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":1567,"title":1568},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1570,"title":1571},"\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":1573,"title":1574},"\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":1576,"title":1577},"\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":1579,"title":1580},"\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":1582,"title":1583},"\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":1585,"title":1586},"\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":1588,"title":1589},"\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":1591,"title":1592},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1594,"title":1595},"\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":1597,"title":1598},"\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":1600,"title":1601},"\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":1603,"title":1604},"\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":1606,"title":1607},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1609,"title":1610},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1612,"title":1613},"\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":1615,"title":1616},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1618,"title":1619},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1621,"title":1622},"\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":1624,"title":1625},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1627,"title":1628},"\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":1630,"title":1631},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1633,"title":1634},"\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":1636,"title":1637},"\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":1639,"title":1640},"\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":1642,"title":1643},"\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":1645,"title":1646},"\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":1648,"title":1649},"\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":1651,"title":1652},"\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":1654,"title":1655},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1657,"title":1658},"\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":1660,"title":1661},"\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":1663,"title":1664},"\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":1666,"title":1667},"\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":1669,"title":1670},"\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":1672,"title":1673},"\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":1675,"title":1500},"\u002Fchoosing-the-right-static-site-generator-for-production",{"path":1677,"title":1678},"\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":1680,"title":1681},"\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":1683,"title":1684},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1686,"title":1687},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1689,"title":1690},"\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":1692,"title":1693},"\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":1695,"title":1696},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1698,"title":1699},"\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":1701,"title":1702},"\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":1704,"title":1705},"\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":1707,"title":1708},"\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":1710,"title":1711},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1713,"title":1714},"\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":1716,"title":1717},"\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":1719,"title":1720},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1722,"title":1723},"\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":1725,"title":1726},"\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":1728,"title":1729},"\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":1731,"title":1732},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1734,"title":1735},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1737,"title":1738},"\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":1740,"title":1741},"\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":1743,"title":1744},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1746,"title":1747},"\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":1749,"title":1750},"\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":1752,"title":1753},"\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":1755,"title":1756},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1758,"title":1759},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1761,"title":1762},"\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":1764,"title":1765},"\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":1767,"title":1768},"\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":1770,"title":1771},"\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":1773,"title":1774},"\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":1776,"title":1777},"\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":1779,"title":1780},"\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":1782,"title":1783},"\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":1785,"title":1786},"\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":1788,"title":1789},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1791,"title":1792},"\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":1794,"title":1795},"\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":1797,"title":1798},"\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":1800,"title":1801},"\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":1803,"title":1804},"\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":1806,"title":1807},"\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":1809,"title":1810},"\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":1812,"title":1813},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Faccessible-search-ui-for-static-sites","Accessible Search UI for Static Sites",{"path":1815,"title":1816},"\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":1818,"title":1819},"\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":1821,"title":1822},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1824,"title":1825},"\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":1827,"title":1828},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1830,"title":1831},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1833,"title":1834},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1836,"title":1837},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1839,"title":1840},"\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":1842,"title":1843},"\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":1845,"title":1846},"\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":1848,"title":1849},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1851,"title":1852},"\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":1854,"title":1855},"\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":1857,"title":1858},"\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":1860,"title":1861},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1863,"title":1864},"\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":1866,"title":1867},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1869,"title":1870},"\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":1872,"title":1873},"\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":1875,"title":1876},"\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":1878,"title":1879},"\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":1881,"title":1882},"\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":1884,"title":1885},"\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":1887,"title":1888},"\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":1890,"title":1891},"\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":1893,"title":1894},"\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":1896,"title":1897},"\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":1899,"title":1900},"\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":1902,"title":1903},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1905,"title":1906},"\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":1908,"title":1909},"\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":1911,"title":1912},"\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":1914,"title":1915},"\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":1917,"title":1918},"\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":1920,"title":1921},"\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":1923,"title":1924},"\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":1926,"title":1927},"\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":1929,"title":1930},"\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":1932,"title":1933},"\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":1935,"title":1936},"\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":1938,"title":1939},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1941,"title":1942},"\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":1944,"title":1945},"\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":1947,"title":1948},"\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":1950,"title":1951},"\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":1953,"title":1954},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1956,"title":1957},"\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":1959,"title":1960},"\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":1962,"title":1963},"\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":1965,"title":1966},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":1968,"title":1969},"\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":1971,"title":1972},"\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":1974,"title":1975},"\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":1977,"title":1978},"\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":1980,"title":1981},"\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":1983,"title":1984},"\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":1986,"title":1987},"\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":1989,"title":1990},"\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":1992,"title":1993},"\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":1995,"title":1996},"\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":1998,"title":1999},"\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":2001,"title":1470},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-dynamic-table-of-contents-widgets",{"path":2003,"title":2004},"\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":2006,"title":2007},"\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":2009,"title":2010},"\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":2012,"title":2013},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":2015,"title":2016},"\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":2018,"title":2019},"\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":2021,"title":2022},"\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":2024,"title":2025},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":2027,"title":2028},"\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":2030,"title":2031},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":2033,"title":2034},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":2036,"title":2037},"\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":2039,"title":2040},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":2042,"title":2043},"\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":2045,"title":2046},"\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":2048,"title":2049},"\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":2051,"title":2052},"\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":2054,"title":2055},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":2057,"title":2058},"\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":2060,"title":2061},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":2063,"title":2064},"\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":2066,"title":2067},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":2069,"title":2070},"\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":2072,"title":2073},"\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":2075,"title":2076},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":2078,"title":2079},"\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":2081,"title":2082},"\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":2084,"title":2085},"\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":2087,"title":2088},"\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":2090,"title":2091},"\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":2093,"title":2094},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":2096,"title":2097},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":2099,"title":2100},"\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":2102,"title":2103},"\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":2105,"title":2106},"\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":2108,"title":2109},"\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":2111,"title":2112},"\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":2114,"title":2115},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":2117,"title":2118},"\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":2120,"title":2121},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":2123,"title":2124},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":2126,"title":2127},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":2129,"title":2130},"\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":2132,"title":2133},"\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":2135,"title":2136},"\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":2138,"title":2139},"\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":2141,"title":2142},"\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":2144,"title":2145},"\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":2147,"title":2148},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":2150,"title":2151},"\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":2153,"title":2154},"\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":2156,"title":2157},"\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":2159,"title":2160},"\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":2162,"title":2163},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":2165,"title":2166},"\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":2168,"title":2169},"\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":2171,"title":2172},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":2174,"title":2175},"\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":2177,"title":2178},"\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":2180,"title":2181},"\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":2183,"title":2184},"\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":2186,"title":2187},"\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":2189,"title":2190},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2192,"title":2193},"\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":2195,"title":2196},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2198,"title":2199},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2201,"title":2202},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2204,"title":2205},"\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":2207,"title":2208},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2210,"title":2211},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2213,"title":2214},"\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":2216,"title":2217},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2219,"title":2220},"\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":2222,"title":2223},"\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":2225,"title":2226},"\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":2228,"title":2229},"\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":2231,"title":2232},"\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":2234,"title":2235},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2237,"title":2238},"\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":2240,"title":2241},"\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":2243,"title":2244},"\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":2246,"title":2247},"\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":2249,"title":2250},"\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":2252,"title":2253},"\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":2255,"title":2256},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2258,"title":2259},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2261,"title":2262},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2264,"title":2265},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2267,"title":2268},"\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":2270,"title":2271},"\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":2273,"title":2274},"\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":2276,"title":2277},"\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":2279,"title":2280},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2282,"title":2283},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2285,"title":2286},"\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":2288,"title":2289},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2291,"title":1463},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint",{"path":2293,"title":2294},"\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":2296,"title":2297},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2299,"title":2300},"\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":2302,"title":2303},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2305,"title":2306},"\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":2308,"title":2309},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2311,"title":2312},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2314,"title":2315},"\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":2317,"title":2318},"\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":2320,"title":2321},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2323,"title":2324},"\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":2326,"title":2327},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2329,"title":2330},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2332,"title":2333},"\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":2335,"title":2336},"\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":2338,"title":2339},"\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":2341,"title":2342},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2344,"title":2345},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2347,"title":2348},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2350,"title":2351},"\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":2353,"title":2354},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2356,"title":2357},"\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":2359,"title":2360},"\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":2362,"title":2363},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2365,"title":2366},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2368,"title":2369},"\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":2371,"title":2372},"\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":2374,"title":2375},"\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":2377,"title":2378},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2380,"title":2381},"\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":2383,"title":2384},"\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":2386,"title":2387},"\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":2389,"title":2390},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":2392,"title":2393},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2395,"title":2396},"\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":2398,"title":2399},"\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":2401,"title":2402},"\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":2404,"title":2405},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2407,"title":2408},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2410,"title":2411},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2413,"title":2414},"\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":2416,"title":2417},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2419,"title":2420},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2422,"title":2423},"\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":2425,"title":2426},"\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":2428,"title":2429},"\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":2431,"title":2432},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2434,"title":2435},"\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":2437,"title":2438},"\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":2440,"title":2441},"\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":2443,"title":2444},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2446,"title":2447},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2449,"title":2450},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2452,"title":2453},"\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":2455,"title":2456},"\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":2458,"title":2459},"\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":2461,"title":2462},"\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":2464,"title":2465},"\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":2467,"title":2468},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2470,"title":2471},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2473,"title":2474},"\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":2476,"title":2477},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2479,"title":2480},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2482,"title":2483},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2485,"title":2486},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2488,"title":2489},"\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":2491,"title":2492},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2494,"title":2495},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2497,"title":2498},"\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":2500,"title":2501},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2503,"title":2504},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2506,"title":2507},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2509,"title":2510},"\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":2512,"title":2513},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2515,"title":2516},"\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":2518,"title":2519},"\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":2521,"title":2522},"\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":2524,"title":2525},"\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":2527,"title":2528},"\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":2530,"title":2531},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2533,"title":2534},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2536,"title":2537},"\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":2539,"title":2540},"\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":2542,"title":2543},"\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":2545,"title":2546},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2548,"title":2549},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2551,"title":2552},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2554,"title":2555},"\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":2557,"title":2558},"\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":2560,"title":2561},"\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":2563,"title":2564},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2566,"title":2567},"\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":2569,"title":2570},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2572,"title":2573},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2575,"title":2576},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2578,"title":2579},"\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":2581,"title":2582},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2584,"title":2585},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2587,"title":2588},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2590,"title":2591},"\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":2593,"title":2594},"\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":2596,"title":2597},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2599,"title":2600},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2602,"title":2603},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2605,"title":2606},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2608,"title":2609},"\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":2611,"title":2612},"\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":2614,"title":2615},"\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":2617,"title":2618},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2620,"title":2621},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2623,"title":2624},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2626,"title":2627},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2629,"title":2630},"\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":2632,"title":2633},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2635,"title":2636},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Faccessibility-testing-with-axe-and-pa11y-in-ci","Accessibility Testing with axe and pa11y in CI",{"path":2638,"title":2639},"\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":2641,"title":2642},"\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":2644,"title":2645},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2647,"title":2648},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2650,"title":2651},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2653,"title":2654},"\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":2656,"title":2657},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2659,"title":2660},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2662,"tools":2666},{"label":2663,"plural":2664,"u":2665},"Fix","Fixes","\u002Fguides\u002Ffixes\u002F",[],1790943191163]