[{"data":1,"prerenderedAt":10},["ShallowReactive",2],{"clay-page:\u002F3.x\u002Fdeployment":3},{"html":4,"toc":5,"description":6,"hero":7,"list":8,"socialImage":9},"\u003Ch1 id=\"deployment\">Deployment\u003C\u002Fh1>\n\u003Cp>A Clay build is a folder of static files. Publish it on GitHub Pages with a ready-made workflow, or on any other host.\u003C\u002Fp>\n\u003Cp>There is no server to run: any host that serves files can serve a Clay site. Two things matter everywhere:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>The base URL.\u003C\u002Fstrong> A site at \u003Ccode>https:\u002F\u002Fexample.com\u002Fdocs\u002F\u003C\u002Fcode> needs to know it lives under \u003Ccode>\u002Fdocs\u002F\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Building in CI.\u003C\u002Fstrong> Let your host or a workflow run \u003Ccode>clay build --strict\u003C\u002Fcode> on every push, so the site always matches your docs.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>If you publish on …\u003C\u002Fth>\n\u003Cth>Read\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>GitHub Pages\u003C\u002Ftd>\n\u003Ctd>\u003Ca href=\"\u002Fclay-example-repo\u002F3.x\u002Fdeployment\u002Fgithub-pages\" data-route=\"\u002F3.x\u002Fdeployment\u002Fgithub-pages\">GitHub Pages\u003C\u002Fa>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Netlify, Cloudflare Pages, GitLab Pages or your own server\u003C\u002Ftd>\n\u003Ctd>\u003Ca href=\"\u002Fclay-example-repo\u002F3.x\u002Fdeployment\u002Fother-hosts\" data-route=\"\u002F3.x\u002Fdeployment\u002Fother-hosts\">Other Hosts\u003C\u002Fa>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n",[],"A Clay build is a folder of static files. Publish it on GitHub Pages with a ready-made workflow, or on any other host.",null,true,"\u002F_clay\u002Fsocial\u002F3.x\u002Fdeployment.png",1792666368803]