Skip to content

For developers

A HubSpot theme workspace your agent can actually work in.

A hosted workspace with the theme’s source, a live preview, a checker that knows HubSpot’s rules and a deploy request a person approves. Built on a headless UI library for HubSpot, so the agent generates the look instead of picking it from a menu.

Connect your portalSee the tooling
Check
Theme
themespot · 22 templates · 55 sections
Checker
0 errors · warnings listed by rule
Preview
home, pricing, docs rendered
Deploy
Awaiting a named approver
The theme workspace: a new chat on the left with suggested edits, and a live preview of the ThemeSpot home page on the right with desktop, tablet and phone views, history and Send to HubSpot.
  1. 1Theme source, versioned
  2. 2Live preview
  3. 3Deploy waits for you
  • Source-form theme, yours to export as a built HubSpot theme
  • Every change checked before it can deploy
  • Reduced motion and editor safety by construction

The hosted workspace.

One place for the theme’s source, its compiled preview and its history. Edit by file or by chat; every save is a checkpoint you can restore from the history rail. A check runs on every batch: HubSpot’s own validation, the standards checker, link audit, image weight, field shapes.

  • Source, preview and history in one window
  • Checkpoints you can restore
  • A check on every batch, by rule name
  • Deploy request, not a deploy button
How a deploy is approved
The theme workbench with the History rail open: checkpoints with Restore, a send that failed with what HubSpot reported, and versions marked Live in HubSpot.

Dev tooling, local and hosted.

Theme Dev Tools for HubSpot is a free Claude Code plugin: it renders a HubL or React theme locally, compares the render with the design and uploads with HubSpot’s CLI. The hosted MCP server adds the workspace, the library, content and QA tools to the same agent. Use what the job needs.

  • Free local plugin: render, compare, upload
  • Hosted MCP: the same agent, more tools
  • HubL guidance that knows the platform’s refusals
  • Honest about what local cannot do
Read about the plugin
The theme workspace: a new chat on the left with suggested edits, and a live preview of this site’s home page on the right with desktop, tablet and phone views, history and Send to HubSpot.

A headless UI library for HubSpot.

Accordion, tabs, dialog, popover, navigation with a mega panel, carousel, forms, HubDB and blog hooks: behaviour, accessibility and HubSpot’s semantics with no look of their own. The theme compiles its own Tailwind. Islands hydrate when visible. Reduced motion is honoured in every moving part.

  • No CSS of its own; the look is this site’s
  • Server-rendered, islands on visibility
  • Field composites and a Styles spine shared by every module
  • A standards checker for platform and editor safety
How the library is used

Content population by chat.

After the deploy, pages are created from templates already holding their layout, fields filled by path, links resolved to real pages and bulk edits sampled before they count. Drafts land straight away. Publishing waits for an approver. You stop doing the typing.

  • Pages from templates, fields by path
  • Links resolve to page ids, not strings
  • Bulk edits sampled first
  • Every edit journalled
See content management
A chat asking to update the page title on the pricing, careers and contact pages: the three pages it ran on, marked approved, and all three live with the new title.

Automated QA, before and after deploy.

Before: the checker, project validation and the link audit gate the deploy request. After: more than 80 deterministic checks read every page, an agent drives a real browser through the money page, and a fix is charged only when the same rule has verified it.

  • Deploy gate: checker, validation, link audit, image weight
  • Site scan: SEO, links, spelling, security headers, page weight, AI crawler access
  • Browser walkthrough, recorded where the plan allows
  • Fixes verified by the rule that found them
How site health scans work
The site health findings: site-wide issues with their severity, status and notes, each with Investigate and Fix it for me.

Client tweaks without a ticket.

Give the client a seat on their own portal with code access off. They ask for the copy change, the new page, the swapped image; the draft lands in their editor and their named approver publishes. The theme stays yours.

  • Code access off for clients
  • Drafts in HubSpot’s editor
  • Approvals with a paper trail
  • Theme changes stay with developers
A chat asking to update the page title on three pages: the pages it will change, then Ready for your approval with Approve and Reject, the agent paused until someone decides.

On every plan, for every role.

The same guardrails whether you are a developer, an agency or an SEO. Nothing reaches a live site without a named person approving it.

  1. Guardrails

    Drafts first. A person approves what goes live.

    Edits land as drafts in the HubSpot editor your team already uses. Publishing, redirects, forms, files and theme deploys queue for approval, with a plain-words description of what will happen and a journal of who approved what.

  2. User groups

    Roles for your team, a guest seat for each client.

    Your organisation owns its portals. Each person is an admin, manager, developer or viewer on each portal; the theme workspace is for developers. A client is a guest on their own portal and sees nothing else.

  3. End-client site management

    Hand the client a site they cannot break.

    Clients chat with their own site with code access off: pages, copy, images, redirects and forms, inside the theme you built. Theme changes stay with your developers.

  4. MCP

    Their own AI, on their own website.

    Connect ThemeSpot to Claude, ChatGPT or any MCP client. The same tools, the same approvals, the same roles: an AI the client already uses manages the site inside the guardrails you set.

You’re thinking: “I don’t trust generated HubSpot code.”
Fair. Here’s the answer:

Neither do we. Nothing deploys without the checker passing, HubSpot’s validation, a preview and a named person approving the request.

You’re thinking: “I want my own tooling.”
Fair. Here’s the answer:

Keep it. The local plugin is free and needs no account; the hosted workspace is there when the job needs the library, content or QA tools.

You’re thinking: “What do I get if I leave?”
Fair. Here’s the answer:

The built HubSpot theme, exported, ready to upload. The site keeps running in the portal exactly as it is.

Connect a portal. Nothing deploys until you say so.

Free to connect. The theme workspace is on paid plans.

Connect your portalRead the docs