Cancer Australia Goes Live on Drupal 11 with GovCMS PaaS and PreviousNext

Staff Reporter

A blog post by Adam Bramley of PreviousNext describes how the team launched Cancer Australia’s website using GovCMS PaaS on Drupal 11. The project began on Drupal 10.3 and went live in early 2025 after overcoming tooling gaps in the GovCMS ecosystem.

The team removed the incompatible govcms/scaffold-tooling library and pulled deployment scripts directly during the Docker image build. The stack included PHP 8.4, Redis, OpenSearch, Storybook, and Vite. Local development used Docker Compose, with logs handled via the Lagoon Logs module integrated into a UDP listener container.

OpenSearch was used as a backend for decoupled React search interfaces, exposed through a read-only Nginx proxy. CI pipelines in GitLab followed a three-stage structure—build, code quality, and test—using cache reuse and tools like Playwright and PHPUnit. Component rendering was tested with the drupal-test-traits library.

Layout Builder was used across content types, supported by block plugins and embedded React apps. Twig templates were powered by Pinto’s Theme Objects, reusing design system components directly from Storybook. Graphs used the reCharts library via Drupal’s media system.

Reference: Turbo-charging Drupal with GovCMS PaaS by Adam Bramley (acbramley), PreviousNext (20 October 2025)

Drupal 11

GovCMS

PreviousNext

Storybook

DevOps

CI/CD

Docker

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.