A government site has to look credible, work on every device and stay on-brand as content scales, all without needing a themer for every change. Convivial's design system gives editors real control over look and feel through configuration, not code, while keeping every page accessible and consistent.
Why design matters
How it works
Foundation
Tailwind and DaisyUI provide the underlying styling framework, giving every component a consistent, modern base.
Configure, don't code
Colour palettes, skins and effects are set through the theme UI. Palettes can be assigned per page region, and skins bundle up settings, effects and colours for campaigns or site sections in one click.
Build with components
Pages are assembled from Single Directory Components (Cards, Sliders, Accordions, Sections and more), each with built-in editor options. So design consistency holds even as different editors build different pages.
Check as you go
The theme UI reports contrast levels as you configure colour palettes, helping you stay WCAG 2.1 AA compliant before you publish.
Frequently asked questions
Why does Convivial use Tailwind and DaisyUI instead of Bootstrap?
Tailwind and DaisyUI are the modern successor to frameworks like Bootstrap, offering a more maintainable, utility-based approach to styling. This gives Convivial sites a consistent design language while making it easier to build and extend components over time.
Can I change the look of my site without a developer?
Yes. Colour palettes, skins and visual effects are configured through no-code theme settings, largely removing the need for a dedicated themer for day-to-day design changes.
What is a skin, and how is it different to a colour palette?
A colour palette defines a set of colours that can be applied to page regions. A skin bundles up settings, effects and colour palettes together, so you can apply a complete visual treatment, for a campaign or site section, for example, in a single step.
Are Convivial's components accessible?
Yes. Components are built to WCAG 2.1 AA, and the theme UI reports colour contrast as you configure palettes, helping you stay compliant before you publish rather than auditing after the fact.
What is a Single Directory Component (SDC)?
An SDC is a structured, self-contained component, such as a Card, Slider or Accordion, that bundles its markup, styling and configuration options together. This makes components consistent, reusable and easier for editors to configure without developer involvement.
Upcoming events
-
ConferenceMorpht at DrupalSouth
Morpht sponsors DrupalSouth and will be showcasing its work at the next conference.