Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Simon Smith
@simonsmith
We added a quick start to the main repo recently but I'm also thinking of a more in depth getting started guide. If you've only just started using SUIT it might be interesting to hear how easy it was to get going
And I also plan to add some common patterns to the docs. Things that get asked a lot, like component spacing etc
Michael Wuergler
@radiovisual
Thanks @simonsmith . I am new to SUIT, and it was not hard to get up and running from the quick start guide, but after the quick start guide, there was a bit of a "ok, now what?" feeling. I had to piece things together by either guessing, looking through closed issues or browsing to plugin pages and looking at the tests. So I think that in general, new users don't get any hand holding, we have to dive deep. I kept going because I like the conventions of SUIT, and I like that the conventions are testable...but if I was not a patient person, I might have abandoned the SUIT tooling and plugins in favor of the SUIT conventions in Sass and lived a long, happy life. So overall, it's my opinion that if the documentation would improve, so would the adoption of the SUIT tooling and plugin space.
Simon Smith
@simonsmith
Good to know, thanks. If I think back then that experience matches mine too
Was it ambiguity around how to use the packages together, or around the tooling to get started? Or both?
If we can distill it down to a few specifics then that will be a good start for some issues
Michael Wuergler
@radiovisual
A little bit of both. As far as the tooling goes, the "How" (to use) is explained better than then the "Why" (to use). So the tooling profiles and descriptions could be improved. As far as the way packages work together, I think that is the part that lacks the most. I have had to do more detective work to figure things out, so it would be nice if there was a better way of connecting all the pieces together, the plugins kinda feel like they are just floating around in space, nothing tethering them to their relevant relationship(s). This is a big challenge though, I understand.
Simon Smith
@simonsmith
Okay, so some examples of the compnents working together sounds like a good addition
Did you read through the docs pages like this one - https://github.com/suitcss/suit/blob/master/doc/design-principles.md ?
It is perhaps a bit too abstract?
Please do continue to point out things. All very valuable
Michael Wuergler
@radiovisual
Yeah, I read through that document. It works as a (super-high-level) abstract of the SUIT ideologies, but nothing truly detailed. Sortof feels like we are reading dictionary definitions of the concepts instead of learning the true motivations for SUIT's design principles. However, I think that the explanations of the SUIT conventions are pretty good, so after learning the SUIT conventions, there is nothing in the Design Principles document that feels very surprising or eye-opening.
Simon Smith
@simonsmith
Okay that's very good to know
Michael Wuergler
@radiovisual
I think one critique I have overall is that after being introduced to SUIT, I am left with more questions than answers, without a lot of online resources to help pad things out, so there is a need to really dive deep into the source (which is a sign of lacking documentation).
Simon Smith
@simonsmith
We get a lot of questions in issues (and I myself used to open a few) so I think covering off some concrete examples of how SUIT can help in real life situations and the problems it solves is useful
Michael Wuergler
@radiovisual
Once you dive in, you like what you find, but there is a big barrier to entry.
Simon Smith
@simonsmith
This is very good feedback. Thanks
Michael Wuergler
@radiovisual
I am happy to help in this regard. I will be using SUIT for all my future work, so as I can contribute, I am happy to help solve this problem.
Simon Smith
@simonsmith
Great. I'll be sure to tag you in any PRs for your opinion
Michael Wuergler
@radiovisual
Yes, please do, I was just going to invite you to do that.
Simon Smith
@simonsmith
How are you using SUIT? With React, <insert another framework> or plain HTML?
Michael Wuergler
@radiovisual
Right now via Gulp > HTML. Next in line will be with Webpack > React
Simon Smith
@simonsmith
Okay cool
Michael Wuergler
@radiovisual
At first it was just straight HTML, trying to wrap my mind around it all.
is there a suitcss-approved webpack starter in existence? Or does everyone just roll their own?
Simon Smith
@simonsmith
Not really. The preprocessor is really just a collection of postcss plugins behind a CLI. So the first stop would be using the postcss-loader for webpack and adding the plugins you need
This is defintley something for the docs, but for now there is nothing official
That is a very specific version as it doesn't include all the postcss plugins, but you can certainly install all the ones you need
Michael Wuergler
@radiovisual
ok, thanks. that is useful. i was looking around and couldnt find any webpack examples, so that would be nice to see in the documentation. and the "how to wire the tooling up in webpack" was one question I got recently from a developer who had never heard of SUIT, so I looked for some good examples, or some starters, to no avail.
Simon Smith
@simonsmith
Are you familiar with postcss itself?
Michael Wuergler
@radiovisual
yes, sortof. I have used it here and there, but it has been my deep-dive into SUIT that keeps leading me back to postcss.
Simon Smith
@simonsmith
Okay well, do feel free to continue asking questions here or in issues
Michael Wuergler
@radiovisual
awesome. thanks very much!
jtyler-dev
@jtyler-dev
Hi, I hope this room is still somewhat active. I've spent the better part of the night trying to figure out how to integrate suitcss with webpack and was wondering if any has solved this? I am just starting to learn suitcss so sorry if this is a super basic thing
Simon Smith
@simonsmith
Hi @jtyler-dev, we're yet to have an official webpack loader (soon)
Until then you may find use in this issue - suitcss/preprocessor#77
jtyler-dev
@jtyler-dev
Are those the only packages I need to get suit working with postcss? are do I have to include all the ones mentioned in the docs for preprocessor?
Simon Smith
@simonsmith
If you do it yourself then just need to add the ones you need
Not everyone uses postcss-apply for example
In the future the proper webpack loader will wrap the preprocessor
jtyler-dev
@jtyler-dev
is there a recommended set? sorry im brand new to suit and still getting my bearings
Simon Smith
@simonsmith
If you want to play it safe then install the same ones the preprocessor uses
jtyler-dev
@jtyler-dev
Does anyone have a working example of suitcss being compiled by webpack via postcss? I have it to a point where it can compile a file, but the styles are close but not correct
Simon Smith
@simonsmith
Tim Kelty
@timkelty
@simonsmith @giuseppeg ya’ll around sometime this week to discuss next major version?
Giuseppe
@giuseppeg
@timkelty sure whenever you want in the following days, are you based in the US?
Tim Kelty
@timkelty
@giuseppeg yeah - EST
Maybe I'll just start a discussion in a GH issue and if we need to chat following we can
Giuseppe
@giuseppeg
sounds good