9 min read
Many people who know HubSpot from the CRM are surprised when they discover what lies behind Content Hub. They thought it was just a visual page editor, the drag-and-drop kind, and they find a complete development environment, with a command line, themes in code, a templating language, and functions that run on the server.
If you come from the web development world and are going to build on Content Hub, this guide is your map. Instead of diving straight into a detail, I will give you the big picture: the workflow, the pieces of the environment, and the role of each, with pointers to go deeper where it makes sense. The idea is that by the end you know what to master and where to start.
Content Hub is more than an editor
The most common misunderstanding is thinking Content Hub is just a marketing tool to assemble pages. It is that, but it is also a real development platform. Beneath the visual editor, there is a system of themes, modules, and templates written in code, plus a templating language and data and server resources. The editor is the tip marketing sees; development is the foundation that supports it.
This dual nature is Content Hub's great strength. It lets the developer build a solid base, with well-made pieces and visual governance, and lets marketing operate that base on its own day to day. When used well, it is the rare balance between technical power and content-creator autonomy. Understanding both layers is what lets a developer get the most out of the platform.
The development workflow
Development on Content Hub combines local editing with the cloud platform. You write the theme files on your own machine, with the code editor and version control you prefer, and push them to the portal when they are ready. The site's structure, templates and modules, lives in those files under the development team's control, while the pages' content stays editable in the interface by marketing.
That separation between structure and content is what keeps the site sustainable. The developer controls how the site is built, with review and version control, and marketing controls what each page says, with no risk of breaking the layout. It is that clear boundary that lets the two teams work in parallel without stepping on each other.
The command line and local development
The bridge between your machine and the portal is HubSpot's command line, the CLI. It is what authenticates your local environment with the portal, lets you see changes in preview while you work, and pushes the theme files to the platform. With the CLI, you develop with the comfort of your local tools and sync with HubSpot whenever you want.
This local development workflow is what separates building a professional theme from editing in the browser. You gain version control, code review, and the speed of working locally, with preview to check the result before publishing. For any serious Content Hub project, mastering the CLI is the starting point that unlocks everything else.
Themes and modules: the visual pieces
The theme is the site's visual base. It bundles templates, styles, and global settings, and uses design tokens that marketing adjusts without code, which keeps the identity consistent and gives the team autonomy. A well-built theme is what lets you change the brand color in one click instead of in a whole project.
Modules are the reusable pieces that build pages. A mature development team invests in generic, well-named modules that get reused across many pages, instead of creating single-use blocks for each situation. Well-built themes and modules are the difference between a site marketing runs on its own and one that depends on the developer for every adjustment.
HubL: the language that brings templates to life
HubL is HubSpot's templating language, and it is what turns fields and data into HTML. With HubL, a module stops being static and gains logic: it loops over lists, decides what to show with conditions, formats values with filters. It is what lets you build pieces that adapt to the content they receive, instead of fixed, dumb structures.
Mastering HubL covers the overwhelming majority of templating needs on Content Hub. The most useful patterns, loops over repeater fields, item counting, conditions, and data conversion, are few and combine to solve almost everything. It is a learning investment that pays off fast, because it is present in practically every module you will build.
HubDB and serverless: data and server logic
For data-driven content, Content Hub offers HubDB, a table system that feeds dynamic pages. Instead of creating a manual page for each item, you store the items in a table and generate the pages from it, which is ideal for catalogs, directories, and listings that grow over time.
And for logic that cannot run in the browser, for security reasons or to access external systems, there are serverless functions. They execute on the server, talk to external APIs using securely stored secrets, and return data to the page. They are the right resource when the site needs back-end intelligence, without you having to maintain a separate server for it. Worth planning around: both features are tied to the plan level, HubDB and its dynamic pages from Professional up, and serverless functions on Enterprise, so confirm the tier before you design an architecture that leans on them.
|
A tip from someone who has been burned: do not try to learn everything at once. Start with the CLI and the local workflow, then themes and modules, then HubL, and only then HubDB and serverless when a project really calls for it. Trying to master every piece at the same time is the recipe for getting lost. Most sites do just fine with theme, modules, and HubL. |
Why this matters for your operation
Mastering development on Content Hub is what lets you build a site that serves the revenue operation, and not just a pretty storefront. A well-developed site loads fast, gives marketing autonomy, integrates with the CRM and the rest of the platform, and grows without becoming a maintenance snowball. Each well-built piece, from the theme to the server functions, translates into a site that works in the business's favor.
Without that mastery, the site becomes a recurring cost and a bottleneck. Slow pages drive visitors away and hurt ranking, rigid modules trap marketing, and the lack of integration isolates the site from the rest of the operation. Investing in quality development on Content Hub is investing in a digital asset that supports demand generation, instead of a weight the team drags along.
In practice: the site nobody could evolve
A company had a HubSpot site built in a rush, with no local development workflow, no structured theme, and single-use modules scattered around. Every change was made straight in the browser, with no version control, and nobody had the confidence to touch it, because one adjustment could break something else without warning. The site had become untouchable.
The turnaround was adopting the proper development workflow: CLI, version control, a theme with tokens, and reusable modules. With the right structure, the team went back to evolving the site safely, knowing each change went through review and that the base was solid. The same site nobody dared touch became a platform the team improves continuously.
Where to start
If you are just starting on Content Hub, the recommended path is clear: first the CLI and the local development workflow, then the theme structure and module creation, next HubL to give the pieces logic, and finally HubDB and serverless when a specific project requires dynamic content or server logic. Each stage builds on the previous one, and following that order avoids the feeling of jumping from stone to stone without firm footing.
Frequently asked questions
Do I need to code to use Content Hub?
To edit content, no. To create themes, modules, and dynamic pages, yes. Content Hub serves both audiences: marketing in the visual editor and the developer in code, each in their own layer.
Where do I write the theme code?
On your machine, with HubSpot's command line connected to the portal, version-controlling the files. Then you push to the portal, and the pages' content stays editable in the interface by marketing.
When should I use HubDB or serverless?
HubDB for pages that come from a data table, like catalogs and directories. Serverless for logic that must run on the server, like talking to an external API using secrets securely.
What is the difference between a theme and a module?
The theme is the site's visual base, with styles and global settings. Modules are the reusable pieces that build pages within that theme. The theme gives the identity, the modules build the content.
Where should a developer start on Content Hub?
With the CLI and local development workflow, then themes and modules, then HubL, and finally HubDB and serverless when a project calls for it. Following that order gives a firm base before the more advanced resources.
Does Content Hub work for large sites?
Yes. With a well-structured theme, reusable modules, HubDB for dynamic content, and serverless for server logic, it supports large, complex sites, integrated with the CRM and the rest of the platform.
About to develop or evolve a site on HubSpot Content Hub? At Insight Sales, as a HubSpot partner, we develop CMS themes, modules, and integrations with a professional workflow. Talk to our team and find out how we can help.
Ready to take your operation to the next level?
Talk to a specialist and see how we can help.
