GOV.UK DXP Components
Aleks Bochniak
I've been building a proof of concept GOV.UK Service website and have used Squiz's prebuilt GOV.UK DXP components. As I have been doing this, I've noticed some differences with the GOV.UK Design System and the ones available as pre-built components.
What is Squiz's roadmap for these components? Are there any plans to update or develop more in line with the documented GOV.UK Frontend Design System? What options are there for me to be able to extend or contribute towards the existing DXP component set?
Rafał Szarafiński
Thank you so much for the feedback. And for trying the prebuilt GOV.UK DXP components. We’d really value any specifics you can share about the differences you’re seeing. If you can point to particular components, behaviours, or HTML structure that diverge from the GOV.UK Design System, that would help us prioritize.
Roadmap and alignment with GOV.UK:
We designed these components to work with an external, evolving design system. Our goal is to align with GOV.UK Frontend’s HTML and behaviour so that, with the right styles and scripts, components work as expected. We do plan updates to follow GOV.UK changes; however, with our recent scope shift, we now schedule these through our roadmap. To assess and plan any changes, we’ll need a clear scope so we can estimate and schedule them properly.
Options to extend or contribute:
You can extend the component set directly. There’s a repository ready to download, so your team can customize and add components as needed. We also welcome contributions: feel free to open a Merge Request. Our team will review for compatibility, accessibility, and correct operation within our repository. We’re happy to provide guidance upfront if that helps.
Suggested next steps:
If you can share the specific gaps or desired updates (with examples or screenshots if possible), plus any priorities or timelines, we can recommend a path — whether quick fixes, incremental enhancements, or broader updates.
Thanks again for the thoughtful input. We’re keen to make this work well for your service and the wider community.
Aleks Bochniak
I think the main feedback I have at this stage comes in two parts:
- Using the existing components available. For something like Panels, Accordions, Tabs, it would be good to have more flexibility with component content, so that source view is editable within the 'wysiwyg' interface or custom code as an option. I found that using tables within tab content quite difficult as there aren't controls for that - this was experienced trying to the tab example on the design system website.
Example
https://fros-eval.matrix.squiz.cloud/govuk/dxp-components#heading-15
vs
https://design-system.service.gov.uk/components/tabs/
- Warning and In-page alert appear to be very similar
https://fros-eval.matrix.squiz.cloud/govuk/dxp-components#heading-8
vs
https://fros-eval.matrix.squiz.cloud/govuk/dxp-components#heading-16
Are you able to share access to the git repo for these components, so that I can go and compare how I've built my 'gov uk masthead' component vs your approach?