Support dynamic generation of classes

[timkelty]

Maybe a broader question as it could apply to several repos, but what do people think of using postcss plugins like postcss-for to make the generation of some of these classes dynamic?

I have done this in my own projects, and think it would likely be too much of a can of worms to include here, but thought I'd start the discussion.

[simonsmith]

I wouldn't be against the idea, but it does quickly move SUIT out of the 'future facing CSS' realm.

Would be nice to be able to configure this to use 12, 16, 24 etc though.

[timkelty]

Maybe theres an alternative -

• We could have an alternate include with the generation stuff.
• The main css files in the repo would be built using that with the default values
• Then you could either include the defaults as you do now, or include the "generator" directly

Something to think about at least.

[simonsmith]

I see, so each package would contain the output of the postcss tools? Could work.

Might also give more weight to moving the packages into a single repo to facilitate this.

[mlnmln]

I can understand the need for that, but I have reservations against this and would like SUIT CSS to stay true to the "future facing CSS' realm." I think this should stay at user level.