Alasdair McLeay

agreed Paragraph component should match govuk-frontend and current component moved to MarkDownParagraph or similar

@stevesims I would prefer that markdown support is out of scope for govuk-react for now, given the edge cases it creates and maintenance overhead. What do you think?

Also see #223

Changing the naming convention would likely be a breaking change so the semver should be updated to reflect (0.1 -> 0.2 for 0. versions)

Yes I think so

We could use the naming convention that Cosmos uses: `TextAreaInput` -> `TextArea` `TextAreaField` -> `Form.TextArea`

> How about? > > `TextArea` as the form field with all standard child elements > `TextArea.input` as the TextArea input alone > `TextArea.label` as the TextArea label alone >...

For the most part, input, label, hint and error aren't needed standalone. So the default export is always the field. It doesn't matter if TextArea.Input or TextArea.Hint don't resolve to...

Related #853

I think bringing styles in line with the latest version of govuk-frontend needs to be done across the board and part of a later milestone, when visual regression is back...