Document suggested package naming convention

[timkelty]

e.g. suitcss-components-, suitcss-utils-

[necolas]

is anyone writing open source components and utils? should they be?

[necolas]

oh i just saw #110, ok that's cool.

[timkelty]

I have some I just need to publish.
I know https://github.com/trunkclub has a few as well.

[timkelty]

https://github.com/trunkclub/suitcss-components-form
https://github.com/trunkclub/suitcss-components-table
https://github.com/tgfjt/suitcss-components-starratings

[giuseppeg]

A good first step would be to write down some guidelines and requirements for components to qualify.
The big question there is how do we keep them consistent? @necolas do you guys have global variables for margin, padding, font-size etc?

[timkelty]

It seems a component should always stand alone, so to me, consistency between component's variables isn't that important.

I usually end up something like:

:root {
  --App-gutter-size: 20px;
}
...
:root {
  --Arrange-gutter-size: var(--App-gutter-size);
  --Grid-gutter-size: var(--App-gutter-size);
}

[oleersoy]

One possible requirement is that suit components should be DRY by assuming the presence of the normalize.css / base.css (Base Styles) layer.

Designers may want to leave suit off the name of the component for the reason that the component works across various frameworks, and respects the structure and conventions of all of them.

I would be great if the theme styling methodology worked really well across autonomous components...maybe it does...Need to experiment more with it. How do we get autonomous components to employ variables so that consistency across them can be plugged (Color palette, font, use of gradients, drop shadows, animation timing, etc)?

[giuseppeg]

@timkelty yeah 👍 we should make that clear and a requirement I guess :)