On Thursday 18th of August, at 2:00pm PDT, we’ll be really lucky to have Miriam Suzanne (@mirisuzanne) join us for our next Q&A!
Miriam is the Co-Founder of OddBird, the team behind Susy and other great (and useful) toolkits! Miriam is also one of the amazing co-authors behind our book Jump Start Sass.
By participating in this Q&A, you’ll:
Understand how to customize Susy for your project (even with flexbox).
Learn about other ways to do layout, and why you might not need a toolkit to help.
Get advice on selecting a toolkit, or build your own!
It’s clear to see that Miriam knows a lot about Sass, Susy, and building web toolkits — so start posting your questions for her now!
If you’re unsure of when this is happening in your timezone, check out this handy link. If you realise you can’t make the event, no need to fret, get ahead of the crowd and leave your questions below. We’ll get around to them during the event.
Hi @rogeclash,
This is a chat session, which means there is no video. You can come back and join the live chat, or feel free to leave your questions for Miriam now, which she’ll get to once the event is happening.
When you are planning a new project, what are your recommended first steps in determining what framework(s), library(ies), toolkit(s), etc you will be needing for your layouts and styling?
How do I know that Susy is worth learning and working with? What are the advantages of using Compass or disadvantages of using something else?
How long does it take to learn it well?
And maybe this is kind of obvious but I know zero about Susy… So I’ll ask anyway.
What’s the reason to create Susy? What makes it different? Aren’t there too many tools on the web? How will you get people to make it “a-must-use” in their toolkit where there are so many tools out there to try and learn?
Sorry for the lack of originality in my questions.
Today we are thrilled to have Miriam Suzanne! She is a designer, developer, author, conference speaker and co-founder of OddBird. A team that builds many useful toolkits for web developers, like the Susy framework.
I love building toolkits, and I’m excited to talk about how we think about the tools we build, and the tools we decide to use from one project to the next.
Good question! I built Susy in 2009, and it looks like the first commit on Neat was published in 2012 - so you’ll have to ask them about that. When Neat came out, it was nearly identical to Susy, and they still provide mostly the same features. Singularity is another great, similar toolkit that came out of a Susy feature request. They’re all great, mostly the same, with some slight variations. You should use (or not use) the one that feels most comfortable to you. Now let’s talk about why you would or wouldn’t…
