Cypress is ideal for testing Drupal content moderation, but the learning curve is rather steep. Well, with the cypress-json-tests package, you can be done within a couple of hours.
Fewer surprises after launch
A good support arrangement means you hear about problems from us first. We scan your site's front-end libraries every month for critical, high, and moderate vulnerabilities, and we raise a ticket for anything we find.
You also get a dedicated account manager and project manager, and at least two developers on your site. Someone always knows how your site is built, and every change gets a second pair of eyes.
What you get:
- Security kept current. Updates are applied as new releases come out, with monthly vulnerability scans as a backstop.
- Help when you need it. Small fixes, content changes, and straight answers, with direct access to the developers working on your site.
- A site that keeps improving. New features and changes as your priorities shift, including machinery of government changes.
Our approach to support and maintenance
Keep it secure and current
We apply updates as new releases come out and scan your front-end libraries each month. Anything we find becomes a ticket. On GovCMS SaaS, the GovCMS team maintains the platform, and we look after your configuration and theme.
Answer questions and fix problems
Raise a request on our Redmine ticket board and it goes straight to the developers, with full visibility of progress. When something needs GovCMS's attention, we liaise with them on technical matters, bugs, and configuration issues.
Keep improving
Go-live is the first step in your site's evolution. We help you plan and build enhancements as needs change, from new features to content model updates.
Work with a dedicated team
You get a dedicated account manager and project manager, plus a frontend and a backend developer. With at least two developers on your site, there's always cover, peer review, and someone who knows how it's built.
Frequently asked questions
Yes. We support the sites we deliver, including security patches, module updates, performance monitoring, content model changes, and new features. Keeping the same development team matters, because they already know how your site is built and can extend it consistently.
A site assessment is a health check on an existing website. We look at UX and content quality, accessibility, SEO, performance, security, and information architecture. You receive a report that prioritises improvements and gives rough budget guidance, so you can plan where to invest.
In most cases, yes. We start with a site assessment to understand the codebase, configuration, and content model, then agree on what support should cover.
On GovCMS SaaS, the GovCMS team maintains the platform and codebase. We work alongside them, looking after your configuration and theme layer, fixing issues, and liaising with GovCMS on technical matters.
Through our Redmine ticket board. You can see every issue, follow its progress, and talk directly to the developers working on it.
Case studies
Case study
Morpht upgraded the AFSA and PPSR websites with new navigation, faster load times and WCAG 2.1 AA accessibility, winning two GovCMS Community Awards in 2025.
Case study
Morpht audited and enhanced the Great Barrier Reef Outlook Report 2024 website before launch, improving accessibility, performance and SEO on GovCMS SaaS.
Case study
Morpht rebuilt the TGA website on GovCMS, turning 95,000+ ARTG records into searchable pages and cutting 71 content types to 49 for 5.5 million monthly users.
Case study
Morpht moved the Attorney-General's Department website from SharePoint to GovCMS, organising 1,200 pages and 6,000+ publications into nine searchable sections.
Latest insights
Article
At DrupalSouth Community Day 2025, Marji Cermak shared a practical and grounded walkthrough of how visual regression testing, powered by BackstopJS, can prevent regressions long before they appear in production.
Article
At DrupalCon Vienna, Marji’s talk showcased a production-grade DevOps setup built specifically for Drupal teams that need reliability, repeatability and automation across multiple environments.
Article
This guide explains how to automate your Cypress tests for a Drupal site using GitHub Actions. We’ll cover setting up a full CI environment, connecting a MySQL database, running the Drupal server, and executing end-to-end Cypress tests - all inside GitHub’s cloud runners. You'll learn practical tips to speed up builds with caching and securely handle environment configurations.