What problem should the add-on solve?
Start with the editor or developer who will live with it every day, and the job they're trying to get done — not a feature list.
Bison designs and develops commercial and custom add-ons for ExpressionEngine and other content platforms, combining product thinking, UX, interface design, and real-world development.
Start with the editor or developer who will live with it every day, and the job they're trying to get done — not a feature list.
An add-on is a guest in someone else's interface. It should feel like it was always there, following the platform's patterns instead of fighting them.
Powerful tools tend to sprout settings. We design so the common path is obvious and the advanced options stay out of the way.
Clean integration with the host's APIs, careful performance on real sites, and code that survives the next major CMS release.
Commercial licensing, documentation, support, updates, and a product lifecycle that's planned from the start.
Visual page building.
Section-based page building that editors can actually use, inside the control panel they already know.
Product details →Modern structured editing.
A block editor for structured content that stays clean in the database and on the page.
Product details →SEO management.
Titles, descriptions, social and structured data, managed where the content lives.
Product details →Email delivery and diagnostics.
Reliable sending, with enough visibility to know why a message did or didn't arrive.
Product details →Documentation libraries.
Product docs written in Markdown, with versions, changelogs and search, published from the control panel you already use.
Product details →A lightweight support desk.
Customers open tickets on your site or by email, and your team works them in the control panel, with Slack alerts when it matters.
Product details →Design tokens for the whole site.
Colour, type, spacing and logos defined once, kept in light and dark schemes, and used everywhere as CSS variables and template tags.
Product details →Page building with guardrails.
Editors arrange pages from the parts you design, picking only from your tokens, so every page stays on brand.
Product details →Tabbed content, field by field.
Organises long entries into tabs, so editors see the fields that matter for each part of the page and nothing else.
Product details →Some add-ons start as one client's problem and become products. Some should stay private. Either way, the process is the same.
Start a Project ↗