A Ruby on Rails application used by UK government publishers to create and manage content for GOV.UK.
Whitehall is a content management system built with Ruby on Rails that powers the UK government's GOV.UK publishing platform. It provides government publishers with tools to create, manage, and publish official content including news, publications, and announcements. The system handles the complete content workflow from creation through to publication on the public-facing website.
Government publishers and content editors within UK government departments who need to publish official information on GOV.UK. Technical teams maintaining government digital services who require a reliable content publishing system.
As the official publishing platform for GOV.UK, Whitehall offers a purpose-built solution for government content workflows with built-in auditing, compliance features, and established Rails conventions. It provides the reliability and structure needed for official government communications while following government digital service standards.
Publishes government content on GOV.UK
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports structured content creation with auditing and versioning, as detailed in the edition workflow documentation, ensuring reliable publishing processes.
Maintains detailed logs of all changes for accountability and compliance, covered in the auditing guide, which is critical for government use.
Provides specific interfaces for managing news and publications, optimized for official content types and publisher workflows on GOV.UK.
Follows established Rails app conventions for maintainability, making it familiar for developers in that ecosystem, as noted in the technical documentation.
Requires the GOV.UK Docker environment for running and testing, which adds significant overhead and limits ease of adoption for external teams.
Deeply integrated with UK government infrastructure and standards, making it challenging to adapt or migrate for other use cases without heavy modification.
Technical docs are spread across multiple files and assume familiarity with GOV.UK systems, hindering onboarding and external contribution efforts.