The Hugo CMS for all your projects

They become Snippets. You describe a shortcode once in your CloudCannon config, listing its parameters and how they map to editor inputs, and from then on editors insert it from a menu inside the Content Editor. Your markdown content file still contains your shortcode, so your templates don’t change and your site builds the same way locally.

The extended version, always, since so many Hugo sites depend on Sass transpiling. The build environment ships a default version and you can pin whichever release you need, which matters if you’re on a site that’s sensitive to template API changes between releases. Embedded Dart Sass is available too.

Yes. CloudCannon fetches your module imports during the build like any other Hugo environment. Private module repositories are one case worth planning for, since your build needs access to them. Site Mounting handles this by treating your module repo as a second CloudCannon site and mounting its files into your main one, which also triggers a rebuild whenever the module changes.

Two things are happening. CloudCannon builds your actual site, so the preview is your real HTML rather than an approximation. On top of that, data bindings connect fields in the sidebar to elements on the page, so text and image edits update as you type instead of waiting for a rebuild. For full component-level page building, Bookshop renders your Hugo components in the browser so editors can add, reorder, and nest them live.

Yes, and they’re a good fit for editing. Leaf and branch bundles keep an entry’s images next to its index.md, so when an editor uploads a photo it lands in the bundle rather than a shared uploads folder. You can configure where new files go, and the path the file picker is opened at, per collection (or even per input).

Data files in data/ are editable through the Data Editor, with the same typed inputs you’d configure for frontmatter. This is how most teams hand off navigation menus, office locations, pricing tables, team member lists, and other structured content that shouldn’t live in a Markdown body. Taxonomy terms — like tags and categories — can be exposed as select inputs so editors pick from your existing tags instead of inventing new ones.

Yes — Hugo’s build speed is most of the answer. PaperCut runs more than 4,000 pages with 110 editors working autonomously, and cut publishing time from weeks to minutes. Large content directories are where a Git-based CMS tends to pull ahead, because editors work on branches and merge rather than queueing behind each other in a database.

No. Hosting is included and optional. Plenty of teams keep their production deploy where it is and connect CloudCannon to the same repository, so editor commits trigger their existing pipeline. Others use CloudCannon hosting for staging and review, then publish elsewhere. Both setups are documented.