[{"data":1,"prerenderedAt":2500},["ShallowReactive",2],{"page:\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ftailwind-v4-in-astro-without-postcss-plugins":3,"all-docs-nav":1349,"filed:\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ftailwind-v4-in-astro-without-postcss-plugins":2491},{"id":4,"title":5,"body":6,"breadcrumb":1325,"dateModified":1335,"datePublished":1335,"description":1336,"extension":1337,"faq":1338,"meta":1343,"navigation":148,"path":1344,"seo":1345,"slug":12,"stem":1346,"type":1347,"__hash__":1348},"content\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ftailwind-v4-in-astro-without-postcss-plugins\u002Findex.md","Tailwind v4 in Astro Without PostCSS Plugins",{"type":7,"value":8,"toc":1305},"minimark",[9,13,26,42,47,68,72,95,184,191,195,198,220,241,374,378,384,393,396,542,580,584,587,680,683,773,908,912,923,927,943,953,957,971,975,1081,1177,1180,1184,1222,1226,1229,1233,1238,1241,1245,1248,1252,1255,1259,1262,1266,1301],[10,11,5],"h1",{"id":12},"tailwind-v4-in-astro-without-postcss-plugins",[14,15,16,17,21,22,25],"p",{},"Tailwind 4 rewrote the engine and the configuration model. It is a Vite plugin rather than a PostCSS plugin, its configuration lives in CSS rather than ",[18,19,20],"code",{},"tailwind.config.js",", and it detects sources automatically. For Astro sites, that means the ",[18,23,24],{},"@astrojs\u002Ftailwind"," integration and the PostCSS pipeline it set up are no longer needed: Astro already runs Vite, and Tailwind plugs straight into it.",[14,27,28,29,31,32,35,36,41],{},"This guide migrates a 900-page Astro 5 documentation and marketing site from Tailwind 3.4 with ",[18,30,24],{}," to Tailwind 4 with ",[18,33,34],{},"@tailwindcss\u002Fvite",", converts the JavaScript config to CSS, keeps dark mode working with the site's data-attribute toggle, and measures the output and build time before and after. It belongs to ",[37,38,40],"a",{"href":39},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002F","CSS and JavaScript Asset Optimization",".",[43,44,46],"h2",{"id":45},"prerequisites","Prerequisites",[48,49,50,54,57],"ul",{},[51,52,53],"li",{},"Astro 5 (Astro 4.x also works with the Vite plugin).",[51,55,56],{},"A clean git tree and the current build's CSS output saved for comparison.",[51,58,59,60,63,64,67],{},"Browsers targeted by Tailwind 4: it relies on cascade layers, ",[18,61,62],{},"@property"," and ",[18,65,66],{},"color-mix()",", which need Safari 16.4+, Chrome 111+ and Firefox 128+. Check analytics first; on this site, older browsers were 0.4% of visits.",[43,69,71],{"id":70},"step-1-swap-the-integration-for-the-vite-plugin","Step 1: Swap the Integration for the Vite Plugin",[73,74,79],"pre",{"className":75,"code":76,"language":77,"meta":78,"style":78},"language-sh shiki shiki-themes github-light github-dark","npm uninstall @astrojs\u002Ftailwind autoprefixer postcss\nnpm install tailwindcss@4 @tailwindcss\u002Fvite@4\n","sh","",[18,80,81,89],{"__ignoreMap":78},[82,83,86],"span",{"class":84,"line":85},"line",1,[82,87,88],{},"npm uninstall @astrojs\u002Ftailwind autoprefixer postcss\n",[82,90,92],{"class":84,"line":91},2,[82,93,94],{},"npm install tailwindcss@4 @tailwindcss\u002Fvite@4\n",[73,96,100],{"className":97,"code":98,"language":99,"meta":78,"style":78},"language-js shiki shiki-themes github-light github-dark","\u002F\u002F astro.config.mjs\nimport { defineConfig } from 'astro\u002Fconfig';\nimport tailwindcss from '@tailwindcss\u002Fvite';\n\nexport default defineConfig({\n  vite: { plugins: [tailwindcss()] },\n});\n","js",[18,101,102,108,128,143,150,166,178],{"__ignoreMap":78},[82,103,104],{"class":84,"line":85},[82,105,107],{"class":106},"sJ8bj","\u002F\u002F astro.config.mjs\n",[82,109,110,114,118,121,125],{"class":84,"line":91},[82,111,113],{"class":112},"szBVR","import",[82,115,117],{"class":116},"sVt8B"," { defineConfig } ",[82,119,120],{"class":112},"from",[82,122,124],{"class":123},"sZZnC"," 'astro\u002Fconfig'",[82,126,127],{"class":116},";\n",[82,129,131,133,136,138,141],{"class":84,"line":130},3,[82,132,113],{"class":112},[82,134,135],{"class":116}," tailwindcss ",[82,137,120],{"class":112},[82,139,140],{"class":123}," '@tailwindcss\u002Fvite'",[82,142,127],{"class":116},[82,144,146],{"class":84,"line":145},4,[82,147,149],{"emptyLinePlaceholder":148},true,"\n",[82,151,153,156,159,163],{"class":84,"line":152},5,[82,154,155],{"class":112},"export",[82,157,158],{"class":112}," default",[82,160,162],{"class":161},"sScJk"," defineConfig",[82,164,165],{"class":116},"({\n",[82,167,169,172,175],{"class":84,"line":168},6,[82,170,171],{"class":116},"  vite: { plugins: [",[82,173,174],{"class":161},"tailwindcss",[82,176,177],{"class":116},"()] },\n",[82,179,181],{"class":84,"line":180},7,[82,182,183],{"class":116},"});\n",[14,185,186,187,190],{},"Remove ",[18,188,189],{},"postcss.config.cjs"," if Tailwind and autoprefixer were its only plugins — Tailwind 4 handles vendor prefixes through Lightning CSS internally.",[43,192,194],{"id":193},"step-2-import-tailwind-in-css","Step 2: Import Tailwind in CSS",[14,196,197],{},"The integration had injected Tailwind's base styles automatically. Now a global stylesheet imports it, and the base layout imports that stylesheet:",[73,199,203],{"className":200,"code":201,"language":202,"meta":78,"style":78},"language-css shiki shiki-themes github-light github-dark","\u002F* src\u002Fstyles\u002Fglobal.css *\u002F\n@import 'tailwindcss';\n","css",[18,204,205,210],{"__ignoreMap":78},[82,206,207],{"class":84,"line":85},[82,208,209],{"class":106},"\u002F* src\u002Fstyles\u002Fglobal.css *\u002F\n",[82,211,212,215,218],{"class":84,"line":91},[82,213,214],{"class":112},"@import",[82,216,217],{"class":123}," 'tailwindcss'",[82,219,127],{"class":116},[73,221,225],{"className":222,"code":223,"language":224,"meta":78,"style":78},"language-astro shiki shiki-themes github-light github-dark","---\nimport '..\u002Fstyles\u002Fglobal.css';\n---\n","astro",[18,226,227,232,237],{"__ignoreMap":78},[82,228,229],{"class":84,"line":85},[82,230,231],{},"---\n",[82,233,234],{"class":84,"line":91},[82,235,236],{},"import '..\u002Fstyles\u002Fglobal.css';\n",[82,238,239],{"class":84,"line":130},[82,240,231],{},[242,243,244,370],"figure",{},[245,246,253,254,253,258,253,262,253,269],"svg",{"viewBox":247,"role":248,"ariaLabelledBy":249,"xmlns":252},"0 0 760 245","img",[250,251],"tw4-setup-title","tw4-setup-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[255,256,257],"title",{"id":250},"Tailwind 3 with the Astro integration compared with Tailwind 4 on the Vite plugin",[259,260,261],"desc",{"id":251},"Two panels. Tailwind 3 used the astrojs tailwind integration, a PostCSS config with autoprefixer, a tailwind.config.js with content paths, theme and plugins, and injected base styles. Tailwind 4 uses the tailwindcss vite plugin in astro.config, a global CSS file importing tailwindcss, theme and sources declared in CSS, and automatic source detection.",[263,264],"rect",{"x":265,"y":265,"width":266,"height":267,"fill":268},"0","760","245","#ffffff",[270,271,273,274,273,284,273,291,273,294,273,297,273,300,273,306,273,309,273,311,273,313,273,315,273,323,273,329,273,334,273,337,273,340,273,344,273,349,273,354,273,358,273,361,273,364,273,367,253],"g",{"style":272},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[263,275],{"x":276,"y":277,"width":278,"height":279,"rx":280,"fill":281,"stroke":282,"style":283},"20.0","58.0","350.0","171.0","10","#f8fafc","#d9e2ef","stroke-width:1.5px",[285,286],"circle",{"cx":287,"cy":288,"r":289,"fill":290,"stroke":290,"style":283},"40.0","103.0","2.5","#1982c4",[285,292],{"cx":287,"cy":293,"r":289,"fill":290,"stroke":290,"style":283},"125.0",[285,295],{"cx":287,"cy":296,"r":289,"fill":290,"stroke":290,"style":283},"146.9",[285,298],{"cx":287,"cy":299,"r":289,"fill":290,"stroke":290,"style":283},"168.9",[263,301],{"x":302,"y":277,"width":278,"height":279,"rx":280,"fill":303,"opacity":304,"stroke":305,"style":283},"390.0","#8ac926","0.2","#5a8a16",[285,307],{"cx":308,"cy":288,"r":289,"fill":303,"stroke":305,"style":283},"410.0",[285,310],{"cx":308,"cy":293,"r":289,"fill":303,"stroke":305,"style":283},[285,312],{"cx":308,"cy":296,"r":289,"fill":303,"stroke":305,"style":283},[285,314],{"cx":308,"cy":299,"r":289,"fill":303,"stroke":305,"style":283},[316,317,322],"text",{"x":318,"y":319,"fill":320,"style":321},"380.0","30.0","#1f2937","font-size:16px;text-anchor:middle;font-weight:700","The two setups side by side",[316,324,328],{"x":325,"y":326,"fill":320,"style":327},"34.0","83.5","font-size:13.5px;text-anchor:start;font-weight:700","Tailwind 3 + integration",[316,330,24],{"x":331,"y":332,"fill":320,"style":333},"50.0","107.0","font-size:11.5px;text-anchor:start",[316,335,189],{"x":331,"y":336,"fill":320,"style":333},"129.0",[316,338,20],{"x":331,"y":339,"fill":320,"style":333},"150.9",[316,341,343],{"x":331,"y":342,"fill":320,"style":333},"172.9","content paths listed",[316,345,348],{"x":325,"y":346,"fill":320,"style":347},"215.0","font-size:12px;text-anchor:start;font-weight:700","3 config files",[316,350,353],{"x":351,"y":326,"fill":352,"style":327},"404.0","#3f6410","Tailwind 4 + Vite plugin",[316,355,357],{"x":356,"y":332,"fill":320,"style":333},"420.0","@tailwindcss\u002Fvite in astro.config",[316,359,360],{"x":356,"y":336,"fill":320,"style":333},"global.css with @import",[316,362,363],{"x":356,"y":339,"fill":320,"style":333},"@theme and @source in CSS",[316,365,366],{"x":356,"y":342,"fill":320,"style":333},"automatic source detection",[316,368,369],{"x":351,"y":346,"fill":320,"style":347},"1 CSS file",[371,372,373],"figcaption",{},"Three config files became one CSS file and one line in the Astro config.",[43,375,377],{"id":376},"step-3-move-the-config-into-css","Step 3: Move the Config Into CSS",[14,379,380,381,383],{},"The old ",[18,382,20],{}," had content paths, a theme extension, one plugin and dark mode set to a class strategy. The official upgrade tool converts most of it:",[73,385,387],{"className":75,"code":386,"language":77,"meta":78,"style":78},"npx @tailwindcss\u002Fupgrade\n",[18,388,389],{"__ignoreMap":78},[82,390,391],{"class":84,"line":85},[82,392,386],{},[14,394,395],{},"It rewrote templates for renamed utilities and produced a CSS config. After tidying, the result:",[73,397,399],{"className":200,"code":398,"language":202,"meta":78,"style":78},"@import 'tailwindcss';\n@plugin '@tailwindcss\u002Ftypography';\n\n@source '..\u002Fcontent\u002Fexternal';\n@source not '..\u002Fdata';\n\n@custom-variant dark (&:where([data-theme=dark], [data-theme=dark] *));\n\n@theme {\n  --font-sans: 'Inter Variable', system-ui, sans-serif;\n  --color-brand-50: oklch(0.97 0.02 250);\n  --color-brand-500: oklch(0.58 0.15 250);\n  --color-brand-700: oklch(0.45 0.14 250);\n  --breakpoint-3xl: 112rem;\n}\n",[18,400,401,409,417,421,429,436,440,448,453,462,480,498,514,530,536],{"__ignoreMap":78},[82,402,403,405,407],{"class":84,"line":85},[82,404,214],{"class":112},[82,406,217],{"class":123},[82,408,127],{"class":116},[82,410,411,414],{"class":84,"line":91},[82,412,413],{"class":112},"@plugin",[82,415,416],{"class":116}," '@tailwindcss\u002Ftypography';\n",[82,418,419],{"class":84,"line":130},[82,420,149],{"emptyLinePlaceholder":148},[82,422,423,426],{"class":84,"line":145},[82,424,425],{"class":112},"@source",[82,427,428],{"class":116}," '..\u002Fcontent\u002Fexternal';\n",[82,430,431,433],{"class":84,"line":152},[82,432,425],{"class":112},[82,434,435],{"class":116}," not '..\u002Fdata';\n",[82,437,438],{"class":84,"line":168},[82,439,149],{"emptyLinePlaceholder":148},[82,441,442,445],{"class":84,"line":180},[82,443,444],{"class":112},"@custom-variant",[82,446,447],{"class":116}," dark (&:where([data-theme=dark], [data-theme=dark] *));\n",[82,449,451],{"class":84,"line":450},8,[82,452,149],{"emptyLinePlaceholder":148},[82,454,456,459],{"class":84,"line":455},9,[82,457,458],{"class":112},"@theme",[82,460,461],{"class":116}," {\n",[82,463,465,468,472,475,478],{"class":84,"line":464},10,[82,466,467],{"class":116},"  --font-sans: 'Inter Variable', ",[82,469,471],{"class":470},"s9eBZ","system-ui",[82,473,474],{"class":116},", ",[82,476,477],{"class":470},"sans-serif",[82,479,127],{"class":116},[82,481,483,486,489,492,495],{"class":84,"line":482},11,[82,484,485],{"class":116},"  --color-brand-50: oklch(0",[82,487,488],{"class":161},".97",[82,490,491],{"class":116}," 0",[82,493,494],{"class":161},".02",[82,496,497],{"class":116}," 250);\n",[82,499,501,504,507,509,512],{"class":84,"line":500},12,[82,502,503],{"class":116},"  --color-brand-500: oklch(0",[82,505,506],{"class":161},".58",[82,508,491],{"class":116},[82,510,511],{"class":161},".15",[82,513,497],{"class":116},[82,515,517,520,523,525,528],{"class":84,"line":516},13,[82,518,519],{"class":116},"  --color-brand-700: oklch(0",[82,521,522],{"class":161},".45",[82,524,491],{"class":116},[82,526,527],{"class":161},".14",[82,529,497],{"class":116},[82,531,533],{"class":84,"line":532},14,[82,534,535],{"class":116},"  --breakpoint-3xl: 112rem;\n",[82,537,539],{"class":84,"line":538},15,[82,540,541],{"class":116},"}\n",[48,543,544,549,558,572],{},[51,545,546,548],{},[18,547,413],{}," loads the typography plugin, which works with Tailwind 4.",[51,550,551,553,554,41],{},[18,552,425],{}," adds content outside automatic detection (a gitignored external content folder) and excludes data files that would otherwise produce accidental utilities, as covered in ",[37,555,557],{"href":556},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fkeeping-tailwind-css-output-small-on-static-sites\u002F","Keeping Tailwind CSS Output Small on Static Sites",[51,559,560,563,564,567,568,571],{},[18,561,562],{},"@custom-variant dark"," makes ",[18,565,566],{},"dark:"," utilities follow the site's ",[18,569,570],{},"data-theme"," attribute instead of the OS preference, matching its existing toggle.",[51,573,574,576,577,41],{},[18,575,458],{}," defines tokens as CSS variables, which also makes them available to plain CSS and inline SVG styles as ",[18,578,579],{},"var(--color-brand-500)",[43,581,583],{"id":582},"step-4-fix-the-renamed-and-changed-utilities","Step 4: Fix the Renamed and Changed Utilities",[14,585,586],{},"The upgrade tool handled most renames, but the visual diff of 40 key pages found four changes it could not:",[588,589,590,606],"table",{},[591,592,593],"thead",{},[594,595,596,600,603],"tr",{},[597,598,599],"th",{},"Change in Tailwind 4",[597,601,602],{},"Effect on this site",[597,604,605],{},"Fix",[607,608,609,633,651,662],"tbody",{},[594,610,611,619,626],{},[612,613,614,615,618],"td",{},"Default border colour is ",[18,616,617],{},"currentColor"," (was gray-200)",[612,620,621,622,625],{},"Bare ",[18,623,624],{},"border"," turned dark",[612,627,628,629,632],{},"Add ",[18,630,631],{},"border-gray-200"," where needed, or set a base style",[594,634,635,641,644],{},[612,636,637,640],{},[18,638,639],{},"ring"," defaults to 1 px (was 3 px)",[612,642,643],{},"Focus rings looked thin",[612,645,646,647,650],{},"Use ",[18,648,649],{},"ring-3"," explicitly",[594,652,653,656,659],{},[612,654,655],{},"Placeholder colour uses current text colour at 50%",[612,657,658],{},"Placeholders darker",[612,660,661],{},"Set placeholder colour in base",[594,663,664,670,673],{},[612,665,666,669],{},[18,667,668],{},"space-x\u002Fy"," selector changed",[612,671,672],{},"Spacing off on items with hidden siblings",[612,674,675,676,679],{},"Switch to ",[18,677,678],{},"gap"," with flex or grid",[14,681,682],{},"A base layer restored the old border and placeholder defaults for the whole site in five lines, which was quicker than editing hundreds of elements:",[73,684,686],{"className":200,"code":685,"language":202,"meta":78,"style":78},"@layer base {\n  *, ::before, ::after { border-color: var(--color-gray-200, currentColor); }\n  input::placeholder, textarea::placeholder { color: var(--color-gray-400); }\n}\n",[18,687,688,696,738,769],{"__ignoreMap":78},[82,689,690,693],{"class":84,"line":85},[82,691,692],{"class":112},"@layer",[82,694,695],{"class":116}," base {\n",[82,697,698,701,703,706,708,711,714,718,721,724,727,731,733,735],{"class":84,"line":91},[82,699,700],{"class":470},"  *",[82,702,474],{"class":116},[82,704,705],{"class":161},"::before",[82,707,474],{"class":116},[82,709,710],{"class":161},"::after",[82,712,713],{"class":116}," { ",[82,715,717],{"class":716},"sj4cs","border-color",[82,719,720],{"class":116},": ",[82,722,723],{"class":716},"var",[82,725,726],{"class":116},"(",[82,728,730],{"class":729},"s4XuR","--color-gray-200",[82,732,474],{"class":116},[82,734,617],{"class":716},[82,736,737],{"class":116},"); }\n",[82,739,740,743,746,748,751,753,755,758,760,762,764,767],{"class":84,"line":130},[82,741,742],{"class":470},"  input",[82,744,745],{"class":161},"::placeholder",[82,747,474],{"class":116},[82,749,750],{"class":470},"textarea",[82,752,745],{"class":161},[82,754,713],{"class":116},[82,756,757],{"class":716},"color",[82,759,720],{"class":116},[82,761,723],{"class":716},[82,763,726],{"class":116},[82,765,766],{"class":729},"--color-gray-400",[82,768,737],{"class":116},[82,770,771],{"class":84,"line":145},[82,772,541],{"class":116},[242,774,775,905],{},[245,776,253,781,253,784,253,787,253,790,253,890],{"viewBox":777,"role":248,"ariaLabelledBy":778,"xmlns":252},"0 0 760 154",[779,780],"tw4-steps-title","tw4-steps-desc",[255,782,783],{"id":779},"Steps of the Tailwind 3 to Tailwind 4 migration in Astro",[259,785,786],{"id":780},"Five steps. Swap the Astro integration for the Vite plugin. Import tailwindcss in a global stylesheet. Run the upgrade tool to move config into CSS and rename utilities. Compare 40 key pages visually and fix default changes for borders, rings and placeholders. Compare built CSS size and run the missing-class check.",[263,788],{"x":265,"y":265,"width":266,"height":789,"fill":268},"154",[270,791,273,792,273,799,273,802,273,809,273,813,273,816,273,822,273,825,273,828,273,831,273,834,273,840,273,845,273,849,273,854,273,858,273,862,273,866,273,870,273,874,273,877,273,880,273,884,273,887,253],{"style":272},[263,793],{"x":276,"y":794,"width":795,"height":796,"rx":797,"fill":290,"opacity":798,"stroke":290,"style":283},"64.0","116.8","74.1","8","0.14",[263,800],{"x":801,"y":794,"width":795,"height":796,"rx":797,"fill":290,"opacity":798,"stroke":290,"style":283},"170.8",[803,804],"path",{"d":805,"fill":806,"stroke":807,"style":808},"M138.8 101.1 L166.8 101.1","none","#556071","stroke-width:2px;marker-end:url(#tw4-steps-arrow)",[263,810],{"x":811,"y":794,"width":795,"height":796,"rx":797,"fill":812,"opacity":798,"stroke":812,"style":283},"321.6","#6a4c93",[803,814],{"d":815,"fill":806,"stroke":807,"style":808},"M289.6 101.1 L317.6 101.1",[263,817],{"x":818,"y":794,"width":795,"height":796,"rx":797,"fill":819,"opacity":820,"stroke":821,"style":283},"472.4","#ffca3a","0.24","#a97b00",[803,823],{"d":824,"fill":806,"stroke":807,"style":808},"M440.4 101.1 L468.4 101.1",[263,826],{"x":827,"y":794,"width":795,"height":796,"rx":797,"fill":303,"opacity":304,"stroke":305,"style":283},"623.2",[803,829],{"d":830,"fill":806,"stroke":807,"style":808},"M591.2 101.1 L619.2 101.1",[316,832,833],{"x":318,"y":319,"fill":320,"style":321},"The migration in order",[316,835,839],{"x":836,"y":837,"fill":320,"style":838},"78.4","91.7","font-size:13px;text-anchor:middle;font-weight:700","Vite plugin",[316,841,844],{"x":836,"y":842,"fill":807,"style":843},"108.6","font-size:11px;text-anchor:middle","replace",[316,846,848],{"x":836,"y":847,"fill":807,"style":843},"122.9","integration",[316,850,853],{"x":851,"y":852,"fill":320,"style":838},"229.2","90.4","@import in",[316,855,857],{"x":851,"y":856,"fill":320,"style":838},"107.3","CSS",[316,859,861],{"x":851,"y":860,"fill":807,"style":843},"124.2","global stylesheet",[316,863,865],{"x":318,"y":864,"fill":320,"style":838},"98.8","Upgrade tool",[316,867,869],{"x":318,"y":868,"fill":807,"style":843},"115.7","config to CSS",[316,871,873],{"x":872,"y":837,"fill":320,"style":838},"530.8","Visual diff",[316,875,876],{"x":872,"y":842,"fill":807,"style":843},"borders, rings,",[316,878,879],{"x":872,"y":847,"fill":807,"style":843},"placeholders",[316,881,883],{"x":882,"y":852,"fill":320,"style":838},"681.6","Size + class",[316,885,886],{"x":882,"y":856,"fill":320,"style":838},"checks",[316,888,889],{"x":882,"y":860,"fill":807,"style":843},"against old build",[891,892,273,893,253],"defs",{},[894,895,901,902,273],"marker",{"id":896,"viewBox":897,"refX":797,"refY":898,"markerWidth":899,"markerHeight":899,"orient":900},"tw4-steps-arrow","0 0 10 10","5","7","auto-start-reverse","\n      ",[803,903],{"d":904,"fill":807},"M0 0 L10 5 L0 10 z",[371,906,907],{},"The whole migration took about half a day; most of it was the visual comparison.",[43,909,911],{"id":910},"step-5-verify-output-and-classes","Step 5: Verify Output and Classes",[14,913,914,915,919,920,922],{},"Two checks before merging. A visual comparison with Playwright screenshots of 40 pages in both themes caught the four default changes above. And the class check from ",[37,916,918],{"href":917},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ffixing-missing-tailwind-classes-in-production-builds\u002F","Fixing Missing Tailwind Classes in Production Builds",", which compares classes used in the built HTML with selectors in the built CSS, confirmed nothing was missing — automatic source detection had found everything the old content paths listed, plus the external folder once the ",[18,921,425],{}," was added.",[43,924,926],{"id":925},"using-theme-tokens-outside-tailwind","Using Theme Tokens Outside Tailwind",[14,928,929,930,932,933,936,937,939,940,942],{},"A side benefit of the CSS-first theme is that every token is a real CSS custom property. Before the migration, the site duplicated its brand colours in three places: ",[18,931,20],{},", a ",[18,934,935],{},"tokens.css"," file for hand-written component styles, and a JSON file read by the Open Graph image generator. Now the ",[18,938,458],{}," block is the single source. Component styles use ",[18,941,579],{}," directly, scoped Astro styles do the same, and the OG image script reads the compiled CSS variables from the built stylesheet with a small regex. Inline SVG diagrams can reference the same variables, which made their dark-mode treatment simpler.",[14,944,945,946,948,949,952],{},"There is one caveat: tokens defined in ",[18,947,458],{}," are emitted as variables whether utilities use them or not. Large palettes that exist only for documentation of the design system can be declared with ",[18,950,951],{},"@theme reference"," in a separate file imported where needed, so they are available to utilities without adding every variable to the shared stylesheet.",[43,954,956],{"id":955},"monorepos-and-shared-packages","Monorepos and Shared Packages",[14,958,959,960,962,963,63,965,967,968,970],{},"The site lives in a monorepo with a shared UI package. Under Tailwind 3 the package had its own ",[18,961,20],{}," preset, imported by each app. In Tailwind 4 the package exports a CSS file with its ",[18,964,458],{},[18,966,425],{}," directives, and each app's global stylesheet imports it after ",[18,969,174],{},". Sources declared in the package's CSS are resolved relative to that file, so the package can point Tailwind at its own components without each app knowing its folder layout. That removed a class of bug where an app's content paths forgot a newly added package folder.",[43,972,974],{"id":973},"measured-impact","Measured Impact",[588,976,977,992],{},[591,978,979],{},[594,980,981,984,987,989],{},[597,982,983],{},"Measure",[597,985,986],{},"Tailwind 3.4 + integration",[597,988,353],{},[597,990,991],{},"Tool",[607,993,994,1008,1022,1036,1052,1065],{},[594,995,996,999,1002,1005],{},[612,997,998],{},"CSS step in production build",[612,1000,1001],{},"3.8 s",[612,1003,1004],{},"0.4 s",[612,1006,1007],{},"Build log timings",[594,1009,1010,1013,1016,1019],{},[612,1011,1012],{},"Full production build",[612,1014,1015],{},"61 s",[612,1017,1018],{},"57 s",[612,1020,1021],{},"hyperfine, 5 runs",[594,1023,1024,1027,1030,1033],{},[612,1025,1026],{},"Dev: class change to browser",[612,1028,1029],{},"~300 ms",[612,1031,1032],{},"~40 ms",[612,1034,1035],{},"Browser performance panel",[594,1037,1038,1041,1044,1047],{},[612,1039,1040],{},"CSS output, brotli",[612,1042,1043],{},"12.4 KB",[612,1045,1046],{},"11.2 KB",[612,1048,1049],{},[18,1050,1051],{},"brotli -c | wc -c",[594,1053,1054,1057,1060,1062],{},[612,1055,1056],{},"Config files",[612,1058,1059],{},"3",[612,1061,369],{},[612,1063,1064],{},"Repository",[594,1066,1067,1070,1073,1076],{},[612,1068,1069],{},"Dependencies removed",[612,1071,1072],{},"—",[612,1074,1075],{},"3 (integration, postcss, autoprefixer)",[612,1077,1078],{},[18,1079,1080],{},"package.json",[242,1082,1083,1174],{},[245,1084,253,1089,253,1092,253,1095,253,1098],{"viewBox":1085,"role":248,"ariaLabelledBy":1086,"xmlns":252},"0 0 760 196",[1087,1088],"tw4-perf-title","tw4-perf-desc",[255,1090,1091],{"id":1087},"CSS build step, full build and dev update time before and after",[259,1093,1094],{"id":1088},"Paired bars. The CSS step in the production build went from 3,800 to 400 milliseconds. A class change reaching the browser in development went from 300 to 40 milliseconds. Total production build went from 61 to 57 seconds.",[263,1096],{"x":265,"y":265,"width":266,"height":1097,"fill":268},"196",[270,1099,273,1100,273,1107,273,1111,273,1117,273,1121,273,1125,273,1129,273,1132,273,1135,273,1141,273,1145,273,1149,273,1155,273,1160,273,1164,273,1169,253],{"style":272},[263,1101],{"x":1102,"y":331,"width":1103,"height":1104,"rx":1105,"fill":282,"stroke":807,"style":1106},"278.0","14.0","12.0","2","stroke-width:1px",[263,1108],{"x":1109,"y":331,"width":1103,"height":1104,"rx":1105,"fill":303,"opacity":1110,"stroke":305,"style":1106},"400.8","0.4",[263,1112],{"x":1113,"y":1114,"width":1115,"height":1116,"rx":1059,"fill":282,"stroke":807,"style":1106},"230.0","82.0","441.9","16.0",[263,1118],{"x":1113,"y":1119,"width":1120,"height":1116,"rx":1059,"fill":303,"opacity":1110,"stroke":305,"style":1106},"102.0","46.5",[263,1122],{"x":1113,"y":1123,"width":1124,"height":1116,"rx":1059,"fill":282,"stroke":807,"style":1106},"134.0","34.9",[263,1126],{"x":1113,"y":1127,"width":1128,"height":1116,"rx":1059,"fill":303,"opacity":1110,"stroke":305,"style":1106},"154.0","4.7",[803,1130],{"d":1131,"fill":806,"stroke":807,"style":283},"M230.0 78.0 L230.0 176.0",[316,1133,1134],{"x":318,"y":319,"fill":320,"style":321},"Build and dev server timing",[316,1136,1140],{"x":1137,"y":1138,"fill":807,"style":1139},"298.0","60.0","font-size:12px;text-anchor:start","Tailwind 3.4",[316,1142,1144],{"x":1143,"y":1138,"fill":807,"style":1139},"420.8","Tailwind 4",[316,1146,1148],{"x":276,"y":1147,"fill":320,"style":1139},"105.2","CSS build step",[316,1150,1154],{"x":1151,"y":1152,"fill":320,"style":1153},"678.9","94.5","font-size:11.5px;text-anchor:start;font-weight:700","3800 ms",[316,1156,1159],{"x":1157,"y":1158,"fill":352,"style":1153},"283.5","114.5","400 ms",[316,1161,1163],{"x":276,"y":1162,"fill":320,"style":1139},"157.2","Dev class change",[316,1165,1168],{"x":1166,"y":1167,"fill":320,"style":1153},"271.9","146.5","300 ms",[316,1170,1173],{"x":1171,"y":1172,"fill":352,"style":1153},"241.7","166.5","40 ms",[371,1175,1176],{},"Production timings from build logs and hyperfine; dev timing from the browser performance panel, median of ten edits.",[14,1178,1179],{},"The full build improved by only 4 seconds because CSS generation was a small part of it; the dev server change was what developers noticed.",[43,1181,1183],{"id":1182},"pitfalls-rollback","Pitfalls & Rollback",[48,1185,1186,1193,1199,1210,1216],{},[51,1187,1188,1192],{},[1189,1190,1191],"strong",{},"Keeping the old integration alongside the Vite plugin."," Remove it; running both generates CSS twice.",[51,1194,1195,1198],{},[1189,1196,1197],{},"Skipping the visual diff."," Default border, ring and placeholder changes are not errors.",[51,1200,1201,1204,1205,474,1207,1209],{},[1189,1202,1203],{},"Forgetting the dark variant."," Without ",[18,1206,444],{},[18,1208,566],{}," follows the OS, not the toggle.",[51,1211,1212,1215],{},[1189,1213,1214],{},"Dropping support for older browsers unknowingly."," Check analytics against Tailwind 4's browser targets.",[51,1217,1218,1221],{},[1189,1219,1220],{},"Rollback:"," the migration is one branch; reverting it restores the integration, PostCSS config and JavaScript config together.",[43,1223,1225],{"id":1224},"conclusion","Conclusion",[14,1227,1228],{},"Tailwind 4 in Astro is simpler than Tailwind 3 was: one Vite plugin, one CSS file holding the theme, sources and variants, and no PostCSS. The migration took half a day on a 900-page site, most of it spent on a visual comparison that caught four changed defaults, and it made the CSS step nine times faster and class edits in the dev server near-instant.",[43,1230,1232],{"id":1231},"faq","FAQ",[1234,1235,1237],"h3",{"id":1236},"do-i-still-need-the-astrojstailwind-integration-with-tailwind-4","Do I still need the @astrojs\u002Ftailwind integration with Tailwind 4?",[14,1239,1240],{},"No. Tailwind 4 ships a Vite plugin, @tailwindcss\u002Fvite, which Astro can use directly through its vite.plugins setting. The older Astro integration was built around Tailwind 3 and PostCSS. Removing it and adding the Vite plugin is the recommended setup for Tailwind 4 in Astro.",[1234,1242,1244],{"id":1243},"where-does-tailwindconfigjs-go-in-tailwind-4","Where does tailwind.config.js go in Tailwind 4?",[14,1246,1247],{},"Configuration moves into CSS. Theme values are defined with the theme directive as CSS variables, sources with the source directive, plugins with the plugin directive and custom variants with the custom-variant directive. A JavaScript config can still be loaded with the config directive during a migration, but the CSS-first form is simpler.",[1234,1249,1251],{"id":1250},"how-is-dark-mode-configured-in-tailwind-4","How is dark mode configured in Tailwind 4?",[14,1253,1254],{},"By default dark variants follow prefers-color-scheme. For a toggle that sets a class or data attribute on the html element, define a custom variant in CSS, for example custom-variant dark with a selector for data-theme dark, so dark utilities apply when that attribute is present.",[1234,1256,1258],{"id":1257},"is-tailwind-4-faster-than-tailwind-3-in-astro-builds","Is Tailwind 4 faster than Tailwind 3 in Astro builds?",[14,1260,1261],{},"In this guide, the CSS step of the production build went from about 3.8 seconds to 0.4 seconds, and the dev server reflected class changes in about 40 milliseconds instead of 300. The overall build time fell by about 4 seconds on a 900-page site, because CSS generation was only a small part of it.",[43,1263,1265],{"id":1264},"related","Related",[48,1267,1268,1277,1282,1287,1294],{},[51,1269,1270,1273,1274,1276],{},[1189,1271,1272],{},"Parent:"," ",[37,1275,40],{"href":39}," — CSS and JS weight on static sites.",[51,1278,1279,1281],{},[37,1280,557],{"href":556}," — sources and safelists after the move.",[51,1283,1284,1286],{},[37,1285,918],{"href":917}," — the class check used here.",[51,1288,1289,1293],{},[37,1290,1292],{"href":1291},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-dark-mode-toggles-for-static-sites\u002F","Accessible Dark Mode Toggles for Static Sites"," — the toggle the dark variant follows.",[51,1295,1296,1300],{},[37,1297,1299],{"href":1298},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fpurging-unused-css-with-tailwind-and-lightningcss\u002F","Purging Unused CSS with Tailwind and Lightning CSS"," — Lightning CSS, which Tailwind 4 uses internally.",[1302,1303,1304],"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 .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}",{"title":78,"searchDepth":91,"depth":91,"links":1306},[1307,1308,1309,1310,1311,1312,1313,1314,1315,1316,1317,1318,1324],{"id":45,"depth":91,"text":46},{"id":70,"depth":91,"text":71},{"id":193,"depth":91,"text":194},{"id":376,"depth":91,"text":377},{"id":582,"depth":91,"text":583},{"id":910,"depth":91,"text":911},{"id":925,"depth":91,"text":926},{"id":955,"depth":91,"text":956},{"id":973,"depth":91,"text":974},{"id":1182,"depth":91,"text":1183},{"id":1224,"depth":91,"text":1225},{"id":1231,"depth":91,"text":1232,"children":1319},[1320,1321,1322,1323],{"id":1236,"depth":130,"text":1237},{"id":1243,"depth":130,"text":1244},{"id":1250,"depth":130,"text":1251},{"id":1257,"depth":130,"text":1258},{"id":1264,"depth":91,"text":1265},[1326,1329,1332,1333],{"name":1327,"item":1328},"Home","\u002F",{"name":1330,"item":1331},"Core Web Vitals Optimization for SSGs","\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002F",{"name":40,"item":39},{"name":5,"item":1334},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ftailwind-v4-in-astro-without-postcss-plugins\u002F","2026-10-02","Move an Astro site from Tailwind 3 with the PostCSS integration to Tailwind 4 on its Vite plugin: CSS-first config, sources, dark mode and build time, measured.","md",[1339,1340,1341,1342],{"q":1237,"a":1240},{"q":1244,"a":1247},{"q":1251,"a":1254},{"q":1258,"a":1261},{},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ftailwind-v4-in-astro-without-postcss-plugins",{"title":5,"description":1336},"performance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ftailwind-v4-in-astro-without-postcss-plugins\u002Findex","article","sRbwZPKCvILhhxKOii0qKe63T4Z77DbwqZ4VD83aHIY",[1350,1353,1355,1358,1361,1364,1367,1370,1373,1376,1379,1382,1385,1388,1391,1394,1397,1400,1403,1406,1409,1412,1415,1418,1421,1424,1427,1430,1433,1436,1439,1442,1445,1448,1451,1454,1457,1460,1463,1466,1469,1472,1475,1478,1481,1484,1487,1490,1493,1496,1499,1502,1505,1508,1511,1514,1517,1520,1523,1526,1529,1532,1535,1538,1541,1544,1547,1550,1553,1556,1559,1562,1565,1568,1571,1574,1577,1580,1583,1586,1589,1592,1595,1598,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,1795,1798,1800,1803,1805,1808,1811,1813,1816,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,1924,1927,1930,1933,1936,1939,1942,1945,1948,1951,1954,1957,1960,1963,1966,1969,1972,1975,1978,1981,1984,1987,1990,1993,1996,1999,2002,2005,2008,2011,2014,2017,2020,2023,2026,2029,2032,2035,2038,2041,2044,2047,2050,2053,2056,2059,2062,2065,2068,2071,2074,2077,2080,2083,2086,2089,2092,2095,2098,2101,2104,2107,2110,2113,2116,2119,2122,2125,2128,2131,2134,2137,2140,2143,2146,2149,2152,2155,2158,2161,2164,2167,2170,2173,2176,2179,2182,2185,2188,2191,2194,2197,2200,2203,2206,2209,2212,2215,2218,2221,2224,2227,2230,2233,2236,2239,2242,2245,2248,2251,2254,2257,2260,2263,2266,2269,2272,2275,2278,2281,2284,2287,2290,2293,2296,2299,2302,2305,2308,2311,2314,2317,2320,2323,2326,2329,2332,2335,2338,2341,2344,2347,2350,2353,2356,2359,2362,2365,2368,2371,2374,2377,2380,2383,2386,2389,2392,2395,2398,2401,2404,2407,2410,2413,2416,2419,2422,2425,2428,2431,2434,2437,2440,2443,2446,2449,2452,2455,2458,2461,2464,2467,2470,2473,2476,2479,2482,2485,2488],{"path":1351,"title":1352},"\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":1354,"title":1292},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-dark-mode-toggles-for-static-sites",{"path":1356,"title":1357},"\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":1359,"title":1360},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fenforcing-alt-text-for-markdown-images-at-build-time","Enforcing Alt Text for Markdown Images at Build Time",{"path":1362,"title":1363},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Ffixing-heading-order-problems-in-markdown-content","Fixing Heading Order Problems in Markdown Content",{"path":1365,"title":1366},"\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":1368,"title":1369},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1371,"title":1372},"\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":1374,"title":1375},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Fskip-links-and-landmarks-in-ssg-layouts","Skip Links and Landmarks in SSG Layouts",{"path":1377,"title":1378},"\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":1380,"title":1381},"\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":1383,"title":1384},"\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":1386,"title":1387},"\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":1389,"title":1390},"\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":1392,"title":1393},"\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":1395,"title":1396},"\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":1398,"title":1399},"\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":1401,"title":1402},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1404,"title":1405},"\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":1407,"title":1408},"\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":1410,"title":1411},"\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":1413,"title":1414},"\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":1416,"title":1417},"\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":1419,"title":1420},"\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":1422,"title":1423},"\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":1425,"title":1426},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1428,"title":1429},"\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":1431,"title":1432},"\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":1434,"title":1435},"\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":1437,"title":1438},"\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":1440,"title":1441},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1443,"title":1444},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1446,"title":1447},"\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":1449,"title":1450},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1452,"title":1453},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1455,"title":1456},"\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":1458,"title":1459},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1461,"title":1462},"\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":1464,"title":1465},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1467,"title":1468},"\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":1470,"title":1471},"\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":1473,"title":1474},"\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":1476,"title":1477},"\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":1479,"title":1480},"\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":1482,"title":1483},"\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":1485,"title":1486},"\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":1488,"title":1489},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1491,"title":1492},"\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":1494,"title":1495},"\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":1497,"title":1498},"\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":1500,"title":1501},"\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":1503,"title":1504},"\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":1506,"title":1507},"\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":1509,"title":1510},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1512,"title":1513},"\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":1515,"title":1516},"\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":1518,"title":1519},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1521,"title":1522},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1524,"title":1525},"\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":1527,"title":1528},"\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":1530,"title":1531},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1533,"title":1534},"\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":1536,"title":1537},"\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":1539,"title":1540},"\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":1542,"title":1543},"\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":1545,"title":1546},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1548,"title":1549},"\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":1551,"title":1552},"\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":1554,"title":1555},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1557,"title":1558},"\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":1560,"title":1561},"\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":1563,"title":1564},"\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":1566,"title":1567},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1569,"title":1570},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1572,"title":1573},"\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":1575,"title":1576},"\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":1578,"title":1579},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1581,"title":1582},"\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":1584,"title":1585},"\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":1587,"title":1588},"\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":1590,"title":1591},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1593,"title":1594},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1596,"title":1597},"\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":1599,"title":1600},"\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":1602,"title":1603},"\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":1605,"title":1606},"\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":1608,"title":1609},"\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":1611,"title":1612},"\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":1614,"title":1615},"\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":1617,"title":1618},"\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":1620,"title":1621},"\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":1623,"title":1624},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1626,"title":1627},"\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":1629,"title":1630},"\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":1632,"title":1633},"\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":1635,"title":1636},"\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":1638,"title":1639},"\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":1641,"title":1642},"\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":1644,"title":1645},"\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":1647,"title":1648},"\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":1650,"title":1651},"\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":1653,"title":1654},"\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":1656,"title":1657},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1659,"title":1660},"\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":1662,"title":1663},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1665,"title":1666},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1668,"title":1669},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1671,"title":1672},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1674,"title":1675},"\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":1677,"title":1678},"\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":1680,"title":1681},"\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":1683,"title":1684},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1686,"title":1687},"\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":1689,"title":1690},"\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":1692,"title":1693},"\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":1695,"title":1696},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1698,"title":1699},"\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":1701,"title":1702},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1704,"title":1705},"\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":1707,"title":1708},"\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":1710,"title":1711},"\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":1713,"title":1714},"\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":1716,"title":1717},"\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":1719,"title":1720},"\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":1722,"title":1723},"\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":1725,"title":1726},"\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":1728,"title":1729},"\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":1731,"title":1732},"\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":1734,"title":1735},"\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":1737,"title":1738},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1740,"title":1741},"\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":1743,"title":1744},"\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":1746,"title":1747},"\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":1749,"title":1750},"\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":1752,"title":1753},"\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":1755,"title":1756},"\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":1758,"title":1759},"\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":1761,"title":1762},"\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":1764,"title":1765},"\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":1767,"title":1768},"\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":1770,"title":1771},"\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":1773,"title":1774},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1776,"title":1777},"\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":1779,"title":1780},"\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":1782,"title":1783},"\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":1785,"title":1786},"\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":1788,"title":1789},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1791,"title":1792},"\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":1794,"title":918},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ffixing-missing-tailwind-classes-in-production-builds",{"path":1796,"title":1797},"\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":1799,"title":40},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization",{"path":1801,"title":1802},"\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":1804,"title":557},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fkeeping-tailwind-css-output-small-on-static-sites",{"path":1806,"title":1807},"\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":1809,"title":1810},"\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":1812,"title":1299},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fpurging-unused-css-with-tailwind-and-lightningcss",{"path":1814,"title":1815},"\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":1344,"title":5},{"path":1818,"title":1819},"\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":1821,"title":1822},"\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":1824,"title":1825},"\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":1827,"title":1828},"\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":1830,"title":1831},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites\u002Ffixing-cls-from-dynamic-table-of-contents-widgets","Fixing CLS From Dynamic Table of Contents Widgets",{"path":1833,"title":1834},"\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":1836,"title":1837},"\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":1839,"title":1840},"\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":1842,"title":1843},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1845,"title":1846},"\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":1848,"title":1849},"\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":1851,"title":1852},"\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":1854,"title":1855},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":1857,"title":1858},"\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":1860,"title":1861},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1863,"title":1864},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1866,"title":1867},"\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":1869,"title":1870},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1872,"title":1873},"\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":1875,"title":1876},"\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":1878,"title":1879},"\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":1881,"title":1882},"\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":1884,"title":1885},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":1887,"title":1888},"\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":1890,"title":1891},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":1893,"title":1894},"\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":1896,"title":1897},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":1899,"title":1900},"\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":1902,"title":1903},"\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":1905,"title":1906},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1908,"title":1909},"\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":1911,"title":1912},"\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":1914,"title":1915},"\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":1917,"title":1918},"\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":1920,"title":1921},"\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":1923,"title":1330},"\u002Fperformance-optimization-core-web-vitals-for-ssgs",{"path":1925,"title":1926},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1928,"title":1929},"\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":1931,"title":1932},"\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":1934,"title":1935},"\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":1937,"title":1938},"\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":1940,"title":1941},"\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":1943,"title":1944},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1946,"title":1947},"\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":1949,"title":1950},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":1952,"title":1953},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1955,"title":1956},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":1958,"title":1959},"\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":1961,"title":1962},"\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":1964,"title":1965},"\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":1967,"title":1968},"\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":1970,"title":1971},"\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":1973,"title":1974},"\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":1976,"title":1977},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1979,"title":1980},"\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":1982,"title":1983},"\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":1985,"title":1986},"\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":1988,"title":1989},"\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":1991,"title":1992},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1994,"title":1995},"\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":1997,"title":1998},"\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":2000,"title":2001},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":2003,"title":2004},"\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":2006,"title":2007},"\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":2009,"title":2010},"\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":2012,"title":2013},"\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":2015,"title":2016},"\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":2018,"title":2019},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2021,"title":2022},"\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":2024,"title":2025},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2027,"title":2028},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2030,"title":2031},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2033,"title":2034},"\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":2036,"title":2037},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2039,"title":2040},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2042,"title":2043},"\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":2045,"title":2046},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2048,"title":2049},"\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":2051,"title":2052},"\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":2054,"title":2055},"\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":2057,"title":2058},"\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":2060,"title":2061},"\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":2063,"title":2064},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2066,"title":2067},"\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":2069,"title":2070},"\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":2072,"title":2073},"\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":2075,"title":2076},"\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":2078,"title":2079},"\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":2081,"title":2082},"\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":2084,"title":2085},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2087,"title":2088},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2090,"title":2091},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2093,"title":2094},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2096,"title":2097},"\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":2099,"title":2100},"\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":2102,"title":2103},"\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":2105,"title":2106},"\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":2108,"title":2109},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2111,"title":2112},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2114,"title":2115},"\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":2117,"title":2118},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2120,"title":2121},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2123,"title":2124},"\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":2126,"title":2127},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2129,"title":2130},"\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":2132,"title":2133},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2135,"title":2136},"\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":2138,"title":2139},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2141,"title":2142},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2144,"title":2145},"\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":2147,"title":2148},"\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":2150,"title":2151},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2153,"title":2154},"\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":2156,"title":2157},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2159,"title":2160},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2162,"title":2163},"\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":2165,"title":2166},"\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":2168,"title":2169},"\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":2171,"title":2172},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2174,"title":2175},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2177,"title":2178},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2180,"title":2181},"\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":2183,"title":2184},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2186,"title":2187},"\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":2189,"title":2190},"\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":2192,"title":2193},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2195,"title":2196},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2198,"title":2199},"\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":2201,"title":2202},"\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":2204,"title":2205},"\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":2207,"title":2208},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2210,"title":2211},"\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":2213,"title":2214},"\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":2216,"title":2217},"\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":2219,"title":2220},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":2222,"title":2223},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2225,"title":2226},"\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":2228,"title":2229},"\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":2231,"title":2232},"\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":2234,"title":2235},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2237,"title":2238},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2240,"title":2241},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2243,"title":2244},"\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":2246,"title":2247},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2249,"title":2250},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2252,"title":2253},"\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":2255,"title":2256},"\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":2258,"title":2259},"\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":2261,"title":2262},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2264,"title":2265},"\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":2267,"title":2268},"\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":2270,"title":2271},"\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":2273,"title":2274},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2276,"title":2277},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2279,"title":2280},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2282,"title":2283},"\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":2285,"title":2286},"\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":2288,"title":2289},"\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":2291,"title":2292},"\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":2294,"title":2295},"\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":2297,"title":2298},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2300,"title":2301},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2303,"title":2304},"\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":2306,"title":2307},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2309,"title":2310},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2312,"title":2313},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2315,"title":2316},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2318,"title":2319},"\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":2321,"title":2322},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2324,"title":2325},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2327,"title":2328},"\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":2330,"title":2331},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2333,"title":2334},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2336,"title":2337},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2339,"title":2340},"\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":2342,"title":2343},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2345,"title":2346},"\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":2348,"title":2349},"\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":2351,"title":2352},"\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":2354,"title":2355},"\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":2357,"title":2358},"\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":2360,"title":2361},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2363,"title":2364},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2366,"title":2367},"\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":2369,"title":2370},"\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":2372,"title":2373},"\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":2375,"title":2376},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2378,"title":2379},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2381,"title":2382},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2384,"title":2385},"\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":2387,"title":2388},"\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":2390,"title":2391},"\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":2393,"title":2394},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2396,"title":2397},"\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":2399,"title":2400},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2402,"title":2403},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2405,"title":2406},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2408,"title":2409},"\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":2411,"title":2412},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2414,"title":2415},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2417,"title":2418},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2420,"title":2421},"\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":2423,"title":2424},"\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":2426,"title":2427},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2429,"title":2430},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2432,"title":2433},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2435,"title":2436},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2438,"title":2439},"\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":2441,"title":2442},"\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":2444,"title":2445},"\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":2447,"title":2448},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2450,"title":2451},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2453,"title":2454},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2456,"title":2457},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2459,"title":2460},"\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":2462,"title":2463},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2465,"title":2466},"\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":2468,"title":2469},"\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":2471,"title":2472},"\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":2474,"title":2475},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2477,"title":2478},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2480,"title":2481},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2483,"title":2484},"\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":2486,"title":2487},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2489,"title":2490},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2492,"tools":2496},{"label":2493,"plural":2494,"u":2495},"How-to","How-tos","\u002Fguides\u002Fhow-to\u002F",[2497],{"label":2498,"u":2499},"Astro","\u002Ftools\u002Fastro\u002F",1790943194236]