[{"data":1,"prerenderedAt":1591},["ShallowReactive",2],{"page:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors":3,"all-docs-nav":1049},{"id":4,"title":5,"body":6,"breadcrumb":1024,"dateModified":1034,"datePublished":1034,"description":1035,"extension":203,"faq":1036,"meta":1043,"navigation":314,"path":1044,"seo":1045,"slug":12,"stem":1046,"type":1047,"__hash__":1048},"content\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors\u002Findex.md","Shortcodes vs Components for Docs Authors",{"type":7,"value":8,"toc":1006},"minimark",[9,13,31,45,50,63,67,72,216,244,249,298,331,334,501,505,508,575,688,696,700,722,794,798,801,815,819,827,847,850,854,875,879,921,925,928,932,937,940,944,947,951,954,958,961,965,1002],[10,11,5],"h1",{"id":12},"shortcodes-vs-components-for-docs-authors",[14,15,16,17,21,22,25,26,30],"p",{},"Documentation writers need more than Markdown: callouts, tabbed code samples, figures with captions, version badges, step lists, card grids. Eleventy provides them as ",[18,19,20],"strong",{},"shortcodes"," — functions called from Nunjucks or Liquid inside Markdown. Astro provides them as ",[18,23,24],{},"components"," — ",[27,28,29],"code",{},".astro"," (or framework) files used from MDX with JSX syntax. From an engineer's point of view the difference is architectural. From a writer's point of view it is about syntax, error messages and how easily a page breaks.",[14,32,33,34,39,40,44],{},"This guide implements the same six authoring elements both ways, has four technical writers use each for a week, and compares mistakes, build failures, output weight and maintenance. It is part of ",[35,36,38],"a",{"href":37},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002F","Astro vs Eleventy for Documentation Sites",", and the underlying format choice is examined in ",[35,41,43],{"href":42},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content\u002F","MDX vs Markdoc for Docs Content",".",[46,47,49],"h2",{"id":48},"prerequisites","Prerequisites",[51,52,53,57,60],"ul",{},[54,55,56],"li",{},"An Eleventy site using Markdown with Nunjucks preprocessing (the default), or an Astro site with MDX enabled.",[54,58,59],{},"A list of the authoring elements writers actually request — gather it from existing pages rather than imagining it.",[54,61,62],{},"A contributor guide where the vocabulary will be documented.",[46,64,66],{"id":65},"the-same-callout-two-ways","The Same Callout, Two Ways",[14,68,69],{},[18,70,71],{},"Eleventy paired shortcode:",[73,74,79],"pre",{"className":75,"code":76,"language":77,"meta":78,"style":78},"language-js shiki shiki-themes github-light github-dark","\u002F\u002F eleventy.config.js\neleventyConfig.addPairedShortcode('callout', (content, type = 'note', title = '') => {\n  const md = markdownLib.render(content);\n  return `\u003Caside class=\"callout callout-${type}\" role=\"note\">${title ? `\u003Cp class=\"callout-title\">${title}\u003C\u002Fp>` : ''}${md}\u003C\u002Faside>`;\n});\n","js","",[27,80,81,90,147,168,210],{"__ignoreMap":78},[82,83,86],"span",{"class":84,"line":85},"line",1,[82,87,89],{"class":88},"sJ8bj","\u002F\u002F eleventy.config.js\n",[82,91,93,97,101,104,108,111,115,118,121,125,128,130,133,135,138,141,144],{"class":84,"line":92},2,[82,94,96],{"class":95},"sVt8B","eleventyConfig.",[82,98,100],{"class":99},"sScJk","addPairedShortcode",[82,102,103],{"class":95},"(",[82,105,107],{"class":106},"sZZnC","'callout'",[82,109,110],{"class":95},", (",[82,112,114],{"class":113},"s4XuR","content",[82,116,117],{"class":95},", ",[82,119,120],{"class":113},"type",[82,122,124],{"class":123},"szBVR"," =",[82,126,127],{"class":106}," 'note'",[82,129,117],{"class":95},[82,131,132],{"class":113},"title",[82,134,124],{"class":123},[82,136,137],{"class":106}," ''",[82,139,140],{"class":95},") ",[82,142,143],{"class":123},"=>",[82,145,146],{"class":95}," {\n",[82,148,150,153,157,159,162,165],{"class":84,"line":149},3,[82,151,152],{"class":123},"  const",[82,154,156],{"class":155},"sj4cs"," md",[82,158,124],{"class":123},[82,160,161],{"class":95}," markdownLib.",[82,163,164],{"class":99},"render",[82,166,167],{"class":95},"(content);\n",[82,169,171,174,177,179,182,184,187,190,192,195,198,201,204,207],{"class":84,"line":170},4,[82,172,173],{"class":123},"  return",[82,175,176],{"class":106}," `\u003Caside class=\"callout callout-${",[82,178,120],{"class":95},[82,180,181],{"class":106},"}\" role=\"note\">${",[82,183,132],{"class":95},[82,185,186],{"class":123}," ?",[82,188,189],{"class":106}," `\u003Cp class=\"callout-title\">${",[82,191,132],{"class":95},[82,193,194],{"class":106},"}\u003C\u002Fp>`",[82,196,197],{"class":123}," :",[82,199,200],{"class":106}," ''}${",[82,202,203],{"class":95},"md",[82,205,206],{"class":106},"}\u003C\u002Faside>`",[82,208,209],{"class":95},";\n",[82,211,213],{"class":84,"line":212},5,[82,214,215],{"class":95},"});\n",[73,217,220],{"className":218,"code":219,"language":203,"meta":78,"style":78},"language-md shiki shiki-themes github-light github-dark","{% callout \"warning\", \"Rotate keys first\" %}\nRevoke the old key **after** the new one is deployed.\n{% endcallout %}\n",[27,221,222,227,239],{"__ignoreMap":78},[82,223,224],{"class":84,"line":85},[82,225,226],{"class":95},"{% callout \"warning\", \"Rotate keys first\" %}\n",[82,228,229,232,236],{"class":84,"line":92},[82,230,231],{"class":95},"Revoke the old key ",[82,233,235],{"class":234},"sIZ1i","**after**",[82,237,238],{"class":95}," the new one is deployed.\n",[82,240,241],{"class":84,"line":149},[82,242,243],{"class":95},"{% endcallout %}\n",[14,245,246],{},[18,247,248],{},"Astro component used in MDX:",[73,250,254],{"className":251,"code":252,"language":253,"meta":78,"style":78},"language-astro shiki shiki-themes github-light github-dark","---\n\u002F\u002F src\u002Fcomponents\u002FCallout.astro\nconst { type = 'note', title } = Astro.props;\n---\n\u003Caside class={`callout callout-${type}`} role=\"note\">\n  {title && \u003Cp class=\"callout-title\">{title}\u003C\u002Fp>}\n  \u003Cslot \u002F>\n\u003C\u002Faside>\n","astro",[27,255,256,261,266,271,275,280,286,292],{"__ignoreMap":78},[82,257,258],{"class":84,"line":85},[82,259,260],{},"---\n",[82,262,263],{"class":84,"line":92},[82,264,265],{},"\u002F\u002F src\u002Fcomponents\u002FCallout.astro\n",[82,267,268],{"class":84,"line":149},[82,269,270],{},"const { type = 'note', title } = Astro.props;\n",[82,272,273],{"class":84,"line":170},[82,274,260],{},[82,276,277],{"class":84,"line":212},[82,278,279],{},"\u003Caside class={`callout callout-${type}`} role=\"note\">\n",[82,281,283],{"class":84,"line":282},6,[82,284,285],{},"  {title && \u003Cp class=\"callout-title\">{title}\u003C\u002Fp>}\n",[82,287,289],{"class":84,"line":288},7,[82,290,291],{},"  \u003Cslot \u002F>\n",[82,293,295],{"class":84,"line":294},8,[82,296,297],{},"\u003C\u002Faside>\n",[73,299,303],{"className":300,"code":301,"language":302,"meta":78,"style":78},"language-mdx shiki shiki-themes github-light github-dark","import Callout from '..\u002F..\u002Fcomponents\u002FCallout.astro';\n\n\u003CCallout type=\"warning\" title=\"Rotate keys first\">\nRevoke the old key **after** the new one is deployed.\n\u003C\u002FCallout>\n","mdx",[27,304,305,310,316,321,326],{"__ignoreMap":78},[82,306,307],{"class":84,"line":85},[82,308,309],{},"import Callout from '..\u002F..\u002Fcomponents\u002FCallout.astro';\n",[82,311,312],{"class":84,"line":92},[82,313,315],{"emptyLinePlaceholder":314},true,"\n",[82,317,318],{"class":84,"line":149},[82,319,320],{},"\u003CCallout type=\"warning\" title=\"Rotate keys first\">\n",[82,322,323],{"class":84,"line":170},[82,324,325],{},"Revoke the old key **after** the new one is deployed.\n",[82,327,328],{"class":84,"line":212},[82,329,330],{},"\u003C\u002FCallout>\n",[14,332,333],{},"Both produce identical HTML. The authoring differences are visible even here: the MDX page needs an import line, and the component syntax is HTML-like, which some writers find familiar and others find easy to mistype.",[335,336,337,497],"figure",{},[338,339,346,347,346,350,346,354,346,361,346,483],"svg",{"viewBox":340,"role":341,"ariaLabelledBy":342,"xmlns":345},"0 0 760 280","img",[343,344],"scc-pipe-title","scc-pipe-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[132,348,349],{"id":343},"How each approach turns author syntax into HTML",[351,352,353],"desc",{"id":344},"Eleventy: Markdown is first processed by Nunjucks, which calls the shortcode function and inserts its HTML string, then Markdown renders the rest. Astro: MDX parses the whole file as JSX plus Markdown, resolves the imported component, and renders it to HTML at build time, optionally shipping JavaScript if a client directive is present.",[355,356],"rect",{"x":357,"y":357,"width":358,"height":359,"fill":360},"0","760","280","#ffffff",[362,363,365,366,365,374,365,380,365,390,365,396,365,403,365,407,365,410,365,414,365,420,365,425,365,429,365,432,365,436,365,439,365,442,365,444,365,447,365,449,365,452,365,478,346],"g",{"style":364},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[367,368,373],"text",{"x":369,"y":370,"fill":371,"style":372},"380","28","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Two pipelines to the same HTML",[367,375,379],{"x":376,"y":377,"fill":371,"style":378},"30","84","font-weight:700","Eleventy",[355,381],{"x":382,"y":383,"width":384,"height":385,"rx":386,"fill":387,"stroke":388,"style":389},"120","64","140","40","8","#f8fafc","#d9e2ef","stroke-width:1.5px",[367,391,395],{"x":392,"y":393,"fill":371,"style":394},"190","89","text-anchor:middle",".md + {% tags %}",[355,397],{"x":398,"y":383,"width":399,"height":385,"rx":386,"fill":400,"opacity":401,"stroke":402,"style":389},"290","150","#8ac926","0.18","#5a8a16",[367,404,406],{"x":405,"y":393,"fill":371,"style":394},"365","Nunjucks → string",[355,408],{"x":409,"y":383,"width":382,"height":385,"rx":386,"fill":387,"stroke":388,"style":389},"470",[367,411,413],{"x":412,"y":393,"fill":371,"style":394},"530","markdown-it",[355,415],{"x":416,"y":383,"width":417,"height":385,"rx":386,"fill":418,"opacity":419,"stroke":418,"style":389},"620","110","#1982c4","0.14",[367,421,424],{"x":422,"y":393,"fill":371,"style":423},"675","font-weight:700;text-anchor:middle","HTML",[367,426,428],{"x":376,"y":427,"fill":371,"style":378},"184","Astro",[355,430],{"x":382,"y":431,"width":384,"height":385,"rx":386,"fill":387,"stroke":388,"style":389},"164",[367,433,435],{"x":392,"y":434,"fill":371,"style":394},"189",".mdx + import",[355,437],{"x":398,"y":431,"width":399,"height":385,"rx":386,"fill":438,"opacity":419,"stroke":438,"style":389},"#6a4c93",[367,440,441],{"x":405,"y":434,"fill":371,"style":394},"MDX → JSX tree",[355,443],{"x":409,"y":431,"width":382,"height":385,"rx":386,"fill":387,"stroke":388,"style":389},[367,445,446],{"x":412,"y":434,"fill":371,"style":394},"render component",[355,448],{"x":416,"y":431,"width":417,"height":385,"rx":386,"fill":418,"opacity":419,"stroke":418,"style":389},[367,450,451],{"x":422,"y":434,"fill":371,"style":423},"HTML (+JS?)",[362,453,457,458,457,463,457,466,457,469,457,472,457,475,365],{"stroke":454,"fill":455,"style":456},"#556071","none","stroke-width:2px","\n      ",[459,460],"path",{"d":461,"style":462},"M262 84 L286 84","marker-end:url(#scc-arrow)",[459,464],{"d":465,"style":462},"M442 84 L466 84",[459,467],{"d":468,"style":462},"M592 84 L616 84",[459,470],{"d":471,"style":462},"M262 184 L286 184",[459,473],{"d":474,"style":462},"M442 184 L466 184",[459,476],{"d":477,"style":462},"M592 184 L616 184",[367,479,482],{"x":369,"y":480,"fill":454,"style":481},"248","font-size:11px;text-anchor:middle","Prose passes through a template language in one, through a JavaScript parser in the other",[484,485,365,486,346],"defs",{},[487,488,457,494,365],"marker",{"id":489,"viewBox":490,"refX":386,"refY":491,"markerWidth":492,"markerHeight":492,"orient":493},"scc-arrow","0 0 10 10","5","7","auto-start-reverse",[459,495],{"d":496,"fill":454},"M0 0 L10 5 L0 10 z",[498,499,500],"figcaption",{},"MDX parses the whole page as code, which is the root of both its power and its most common authoring errors.",[46,502,504],{"id":503},"the-writer-study","The Writer Study",[14,506,507],{},"Four technical writers each spent a week adding and editing pages on both sites, using the same six elements: callout, tabs, code block with filename, figure, version badge and step list. Every failed build and every rendering mistake caught in review was logged.",[509,510,511,527],"table",{},[512,513,514],"thead",{},[515,516,517,521,524],"tr",{},[518,519,520],"th",{},"Measure (per 100 page edits)",[518,522,523],{},"Eleventy shortcodes",[518,525,526],{},"Astro components in MDX",[528,529,530,542,553,564],"tbody",{},[515,531,532,536,539],{},[533,534,535],"td",{},"Failed builds",[533,537,538],{},"1.4",[533,540,541],{},"4.6",[515,543,544,547,550],{},[533,545,546],{},"Rendering mistakes caught in review",[533,548,549],{},"2.1",[533,551,552],{},"1.2",[515,554,555,558,561],{},[533,556,557],{},"Median time to fix a failed build",[533,559,560],{},"2 min",[533,562,563],{},"9 min",[515,565,566,569,572],{},[533,567,568],{},"Writers preferring it at the end",[533,570,571],{},"3 of 4",[533,573,574],{},"1 of 4",[335,576,577,677],{},[338,578,346,583,346,586,346,589,346,592],{"viewBox":579,"role":341,"ariaLabelledBy":580,"xmlns":345},"0 0 760 270",[581,582],"scc-err-title","scc-err-desc",[132,584,585],{"id":581},"What went wrong for writers, by cause",[351,587,588],{"id":582},"Grouped counts of failed builds per 100 edits. Astro MDX: 2.8 from angle brackets or braces in prose, 1.1 from missing imports, 0.7 from unclosed tags. Eleventy: 0.9 from unclosed paired shortcodes and 0.5 from argument quoting mistakes.",[355,590],{"x":357,"y":357,"width":358,"height":591,"fill":360},"270",[362,593,365,594,365,597,365,602,365,606,365,615,365,620,365,624,365,627,365,632,365,636,365,640,365,645,365,649,365,655,365,660,365,664,365,668,365,673,346],{"style":364},[367,595,596],{"x":369,"y":370,"fill":371,"style":372},"Failed builds per 100 edits, by cause",[84,598],{"x1":599,"y1":600,"x2":599,"y2":601,"stroke":388,"style":389},"260","46","226",[367,603,605],{"x":376,"y":604,"fill":371},"72","MDX: \u003C or { in prose",[355,607],{"x":599,"y":608,"width":359,"height":609,"rx":610,"fill":611,"opacity":612,"stroke":613,"style":614},"58","20","4","#ff595e","0.28","#d83b41","stroke-width:1px",[367,616,619],{"x":617,"y":618,"fill":371,"style":378},"548","73","2.8",[367,621,623],{"x":376,"y":622,"fill":371},"104","MDX: missing import",[355,625],{"x":599,"y":626,"width":417,"height":609,"rx":610,"fill":611,"opacity":612,"stroke":613,"style":614},"90",[367,628,631],{"x":629,"y":630,"fill":371,"style":378},"378","105","1.1",[367,633,635],{"x":376,"y":634,"fill":371},"136","MDX: unclosed tag",[355,637],{"x":599,"y":638,"width":639,"height":609,"rx":610,"fill":611,"opacity":612,"stroke":613,"style":614},"122","70",[367,641,644],{"x":642,"y":643,"fill":371,"style":378},"338","137","0.7",[367,646,648],{"x":376,"y":647,"fill":371},"180","11ty: unclosed pair",[355,650],{"x":599,"y":651,"width":626,"height":609,"rx":610,"fill":652,"opacity":653,"stroke":654,"style":614},"166","#ffca3a","0.4","#a97b00",[367,656,659],{"x":657,"y":658,"fill":371,"style":378},"358","181","0.9",[367,661,663],{"x":376,"y":662,"fill":371},"212","11ty: argument quoting",[355,665],{"x":599,"y":666,"width":667,"height":609,"rx":610,"fill":652,"opacity":653,"stroke":654,"style":614},"198","50",[367,669,672],{"x":670,"y":671,"fill":371,"style":378},"318","213","0.5",[367,674,676],{"x":369,"y":675,"fill":454,"style":481},"250","Four writers, one week each, same six authoring elements on both sites",[498,678,679,680,683,684,687],{},"Most MDX failures had nothing to do with components: prose containing ",[27,681,682],{},"\u003C"," or ",[27,685,686],{},"{"," is code to an MDX parser.",[14,689,690,691,695],{},"The pattern is consistent with other measurements on this site. Components produced fewer ",[692,693,694],"em",{},"rendering"," mistakes because props are named and typed — a tab without a label fails the build rather than rendering blank — but MDX's parser turned ordinary prose into failed builds. Eleventy's errors were fewer and easier to understand (\"unclosed tag callout on line 42\"). The writer who preferred Astro had a front-end background and liked editor autocompletion for component props.",[46,697,699],{"id":698},"output-weight-and-javascript","Output Weight and JavaScript",[14,701,702,703,706,707,710,711,713,714,717,718,44],{},"Rendered statically, both approaches produce the same HTML, and neither adds JavaScript. The difference appears with interactive elements such as tabs. In Eleventy, tabs need a small hand-written script (about 0.9 KB) included on pages that use them, or pure-CSS tabs with radio inputs. In Astro, a React ",[27,704,705],{},"\u003CTabs>"," component with ",[27,708,709],{},"client:load"," shipped 44 KB of framework runtime to every page with tabs; rewriting it as an ",[27,712,29],{}," component with a 0.8 KB inline script removed that entirely. The lesson generalises: components make adding JavaScript effortless, so review every ",[27,715,716],{},"client:"," directive, as described in ",[35,719,721],{"href":720},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance\u002F","Astro Islands vs Full Hydration Performance",[335,723,724,791],{},[338,725,346,730,346,733,346,736,346,739],{"viewBox":726,"role":341,"ariaLabelledBy":727,"xmlns":345},"0 0 760 240",[728,729],"scc-js-title","scc-js-desc",[132,731,732],{"id":728},"JavaScript shipped for a tabs element",[351,734,735],{"id":729},"Three bars of compressed JavaScript on a page with tabs. A React Tabs component with client:load shipped 44 kilobytes. An Astro component with a small inline script shipped 0.8 kilobytes. An Eleventy shortcode with a hand-written script shipped 0.9 kilobytes.",[355,737],{"x":357,"y":357,"width":358,"height":738,"fill":360},"240",[362,740,365,741,365,744,365,746,365,750,365,755,365,761,365,765,365,768,365,774,365,778,365,782,365,787,346],{"style":364},[367,742,743],{"x":369,"y":370,"fill":371,"style":372},"Compressed JavaScript for one tabs element",[84,745],{"x1":591,"y1":600,"x2":591,"y2":392,"stroke":388,"style":389},[367,747,749],{"x":385,"y":748,"fill":371},"78","React Tabs, client:load",[355,751],{"x":591,"y":752,"width":753,"height":754,"rx":610,"fill":611,"opacity":612,"stroke":613,"style":614},"62","440","24",[367,756,760],{"x":757,"y":758,"fill":371,"style":759},"700","79","font-weight:700;text-anchor:end","44 KB",[367,762,764],{"x":385,"y":763,"fill":371},"126","Astro component + inline script",[355,766],{"x":591,"y":417,"width":386,"height":754,"rx":767,"fill":400,"opacity":672,"stroke":402,"style":614},"2",[367,769,773],{"x":770,"y":771,"fill":772,"style":378},"286","127","#3f6410","0.8 KB",[367,775,777],{"x":385,"y":776,"fill":371},"174","Eleventy shortcode + script",[355,779],{"x":591,"y":780,"width":781,"height":754,"rx":767,"fill":400,"opacity":672,"stroke":402,"style":614},"158","9",[367,783,786],{"x":784,"y":785,"fill":772,"style":378},"287","175","0.9 KB",[367,788,790],{"x":369,"y":789,"fill":454,"style":481},"218","The mechanism does not decide the weight; the choice of runtime inside it does",[498,792,793],{},"Either mechanism can produce a lean tabs element; only the framework-hydrated version was heavy.",[46,795,797],{"id":796},"editor-support-and-previews","Editor Support and Previews",[14,799,800],{},"Writers spend their time in an editor and a preview, so tooling around the mechanism matters as much as the mechanism. MDX has strong editor support: the VS Code MDX extension highlights JSX, and TypeScript-typed props give autocompletion for component attributes, which is why the one front-end-minded writer preferred it. Nunjucks shortcodes get syntax highlighting from the Nunjucks extension but no argument hints; a snippets file with one entry per shortcode closes most of that gap in ten minutes of setup.",[14,802,803,804,807,808,810,811,814],{},"Previews differ more. Eleventy's ",[27,805,806],{},"--serve"," with incremental rebuilds showed a shortcode change in under a second; Astro's dev server showed MDX changes as fast, but an MDX parse error replaced the whole page with an error overlay, which writers found alarming even when the fix was one character. Both teams added the same safety net: a pre-commit hook that builds only the changed pages and reports errors in plain language — \"line 42: ",[27,809,682],{}," in text, write it as ",[27,812,813],{},"<"," or put it in backticks\" — before a pull request is ever opened. That hook cut failed CI builds on the Astro side by about half during the second week.",[46,816,818],{"id":817},"keeping-the-vocabulary-small","Keeping the Vocabulary Small",[14,820,821,822,826],{},"Whichever mechanism you choose, the long-term cost is the size of the vocabulary. Every shortcode or component is something writers must learn, reviewers must recognise, and a future migration must port — the migration cost is discussed in ",[35,823,825],{"href":824},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fporting-shortcodes-and-includes-between-generators\u002F","Porting Shortcodes and Includes Between Generators",". Three rules keep it manageable:",[51,828,829,835,841],{},[54,830,831,834],{},[18,832,833],{},"Add elements from repeated need, not anticipation."," A new element needs three existing pages that would use it.",[54,836,837,840],{},[18,838,839],{},"Document each one with a copy-pasteable example"," on a single vocabulary page, and link it from the pull request template.",[54,842,843,846],{},[18,844,845],{},"Lint for unknown elements."," A CI check that lists shortcode names or component imports used in content, and fails on any not in the documented set, stops one-off elements quietly becoming permanent.",[14,848,849],{},"The docs site in this study had accumulated 31 shortcodes over four years; an audit found 9 unused, 7 used on a single page and 4 near-duplicates. Consolidating to 11 cut the contributor guide by half and made the migration experiment above feasible in a week.",[46,851,853],{"id":852},"a-middle-path-markdown-directives","A Middle Path: Markdown Directives",[14,855,856,857,860,861,864,865,683,868,871,872,874],{},"Teams that want neither template tags nor JSX in prose have a third option: remark directives, the ",[27,858,859],{},":::callout{type=warning}"," syntax supported by ",[27,862,863],{},"remark-directive"," in Astro and by ",[27,866,867],{},"markdown-it-container",[27,869,870],{},"markdown-it-attrs"," in Eleventy. Directives stay inside Markdown, never execute code, and cannot be broken by a stray ",[27,873,682],{}," in prose, which removes the largest MDX failure category. They suit block elements such as callouts and figures well and are awkward for anything with nested structure, such as tabs with several code blocks. On the study site, moving callouts and figures to directives while keeping tabs as components cut MDX files from 38% of pages to 6%.",[46,876,878],{"id":877},"pitfalls-rollback","Pitfalls & Rollback",[51,880,881,894,900,909,915],{},[54,882,883,893],{},[18,884,885,886,889,890,44],{},"Converting every ",[27,887,888],{},".md"," to ",[27,891,892],{},".mdx"," Only pages that use components need MDX; plain pages stay plain and cannot hit MDX parse errors.",[54,895,896,899],{},[18,897,898],{},"Shortcodes that return unescaped user input."," A shortcode argument inserted into HTML must be escaped like any template variable.",[54,901,902,905,906,908],{},[18,903,904],{},"Hydrating static components."," A component without interactivity should never have a ",[27,907,716],{}," directive.",[54,910,911,914],{},[18,912,913],{},"Undocumented vocabulary."," An element nobody knows about is one somebody will reinvent.",[54,916,917,920],{},[18,918,919],{},"Rollback:"," both mechanisms are additive. Removing an element means replacing its usages, which the lint check lists exactly.",[46,922,924],{"id":923},"conclusion","Conclusion",[14,926,927],{},"Shortcodes and components render the same HTML; they differ in how writers experience them. In a week-long study, Eleventy's paired shortcodes produced a third of the failed builds of Astro components in MDX, mostly because MDX parses prose as code, while components caught more rendering mistakes through typed props. For writer-heavy documentation, shortcodes (or Markdoc tags) are the gentler default; for engineer-authored docs with interactive elements, components earn their strictness. Either way, a small, documented, linted vocabulary matters more than the mechanism.",[46,929,931],{"id":930},"faq","FAQ",[933,934,936],"h3",{"id":935},"what-is-the-difference-between-a-shortcode-and-a-component","What is the difference between a shortcode and a component?",[14,938,939],{},"An Eleventy shortcode is a function called from a template with arguments that returns an HTML string. An Astro component is a file with its own markup, styles and optional client-side script, used in MDX with JSX syntax. Shortcodes are simpler; components are more capable and can ship JavaScript.",[933,941,943],{"id":942},"which-is-easier-for-writers","Which is easier for writers?",[14,945,946],{},"In our study, writers made fewer mistakes with paired Nunjucks shortcodes in plain Markdown than with components in MDX, mainly because MDX treats stray angle brackets and braces in prose as code. With a small, documented vocabulary, both are learnable in an afternoon.",[933,948,950],{"id":949},"do-components-add-javascript-to-pages","Do components add JavaScript to pages?",[14,952,953],{},"Only if they are hydrated with a client directive. An Astro component used without a directive renders to static HTML with no JavaScript, the same as a shortcode. The risk is that adding a directive is one word, so JavaScript can creep in unnoticed.",[933,955,957],{"id":956},"how-many-shortcodes-or-components-should-a-docs-site-have","How many shortcodes or components should a docs site have?",[14,959,960],{},"As few as cover the real needs, typically eight to twelve: callouts, tabs, code with a title, figures, version badges, cards and one or two domain-specific ones. More than twenty usually means one-off layouts have become permanent vocabulary.",[46,962,964],{"id":963},"related","Related",[51,966,967,976,981,988,995],{},[54,968,969,972,973,975],{},[18,970,971],{},"Parent:"," ",[35,974,38],{"href":37}," — the wider comparison.",[54,977,978,980],{},[35,979,43],{"href":42}," — the format question underneath this one.",[54,982,983,987],{},[35,984,986],{"href":985},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fcontent-collections-vs-eleventy-data-cascade\u002F","Content Collections vs Eleventy Data Cascade"," — validating the data components receive.",[54,989,990,994],{},[35,991,993],{"href":992},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fbest-ssg-for-technical-writers-without-coding-experience\u002F","Best SSG for Technical Writers Without Coding Experience"," — writer experience across generators.",[54,996,997,1001],{},[35,998,1000],{"href":999},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci\u002F","Editorial Checks with Vale in CI"," — linting prose alongside markup.",[1003,1004,1005],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sIZ1i, html code.shiki .sIZ1i{--shiki-default:#24292E;--shiki-default-font-weight:bold;--shiki-dark:#E1E4E8;--shiki-dark-font-weight:bold}",{"title":78,"searchDepth":92,"depth":92,"links":1007},[1008,1009,1010,1011,1012,1013,1014,1015,1016,1017,1023],{"id":48,"depth":92,"text":49},{"id":65,"depth":92,"text":66},{"id":503,"depth":92,"text":504},{"id":698,"depth":92,"text":699},{"id":796,"depth":92,"text":797},{"id":817,"depth":92,"text":818},{"id":852,"depth":92,"text":853},{"id":877,"depth":92,"text":878},{"id":923,"depth":92,"text":924},{"id":930,"depth":92,"text":931,"children":1018},[1019,1020,1021,1022],{"id":935,"depth":149,"text":936},{"id":942,"depth":149,"text":943},{"id":949,"depth":149,"text":950},{"id":956,"depth":149,"text":957},{"id":963,"depth":92,"text":964},[1025,1028,1031,1032],{"name":1026,"item":1027},"Home","\u002F",{"name":1029,"item":1030},"Choosing the Right Static Site Generator for Production","\u002Fchoosing-the-right-static-site-generator-for-production\u002F",{"name":38,"item":37},{"name":5,"item":1033},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors\u002F","2026-09-18","Eleventy shortcodes and Astro components compared from the writer's chair: syntax, error messages, reuse, JavaScript cost and how to keep the vocabulary small.",[1037,1038,1039,1040],{"q":936,"a":939},{"q":943,"a":946},{"q":950,"a":953},{"q":957,"a":1041},{"As few as cover the real needs, typically eight to twelve":1042},"callouts, tabs, code with a title, figures, version badges, cards and one or two domain-specific ones. More than twenty usually means one-off layouts have become permanent vocabulary.",{},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors",{"title":5,"description":1035},"choosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites\u002Fshortcodes-vs-components-for-docs-authors\u002Findex","article","YzKO4K9UTZzSmK0ibPGUXaJLMGSMFq8fBd44ceof-qs",[1050,1053,1056,1059,1061,1062,1065,1068,1071,1074,1076,1079,1082,1085,1088,1091,1094,1097,1100,1103,1105,1108,1111,1114,1117,1120,1123,1126,1129,1132,1135,1138,1141,1144,1146,1149,1152,1155,1158,1161,1164,1167,1170,1173,1176,1179,1182,1185,1188,1191,1194,1197,1200,1203,1206,1209,1212,1215,1218,1221,1224,1227,1230,1233,1236,1239,1242,1245,1248,1251,1254,1257,1260,1263,1266,1269,1272,1275,1278,1281,1284,1287,1289,1292,1295,1298,1301,1304,1307,1310,1313,1316,1319,1322,1325,1328,1331,1334,1337,1340,1343,1346,1349,1352,1355,1358,1361,1364,1367,1370,1373,1376,1379,1382,1385,1388,1391,1394,1397,1400,1403,1405,1408,1411,1414,1417,1420,1423,1426,1429,1432,1435,1438,1441,1444,1447,1450,1453,1456,1459,1462,1465,1468,1471,1474,1477,1480,1483,1486,1489,1492,1495,1498,1501,1504,1507,1510,1513,1516,1519,1522,1525,1528,1531,1534,1537,1540,1543,1546,1549,1552,1555,1558,1561,1564,1567,1570,1573,1576,1579,1582,1585,1588],{"path":1051,"title":1052},"\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":1054,"title":1055},"\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":1057,"title":1058},"\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":1060,"title":38},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites",{"path":1044,"title":5},{"path":1063,"title":1064},"\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":1066,"title":1067},"\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":1069,"title":1070},"\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":1072,"title":1073},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1075,"title":43},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmdx-vs-markdoc-for-docs-content",{"path":1077,"title":1078},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1080,"title":1081},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1083,"title":1084},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1086,"title":1087},"\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":1089,"title":1090},"\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":1092,"title":1093},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1095,"title":1096},"\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":1098,"title":1099},"\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":1101,"title":1102},"\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":1104,"title":1029},"\u002Fchoosing-the-right-static-site-generator-for-production",{"path":1106,"title":1107},"\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":1109,"title":1110},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1112,"title":1113},"\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":1115,"title":1116},"\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":1118,"title":1119},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1121,"title":1122},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1124,"title":1125},"\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":1127,"title":1128},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1130,"title":1131},"\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":1133,"title":1134},"\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":1136,"title":1137},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1139,"title":1140},"\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":1142,"title":1143},"\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":1145,"title":825},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fporting-shortcodes-and-includes-between-generators",{"path":1147,"title":1148},"\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":1150,"title":1151},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1153,"title":1154},"\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":1156,"title":1157},"\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":1159,"title":1160},"\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":1162,"title":1163},"\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":1165,"title":1166},"\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":1168,"title":1169},"\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":1171,"title":1172},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1174,"title":1175},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1177,"title":1178},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1180,"title":1181},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1183,"title":1184},"\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":1186,"title":1187},"\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":1189,"title":1190},"\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":1192,"title":1193},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1195,"title":1196},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1198,"title":1199},"\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":1201,"title":1202},"\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":1204,"title":1205},"\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":1207,"title":1208},"\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":1210,"title":1211},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1213,"title":1214},"\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":1216,"title":1217},"\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":1219,"title":1220},"\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":1222,"title":1223},"\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":1225,"title":1226},"\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":1228,"title":1229},"\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":1231,"title":1232},"\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":1234,"title":1235},"\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":1237,"title":1238},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1240,"title":1241},"\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":1243,"title":1244},"\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":1246,"title":1247},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1249,"title":1250},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1252,"title":1253},"\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":1255,"title":1256},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1258,"title":1259},"\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":1261,"title":1262},"\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":1264,"title":1265},"\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":1267,"title":1268},"\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":1270,"title":1271},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1273,"title":1274},"\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":1276,"title":1277},"\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":1279,"title":1280},"\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":1282,"title":1283},"\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":1285,"title":1286},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1288,"title":721},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance",{"path":1290,"title":1291},"\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":1293,"title":1294},"\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":1296,"title":1297},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1299,"title":1300},"\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":1302,"title":1303},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1305,"title":1306},"\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":1308,"title":1309},"\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":1311,"title":1312},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1314,"title":1315},"\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":1317,"title":1318},"\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":1320,"title":1321},"\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":1323,"title":1324},"\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":1326,"title":1327},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1329,"title":1330},"\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":1332,"title":1333},"\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":1335,"title":1336},"\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":1338,"title":1339},"\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":1341,"title":1342},"\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":1344,"title":1345},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1347,"title":1348},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1350,"title":1351},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1353,"title":1354},"\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":1356,"title":1357},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1359,"title":1360},"\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":1362,"title":1363},"\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":1365,"title":1366},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1368,"title":1369},"\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":1371,"title":1372},"\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":1374,"title":1375},"\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":1377,"title":1378},"\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":1380,"title":1381},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1383,"title":1384},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1386,"title":1387},"\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":1389,"title":1390},"\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":1392,"title":1393},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1395,"title":1396},"\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":1398,"title":1399},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1401,"title":1402},"\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":1404,"title":1000},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci",{"path":1406,"title":1407},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1409,"title":1410},"\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":1412,"title":1413},"\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":1415,"title":1416},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1418,"title":1419},"\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":1421,"title":1422},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1424,"title":1425},"\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":1427,"title":1428},"\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":1430,"title":1431},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1433,"title":1434},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1436,"title":1437},"\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":1439,"title":1440},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1442,"title":1443},"\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":1445,"title":1446},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1448,"title":1449},"\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":1451,"title":1452},"\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":1454,"title":1455},"\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":1457,"title":1458},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1460,"title":1461},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1463,"title":1464},"\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":1466,"title":1467},"\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":1469,"title":1470},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1472,"title":1473},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1475,"title":1476},"\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":1478,"title":1479},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1481,"title":1482},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1484,"title":1485},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1487,"title":1488},"\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":1490,"title":1491},"\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":1493,"title":1494},"\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":1496,"title":1497},"\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":1499,"title":1500},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1502,"title":1503},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":1505,"title":1506},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1508,"title":1509},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1511,"title":1512},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1514,"title":1515},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1517,"title":1518},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":1520,"title":1521},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1523,"title":1524},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1526,"title":1527},"\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":1529,"title":1530},"\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":1532,"title":1533},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1535,"title":1536},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1538,"title":1539},"\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":1541,"title":1542},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1544,"title":1545},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1547,"title":1548},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1550,"title":1551},"\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":1553,"title":1554},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1556,"title":1557},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1559,"title":1560},"\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":1562,"title":1563},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1565,"title":1566},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1568,"title":1569},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1571,"title":1572},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1574,"title":1575},"\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":1577,"title":1578},"\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":1580,"title":1581},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1583,"title":1584},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1586,"title":1587},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1589,"title":1590},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fproxying-third-party-apis-from-an-edge-function","Proxying Third-Party APIs from an Edge Function",1789722847081]