Component organisation about govuk-components HOT 4 CLOSED

I think GOVUK might be too generic, when I was on GOV.UK we tried to avoid it because of the risk of collisions with internal & external libraries (compounded by problems with Govuk vs GOVUK and Rails inflection).

To the suffix question, I think -Component is indeed noise if we have a namespace, so perhaps this works:

GovukComponent::Panel.new
GovukComponent::Tag.new
GovukComponent::StartNowButton.new

from govuk-components.

I like separating components by directory; I'd argue for colocating (unit) specs next to components as well.

👍 for GOVUK::StartNowButtonComponent

from govuk-components.

I've submitted #5 and it feels like the the right approach. I can't see a way of keeping the names simple and predictable and organising with one component per directory.

Leaving the task unchecked in case I've missed something obvious.

from govuk-components.

Merged #5, I like this approach apart from the previously stated reasons (multiple components in one directory, the weird capitalisation of Govuk 😞).

Everything else is better though, so until something better comes along let's go with it

from govuk-components.