[{"data":1,"prerenderedAt":1414},["ShallowReactive",2],{"page:\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts":3,"all-docs-nav":871},{"id":4,"title":5,"body":6,"breadcrumb":847,"dateModified":857,"datePublished":857,"description":858,"extension":859,"faq":860,"meta":865,"navigation":394,"path":866,"seo":867,"slug":12,"stem":868,"type":869,"__hash__":870},"content\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts\u002Findex.md","Previewing Headless CMS Drafts",{"type":7,"value":8,"toc":828},"minimark",[9,13,17,26,31,48,52,193,197,204,334,341,348,352,355,358,447,454,573,577,584,588,591,660,663,667,670,701,705,708,712,747,751,754,758,763,766,770,773,777,780,784,787,791,824],[10,11,5],"h1",{"id":12},"previewing-headless-cms-drafts",[14,15,16],"p",{},"Editors who move from a traditional CMS to a headless one lose something they took for granted: the \"Preview\" button. In WordPress, preview renders the draft with the real theme instantly. On a static site backed by a headless CMS, the site is built from published content, so an unpublished draft is not in any build. Editors publish to see how a change looks, fix it, publish again, and occasionally ship a half-finished page to production because that was the only way to check the layout.",[14,18,19,20,25],{},"There are three ways to restore preview, from a zero-code second build to instant on-demand rendering. This guide explains each, how to connect the CMS's preview button to it, and how to keep draft content private. It is part of ",[21,22,24],"a",{"href":23},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002F","Preview Environments for Pull Requests",".",[27,28,30],"h2",{"id":29},"prerequisites","Prerequisites",[32,33,34,42,45],"ul",{},[35,36,37,38,25],"li",{},"A static site pulling content from a headless CMS at build time — see ",[21,39,41],{"href":40},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fwiring-a-headless-cms-to-a-static-build\u002F","Wiring a Headless CMS to a Static Build",[35,43,44],{},"A CMS with a draft or preview API (Contentful, Sanity, Storyblok, Strapi, Hygraph and most others have one) and a preview token.",[35,46,47],{},"The ability to add a second deployment or a small amount of server code.",[27,49,51],{"id":50},"three-approaches","Three Approaches",[53,54,55,189],"figure",{},[56,57,64,65,64,69,64,73,64,80],"svg",{"viewBox":58,"role":59,"ariaLabelledBy":60,"xmlns":63},"0 0 760 290","img",[61,62],"hcd-opt-title","hcd-opt-desc","http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg","\n  ",[66,67,68],"title",{"id":61},"Three ways to preview headless CMS drafts",[70,71,72],"desc",{"id":62},"A draft build: a second deployment built with the draft API, rebuilt on each save; no code, but a wait of one build. On-demand preview routes: a few server-rendered routes fetch the draft and render it with the same templates; instant, needs an adapter. Live visual editing: the CMS embeds the preview and updates it as the editor types; best experience, most integration work.",[74,75],"rect",{"x":76,"y":76,"width":77,"height":78,"fill":79},"0","760","290","#ffffff",[81,82,84,85,84,93,84,102,84,108,84,113,84,117,84,121,84,126,84,131,84,137,84,140,84,143,84,147,84,150,84,153,84,156,84,159,84,162,84,166,84,170,84,174,84,177,84,180,84,183,84,186,64],"g",{"style":83},"font-family:system-ui, sans-serif;font-size:12px","\n    ",[86,87,92],"text",{"x":88,"y":89,"fill":90,"style":91},"380","26","#1f2937","font-size:16px;font-weight:700;text-anchor:middle","Effort against preview speed",[74,94],{"x":95,"y":96,"width":97,"height":98,"rx":99,"fill":100,"style":101,"stroke":100},"20","46","230","220","8","#166a9e","fill-opacity:0.06",[86,103,107],{"x":104,"y":105,"fill":100,"style":106},"135","72","font-weight:700;text-anchor:middle","1 · Draft build",[86,109,112],{"x":110,"y":111,"fill":90},"36","102","second deployment",[86,114,116],{"x":110,"y":115,"fill":90},"124","built with draft token",[86,118,120],{"x":110,"y":119,"fill":90},"146","webhook rebuilds on save",[86,122,125],{"x":110,"y":123,"fill":124},"186","#3f6410","no code changes",[86,127,130],{"x":110,"y":128,"fill":129},"208","#b32b30","waits one build per save",[86,132,136],{"x":110,"y":133,"fill":134,"style":135},"248","#556071","font-size:11px","small and mid-size sites",[74,138],{"x":139,"y":96,"width":97,"height":98,"rx":99,"fill":124,"style":101,"stroke":124},"265",[86,141,142],{"x":88,"y":105,"fill":124,"style":106},"2 · On-demand routes",[86,144,146],{"x":145,"y":111,"fill":90},"281","\u002Fpreview\u002F[type]\u002F[id]",[86,148,149],{"x":145,"y":115,"fill":90},"fetches draft per request",[86,151,152],{"x":145,"y":119,"fill":90},"same templates",[86,154,155],{"x":145,"y":123,"fill":124},"instant",[86,157,158],{"x":145,"y":128,"fill":129},"needs server adapter",[86,160,161],{"x":145,"y":133,"fill":134,"style":135},"most teams' best balance",[74,163],{"x":164,"y":96,"width":97,"height":98,"rx":99,"fill":165,"style":101,"stroke":165},"510","#6a4c93",[86,167,169],{"x":168,"y":105,"fill":165,"style":106},"625","3 · Live visual editing",[86,171,173],{"x":172,"y":111,"fill":90},"526","preview inside the CMS",[86,175,176],{"x":172,"y":115,"fill":90},"updates as you type",[86,178,179],{"x":172,"y":119,"fill":90},"click-to-edit overlays",[86,181,182],{"x":172,"y":123,"fill":124},"best editor experience",[86,184,185],{"x":172,"y":128,"fill":129},"CMS-specific integration",[86,187,188],{"x":172,"y":133,"fill":134,"style":135},"marketing-heavy teams",[190,191,192],"figcaption",{},"Most teams start with a draft build and move to on-demand routes when editors ask for speed.",[27,194,196],{"id":195},"approach-1-a-draft-build","Approach 1: A Draft Build",[14,198,199,200,25],{},"Create a second deployment of the same repository — a separate Cloudflare, Netlify or Vercel project, or a separate environment — with two differences: it uses the CMS preview token, which returns drafts, and it is protected and marked ",[201,202,203],"code",{},"noindex",[205,206,211],"pre",{"className":207,"code":208,"language":209,"meta":210,"style":210},"language-js shiki shiki-themes github-light github-dark","\u002F\u002F src\u002Flib\u002Fcms.js\nconst isDraft = process.env.CONTENT_MODE === 'draft';\nexport const client = createClient({\n  space: process.env.CMS_SPACE,\n  accessToken: isDraft ? process.env.CMS_PREVIEW_TOKEN : process.env.CMS_DELIVERY_TOKEN,\n  host: isDraft ? 'preview.cms.example.com' : 'cdn.cms.example.com',\n});\n","js","",[201,212,213,222,253,274,286,310,328],{"__ignoreMap":210},[214,215,218],"span",{"class":216,"line":217},"line",1,[214,219,221],{"class":220},"sJ8bj","\u002F\u002F src\u002Flib\u002Fcms.js\n",[214,223,225,229,233,236,240,243,246,250],{"class":216,"line":224},2,[214,226,228],{"class":227},"szBVR","const",[214,230,232],{"class":231},"sj4cs"," isDraft",[214,234,235],{"class":227}," =",[214,237,239],{"class":238},"sVt8B"," process.env.",[214,241,242],{"class":231},"CONTENT_MODE",[214,244,245],{"class":227}," ===",[214,247,249],{"class":248},"sZZnC"," 'draft'",[214,251,252],{"class":238},";\n",[214,254,256,259,262,265,267,271],{"class":216,"line":255},3,[214,257,258],{"class":227},"export",[214,260,261],{"class":227}," const",[214,263,264],{"class":231}," client",[214,266,235],{"class":227},[214,268,270],{"class":269},"sScJk"," createClient",[214,272,273],{"class":238},"({\n",[214,275,277,280,283],{"class":216,"line":276},4,[214,278,279],{"class":238},"  space: process.env.",[214,281,282],{"class":231},"CMS_SPACE",[214,284,285],{"class":238},",\n",[214,287,289,292,295,297,300,303,305,308],{"class":216,"line":288},5,[214,290,291],{"class":238},"  accessToken: isDraft ",[214,293,294],{"class":227},"?",[214,296,239],{"class":238},[214,298,299],{"class":231},"CMS_PREVIEW_TOKEN",[214,301,302],{"class":227}," :",[214,304,239],{"class":238},[214,306,307],{"class":231},"CMS_DELIVERY_TOKEN",[214,309,285],{"class":238},[214,311,313,316,318,321,323,326],{"class":216,"line":312},6,[214,314,315],{"class":238},"  host: isDraft ",[214,317,294],{"class":227},[214,319,320],{"class":248}," 'preview.cms.example.com'",[214,322,302],{"class":227},[214,324,325],{"class":248}," 'cdn.cms.example.com'",[214,327,285],{"class":238},[214,329,331],{"class":216,"line":330},7,[214,332,333],{"class":238},"});\n",[14,335,336,337,340],{},"Point a CMS webhook at the draft deployment's build hook so every save triggers a rebuild, and set the CMS's preview URL template to the draft site, for example ",[201,338,339],{},"https:\u002F\u002Fdrafts.example.com\u002Fblog\u002F{slug}\u002F",". Editors click Preview, wait for the build, and see the page with the real templates.",[14,342,343,344,25],{},"The weakness is speed. A two-minute build means a two-minute wait after every change, and many saves in quick succession queue builds. Debounce the webhook, or use a build hook that cancels superseded builds; see ",[21,345,347],{"href":346},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates\u002F","Netlify Build Hooks for Content Updates",[27,349,351],{"id":350},"approach-2-on-demand-preview-routes","Approach 2: On-Demand Preview Routes",[14,353,354],{},"Most generators can mix static pages with a few server-rendered routes. Keep every public page static and add one preview route that fetches a draft from the CMS on each request and renders it with the same layout components.",[14,356,357],{},"In Astro with a server adapter, mark one page as on-demand:",[205,359,363],{"className":360,"code":361,"language":362,"meta":210,"style":210},"language-astro shiki shiki-themes github-light github-dark","---\n\u002F\u002F src\u002Fpages\u002Fpreview\u002F[type]\u002F[id].astro\nexport const prerender = false;\nimport { getDraft } from '..\u002F..\u002F..\u002Flib\u002Fcms';\nimport ArticleLayout from '..\u002F..\u002F..\u002Flayouts\u002FArticleLayout.astro';\n\nconst secret = Astro.url.searchParams.get('secret');\nif (secret !== import.meta.env.PREVIEW_SECRET) return new Response('Not found', { status: 404 });\n\nconst entry = await getDraft(Astro.params.type, Astro.params.id);\nif (!entry) return new Response('Not found', { status: 404 });\nAstro.response.headers.set('X-Robots-Tag', 'noindex');\nAstro.response.headers.set('Cache-Control', 'private, no-store');\n---\n\u003CArticleLayout entry={entry} \u002F>\n","astro",[201,364,365,370,375,380,385,390,396,401,407,412,418,424,430,436,441],{"__ignoreMap":210},[214,366,367],{"class":216,"line":217},[214,368,369],{},"---\n",[214,371,372],{"class":216,"line":224},[214,373,374],{},"\u002F\u002F src\u002Fpages\u002Fpreview\u002F[type]\u002F[id].astro\n",[214,376,377],{"class":216,"line":255},[214,378,379],{},"export const prerender = false;\n",[214,381,382],{"class":216,"line":276},[214,383,384],{},"import { getDraft } from '..\u002F..\u002F..\u002Flib\u002Fcms';\n",[214,386,387],{"class":216,"line":288},[214,388,389],{},"import ArticleLayout from '..\u002F..\u002F..\u002Flayouts\u002FArticleLayout.astro';\n",[214,391,392],{"class":216,"line":312},[214,393,395],{"emptyLinePlaceholder":394},true,"\n",[214,397,398],{"class":216,"line":330},[214,399,400],{},"const secret = Astro.url.searchParams.get('secret');\n",[214,402,404],{"class":216,"line":403},8,[214,405,406],{},"if (secret !== import.meta.env.PREVIEW_SECRET) return new Response('Not found', { status: 404 });\n",[214,408,410],{"class":216,"line":409},9,[214,411,395],{"emptyLinePlaceholder":394},[214,413,415],{"class":216,"line":414},10,[214,416,417],{},"const entry = await getDraft(Astro.params.type, Astro.params.id);\n",[214,419,421],{"class":216,"line":420},11,[214,422,423],{},"if (!entry) return new Response('Not found', { status: 404 });\n",[214,425,427],{"class":216,"line":426},12,[214,428,429],{},"Astro.response.headers.set('X-Robots-Tag', 'noindex');\n",[214,431,433],{"class":216,"line":432},13,[214,434,435],{},"Astro.response.headers.set('Cache-Control', 'private, no-store');\n",[214,437,439],{"class":216,"line":438},14,[214,440,369],{},[214,442,444],{"class":216,"line":443},15,[214,445,446],{},"\u003CArticleLayout entry={entry} \u002F>\n",[14,448,449,450,453],{},"The CMS preview URL becomes ",[201,451,452],{},"https:\u002F\u002Fwww.example.com\u002Fpreview\u002Farticle\u002F{id}?secret=...",". The preview is instant because nothing is built — one CMS request, one render. Next.js offers the same pattern with draft mode, which sets a cookie so the normal page routes render drafts for that browser. Eleventy and Hugo, which have no request-time rendering, can reach the same result with an edge function that fetches the draft and renders it with a shared template engine, though that means maintaining templates in two places.",[53,455,456,570],{},[56,457,64,462,64,465,64,468,64,471,64,487],{"viewBox":458,"role":59,"ariaLabelledBy":459,"xmlns":63},"0 0 760 260",[460,461],"hcd-req-title","hcd-req-desc",[66,463,464],{"id":460},"Request flow for an on-demand preview route",[70,466,467],{"id":461},"The editor clicks Preview in the CMS, which opens the preview route with the entry id and a secret. The route validates the secret, fetches the draft from the CMS preview API using a server-side token, renders it with the production layout, and returns it with noindex and no-store headers. Public pages continue to be served from static files.",[74,469],{"x":76,"y":76,"width":77,"height":470,"fill":79},"260",[472,473,84,474,64],"defs",{},[475,476,483],"marker",{"id":477,"viewBox":478,"refX":479,"refY":480,"markerWidth":481,"markerHeight":481,"orient":482},"hcd-req-arrow","0 0 10 10","9","5","7","auto-start-reverse",[484,485],"path",{"d":486,"fill":134},"M0,0 L10,5 L0,10 z",[81,488,84,489,84,492,84,497,84,503,84,508,84,514,84,519,84,523,84,527,84,531,84,535,84,538,84,543,84,548,84,552,84,554,84,558,84,562,84,566,64],{"style":83},[86,490,491],{"x":88,"y":89,"fill":90,"style":91},"One click, one render, no build",[74,493],{"x":95,"y":494,"width":495,"height":494,"rx":99,"fill":165,"style":496,"stroke":165},"60","140","fill-opacity:0.1",[86,498,502],{"x":499,"y":500,"fill":90,"style":501},"90","86","text-anchor:middle","CMS editor",[86,504,507],{"x":499,"y":505,"fill":134,"style":506},"104","font-size:11px;text-anchor:middle","clicks Preview",[74,509],{"x":510,"y":511,"width":97,"height":512,"rx":99,"fill":124,"style":513,"stroke":124},"210","50","80","fill-opacity:0.08",[86,515,518],{"x":516,"y":517,"fill":124,"style":106},"325","74","\u002Fpreview\u002Farticle\u002F{id}",[86,520,522],{"x":516,"y":521,"fill":90,"style":501},"96","check secret",[86,524,526],{"x":516,"y":525,"fill":90,"style":501},"114","render with ArticleLayout",[74,528],{"x":529,"y":494,"width":530,"height":494,"rx":99,"fill":100,"style":496,"stroke":100},"500","240",[86,532,534],{"x":533,"y":500,"fill":90,"style":501},"620","CMS preview API",[86,536,537],{"x":533,"y":505,"fill":134,"style":506},"server-side token only",[216,539],{"x1":540,"y1":499,"x2":541,"y2":499,"stroke":134,"style":542},"160","206","stroke-width:1.5px;marker-end:url(#hcd-req-arrow)",[216,544],{"x1":545,"y1":546,"x2":547,"y2":546,"stroke":134,"style":542},"440","82","496",[216,549],{"x1":547,"y1":550,"x2":551,"y2":550,"stroke":134,"style":542},"100","444",[74,553],{"x":510,"y":540,"width":97,"height":511,"rx":99,"fill":79,"stroke":134},[86,555,557],{"x":516,"y":556,"fill":90,"style":501},"181","response headers",[86,559,561],{"x":516,"y":560,"fill":134,"style":506},"199","X-Robots-Tag: noindex · no-store",[216,563],{"x1":516,"y1":564,"x2":516,"y2":565,"stroke":134,"style":542},"130","156",[86,567,569],{"x":88,"y":568,"fill":134,"style":506},"244","every public page is still a static file; only \u002Fpreview\u002F* runs code",[190,571,572],{},"The preview uses the production layout, so what editors see is what will ship.",[27,574,576],{"id":575},"approach-3-live-visual-editing","Approach 3: Live Visual Editing",[14,578,579,580,583],{},"Several CMSs now offer visual editing: the preview is embedded in the CMS, updates as the editor types, and overlays let editors click a heading on the page to jump to its field. Sanity's Presentation tool, Storyblok's Visual Editor and Contentful's Live Preview all work this way. They build on approach 2 — an on-demand route that renders drafts — and add a small client script that listens for content changes and re-renders. The integration is CMS-specific and adds client JavaScript to the preview route only, never to public pages. Because the preview is embedded in the CMS in an iframe, the preview route must allow framing by the CMS origin with a ",[201,581,582],{},"Content-Security-Policy: frame-ancestors"," header on preview responses only, while public pages keep denying it. Budget time for this integration: it touches the CMS configuration, the preview route and the content model, and it is easiest to add once the plain on-demand route is working.",[27,585,587],{"id":586},"choosing-between-them","Choosing Between Them",[14,589,590],{},"The deciding factor is usually how often editors preview. A documentation team that publishes a few pages a week and previews each once is well served by a draft build; a two-minute wait a few times a week costs little. A marketing team iterating on a landing page previews dozens of times an hour, and every minute of waiting is a minute of lost flow — on-demand routes pay for themselves within days.",[53,592,593,657],{},[56,594,64,599,64,602,64,605,64,607],{"viewBox":595,"role":59,"ariaLabelledBy":596,"xmlns":63},"0 0 760 230",[597,598],"hcd-time-title","hcd-time-desc",[66,600,601],{"id":597},"Time from save to visible preview by approach",[70,603,604],{"id":598},"For a 1,200-page site, a draft build takes about 90 seconds from save to preview. An on-demand preview route takes under one second. Live visual editing updates in about 200 milliseconds as the editor types.",[74,606],{"x":76,"y":76,"width":77,"height":97,"fill":79},[81,608,84,609,84,613,84,617,84,621,84,627,84,630,84,635,84,639,84,643,84,648,84,653,64],{"style":83},[86,610,612],{"x":88,"y":611,"fill":90,"style":91},"28","Save-to-preview time, 1,200-page site",[86,614,616],{"x":615,"y":517,"fill":90},"168","draft build",[74,618],{"x":97,"y":619,"width":545,"height":95,"fill":100,"style":620},"62","fill-opacity:0.45",[86,622,626],{"x":623,"y":624,"fill":90,"style":625},"662","77","text-anchor:end","≈ 90 s",[86,628,629],{"x":98,"y":115,"fill":90,"style":625},"on-demand route",[74,631],{"x":97,"y":632,"width":633,"height":95,"fill":124,"style":634},"112","6","fill-opacity:0.6",[86,636,638],{"x":568,"y":637,"fill":90},"127","\u003C 1 s",[86,640,642],{"x":98,"y":641,"fill":90,"style":625},"174","live visual editing",[74,644],{"x":97,"y":645,"width":646,"height":95,"fill":165,"style":647},"162","3","fill-opacity:0.7",[86,649,652],{"x":650,"y":651,"fill":90},"241","177","≈ 0.2 s, while typing",[86,654,656],{"x":88,"y":655,"fill":134,"style":506},"214","bar length is proportional to time",[190,658,659],{},"The first step from a build to a request-time render removes almost all the waiting.",[14,661,662],{},"Hosting constraints matter too. On-demand routes need an adapter and a host that runs server code — Cloudflare, Netlify, Vercel and most others do. A site deployed to plain object storage with no edge compute is limited to the draft build, or to a preview route hosted separately on a platform that can run it.",[27,664,666],{"id":665},"keeping-drafts-private","Keeping Drafts Private",[14,668,669],{},"Draft content is often the most sensitive content a site has: unannounced products, embargoed news, pricing changes. Whatever approach you use:",[32,671,672,679,685,695],{},[35,673,674,678],{},[675,676,677],"strong",{},"Keep the preview token server-side."," It must never appear in client JavaScript or in the static build of public pages.",[35,680,681,684],{},[675,682,683],{},"Require a secret."," The CMS preview link should carry a secret the route validates, or the route should sit behind authentication. Rotate the secret if it leaks.",[35,686,687,690,691,25],{},[675,688,689],{},"Protect draft deployments."," Put the whole draft site behind SSO; see ",[21,692,694],{"href":693},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments\u002F","Password-Protecting Preview Deployments",[35,696,697,700],{},[675,698,699],{},"Send noindex and no-store"," on every draft response, so neither search engines nor CDNs keep a copy.",[27,702,704],{"id":703},"measured-impact","Measured Impact",[14,706,707],{},"A marketing team using Contentful and Astro had no preview; editors published to check layouts and reverted about one change in twelve. The team first added a draft build, which editors used but found slow at about 90 seconds per save. They then added an on-demand preview route with the Cloudflare adapter, reusing the production layouts. Preview time dropped to under a second, reverted publishes fell from about one in twelve to one in eighty over the next quarter, and public pages remained fully static with no change in Core Web Vitals.",[27,709,711],{"id":710},"pitfalls-rollback","Pitfalls & Rollback",[32,713,714,720,726,735,741],{},[35,715,716,719],{},[675,717,718],{},"Separate preview templates."," Previews rendered with different code drift from production; always reuse the real layouts.",[35,721,722,725],{},[675,723,724],{},"Token in the client bundle."," Check the built output for the preview token string in CI.",[35,727,728,731,732,25],{},[675,729,730],{},"Caching drafts."," A CDN that caches a preview response can serve drafts to others; send ",[201,733,734],{},"no-store",[35,736,737,740],{},[675,738,739],{},"References to unpublished entries."," Drafts often link to other drafts; the preview fetch must request linked entries from the preview API too.",[35,742,743,746],{},[675,744,745],{},"Rollback:"," point the CMS preview URL back to the draft build, or remove it; public pages are unaffected.",[27,748,750],{"id":749},"conclusion","Conclusion",[14,752,753],{},"Static sites can give editors a real preview button. A draft build is the zero-code option, an on-demand preview route is instant and reuses production templates, and live visual editing adds in-CMS editing on top. Whichever you choose, keep the preview token on the server, require a secret or authentication, send noindex and no-store, and render with the same components as the live site so preview and production never disagree.",[27,755,757],{"id":756},"faq","FAQ",[759,760,762],"h3",{"id":761},"why-is-previewing-drafts-hard-on-a-static-site","Why is previewing drafts hard on a static site?",[14,764,765],{},"A static site is built ahead of time from published content, so an editor's unpublished changes are not in any build. Seeing a draft means either building a separate site that includes drafts, or rendering the draft on request with a small amount of server code.",[759,767,769],{"id":768},"what-is-the-simplest-way-to-preview-cms-drafts","What is the simplest way to preview CMS drafts?",[14,771,772],{},"A second deployment of the same site that builds with the CMS draft or preview API token and is rebuilt by a webhook whenever content is saved. It needs no code changes beyond an environment switch, but each preview waits for a build.",[759,774,776],{"id":775},"how-do-i-get-instant-draft-previews-without-a-server","How do I get instant draft previews without a server?",[14,778,779],{},"Most hosts let a static site include a few on-demand routes - Astro server islands or on-demand pages with an adapter, Next.js draft mode, or an edge function - that fetch the draft from the CMS preview API and render it with the same templates, while every other page stays static.",[759,781,783],{"id":782},"how-do-i-keep-draft-content-private","How do I keep draft content private?",[14,785,786],{},"Use the CMS's preview token only on the server side, never in client JavaScript, require a signed or secret preview link from the CMS, protect the draft deployment with authentication, and send noindex on every draft response.",[27,788,790],{"id":789},"related","Related",[32,792,793,802,807,812,817],{},[35,794,795,798,799,801],{},[675,796,797],{},"Parent:"," ",[21,800,24],{"href":23}," — the full preview workflow.",[35,803,804,806],{},[21,805,41],{"href":40}," — the published-content side.",[35,808,809,811],{},[21,810,694],{"href":693}," — securing draft sites.",[35,813,814,816],{},[21,815,347],{"href":346}," — triggering draft builds.",[35,818,819,823],{},[21,820,822],{"href":821},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduling-content-publication-with-cron-triggered-builds\u002F","Scheduling Content Publication With Cron-Triggered Builds"," — what happens after preview.",[825,826,827],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html .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":210,"searchDepth":224,"depth":224,"links":829},[830,831,832,833,834,835,836,837,838,839,840,846],{"id":29,"depth":224,"text":30},{"id":50,"depth":224,"text":51},{"id":195,"depth":224,"text":196},{"id":350,"depth":224,"text":351},{"id":575,"depth":224,"text":576},{"id":586,"depth":224,"text":587},{"id":665,"depth":224,"text":666},{"id":703,"depth":224,"text":704},{"id":710,"depth":224,"text":711},{"id":749,"depth":224,"text":750},{"id":756,"depth":224,"text":757,"children":841},[842,843,844,845],{"id":761,"depth":255,"text":762},{"id":768,"depth":255,"text":769},{"id":775,"depth":255,"text":776},{"id":782,"depth":255,"text":783},{"id":789,"depth":224,"text":790},[848,851,854,855],{"name":849,"item":850},"Home","\u002F",{"name":852,"item":853},"Production-Ready Deployment & CI\u002FCD Workflows","\u002Fproduction-ready-deployment-cicd-workflows\u002F",{"name":24,"item":23},{"name":5,"item":856},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts\u002F","2026-09-18","Show editors unpublished headless CMS content on a static site: a draft build, on-demand preview routes, or a small preview server, and how to secure each.","md",[861,862,863,864],{"q":762,"a":765},{"q":769,"a":772},{"q":776,"a":779},{"q":783,"a":786},{},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts",{"title":5,"description":858},"production-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpreviewing-headless-cms-drafts\u002Findex","article","X5ggTXjVMk8va3CfA9JRg1ZGWua28AvvEFU6O8A1d3I",[872,875,878,881,884,887,890,893,896,899,902,905,908,911,914,917,920,923,926,929,932,935,938,941,944,947,950,953,956,959,962,965,968,971,974,977,980,983,986,989,992,995,998,1001,1004,1007,1010,1013,1016,1019,1022,1025,1028,1031,1034,1037,1040,1043,1046,1049,1052,1055,1058,1061,1064,1067,1070,1073,1076,1079,1082,1085,1088,1091,1094,1097,1100,1103,1106,1109,1112,1115,1118,1121,1124,1127,1130,1133,1136,1139,1142,1145,1148,1151,1154,1157,1160,1163,1166,1169,1172,1175,1178,1181,1184,1187,1190,1193,1196,1199,1202,1205,1208,1211,1214,1217,1220,1223,1226,1229,1232,1235,1238,1240,1242,1245,1248,1251,1254,1257,1260,1263,1266,1269,1272,1275,1278,1281,1284,1287,1290,1293,1296,1299,1302,1305,1308,1311,1313,1316,1319,1322,1325,1328,1330,1332,1333,1336,1339,1342,1345,1348,1351,1354,1357,1360,1363,1366,1369,1372,1375,1378,1381,1384,1387,1390,1393,1396,1399,1402,1405,1408,1411],{"path":873,"title":874},"\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":876,"title":877},"\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":879,"title":880},"\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":882,"title":883},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fastro-vs-eleventy-for-documentation-sites","Astro vs Eleventy for Documentation Sites",{"path":885,"title":886},"\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":888,"title":889},"\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":891,"title":892},"\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":894,"title":895},"\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":897,"title":898},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress","Docs Frameworks: Docusaurus, Starlight and VitePress",{"path":900,"title":901},"\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":903,"title":904},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fmigrating-from-mkdocs-to-starlight","Migrating from MkDocs to Starlight",{"path":906,"title":907},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fversioned-documentation-with-docusaurus","Versioned Documentation with Docusaurus",{"path":909,"title":910},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fdocs-frameworks-docusaurus-starlight-vitepress\u002Fvitepress-for-library-documentation","VitePress for Library Documentation",{"path":912,"title":913},"\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":915,"title":916},"\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":918,"title":919},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fhugo-build-times-for-large-repositories","Hugo Build Times for Large Repositories",{"path":921,"title":922},"\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":924,"title":925},"\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":927,"title":928},"\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":930,"title":931},"\u002Fchoosing-the-right-static-site-generator-for-production","Choosing the Right Static Site Generator for Production",{"path":933,"title":934},"\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":936,"title":937},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem","Jekyll Plugin Ecosystem",{"path":939,"title":940},"\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":942,"title":943},"\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":945,"title":946},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fspeeding-up-slow-jekyll-builds","Speeding Up Slow Jekyll Builds",{"path":948,"title":949},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fjekyll-plugin-ecosystem\u002Fupgrading-jekyll-and-ruby-versions-safely","Upgrading Jekyll and Ruby Versions Safely",{"path":951,"title":952},"\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":954,"title":955},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators","Migrating Between Static Site Generators",{"path":957,"title":958},"\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":960,"title":961},"\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":963,"title":964},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fmigrating-between-static-site-generators\u002Fmigrating-from-gatsby-to-astro","Migrating from Gatsby to Astro",{"path":966,"title":967},"\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":969,"title":970},"\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":972,"title":973},"\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":975,"title":976},"\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":978,"title":979},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fnextjs-static-export-for-content-sites","Next.js Static Export for Content Sites",{"path":981,"title":982},"\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":984,"title":985},"\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":987,"title":988},"\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":990,"title":991},"\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":993,"title":994},"\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":996,"title":997},"\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":999,"title":1000},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites","Search for Static Sites",{"path":1002,"title":1003},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Findexing-hugo-sites-with-pagefind","Indexing Hugo Sites with Pagefind",{"path":1005,"title":1006},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fmultilingual-search-on-static-sites","Multilingual Search on Static Sites",{"path":1008,"title":1009},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fsearch-for-static-sites\u002Fpagefind-vs-algolia-docsearch","Pagefind vs Algolia DocSearch",{"path":1011,"title":1012},"\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":1014,"title":1015},"\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":1017,"title":1018},"\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":1020,"title":1021},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix\u002Fevaluating-ssg-accessibility-defaults","Evaluating SSG Accessibility Defaults",{"path":1023,"title":1024},"\u002Fchoosing-the-right-static-site-generator-for-production\u002Fssg-framework-selection-matrix","SSG Framework Selection Matrix",{"path":1026,"title":1027},"\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":1029,"title":1030},"\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":1032,"title":1033},"\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":1035,"title":1036},"\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":1038,"title":1039},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcdn-caching-rules-for-ssgs","CDN Caching Rules for SSGs",{"path":1041,"title":1042},"\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":1044,"title":1045},"\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":1047,"title":1048},"\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":1050,"title":1051},"\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":1053,"title":1054},"\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":1056,"title":1057},"\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":1059,"title":1060},"\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":1062,"title":1063},"\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":1065,"title":1066},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fcumulative-layout-shift-fixes-for-static-sites","Cumulative Layout Shift Fixes for Static Sites",{"path":1068,"title":1069},"\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":1071,"title":1072},"\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":1074,"title":1075},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Ffont-display-optional-vs-swap","font-display: optional vs swap",{"path":1077,"title":1078},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites","Font Loading Strategies for Static Sites",{"path":1080,"title":1081},"\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":1083,"title":1084},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Ffont-loading-strategies-for-static-sites\u002Fpreloading-fonts-without-double-downloads","Preloading Fonts Without Double Downloads",{"path":1086,"title":1087},"\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":1089,"title":1090},"\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":1092,"title":1093},"\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":1095,"title":1096},"\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":1098,"title":1099},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fimage-optimization-pipelines-in-astro","Image Optimization Pipelines in Astro",{"path":1101,"title":1102},"\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":1104,"title":1105},"\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":1107,"title":1108},"\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":1110,"title":1111},"\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":1113,"title":1114},"\u002Fperformance-optimization-core-web-vitals-for-ssgs","Core Web Vitals Optimization for SSGs",{"path":1116,"title":1117},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Fastro-islands-vs-full-hydration-performance","Astro Islands vs Full Hydration Performance",{"path":1119,"title":1120},"\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":1122,"title":1123},"\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":1125,"title":1126},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering","JavaScript Hydration & Partial Rendering",{"path":1128,"title":1129},"\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":1131,"title":1132},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fjavascript-hydration-partial-rendering\u002Freplacing-react-islands-with-web-components","Replacing React Islands with Web Components",{"path":1134,"title":1135},"\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":1137,"title":1138},"\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":1140,"title":1141},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Flargest-contentful-paint-optimization-for-static-sites","Largest Contentful Paint Optimization for Static Sites",{"path":1143,"title":1144},"\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":1146,"title":1147},"\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":1149,"title":1150},"\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":1152,"title":1153},"\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":1155,"title":1156},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fperformance-budgets-and-lighthouse-ci","Performance Budgets and Lighthouse CI",{"path":1158,"title":1159},"\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":1161,"title":1162},"\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":1164,"title":1165},"\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":1167,"title":1168},"\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":1170,"title":1171},"\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":1173,"title":1174},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fauditing-unused-preloads","Auditing Unused Preloads",{"path":1176,"title":1177},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed","Resource Hints and Navigation Speed",{"path":1179,"title":1180},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Finstant-navigation-with-speculation-rules","Instant Navigation with Speculation Rules",{"path":1182,"title":1183},"\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":1185,"title":1186},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fresource-hints-and-navigation-speed\u002Fprefetching-links-in-astro","Prefetching Links in Astro",{"path":1188,"title":1189},"\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":1191,"title":1192},"\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":1194,"title":1195},"\u002Fperformance-optimization-core-web-vitals-for-ssgs\u002Fthird-party-script-performance-on-static-sites","Third-Party Script Performance on Static Sites",{"path":1197,"title":1198},"\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":1200,"title":1201},"\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":1203,"title":1204},"\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":1206,"title":1207},"\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":1209,"title":1210},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fautomating-eleventy-deployments-with-cloudflare-pages","Automating Eleventy Deployments on Cloudflare Pages",{"path":1212,"title":1213},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup\u002Fconfiguring-redirects-on-cloudflare-pages","Configuring Redirects on Cloudflare Pages",{"path":1215,"title":1216},"\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":1218,"title":1219},"\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":1221,"title":1222},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcloudflare-pages-edge-caching-setup","Cloudflare Pages Edge Caching Setup",{"path":1224,"title":1225},"\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":1227,"title":1228},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fchecking-links-in-pull-requests","Checking Links in Pull Requests",{"path":1230,"title":1231},"\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":1233,"title":1234},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Feditorial-checks-with-vale-in-ci","Editorial Checks with Vale in CI",{"path":1236,"title":1237},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams","Content Workflows for Documentation Teams",{"path":1239,"title":822},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fscheduling-content-publication-with-cron-triggered-builds",{"path":1241,"title":41},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fcontent-workflows-for-documentation-teams\u002Fwiring-a-headless-cms-to-a-static-build",{"path":1243,"title":1244},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fbuilding-astro-sites-with-github-actions","Building Astro Sites with GitHub Actions",{"path":1246,"title":1247},"\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":1249,"title":1250},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fdeploying-to-github-pages-with-actions","Deploying to GitHub Pages with Actions",{"path":1252,"title":1253},"\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":1255,"title":1256},"\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":1258,"title":1259},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds","GitHub Actions for Automated SSG Builds",{"path":1261,"title":1262},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fgithub-actions-for-automated-ssg-builds\u002Fmatrix-builds-for-multi-site-monorepos","Matrix Builds for Multi-Site Monorepos",{"path":1264,"title":1265},"\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":1267,"title":1268},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs\u002Fenabling-incremental-builds-in-eleventy","Enabling Incremental Builds in Eleventy",{"path":1270,"title":1271},"\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":1273,"title":1274},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fincremental-builds-and-build-caching-for-ssgs","Incremental Builds and Build Caching for SSGs",{"path":1276,"title":1277},"\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":1279,"title":1280},"\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":1282,"title":1283},"\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":1285,"title":1286},"\u002Fproduction-ready-deployment-cicd-workflows","Production-Ready Deployment & CI\u002FCD for SSGs",{"path":1288,"title":1289},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Falerting-on-cache-hit-ratio-drops","Alerting on Cache Hit Ratio Drops",{"path":1291,"title":1292},"\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":1294,"title":1295},"\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":1297,"title":1298},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production","Monitoring Static Sites in Production",{"path":1300,"title":1301},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fmonitoring-static-sites-in-production\u002Flogging-404s-at-the-edge","Logging 404s at the Edge",{"path":1303,"title":1304},"\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":1306,"title":1307},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fconfiguring-vercel-for-hugo-and-eleventy","Configuring Vercel for Hugo and Eleventy",{"path":1309,"title":1310},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies","Netlify vs Vercel Deployment Strategies",{"path":1312,"title":347},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fnetlify-vs-vercel-deployment-strategies\u002Fnetlify-build-hooks-for-content-updates",{"path":1314,"title":1315},"\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":1317,"title":1318},"\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":1320,"title":1321},"\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":1323,"title":1324},"\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":1326,"title":1327},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fcleaning-up-stale-preview-deployments","Cleaning Up Stale Preview Deployments",{"path":1329,"title":24},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests",{"path":1331,"title":694},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fpassword-protecting-preview-deployments",{"path":866,"title":5},{"path":1334,"title":1335},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fpreview-environments-for-pull-requests\u002Fvisual-regression-testing-on-preview-deploys","Visual Regression Testing on Preview Deploys",{"path":1337,"title":1338},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fatomic-deploys-vs-incremental-uploads","Atomic Deploys vs Incremental Uploads",{"path":1340,"title":1341},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Fcanary-releases-for-static-sites","Canary Releases for Static Sites",{"path":1343,"title":1344},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites\u002Ffeature-flags-on-static-sites","Feature Flags on Static Sites",{"path":1346,"title":1347},"\u002Fproduction-ready-deployment-cicd-workflows\u002Frollbacks-and-deploy-safety-for-static-sites","Rollbacks and Deploy Safety for Static Sites",{"path":1349,"title":1350},"\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":1352,"title":1353},"\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":1355,"title":1356},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fauditing-npm-dependencies-in-ssg-pipelines","Auditing npm Dependencies in SSG Pipelines",{"path":1358,"title":1359},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fenabling-hsts-and-preload-safely","Enabling HSTS and Preload Safely",{"path":1361,"title":1362},"\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":1364,"title":1365},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites","Security Headers and Hardening for Static Sites",{"path":1367,"title":1368},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsecuring-deploy-credentials-with-github-oidc","Securing Deploy Credentials with GitHub OIDC",{"path":1370,"title":1371},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fsecurity-headers-for-static-sites\u002Fsubresource-integrity-for-third-party-assets","Subresource Integrity for Third-Party Assets",{"path":1373,"title":1374},"\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":1376,"title":1377},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fclean-urls-and-trailing-slashes-on-s3","Clean URLs and Trailing Slashes on S3",{"path":1379,"title":1380},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fcloudfront-functions-for-redirects","CloudFront Functions for Redirects",{"path":1382,"title":1383},"\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":1385,"title":1386},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites","Self-Hosting Static Sites on S3, Nginx and Caddy",{"path":1388,"title":1389},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-caddy","Serving a Static Site with Caddy",{"path":1391,"title":1392},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fserving-a-static-site-with-nginx","Serving a Static Site with Nginx",{"path":1394,"title":1395},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fself-hosting-static-sites\u002Fzero-downtime-deploys-with-symlink-swaps","Zero-Downtime Deploys with Symlink Swaps",{"path":1397,"title":1398},"\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":1400,"title":1401},"\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":1403,"title":1404},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites","Serverless Functions for Static Sites",{"path":1406,"title":1407},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fnetlify-functions-vs-cloudflare-workers","Netlify Functions vs Cloudflare Workers",{"path":1409,"title":1410},"\u002Fproduction-ready-deployment-cicd-workflows\u002Fserverless-functions-for-static-sites\u002Fprotecting-a-static-site-behind-authentication","Protecting a Static Site Behind Authentication",{"path":1412,"title":1413},"\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",1789722848216]