Hugo CMS? That's BCMS.

Looking for a Hugo CMS? Keep Hugo as your SSG. BCMS is the headless CMS for Hugo content: fetch entries in a prep script, export Markdown or data files, then build. Agents write entries. Clients edit in the UI.

npm i @thebcms/client
NorthloopNorthloop
7 members
Search
⌘+K
Administration
  • Settings
  • Trash
Entries
  • ·
  • @thebcms
  • Terms of use
  • ·
  • Log out
Hello Mira,
Have a nice day at work!
Entries created
12
Megabytes uploaded
14.2
Members
7
Manage members
See all members
Mira Chen
mira@northloop.co
Admin
Priya Nair
priya@northloop.co
Admin
Sofia Reyes
sofia@northloop.co
Amara Okonkwo
amara@northloop.co
Nadia Hassan
nadia@northloop.co
Camila Duarte
camila@northloop.co
Jordan Hale
jordan@northloop.co
Admin
Elias Brandt
elias@northloop.co
Kenji Watanabe
kenji@northloop.co
Luca Moretti
luca@northloop.co
Theo Andersson
theo@northloop.co
Invites
  • alex.morgan@northloop.co
    Pending
    Cancel invitation
  • Recently uploaded
    homepage-hero.jpg
    fintech-case-cover.jpg
    design-systems-blog.jpg
    studio-team.jpg

    Why use a headless CMS for Hugo

    This is not Hugo the SSG. It is a headless CMS for Hugo sites: structured content in BCMS, static output from Hugo, no forced Hugo module.

    • Build-script content pull

      Use @thebcms/client (or the REST API) in a Node prep step. Export entries to content/ or data/, then run Hugo as usual.

    • Keep your Hugo theme

      Layouts, shortcodes, and archetypes stay yours. BCMS supplies structured content; Hugo renders the HTML.

    • Markdown or data files

      Map BCMS entries to Markdown with front matter, or to JSON/YAML under data/. Fit whatever your theme expects.

    What you get from a CMS for Hugo

    Headless content for Hugo static sites: JS client or REST prep step, Markdown or data export, locales, and agent-ready APIs.

    • Separate theme from content

      Developers own Hugo config and templates. BCMS holds pages, posts, and media. Agents can create entries at scale.

    • JS client or REST API

      Pull with @thebcms/client from Node, or call the BCMS REST API from any language before the Hugo build.

    • No Hugo module lock-in

      No required Hugo module for content. Fetch, write files, build. Your deployment pipeline stays simple.

    • CDN-backed content API

      Pull content from BCMS over CDN at build time. Host the Hugo output wherever you already deploy.

    • Multilingual Hugo sites

      Add locales in BCMS. Generate language-specific content files for Hugo multilingual mode.

    • Agents and humans together

      Agents create entries over MCP. Clients edit in the dashboard. Rebuild Hugo when content changes.

    Structured content for Hugo builds

    Model once in BCMS. Export at build time. Render with Hugo layouts and shortcodes.

    14-day free trial · No credit card required

    Inputs

    Dropdowns, files, numbers, and rich text. Standard fields for editable content.

    BCMS + Hugo

    Fetch entries in a prep script, write Markdown or data files, then run hugo. Agents can write entries from code.

    Generated types

    Optional TypeScript interfaces for Node scripts that pull and shape content before the Hugo build.

    Media

    Folders, previews, and CDN URLs for images and files referenced from Hugo pages.

    Widgets

    Reusable blocks like galleries and CTAs. Model once, map to shortcodes or partials in Hugo.

    Groups

    Author bios, SEO fields, and repeated shapes. Define once and reuse across entries.

    Multilingual Hugo sites

    Manage content in any number of languages in BCMS, then render localized pages in Hugo without awkward workarounds.

    General
    Docs

    Status

    Last updated 4 days ago

    Language

    English

    Links

    There is one other entry that links to this entry:

    10 Fabulous Infographics about JAMstack

    A picture is worth a thousand words, so let's see through these infographics what makes JAMstack so beloved.

    Publishing statuses for Hugo

    Draft, review, and publish content in BCMS, then ship only what is ready into your Hugo app.

    Frequently asked questions

    Common questions about using BCMS as a Hugo CMS or headless CMS for Hugo.

    Is Hugo a CMS, or do I need a Hugo CMS?

    Hugo is a static site generator. A Hugo CMS usually means a content system that feeds Hugo. BCMS is that headless layer: editors work in BCMS, a build script writes content files, then hugo generates the site.

    You can call the REST API from any language, including Go. Most teams use a short Node script with @thebcms/client before hugo, which is the path we document.

    On rebuild. Trigger a new Hugo build when content changes (webhook, CI, or manual deploy). Clients edit in BCMS; the static site refreshes on the next build.

    Yes. Connect via MCP with scoped API keys. Agents write entries. Clients edit them in the dashboard. Rebuild to publish.

    Map each BCMS entry to a Markdown file with front matter, or to JSON/YAML under data/. Your layouts and content organization stay under your control.

    Add a prep script that installs @thebcms/client, fetches an entry, writes a content file, then run hugo. The trial is 14 days free.

    No. Docs and a free trial are available. Contact us if you want direct support.

    Alright. Enough pitch.

    14 days free. About 13 seconds. Zero demo tax.

    14-day free trial · No credit card required