[{"data":1,"prerenderedAt":1843},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions":3,"all-docs-nav":1302},{"id":4,"title":5,"body":6,"breadcrumb":1279,"dateModified":1288,"datePublished":1288,"description":1289,"extension":1290,"faq":1291,"meta":1296,"navigation":149,"path":1297,"seo":1298,"slug":12,"stem":1299,"type":1300,"__hash__":1301},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions\u002Findex.md","Deploying to GitHub Pages with Actions",{"type":7,"value":8,"toc":1260},"minimark",[9,13,22,31,36,49,53,73,77,512,515,572,712,716,730,736,817,824,894,897,901,920,927,931,934,1033,1077,1088,1092,1107,1111,1121,1125,1170,1174,1183,1187,1192,1195,1199,1202,1206,1209,1213,1216,1220,1256],[10,11,5],"h1",{"id":12},"deploying-to-github-pages-with-actions",[14,15,16,17,21],"p",{},"GitHub Pages is the simplest free host for a static site whose code already lives on GitHub. For years it meant pushing built files to a ",[18,19,20],"code",{},"gh-pages"," branch, or letting Pages run Jekyll for you. Today the recommended path is a GitHub Actions workflow that builds the site with any generator and publishes the output directly as a Pages artifact, with no branch of built files and no Jekyll involved.",[14,23,24,25,30],{},"This guide sets up that workflow for any static site generator, handles the base path problem for project sites, adds a custom domain, and is honest about what Pages cannot do so you know when to pick a different host. It is part of ",[26,27,29],"a",{"href":28},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002F","GitHub Actions for Automated SSG Builds",".",[32,33,35],"h2",{"id":34},"prerequisites","Prerequisites",[37,38,39,43,46],"ul",{},[40,41,42],"li",{},"A static site in a GitHub repository that builds to a folder with one command.",[40,44,45],{},"Repository admin access to change the Pages settings.",[40,47,48],{},"Optional: a custom domain you control.",[32,50,52],{"id":51},"enable-actions-as-the-source","Enable Actions as the Source",[14,54,55,56,60,61,64,65,68,69,72],{},"In the repository, open ",[57,58,59],"strong",{},"Settings → Pages"," and set ",[57,62,63],{},"Source"," to ",[57,66,67],{},"GitHub Actions",". This tells Pages to publish whatever a workflow deploys, rather than a branch. It also creates a ",[18,70,71],{},"github-pages"," environment that the deploy job will use.",[32,74,76],{"id":75},"the-workflow","The Workflow",[78,79,84],"pre",{"className":80,"code":81,"language":82,"meta":83,"style":83},"language-yaml shiki shiki-themes github-light github-dark","name: Deploy to Pages\non:\n  push:\n    branches: [main]\n  workflow_dispatch:\n\npermissions:\n  contents: read\n  pages: write\n  id-token: write\n\nconcurrency:\n  group: pages\n  cancel-in-progress: false\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with: { node-version-file: .nvmrc, cache: npm }\n      - id: pages\n        uses: actions\u002Fconfigure-pages@v5\n      - run: npm ci\n      - run: npm run build\n        env:\n          BASE_PATH: ${{ steps.pages.outputs.base_path }}\n      - uses: actions\u002Fupload-pages-artifact@v3\n        with:\n          path: dist\n\n  deploy:\n    needs: build\n    runs-on: ubuntu-latest\n    environment:\n      name: github-pages\n      url: ${{ steps.deployment.outputs.page_url }}\n    steps:\n      - id: deployment\n        uses: actions\u002Fdeploy-pages@v4\n","yaml","",[18,85,86,103,113,121,136,144,151,159,170,181,191,196,204,215,226,231,239,247,258,266,280,292,323,335,346,359,371,379,390,402,409,420,425,433,444,453,461,472,483,490,502],{"__ignoreMap":83},[87,88,91,95,99],"span",{"class":89,"line":90},"line",1,[87,92,94],{"class":93},"s9eBZ","name",[87,96,98],{"class":97},"sVt8B",": ",[87,100,102],{"class":101},"sZZnC","Deploy to Pages\n",[87,104,106,110],{"class":89,"line":105},2,[87,107,109],{"class":108},"sj4cs","on",[87,111,112],{"class":97},":\n",[87,114,116,119],{"class":89,"line":115},3,[87,117,118],{"class":93},"  push",[87,120,112],{"class":97},[87,122,124,127,130,133],{"class":89,"line":123},4,[87,125,126],{"class":93},"    branches",[87,128,129],{"class":97},": [",[87,131,132],{"class":101},"main",[87,134,135],{"class":97},"]\n",[87,137,139,142],{"class":89,"line":138},5,[87,140,141],{"class":93},"  workflow_dispatch",[87,143,112],{"class":97},[87,145,147],{"class":89,"line":146},6,[87,148,150],{"emptyLinePlaceholder":149},true,"\n",[87,152,154,157],{"class":89,"line":153},7,[87,155,156],{"class":93},"permissions",[87,158,112],{"class":97},[87,160,162,165,167],{"class":89,"line":161},8,[87,163,164],{"class":93},"  contents",[87,166,98],{"class":97},[87,168,169],{"class":101},"read\n",[87,171,173,176,178],{"class":89,"line":172},9,[87,174,175],{"class":93},"  pages",[87,177,98],{"class":97},[87,179,180],{"class":101},"write\n",[87,182,184,187,189],{"class":89,"line":183},10,[87,185,186],{"class":93},"  id-token",[87,188,98],{"class":97},[87,190,180],{"class":101},[87,192,194],{"class":89,"line":193},11,[87,195,150],{"emptyLinePlaceholder":149},[87,197,199,202],{"class":89,"line":198},12,[87,200,201],{"class":93},"concurrency",[87,203,112],{"class":97},[87,205,207,210,212],{"class":89,"line":206},13,[87,208,209],{"class":93},"  group",[87,211,98],{"class":97},[87,213,214],{"class":101},"pages\n",[87,216,218,221,223],{"class":89,"line":217},14,[87,219,220],{"class":93},"  cancel-in-progress",[87,222,98],{"class":97},[87,224,225],{"class":108},"false\n",[87,227,229],{"class":89,"line":228},15,[87,230,150],{"emptyLinePlaceholder":149},[87,232,234,237],{"class":89,"line":233},16,[87,235,236],{"class":93},"jobs",[87,238,112],{"class":97},[87,240,242,245],{"class":89,"line":241},17,[87,243,244],{"class":93},"  build",[87,246,112],{"class":97},[87,248,250,253,255],{"class":89,"line":249},18,[87,251,252],{"class":93},"    runs-on",[87,254,98],{"class":97},[87,256,257],{"class":101},"ubuntu-latest\n",[87,259,261,264],{"class":89,"line":260},19,[87,262,263],{"class":93},"    steps",[87,265,112],{"class":97},[87,267,269,272,275,277],{"class":89,"line":268},20,[87,270,271],{"class":97},"      - ",[87,273,274],{"class":93},"uses",[87,276,98],{"class":97},[87,278,279],{"class":101},"actions\u002Fcheckout@v4\n",[87,281,283,285,287,289],{"class":89,"line":282},21,[87,284,271],{"class":97},[87,286,274],{"class":93},[87,288,98],{"class":97},[87,290,291],{"class":101},"actions\u002Fsetup-node@v4\n",[87,293,295,298,301,304,306,309,312,315,317,320],{"class":89,"line":294},22,[87,296,297],{"class":93},"        with",[87,299,300],{"class":97},": { ",[87,302,303],{"class":93},"node-version-file",[87,305,98],{"class":97},[87,307,308],{"class":101},".nvmrc",[87,310,311],{"class":97},", ",[87,313,314],{"class":93},"cache",[87,316,98],{"class":97},[87,318,319],{"class":101},"npm",[87,321,322],{"class":97}," }\n",[87,324,326,328,331,333],{"class":89,"line":325},23,[87,327,271],{"class":97},[87,329,330],{"class":93},"id",[87,332,98],{"class":97},[87,334,214],{"class":101},[87,336,338,341,343],{"class":89,"line":337},24,[87,339,340],{"class":93},"        uses",[87,342,98],{"class":97},[87,344,345],{"class":101},"actions\u002Fconfigure-pages@v5\n",[87,347,349,351,354,356],{"class":89,"line":348},25,[87,350,271],{"class":97},[87,352,353],{"class":93},"run",[87,355,98],{"class":97},[87,357,358],{"class":101},"npm ci\n",[87,360,362,364,366,368],{"class":89,"line":361},26,[87,363,271],{"class":97},[87,365,353],{"class":93},[87,367,98],{"class":97},[87,369,370],{"class":101},"npm run build\n",[87,372,374,377],{"class":89,"line":373},27,[87,375,376],{"class":93},"        env",[87,378,112],{"class":97},[87,380,382,385,387],{"class":89,"line":381},28,[87,383,384],{"class":93},"          BASE_PATH",[87,386,98],{"class":97},[87,388,389],{"class":101},"${{ steps.pages.outputs.base_path }}\n",[87,391,393,395,397,399],{"class":89,"line":392},29,[87,394,271],{"class":97},[87,396,274],{"class":93},[87,398,98],{"class":97},[87,400,401],{"class":101},"actions\u002Fupload-pages-artifact@v3\n",[87,403,405,407],{"class":89,"line":404},30,[87,406,297],{"class":93},[87,408,112],{"class":97},[87,410,412,415,417],{"class":89,"line":411},31,[87,413,414],{"class":93},"          path",[87,416,98],{"class":97},[87,418,419],{"class":101},"dist\n",[87,421,423],{"class":89,"line":422},32,[87,424,150],{"emptyLinePlaceholder":149},[87,426,428,431],{"class":89,"line":427},33,[87,429,430],{"class":93},"  deploy",[87,432,112],{"class":97},[87,434,436,439,441],{"class":89,"line":435},34,[87,437,438],{"class":93},"    needs",[87,440,98],{"class":97},[87,442,443],{"class":101},"build\n",[87,445,447,449,451],{"class":89,"line":446},35,[87,448,252],{"class":93},[87,450,98],{"class":97},[87,452,257],{"class":101},[87,454,456,459],{"class":89,"line":455},36,[87,457,458],{"class":93},"    environment",[87,460,112],{"class":97},[87,462,464,467,469],{"class":89,"line":463},37,[87,465,466],{"class":93},"      name",[87,468,98],{"class":97},[87,470,471],{"class":101},"github-pages\n",[87,473,475,478,480],{"class":89,"line":474},38,[87,476,477],{"class":93},"      url",[87,479,98],{"class":97},[87,481,482],{"class":101},"${{ steps.deployment.outputs.page_url }}\n",[87,484,486,488],{"class":89,"line":485},39,[87,487,263],{"class":93},[87,489,112],{"class":97},[87,491,493,495,497,499],{"class":89,"line":492},40,[87,494,271],{"class":97},[87,496,330],{"class":93},[87,498,98],{"class":97},[87,500,501],{"class":101},"deployment\n",[87,503,505,507,509],{"class":89,"line":504},41,[87,506,340],{"class":93},[87,508,98],{"class":97},[87,510,511],{"class":101},"actions\u002Fdeploy-pages@v4\n",[14,513,514],{},"What each part does:",[37,516,517,529,540,556,564],{},[40,518,519,528],{},[57,520,521,524,525],{},[18,522,523],{},"pages: write"," and ",[18,526,527],{},"id-token: write"," let the deploy action authenticate to Pages with a short-lived OIDC token. No personal access token or deploy key is involved.",[40,530,531,539],{},[57,532,533,535,536],{},[18,534,201],{}," with ",[18,537,538],{},"cancel-in-progress: false"," queues deployments rather than cancelling one mid-publish.",[40,541,542,547,548,551,552,555],{},[57,543,544],{},[18,545,546],{},"configure-pages"," outputs the site's ",[18,549,550],{},"base_path"," — empty for a custom domain or a user site, ",[18,553,554],{},"\u002Frepo"," for a project site — which the build can use.",[40,557,558,563],{},[57,559,560],{},[18,561,562],{},"upload-pages-artifact"," packages the folder as a tarball artifact in the format Pages expects.",[40,565,566,571],{},[57,567,568],{},[18,569,570],{},"deploy-pages"," publishes it and reports the URL on the workflow run.",[573,574,575,708],"figure",{},[576,577,584,585,584,589,584,593,584,600,584,618],"svg",{"viewBox":578,"role":579,"ariaLabelledBy":580,"xmlns":583},"0 0 760 250","img",[581,582],"ghp-flow-title","ghp-flow-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[586,587,588],"title",{"id":581},"GitHub Pages deployment with Actions",[590,591,592],"desc",{"id":582},"A push to main triggers the build job, which runs configure-pages to get the base path, builds the site and uploads a Pages artifact. The deploy job, in the github-pages environment, publishes the artifact using an OIDC token. No gh-pages branch is involved.",[594,595],"rect",{"x":596,"y":596,"width":597,"height":598,"fill":599},"0","760","250","#ffffff",[601,602,603,604,584],"defs",{},"\n    ",[605,606,613],"marker",{"id":607,"viewBox":608,"refX":609,"refY":610,"markerWidth":611,"markerHeight":611,"orient":612},"ghp-flow-arrow","0 0 10 10","9","5","7","auto-start-reverse",[614,615],"path",{"d":616,"fill":617},"M0,0 L10,5 L0,10 z","#556071",[619,620,603,622,603,630,603,638,603,644,603,652,603,658,603,663,603,667,603,671,603,676,603,680,603,684,603,687,603,690,603,695,603,699,603,703,584],"g",{"style":621},"font-family:system-ui, sans-serif;font-size:12px",[623,624,629],"text",{"x":625,"y":626,"fill":627,"style":628},"380","26","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Push to published site, no built-files branch",[594,631],{"x":632,"y":633,"width":634,"height":635,"rx":636,"fill":617,"style":637,"stroke":617},"20","70","110","60","8","fill-opacity:0.1",[623,639,643],{"x":640,"y":641,"fill":627,"style":642},"75","104","text-anchor:middle","push main",[594,645],{"x":646,"y":647,"width":648,"height":649,"rx":636,"fill":650,"style":651,"stroke":650},"160","50","330","100","#166a9e","fill-opacity:0.08",[623,653,657],{"x":654,"y":655,"fill":650,"style":656},"325","72","font-weight:700;text-anchor:middle","build job",[623,659,662],{"x":660,"y":661,"fill":627},"176","98","configure-pages → base_path",[623,664,666],{"x":660,"y":665,"fill":627},"118","npm ci · npm run build",[623,668,670],{"x":660,"y":669,"fill":627},"138","upload-pages-artifact (dist)",[594,672],{"x":673,"y":647,"width":674,"height":649,"rx":636,"fill":675,"style":651,"stroke":675},"520","220","#3f6410",[623,677,679],{"x":678,"y":655,"fill":675,"style":656},"630","deploy job",[623,681,683],{"x":682,"y":661,"fill":627},"536","env: github-pages",[623,685,686],{"x":682,"y":665,"fill":627},"OIDC token, no secrets",[623,688,689],{"x":682,"y":669,"fill":627},"deploy-pages → URL",[89,691],{"x1":692,"y1":649,"x2":693,"y2":649,"stroke":617,"style":694},"130","156","stroke-width:1.5px;marker-end:url(#ghp-flow-arrow)",[89,696],{"x1":697,"y1":649,"x2":698,"y2":649,"stroke":617,"style":694},"490","516",[623,700,702],{"x":625,"y":701,"fill":627,"style":642},"190","user.github.io\u002Frepo\u002F  or  docs.example.com\u002F",[623,704,707],{"x":625,"y":705,"fill":617,"style":706},"226","font-size:11px;text-anchor:middle","each deployment is recorded in the environment, with a link to the run that produced it",[709,710,711],"figcaption",{},"Build output never enters Git history; each deployment is an artifact attached to a run.",[32,713,715],{"id":714},"the-base-path-problem","The Base Path Problem",[14,717,718,719,722,723,311,726,729],{},"A project site is served from ",[18,720,721],{},"https:\u002F\u002Fuser.github.io\u002Frepo\u002F",", not from the root. Every root-relative URL the generator emits — ",[18,724,725],{},"\u002Fassets\u002Fapp.css",[18,727,728],{},"\u002Fdocs\u002Finstall\u002F"," — then points outside the site and returns 404. This is the most common reason a Pages deployment \"works\" but shows an unstyled page with broken links.",[14,731,732,733,735],{},"Tell the generator about the subpath. The ",[18,734,546],{}," output makes it automatic:",[37,737,738,759,776,790,804],{},[40,739,740,743,744,524,747,750,751,754,755,758],{},[57,741,742],{},"Astro:"," ",[18,745,746],{},"base: process.env.BASE_PATH || '\u002F'",[18,748,749],{},"site: 'https:\u002F\u002Fuser.github.io'"," in ",[18,752,753],{},"astro.config.mjs",". Use ",[18,756,757],{},"import.meta.env.BASE_URL"," when building links in components.",[40,760,761,743,764,767,768,771,772,775],{},[57,762,763],{},"Hugo:",[18,765,766],{},"hugo --baseURL \"${{ steps.pages.outputs.base_url }}\u002F\"",", and use ",[18,769,770],{},"relURL"," or ",[18,773,774],{},"absURL"," in templates.",[40,777,778,781,782,785,786,789],{},[57,779,780],{},"Eleventy:"," set ",[18,783,784],{},"pathPrefix"," from the environment variable and use the ",[18,787,788],{},"url"," filter on links.",[40,791,792,743,795,524,798,750,801,30],{},[57,793,794],{},"Next.js static export:",[18,796,797],{},"basePath",[18,799,800],{},"assetPrefix",[18,802,803],{},"next.config.js",[40,805,806,809,810,771,813,816],{},[57,807,808],{},"Docusaurus, VitePress, Starlight:"," each has a ",[18,811,812],{},"baseUrl",[18,814,815],{},"base"," option for the same purpose.",[14,818,819,820,823],{},"Content links written by hand in Markdown also need the prefix, which is why many teams prefer a custom domain: the site is then served from ",[18,821,822],{},"\u002F"," and the problem disappears.",[573,825,826,891],{},[576,827,584,832,584,835,584,838,584,841],{"viewBox":828,"role":579,"ariaLabelledBy":829,"xmlns":583},"0 0 760 230",[830,831],"ghp-base-title","ghp-base-desc",[586,833,834],{"id":830},"How a missing base path breaks a project site",[590,836,837],{"id":831},"The site lives at user.github.io\u002Frepo\u002F. Without a base path, the page requests \u002Fassets\u002Fapp.css, which resolves to user.github.io\u002Fassets\u002Fapp.css and returns 404. With base set to \u002Frepo\u002F, it requests \u002Frepo\u002Fassets\u002Fapp.css, which exists.",[594,839],{"x":596,"y":596,"width":597,"height":840,"fill":599},"230",[619,842,603,843,603,846,603,852,603,858,603,862,603,865,603,870,603,873,603,877,603,881,603,884,603,887,584],{"style":621},[623,844,845],{"x":625,"y":626,"fill":627,"style":628},"Page at user.github.io\u002Frepo\u002F requests its stylesheet",[594,847],{"x":848,"y":647,"width":648,"height":849,"rx":636,"fill":850,"style":851,"stroke":850},"30","140","#d83b41","fill-opacity:0.06",[623,853,857],{"x":854,"y":855,"fill":856,"style":656},"195","74","#b32b30","base not set",[623,859,861],{"x":860,"y":641,"fill":627},"48","href=\"\u002Fassets\u002Fapp.css\"",[623,863,864],{"x":860,"y":692,"fill":627},"→ user.github.io\u002Fassets\u002Fapp.css",[623,866,869],{"x":860,"y":867,"fill":856,"style":868},"164","font-weight:700","404, unstyled page",[594,871],{"x":872,"y":647,"width":648,"height":849,"rx":636,"fill":675,"style":851,"stroke":675},"400",[623,874,876],{"x":875,"y":855,"fill":675,"style":656},"565","base: '\u002Frepo\u002F'",[623,878,880],{"x":879,"y":641,"fill":627},"418","href=\"\u002Frepo\u002Fassets\u002Fapp.css\"",[623,882,883],{"x":879,"y":692,"fill":627},"→ user.github.io\u002Frepo\u002Fassets\u002Fapp.css",[623,885,886],{"x":879,"y":867,"fill":675,"style":868},"200, styled page",[623,888,890],{"x":625,"y":889,"fill":617,"style":706},"216","with a custom domain the base is \"\u002F\" and both columns are identical",[709,892,893],{},"The same build works locally and fails on Pages when the base path is missing, which makes it easy to miss.",[14,895,896],{},"To catch this before publishing, run a link check against the build output with the base path applied; a missing prefix shows up as hundreds of broken internal links in one run.",[32,898,900],{"id":899},"custom-domains","Custom Domains",[14,902,903,904,907,908,911,912,915,916,919],{},"Add the domain in ",[57,905,906],{},"Settings → Pages → Custom domain",". For a subdomain like ",[18,909,910],{},"docs.example.com",", create a CNAME record to ",[18,913,914],{},"user.github.io",". For an apex domain, create A records to GitHub's Pages IP addresses (listed in GitHub's documentation) and AAAA records for IPv6. Tick ",[57,917,918],{},"Enforce HTTPS"," once the certificate is issued, usually within an hour.",[14,921,922,923,926],{},"With Actions deployments, the custom domain is stored in the repository settings, so you do not need a ",[18,924,925],{},"CNAME"," file in the build output. Verify the domain at the organisation or account level as well, which prevents someone else from claiming it for their Pages site if your configuration is ever removed.",[32,928,930],{"id":929},"what-github-pages-cannot-do","What GitHub Pages Cannot Do",[14,932,933],{},"Pages is deliberately simple, and some of its limits matter for production sites:",[573,935,936,1030],{},[576,937,584,942,584,945,584,948,584,951],{"viewBox":938,"role":579,"ariaLabelledBy":939,"xmlns":583},"0 0 760 280",[940,941],"ghp-lim-title","ghp-lim-desc",[586,943,944],{"id":940},"GitHub Pages capabilities compared with CDN-backed static hosts",[590,946,947],{"id":941},"GitHub Pages lacks custom headers, server-side redirects, configurable cache lifetimes, preview deployments per pull request and serverless functions, all of which Cloudflare, Netlify and Vercel offer. Pages offers free hosting, HTTPS and custom domains, like the others.",[594,949],{"x":596,"y":596,"width":597,"height":950,"fill":599},"280",[619,952,603,953,603,956,603,962,603,965,603,969,603,974,603,979,603,982,603,984,603,988,603,991,603,993,603,997,603,999,603,1001,603,1005,603,1008,603,1010,603,1014,603,1016,603,1018,603,1022,603,1024,603,1026,584],{"style":621},[623,954,955],{"x":625,"y":626,"fill":627,"style":628},"What you give up for simplicity",[623,957,961],{"x":958,"y":959,"fill":627,"style":960},"260","58","font-weight:700;text-anchor:end","capability",[623,963,964],{"x":872,"y":959,"fill":627,"style":656},"GitHub Pages",[623,966,968],{"x":967,"y":959,"fill":627,"style":656},"590","Cloudflare \u002F Netlify \u002F Vercel",[89,970],{"x1":635,"y1":971,"x2":972,"y2":971,"stroke":617,"style":973},"68","720","stroke-width:1px",[623,975,978],{"x":958,"y":976,"fill":627,"style":977},"94","text-anchor:end","HTTPS + custom domain",[623,980,981],{"x":872,"y":976,"fill":675,"style":642},"yes",[623,983,981],{"x":967,"y":976,"fill":675,"style":642},[623,985,987],{"x":958,"y":986,"fill":627,"style":977},"122","custom response headers",[623,989,990],{"x":872,"y":986,"fill":856,"style":642},"no",[623,992,981],{"x":967,"y":986,"fill":675,"style":642},[623,994,996],{"x":958,"y":995,"fill":627,"style":977},"150","server-side redirects",[623,998,990],{"x":872,"y":995,"fill":856,"style":642},[623,1000,981],{"x":967,"y":995,"fill":675,"style":642},[623,1002,1004],{"x":958,"y":1003,"fill":627,"style":977},"178","long cache for hashed assets",[623,1006,1007],{"x":872,"y":1003,"fill":856,"style":642},"no (≈10 min)",[623,1009,981],{"x":967,"y":1003,"fill":675,"style":642},[623,1011,1013],{"x":958,"y":1012,"fill":627,"style":977},"206","preview per pull request",[623,1015,990],{"x":872,"y":1012,"fill":856,"style":642},[623,1017,981],{"x":967,"y":1012,"fill":675,"style":642},[623,1019,1021],{"x":958,"y":1020,"fill":627,"style":977},"234","functions \u002F edge code",[623,1023,990],{"x":872,"y":1020,"fill":856,"style":642},[623,1025,981],{"x":967,"y":1020,"fill":675,"style":642},[623,1027,1029],{"x":625,"y":1028,"fill":617,"style":706},"268","a CDN such as Cloudflare in front of Pages can add headers and caching, at the cost of a second system",[709,1031,1032],{},"For open-source docs these limits rarely matter; for a product site several of them do.",[37,1034,1035,1049,1059,1065,1071],{},[40,1036,1037,1040,1041,1044,1045,1048],{},[57,1038,1039],{},"No custom headers."," You cannot set a Content Security Policy, HSTS with preload, or ",[18,1042,1043],{},"Cache-Control",". A ",[18,1046,1047],{},"\u003Cmeta http-equiv>"," tag covers some CSP directives but not all.",[40,1050,1051,1054,1055,1058],{},[57,1052,1053],{},"Fixed caching."," Responses carry ",[18,1056,1057],{},"Cache-Control: max-age=600",". Content-hashed assets that could be cached for a year are revalidated every ten minutes, which costs repeat visitors a round trip per asset.",[40,1060,1061,1064],{},[57,1062,1063],{},"No server-side redirects."," Moved pages need HTML files with a meta refresh, which is slower and weaker for search engines. Jekyll's redirect plugin generates these for you; other generators need a small script.",[40,1066,1067,1070],{},[57,1068,1069],{},"No pull request previews."," Pages has one production site per repository. Previews need another host or a separate repository.",[40,1072,1073,1076],{},[57,1074,1075],{},"Limits."," Sites should stay under 1 GB, each deployment times out after 10 minutes, and there is a soft bandwidth limit of 100 GB a month.",[14,1078,1079,1080,524,1084,30],{},"For open-source project documentation these are acceptable trade-offs for free, zero-maintenance hosting. For a company's product site, the missing headers and caching usually justify a CDN-backed host; see ",[26,1081,1083],{"href":1082},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002F","Netlify vs Vercel Deployment Strategies",[26,1085,1087],{"href":1086},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002F","Cloudflare Pages Edge Caching Setup",[32,1089,1091],{"id":1090},"adding-checks-before-deploy","Adding Checks Before Deploy",[14,1093,1094,1095,1097,1098,1102,1103,1106],{},"The build job is the place for quality gates. Add a link check on the built output before ",[18,1096,562],{},", so a broken build never publishes; see ",[26,1099,1101],{"href":1100},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests\u002F","Checking Links in Pull Requests",". For pull requests, run the same build and checks in a separate workflow triggered on ",[18,1104,1105],{},"pull_request"," without the deploy job, so contributors get feedback even though there is no preview site.",[32,1108,1110],{"id":1109},"measured-impact","Measured Impact",[14,1112,1113,1114,1116,1117,1120],{},"An open-source project with a 600-page Hugo documentation site moved from a workflow that force-pushed built files to a ",[18,1115,20],{}," branch to the Actions deployment above. The repository shrank from 2.1 GB to 180 MB after the old branch was deleted, clone times for contributors fell accordingly, and deploys dropped from about four minutes to two because the push of thousands of changed files was replaced by a single artifact upload. The project also moved to a custom domain, which removed 340 hand-written links that had needed the ",[18,1118,1119],{},"\u002Frepo\u002F"," prefix.",[32,1122,1124],{"id":1123},"pitfalls-rollback","Pitfalls & Rollback",[37,1126,1127,1135,1141,1155,1164],{},[40,1128,1129,1132,1133,30],{},[57,1130,1131],{},"Source still set to a branch."," The workflow succeeds but nothing changes on the site; check ",[57,1134,59],{},[40,1136,1137,1140],{},[57,1138,1139],{},"Missing base path."," Unstyled pages and 404s on a project site; configure the generator's base.",[40,1142,1143,1146,1147,1150,1151,1154],{},[57,1144,1145],{},"Jekyll processing."," With Actions deployment, Pages does not run Jekyll, so folders starting with ",[18,1148,1149],{},"_"," are served as-is; no ",[18,1152,1153],{},".nojekyll"," file is needed.",[40,1156,1157,1160,1161,1163],{},[57,1158,1159],{},"Environment protection rules."," A rule that restricts ",[18,1162,71],{}," to certain branches blocks deploys from others.",[40,1165,1166,1169],{},[57,1167,1168],{},"Rollback:"," re-run the deploy job of an earlier successful workflow run; it republishes that run's artifact while it is retained.",[32,1171,1173],{"id":1172},"conclusion","Conclusion",[14,1175,1176,1177,1179,1180,1182],{},"Deploying to GitHub Pages with Actions works with any static site generator: set the source to GitHub Actions, build the site, upload it with ",[18,1178,562],{}," and publish with ",[18,1181,570],{}," using OIDC. Configure the base path for project sites or use a custom domain, add checks before the upload, and keep Pages' limits in mind — no headers, fixed caching, no redirects and no previews. For documentation and open-source projects it is hard to beat; for production product sites, a CDN-backed host usually fits better.",[32,1184,1186],{"id":1185},"faq","FAQ",[1188,1189,1191],"h3",{"id":1190},"do-i-still-need-a-gh-pages-branch-to-deploy-to-github-pages","Do I still need a gh-pages branch to deploy to GitHub Pages?",[14,1193,1194],{},"No. With the source set to GitHub Actions, a workflow uploads the built site as a Pages artifact with actions\u002Fupload-pages-artifact and publishes it with actions\u002Fdeploy-pages. No branch holds the built files, which keeps repository history clean.",[1188,1196,1198],{"id":1197},"why-are-my-css-and-links-broken-on-usernamegithubiorepo","Why are my CSS and links broken on username.github.io\u002Frepo?",[14,1200,1201],{},"Project sites are served from a subpath, so root-relative links such as \u002Fassets\u002Fapp.css point to the wrong place. Configure the generator's base path, for example base in Astro or baseURL in Hugo, to \u002Frepo\u002F, or use a custom domain so the site is served from the root.",[1188,1203,1205],{"id":1204},"can-i-set-custom-headers-or-redirects-on-github-pages","Can I set custom headers or redirects on GitHub Pages?",[14,1207,1208],{},"No. GitHub Pages does not support custom response headers, server-side redirects or rewrite rules, and cache lifetimes are fixed at about ten minutes. Sites that need security headers, long-lived asset caching or many redirects should use a CDN in front or a different host.",[1188,1210,1212],{"id":1211},"are-there-limits-on-github-pages-sites","Are there limits on GitHub Pages sites?",[14,1214,1215],{},"Published sites should be under 1 GB, deployments time out after 10 minutes, and there is a soft bandwidth limit of 100 GB per month. Pages is intended for project sites and documentation, not commercial high-traffic sites.",[32,1217,1219],{"id":1218},"related","Related",[37,1221,1222,1230,1237,1244,1251],{},[40,1223,1224,743,1227,1229],{},[57,1225,1226],{},"Parent:",[26,1228,29],{"href":28}," — every workflow pattern.",[40,1231,1232,1236],{},[26,1233,1235],{"href":1234},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions\u002F","Building Astro Sites with GitHub Actions"," — the build job in more depth.",[40,1238,1239,1243],{},[26,1240,1242],{"href":1241},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fhow-to-set-up-github-actions-for-hugo-deployments\u002F","GitHub Actions for Hugo Deployments"," — Hugo-specific setup.",[40,1245,1246,1250],{},[26,1247,1249],{"href":1248},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely\u002F","Upgrading Jekyll and Ruby Versions Safely"," — moving off the built-in Jekyll build.",[40,1252,1253,1255],{},[26,1254,1087],{"href":1086}," — when you need headers and caching.",[1257,1258,1259],"style",{},"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}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":83,"searchDepth":105,"depth":105,"links":1261},[1262,1263,1264,1265,1266,1267,1268,1269,1270,1271,1272,1278],{"id":34,"depth":105,"text":35},{"id":51,"depth":105,"text":52},{"id":75,"depth":105,"text":76},{"id":714,"depth":105,"text":715},{"id":899,"depth":105,"text":900},{"id":929,"depth":105,"text":930},{"id":1090,"depth":105,"text":1091},{"id":1109,"depth":105,"text":1110},{"id":1123,"depth":105,"text":1124},{"id":1172,"depth":105,"text":1173},{"id":1185,"depth":105,"text":1186,"children":1273},[1274,1275,1276,1277],{"id":1190,"depth":115,"text":1191},{"id":1197,"depth":115,"text":1198},{"id":1204,"depth":115,"text":1205},{"id":1211,"depth":115,"text":1212},{"id":1218,"depth":105,"text":1219},[1280,1282,1285,1286],{"name":1281,"item":822},"Home",{"name":1283,"item":1284},"Production-Ready Deployment & CI\u002FCD Workflows","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":29,"item":28},{"name":5,"item":1287},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions\u002F","2026-09-18","Deploy any static site generator to GitHub Pages with the official Actions workflow: artifacts, base paths, custom domains and what Pages cannot do.","md",[1292,1293,1294,1295],{"q":1191,"a":1194},{"q":1198,"a":1201},{"q":1205,"a":1208},{"q":1212,"a":1215},{},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions",{"title":5,"description":1289},"production-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions\u002Findex","article","DceEinhkMua71V2GWCXY7ofwMbb9txQ7qniycBiNKXM",[1303,1306,1309,1312,1315,1318,1321,1324,1327,1330,1333,1336,1339,1342,1345,1348,1351,1354,1357,1360,1363,1366,1369,1372,1375,1378,1380,1383,1386,1389,1392,1395,1398,1401,1404,1407,1410,1413,1416,1419,1422,1425,1428,1431,1434,1437,1440,1443,1446,1449,1452,1455,1458,1461,1464,1467,1470,1473,1476,1479,1482,1485,1488,1491,1494,1497,1500,1503,1506,1509,1512,1515,1518,1521,1524,1527,1530,1533,1536,1539,1542,1545,1548,1551,1554,1557,1560,1563,1566,1569,1572,1575,1578,1581,1584,1587,1590,1593,1596,1599,1602,1605,1608,1611,1614,1617,1620,1623,1626,1629,1632,1635,1638,1641,1644,1647,1650,1652,1655,1657,1660,1663,1666,1669,1672,1674,1677,1678,1681,1683,1685,1688,1691,1694,1697,1700,1703,1706,1709,1712,1715,1718,1721,1724,1727,1730,1733,1735,1738,1741,1744,1747,1750,1753,1756,1759,1762,1765,1768,1771,1774,1777,1780,1783,1786,1789,1792,1795,1798,1801,1804,1807,1810,1813,1816,1819,1822,1825,1828,1831,1834,1837,1840],{"path":1304,"title":1305},"\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":1307,"title":1308},"\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":1310,"title":1311},"\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":1313,"title":1314},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":1316,"title":1317},"\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":1319,"title":1320},"\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":1322,"title":1323},"\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":1325,"title":1326},"\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":1328,"title":1329},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":1331,"title":1332},"\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":1334,"title":1335},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":1337,"title":1338},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":1340,"title":1341},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":1343,"title":1344},"\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":1346,"title":1347},"\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":1349,"title":1350},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":1352,"title":1353},"\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":1355,"title":1356},"\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":1358,"title":1359},"\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":1361,"title":1362},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":1364,"title":1365},"\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":1367,"title":1368},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":1370,"title":1371},"\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":1373,"title":1374},"\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":1376,"title":1377},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":1379,"title":1249},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely",{"path":1381,"title":1382},"\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":1384,"title":1385},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":1387,"title":1388},"\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":1390,"title":1391},"\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":1393,"title":1394},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":1396,"title":1397},"\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":1399,"title":1400},"\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":1402,"title":1403},"\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":1405,"title":1406},"\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":1408,"title":1409},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":1411,"title":1412},"\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":1414,"title":1415},"\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":1417,"title":1418},"\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":1420,"title":1421},"\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":1423,"title":1424},"\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":1426,"title":1427},"\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":1429,"title":1430},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1432,"title":1433},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1435,"title":1436},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1438,"title":1439},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1441,"title":1442},"\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":1444,"title":1445},"\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":1447,"title":1448},"\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":1450,"title":1451},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1453,"title":1454},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1456,"title":1457},"\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":1459,"title":1460},"\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":1462,"title":1463},"\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":1465,"title":1466},"\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":1468,"title":1469},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1471,"title":1472},"\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":1474,"title":1475},"\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":1477,"title":1478},"\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":1480,"title":1481},"\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":1483,"title":1484},"\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":1486,"title":1487},"\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":1489,"title":1490},"\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":1492,"title":1493},"\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":1495,"title":1496},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1498,"title":1499},"\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":1501,"title":1502},"\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":1504,"title":1505},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1507,"title":1508},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1510,"title":1511},"\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":1513,"title":1514},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1516,"title":1517},"\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":1519,"title":1520},"\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":1522,"title":1523},"\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":1525,"title":1526},"\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":1528,"title":1529},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1531,"title":1532},"\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":1534,"title":1535},"\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":1537,"title":1538},"\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":1540,"title":1541},"\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":1543,"title":1544},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1546,"title":1547},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1549,"title":1550},"\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":1552,"title":1553},"\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":1555,"title":1556},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1558,"title":1559},"\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":1561,"title":1562},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1564,"title":1565},"\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":1567,"title":1568},"\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":1570,"title":1571},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1573,"title":1574},"\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":1576,"title":1577},"\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":1579,"title":1580},"\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":1582,"title":1583},"\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":1585,"title":1586},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1588,"title":1589},"\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":1591,"title":1592},"\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":1594,"title":1595},"\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":1597,"title":1598},"\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":1600,"title":1601},"\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":1603,"title":1604},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1606,"title":1607},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1609,"title":1610},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1612,"title":1613},"\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":1615,"title":1616},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1618,"title":1619},"\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":1621,"title":1622},"\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":1624,"title":1625},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1627,"title":1628},"\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":1630,"title":1631},"\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":1633,"title":1634},"\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":1636,"title":1637},"\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":1639,"title":1640},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1642,"title":1643},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1645,"title":1646},"\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":1648,"title":1649},"\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":1651,"title":1087},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup",{"path":1653,"title":1654},"\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":1656,"title":1101},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests",{"path":1658,"title":1659},"\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":1661,"title":1662},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1664,"title":1665},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1667,"title":1668},"\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":1670,"title":1671},"\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":1673,"title":1235},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions",{"path":1675,"title":1676},"\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":1297,"title":5},{"path":1679,"title":1680},"\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":1682,"title":1242},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fhow-to-set-up-github-actions-for-hugo-deployments",{"path":1684,"title":29},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds",{"path":1686,"title":1687},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1689,"title":1690},"\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":1692,"title":1693},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1695,"title":1696},"\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":1698,"title":1699},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1701,"title":1702},"\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":1704,"title":1705},"\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":1707,"title":1708},"\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":1710,"title":1711},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1713,"title":1714},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1716,"title":1717},"\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":1719,"title":1720},"\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":1722,"title":1723},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1725,"title":1726},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1728,"title":1729},"\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":1731,"title":1732},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1734,"title":1083},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies",{"path":1736,"title":1737},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates","Netlify Build Hooks for Content Updates",{"path":1739,"title":1740},"\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":1742,"title":1743},"\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":1745,"title":1746},"\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":1748,"title":1749},"\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":1751,"title":1752},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1754,"title":1755},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests","Preview Environments for Pull Requests",{"path":1757,"title":1758},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments","Password-Protecting Preview Deployments",{"path":1760,"title":1761},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts","Previewing Headless CMS Drafts",{"path":1763,"title":1764},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1766,"title":1767},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1769,"title":1770},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":1772,"title":1773},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1775,"title":1776},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1778,"title":1779},"\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":1781,"title":1782},"\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":1784,"title":1785},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1787,"title":1788},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1790,"title":1791},"\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":1793,"title":1794},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1796,"title":1797},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1799,"title":1800},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1802,"title":1803},"\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":1805,"title":1806},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1808,"title":1809},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1811,"title":1812},"\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":1814,"title":1815},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1817,"title":1818},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1820,"title":1821},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1823,"title":1824},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1826,"title":1827},"\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":1829,"title":1830},"\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":1832,"title":1833},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1835,"title":1836},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1838,"title":1839},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1841,"title":1842},"\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",1789722848022]