Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Aurelian Spodarec
10,801 PointsCompass Project
How does a clean, compass project looks like, with methologies like SMACSS, etc.. ?
And do you use compass every time when you use Sass? Because I don't see any reason why someone woudn't ever use compass.
Should I now use compass on every single project when doing Sass? If no, why not?
2 Answers
Jennifer Nordell
Treehouse TeacherHi Aurelian! Based upon other questions you've put forth to the Community I'm assuming that what you are looking for is a way to get a job. Programming languages, Frameworks, CSS pre-processor choices change and develop rapidly. And they do so at such a rate, that anything you learn can be outdated by the time you manage to produce a project and show it off to a potential employer.
This is my own personal opinion, but I feel like the bulk of your energy should be producing a portfolio that shows off your current skill set as is so that you can immediately begin to display it to others. I'd worry less about naming conventions being "perfect" and more about the overall look and feel of your projects. Unless you're looking at a specific employer who says they want experience in a specific language/framework, your best bet is to make your skills more general and solid. Making your skill set very narrow and specific is a great way to exclude yourself from amazing opportunities. Most employers want someone who is flexible and can adapt as needed.
I would say focus less and expand more. But that's just me
miikis
44,957 PointsHi Aurelian,
The choice of what framework to use — or whether to use a framework at all — is really one that you have to make for yourself as a function of the particular constraints of the project that you are working on. Outside of that context, it's non-sensical to debate the issue. Personally, I don't ever use Compass in my projects because I find it to cumbersome to use. I do use ThoughtBot's Bourbon pretty regularly though. I also use Neat for layout pretty often.
Aurelian Spodarec
10,801 PointsHi,
I totally agree with you, but let's be real, everyone these days use some kind of CSS pre-processor, so we can safelly say it's a must in every project (ok, maybe not in some super small project for my grandmother).
But, http://bourbon.io/ is like Compass, just different, so in reality you are using Sass, like we all, and you have an option of Compass or Bourbon. So it concludes to the same thing.
So what I understand COmpass or http://bourbon.io/ is a must known tool for front-end developers.
Am I right? Then after this I can go and learn some back-end : d
miikis
44,957 PointsI am being real. You're conflating the idea of a CSS pre-processor with the concept of a Sass Framework; they're completely different. The former is a language (i.e., Sass, Less etc.) and the latter is a tool to use in congruence with a language. So, yes, I am using Sass ... but I never said I wasn't.
Also, no, you misunderstood me; there is no "must-know" tool for front-end developers as far as Sass frameworks go. At the end of the day, you just need to get your work done — with a reasonable level of quality, in a reasonable amount of time — and whatever aids you towards that goal is what you'll need to know how to use.
And don't underestimate the world of back-end development. Although, the lines of the dichotomy are getting increasingly blurrier, the world of back-end development is just as involved — arguably more involved — than the front-end.
Aurelian Spodarec
10,801 PointsMen, I'm just all over the place. But thank you for this too.
I go go and focus on the bigger picture for now, like Jennifer said. Then I can worry about the details xd
Aurelian Spodarec
10,801 PointsAurelian Spodarec
10,801 PointsPerfect answer. Really. Meh xd agrr xd
First focus on the big picture, then go in the details, right.
Thank you! This is the best answer on what I had in mind, and you just looked inside it!
Now I can begin my first steps!
Day #1 lol
Really like this answer, thank you :)