Custom Components
We build the part you're missing.
Some of what you need is a gap in the shared library, and that's ours to close. Some of it is built for the way you specifically operate, and that's quoted. Either way you aren't stuck with what's in the box.
How it works
From a complaint to a setting.
Tell us what's blocking you
If you hit a wall in the editor, flag it. It's usually a component that needs a setting it doesn't have yet.
We build it into the shared layer
The change goes into the shared component library, so it's part of the platform rather than a one-off attached to your account.
It ships defaulted to today's behavior
Pages you've already published render exactly as they did. You turn the new setting on when you want it.
What that means for you
A fix for you is a fix for everyone.
Ask for it once, everyone gets it
New behavior goes in as a setting on the shared component. The next operator who needs it finds it already there.
Nothing you already built changes
Every new setting arrives defaulted to current behavior, so your live pages keep rendering the way they render today.
Bespoke work is quoted, not guessed
Custom Components are quoted individually rather than priced per location, because what you're asking for is specific to how you operate.
Tell us what's wrong with your template.
That's usually a component that needs a setting. We want to hear it.