[{"data":1,"prerenderedAt":2654},["ShallowReactive",2],{"page:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-in-docker-for-reproducible-builds":3,"all-docs-nav":1502,"filed:\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-in-docker-for-reproducible-builds":2645},{"id":4,"title":5,"body":6,"breadcrumb":1478,"dateModified":1488,"datePublished":1488,"description":1489,"extension":1490,"faq":1491,"meta":1496,"navigation":88,"path":1497,"seo":1498,"slug":12,"stem":1499,"type":1500,"__hash__":1501},"content\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-in-docker-for-reproducible-builds\u002Findex.md","Running Jekyll in Docker for Reproducible Builds",{"type":7,"value":8,"toc":1459},"minimark",[9,13,22,31,36,53,57,60,195,217,224,375,379,386,522,548,552,555,813,816,920,1049,1053,1069,1073,1104,1111,1214,1218,1247,1250,1254,1326,1330,1377,1381,1384,1388,1393,1396,1400,1403,1407,1410,1414,1417,1421,1455],[10,11,5],"h1",{"id":12},"running-jekyll-in-docker-for-reproducible-builds",[14,15,16,17,21],"p",{},"Jekyll's biggest operational problem is not speed or features; it is Ruby. A Jekyll site depends on a particular Ruby version, a particular Bundler, and gems with native extensions that compile against system libraries. On a documentation team with a mix of macOS, Windows and Linux machines, \"it builds on my laptop\" becomes a weekly conversation: a macOS update breaks the system Ruby, a new writer's Windows machine cannot compile ",[18,19,20],"code",{},"eventmachine",", and CI uses yet another Ruby from a setup action. Builds that differ between machines also produce subtly different output — a gem resolved to a different version renders Markdown differently.",[14,23,24,25,30],{},"This guide packages a Jekyll site's toolchain in a small, pinned Docker image used identically by writers, CI and the production build. It covers the Dockerfile, fast rebuilds through layer caching, live reload for local previews, and CI integration. It is part of ",[26,27,29],"a",{"href":28},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002F","Jekyll Plugin Ecosystem",". The site is a 1,100-page documentation site with nine plugins, maintained by eleven writers.",[32,33,35],"h2",{"id":34},"prerequisites","Prerequisites",[37,38,39,47,50],"ul",{},[40,41,42,43,46],"li",{},"A Jekyll site with a committed ",[18,44,45],{},"Gemfile.lock",".",[40,48,49],{},"Docker Desktop or Docker Engine on each machine, or Podman with the Docker CLI alias.",[40,51,52],{},"A container registry (GitHub Container Registry works well with GitHub Actions).",[32,54,56],{"id":55},"step-1-a-minimal-pinned-image","Step 1: A Minimal, Pinned Image",[14,58,59],{},"Base the image on the official Ruby slim image at an exact version, install only the build dependencies the gems need, and install gems from the lockfile:",[61,62,67],"pre",{"className":63,"code":64,"language":65,"meta":66,"style":66},"language-dockerfile shiki shiki-themes github-light github-dark","# Dockerfile\nFROM ruby:3.3.5-slim-bookworm\n\nENV LANG=C.UTF-8 \\\n    BUNDLE_PATH=\u002Fusr\u002Flocal\u002Fbundle \\\n    BUNDLE_JOBS=4 \\\n    BUNDLE_WITHOUT=development:test \\\n    JEKYLL_ENV=production\n\nRUN apt-get update \\\n && apt-get install -y --no-install-recommends build-essential git \\\n && rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F*\n\nWORKDIR \u002Fsite\nCOPY Gemfile Gemfile.lock .\u002F\nRUN gem install bundler -v \"$(tail -n1 Gemfile.lock | tr -d ' ')\" \\\n && bundle install \\\n && rm -rf \u002Fusr\u002Flocal\u002Fbundle\u002Fcache\n\nEXPOSE 4000 35729\nCMD [\"bundle\", \"exec\", \"jekyll\", \"build\"]\n","dockerfile","",[18,68,69,77,83,90,96,102,108,114,120,125,131,137,143,148,154,160,166,172,178,183,189],{"__ignoreMap":66},[70,71,74],"span",{"class":72,"line":73},"line",1,[70,75,76],{},"# Dockerfile\n",[70,78,80],{"class":72,"line":79},2,[70,81,82],{},"FROM ruby:3.3.5-slim-bookworm\n",[70,84,86],{"class":72,"line":85},3,[70,87,89],{"emptyLinePlaceholder":88},true,"\n",[70,91,93],{"class":72,"line":92},4,[70,94,95],{},"ENV LANG=C.UTF-8 \\\n",[70,97,99],{"class":72,"line":98},5,[70,100,101],{},"    BUNDLE_PATH=\u002Fusr\u002Flocal\u002Fbundle \\\n",[70,103,105],{"class":72,"line":104},6,[70,106,107],{},"    BUNDLE_JOBS=4 \\\n",[70,109,111],{"class":72,"line":110},7,[70,112,113],{},"    BUNDLE_WITHOUT=development:test \\\n",[70,115,117],{"class":72,"line":116},8,[70,118,119],{},"    JEKYLL_ENV=production\n",[70,121,123],{"class":72,"line":122},9,[70,124,89],{"emptyLinePlaceholder":88},[70,126,128],{"class":72,"line":127},10,[70,129,130],{},"RUN apt-get update \\\n",[70,132,134],{"class":72,"line":133},11,[70,135,136],{}," && apt-get install -y --no-install-recommends build-essential git \\\n",[70,138,140],{"class":72,"line":139},12,[70,141,142],{}," && rm -rf \u002Fvar\u002Flib\u002Fapt\u002Flists\u002F*\n",[70,144,146],{"class":72,"line":145},13,[70,147,89],{"emptyLinePlaceholder":88},[70,149,151],{"class":72,"line":150},14,[70,152,153],{},"WORKDIR \u002Fsite\n",[70,155,157],{"class":72,"line":156},15,[70,158,159],{},"COPY Gemfile Gemfile.lock .\u002F\n",[70,161,163],{"class":72,"line":162},16,[70,164,165],{},"RUN gem install bundler -v \"$(tail -n1 Gemfile.lock | tr -d ' ')\" \\\n",[70,167,169],{"class":72,"line":168},17,[70,170,171],{}," && bundle install \\\n",[70,173,175],{"class":72,"line":174},18,[70,176,177],{}," && rm -rf \u002Fusr\u002Flocal\u002Fbundle\u002Fcache\n",[70,179,181],{"class":72,"line":180},19,[70,182,89],{"emptyLinePlaceholder":88},[70,184,186],{"class":72,"line":185},20,[70,187,188],{},"EXPOSE 4000 35729\n",[70,190,192],{"class":72,"line":191},21,[70,193,194],{},"CMD [\"bundle\", \"exec\", \"jekyll\", \"build\"]\n",[14,196,197,200,201,204,205,208,209,212,213,216],{},[18,198,199],{},"COPY Gemfile Gemfile.lock"," before ",[18,202,203],{},"bundle install"," is the important line: Docker caches the gem layer and reuses it until the lockfile changes, so rebuilding the image after a content change takes seconds. The Bundler version comes from the lockfile's ",[18,206,207],{},"BUNDLED WITH"," line, so the image uses exactly the Bundler that created the lock. ",[18,210,211],{},"git"," is included because ",[18,214,215],{},"jekyll-last-modified-at"," and similar plugins shell out to it.",[14,218,219,220,223],{},"The final image was 412 MB; a multi-stage variant that drops ",[18,221,222],{},"build-essential"," after compiling gems came to 268 MB, which mattered for writers on slow connections pulling updates.",[225,226,227,371],"figure",{},[228,229,236,237,236,241,236,245,236,252,236,356],"svg",{"viewBox":230,"role":231,"ariaLabelledBy":232,"xmlns":235},"0 0 760 383","img",[233,234],"jd-layers-title","jd-layers-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[238,239,240],"title",{"id":233},"Docker image layers for a Jekyll site",[242,243,244],"desc",{"id":234},"Four layers from bottom to top. The Ruby 3.3.5 slim base image changes only when the Ruby version is bumped. The apt build dependencies layer changes rarely. The bundle install layer is invalidated only when Gemfile.lock changes. The site content is mounted or copied at build time and changes constantly without invalidating the layers below.",[246,247],"rect",{"x":248,"y":248,"width":249,"height":250,"fill":251},"0","760","383","#ffffff",[253,254,256,257,256,268,256,275,256,280,256,283,256,289,256,292,256,296,256,304,256,310,256,315,256,321,256,324,256,328,256,332,256,336,256,340,256,344,256,348,256,352,236],"g",{"style":255},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[246,258],{"x":259,"y":260,"width":261,"height":262,"rx":263,"fill":264,"opacity":265,"stroke":266,"style":267},"40.0","60.0","440.0","57.2","8","#8ac926","0.2","#5a8a16","stroke-width:1.5px",[269,270],"path",{"d":271,"fill":272,"stroke":273,"style":274},"M260.0 119.2 L260.0 139.2","none","#556071","stroke-width:2px;marker-end:url(#jd-layers-arrow)",[246,276],{"x":259,"y":277,"width":261,"height":262,"rx":263,"fill":278,"opacity":279,"stroke":278,"style":267},"143.2","#1982c4","0.14",[269,281],{"d":282,"fill":272,"stroke":273,"style":274},"M260.0 202.4 L260.0 222.4",[246,284],{"x":259,"y":285,"width":261,"height":262,"rx":263,"fill":286,"opacity":287,"stroke":288,"style":267},"226.4","#ffca3a","0.24","#a97b00",[269,290],{"d":291,"fill":272,"stroke":273,"style":274},"M260.0 285.6 L260.0 305.6",[246,293],{"x":259,"y":294,"width":261,"height":262,"rx":263,"fill":295,"opacity":279,"stroke":295,"style":267},"309.6","#6a4c93",[297,298,303],"text",{"x":299,"y":300,"fill":301,"style":302},"380.0","30.0","#1f2937","font-size:16px;text-anchor:middle;font-weight:700","Image layers and what invalidates them",[297,305,309],{"x":306,"y":307,"fill":301,"style":308},"260.0","86.4","font-size:13px;text-anchor:middle;font-weight:700","Site content",[297,311,314],{"x":306,"y":312,"fill":273,"style":313},"103.3","font-size:11px;text-anchor:middle","mounted or copied last",[297,316,320],{"x":317,"y":318,"fill":273,"style":319},"504.0","92.6","font-size:11.5px;text-anchor:start","changes every commit",[297,322,203],{"x":306,"y":323,"fill":301,"style":308},"169.5",[297,325,327],{"x":306,"y":326,"fill":273,"style":313},"186.4","from Gemfile.lock",[297,329,331],{"x":317,"y":330,"fill":273,"style":319},"175.8","rebuilt when the lockfile changes",[297,333,335],{"x":306,"y":334,"fill":301,"style":308},"252.7","apt build deps",[297,337,339],{"x":306,"y":338,"fill":273,"style":313},"269.6","build-essential, git",[297,341,343],{"x":317,"y":342,"fill":273,"style":319},"259.0","rarely changes",[297,345,347],{"x":306,"y":346,"fill":301,"style":308},"335.9","ruby:3.3.5-slim-bookworm",[297,349,351],{"x":306,"y":350,"fill":273,"style":313},"352.8","pinned base",[297,353,355],{"x":317,"y":354,"fill":273,"style":319},"342.2","changes on Ruby upgrades",[357,358,256,359,236],"defs",{},[360,361,367,368,256],"marker",{"id":362,"viewBox":363,"refX":263,"refY":364,"markerWidth":365,"markerHeight":365,"orient":366},"jd-layers-arrow","0 0 10 10","5","7","auto-start-reverse","\n      ",[269,369],{"d":370,"fill":273},"M0 0 L10 5 L0 10 z",[372,373,374],"figcaption",{},"Content edits never rebuild gems; only a lockfile change does.",[32,376,378],{"id":377},"step-2-local-preview-with-live-reload","Step 2: Local Preview With Live Reload",[14,380,381,382,385],{},"Writers run one command. A ",[18,383,384],{},"compose.yaml"," mounts the site, publishes the ports and enables live reload:",[61,387,391],{"className":388,"code":389,"language":390,"meta":66,"style":66},"language-yaml shiki shiki-themes github-light github-dark","# compose.yaml\nservices:\n  docs:\n    image: ghcr.io\u002Fexample\u002Fdocs-jekyll:2026-09\n    build: .\n    command: bundle exec jekyll serve --host 0.0.0.0 --livereload --incremental --force_polling\n    environment:\n      JEKYLL_ENV: development\n    ports: [\"4000:4000\", \"35729:35729\"]\n    volumes:\n      - .:\u002Fsite\n      - jekyll-cache:\u002Fsite\u002F.jekyll-cache\nvolumes:\n  jekyll-cache:\n","yaml",[18,392,393,399,409,416,428,439,449,456,466,486,493,501,508,515],{"__ignoreMap":66},[70,394,395],{"class":72,"line":73},[70,396,398],{"class":397},"sJ8bj","# compose.yaml\n",[70,400,401,405],{"class":72,"line":79},[70,402,404],{"class":403},"s9eBZ","services",[70,406,408],{"class":407},"sVt8B",":\n",[70,410,411,414],{"class":72,"line":85},[70,412,413],{"class":403},"  docs",[70,415,408],{"class":407},[70,417,418,421,424],{"class":72,"line":92},[70,419,420],{"class":403},"    image",[70,422,423],{"class":407},": ",[70,425,427],{"class":426},"sZZnC","ghcr.io\u002Fexample\u002Fdocs-jekyll:2026-09\n",[70,429,430,433,435],{"class":72,"line":98},[70,431,432],{"class":403},"    build",[70,434,423],{"class":407},[70,436,438],{"class":437},"sj4cs",".\n",[70,440,441,444,446],{"class":72,"line":104},[70,442,443],{"class":403},"    command",[70,445,423],{"class":407},[70,447,448],{"class":426},"bundle exec jekyll serve --host 0.0.0.0 --livereload --incremental --force_polling\n",[70,450,451,454],{"class":72,"line":110},[70,452,453],{"class":403},"    environment",[70,455,408],{"class":407},[70,457,458,461,463],{"class":72,"line":116},[70,459,460],{"class":403},"      JEKYLL_ENV",[70,462,423],{"class":407},[70,464,465],{"class":426},"development\n",[70,467,468,471,474,477,480,483],{"class":72,"line":122},[70,469,470],{"class":403},"    ports",[70,472,473],{"class":407},": [",[70,475,476],{"class":426},"\"4000:4000\"",[70,478,479],{"class":407},", ",[70,481,482],{"class":426},"\"35729:35729\"",[70,484,485],{"class":407},"]\n",[70,487,488,491],{"class":72,"line":127},[70,489,490],{"class":403},"    volumes",[70,492,408],{"class":407},[70,494,495,498],{"class":72,"line":133},[70,496,497],{"class":407},"      - ",[70,499,500],{"class":426},".:\u002Fsite\n",[70,502,503,505],{"class":72,"line":139},[70,504,497],{"class":407},[70,506,507],{"class":426},"jekyll-cache:\u002Fsite\u002F.jekyll-cache\n",[70,509,510,513],{"class":72,"line":145},[70,511,512],{"class":403},"volumes",[70,514,408],{"class":407},[70,516,517,520],{"class":72,"line":150},[70,518,519],{"class":403},"  jekyll-cache",[70,521,408],{"class":407},[14,523,524,527,528,531,532,535,536,539,540,543,544,46],{},[18,525,526],{},"docker compose up"," starts the preview at ",[18,529,530],{},"http:\u002F\u002Flocalhost:4000",". The named volume for ",[18,533,534],{},".jekyll-cache"," keeps Jekyll's own cache (Sass compilation, Liquid template caching) between sessions. ",[18,537,538],{},"--force_polling"," is needed on macOS and Windows, where file change events do not always cross the volume boundary; it costs a little CPU. With ",[18,541,542],{},"--incremental",", a single-page edit regenerated in 1.4 s instead of 21 s for a full rebuild, as described in ",[26,545,547],{"href":546},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds\u002F","Speeding Up Slow Jekyll Builds",[32,549,551],{"id":550},"step-3-build-the-image-once-use-it-everywhere","Step 3: Build the Image Once, Use It Everywhere",[14,553,554],{},"Building the image on every CI run wastes minutes. Build and push it only when the Dockerfile or lockfile changes, tagged with a hash of both, and pull it everywhere else:",[61,556,558],{"className":388,"code":557,"language":390,"meta":66,"style":66},"# .github\u002Fworkflows\u002Fimage.yml\non:\n  push:\n    branches: [main]\n    paths: ['Dockerfile', 'Gemfile', 'Gemfile.lock']\njobs:\n  image:\n    runs-on: ubuntu-latest\n    permissions: { contents: read, packages: write }\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: docker\u002Fsetup-buildx-action@v3\n      - uses: docker\u002Flogin-action@v3\n        with: { registry: ghcr.io, username: ${{ github.actor }}, password: ${{ secrets.GITHUB_TOKEN }} }\n      - uses: docker\u002Fbuild-push-action@v6\n        with:\n          push: true\n          tags: ghcr.io\u002Fexample\u002Fdocs-jekyll:${{ hashFiles('Dockerfile', 'Gemfile.lock') }}\n          cache-from: type=gha\n          cache-to: type=gha,mode=max\n",[18,559,560,565,572,579,591,613,620,627,637,666,673,685,696,707,756,767,773,783,793,803],{"__ignoreMap":66},[70,561,562],{"class":72,"line":73},[70,563,564],{"class":397},"# .github\u002Fworkflows\u002Fimage.yml\n",[70,566,567,570],{"class":72,"line":79},[70,568,569],{"class":437},"on",[70,571,408],{"class":407},[70,573,574,577],{"class":72,"line":85},[70,575,576],{"class":403},"  push",[70,578,408],{"class":407},[70,580,581,584,586,589],{"class":72,"line":92},[70,582,583],{"class":403},"    branches",[70,585,473],{"class":407},[70,587,588],{"class":426},"main",[70,590,485],{"class":407},[70,592,593,596,598,601,603,606,608,611],{"class":72,"line":98},[70,594,595],{"class":403},"    paths",[70,597,473],{"class":407},[70,599,600],{"class":426},"'Dockerfile'",[70,602,479],{"class":407},[70,604,605],{"class":426},"'Gemfile'",[70,607,479],{"class":407},[70,609,610],{"class":426},"'Gemfile.lock'",[70,612,485],{"class":407},[70,614,615,618],{"class":72,"line":104},[70,616,617],{"class":403},"jobs",[70,619,408],{"class":407},[70,621,622,625],{"class":72,"line":110},[70,623,624],{"class":403},"  image",[70,626,408],{"class":407},[70,628,629,632,634],{"class":72,"line":116},[70,630,631],{"class":403},"    runs-on",[70,633,423],{"class":407},[70,635,636],{"class":426},"ubuntu-latest\n",[70,638,639,642,645,648,650,653,655,658,660,663],{"class":72,"line":122},[70,640,641],{"class":403},"    permissions",[70,643,644],{"class":407},": { ",[70,646,647],{"class":403},"contents",[70,649,423],{"class":407},[70,651,652],{"class":426},"read",[70,654,479],{"class":407},[70,656,657],{"class":403},"packages",[70,659,423],{"class":407},[70,661,662],{"class":426},"write",[70,664,665],{"class":407}," }\n",[70,667,668,671],{"class":72,"line":127},[70,669,670],{"class":403},"    steps",[70,672,408],{"class":407},[70,674,675,677,680,682],{"class":72,"line":133},[70,676,497],{"class":407},[70,678,679],{"class":403},"uses",[70,681,423],{"class":407},[70,683,684],{"class":426},"actions\u002Fcheckout@v4\n",[70,686,687,689,691,693],{"class":72,"line":139},[70,688,497],{"class":407},[70,690,679],{"class":403},[70,692,423],{"class":407},[70,694,695],{"class":426},"docker\u002Fsetup-buildx-action@v3\n",[70,697,698,700,702,704],{"class":72,"line":145},[70,699,497],{"class":407},[70,701,679],{"class":403},[70,703,423],{"class":407},[70,705,706],{"class":426},"docker\u002Flogin-action@v3\n",[70,708,709,712,714,717,719,722,724,727,729,732,735,738,741,744,746,748,750,753],{"class":72,"line":150},[70,710,711],{"class":403},"        with",[70,713,644],{"class":407},[70,715,716],{"class":403},"registry",[70,718,423],{"class":407},[70,720,721],{"class":426},"ghcr.io",[70,723,479],{"class":407},[70,725,726],{"class":403},"username",[70,728,423],{"class":407},[70,730,731],{"class":426},"$",[70,733,734],{"class":407},"{{ ",[70,736,737],{"class":426},"github.actor",[70,739,740],{"class":407}," }}, ",[70,742,743],{"class":403},"password",[70,745,423],{"class":407},[70,747,731],{"class":426},[70,749,734],{"class":407},[70,751,752],{"class":426},"secrets.GITHUB_TOKEN",[70,754,755],{"class":407}," }} }\n",[70,757,758,760,762,764],{"class":72,"line":156},[70,759,497],{"class":407},[70,761,679],{"class":403},[70,763,423],{"class":407},[70,765,766],{"class":426},"docker\u002Fbuild-push-action@v6\n",[70,768,769,771],{"class":72,"line":162},[70,770,711],{"class":403},[70,772,408],{"class":407},[70,774,775,778,780],{"class":72,"line":168},[70,776,777],{"class":403},"          push",[70,779,423],{"class":407},[70,781,782],{"class":437},"true\n",[70,784,785,788,790],{"class":72,"line":174},[70,786,787],{"class":403},"          tags",[70,789,423],{"class":407},[70,791,792],{"class":426},"ghcr.io\u002Fexample\u002Fdocs-jekyll:${{ hashFiles('Dockerfile', 'Gemfile.lock') }}\n",[70,794,795,798,800],{"class":72,"line":180},[70,796,797],{"class":403},"          cache-from",[70,799,423],{"class":407},[70,801,802],{"class":426},"type=gha\n",[70,804,805,808,810],{"class":72,"line":185},[70,806,807],{"class":403},"          cache-to",[70,809,423],{"class":407},[70,811,812],{"class":426},"type=gha,mode=max\n",[14,814,815],{},"The site build job then runs inside that image as a container job, so there is no Ruby setup step at all:",[61,817,819],{"className":388,"code":818,"language":390,"meta":66,"style":66},"jobs:\n  build:\n    runs-on: ubuntu-latest\n    container: ghcr.io\u002Fexample\u002Fdocs-jekyll:${{ hashFiles('Dockerfile', 'Gemfile.lock') }}\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with: { fetch-depth: 0 }\n      - run: bundle exec jekyll build --trace\n      - uses: actions\u002Fupload-pages-artifact@v3\n        with: { path: _site }\n",[18,820,821,827,834,842,851,857,867,882,894,905],{"__ignoreMap":66},[70,822,823,825],{"class":72,"line":73},[70,824,617],{"class":403},[70,826,408],{"class":407},[70,828,829,832],{"class":72,"line":79},[70,830,831],{"class":403},"  build",[70,833,408],{"class":407},[70,835,836,838,840],{"class":72,"line":85},[70,837,631],{"class":403},[70,839,423],{"class":407},[70,841,636],{"class":426},[70,843,844,847,849],{"class":72,"line":92},[70,845,846],{"class":403},"    container",[70,848,423],{"class":407},[70,850,792],{"class":426},[70,852,853,855],{"class":72,"line":98},[70,854,670],{"class":403},[70,856,408],{"class":407},[70,858,859,861,863,865],{"class":72,"line":104},[70,860,497],{"class":407},[70,862,679],{"class":403},[70,864,423],{"class":407},[70,866,684],{"class":426},[70,868,869,871,873,876,878,880],{"class":72,"line":110},[70,870,711],{"class":403},[70,872,644],{"class":407},[70,874,875],{"class":403},"fetch-depth",[70,877,423],{"class":407},[70,879,248],{"class":437},[70,881,665],{"class":407},[70,883,884,886,889,891],{"class":72,"line":116},[70,885,497],{"class":407},[70,887,888],{"class":403},"run",[70,890,423],{"class":407},[70,892,893],{"class":426},"bundle exec jekyll build --trace\n",[70,895,896,898,900,902],{"class":72,"line":122},[70,897,497],{"class":407},[70,899,679],{"class":403},[70,901,423],{"class":407},[70,903,904],{"class":426},"actions\u002Fupload-pages-artifact@v3\n",[70,906,907,909,911,913,915,918],{"class":72,"line":127},[70,908,711],{"class":403},[70,910,644],{"class":407},[70,912,269],{"class":403},[70,914,423],{"class":407},[70,916,917],{"class":426},"_site",[70,919,665],{"class":407},[225,921,922,1046],{},[228,923,236,928,236,931,236,934,236,937,236,1039],{"viewBox":924,"role":231,"ariaLabelledBy":925,"xmlns":235},"0 0 760 324",[926,927],"jd-flow-title","jd-flow-desc",[238,929,930],{"id":926},"How the Jekyll image is built once and used by writers and CI",[242,932,933],{"id":927},"A lockfile change on main triggers the image workflow, which builds and pushes an image tagged with the lockfile hash to the registry. Writers pull the image and run the preview with docker compose. Pull request builds and production builds run as container jobs in the same image and publish the site.",[246,935],{"x":248,"y":248,"width":249,"height":936,"fill":251},"324",[253,938,256,939,256,943,256,948,256,951,256,954,256,958,256,961,256,964,256,968,256,971,256,974,256,977,256,980,256,985,256,989,256,993,256,995,256,999,256,1001,256,1005,256,1008,256,1014,256,1018,256,1022,256,1026,256,1030,256,1035,236],{"style":255},[246,940],{"x":300,"y":941,"width":942,"height":262,"rx":263,"fill":295,"opacity":279,"stroke":295,"style":267},"56.0","160.0",[246,944],{"x":945,"y":941,"width":942,"height":262,"rx":263,"fill":946,"stroke":947,"style":267},"210.0","#f8fafc","#d9e2ef",[246,949],{"x":950,"y":941,"width":942,"height":262,"rx":263,"fill":278,"opacity":279,"stroke":278,"style":267},"390.0",[246,952],{"x":953,"y":941,"width":942,"height":262,"rx":263,"fill":264,"opacity":265,"stroke":266,"style":267},"570.0",[269,955],{"d":956,"fill":272,"stroke":273,"style":957},"M114.0 163.1 L284.0 163.1","stroke-width:1.8px;marker-end:url(#jd-flow-arrow)",[269,959],{"d":960,"fill":272,"stroke":273,"style":957},"M466.0 211.0 L296.0 211.0",[269,962],{"d":963,"fill":272,"stroke":273,"style":957},"M646.0 243.9 L296.0 243.9",[269,965],{"d":966,"fill":272,"stroke":947,"style":967},"M110.0 115.2 L110.0 307.8","stroke-width:1.5px;stroke-dasharray:4 4",[269,969],{"d":970,"fill":272,"stroke":947,"style":967},"M290.0 115.2 L290.0 307.8",[269,972],{"d":973,"fill":272,"stroke":947,"style":967},"M470.0 115.2 L470.0 307.8",[269,975],{"d":976,"fill":272,"stroke":947,"style":967},"M650.0 115.2 L650.0 307.8",[297,978,979],{"x":299,"y":300,"fill":301,"style":302},"One image, three consumers",[297,981,984],{"x":982,"y":983,"fill":301,"style":308},"110.0","82.4","Image workflow",[297,986,988],{"x":982,"y":987,"fill":273,"style":313},"99.3","on lockfile change",[297,990,992],{"x":991,"y":983,"fill":301,"style":308},"290.0","GHCR",[297,994,716],{"x":991,"y":987,"fill":273,"style":313},[297,996,998],{"x":997,"y":983,"fill":301,"style":308},"470.0","Writers",[297,1000,526],{"x":997,"y":987,"fill":273,"style":313},[297,1002,1004],{"x":1003,"y":983,"fill":301,"style":308},"650.0","CI builds",[297,1006,1007],{"x":1003,"y":987,"fill":273,"style":313},"container jobs",[297,1009,1013],{"x":1010,"y":1011,"fill":301,"style":1012},"200.0","140.1","font-size:11.5px;text-anchor:middle","push image tagged with",[297,1015,1017],{"x":1010,"y":1016,"fill":301,"style":1012},"155.1","lockfile hash",[297,1019,1021],{"x":299,"y":1020,"fill":301,"style":1012},"188.0","pull once per dependency",[297,1023,1025],{"x":299,"y":1024,"fill":301,"style":1012},"203.0","change",[297,1027,1029],{"x":997,"y":1028,"fill":301,"style":1012},"235.9","pull cached image per job",[297,1031,1034],{"x":1032,"y":1033,"fill":301,"style":1012},"690.0","268.9","jekyll build in identical",[297,1036,1038],{"x":1032,"y":1037,"fill":301,"style":1012},"283.8","toolchain",[357,1040,256,1041,236],{},[360,1042,367,1044,256],{"id":1043,"viewBox":363,"refX":263,"refY":364,"markerWidth":365,"markerHeight":365,"orient":366},"jd-flow-arrow",[269,1045],{"d":370,"fill":273},[372,1047,1048],{},"The image tag is derived from the Dockerfile and lockfile, so every consumer of a given commit uses the same toolchain.",[32,1050,1052],{"id":1051},"step-4-upgrading-ruby-and-gems","Step 4: Upgrading Ruby and Gems",[14,1054,1055,1056,1059,1060,1063,1064,1068],{},"Upgrades become ordinary pull requests. Bump the base image tag or run ",[18,1057,1058],{},"bundle update"," inside the container (",[18,1061,1062],{},"docker compose run --rm docs bundle update jekyll","), commit the new lockfile, and CI builds a new image and a preview. Compare the built output with the previous build to see what the upgrade changed, as in ",[26,1065,1067],{"href":1066},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely\u002F","Upgrading Jekyll and Ruby Versions Safely",". The Ruby 3.1 to 3.3 upgrade on this site was a single pull request with a one-line Dockerfile change and a lockfile update; the output diff showed no changes, and it was merged the same day. Previously, a Ruby upgrade had taken a week of fixing individual laptops.",[32,1070,1072],{"id":1071},"platform-differences-worth-knowing","Platform Differences Worth Knowing",[14,1074,1075,1076,1079,1080,1083,1084,1087,1088,1091,1092,1095,1096,1099,1100,1103],{},"Apple Silicon Macs run ",[18,1077,1078],{},"linux\u002Farm64"," images natively, while CI runners use ",[18,1081,1082],{},"linux\u002Famd64",". Most gems have native builds for both, but a few publish precompiled binaries only for one; build the image for both platforms with ",[18,1085,1086],{},"platforms: linux\u002Famd64,linux\u002Farm64"," in ",[18,1089,1090],{},"build-push-action"," so writers on M-series Macs do not run under emulation, which made builds about four times slower in testing. Also add ",[18,1093,1094],{},"x86_64-linux"," and ",[18,1097,1098],{},"aarch64-linux"," to the lockfile's platforms (",[18,1101,1102],{},"bundle lock --add-platform",") so Bundler resolves native gems for both.",[14,1105,1106,1107,1110],{},"On Windows, run Docker with the WSL 2 backend and keep the repository inside the WSL filesystem rather than on the Windows drive; volume mounts from ",[18,1108,1109],{},"C:"," were slow enough to make incremental rebuilds take 9 s instead of 1.4 s.",[225,1112,1113,1211],{},[228,1114,236,1119,236,1122,236,1125,236,1128],{"viewBox":1115,"role":231,"ariaLabelledBy":1116,"xmlns":235},"0 0 760 196",[1117,1118],"jd-time-title","jd-time-desc",[238,1120,1121],{"id":1117},"Onboarding and build times with local Ruby and with Docker",[242,1123,1124],{"id":1118},"Paired bars. A new writer's setup took 95 minutes on average with local Ruby and 9 minutes with Docker, mostly the image pull. The CI job took 3.1 minutes with ruby setup and bundle install and 1.2 minutes in the prebuilt container.",[246,1126],{"x":248,"y":248,"width":249,"height":1127,"fill":251},"196",[253,1129,256,1130,256,1141,256,1145,256,1152,256,1156,256,1160,256,1164,256,1167,256,1170,256,1175,256,1179,256,1184,256,1191,256,1197,256,1201,256,1206,236],{"style":255},[246,1131],{"x":1132,"y":1133,"width":1134,"height":1135,"rx":1136,"fill":1137,"opacity":1138,"stroke":1139,"style":1140},"273.5","50.0","14.0","12.0","2","#ff595e","0.3","#d83b41","stroke-width:1px",[246,1142],{"x":1143,"y":1133,"width":1134,"height":1135,"rx":1136,"fill":264,"opacity":1144,"stroke":266,"style":1140},"386.8","0.4",[246,1146],{"x":1147,"y":1148,"width":1149,"height":1150,"rx":1151,"fill":1137,"opacity":1138,"stroke":1139,"style":1140},"230.0","82.0","450.7","16.0","3",[246,1153],{"x":1147,"y":1154,"width":1155,"height":1150,"rx":1151,"fill":264,"opacity":1144,"stroke":266,"style":1140},"102.0","42.7",[246,1157],{"x":1147,"y":1158,"width":1159,"height":1150,"rx":1151,"fill":1137,"opacity":1138,"stroke":1139,"style":1140},"134.0","14.7",[246,1161],{"x":1147,"y":1162,"width":1163,"height":1150,"rx":1151,"fill":264,"opacity":1144,"stroke":266,"style":1140},"154.0","5.7",[269,1165],{"d":1166,"fill":272,"stroke":273,"style":267},"M230.0 78.0 L230.0 176.0",[297,1168,1169],{"x":299,"y":300,"fill":301,"style":302},"Setup and build times before and after",[297,1171,1174],{"x":1172,"y":260,"fill":273,"style":1173},"293.5","font-size:12px;text-anchor:start","Local Ruby",[297,1176,1178],{"x":1177,"y":260,"fill":273,"style":1173},"406.8","Docker image",[297,1180,1183],{"x":1181,"y":1182,"fill":301,"style":1173},"20.0","105.2","New writer setup",[297,1185,1190],{"x":1186,"y":1187,"fill":1188,"style":1189},"687.7","94.5","#b32b30","font-size:11.5px;text-anchor:start;font-weight:700","95 min",[297,1192,1196],{"x":1193,"y":1194,"fill":1195,"style":1189},"279.7","114.5","#3f6410","9 min",[297,1198,1200],{"x":1181,"y":1199,"fill":301,"style":1173},"157.2","CI job total",[297,1202,1205],{"x":1203,"y":1204,"fill":1188,"style":1189},"251.7","146.5","3.1 min",[297,1207,1210],{"x":1208,"y":1209,"fill":1195,"style":1189},"242.7","166.5","1.2 min",[372,1212,1213],{},"Onboarding time averaged over the last six writers to join under each setup; CI times are medians of 50 runs.",[32,1215,1217],{"id":1216},"making-it-easy-for-writers","Making It Easy for Writers",[14,1219,1220,1221,1224,1225,479,1228,1095,1231,1234,1235,1238,1239,1242,1243,1246],{},"The container only helps if writers use it, and most writers do not want to learn Docker. Three small things made adoption painless on this team. A ",[18,1222,1223],{},"Makefile"," (or npm scripts) with ",[18,1226,1227],{},"make preview",[18,1229,1230],{},"make build",[18,1232,1233],{},"make check"," hides the ",[18,1236,1237],{},"docker compose"," commands entirely; the README's getting-started section shrank from two pages of Ruby installation notes to three lines. A VS Code dev container definition (",[18,1240,1241],{},".devcontainer\u002Fdevcontainer.json",") pointing at the same image lets writers who use VS Code open the repository and get a working preview with no terminal at all. And a weekly scheduled workflow that rebuilds the image with ",[18,1244,1245],{},"--pull"," and runs the site build catches base-image security updates that break something, before a writer discovers it on a Monday morning.",[14,1248,1249],{},"The support channel's Ruby questions stopped entirely within a month, which the team counted as the most valuable outcome of the whole change.",[32,1251,1253],{"id":1252},"measured-impact","Measured Impact",[1255,1256,1257,1273],"table",{},[1258,1259,1260],"thead",{},[1261,1262,1263,1267,1270],"tr",{},[1264,1265,1266],"th",{},"Measure",[1264,1268,1269],{},"Local Ruby everywhere",[1264,1271,1272],{},"Pinned Docker image",[1274,1275,1276,1286,1296,1305,1315],"tbody",{},[1261,1277,1278,1282,1284],{},[1279,1280,1281],"td",{},"New writer setup time (average)",[1279,1283,1190],{},[1279,1285,1196],{},[1261,1287,1288,1291,1294],{},[1279,1289,1290],{},"\"Build fails on my machine\" support requests per month",[1279,1292,1293],{},"6",[1279,1295,1138],{},[1261,1297,1298,1301,1303],{},[1279,1299,1300],{},"CI job duration (median)",[1279,1302,1205],{},[1279,1304,1210],{},[1261,1306,1307,1310,1313],{},[1279,1308,1309],{},"Output differences between a writer's build and CI (sample of 20)",[1279,1311,1312],{},"4",[1279,1314,248],{},[1261,1316,1317,1320,1323],{},[1279,1318,1319],{},"Ruby upgrade effort (3.1 to 3.3)",[1279,1321,1322],{},"~1 week across laptops",[1279,1324,1325],{},"1 pull request",[32,1327,1329],{"id":1328},"pitfalls-rollback","Pitfalls & Rollback",[37,1331,1332,1343,1351,1357,1363],{},[40,1333,1334,1338,1339,1342],{},[1335,1336,1337],"strong",{},"Unpinned base images."," ",[18,1340,1341],{},"ruby:3-slim"," changes under you; pin to an exact version.",[40,1344,1345,1350],{},[1335,1346,1347,1348,46],{},"Copying the whole site before ",[18,1349,203],{}," Every content change rebuilds gems.",[40,1352,1353,1356],{},[1335,1354,1355],{},"Single-platform images on Apple Silicon."," Emulation is slow; build multi-arch.",[40,1358,1359,1362],{},[1335,1360,1361],{},"Bind mounts from the Windows filesystem."," Keep the repository inside WSL.",[40,1364,1365,1368,1369,1372,1373,1376],{},[1335,1366,1367],{},"Rollback:"," the image is only a packaging of the same toolchain; writers can still run ",[18,1370,1371],{},"bundle exec jekyll serve"," locally, and CI can switch back to ",[18,1374,1375],{},"ruby\u002Fsetup-ruby"," by removing the container line.",[32,1378,1380],{"id":1379},"conclusion","Conclusion",[14,1382,1383],{},"A small, pinned Docker image turns Jekyll's Ruby dependency from a recurring support issue into a single file under version control. Build it once per dependency change, tag it by lockfile hash, and use it for local previews, pull request builds and production. On this team it cut onboarding from an hour and a half to minutes, halved CI time and made every build produce identical output.",[32,1385,1387],{"id":1386},"faq","FAQ",[1389,1390,1392],"h3",{"id":1391},"why-run-jekyll-in-docker-instead-of-installing-ruby-locally","Why run Jekyll in Docker instead of installing Ruby locally?",[14,1394,1395],{},"Jekyll depends on a specific Ruby version, Bundler, and gems with native extensions such as sass-embedded, eventmachine and nokogiri. Local installs drift between machines and operating systems, especially on macOS after system updates. A pinned image gives every writer and CI runner the same toolchain with one command.",[1389,1397,1399],{"id":1398},"is-the-official-jekylljekyll-image-still-a-good-choice","Is the official jekyll\u002Fjekyll image still a good choice?",[14,1401,1402],{},"It has not been updated for current Ruby and Jekyll releases. A small custom image based on the official ruby slim image, with the site's Gemfile.lock installed, is easier to keep current and gives exact control over versions.",[1389,1404,1406],{"id":1405},"how-do-i-keep-gem-installation-fast","How do I keep gem installation fast?",[14,1408,1409],{},"Copy only Gemfile and Gemfile.lock into the image before running bundle install, so the gem layer is cached until dependencies change. In CI, use Docker layer caching or build the image once and push it to a registry.",[1389,1411,1413],{"id":1412},"does-live-reload-work-inside-docker","Does live reload work inside Docker?",[14,1415,1416],{},"Yes. Run jekyll serve with --host 0.0.0.0 and --livereload, publish ports 4000 and 35729, and mount the site directory as a volume. On macOS, add --force_polling if file changes are not detected through the volume mount.",[32,1418,1420],{"id":1419},"related","Related",[37,1422,1423,1431,1438,1443,1448],{},[40,1424,1425,1338,1428,1430],{},[1335,1426,1427],{},"Parent:",[26,1429,29],{"href":28}," — plugins and their operational cost.",[40,1432,1433,1437],{},[26,1434,1436],{"href":1435},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions\u002F","Deploying Jekyll with GitHub Actions"," — publishing what the container builds.",[40,1439,1440,1442],{},[26,1441,1067],{"href":1066}," — the upgrade process in detail.",[40,1444,1445,1447],{},[26,1446,547],{"href":546}," — incremental builds and profiling.",[40,1449,1450,1454],{},[26,1451,1453],{"href":1452},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fbest-ssg-for-technical-writers-without-coding-experience\u002F","Best SSG for Technical Writers Without Coding Experience"," — tooling burden in generator choice.",[1456,1457,1458],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .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 .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}",{"title":66,"searchDepth":79,"depth":79,"links":1460},[1461,1462,1463,1464,1465,1466,1467,1468,1469,1470,1471,1477],{"id":34,"depth":79,"text":35},{"id":55,"depth":79,"text":56},{"id":377,"depth":79,"text":378},{"id":550,"depth":79,"text":551},{"id":1051,"depth":79,"text":1052},{"id":1071,"depth":79,"text":1072},{"id":1216,"depth":79,"text":1217},{"id":1252,"depth":79,"text":1253},{"id":1328,"depth":79,"text":1329},{"id":1379,"depth":79,"text":1380},{"id":1386,"depth":79,"text":1387,"children":1472},[1473,1474,1475,1476],{"id":1391,"depth":85,"text":1392},{"id":1398,"depth":85,"text":1399},{"id":1405,"depth":85,"text":1406},{"id":1412,"depth":85,"text":1413},{"id":1419,"depth":79,"text":1420},[1479,1482,1485,1486],{"name":1480,"item":1481},"Home","\u002F",{"name":1483,"item":1484},"Choosing the Right Static Site Generator for Production","\u002Fchoosing-the-right-static-site-generator-for-production\u002F",{"name":29,"item":28},{"name":5,"item":1487},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-in-docker-for-reproducible-builds\u002F","2026-09-25","Build a Jekyll site in a pinned Docker image so writers, CI and production use the same Ruby, gems and native extensions, with fast cached rebuilds.","md",[1492,1493,1494,1495],{"q":1392,"a":1395},{"q":1399,"a":1402},{"q":1406,"a":1409},{"q":1413,"a":1416},{},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-in-docker-for-reproducible-builds",{"title":5,"description":1489},"choosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Frunning-jekyll-in-docker-for-reproducible-builds\u002Findex","article","iPtt81H9hd4zLmwnwIxxN2VeogSwUf0ly7v8o80vqG4",[1503,1506,1509,1512,1515,1518,1521,1524,1527,1530,1533,1536,1539,1542,1545,1548,1551,1554,1557,1560,1563,1566,1569,1572,1575,1578,1581,1584,1587,1590,1593,1596,1599,1602,1605,1608,1611,1614,1617,1620,1623,1626,1629,1632,1635,1638,1641,1644,1647,1650,1653,1656,1659,1662,1664,1667,1670,1673,1676,1679,1682,1685,1688,1691,1694,1697,1699,1702,1705,1707,1710,1711,1714,1716,1718,1721,1724,1727,1730,1733,1736,1739,1742,1745,1748,1751,1754,1757,1760,1763,1766,1769,1772,1775,1778,1781,1784,1787,1790,1793,1796,1799,1802,1805,1808,1811,1814,1817,1820,1823,1826,1829,1832,1835,1838,1841,1844,1847,1850,1853,1856,1859,1862,1865,1868,1871,1874,1877,1880,1883,1886,1889,1892,1895,1898,1901,1904,1907,1910,1913,1916,1919,1922,1925,1928,1931,1934,1937,1940,1943,1946,1949,1952,1955,1958,1961,1964,1967,1970,1973,1976,1979,1982,1985,1988,1991,1994,1997,2000,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,2234,2237,2240,2243,2246,2249,2252,2255,2258,2261,2264,2267,2270,2273,2276,2279,2282,2285,2288,2291,2294,2297,2300,2303,2306,2309,2312,2315,2318,2321,2324,2327,2330,2333,2336,2339,2342,2345,2348,2351,2354,2357,2360,2363,2366,2369,2372,2375,2378,2381,2384,2387,2390,2393,2396,2399,2402,2405,2408,2411,2414,2417,2420,2423,2426,2429,2432,2435,2438,2441,2444,2447,2450,2453,2456,2459,2462,2465,2468,2471,2474,2477,2480,2483,2486,2489,2492,2495,2498,2501,2504,2507,2510,2513,2516,2519,2522,2525,2528,2531,2534,2537,2540,2543,2546,2549,2552,2555,2558,2561,2564,2567,2570,2573,2576,2579,2582,2585,2588,2591,2594,2597,2600,2603,2606,2609,2612,2615,2618,2621,2624,2627,2630,2633,2636,2639,2642],{"path":1504,"title":1505},"\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":1507,"title":1508},"\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":1510,"title":1511},"\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":1513,"title":1514},"\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":1516,"title":1517},"\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":1519,"title":1520},"\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":1522,"title":1523},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Faccessibility-for-static-sites","Accessibility for Static Sites",{"path":1525,"title":1526},"\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":1528,"title":1529},"\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":1531,"title":1532},"\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":1534,"title":1535},"\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":1537,"title":1538},"\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":1540,"title":1541},"\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":1543,"title":1544},"\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":1546,"title":1547},"\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":1549,"title":1550},"\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":1552,"title":1553},"\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":1555,"title":1556},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1558,"title":1559},"\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":1561,"title":1562},"\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":1564,"title":1565},"\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":1567,"title":1568},"\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":1570,"title":1571},"\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":1573,"title":1574},"\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":1576,"title":1577},"\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":1579,"title":1580},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fcomparing-docs-framework-build-times","Comparing Docs Framework Build Times",{"path":1582,"title":1583},"\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":1585,"title":1586},"\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":1588,"title":1589},"\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":1591,"title":1592},"\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":1594,"title":1595},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1597,"title":1598},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Finternationalizing-starlight-docs","Internationalizing Starlight Docs",{"path":1600,"title":1601},"\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":1603,"title":1604},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1606,"title":1607},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-mkdocs-documentation-to-vitepress","Migrating MkDocs Documentation to VitePress",{"path":1609,"title":1610},"\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":1612,"title":1613},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1615,"title":1616},"\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":1618,"title":1619},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1621,"title":1622},"\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":1624,"title":1625},"\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":1627,"title":1628},"\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":1630,"title":1631},"\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":1633,"title":1634},"\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":1636,"title":1637},"\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":1639,"title":1640},"\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":1642,"title":1643},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1645,"title":1646},"\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":1648,"title":1649},"\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":1651,"title":1652},"\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":1654,"title":1655},"\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":1657,"title":1658},"\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":1660,"title":1661},"\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":1663,"title":1483},"\u002Fchoosing-the-right-static-site-generator-for-production",{"path":1665,"title":1666},"\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":1668,"title":1669},"\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":1671,"title":1672},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fi18n-routing-in-astro","i18n Routing in Astro",{"path":1674,"title":1675},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites","Internationalization for Static Sites",{"path":1677,"title":1678},"\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":1680,"title":1681},"\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":1683,"title":1684},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Finternationalization-for-static-sites\u002Fmultilingual-sites-with-hugo","Multilingual Sites with Hugo",{"path":1686,"title":1687},"\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":1689,"title":1690},"\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":1692,"title":1693},"\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":1695,"title":1696},"\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":1698,"title":1436},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fdeploying-jekyll-with-github-actions",{"path":1700,"title":1701},"\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":1703,"title":1704},"\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":1706,"title":29},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem",{"path":1708,"title":1709},"\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":1497,"title":5},{"path":1712,"title":1713},"\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":1715,"title":547},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds",{"path":1717,"title":1067},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely",{"path":1719,"title":1720},"\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":1722,"title":1723},"\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":1725,"title":1726},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1728,"title":1729},"\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":1731,"title":1732},"\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":1734,"title":1735},"\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":1737,"title":1738},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-docusaurus-to-starlight","Migrating from Docusaurus to Starlight",{"path":1740,"title":1741},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1743,"title":1744},"\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":1746,"title":1747},"\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":1749,"title":1750},"\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":1752,"title":1753},"\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":1755,"title":1756},"\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":1758,"title":1759},"\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":1761,"title":1762},"\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":1764,"title":1765},"\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":1767,"title":1768},"\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":1770,"title":1771},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1773,"title":1774},"\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":1776,"title":1777},"\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":1779,"title":1780},"\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":1782,"title":1783},"\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":1785,"title":1786},"\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":1788,"title":1789},"\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":1791,"title":1792},"\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":1794,"title":1795},"\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":1797,"title":1798},"\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":1800,"title":1801},"\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":1803,"title":1804},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fcustomizing-the-pagefind-ui","Customizing the Pagefind UI",{"path":1806,"title":1807},"\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":1809,"title":1810},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1812,"title":1813},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1815,"title":1816},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1818,"title":1819},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1821,"title":1822},"\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":1824,"title":1825},"\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":1827,"title":1828},"\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":1830,"title":1831},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Ftracking-zero-result-searches","Tracking Zero-Result Searches",{"path":1833,"title":1834},"\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":1836,"title":1837},"\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":1839,"title":1840},"\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":1842,"title":1843},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1845,"title":1846},"\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":1848,"title":1849},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1851,"title":1852},"\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":1854,"title":1855},"\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":1857,"title":1858},"\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":1860,"title":1861},"\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":1863,"title":1864},"\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":1866,"title":1867},"\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":1869,"title":1870},"\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":1872,"title":1873},"\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":1875,"title":1876},"\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":1878,"title":1879},"\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":1881,"title":1882},"\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":1884,"title":1885},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Ftechnical-seo-for-static-sites","Technical SEO for Static Sites",{"path":1887,"title":1888},"\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":1890,"title":1891},"\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":1893,"title":1894},"\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":1896,"title":1897},"\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":1899,"title":1900},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Fcache-control-headers-for-static-sites-in-nginx","Cache-Control Headers for Static Sites in Nginx",{"path":1902,"title":1903},"\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":1905,"title":1906},"\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":1908,"title":1909},"\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":1911,"title":1912},"\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":1914,"title":1915},"\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":1917,"title":1918},"\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":1920,"title":1921},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1923,"title":1924},"\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":1926,"title":1927},"\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":1929,"title":1930},"\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":1932,"title":1933},"\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":1935,"title":1936},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs\u002Ftiered-caching-and-origin-shield","Tiered Caching and Origin Shield",{"path":1938,"title":1939},"\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":1941,"title":1942},"\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":1944,"title":1945},"\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":1947,"title":1948},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcss-and-javascript-asset-optimization","CSS and JavaScript Asset Optimization",{"path":1950,"title":1951},"\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":1953,"title":1954},"\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":1956,"title":1957},"\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":1959,"title":1960},"\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":1962,"title":1963},"\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":1965,"title":1966},"\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":1968,"title":1969},"\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":1971,"title":1972},"\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":1974,"title":1975},"\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":1977,"title":1978},"\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":1980,"title":1981},"\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":1983,"title":1984},"\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":1986,"title":1987},"\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":1989,"title":1990},"\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":1992,"title":1993},"\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":1995,"title":1996},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1998,"title":1999},"\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":2001,"title":2002},"\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":2004,"title":2005},"\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":2007,"title":2008},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fauditing-font-payload-per-page","Auditing Font Payload per Page",{"path":2010,"title":2011},"\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":2013,"title":2014},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":2016,"title":2017},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":2019,"title":2020},"\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":2022,"title":2023},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":2025,"title":2026},"\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":2028,"title":2029},"\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":2031,"title":2032},"\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":2034,"title":2035},"\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":2037,"title":2038},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fvariable-fonts-vs-static-weights","Variable Fonts vs Static Weights",{"path":2040,"title":2041},"\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":2043,"title":2044},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fblur-up-placeholders-with-lqip","Blur-Up Placeholders with LQIP",{"path":2046,"title":2047},"\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":2049,"title":2050},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro\u002Fcaching-processed-images-between-builds","Caching Processed Images Between Builds",{"path":2052,"title":2053},"\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":2055,"title":2056},"\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":2058,"title":2059},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":2061,"title":2062},"\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":2064,"title":2065},"\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":2067,"title":2068},"\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":2070,"title":2071},"\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":2073,"title":2074},"\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":2076,"title":2077},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":2079,"title":2080},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":2082,"title":2083},"\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":2085,"title":2086},"\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":2088,"title":2089},"\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":2091,"title":2092},"\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":2094,"title":2095},"\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":2097,"title":2098},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":2100,"title":2101},"\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":2103,"title":2104},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fpreact-vs-react-islands-bundle-size","Preact vs React Islands Bundle Size",{"path":2106,"title":2107},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":2109,"title":2110},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fserver-islands-in-astro","Server Islands in Astro",{"path":2112,"title":2113},"\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":2115,"title":2116},"\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":2118,"title":2119},"\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":2121,"title":2122},"\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":2124,"title":2125},"\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":2127,"title":2128},"\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":2130,"title":2131},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":2133,"title":2134},"\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":2136,"title":2137},"\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":2139,"title":2140},"\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":2142,"title":2143},"\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":2145,"title":2146},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":2148,"title":2149},"\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":2151,"title":2152},"\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":2154,"title":2155},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Fper-template-performance-budgets","Per-Template Performance Budgets",{"path":2157,"title":2158},"\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":2160,"title":2161},"\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":2163,"title":2164},"\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":2166,"title":2167},"\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":2169,"title":2170},"\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":2172,"title":2173},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci\u002Ftracking-page-weight-over-time","Tracking Page Weight Over Time",{"path":2175,"title":2176},"\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":2178,"title":2179},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":2181,"title":2182},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fearly-hints-103-on-cloudflare","Early Hints (103) on Cloudflare",{"path":2184,"title":2185},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Ffetchpriority-beyond-the-hero-image","Fetchpriority Beyond the Hero Image",{"path":2187,"title":2188},"\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":2190,"title":2191},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":2193,"title":2194},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":2196,"title":2197},"\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":2199,"title":2200},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":2202,"title":2203},"\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":2205,"title":2206},"\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":2208,"title":2209},"\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":2211,"title":2212},"\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":2214,"title":2215},"\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":2217,"title":2218},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":2220,"title":2221},"\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":2223,"title":2224},"\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":2226,"title":2227},"\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":2229,"title":2230},"\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":2232,"title":2233},"\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":2235,"title":2236},"\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":2238,"title":2239},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":2241,"title":2242},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fbranch-deploy-controls-on-cloudflare-pages","Branch Deploy Controls on Cloudflare Pages",{"path":2244,"title":2245},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fcloudflare-pages-functions-middleware","Cloudflare Pages Functions Middleware",{"path":2247,"title":2248},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":2250,"title":2251},"\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":2253,"title":2254},"\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":2256,"title":2257},"\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":2259,"title":2260},"\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":2262,"title":2263},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Ffixing-redirect-loops-on-cloudflare-pages","Fixing Redirect Loops on Cloudflare Pages",{"path":2265,"title":2266},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":2268,"title":2269},"\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":2271,"title":2272},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":2274,"title":2275},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fcontent-linting-with-markdownlint","Content Linting with markdownlint",{"path":2277,"title":2278},"\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":2280,"title":2281},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":2283,"title":2284},"\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":2286,"title":2287},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":2289,"title":2290},"\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":2292,"title":2293},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Frelease-notes-and-changelogs-from-git","Release Notes and Changelogs from Git",{"path":2295,"title":2296},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduled-content-publishing-with-github-actions","Scheduled Content Publishing With GitHub Actions",{"path":2298,"title":2299},"\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":2301,"title":2302},"\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":2304,"title":2305},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":2307,"title":2308},"\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":2310,"title":2311},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fconcurrency-groups-to-cancel-stale-builds","Concurrency Groups to Cancel Stale Builds",{"path":2313,"title":2314},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":2316,"title":2317},"\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":2319,"title":2320},"\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":2322,"title":2323},"\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":2325,"title":2326},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":2328,"title":2329},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":2331,"title":2332},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fpinning-actions-by-commit-sha","Pinning Actions by Commit SHA",{"path":2334,"title":2335},"\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":2337,"title":2338},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Freusable-workflows-for-ssg-builds","Reusable Workflows for SSG Builds",{"path":2340,"title":2341},"\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":2343,"title":2344},"\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":2346,"title":2347},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fdeploying-only-changed-files","Deploying Only Changed Files",{"path":2349,"title":2350},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":2352,"title":2353},"\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":2355,"title":2356},"\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":2358,"title":2359},"\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":2361,"title":2362},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":2364,"title":2365},"\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":2367,"title":2368},"\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":2370,"title":2371},"\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":2373,"title":2374},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":2376,"title":2377},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":2379,"title":2380},"\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":2382,"title":2383},"\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":2385,"title":2386},"\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":2388,"title":2389},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":2391,"title":2392},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":2394,"title":2395},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fmonitoring-tls-certificate-expiry","Monitoring TLS Certificate Expiry",{"path":2397,"title":2398},"\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":2400,"title":2401},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Fsynthetic-monitoring-with-scheduled-playwright-checks","Synthetic Monitoring With Scheduled Playwright Checks",{"path":2403,"title":2404},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Ftracking-deploy-markers-in-analytics","Tracking Deploy Markers in Analytics",{"path":2406,"title":2407},"\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":2409,"title":2410},"\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":2412,"title":2413},"\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":2415,"title":2416},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":2418,"title":2419},"\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":2421,"title":2422},"\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":2424,"title":2425},"\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":2427,"title":2428},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":2430,"title":2431},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":2433,"title":2434},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-edge-functions-for-static-sites","Netlify Edge Functions for Static Sites",{"path":2436,"title":2437},"\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":2439,"title":2440},"\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":2442,"title":2443},"\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":2445,"title":2446},"\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":2448,"title":2449},"\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":2451,"title":2452},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":2454,"title":2455},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcommenting-on-preview-deploys","Commenting on Preview Deploys",{"path":2457,"title":2458},"\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":2460,"title":2461},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":2463,"title":2464},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":2466,"title":2467},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreview-deploys-for-monorepos","Preview Deploys for Monorepos",{"path":2469,"title":2470},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":2472,"title":2473},"\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":2475,"title":2476},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":2478,"title":2479},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":2481,"title":2482},"\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":2484,"title":2485},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":2487,"title":2488},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":2490,"title":2491},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":2493,"title":2494},"\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":2496,"title":2497},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fpost-deploy-verification-checklists","Post-Deploy Verification Checklists",{"path":2499,"title":2500},"\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":2502,"title":2503},"\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":2505,"title":2506},"\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":2508,"title":2509},"\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":2511,"title":2512},"\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":2514,"title":2515},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":2517,"title":2518},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":2520,"title":2521},"\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":2523,"title":2524},"\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":2526,"title":2527},"\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":2529,"title":2530},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":2532,"title":2533},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fpermissions-policy-and-cross-origin-headers","Permissions-Policy and Cross-Origin Headers",{"path":2535,"title":2536},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":2538,"title":2539},"\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":2541,"title":2542},"\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":2544,"title":2545},"\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":2547,"title":2548},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":2550,"title":2551},"\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":2553,"title":2554},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fbrotli-and-gzip-precompression-served-by-nginx","Brotli and Gzip Precompression Served by Nginx",{"path":2556,"title":2557},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":2559,"title":2560},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":2562,"title":2563},"\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":2565,"title":2566},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fhosting-on-azure-static-web-apps","Hosting on Azure Static Web Apps",{"path":2568,"title":2569},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":2571,"title":2572},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fnginx-vs-caddy-for-serving-static-sites","Nginx vs Caddy for Serving Static Sites",{"path":2574,"title":2575},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-from-a-docker-container-with-nginx","Serving a Static Site From a Docker Container With Nginx",{"path":2577,"title":2578},"\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":2580,"title":2581},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":2583,"title":2584},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":2586,"title":2587},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fstatic-hosting-on-google-cloud-storage","Static Hosting on Google Cloud Storage",{"path":2589,"title":2590},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":2592,"title":2593},"\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":2595,"title":2596},"\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":2598,"title":2599},"\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":2601,"title":2602},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":2604,"title":2605},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":2607,"title":2608},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnewsletter-signup-with-an-edge-function","Newsletter Signup with an Edge Function",{"path":2610,"title":2611},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":2613,"title":2614},"\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":2616,"title":2617},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Frate-limiting-edge-functions","Rate Limiting Edge Functions",{"path":2619,"title":2620},"\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":2622,"title":2623},"\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":2625,"title":2626},"\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":2628,"title":2629},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci","Testing Static Sites in CI",{"path":2631,"title":2632},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fsnapshot-testing-build-output","Snapshot Testing Build Output",{"path":2634,"title":2635},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-redirects-and-headers-before-deploy","Testing Redirects and Headers Before Deploy",{"path":2637,"title":2638},"\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":2640,"title":2641},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Ftesting-structured-data-and-meta-tags","Testing Structured Data and Meta Tags",{"path":2643,"title":2644},"\u002Fproduction-ready-deployment-cicd-workflows\u002Ftesting-static-sites-in-ci\u002Fvalidating-html-output-in-ci","Validating HTML Output in CI",{"kind":2646,"tools":2650},{"label":2647,"plural":2648,"u":2649},"How-to","How-tos","\u002Fguides\u002Fhow-to\u002F",[2651],{"label":2652,"u":2653},"Jekyll","\u002Ftools\u002Fjekyll\u002F",1790943194012]