[{"data":1,"prerenderedAt":2504},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-from-a-docker-container-with-nginx":3,"all-docs-nav":1356,"filed:\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-from-a-docker-container-with-nginx":2496},{"id":4,"title":5,"body":6,"breadcrumb":1332,"dateModified":1342,"datePublished":1342,"description":1343,"extension":1344,"faq":1345,"meta":1350,"navigation":127,"path":1351,"seo":1352,"slug":12,"stem":1353,"type":1354,"__hash__":1355},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-from-a-docker-container-with-nginx\u002Findex.md","Serving a Static Site From a Docker Container With Nginx",{"type":7,"value":8,"toc":1314},"minimark",[9,13,17,31,36,53,57,165,181,313,317,454,481,485,492,715,718,841,845,848,939,942,946,1050,1053,1060,1064,1178,1187,1190,1194,1229,1233,1236,1240,1245,1248,1252,1255,1259,1262,1266,1269,1273,1310],[10,11,5],"h1",{"id":12},"serving-a-static-site-from-a-docker-container-with-nginx",[14,15,16],"p",{},"Static sites do not need containers — a CDN or object store serves them perfectly well. But many teams deploy everything to a container platform: a Kubernetes cluster, Cloud Run, Fly.io, or an internal platform where \"a service\" means \"an image\". There, the static site ships as an Nginx container like everything else, and the question becomes how to build a small, secure, well-configured image rather than a 900 MB one that runs as root with the default Nginx configuration.",[14,18,19,20,25,26,30],{},"This guide packages an Astro documentation site as an Nginx container for a Kubernetes cluster: a multi-stage Dockerfile, a non-root Nginx with a read-only filesystem, the site's headers and redirects baked into the image, health checks, and measured image size and startup. It belongs to ",[21,22,24],"a",{"href":23},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002F","Self-Hosting Static Sites on S3, Nginx and Caddy","; the Nginx configuration itself is covered in ",[21,27,29],{"href":28},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx\u002F","Serving a Static Site with Nginx",".",[32,33,35],"h2",{"id":34},"prerequisites","Prerequisites",[37,38,39,43,50],"ul",{},[40,41,42],"li",{},"Docker (or another OCI image builder) and a registry the platform can pull from.",[40,44,45,46,30],{},"A static site whose build runs in Node (here Astro 5) and outputs to ",[47,48,49],"code",{},"dist\u002F",[40,51,52],{},"An ingress or load balancer in front of the container that terminates TLS.",[32,54,56],{"id":55},"step-1-a-multi-stage-dockerfile","Step 1: A Multi-Stage Dockerfile",[58,59,64],"pre",{"className":60,"code":61,"language":62,"meta":63,"style":63},"language-dockerfile shiki shiki-themes github-light github-dark","# --- build stage: Node and the generator, discarded afterwards\nFROM node:20-alpine AS build\nWORKDIR \u002Fapp\nCOPY package.json package-lock.json .\u002F\nRUN --mount=type=cache,target=\u002Froot\u002F.npm npm ci\nCOPY . .\nRUN npm run build && \\\n    find dist -type f \\( -name '*.html' -o -name '*.css' -o -name '*.js' -o -name '*.svg' -o -name '*.json' \\) \\\n      -exec gzip -9 -k -n {} \\;\n\n# --- runtime stage: Nginx and the built files only\nFROM nginxinc\u002Fnginx-unprivileged:1.27-alpine-slim\nCOPY nginx\u002Fdefault.conf \u002Fetc\u002Fnginx\u002Fconf.d\u002Fdefault.conf\nCOPY --from=build --chown=101:101 \u002Fapp\u002Fdist \u002Fusr\u002Fshare\u002Fnginx\u002Fhtml\nEXPOSE 8080\nHEALTHCHECK --interval=30s --timeout=3s CMD wget -q -O \u002Fdev\u002Fnull http:\u002F\u002F127.0.0.1:8080\u002Fhealthz || exit 1\n","dockerfile","",[47,65,66,74,80,86,92,98,104,110,116,122,129,135,141,147,153,159],{"__ignoreMap":63},[67,68,71],"span",{"class":69,"line":70},"line",1,[67,72,73],{},"# --- build stage: Node and the generator, discarded afterwards\n",[67,75,77],{"class":69,"line":76},2,[67,78,79],{},"FROM node:20-alpine AS build\n",[67,81,83],{"class":69,"line":82},3,[67,84,85],{},"WORKDIR \u002Fapp\n",[67,87,89],{"class":69,"line":88},4,[67,90,91],{},"COPY package.json package-lock.json .\u002F\n",[67,93,95],{"class":69,"line":94},5,[67,96,97],{},"RUN --mount=type=cache,target=\u002Froot\u002F.npm npm ci\n",[67,99,101],{"class":69,"line":100},6,[67,102,103],{},"COPY . .\n",[67,105,107],{"class":69,"line":106},7,[67,108,109],{},"RUN npm run build && \\\n",[67,111,113],{"class":69,"line":112},8,[67,114,115],{},"    find dist -type f \\( -name '*.html' -o -name '*.css' -o -name '*.js' -o -name '*.svg' -o -name '*.json' \\) \\\n",[67,117,119],{"class":69,"line":118},9,[67,120,121],{},"      -exec gzip -9 -k -n {} \\;\n",[67,123,125],{"class":69,"line":124},10,[67,126,128],{"emptyLinePlaceholder":127},true,"\n",[67,130,132],{"class":69,"line":131},11,[67,133,134],{},"# --- runtime stage: Nginx and the built files only\n",[67,136,138],{"class":69,"line":137},12,[67,139,140],{},"FROM nginxinc\u002Fnginx-unprivileged:1.27-alpine-slim\n",[67,142,144],{"class":69,"line":143},13,[67,145,146],{},"COPY nginx\u002Fdefault.conf \u002Fetc\u002Fnginx\u002Fconf.d\u002Fdefault.conf\n",[67,148,150],{"class":69,"line":149},14,[67,151,152],{},"COPY --from=build --chown=101:101 \u002Fapp\u002Fdist \u002Fusr\u002Fshare\u002Fnginx\u002Fhtml\n",[67,154,156],{"class":69,"line":155},15,[67,157,158],{},"EXPOSE 8080\n",[67,160,162],{"class":69,"line":161},16,[67,163,164],{},"HEALTHCHECK --interval=30s --timeout=3s CMD wget -q -O \u002Fdev\u002Fnull http:\u002F\u002F127.0.0.1:8080\u002Fhealthz || exit 1\n",[14,166,167,168,171,172,175,176,180],{},"The build stage has Node, the generator and ",[47,169,170],{},"node_modules","; none of it reaches the final image. ",[47,173,174],{},"nginx-unprivileged"," runs as user 101 on port 8080 with its pid file and temp paths already writable. Files are precompressed with gzip at build time; Brotli needs an Nginx build with the module, which the slim image lacks — see ",[21,177,179],{"href":178},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx\u002F","Brotli and Gzip Precompression Served by Nginx"," for when that is worth a custom image.",[182,183,184,309],"figure",{},[185,186,193,194,193,198,193,202,193,209,193,294],"svg",{"viewBox":187,"role":188,"ariaLabelledBy":189,"xmlns":192},"0 0 760 300","img",[190,191],"dockngx-layers-title","dockngx-layers-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[195,196,197],"title",{"id":190},"Layers of the final runtime image",[199,200,201],"desc",{"id":191},"Three layers. The base nginx unprivileged alpine slim image, about 12 megabytes. The Nginx site configuration, a few kilobytes. The built site files with precompressed copies, about 35 megabytes. The Node runtime, the generator and node_modules from the build stage are not included.",[203,204],"rect",{"x":205,"y":205,"width":206,"height":207,"fill":208},"0","760","300","#ffffff",[210,211,213,214,213,224,213,231,213,236,213,239,213,245,213,253,213,259,213,264,213,270,213,274,213,278,213,282,213,286,213,290,193],"g",{"style":212},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[203,215],{"x":216,"y":217,"width":218,"height":219,"rx":220,"fill":221,"stroke":222,"style":223},"40.0","60.0","440.0","57.2","8","#f8fafc","#d9e2ef","stroke-width:1.5px",[225,226],"path",{"d":227,"fill":228,"stroke":229,"style":230},"M260.0 119.2 L260.0 139.2","none","#556071","stroke-width:2px;marker-end:url(#dockngx-layers-arrow)",[203,232],{"x":216,"y":233,"width":218,"height":219,"rx":220,"fill":234,"opacity":235,"stroke":234,"style":223},"143.2","#6a4c93","0.14",[225,237],{"d":238,"fill":228,"stroke":229,"style":230},"M260.0 202.4 L260.0 222.4",[203,240],{"x":216,"y":241,"width":218,"height":219,"rx":220,"fill":242,"opacity":243,"stroke":244,"style":223},"226.4","#8ac926","0.2","#5a8a16",[246,247,252],"text",{"x":248,"y":249,"fill":250,"style":251},"380.0","30.0","#1f2937","font-size:16px;text-anchor:middle;font-weight:700","What ends up in the image",[246,254,258],{"x":255,"y":256,"fill":250,"style":257},"260.0","86.4","font-size:13px;text-anchor:middle;font-weight:700","nginx-unprivileged alpine-slim",[246,260,263],{"x":255,"y":261,"fill":229,"style":262},"103.3","font-size:11px;text-anchor:middle","base image",[246,265,269],{"x":266,"y":267,"fill":229,"style":268},"504.0","92.6","font-size:11.5px;text-anchor:start","~12 MB",[246,271,273],{"x":255,"y":272,"fill":250,"style":257},"169.5","default.conf",[246,275,277],{"x":255,"y":276,"fill":229,"style":262},"186.4","headers, redirects, caching",[246,279,281],{"x":266,"y":280,"fill":229,"style":268},"175.8","~4 KB",[246,283,285],{"x":255,"y":284,"fill":250,"style":257},"252.7","dist\u002F + .gz files",[246,287,289],{"x":255,"y":288,"fill":229,"style":262},"269.6","the site",[246,291,293],{"x":266,"y":292,"fill":229,"style":268},"259.0","~35 MB",[295,296,213,297,193],"defs",{},[298,299,305,306,213],"marker",{"id":300,"viewBox":301,"refX":220,"refY":302,"markerWidth":303,"markerHeight":303,"orient":304},"dockngx-layers-arrow","0 0 10 10","5","7","auto-start-reverse","\n      ",[225,307],{"d":308,"fill":229},"M0 0 L10 5 L0 10 z",[310,311,312],"figcaption",{},"The final image was 47 MB; a single-stage image based on node:20 was 1.1 GB.",[32,314,316],{"id":315},"step-2-the-nginx-configuration","Step 2: The Nginx Configuration",[58,318,322],{"className":319,"code":320,"language":321,"meta":63,"style":63},"language-nginx shiki shiki-themes github-light github-dark","server {\n  listen 8080;\n  server_name _;\n  root \u002Fusr\u002Fshare\u002Fnginx\u002Fhtml;\n  gzip_static on;\n  gzip_vary on;\n  absolute_redirect off;      # behind a proxy, keep redirects relative\n  server_tokens off;\n\n  location = \u002Fhealthz { access_log off; return 200 \"ok\\n\"; }\n\n  location \u002F_astro\u002F {\n    add_header Cache-Control \"public, max-age=31536000, immutable\" always;\n    add_header X-Content-Type-Options \"nosniff\" always;\n    try_files $uri =404;\n  }\n  location \u002F {\n    add_header Cache-Control \"public, max-age=0, must-revalidate\" always;\n    add_header X-Content-Type-Options \"nosniff\" always;\n    add_header Referrer-Policy \"strict-origin-when-cross-origin\" always;\n    try_files $uri $uri\u002Findex.html =404;\n  }\n  error_page 404 \u002F404.html;\n  include \u002Fetc\u002Fnginx\u002Fconf.d\u002Fredirects.inc;\n}\n","nginx",[47,323,324,329,334,339,344,349,354,359,364,368,373,377,382,387,392,397,402,408,414,419,425,431,436,442,448],{"__ignoreMap":63},[67,325,326],{"class":69,"line":70},[67,327,328],{},"server {\n",[67,330,331],{"class":69,"line":76},[67,332,333],{},"  listen 8080;\n",[67,335,336],{"class":69,"line":82},[67,337,338],{},"  server_name _;\n",[67,340,341],{"class":69,"line":88},[67,342,343],{},"  root \u002Fusr\u002Fshare\u002Fnginx\u002Fhtml;\n",[67,345,346],{"class":69,"line":94},[67,347,348],{},"  gzip_static on;\n",[67,350,351],{"class":69,"line":100},[67,352,353],{},"  gzip_vary on;\n",[67,355,356],{"class":69,"line":106},[67,357,358],{},"  absolute_redirect off;      # behind a proxy, keep redirects relative\n",[67,360,361],{"class":69,"line":112},[67,362,363],{},"  server_tokens off;\n",[67,365,366],{"class":69,"line":118},[67,367,128],{"emptyLinePlaceholder":127},[67,369,370],{"class":69,"line":124},[67,371,372],{},"  location = \u002Fhealthz { access_log off; return 200 \"ok\\n\"; }\n",[67,374,375],{"class":69,"line":131},[67,376,128],{"emptyLinePlaceholder":127},[67,378,379],{"class":69,"line":137},[67,380,381],{},"  location \u002F_astro\u002F {\n",[67,383,384],{"class":69,"line":143},[67,385,386],{},"    add_header Cache-Control \"public, max-age=31536000, immutable\" always;\n",[67,388,389],{"class":69,"line":149},[67,390,391],{},"    add_header X-Content-Type-Options \"nosniff\" always;\n",[67,393,394],{"class":69,"line":155},[67,395,396],{},"    try_files $uri =404;\n",[67,398,399],{"class":69,"line":161},[67,400,401],{},"  }\n",[67,403,405],{"class":69,"line":404},17,[67,406,407],{},"  location \u002F {\n",[67,409,411],{"class":69,"line":410},18,[67,412,413],{},"    add_header Cache-Control \"public, max-age=0, must-revalidate\" always;\n",[67,415,417],{"class":69,"line":416},19,[67,418,391],{},[67,420,422],{"class":69,"line":421},20,[67,423,424],{},"    add_header Referrer-Policy \"strict-origin-when-cross-origin\" always;\n",[67,426,428],{"class":69,"line":427},21,[67,429,430],{},"    try_files $uri $uri\u002Findex.html =404;\n",[67,432,434],{"class":69,"line":433},22,[67,435,401],{},[67,437,439],{"class":69,"line":438},23,[67,440,441],{},"  error_page 404 \u002F404.html;\n",[67,443,445],{"class":69,"line":444},24,[67,446,447],{},"  include \u002Fetc\u002Fnginx\u002Fconf.d\u002Fredirects.inc;\n",[67,449,451],{"class":69,"line":450},25,[67,452,453],{},"}\n",[14,455,456,457,460,461,464,465,468,469,472,473,477,478,30],{},"Two container-specific settings: ",[47,458,459],{},"absolute_redirect off"," makes Nginx's own redirects (for example, adding a trailing slash) relative, so they do not leak the internal ",[47,462,463],{},":8080"," port behind the ingress; and the dedicated ",[47,466,467],{},"\u002Fhealthz"," location gives the platform a cheap health endpoint that is not a real page. Security headers are repeated in each location because of Nginx's ",[47,470,471],{},"add_header"," inheritance rule, as explained in ",[21,474,476],{"href":475},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-for-static-sites-in-nginx\u002F","Cache-Control Headers for Static Sites in Nginx",". Redirects are generated at build time into ",[47,479,480],{},"redirects.inc",[32,482,484],{"id":483},"step-3-run-read-only-and-unprivileged","Step 3: Run Read-Only and Unprivileged",[14,486,487,488,491],{},"In Kubernetes, the pod runs with a read-only root filesystem and no privileges; Nginx only needs a few writable temp directories, mounted as ",[47,489,490],{},"emptyDir"," volumes:",[58,493,497],{"className":494,"code":495,"language":496,"meta":63,"style":63},"language-yaml shiki shiki-themes github-light github-dark","securityContext: { runAsNonRoot: true, runAsUser: 101, readOnlyRootFilesystem: true, allowPrivilegeEscalation: false,\n                   capabilities: { drop: [ALL] } }\nvolumeMounts:\n  - { name: tmp, mountPath: \u002Ftmp }\n  - { name: cache, mountPath: \u002Fvar\u002Fcache\u002Fnginx }\nreadinessProbe: { httpGet: { path: \u002Fhealthz, port: 8080 }, periodSeconds: 5 }\nresources: { requests: { cpu: 20m, memory: 16Mi }, limits: { memory: 64Mi } }\n","yaml",[47,498,499,552,572,580,606,628,668],{"__ignoreMap":63},[67,500,501,505,509,512,515,519,522,525,527,530,532,535,537,539,541,544,546,549],{"class":69,"line":70},[67,502,504],{"class":503},"s9eBZ","securityContext",[67,506,508],{"class":507},"sVt8B",": { ",[67,510,511],{"class":503},"runAsNonRoot",[67,513,514],{"class":507},": ",[67,516,518],{"class":517},"sj4cs","true",[67,520,521],{"class":507},", ",[67,523,524],{"class":503},"runAsUser",[67,526,514],{"class":507},[67,528,529],{"class":517},"101",[67,531,521],{"class":507},[67,533,534],{"class":503},"readOnlyRootFilesystem",[67,536,514],{"class":507},[67,538,518],{"class":517},[67,540,521],{"class":507},[67,542,543],{"class":503},"allowPrivilegeEscalation",[67,545,514],{"class":507},[67,547,548],{"class":517},"false",[67,550,551],{"class":507},",\n",[67,553,554,557,559,562,565,569],{"class":69,"line":76},[67,555,556],{"class":503},"                   capabilities",[67,558,508],{"class":507},[67,560,561],{"class":503},"drop",[67,563,564],{"class":507},": [",[67,566,568],{"class":567},"sZZnC","ALL",[67,570,571],{"class":507},"] } }\n",[67,573,574,577],{"class":69,"line":82},[67,575,576],{"class":503},"volumeMounts",[67,578,579],{"class":507},":\n",[67,581,582,585,588,590,593,595,598,600,603],{"class":69,"line":88},[67,583,584],{"class":507},"  - { ",[67,586,587],{"class":503},"name",[67,589,514],{"class":507},[67,591,592],{"class":567},"tmp",[67,594,521],{"class":507},[67,596,597],{"class":503},"mountPath",[67,599,514],{"class":507},[67,601,602],{"class":567},"\u002Ftmp",[67,604,605],{"class":507}," }\n",[67,607,608,610,612,614,617,619,621,623,626],{"class":69,"line":94},[67,609,584],{"class":507},[67,611,587],{"class":503},[67,613,514],{"class":507},[67,615,616],{"class":567},"cache",[67,618,521],{"class":507},[67,620,597],{"class":503},[67,622,514],{"class":507},[67,624,625],{"class":567},"\u002Fvar\u002Fcache\u002Fnginx",[67,627,605],{"class":507},[67,629,630,633,635,638,640,642,644,646,648,651,653,656,659,662,664,666],{"class":69,"line":100},[67,631,632],{"class":503},"readinessProbe",[67,634,508],{"class":507},[67,636,637],{"class":503},"httpGet",[67,639,508],{"class":507},[67,641,225],{"class":503},[67,643,514],{"class":507},[67,645,467],{"class":567},[67,647,521],{"class":507},[67,649,650],{"class":503},"port",[67,652,514],{"class":507},[67,654,655],{"class":517},"8080",[67,657,658],{"class":507}," }, ",[67,660,661],{"class":503},"periodSeconds",[67,663,514],{"class":507},[67,665,302],{"class":517},[67,667,605],{"class":507},[67,669,670,673,675,678,680,683,685,688,690,693,695,698,700,703,705,707,709,712],{"class":69,"line":106},[67,671,672],{"class":503},"resources",[67,674,508],{"class":507},[67,676,677],{"class":503},"requests",[67,679,508],{"class":507},[67,681,682],{"class":503},"cpu",[67,684,514],{"class":507},[67,686,687],{"class":567},"20m",[67,689,521],{"class":507},[67,691,692],{"class":503},"memory",[67,694,514],{"class":507},[67,696,697],{"class":567},"16Mi",[67,699,658],{"class":507},[67,701,702],{"class":503},"limits",[67,704,508],{"class":507},[67,706,692],{"class":503},[67,708,514],{"class":507},[67,710,711],{"class":567},"64Mi",[67,713,714],{"class":507}," } }\n",[14,716,717],{},"A read-only root filesystem means even a compromised Nginx process cannot modify the site's files. The resource requests reflect measured use: about 6 MB of memory per pod at idle and a few millicores of CPU, since the ingress and the CDN in front absorb most traffic.",[182,719,720,838],{},[185,721,193,726,193,729,193,732,193,735],{"viewBox":722,"role":188,"ariaLabelledBy":723,"xmlns":192},"0 0 760 248",[724,725],"dockngx-size-title","dockngx-size-desc",[195,727,728],{"id":724},"Image size and container start time for three Dockerfile approaches",[199,730,731],{"id":725},"Paired bars. A single-stage image based on node 20 was 1,100 megabytes and started in 2.4 seconds. A multi-stage image on the full nginx base was 196 megabytes and started in 0.4 seconds. A multi-stage image on nginx unprivileged alpine slim was 47 megabytes and started in 0.2 seconds.",[203,733],{"x":205,"y":205,"width":206,"height":734,"fill":208},"248",[210,736,213,737,213,747,213,751,213,758,213,762,213,766,213,770,213,774,213,778,213,781,213,784,213,789,213,793,213,798,213,804,213,810,213,814,213,819,213,824,213,828,213,833,193],{"style":212},[203,738],{"x":739,"y":740,"width":741,"height":742,"rx":743,"fill":744,"opacity":745,"stroke":744,"style":746},"244.3","50.0","14.0","12.0","2","#1982c4","0.3","stroke-width:1px",[203,748],{"x":749,"y":740,"width":741,"height":742,"rx":743,"fill":242,"opacity":750,"stroke":244,"style":746},"396.3","0.4",[203,752],{"x":753,"y":754,"width":755,"height":756,"rx":757,"fill":744,"opacity":745,"stroke":744,"style":746},"230.0","82.0","463.8","16.0","3",[203,759],{"x":753,"y":760,"width":761,"height":756,"rx":757,"fill":242,"opacity":750,"stroke":244,"style":746},"102.0","101.2",[203,763],{"x":753,"y":764,"width":765,"height":756,"rx":757,"fill":744,"opacity":745,"stroke":744,"style":746},"134.0","82.6",[203,767],{"x":753,"y":768,"width":769,"height":756,"rx":757,"fill":242,"opacity":750,"stroke":244,"style":746},"154.0","16.9",[203,771],{"x":753,"y":772,"width":773,"height":756,"rx":757,"fill":744,"opacity":745,"stroke":744,"style":746},"186.0","19.8",[203,775],{"x":753,"y":776,"width":777,"height":756,"rx":757,"fill":242,"opacity":750,"stroke":244,"style":746},"206.0","8.4",[225,779],{"d":780,"fill":228,"stroke":229,"style":223},"M230.0 78.0 L230.0 228.0",[246,782,783],{"x":248,"y":249,"fill":250,"style":251},"Image size and startup",[246,785,788],{"x":786,"y":217,"fill":229,"style":787},"264.3","font-size:12px;text-anchor:start","Image size (MB)",[246,790,792],{"x":791,"y":217,"fill":229,"style":787},"416.3","Start to healthy",[246,794,797],{"x":795,"y":796,"fill":250,"style":787},"20.0","105.2","Single-stage node:20",[246,799,803],{"x":800,"y":801,"fill":250,"style":802},"700.8","94.5","font-size:11.5px;text-anchor:start;font-weight:700","1100",[246,805,809],{"x":806,"y":807,"fill":808,"style":802},"338.2","114.5","#3f6410","2.4 s",[246,811,813],{"x":795,"y":812,"fill":250,"style":787},"157.2","Multi-stage, nginx full",[246,815,818],{"x":816,"y":817,"fill":250,"style":802},"319.6","146.5","196",[246,820,823],{"x":821,"y":822,"fill":808,"style":802},"253.9","166.5","0.4 s",[246,825,827],{"x":795,"y":826,"fill":250,"style":787},"209.2","Multi-stage, alpine-slim",[246,829,832],{"x":830,"y":831,"fill":250,"style":802},"256.8","198.5","47",[246,834,837],{"x":835,"y":836,"fill":808,"style":802},"245.4","218.5","0.2 s",[310,839,840],{},"Sizes from docker image ls; start time to first successful health check, median of ten starts on the cluster.",[32,842,844],{"id":843},"step-4-build-and-ship","Step 4: Build and Ship",[14,846,847],{},"The CI job builds with BuildKit's cache mounts, tags the image with the commit SHA, scans it and pushes:",[58,849,853],{"className":850,"code":851,"language":852,"meta":63,"style":63},"language-sh shiki shiki-themes github-light github-dark","docker buildx build --cache-from type=registry,ref=$REG\u002Fdocs:cache --cache-to type=registry,ref=$REG\u002Fdocs:cache,mode=max \\\n  -t $REG\u002Fdocs:$GITHUB_SHA --push .\ntrivy image --exit-code 1 --severity HIGH,CRITICAL $REG\u002Fdocs:$GITHUB_SHA\n","sh",[47,854,855,892,912],{"__ignoreMap":63},[67,856,857,861,864,867,870,873,876,879,882,884,886,889],{"class":69,"line":70},[67,858,860],{"class":859},"sScJk","docker",[67,862,863],{"class":567}," buildx",[67,865,866],{"class":567}," build",[67,868,869],{"class":517}," --cache-from",[67,871,872],{"class":567}," type=registry,ref=",[67,874,875],{"class":507},"$REG",[67,877,878],{"class":567},"\u002Fdocs:cache",[67,880,881],{"class":517}," --cache-to",[67,883,872],{"class":567},[67,885,875],{"class":507},[67,887,888],{"class":567},"\u002Fdocs:cache,mode=max",[67,890,891],{"class":517}," \\\n",[67,893,894,897,900,903,906,909],{"class":69,"line":76},[67,895,896],{"class":517},"  -t",[67,898,899],{"class":507}," $REG",[67,901,902],{"class":567},"\u002Fdocs:",[67,904,905],{"class":507},"$GITHUB_SHA ",[67,907,908],{"class":517},"--push",[67,910,911],{"class":567}," .\n",[67,913,914,917,920,923,926,929,932,934,936],{"class":69,"line":82},[67,915,916],{"class":859},"trivy",[67,918,919],{"class":567}," image",[67,921,922],{"class":517}," --exit-code",[67,924,925],{"class":517}," 1",[67,927,928],{"class":517}," --severity",[67,930,931],{"class":567}," HIGH,CRITICAL",[67,933,899],{"class":507},[67,935,902],{"class":567},[67,937,938],{"class":507},"$GITHUB_SHA\n",[14,940,941],{},"Deploying is a change to the image tag in the cluster's manifest; Kubernetes rolls out new pods and keeps old ones until the new ones pass readiness, so there is no moment without a working site. Rollback is setting the previous tag. Because the image contains the server configuration, staging and production run byte-identical configurations — a header or redirect change is tested in staging exactly as it will run in production.",[32,943,945],{"id":944},"request-path-in-the-cluster","Request Path in the Cluster",[182,947,948,1047],{},[185,949,193,954,193,957,193,960,193,963,193,1040],{"viewBox":950,"role":188,"ariaLabelledBy":951,"xmlns":192},"0 0 760 152",[952,953],"dockngx-path-title","dockngx-path-desc",[195,955,956],{"id":952},"Request path from a reader to the static site container in the cluster",[199,958,959],{"id":953},"Five steps. The reader connects over HTTPS to the CDN, which serves most requests from cache. Cache misses go to the cluster's ingress controller, which terminates TLS with a managed certificate. The ingress routes by hostname to the docs service. The service load-balances across two Nginx pods on port 8080. Nginx serves the file or the precompressed copy with the site's headers.",[203,961],{"x":205,"y":205,"width":206,"height":962,"fill":208},"152",[210,964,213,965,213,970,213,973,213,977,213,980,213,983,213,986,213,989,213,992,213,995,213,998,213,1003,213,1007,213,1011,213,1016,213,1020,213,1023,213,1026,213,1030,213,1033,213,1037,193],{"style":212},[203,966],{"x":795,"y":967,"width":968,"height":969,"rx":220,"fill":242,"opacity":243,"stroke":244,"style":223},"64.0","116.8","71.5",[203,971],{"x":972,"y":967,"width":968,"height":969,"rx":220,"fill":744,"opacity":235,"stroke":744,"style":223},"170.8",[225,974],{"d":975,"fill":228,"stroke":229,"style":976},"M138.8 99.8 L166.8 99.8","stroke-width:2px;marker-end:url(#dockngx-path-arrow)",[203,978],{"x":979,"y":967,"width":968,"height":969,"rx":220,"fill":744,"opacity":235,"stroke":744,"style":223},"321.6",[225,981],{"d":982,"fill":228,"stroke":229,"style":976},"M289.6 99.8 L317.6 99.8",[203,984],{"x":985,"y":967,"width":968,"height":969,"rx":220,"fill":234,"opacity":235,"stroke":234,"style":223},"472.4",[225,987],{"d":988,"fill":228,"stroke":229,"style":976},"M440.4 99.8 L468.4 99.8",[203,990],{"x":991,"y":967,"width":968,"height":969,"rx":220,"fill":221,"stroke":222,"style":223},"623.2",[225,993],{"d":994,"fill":228,"stroke":229,"style":976},"M591.2 99.8 L619.2 99.8",[246,996,997],{"x":248,"y":249,"fill":250,"style":251},"How a request reaches the container",[246,999,1002],{"x":1000,"y":1001,"fill":250,"style":257},"78.4","90.4","CDN",[246,1004,1006],{"x":1000,"y":1005,"fill":229,"style":262},"107.3","most requests",[246,1008,1010],{"x":1000,"y":1009,"fill":229,"style":262},"121.6","end here",[246,1012,1015],{"x":1013,"y":1014,"fill":250,"style":257},"229.2","97.5","Ingress",[246,1017,1019],{"x":1013,"y":1018,"fill":229,"style":262},"114.4","TLS terminated",[246,1021,1022],{"x":248,"y":1014,"fill":250,"style":257},"Service",[246,1024,1025],{"x":248,"y":1018,"fill":229,"style":262},"by hostname",[246,1027,1029],{"x":1028,"y":1014,"fill":250,"style":257},"530.8","Nginx pods ×2",[246,1031,1032],{"x":1028,"y":1018,"fill":229,"style":262},"port 8080",[246,1034,1036],{"x":1035,"y":1014,"fill":250,"style":257},"681.6","File + headers",[246,1038,1039],{"x":1035,"y":1018,"fill":229,"style":262},"from the image",[295,1041,213,1042,193],{},[298,1043,305,1045,213],{"id":1044,"viewBox":301,"refX":220,"refY":302,"markerWidth":303,"markerHeight":303,"orient":304},"dockngx-path-arrow",[225,1046],{"d":308,"fill":229},[310,1048,1049],{},"TLS, certificates and load balancing live in the platform; the container only serves files.",[14,1051,1052],{},"Two replicas run at all times, spread across nodes by a pod anti-affinity rule, so a node failure or a rollout never leaves the site without a serving pod. The CDN in front caches HTML for a short time and assets for a year, so the pods themselves serve a few requests per second; a horizontal autoscaler was considered and judged unnecessary at that load.",[14,1054,1055,1056,1059],{},"Logs go to standard output in Nginx's combined format, which the cluster's log collector already parses. The ingress adds an ",[47,1057,1058],{},"X-Request-ID"," header that Nginx logs, so a single request can be followed from the CDN's logs through the ingress to the pod when diagnosing a problem.",[32,1061,1063],{"id":1062},"measured-impact","Measured Impact",[1065,1066,1067,1086],"table",{},[1068,1069,1070],"thead",{},[1071,1072,1073,1077,1080,1083],"tr",{},[1074,1075,1076],"th",{},"Measure",[1074,1078,1079],{},"Previous image (single-stage)",[1074,1081,1082],{},"New image",[1074,1084,1085],{},"Tool",[1087,1088,1089,1106,1120,1131,1144,1164],"tbody",{},[1071,1090,1091,1095,1098,1101],{},[1092,1093,1094],"td",{},"Image size",[1092,1096,1097],{},"1.1 GB",[1092,1099,1100],{},"47 MB",[1092,1102,1103],{},[47,1104,1105],{},"docker image ls",[1071,1107,1108,1111,1114,1117],{},[1092,1109,1110],{},"Pull time on a new node",[1092,1112,1113],{},"38 s",[1092,1115,1116],{},"2 s",[1092,1118,1119],{},"Kubelet events",[1071,1121,1122,1124,1126,1128],{},[1092,1123,792],{},[1092,1125,809],{},[1092,1127,837],{},[1092,1129,1130],{},"Readiness probe timing",[1071,1132,1133,1136,1139,1141],{},[1092,1134,1135],{},"High\u002Fcritical CVEs in image",[1092,1137,1138],{},"23 (Node, build tools)",[1092,1140,205],{},[1092,1142,1143],{},"Trivy",[1071,1145,1146,1149,1156,1159],{},[1092,1147,1148],{},"Memory per pod, idle",[1092,1150,1151,1152,1155],{},"120 MB (",[47,1153,1154],{},"npx serve",")",[1092,1157,1158],{},"6 MB",[1092,1160,1161],{},[47,1162,1163],{},"kubectl top",[1071,1165,1166,1169,1172,1175],{},[1092,1167,1168],{},"Runs as root",[1092,1170,1171],{},"Yes",[1092,1173,1174],{},"No (UID 101, read-only FS)",[1092,1176,1177],{},"Pod spec",[14,1179,1180,1181,1183,1184,1186],{},"The previous image had used ",[47,1182,1154],{}," inside a Node image to serve ",[47,1185,49],{},", which carried the whole build toolchain into production along with its vulnerabilities.",[14,1188,1189],{},"Pull time mattered most during node replacements: with the small image, a new node served the site within a few seconds of joining the cluster, instead of waiting over half a minute for a gigabyte to download.",[32,1191,1193],{"id":1192},"pitfalls-rollback","Pitfalls & Rollback",[37,1195,1196,1203,1209,1217,1223],{},[40,1197,1198,1202],{},[1199,1200,1201],"strong",{},"Single-stage images."," The build toolchain ends up in production with its CVEs.",[40,1204,1205,1208],{},[1199,1206,1207],{},"Root and writable filesystems."," Use the unprivileged image and a read-only root.",[40,1210,1211,1214,1215,30],{},[1199,1212,1213],{},"Absolute redirects behind a proxy."," They expose the internal port; set ",[47,1216,459],{},[40,1218,1219,1222],{},[1199,1220,1221],{},"Health checks against real pages."," Use a dedicated endpoint so checks do not distort logs or caches.",[40,1224,1225,1228],{},[1199,1226,1227],{},"Rollback:"," deploy the previous image tag; the cluster rolls back pod by pod with no downtime.",[32,1230,1232],{"id":1231},"conclusion","Conclusion",[14,1234,1235],{},"A static site in a container should be a small Nginx image with the built files and the server configuration, nothing else. A multi-stage build, the unprivileged slim base, precompressed files, a read-only filesystem and a dedicated health endpoint took this site's image from 1.1 GB with 23 high-severity CVEs to 47 MB with none, starting in a fifth of a second.",[32,1237,1239],{"id":1238},"faq","FAQ",[1241,1242,1244],"h3",{"id":1243},"why-put-a-static-site-in-a-container-at-all","Why put a static site in a container at all?",[14,1246,1247],{},"Because the platform you deploy to runs containers: Kubernetes, a container platform such as Cloud Run or Fly.io, or an internal hosting system that expects images. A container also bundles the server configuration with the site, so headers, redirects and caching travel with every deploy and are identical in staging and production.",[1241,1249,1251],{"id":1250},"how-small-can-a-static-site-container-be","How small can a static site container be?",[14,1253,1254],{},"The nginx alpine-slim base image is about 12 megabytes. With the site's files added, the image in this guide was 47 megabytes, most of it images. A multi-stage build keeps Node, the generator and node_modules out of the final image, which otherwise adds hundreds of megabytes.",[1241,1256,1258],{"id":1257},"can-nginx-run-as-a-non-root-user-in-a-container","Can Nginx run as a non-root user in a container?",[14,1260,1261],{},"Yes, by listening on an unprivileged port such as 8080 and moving the pid file and temporary directories to writable locations. The official nginx-unprivileged image is preconfigured this way. Running as non-root limits what a compromise of the server process could do.",[1241,1263,1265],{"id":1264},"where-should-tls-terminate-for-a-containerised-static-site","Where should TLS terminate for a containerised static site?",[14,1267,1268],{},"Usually outside the container, at the platform's load balancer, ingress controller or reverse proxy, which manages certificates for many services. The container serves plain HTTP on an internal port. Terminating TLS inside every container means managing certificates per container, which platforms are designed to avoid.",[32,1270,1272],{"id":1271},"related","Related",[37,1274,1275,1284,1289,1296,1303],{},[40,1276,1277,1280,1281,1283],{},[1199,1278,1279],{},"Parent:"," ",[21,1282,24],{"href":23}," — running your own hosting.",[40,1285,1286,1288],{},[21,1287,29],{"href":28}," — the Nginx configuration in depth.",[40,1290,1291,1295],{},[21,1292,1294],{"href":1293},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-in-docker-for-reproducible-builds\u002F","Running Jekyll in Docker for Reproducible Builds"," — containers for the build side.",[40,1297,1298,1302],{},[21,1299,1301],{"href":1300},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines\u002F","Auditing npm Dependencies in SSG Pipelines"," — keeping the build stage clean too.",[40,1304,1305,1309],{},[21,1306,1308],{"href":1307},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites\u002F","Nginx vs Caddy for Serving Static Sites"," — the alternative server.",[1311,1312,1313],"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 .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}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}",{"title":63,"searchDepth":76,"depth":76,"links":1315},[1316,1317,1318,1319,1320,1321,1322,1323,1324,1325,1331],{"id":34,"depth":76,"text":35},{"id":55,"depth":76,"text":56},{"id":315,"depth":76,"text":316},{"id":483,"depth":76,"text":484},{"id":843,"depth":76,"text":844},{"id":944,"depth":76,"text":945},{"id":1062,"depth":76,"text":1063},{"id":1192,"depth":76,"text":1193},{"id":1231,"depth":76,"text":1232},{"id":1238,"depth":76,"text":1239,"children":1326},[1327,1328,1329,1330],{"id":1243,"depth":82,"text":1244},{"id":1250,"depth":82,"text":1251},{"id":1257,"depth":82,"text":1258},{"id":1264,"depth":82,"text":1265},{"id":1271,"depth":76,"text":1272},[1333,1336,1339,1340],{"name":1334,"item":1335},"Home","\u002F",{"name":1337,"item":1338},"Production-Ready Deployment & CI\u002FCD for SSGs","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":24,"item":23},{"name":5,"item":1341},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-from-a-docker-container-with-nginx\u002F","2026-10-02","Package a static site in a small Nginx container: multi-stage build, non-root user, read-only filesystem, health checks and running behind a proxy.","md",[1346,1347,1348,1349],{"q":1244,"a":1247},{"q":1251,"a":1254},{"q":1258,"a":1261},{"q":1265,"a":1268},{},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-from-a-docker-container-with-nginx",{"title":5,"description":1343},"production-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-from-a-docker-container-with-nginx\u002Findex","article","VymPGXyapOMbgnma4cDH8k1vC0k0arW5N0VVww5FODI",[1357,1360,1363,1366,1369,1372,1375,1378,1381,1384,1387,1390,1393,1396,1399,1402,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,1569,1572,1575,1578,1581,1584,1587,1590,1593,1596,1599,1602,1605,1608,1611,1614,1617,1620,1623,1626,1629,1632,1635,1638,1641,1644,1647,1650,1653,1656,1659,1662,1665,1668,1671,1674,1677,1680,1683,1686,1689,1692,1695,1698,1701,1704,1707,1710,1713,1716,1719,1722,1725,1728,1731,1734,1737,1740,1743,1746,1749,1752,1755,1758,1760,1763,1766,1769,1772,1775,1778,1781,1784,1787,1790,1793,1796,1799,1802,1805,1808,1811,1814,1817,1820,1823,1826,1829,1832,1835,1838,1841,1844,1847,1850,1853,1856,1859,1862,1865,1868,1871,1874,1877,1880,1883,1886,1889,1892,1895,1898,1901,1904,1907,1910,1913,1916,1919,1922,1925,1928,1931,1934,1937,1940,1943,1946,1949,1952,1955,1958,1961,1964,1967,1970,1973,1976,1979,1982,1985,1988,1991,1994,1997,2000,2003,2006,2009,2012,2015,2018,2021,2024,2027,2030,2033,2036,2039,2042,2045,2048,2051,2054,2057,2060,2063,2066,2069,2072,2075,2078,2081,2084,2087,2090,2093,2096,2099,2102,2105,2108,2111,2114,2117,2120,2123,2126,2129,2132,2135,2138,2141,2144,2147,2150,2153,2156,2159,2162,2165,2168,2171,2174,2177,2180,2183,2186,2189,2192,2195,2198,2201,2204,2207,2210,2213,2216,2219,2222,2225,2228,2231,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,2373,2376,2379,2382,2385,2388,2391,2394,2397,2400,2403,2406,2409,2411,2414,2417,2420,2423,2425,2427,2428,2431,2434,2436,2439,2442,2445,2448,2451,2454,2457,2460,2463,2466,2469,2472,2475,2478,2481,2484,2487,2490,2493],{"path":1358,"title":1359},"\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":1361,"title":1362},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites\u002Faccessible-dark-mode-toggles-for-static-sites","Accessible Dark Mode Toggles for Static Sites",{"path":1364,"title":1365},"\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":1367,"title":1368},"\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":1370,"title":1371},"\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":1373,"title":1374},"\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":1376,"title":1377},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1379,"title":1380},"\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":1382,"title":1383},"\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":1385,"title":1386},"\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":1388,"title":1389},"\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":1391,"title":1392},"\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":1394,"title":1395},"\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":1397,"title":1398},"\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":1400,"title":1401},"\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":1403,"title":1404},"\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":1406,"title":1407},"\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":1409,"title":1410},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1412,"title":1413},"\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":1415,"title":1416},"\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":1418,"title":1419},"\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":1421,"title":1422},"\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":1424,"title":1425},"\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":1427,"title":1428},"\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":1430,"title":1431},"\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":1433,"title":1434},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1436,"title":1437},"\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":1439,"title":1440},"\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":1442,"title":1443},"\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":1445,"title":1446},"\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":1448,"title":1449},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1451,"title":1452},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1454,"title":1455},"\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":1457,"title":1458},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1460,"title":1461},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1463,"title":1464},"\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":1466,"title":1467},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1469,"title":1470},"\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":1472,"title":1473},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1475,"title":1476},"\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":1478,"title":1479},"\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":1481,"title":1482},"\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":1484,"title":1485},"\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":1487,"title":1488},"\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":1490,"title":1491},"\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":1493,"title":1494},"\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":1496,"title":1497},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1499,"title":1500},"\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":1502,"title":1503},"\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":1505,"title":1506},"\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":1508,"title":1509},"\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":1511,"title":1512},"\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":1514,"title":1515},"\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":1517,"title":1518},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1520,"title":1521},"\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":1523,"title":1524},"\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":1526,"title":1527},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1529,"title":1530},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1532,"title":1533},"\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":1535,"title":1536},"\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":1538,"title":1539},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1541,"title":1542},"\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":1544,"title":1545},"\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":1547,"title":1548},"\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":1550,"title":1551},"\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":1553,"title":1554},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions","Deploying Jekyll with GitHub Actions",{"path":1556,"title":1557},"\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":1559,"title":1560},"\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":1562,"title":1563},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1565,"title":1566},"\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":1568,"title":1294},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-in-docker-for-reproducible-builds",{"path":1570,"title":1571},"\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":1573,"title":1574},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1576,"title":1577},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":1579,"title":1580},"\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":1582,"title":1583},"\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":1585,"title":1586},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1588,"title":1589},"\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":1591,"title":1592},"\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":1594,"title":1595},"\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":1597,"title":1598},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1600,"title":1601},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1603,"title":1604},"\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":1606,"title":1607},"\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":1609,"title":1610},"\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":1612,"title":1613},"\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":1615,"title":1616},"\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":1618,"title":1619},"\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":1621,"title":1622},"\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":1624,"title":1625},"\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":1627,"title":1628},"\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":1630,"title":1631},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1633,"title":1634},"\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":1636,"title":1637},"\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":1639,"title":1640},"\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":1642,"title":1643},"\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":1645,"title":1646},"\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":1648,"title":1649},"\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":1651,"title":1652},"\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":1654,"title":1655},"\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":1657,"title":1658},"\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":1660,"title":1661},"\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":1663,"title":1664},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1666,"title":1667},"\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":1669,"title":1670},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1672,"title":1673},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1675,"title":1676},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1678,"title":1679},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1681,"title":1682},"\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":1684,"title":1685},"\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":1687,"title":1688},"\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":1690,"title":1691},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1693,"title":1694},"\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":1696,"title":1697},"\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":1699,"title":1700},"\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":1702,"title":1703},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1705,"title":1706},"\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":1708,"title":1709},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1711,"title":1712},"\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":1714,"title":1715},"\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":1717,"title":1718},"\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":1720,"title":1721},"\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":1723,"title":1724},"\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":1726,"title":1727},"\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":1729,"title":1730},"\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":1732,"title":1733},"\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":1735,"title":1736},"\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":1738,"title":1739},"\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":1741,"title":1742},"\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":1744,"title":1745},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1747,"title":1748},"\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":1750,"title":1751},"\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":1753,"title":1754},"\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":1756,"title":1757},"\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":1759,"title":476},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-for-static-sites-in-nginx",{"path":1761,"title":1762},"\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":1764,"title":1765},"\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":1767,"title":1768},"\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":1770,"title":1771},"\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":1773,"title":1774},"\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":1776,"title":1777},"\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":1779,"title":1780},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1782,"title":1783},"\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":1785,"title":1786},"\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":1788,"title":1789},"\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":1791,"title":1792},"\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":1794,"title":1795},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1797,"title":1798},"\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":1800,"title":1801},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ffixing-missing-tailwind-classes-in-production-builds","Fixing Missing Tailwind Classes in Production Builds",{"path":1803,"title":1804},"\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":1806,"title":1807},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":1809,"title":1810},"\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":1812,"title":1813},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fkeeping-tailwind-css-output-small-on-static-sites","Keeping Tailwind CSS Output Small on Static Sites",{"path":1815,"title":1816},"\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":1818,"title":1819},"\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":1821,"title":1822},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Fpurging-unused-css-with-tailwind-and-lightningcss","Purging Unused CSS with Tailwind and Lightning CSS",{"path":1824,"title":1825},"\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":1827,"title":1828},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization\u002Ftailwind-v4-in-astro-without-postcss-plugins","Tailwind v4 in Astro Without PostCSS Plugins",{"path":1830,"title":1831},"\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":1833,"title":1834},"\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":1836,"title":1837},"\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":1839,"title":1840},"\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":1842,"title":1843},"\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":1845,"title":1846},"\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":1848,"title":1849},"\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":1851,"title":1852},"\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":1854,"title":1855},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1857,"title":1858},"\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":1860,"title":1861},"\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":1863,"title":1864},"\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":1866,"title":1867},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":1869,"title":1870},"\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":1872,"title":1873},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1875,"title":1876},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1878,"title":1879},"\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":1881,"title":1882},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1884,"title":1885},"\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":1887,"title":1888},"\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":1890,"title":1891},"\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":1893,"title":1894},"\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":1896,"title":1897},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":1899,"title":1900},"\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":1902,"title":1903},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":1905,"title":1906},"\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":1908,"title":1909},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":1911,"title":1912},"\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":1914,"title":1915},"\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":1917,"title":1918},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1920,"title":1921},"\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":1923,"title":1924},"\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":1926,"title":1927},"\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":1929,"title":1930},"\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":1932,"title":1933},"\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":1935,"title":1936},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1938,"title":1939},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1941,"title":1942},"\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":1944,"title":1945},"\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":1947,"title":1948},"\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":1950,"title":1951},"\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":1953,"title":1954},"\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":1956,"title":1957},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1959,"title":1960},"\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":1962,"title":1963},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":1965,"title":1966},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1968,"title":1969},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":1971,"title":1972},"\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":1974,"title":1975},"\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":1977,"title":1978},"\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":1980,"title":1981},"\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":1983,"title":1984},"\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":1986,"title":1987},"\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":1989,"title":1990},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1992,"title":1993},"\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":1995,"title":1996},"\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":1998,"title":1999},"\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":2001,"title":2002},"\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":2004,"title":2005},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":2007,"title":2008},"\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":2010,"title":2011},"\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":2013,"title":2014},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":2016,"title":2017},"\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":2019,"title":2020},"\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":2022,"title":2023},"\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":2025,"title":2026},"\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":2028,"title":2029},"\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":2031,"title":2032},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2034,"title":2035},"\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":2037,"title":2038},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2040,"title":2041},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2043,"title":2044},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2046,"title":2047},"\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":2049,"title":2050},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2052,"title":2053},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2055,"title":2056},"\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":2058,"title":2059},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2061,"title":2062},"\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":2064,"title":2065},"\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":2067,"title":2068},"\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":2070,"title":2071},"\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":2073,"title":2074},"\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":2076,"title":2077},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2079,"title":2080},"\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":2082,"title":2083},"\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":2085,"title":2086},"\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":2088,"title":2089},"\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":2091,"title":2092},"\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":2094,"title":2095},"\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":2097,"title":2098},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2100,"title":2101},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2103,"title":2104},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2106,"title":2107},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2109,"title":2110},"\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":2112,"title":2113},"\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":2115,"title":2116},"\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":2118,"title":2119},"\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":2121,"title":2122},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2124,"title":2125},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2127,"title":2128},"\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":2130,"title":2131},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2133,"title":2134},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2136,"title":2137},"\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":2139,"title":2140},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2142,"title":2143},"\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":2145,"title":2146},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2148,"title":2149},"\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":2151,"title":2152},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2154,"title":2155},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2157,"title":2158},"\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":2160,"title":2161},"\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":2163,"title":2164},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2166,"title":2167},"\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":2169,"title":2170},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2172,"title":2173},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2175,"title":2176},"\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":2178,"title":2179},"\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":2181,"title":2182},"\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":2184,"title":2185},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2187,"title":2188},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2190,"title":2191},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2193,"title":2194},"\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":2196,"title":2197},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2199,"title":2200},"\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":2202,"title":2203},"\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":2205,"title":2206},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2208,"title":2209},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2211,"title":2212},"\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":2214,"title":2215},"\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":2217,"title":2218},"\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":2220,"title":2221},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2223,"title":2224},"\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":2226,"title":2227},"\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":2229,"title":2230},"\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":2232,"title":1337},"\u002Fproduction-ready-deployment-cicd-workflows",{"path":2234,"title":2235},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2237,"title":2238},"\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":2240,"title":2241},"\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":2243,"title":2244},"\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":2246,"title":2247},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2249,"title":2250},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2252,"title":2253},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2255,"title":2256},"\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":2258,"title":2259},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2261,"title":2262},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2264,"title":2265},"\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":2267,"title":2268},"\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":2270,"title":2271},"\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":2273,"title":2274},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2276,"title":2277},"\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":2279,"title":2280},"\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":2282,"title":2283},"\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":2285,"title":2286},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2288,"title":2289},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2291,"title":2292},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2294,"title":2295},"\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":2297,"title":2298},"\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":2300,"title":2301},"\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":2303,"title":2304},"\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":2306,"title":2307},"\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":2309,"title":2310},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2312,"title":2313},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2315,"title":2316},"\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":2318,"title":2319},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2321,"title":2322},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2324,"title":2325},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2327,"title":2328},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2330,"title":2331},"\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":2333,"title":2334},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2336,"title":2337},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2339,"title":2340},"\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":2342,"title":2343},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2345,"title":2346},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2348,"title":2349},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2351,"title":2352},"\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":2354,"title":2355},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2357,"title":2358},"\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":2360,"title":2361},"\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":2363,"title":2364},"\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":2366,"title":2367},"\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":2369,"title":2370},"\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":2372,"title":1301},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines",{"path":2374,"title":2375},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2377,"title":2378},"\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":2380,"title":2381},"\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":2383,"title":2384},"\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":2386,"title":2387},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2389,"title":2390},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2392,"title":2393},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2395,"title":2396},"\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":2398,"title":2399},"\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":2401,"title":2402},"\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":2404,"title":2405},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2407,"title":2408},"\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":2410,"title":179},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx",{"path":2412,"title":2413},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2415,"title":2416},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2418,"title":2419},"\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":2421,"title":2422},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2424,"title":24},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites",{"path":2426,"title":1308},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites",{"path":1351,"title":5},{"path":2429,"title":2430},"\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":2432,"title":2433},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2435,"title":29},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx",{"path":2437,"title":2438},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2440,"title":2441},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2443,"title":2444},"\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":2446,"title":2447},"\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":2449,"title":2450},"\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":2452,"title":2453},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2455,"title":2456},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2458,"title":2459},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2461,"title":2462},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2464,"title":2465},"\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":2467,"title":2468},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2470,"title":2471},"\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":2473,"title":2474},"\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":2476,"title":2477},"\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":2479,"title":2480},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2482,"title":2483},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2485,"title":2486},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2488,"title":2489},"\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":2491,"title":2492},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2494,"title":2495},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2497,"tools":2501},{"label":2498,"plural":2499,"u":2500},"How-to","How-tos","\u002Fguides\u002Fhow-to\u002F",[2502],{"label":321,"u":2503},"\u002Ftools\u002Fnginx\u002F",1790943197687]