Operations
Use this section after you write the content. Preview the site locally, build and deploy the output, configure comments and analytics, track theme versions, and diagnose problems. The previous five sections describe the site’s appearance and content. This section describes its build, deployment, and diagnosis.
Find it by task
| What you want to do | Where to go |
|---|---|
| See a change on your own machine | Local preview |
Build a deployable public/ |
Local preview |
| Deploy to GitHub Pages / Cloudflare / Netlify | Deploy |
Deploy to a subpath such as example.com/docs/ |
Deploy |
| Let readers comment at the end of a page | Comments |
| Connect Google Analytics or a self-hosted alternative | Analytics and SEO |
| Configure correct search engine indexing | Analytics and SEO |
| Upgrade the theme, or migrate from Docsy or 0.4 | Upgrade |
| Diagnose a build error, missing search results, or a 404 | Troubleshooting |
Preview changes with hugo server and build deployable output with hugo. Neither Node nor a CDN is required.
Publish public/ to GitHub Pages, Cloudflare Pages, or another static host. Set baseURL, review Content Security Policy, verify deployment, and prepare rollback.
Use giscus for page comments through GitHub Discussions. Control comments for the site or a page, and match light and dark themes.
Configure an optional analytics service. Check the canonical URLs, hreflang links, social cards, sitemap, and robots output that the theme generates.
Pin a theme version, upgrade to 1.5.1, migrate legacy content or a Docsy site, and keep a rollback path.
Diagnose build, language, search, and platform problems by symptom, cause, and fix. Run checks on your site.