A GovCMS build usually means commissioning a theme, a component library, a content model and an accessibility pass before anyone can start on content. Convivial ships with all four already built, so a site owner's budget and timeline go toward the site's actual purpose, not its plumbing.
Less to build. Less to worry about.
Frequently asked questions
How do we procure Convivial for GovCMS?
Convivial is available through the GovCMS Drupal Services Panel (DSP), on which Morpht has been selected as a supplier. This lets eligible government agencies engage Morpht directly for a build, rather than running an open tender.
Is Convivial accessible and WCAG 2.1 AA compliant?
Yes. Convivial is built to meet WCAG 2.1 AA, with features including skip links, keyboard navigation and dark mode, and is targeted to score 100 on Lighthouse accessibility and SEO audits.
What's included in ongoing DXP services?
Beyond the initial build, Morpht offers content personalisation, Recommendations as a Service, and AI content augmentation as ongoing DXP services through the panel arrangement, alongside broader UX, design, content and development support.
How does Convivial support governance across a large site?
Business-unit content ownership, scheduled content review workflows, and bulk redirect management help distributed teams keep large government sites accurate and accountable as they scale.
What search technology does Convivial use?
Convivial uses Apache Solr for enterprise-grade search, supporting facets and autocomplete so users and editors can reliably find the right content as the site grows.
Is it cheaper to build from scratch or start with Convivial for GovCMS?
A from-scratch build means commissioning a theme, a component library, a content model, and an accessibility pass before content work even starts. Convivial ships with all four already built, so budget and timeline go toward the site's actual purpose rather than its plumbing.
What's the difference between a Drupal distribution like Convivial and a custom build?
A distribution is a pre-built foundation: content types, components, view modes and accessibility already in place, that a team customises and extends. A custom build starts from zero, so every one of those pieces has to be designed, built and tested from scratch before content and features can begin.
What are the main risks in a GovCMS implementation, and how does Convivial address them?
The recurring risks are scope creep during foundational build work, accessibility non-compliance discovered late, and governance gaps on large or distributed sites. Convivial addresses these by shipping WCAG 2.2 AA compliance, a proven component library and content model as standard, plus governance tools like scheduled content review and editorial dashboards that flag accessibility and quality gaps automatically.
Does Convivial meet government build standards out of the box?
Yes. Convivial is built to WCAG 2.2 AA and is designed for the GovCMS SaaS platform, so agencies get a standards-compliant foundation without a separate compliance or remediation phase at the end of the build.
Top tasks
Recent news
-
AnnouncementsMorpht selected for GovCMS DXP Panel
Morpht is pleased to announce that we have been selected for the GovCMS Drupal Services Panel (DSP). -
AnnouncementsGovCMS Mega Meetup 2023
Morpht will be presenting on personalisation at the GovCMS Mega Meetup. -
InsightsHow personalisation works in Convivial for GovCMS
An overview of how personalisation works in Convivial for GovCMS.
Upcoming events
-
ConferenceMorpht at DrupalSouth
Morpht sponsors DrupalSouth and will be showcasing its work at the next conference.