global-forms: master issue

[alexkilgour]

This issue aims to link all the other global-forms issues together in order to facilitate discussion around how we should handle this going forward

Issues

• global-forms: GDS style big checkboxes/radios #484
• global-forms: focus styles for inputs #168
• global-forms: Handling required fields #48
• global-forms: Should we nest errors with inputs? #49
• global-forms: adapt for internationalisation #50
• global-forms: Should we exclude all layout related elements? #51

Considerations

Some considerations for how we handle forms going forward

• Standardised UX across different brands?
• How do we handle error messaging (we already have global-status-message)?
• Handle form elements in a single component (global-forms) or individual (like GDS)?
• Do we include javascript validation?

[sturobson]

Now that a reworked version of global-forms is up and running as a release candidate version:

1. are the issues linked above still relevant for todays use cases?
2. are they fixed with the current release candidate?
3. can they be worked on as part of the release candidate workflow for '2022' global-forms?

cc @alexkilgour @Heydon

[sturobson]

There has been no update on this issue for 30 days. It is now marked as "stale". If you think this issue is still relevant and needs attention then reply with an update. If there is no update in 14 days, this issue will be closed.