Custom theme
Your own theme with the brand in the theme settings, a global header and footer and a set of modules for every type of page.
THEME
HubSpot & CRMHubSpot CMS developer for themes and modules.
A custom theme, a module that doesn’t exist yet or dynamic pages from HubDB. We build it in HubL, with fields your marketing team fills in. For businesses and, white-label, for agencies.
Themes, modules and HubDB in HubL, with fields your team fills in.
Fixed price per job, up front · module, child theme or HubDB · excl. VAT
- Based in Julianadorp, NL · Chamber of Commerce 54099897 · you talk to the people who build it
In short
What does a HubSpot CMS developer do?
A HubSpot CMS developer builds the parts of a HubSpot website you can’t make with a few clicks in the editor: themes, custom modules, templates and dynamic pages. Sharp Creations does this from Julianadorp, the Netherlands, in HubL, with the HubSpot CLI and Git. We build for businesses that want to extend their HubSpot site and, white-label, for agencies that need a developer. You get a fixed price per job up front, after your brief: we price a single module, a child theme or a HubDB integration per piece. Looking for a complete site with a custom theme? See having a HubSpot website built.
What we build
What we build in the HubSpot CMS.
Extending a bought theme
Adapting a Marketplace theme through a child theme, so updates from its maker don’t overwrite your changes.
CHILD THEME
Custom modules
Modules that don’t exist yet: pricing tables, comparison tools, tabs, maps or an FAQ with FAQPage schema.
MODULES
HubDB and dynamic pages
Jobs, locations or products in a table, with an overview and a page of its own for every row.
HUBDB
Blog and listing templates
Blog overview, article page, authors and tags, with filters and clean metadata.
TEMPLATES
Multilingual and memberships
Language variants with correct hreflang, and gated pages for clients or members where your licence allows it.
MORE
Example
What a module looks like.
A custom module consists of fields (fields.json) and a template in HubL (module.html). This is a shortened version of a card module as we build them:
[
{ "name": "heading", "label": "Heading", "type": "text", "default": "Why clients choose us" },
{ "name": "body", "label": "Text", "type": "richtext" },
{ "name": "button", "label": "Button", "type": "link" },
{ "name": "button_text", "label": "Button text", "type": "text", "default": "Request a quote" }
]{# module.html #}
<div class="card">
<h3>{{ module.heading }}</h3>
{{ module.body }}
{% if module.button.url.href %}
<a class="button" href="{{ module.button.url.href }}">{{ module.button_text }}</a>
{% endif %}
</div>In the editor the marketer only sees Heading, Text, Button and Button text. The styling comes from the theme, so every new page looks like the rest. If someone leaves the button empty, it disappears instead of showing an empty button.
How we work
How we build.
- Locally, with the HubSpot CLI. We build on our own machines and push changes to a test or developer portal. Your live site never sees half-finished versions.
- Everything in Git. Every change can be traced and rolled back. At delivery you get the repository.
- Brand in one place. Colours, fonts and spacing live in the theme settings. Change the brand colour and it changes everywhere.
- Fields a marketer understands. Clear names, default values and help text, so nobody has to open the code.
- Documentation per module. A short guide: what the module does, which fields it has and what to watch for.
The design can come from you (Figma or Adobe XD), or we create it based on your brand.
Who it's for
For businesses and for agencies.
For businesses already on HubSpot that want more from their site: a new feature, a cleaned-up theme or a complete new site. For a new site, see having a HubSpot website built; for a move, see migrating to HubSpot CMS.
For agencies we build the same under your name. We don’t approach your clients and our name appears nowhere in the code. How that works and what it costs is on white-label HubSpot development and the rates for agencies.
Our work is there to see: nine HubSpot websites are listed by name on our cases page.
Frequently asked questions
Good to know.
Question not listed? Just ask, one of the four of us will answer.
Ask your questionChild theme or a custom theme?
A child theme is faster and cheaper if a bought theme is already close to your design. A custom theme is better if your brand and page types are far from it. We advise once we’ve seen your design.
Can you adapt a bought Marketplace theme?
Yes. We do it through a child theme or our own modules, so updates from the theme’s maker don’t overwrite your changes.
What works on Content Hub Starter and what only on Professional?
Themes and custom modules also work on Starter. HubDB and dynamic pages need Professional, and some features such as memberships or serverless functions need a higher tier. HubSpot changes this regularly, so we check it in your portal up front.
Do you turn a Figma design into HubSpot?
Yes. We translate the design into theme settings and modules, and tell you where something has to work differently in HubSpot than in Figma.
Do marketers get documentation?
Yes, a short guide per module: what it does, which fields it has and what to watch for.
Who owns the code?
You do, once the invoice is paid. You get the files and the Git repository.
Which theme or module do you need?
Send a design, an example or a few sentences. You get a fixed price or focused questions within one working day.