govuk-frontend VS react-scanner

It depends on the level of contribution.

You can contribute by responding to the discussions in the backlog[0], by improving the actual distributed styles and code[1] or suggesting improvements to the documentation in the link I posted above.

Bigger changes need to be backed up with user research, evidence of user needs and accessibility reviews and checks.

[0] https://github.com/alphagov/govuk-design-system-backlog

[1] https://github.com/alphagov/govuk-frontend

However looking at the samples with modern browsers I was unable to see the overflow issue. So it might now be entirely possible that setting negative margin is not required anymore. And it happens to actually be harmful: negative margin can change the reading order in VoiceOver!

It's quite literally open source, with a permissive license. It's often more than just inspiration, it's the literal code.

Check it out: https://design-system.service.gov.uk/ and: https://github.com/alphagov/govuk-frontend (MIT license)

For those who may be interested, the front end is actually open sourced for third parties to use.

To that end, we're still in the process of dropping support for IE 8–10, along with reducing IE 11 to 'functional'—it doesn't always look the same, but users can still complete tasks.

They're also looking to reduce support for IE11:

> has had any ability to tell me where, how often, or even whether a particular component is in use in the production UI

I built a dashboard to display this for the design system I work on at my day job to give product designers better visibility into this, using a library called react-scanner[0] and some logic related to the way our different product repos are structured. there are probably other libraries for this sort of thing in different ecosystems, and you can always build your own with a parser as well.

[0] https://github.com/moroshko/react-scanner

react-scanner - Extract React components and props usage from code