[{"data":1,"prerenderedAt":1938},["ShallowReactive",2],{"page:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcustomizing-starlight-without-forking-the-theme":3,"all-docs-nav":1398},{"id":4,"title":5,"body":6,"breadcrumb":1373,"dateModified":1383,"datePublished":1383,"description":1384,"extension":1385,"faq":1386,"meta":1391,"navigation":1392,"path":1393,"seo":1394,"slug":12,"stem":1395,"type":1396,"__hash__":1397},"content\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcustomizing-starlight-without-forking-the-theme\u002Findex.md","Customizing Starlight Without Forking the Theme",{"type":7,"value":8,"toc":1355},"minimark",[9,13,17,31,36,53,57,60,327,342,345,462,466,492,558,565,569,572,618,633,755,759,762,915,926,930,933,1017,1149,1152,1156,1159,1174,1185,1195,1205,1208,1212,1270,1274,1277,1281,1286,1289,1293,1296,1300,1303,1307,1310,1314,1351],[10,11,5],"h1",{"id":12},"customizing-starlight-without-forking-the-theme",[14,15,16],"p",{},"Starlight is easy to brand badly. The fastest route to \"make it look like our product\" is to copy its layout components into your project and edit them, and that route turns every Starlight release into a manual merge. The alternative takes the same afternoon and costs nothing on upgrade: change design tokens first, override named components second, wrap rather than replace, and package repeated changes as a plugin.",[14,18,19,20,25,26,30],{},"This guide applies that ladder to a real brand restyle — the one from ",[21,22,24],"a",{"href":23},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fdocusaurus-vs-starlight-for-product-documentation\u002F","Docusaurus vs Starlight for Product Documentation"," — and measures what each rung cost at upgrade time. It sits under ",[21,27,29],{"href":28},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002F","Docs Frameworks: Docusaurus, Starlight and VitePress",".",[32,33,35],"h2",{"id":34},"prerequisites","Prerequisites",[37,38,39,43,46],"ul",{},[40,41,42],"li",{},"A Starlight project (Astro 5, Starlight 0.30 or newer).",[40,44,45],{},"The brand's colour palette with light and dark values, the web font files, and a logo in SVG.",[40,47,48,49,30],{},"A preview deploy for every pull request so each change is reviewed on a real URL — see ",[21,50,52],{"href":51},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002F","Preview Environments for Pull Requests",[32,54,56],{"id":55},"rung-1-design-tokens-in-css","Rung 1: Design Tokens in CSS",[14,58,59],{},"Starlight reads roughly sixty CSS custom properties. Colours, the accent hue, fonts, the content width and the sidebar width are all tokens, and most brand requirements end here.",[61,62,67],"pre",{"className":63,"code":64,"language":65,"meta":66,"style":66},"language-css shiki shiki-themes github-light github-dark","\u002F* src\u002Fstyles\u002Fbrand.css *\u002F\n:root {\n  --sl-font: 'Inter Variable', system-ui, sans-serif;\n  --sl-font-mono: 'JetBrains Mono', ui-monospace, monospace;\n  --sl-content-width: 48rem;\n  --sl-sidebar-width: 17rem;\n}\n:root[data-theme='light'] {\n  --sl-color-accent-low: #e6ddf3;\n  --sl-color-accent: #6a4c93;\n  --sl-color-accent-high: #34244d;\n  --sl-color-white: #1f2937;\n  --sl-color-gray-1: #334155;\n}\n:root[data-theme='dark'] {\n  --sl-color-accent-low: #2a1f3b;\n  --sl-color-accent: #b79de0;\n  --sl-color-accent-high: #ece4f8;\n}\n","css","",[68,69,70,79,90,119,142,159,174,180,200,213,226,239,252,265,270,286,298,310,322],"code",{"__ignoreMap":66},[71,72,75],"span",{"class":73,"line":74},"line",1,[71,76,78],{"class":77},"sJ8bj","\u002F* src\u002Fstyles\u002Fbrand.css *\u002F\n",[71,80,82,86],{"class":73,"line":81},2,[71,83,85],{"class":84},"sScJk",":root",[71,87,89],{"class":88},"sVt8B"," {\n",[71,91,93,97,100,104,107,111,113,116],{"class":73,"line":92},3,[71,94,96],{"class":95},"s4XuR","  --sl-font",[71,98,99],{"class":88},": ",[71,101,103],{"class":102},"sZZnC","'Inter Variable'",[71,105,106],{"class":88},", ",[71,108,110],{"class":109},"sj4cs","system-ui",[71,112,106],{"class":88},[71,114,115],{"class":109},"sans-serif",[71,117,118],{"class":88},";\n",[71,120,122,125,127,130,132,135,137,140],{"class":73,"line":121},4,[71,123,124],{"class":95},"  --sl-font-mono",[71,126,99],{"class":88},[71,128,129],{"class":102},"'JetBrains Mono'",[71,131,106],{"class":88},[71,133,134],{"class":109},"ui-monospace",[71,136,106],{"class":88},[71,138,139],{"class":109},"monospace",[71,141,118],{"class":88},[71,143,145,148,150,153,157],{"class":73,"line":144},5,[71,146,147],{"class":95},"  --sl-content-width",[71,149,99],{"class":88},[71,151,152],{"class":109},"48",[71,154,156],{"class":155},"szBVR","rem",[71,158,118],{"class":88},[71,160,162,165,167,170,172],{"class":73,"line":161},6,[71,163,164],{"class":95},"  --sl-sidebar-width",[71,166,99],{"class":88},[71,168,169],{"class":109},"17",[71,171,156],{"class":155},[71,173,118],{"class":88},[71,175,177],{"class":73,"line":176},7,[71,178,179],{"class":88},"}\n",[71,181,183,185,188,191,194,197],{"class":73,"line":182},8,[71,184,85],{"class":84},[71,186,187],{"class":88},"[",[71,189,190],{"class":84},"data-theme",[71,192,193],{"class":155},"=",[71,195,196],{"class":102},"'light'",[71,198,199],{"class":88},"] {\n",[71,201,203,206,208,211],{"class":73,"line":202},9,[71,204,205],{"class":95},"  --sl-color-accent-low",[71,207,99],{"class":88},[71,209,210],{"class":109},"#e6ddf3",[71,212,118],{"class":88},[71,214,216,219,221,224],{"class":73,"line":215},10,[71,217,218],{"class":95},"  --sl-color-accent",[71,220,99],{"class":88},[71,222,223],{"class":109},"#6a4c93",[71,225,118],{"class":88},[71,227,229,232,234,237],{"class":73,"line":228},11,[71,230,231],{"class":95},"  --sl-color-accent-high",[71,233,99],{"class":88},[71,235,236],{"class":109},"#34244d",[71,238,118],{"class":88},[71,240,242,245,247,250],{"class":73,"line":241},12,[71,243,244],{"class":95},"  --sl-color-white",[71,246,99],{"class":88},[71,248,249],{"class":109},"#1f2937",[71,251,118],{"class":88},[71,253,255,258,260,263],{"class":73,"line":254},13,[71,256,257],{"class":95},"  --sl-color-gray-1",[71,259,99],{"class":88},[71,261,262],{"class":109},"#334155",[71,264,118],{"class":88},[71,266,268],{"class":73,"line":267},14,[71,269,179],{"class":88},[71,271,273,275,277,279,281,284],{"class":73,"line":272},15,[71,274,85],{"class":84},[71,276,187],{"class":88},[71,278,190],{"class":84},[71,280,193],{"class":155},[71,282,283],{"class":102},"'dark'",[71,285,199],{"class":88},[71,287,289,291,293,296],{"class":73,"line":288},16,[71,290,205],{"class":95},[71,292,99],{"class":88},[71,294,295],{"class":109},"#2a1f3b",[71,297,118],{"class":88},[71,299,301,303,305,308],{"class":73,"line":300},17,[71,302,218],{"class":95},[71,304,99],{"class":88},[71,306,307],{"class":109},"#b79de0",[71,309,118],{"class":88},[71,311,313,315,317,320],{"class":73,"line":312},18,[71,314,231],{"class":95},[71,316,99],{"class":88},[71,318,319],{"class":109},"#ece4f8",[71,321,118],{"class":88},[71,323,325],{"class":73,"line":324},19,[71,326,179],{"class":88},[14,328,329,330,333,334,337,338,30],{},"Register the file with ",[68,331,332],{},"customCss: ['.\u002Fsrc\u002Fstyles\u002Fbrand.css']"," and add the fonts with ",[68,335,336],{},"@fontsource-variable\u002Finter"," imported from the same list, so they are bundled and preloaded rather than fetched from a third party — the reasoning is in ",[21,339,341],{"href":340},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fself-hosting-google-fonts-to-eliminate-layout-shift\u002F","Self-Hosting Google Fonts to Eliminate Layout Shift",[14,343,344],{},"Check contrast in both themes before moving on. The accent colour is used for link text and the active sidebar item, and a brand purple that passes on white often fails on Starlight's dark background; that is why the dark block above uses a lighter tint rather than the same hex.",[346,347,348,458],"figure",{},[349,350,357,358,357,362,357,366,357,373],"svg",{"viewBox":351,"role":352,"ariaLabelledBy":353,"xmlns":356},"0 0 760 300","img",[354,355],"csl-ladder-title","csl-ladder-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[359,360,361],"title",{"id":354},"Four rungs of Starlight customisation and what each touches",[363,364,365],"desc",{"id":355},"Four stacked layers. Tokens change CSS variables and touch no markup. Overrides replace a named component with one of the same props. Wrappers import the original and add content around it. Plugins bundle config, overrides and routes for reuse. Upgrade risk rises from none to low as you go up.",[367,368],"rect",{"x":369,"y":369,"width":370,"height":371,"fill":372},"0","760","300","#ffffff",[374,375,377,378,377,385,377,396,377,402,377,407,377,413,377,417,377,421,377,424,377,427,377,433,377,437,377,440,377,444,377,448,377,452,377,455,357],"g",{"style":376},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[379,380,384],"text",{"x":381,"y":382,"fill":249,"style":383},"380","28","font-size:16px;font-weight:700;text-anchor:middle","Stop at the lowest rung that meets the design",[367,386],{"x":387,"y":388,"width":389,"height":390,"rx":391,"fill":392,"opacity":393,"stroke":394,"style":395},"60","226","640","46","8","#8ac926","0.18","#5a8a16","stroke-width:1.5px",[379,397,401],{"x":398,"y":399,"fill":249,"style":400},"80","254","font-weight:700","1 · Tokens",[379,403,406],{"x":404,"y":399,"fill":405},"230","#556071","--sl-color-accent, --sl-font, widths",[379,408,412],{"x":409,"y":399,"fill":410,"style":411},"680","#3f6410","font-weight:700;text-anchor:end","no upgrade risk",[367,414],{"x":387,"y":415,"width":389,"height":390,"rx":391,"fill":392,"opacity":416,"stroke":394,"style":395},"170","0.1",[379,418,420],{"x":398,"y":419,"fill":249,"style":400},"198","2 · Override",[379,422,423],{"x":404,"y":419,"fill":405},"components: { Header: '.\u002FHeader.astro' }",[379,425,426],{"x":409,"y":419,"fill":410,"style":411},"props contract",[367,428],{"x":387,"y":429,"width":389,"height":390,"rx":391,"fill":430,"opacity":431,"stroke":432,"style":395},"114","#ffca3a","0.22","#a97b00",[379,434,436],{"x":398,"y":435,"fill":249,"style":400},"142","3 · Wrap",[379,438,439],{"x":404,"y":435,"fill":405},"import Default from '@astrojs\u002Fstarlight\u002Fcomponents\u002F…'",[379,441,443],{"x":409,"y":435,"fill":442,"style":411},"#8a6d0f","low",[367,445],{"x":387,"y":446,"width":389,"height":390,"rx":391,"fill":223,"opacity":447,"stroke":223,"style":395},"58","0.12",[379,449,451],{"x":398,"y":450,"fill":249,"style":400},"86","4 · Plugin",[379,453,454],{"x":404,"y":450,"fill":405},"config hooks + overrides + routes, versioned package",[379,456,457],{"x":409,"y":450,"fill":223,"style":411},"low, shared",[459,460,461],"figcaption",{},"Copying Starlight's source is deliberately absent from this ladder: nothing in a normal brand restyle requires it.",[32,463,465],{"id":464},"rung-2-override-a-named-component","Rung 2: Override a Named Component",[14,467,468,469,106,472,106,475,106,478,106,481,106,484,487,488,491],{},"When the markup itself must change — a product switcher in the header, a support link in the footer — override that one component. Starlight exposes components such as ",[68,470,471],{},"Header",[68,473,474],{},"Footer",[68,476,477],{},"PageTitle",[68,479,480],{},"Sidebar",[68,482,483],{},"SocialIcons",[68,485,486],{},"ThemeSelect"," and ",[68,489,490],{},"Head"," by name.",[61,493,497],{"className":494,"code":495,"language":496,"meta":66,"style":66},"language-js shiki shiki-themes github-light github-dark","\u002F\u002F astro.config.mjs\nstarlight({\n  title: 'Acme Docs',\n  components: {\n    SocialIcons: '.\u002Fsrc\u002Fcomponents\u002FProductSwitcher.astro',\n    Footer: '.\u002Fsrc\u002Fcomponents\u002FFooter.astro',\n  },\n});\n","js",[68,498,499,504,512,523,528,538,548,553],{"__ignoreMap":66},[71,500,501],{"class":73,"line":74},[71,502,503],{"class":77},"\u002F\u002F astro.config.mjs\n",[71,505,506,509],{"class":73,"line":81},[71,507,508],{"class":84},"starlight",[71,510,511],{"class":88},"({\n",[71,513,514,517,520],{"class":73,"line":92},[71,515,516],{"class":88},"  title: ",[71,518,519],{"class":102},"'Acme Docs'",[71,521,522],{"class":88},",\n",[71,524,525],{"class":73,"line":121},[71,526,527],{"class":88},"  components: {\n",[71,529,530,533,536],{"class":73,"line":144},[71,531,532],{"class":88},"    SocialIcons: ",[71,534,535],{"class":102},"'.\u002Fsrc\u002Fcomponents\u002FProductSwitcher.astro'",[71,537,522],{"class":88},[71,539,540,543,546],{"class":73,"line":161},[71,541,542],{"class":88},"    Footer: ",[71,544,545],{"class":102},"'.\u002Fsrc\u002Fcomponents\u002FFooter.astro'",[71,547,522],{"class":88},[71,549,550],{"class":73,"line":176},[71,551,552],{"class":88},"  },\n",[71,554,555],{"class":73,"line":182},[71,556,557],{"class":88},"});\n",[14,559,560,561,564],{},"An override receives ",[68,562,563],{},"Astro.locals.starlightRoute"," with the same data the original uses — the current page's entry, the sidebar, the locale, the edit URL — so it can render anything the original could. Keep overrides small and presentational; anything that fetches data or computes navigation belongs in a plugin or a content collection, where it can be tested independently.",[32,566,568],{"id":567},"rung-3-wrap-the-original","Rung 3: Wrap the Original",[14,570,571],{},"Most \"override\" requests are really \"add something next to the existing thing\". Import the default component and render it inside yours:",[61,573,577],{"className":574,"code":575,"language":576,"meta":66,"style":66},"language-astro shiki shiki-themes github-light github-dark","---\n\u002F\u002F src\u002Fcomponents\u002FFooter.astro\nimport Default from '@astrojs\u002Fstarlight\u002Fcomponents\u002FFooter.astro';\nconst { entry } = Astro.locals.starlightRoute;\nconst owner = entry.data.owner ?? 'docs-team';\n---\n\u003CDefault>\u003Cslot \u002F>\u003C\u002FDefault>\n\u003Cp class=\"page-owner\">Maintained by \u003Ca href={`\u002Fteam\u002F${owner}\u002F`}>{owner}\u003C\u002Fa>\u003C\u002Fp>\n","astro",[68,578,579,584,589,594,599,604,608,613],{"__ignoreMap":66},[71,580,581],{"class":73,"line":74},[71,582,583],{},"---\n",[71,585,586],{"class":73,"line":81},[71,587,588],{},"\u002F\u002F src\u002Fcomponents\u002FFooter.astro\n",[71,590,591],{"class":73,"line":92},[71,592,593],{},"import Default from '@astrojs\u002Fstarlight\u002Fcomponents\u002FFooter.astro';\n",[71,595,596],{"class":73,"line":121},[71,597,598],{},"const { entry } = Astro.locals.starlightRoute;\n",[71,600,601],{"class":73,"line":144},[71,602,603],{},"const owner = entry.data.owner ?? 'docs-team';\n",[71,605,606],{"class":73,"line":161},[71,607,583],{},[71,609,610],{"class":73,"line":176},[71,611,612],{},"\u003CDefault>\u003Cslot \u002F>\u003C\u002FDefault>\n",[71,614,615],{"class":73,"line":182},[71,616,617],{},"\u003Cp class=\"page-owner\">Maintained by \u003Ca href={`\u002Fteam\u002F${owner}\u002F`}>{owner}\u003C\u002Fa>\u003C\u002Fp>\n",[14,619,620,621,624,625,628,629,632],{},"Because the original still renders, upstream improvements to the footer (a new \"last updated\" format, an accessibility fix) arrive automatically. Custom front matter such as ",[68,622,623],{},"owner"," is added by extending the docs schema with ",[68,626,627],{},"docsSchema({ extend: z.object({ owner: z.string().optional() }) })"," in ",[68,630,631],{},"src\u002Fcontent.config.ts",", so a typo in front matter fails the build instead of rendering silently.",[346,634,635,744],{},[349,636,357,641,357,644,357,647,357,650,357,729],{"viewBox":637,"role":352,"ariaLabelledBy":638,"xmlns":356},"0 0 760 280",[639,640],"csl-wrap-title","csl-wrap-desc",[359,642,643],{"id":639},"Replace versus wrap on upgrade",[363,645,646],{"id":640},"Two lanes. In the replace lane, the site renders a copied footer, so an upstream fix in the new Starlight release never reaches the site. In the wrap lane, the site renders the original footer plus an addition, so the upstream fix flows through automatically on upgrade.",[367,648],{"x":369,"y":369,"width":370,"height":649,"fill":372},"280",[374,651,377,652,377,655,377,660,377,668,377,674,377,680,377,684,377,689,377,695,377,699,377,702,377,705,377,709,377,713,377,717,377,720,377,724,357],{"style":376},[379,653,654],{"x":381,"y":382,"fill":249,"style":383},"An upstream accessibility fix ships in Starlight x.y+1",[379,656,659],{"x":657,"y":658,"fill":249,"style":400},"40","74","Replace",[367,661],{"x":662,"y":663,"width":664,"height":665,"rx":391,"fill":666,"stroke":667,"style":395},"130","54","160","34","#f8fafc","#d9e2ef",[379,669,673],{"x":670,"y":671,"fill":249,"style":672},"210","76","text-anchor:middle","upstream Footer (fixed)",[367,675],{"x":676,"y":663,"width":415,"height":665,"rx":391,"fill":677,"opacity":678,"stroke":679,"style":395},"330","#ff595e","0.14","#d83b41",[379,681,683],{"x":682,"y":671,"fill":249,"style":672},"415","your copied Footer",[379,685,688],{"x":686,"y":671,"fill":687,"style":400},"520","#b32b30","fix never arrives",[690,691],"path",{"d":692,"stroke":679,"fill":693,"style":694},"M292 71 L326 71","none","stroke-width:2px;stroke-dasharray:4 4",[379,696,698],{"x":657,"y":697,"fill":249,"style":400},"164","Wrap",[367,700],{"x":662,"y":701,"width":664,"height":665,"rx":391,"fill":666,"stroke":667,"style":395},"144",[379,703,673],{"x":670,"y":704,"fill":249,"style":672},"166",[367,706],{"x":676,"y":707,"width":415,"height":446,"rx":391,"fill":392,"opacity":708,"stroke":394,"style":395},"132","0.16",[379,710,712],{"x":682,"y":711,"fill":249,"style":672},"156","\u003CDefault \u002F>",[379,714,716],{"x":682,"y":715,"fill":249,"style":672},"176","+ owner line",[379,718,719],{"x":686,"y":704,"fill":410,"style":400},"fix flows through",[690,721],{"d":722,"stroke":405,"fill":693,"style":723},"M292 161 L326 161","stroke-width:2px;marker-end:url(#csl-wrap-arrow)",[379,725,728],{"x":381,"y":726,"fill":405,"style":727},"240","font-size:11px;text-anchor:middle","Wrapping keeps you on the upstream code path; copying freezes you on the version you copied",[730,731,377,732,357],"defs",{},[733,734,740,741,377],"marker",{"id":735,"viewBox":736,"refX":391,"refY":737,"markerWidth":738,"markerHeight":738,"orient":739},"csl-wrap-arrow","0 0 10 10","5","7","auto-start-reverse","\n      ",[690,742],{"d":743,"fill":405},"M0 0 L10 5 L0 10 z",[459,745,746,747,750,751,754],{},"The same logic applies to Docusaurus: swizzle with ",[68,748,749],{},"--wrap"," rather than ",[68,752,753],{},"--eject"," whenever the change is additive.",[32,756,758],{"id":757},"rung-4-package-shared-changes-as-a-plugin","Rung 4: Package Shared Changes as a Plugin",[14,760,761],{},"When two or more docs sites share a brand — a product docs site and a developer portal, say — the overrides and CSS belong in a Starlight plugin published as an internal package:",[61,763,765],{"className":494,"code":764,"language":496,"meta":66,"style":66},"\u002F\u002F packages\u002Fstarlight-acme\u002Findex.js\nexport default function acmeTheme() {\n  return {\n    name: 'starlight-acme',\n    hooks: {\n      'config:setup'({ config, updateConfig }) {\n        updateConfig({\n          customCss: [...(config.customCss ?? []), 'starlight-acme\u002Fbrand.css'],\n          components: {\n            Footer: 'starlight-acme\u002FFooter.astro',\n            ...config.components,   \u002F\u002F a site can still override locally\n          },\n        });\n      },\n    },\n  };\n}\n",[68,766,767,772,789,796,806,811,830,837,860,865,875,886,891,896,901,906,911],{"__ignoreMap":66},[71,768,769],{"class":73,"line":74},[71,770,771],{"class":77},"\u002F\u002F packages\u002Fstarlight-acme\u002Findex.js\n",[71,773,774,777,780,783,786],{"class":73,"line":81},[71,775,776],{"class":155},"export",[71,778,779],{"class":155}," default",[71,781,782],{"class":155}," function",[71,784,785],{"class":84}," acmeTheme",[71,787,788],{"class":88},"() {\n",[71,790,791,794],{"class":73,"line":92},[71,792,793],{"class":155},"  return",[71,795,89],{"class":88},[71,797,798,801,804],{"class":73,"line":121},[71,799,800],{"class":88},"    name: ",[71,802,803],{"class":102},"'starlight-acme'",[71,805,522],{"class":88},[71,807,808],{"class":73,"line":144},[71,809,810],{"class":88},"    hooks: {\n",[71,812,813,816,819,822,824,827],{"class":73,"line":161},[71,814,815],{"class":102},"      'config:setup'",[71,817,818],{"class":88},"({ ",[71,820,821],{"class":95},"config",[71,823,106],{"class":88},[71,825,826],{"class":95},"updateConfig",[71,828,829],{"class":88}," }) {\n",[71,831,832,835],{"class":73,"line":176},[71,833,834],{"class":84},"        updateConfig",[71,836,511],{"class":88},[71,838,839,842,845,848,851,854,857],{"class":73,"line":182},[71,840,841],{"class":88},"          customCss: [",[71,843,844],{"class":155},"...",[71,846,847],{"class":88},"(config.customCss ",[71,849,850],{"class":155},"??",[71,852,853],{"class":88}," []), ",[71,855,856],{"class":102},"'starlight-acme\u002Fbrand.css'",[71,858,859],{"class":88},"],\n",[71,861,862],{"class":73,"line":202},[71,863,864],{"class":88},"          components: {\n",[71,866,867,870,873],{"class":73,"line":215},[71,868,869],{"class":88},"            Footer: ",[71,871,872],{"class":102},"'starlight-acme\u002FFooter.astro'",[71,874,522],{"class":88},[71,876,877,880,883],{"class":73,"line":228},[71,878,879],{"class":155},"            ...",[71,881,882],{"class":88},"config.components,   ",[71,884,885],{"class":77},"\u002F\u002F a site can still override locally\n",[71,887,888],{"class":73,"line":241},[71,889,890],{"class":88},"          },\n",[71,892,893],{"class":73,"line":254},[71,894,895],{"class":88},"        });\n",[71,897,898],{"class":73,"line":267},[71,899,900],{"class":88},"      },\n",[71,902,903],{"class":73,"line":272},[71,904,905],{"class":88},"    },\n",[71,907,908],{"class":73,"line":288},[71,909,910],{"class":88},"  };\n",[71,912,913],{"class":73,"line":300},[71,914,179],{"class":88},[14,916,917,918,921,922,925],{},"Each site then lists ",[68,919,920],{},"plugins: [acmeTheme()]"," and gets the brand with one dependency. The spread of ",[68,923,924],{},"config.components"," last lets an individual site override a component the plugin also sets, which avoids forking the plugin for one site's exception.",[32,927,929],{"id":928},"measured-impact","Measured Impact",[14,931,932],{},"The restyle used all four rungs: 41 lines of token CSS, two overrides, one wrapper and, later, a plugin shared with a second site. Twelve months of upgrades were logged:",[934,935,936,952],"table",{},[937,938,939],"thead",{},[940,941,942,946,949],"tr",{},[943,944,945],"th",{},"Upgrade",[943,947,948],{},"Files changed in our code",[943,950,951],{},"Time to upgrade",[953,954,955,966,977,987,997,1007],"tbody",{},[940,956,957,961,963],{},[958,959,960],"td",{},"0.28 → 0.29",[958,962,369],{},[958,964,965],{},"10 min",[940,967,968,971,974],{},[958,969,970],{},"0.29 → 0.30 (props rename)",[958,972,973],{},"1 override",[958,975,976],{},"45 min",[940,978,979,982,984],{},[958,980,981],{},"0.30 → 0.31",[958,983,369],{},[958,985,986],{},"8 min",[940,988,989,992,994],{},[958,990,991],{},"0.31 → 0.32",[958,993,369],{},[958,995,996],{},"12 min",[940,998,999,1002,1004],{},[958,1000,1001],{},"0.32 → 0.33",[958,1003,369],{},[958,1005,1006],{},"9 min",[940,1008,1009,1012,1014],{},[958,1010,1011],{},"0.33 → 0.34",[958,1013,369],{},[958,1015,1016],{},"11 min",[346,1018,1019,1146],{},[349,1020,357,1024,357,1027,357,1030,357,1032],{"viewBox":637,"role":352,"ariaLabelledBy":1021,"xmlns":356},[1022,1023],"csl-up-title","csl-up-desc",[359,1025,1026],{"id":1022},"Upgrade minutes over twelve months, two strategies",[363,1028,1029],{"id":1023},"Bars for six upgrades. The token-and-wrap site took 10, 45, 8, 12, 9 and 11 minutes, 95 in total. A comparison site that had copied eight layout components took 90, 240, 60, 120, 75 and 150 minutes, 735 in total.",[367,1031],{"x":369,"y":369,"width":370,"height":649,"fill":372},[374,1033,377,1034,377,1037,377,1041,377,1047,377,1050,377,1054,377,1057,377,1062,377,1067,377,1070,377,1075,377,1078,377,1083,377,1086,377,1091,377,1096,377,1100,377,1104,377,1108,377,1112,377,1116,377,1122,377,1126,377,1130,377,1136,377,1138,377,1142,357],{"style":376},[379,1035,1036],{"x":381,"y":382,"fill":249,"style":383},"Minutes per upgrade: tokens and wrappers vs copied components",[73,1038],{"x1":1039,"y1":404,"x2":1040,"y2":404,"stroke":405,"style":395},"70","720",[367,1042],{"x":1043,"y":388,"width":1044,"height":1045,"fill":392,"stroke":394,"style":1046},"95","30","4","stroke-width:1px",[367,1048],{"x":662,"y":715,"width":1044,"height":663,"fill":677,"opacity":1049,"stroke":679,"style":1046},"0.3",[367,1051],{"x":1052,"y":670,"width":1044,"height":1053,"fill":392,"stroke":394,"style":1046},"200","20",[367,1055],{"x":1056,"y":450,"width":1044,"height":701,"fill":677,"opacity":1049,"stroke":679,"style":1046},"235",[367,1058],{"x":1059,"y":1060,"width":1044,"height":1061,"fill":392,"stroke":394,"style":1046},"305","227","3",[367,1063],{"x":1064,"y":1065,"width":1044,"height":1066,"fill":677,"opacity":1049,"stroke":679,"style":1046},"340","194","36",[367,1068],{"x":1069,"y":388,"width":1044,"height":1045,"fill":392,"stroke":394,"style":1046},"410",[367,1071],{"x":1072,"y":1073,"width":1044,"height":1074,"fill":677,"opacity":1049,"stroke":679,"style":1046},"445","158","72",[367,1076],{"x":1077,"y":388,"width":1044,"height":1045,"fill":392,"stroke":394,"style":1046},"515",[367,1079],{"x":1080,"y":1081,"width":1044,"height":1082,"fill":677,"opacity":1049,"stroke":679,"style":1046},"550","185","45",[367,1084],{"x":1085,"y":388,"width":1044,"height":1045,"fill":392,"stroke":394,"style":1046},"620",[367,1087],{"x":1088,"y":1089,"width":1044,"height":1090,"fill":677,"opacity":1049,"stroke":679,"style":1046},"655","140","90",[379,1092,1095],{"x":1093,"y":1094,"fill":405,"style":727},"127","248","0.29",[379,1097,1099],{"x":1098,"y":1094,"fill":405,"style":727},"232","0.30",[379,1101,1103],{"x":1102,"y":1094,"fill":405,"style":727},"337","0.31",[379,1105,1107],{"x":1106,"y":1094,"fill":405,"style":727},"442","0.32",[379,1109,1111],{"x":1110,"y":1094,"fill":405,"style":727},"547","0.33",[379,1113,1115],{"x":1114,"y":1094,"fill":405,"style":727},"652","0.34",[379,1117,1121],{"x":1118,"y":1119,"fill":687,"style":1120},"250","78","font-size:11px;font-weight:700;text-anchor:middle","240 min",[379,1123,1082],{"x":1124,"y":1125,"fill":410,"style":1120},"215","202",[367,1127],{"x":1128,"y":663,"width":1129,"height":1129,"fill":392,"stroke":394,"style":1046},"480","12",[379,1131,1135],{"x":1132,"y":1133,"fill":405,"style":1134},"498","64","font-size:11px","tokens + wrap: 95 min total",[367,1137],{"x":1128,"y":658,"width":1129,"height":1129,"fill":677,"opacity":1049,"stroke":679,"style":1046},[379,1139,1141],{"x":1132,"y":1140,"fill":405,"style":1134},"84","8 copied components: 735 min total",[379,1143,1145],{"x":381,"y":1144,"fill":405,"style":727},"272","Time-tracked upgrades on two production docs sites over the same twelve months",[459,1147,1148],{},"Roughly an eightfold difference in upgrade effort, almost all of it in merging changes into copied markup.",[14,1150,1151],{},"The comparison site, a sibling team's docs that had copied eight layout components into its repository, spent 735 minutes on the same six upgrades and skipped two releases entirely because the merge was too large to schedule. Skipped upgrades compound: the eventual jump covered three releases of breaking changes at once.",[32,1153,1155],{"id":1154},"testing-customisations-before-each-upgrade","Testing Customisations Before Each Upgrade",[14,1157,1158],{},"Low upgrade cost is not the same as zero risk. A props rename in an overridden component fails loudly at build time, which is fine; a visual regression in a wrapped component builds cleanly and ships. Three cheap checks catch nearly everything.",[14,1160,1161,1165,1166,1169,1170,1173],{},[1162,1163,1164],"strong",{},"Pin, then bump deliberately."," Pin ",[68,1167,1168],{},"@astrojs\u002Fstarlight"," to an exact version in ",[68,1171,1172],{},"package.json"," and let a dependency bot open one pull request per release. Each pull request gets a preview deploy, so the upgrade is reviewed on a real URL before anyone merges it.",[14,1175,1176,1179,1180,1184],{},[1162,1177,1178],{},"Screenshot the four templates."," Capture the homepage, a long guide, a page with tabs and asides, and the 404 page in both themes, and diff them against the production build. On this site that is eight screenshots and about forty seconds in CI using the approach from ",[21,1181,1183],{"href":1182},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys\u002F","Visual Regression Testing on Preview Deploys",". The 0.30 props rename showed up there first, as a footer missing its \"last updated\" line.",[14,1186,1187,1190,1191,1194],{},[1162,1188,1189],{},"Run the accessibility pass on overrides only."," An override can silently drop an ",[68,1192,1193],{},"aria-label"," that the original carried. Running axe-core against the pages that render your overridden components — not the whole site — keeps the check under ten seconds and focused on the code you own.",[14,1196,1197,1200,1201,1204],{},[1162,1198,1199],{},"Read the changelog for your override list."," Keep the list of overridden component names in a comment at the top of ",[68,1202,1203],{},"astro.config.mjs",". When a release note mentions one of those names, that is the pull request to review carefully; the rest can be merged on a green preview.",[14,1206,1207],{},"Together these turned upgrades into a routine the on-call writer could merge, rather than a task that waited for an engineer with Astro experience.",[32,1209,1211],{"id":1210},"pitfalls-rollback","Pitfalls & Rollback",[37,1213,1214,1224,1237,1247,1256],{},[40,1215,1216,1219,1220,1223],{},[1162,1217,1218],{},"Styling by selector instead of token."," CSS such as ",[68,1221,1222],{},".sidebar-content a { color: purple }"," depends on class names that are not a public API. Use the documented custom properties; they are stable across releases.",[40,1225,1226,1232,1233,1236],{},[1162,1227,1228,1229,1231],{},"Overriding ",[68,1230,490],{}," to add one tag."," Use the ",[68,1234,1235],{},"head"," config option for extra meta, link or script tags instead of replacing the whole component.",[40,1238,1239,1242,1243,1246],{},[1162,1240,1241],{},"Forgetting dark mode."," Token blocks need a ",[68,1244,1245],{},"[data-theme='dark']"," variant; otherwise the brand accent drops below AA contrast on dark backgrounds.",[40,1248,1249,1252,1253,1255],{},[1162,1250,1251],{},"Plugins that swallow local overrides."," Spread the site's own ",[68,1254,924],{}," after the plugin's so a site can still override locally.",[40,1257,1258,1261,1262,1265,1266,1269],{},[1162,1259,1260],{},"Rollback:"," every rung is additive configuration. Removing a line from ",[68,1263,1264],{},"components",", deleting the ",[68,1267,1268],{},"customCss"," entry or removing the plugin restores Starlight's default for that piece without touching content.",[32,1271,1273],{"id":1272},"conclusion","Conclusion",[14,1275,1276],{},"Branding Starlight is a configuration exercise when approached in order: tokens for colour, type and width; named overrides for structural changes; wrappers for additions; a plugin once more than one site shares the result. The site that followed that order upgraded six times in a year for 95 minutes of total effort. The site that copied components spent nearly eight times as long and fell behind. Choose the lowest rung that meets the design, and treat any urge to copy Starlight's source as a sign that the change belongs one rung down.",[32,1278,1280],{"id":1279},"faq","FAQ",[1282,1283,1285],"h3",{"id":1284},"can-i-change-starlights-colours-without-overriding-components","Can I change Starlight's colours without overriding components?",[14,1287,1288],{},"Yes. Starlight's theme is driven by CSS custom properties such as --sl-color-accent and --sl-font. Set them in a stylesheet listed under customCss, separately for light and dark mode, and every component picks them up.",[1282,1290,1292],{"id":1291},"what-happens-to-my-component-overrides-when-starlight-upgrades","What happens to my component overrides when Starlight upgrades?",[14,1294,1295],{},"Overrides receive the same props as the built-in component, so they keep working unless a release changes those props. Breaking prop changes are listed in the changelog. In a year of upgrades on one site, one of six overrides needed a change.",[1282,1297,1299],{"id":1298},"can-an-override-reuse-the-original-component","Can an override reuse the original component?",[14,1301,1302],{},"Yes. Import the default from @astrojs\u002Fstarlight\u002Fcomponents and render it inside your own component. This wrapping pattern lets you add content around the original without copying its markup.",[1282,1304,1306],{"id":1305},"should-i-use-a-starlight-plugin-or-a-component-override","Should I use a Starlight plugin or a component override?",[14,1308,1309],{},"Use an override for one site's layout change. Use a plugin when several sites need the same change or when you need to modify configuration, add routes or register several overrides together.",[32,1311,1313],{"id":1312},"related","Related",[37,1315,1316,1325,1330,1337,1344],{},[40,1317,1318,1321,1322,1324],{},[1162,1319,1320],{},"Parent:"," ",[21,1323,29],{"href":28}," — how customisation compares across frameworks.",[40,1326,1327,1329],{},[21,1328,24],{"href":23}," — the port this restyle came from.",[40,1331,1332,1336],{},[21,1333,1335],{"href":1334},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content\u002F","MDX vs Markdoc for Docs Content"," — customising content components rather than layout.",[40,1338,1339,1343],{},[21,1340,1342],{"href":1341},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fmetric-matched-fallback-fonts-with-size-adjust\u002F","Metric-Matched Fallback Fonts with size-adjust"," — keeping a brand font from shifting layout.",[40,1345,1346,1350],{},[21,1347,1349],{"href":1348},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors\u002F","Shortcodes vs Components for Docs Authors"," — the same trade-off in Eleventy.",[1352,1353,1354],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":66,"searchDepth":81,"depth":81,"links":1356},[1357,1358,1359,1360,1361,1362,1363,1364,1365,1366,1372],{"id":34,"depth":81,"text":35},{"id":55,"depth":81,"text":56},{"id":464,"depth":81,"text":465},{"id":567,"depth":81,"text":568},{"id":757,"depth":81,"text":758},{"id":928,"depth":81,"text":929},{"id":1154,"depth":81,"text":1155},{"id":1210,"depth":81,"text":1211},{"id":1272,"depth":81,"text":1273},{"id":1279,"depth":81,"text":1280,"children":1367},[1368,1369,1370,1371],{"id":1284,"depth":92,"text":1285},{"id":1291,"depth":92,"text":1292},{"id":1298,"depth":92,"text":1299},{"id":1305,"depth":92,"text":1306},{"id":1312,"depth":81,"text":1313},[1374,1377,1380,1381],{"name":1375,"item":1376},"Home","\u002F",{"name":1378,"item":1379},"Choosing the Right Static Site Generator for Production","\u002Fchoosing-the-right-static-site-generator-for-production\u002F",{"name":29,"item":28},{"name":5,"item":1382},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcustomizing-starlight-without-forking-the-theme\u002F","2026-09-18","Brand a Starlight docs site with CSS custom properties, component overrides and plugins so every upgrade stays a one-line version bump instead of a merge.","md",[1387,1388,1389,1390],{"q":1285,"a":1288},{"q":1292,"a":1295},{"q":1299,"a":1302},{"q":1306,"a":1309},{},true,"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcustomizing-starlight-without-forking-the-theme",{"title":5,"description":1384},"choosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcustomizing-starlight-without-forking-the-theme\u002Findex","article","CMGjfCDBWQrOQfIck1hJftUpVBmzViklt-u_5DOi7y8",[1399,1402,1405,1408,1411,1413,1416,1417,1419,1421,1423,1426,1429,1432,1435,1438,1441,1444,1447,1450,1452,1455,1458,1461,1464,1467,1470,1473,1476,1479,1482,1485,1488,1491,1494,1497,1500,1503,1506,1509,1512,1515,1518,1521,1524,1527,1530,1533,1536,1539,1542,1545,1548,1551,1554,1557,1560,1563,1566,1569,1572,1575,1578,1581,1584,1587,1590,1593,1596,1599,1601,1604,1607,1610,1613,1616,1619,1622,1625,1628,1631,1634,1637,1640,1643,1646,1649,1652,1655,1658,1661,1664,1667,1670,1673,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,1852,1855,1858,1860,1863,1866,1869,1872,1875,1878,1881,1884,1887,1890,1893,1896,1899,1902,1905,1908,1911,1914,1917,1920,1923,1926,1929,1932,1935],{"path":1400,"title":1401},"\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":1403,"title":1404},"\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":1406,"title":1407},"\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":1409,"title":1410},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1412,"title":1349},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors",{"path":1414,"title":1415},"\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":1393,"title":5},{"path":1418,"title":24},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fdocusaurus-vs-starlight-for-product-documentation",{"path":1420,"title":29},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress",{"path":1422,"title":1335},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content",{"path":1424,"title":1425},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1427,"title":1428},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1430,"title":1431},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1433,"title":1434},"\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":1436,"title":1437},"\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":1439,"title":1440},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1442,"title":1443},"\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":1445,"title":1446},"\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":1448,"title":1449},"\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":1451,"title":1378},"\u002Fchoosing-the-right-static-site-generator-for-production",{"path":1453,"title":1454},"\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":1456,"title":1457},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1459,"title":1460},"\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":1462,"title":1463},"\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":1465,"title":1466},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1468,"title":1469},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1471,"title":1472},"\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":1474,"title":1475},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1477,"title":1478},"\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":1480,"title":1481},"\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":1483,"title":1484},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1486,"title":1487},"\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":1489,"title":1490},"\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":1492,"title":1493},"\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":1495,"title":1496},"\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":1498,"title":1499},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1501,"title":1502},"\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":1504,"title":1505},"\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":1507,"title":1508},"\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":1510,"title":1511},"\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":1513,"title":1514},"\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":1516,"title":1517},"\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":1519,"title":1520},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1522,"title":1523},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1525,"title":1526},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1528,"title":1529},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1531,"title":1532},"\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":1534,"title":1535},"\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":1537,"title":1538},"\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":1540,"title":1541},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1543,"title":1544},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1546,"title":1547},"\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":1549,"title":1550},"\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":1552,"title":1553},"\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":1555,"title":1556},"\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":1558,"title":1559},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1561,"title":1562},"\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":1564,"title":1565},"\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":1567,"title":1568},"\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":1570,"title":1571},"\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":1573,"title":1574},"\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":1576,"title":1577},"\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":1579,"title":1580},"\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":1582,"title":1583},"\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":1585,"title":1586},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1588,"title":1589},"\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":1591,"title":1592},"\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":1594,"title":1595},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1597,"title":1598},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1600,"title":1342},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fmetric-matched-fallback-fonts-with-size-adjust",{"path":1602,"title":1603},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1605,"title":1606},"\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":1608,"title":1609},"\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":1611,"title":1612},"\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":1614,"title":1615},"\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":1617,"title":1618},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1620,"title":1621},"\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":1623,"title":1624},"\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":1626,"title":1627},"\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":1629,"title":1630},"\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":1632,"title":1633},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1635,"title":1636},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1638,"title":1639},"\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":1641,"title":1642},"\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":1644,"title":1645},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1647,"title":1648},"\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":1650,"title":1651},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1653,"title":1654},"\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":1656,"title":1657},"\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":1659,"title":1660},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1662,"title":1663},"\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":1665,"title":1666},"\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":1668,"title":1669},"\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":1671,"title":1672},"\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":1674,"title":1675},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1677,"title":1678},"\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":1680,"title":1681},"\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":1683,"title":1684},"\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":1686,"title":1687},"\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":1689,"title":1690},"\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":1692,"title":1693},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1695,"title":1696},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1698,"title":1699},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1701,"title":1702},"\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":1704,"title":1705},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1707,"title":1708},"\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":1710,"title":1711},"\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":1713,"title":1714},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1716,"title":1717},"\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":1719,"title":1720},"\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":1722,"title":1723},"\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":1725,"title":1726},"\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":1728,"title":1729},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1731,"title":1732},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1734,"title":1735},"\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":1737,"title":1738},"\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":1740,"title":1741},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1743,"title":1744},"\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":1746,"title":1747},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1749,"title":1750},"\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":1752,"title":1753},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1755,"title":1756},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1758,"title":1759},"\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":1761,"title":1762},"\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":1764,"title":1765},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1767,"title":1768},"\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":1770,"title":1771},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1773,"title":1774},"\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":1776,"title":1777},"\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":1779,"title":1780},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1782,"title":1783},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1785,"title":1786},"\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":1788,"title":1789},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1791,"title":1792},"\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":1794,"title":1795},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1797,"title":1798},"\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":1800,"title":1801},"\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":1803,"title":1804},"\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":1806,"title":1807},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1809,"title":1810},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1812,"title":1813},"\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":1815,"title":1816},"\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":1818,"title":1819},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1821,"title":1822},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1824,"title":1825},"\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":1827,"title":1828},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1830,"title":1831},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1833,"title":1834},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1836,"title":1837},"\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":1839,"title":1840},"\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":1842,"title":1843},"\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":1845,"title":1846},"\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":1848,"title":1849},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1851,"title":52},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests",{"path":1853,"title":1854},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1856,"title":1857},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1859,"title":1183},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys",{"path":1861,"title":1862},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1864,"title":1865},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":1867,"title":1868},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1870,"title":1871},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1873,"title":1874},"\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":1876,"title":1877},"\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":1879,"title":1880},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1882,"title":1883},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1885,"title":1886},"\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":1888,"title":1889},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1891,"title":1892},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1894,"title":1895},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1897,"title":1898},"\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":1900,"title":1901},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1903,"title":1904},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1906,"title":1907},"\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":1909,"title":1910},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1912,"title":1913},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1915,"title":1916},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1918,"title":1919},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1921,"title":1922},"\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":1924,"title":1925},"\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":1927,"title":1928},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1930,"title":1931},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1933,"title":1934},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1936,"title":1937},"\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",1789722847081]