status | implementation | status_last_reviewed | status_notes |
---|---|---|---|
accepted |
done |
2024-03-04 |
We're getting close to being able to archive this again, with the publishing apps removing their dependency on Bootstrap |
The govuk-admin-template gem has been deprecated for a while, and new GOV.UK admin applications should be built using the layout component in govuk_publishing_components. Ideally, we would have migrated all our applications to use the new Design System and publishing components, however there are still several in active use which still rely on govuk-admin-template. The GitHub project is archived, and is therefore read-only.
This RFC proposes un-archiving the project to allow iterative accessibility fixes to be applied to live applications.
Importantly, this RFC does not propose removing the deprecation notice, or advocate for significant development of govuk_admin_template. It is intended as a stop-gap that acknowledges the slow pace of migration to the Design System, and its intention is to yield accessibility fixes for users prior to those migrations taking place.
When govuk-admin-template was deprecated and made read-only back in July 2018, we anticipated projects would be swiftly migrated to the GOV.UK Design System. There are many benefits to this, and projects should still aim to be migrated.
Three and a half years on, we still have 18 projects referencing govuk-admin-template. This includes many publishing apps, most prominently Whitehall.
Several accessibility issues have been identified our publishing applications which stem from govuk-admin-template. Some of these are relatively easy fixes, however we can't apply them because the repository is read-only.
With the intention of enabling quick wins for some perennial accessibility issues, we propose:
-
We will un-archive govuk-admin-template on GitHub, making it possible to release new versions of the gem with accessibility fixes.
-
GOV.UK developers may release new versions of the gem to address critical accessibility, usability, and security issues.
-
Teams MUST endeavour to migrate pages and applications to the GOV.UK Design System where practical.
-
(Unchanged) Teams MUST NOT create new applications, user journeys or significant new features using
govuk-admin-template
.
-
By improving accessibility in the govuk-admin-template, there may be less impetus to migrate to the GOV.UK Design System. We believe the immediate benefits to users outweighs this concern. All applications are still expected to be migrated, and it's important that we retain senior management buy-in for the migration.
-
By enabling fixes in the underlying gems, we can start iteratively improving some of our oldest and most painful systems.
It's not possible to filter archived repositories in GitHub search yet, but manually filtering this search yields: