A HubSpot site that keeps up with a global agency.
OneMagnify's website runs on HubSpot CMS, with shared modules across many pages. We maintain and extend it, adding new modules and layouts without letting a change on one page leak into another.
- Client
- OneMagnify
- Sector
- Marketing, data and technology
- What we did
- HubSpot CMS development, Module design and build, Careers page, Website maintenance, Staging setup
- Built to drive
- More qualified candidates.
- Live site
- onemagnify.com
The problem
On a shared module system, one change can show up everywhere.
OneMagnify's site is built from HubSpot modules reused across many pages. That speeds up page building, but a style written for one module instance can quietly override another, and a draft upload to a shared module can reach the live site. The team also needed pages that told the company's story better, starting with careers.
- Shared modules, so an edit on one page could change many others.
- A careers page built around a jobs list instead of the people behind it.
- Staging templates that shared modules with production.
The solution
Dedicated modules, scoped styles and a staging setup that can't touch production.
When a page needs something new, we build a small dedicated module instead of bending a shared one. Styles are scoped to each instance, and staging runs on its own templates and modules, so nothing reaches production until it has been reviewed.
Our intervention
What we took on.
The work runs as a steady stream of page and module changes on the live site.
- 01
Careers page
A dedicated testimonial module for employee quotes, and a careers hero reduced to one clear call to action in place of the jobs list.
- 02
Executive leadership
A new leadership layout on the About page that presents the executive team clearly on desktop and mobile.
- 03
Locations page
Los Angeles added to the office list, and location cards that inform without sending visitors to dead-end pages.
- 04
Staging and fixes
Staging templates isolated from production, plus fixes such as partner logos that now keep their proportions.
The Stega fix
Small modules, scoped styles, reviewed releases.
On a large CMS, most bugs come from reuse that nobody planned for. We make each change as narrow as it can be.
Dedicated over reused
A single quote got its own simple module after the shared slider brought along a default image and stray controls.
Scope every style
Padding and spacing are set per instance, so a second module on the same page cannot override the first.
Nothing unreviewed goes live
If a change touches a shared module, we roll back the module as well as the page row that uses it.
Stega initiatives
What we keep working on.
Maintenance is ongoing, and each request teaches us something about the module library.
Ongoing page changes
We take new layouts, content updates and fixes as the team needs them, tested on staging first.
Module library review
Next we propose a review of shared modules, to find the global styles most likely to leak between pages.
Careers content
We are ready to add more employee stories to the careers page as the team approves them.
Toolstack
The tools behind it.
- HubSpotThe CMS, templates and modules the whole site is built from.
- HubLModule and template logic inside HubSpot.
- JavaScriptSmall interactive behaviours inside modules.
- CSSInstance-scoped styles that keep modules from overriding each other.