Camp

Design system with design assets, tokens, and code components for ActiveCampaign products

Why we like it

Camp is a tidy example of a product team giving AI features a home of their own rather than bolting them on. Its Active Intelligence layer has a signature visual language, a gradient border and an AI icon that appear on the AI-driven variants of chips, toggles, inputs and more, so people can always tell when they're working with the model.

Around that, Camp runs a clear three-track model: a current standard for new work, the Active Intelligence layer being folded into it, and a legacy set kept only as a fallback. It's a small thing that says a lot about a team thinking through how AI should feel in a product, not only whether it works.

Where it fits

Camp fits React SaaS teams adding AI features who want a consistent 'this is AI' signal across the interface. It's ActiveCampaign's own system: the docs and Storybook are public, but the repo is a private internal one, so treat it as a reference for the idea rather than something to adopt.

Ideas to borrow

  1. 01.

    Language & naming

    Give AI features one consistent visual marker (here, a gradient and an AI icon) across every component, so people always recognize AI-driven UI.

  2. 02.

    Governance

    Run a three-track model (current, incoming, legacy-fallback) so migration happens without blocking new feature work.

Screenshots

Fig. 1Camp's introduction, splitting getting-started paths for developers and designers, with a persistent 'Ask AI' input docked at the bottom of the page.
Fig. 2Camp's color page, with a four-tier diagram tracing a hex value through primitive and semantic tokens to the components that render them.
Fig. 3The Slider page: a live slider above an editable props table, with sections for migrating to Next Gen alongside the current variants.

Further reading

Related