search

manikrathee / feedback

Ask @manikrathee anything!
www.manikrathee.com
0 stars 0 forks source link

Question for Manik Rathee #1

Closed ghost closed 11 years ago

ghost commented 11 years ago

I see that you have a few repository's with your own setups of css frameworks like bootstrap and foundation and I was wondering if you think that people should use the CSS classes or use sass or less mixins so they can make there class names more semantically correct?

manikrathee commented 11 years ago

@gevvek I think it depends on the project. If you're working on something, maybe a side project or personal site, then I would suggest going the completely semantic route and use sass/less mixins to adjust styles.

However, for larger projects where multiple people will need to see/edit/understand your code, using classes is critical. The OOCSS methodology is best here. For example, if you're working on a web app, and an engineer noticed a little bug where a button needed to be a larger size for a call-to-action, he/she shouldn't have to create a bug for something that simple. Instead he could add .button-large (by consulting the styleguide that the front-end engineer so lovingly created) and be done with it.

This isn't to say that large projects shouldn't have semantic classes - even class-based styles like what I mentioned above can be semantic.

ghost commented 11 years ago

Hi Manik,

Thanks a lot of your reply! It really helps to be able to ask pro's like yourself questions.

Thanks Gabriel On 23/05/2013, at 6:09 AM, Manik Rathee notifications@github.com wrote:

@gevvek I think it depends on the project. If you're working on something, maybe a side project or personal site, then I would suggest going the completely semantic route and use sass/less mixins to adjust styles.

However, for larger projects where multiple people will need to see/edit/understand your code, using classes is critical. The OOCSS methodology is best here. For example, if you're working on a web app, and an engineer noticed a little bug where a button needed to be a larger size for a call-to-action, he/she shouldn't have to create a bug for something that simple. Instead he could add .button-large (by consulting the styleguide that the front-end engineer so lovingly created) and be done with it.

This isn't to say that large projects shouldn't have semantic classes - even class-based styles like what I mentioned above can be semantic.

— Reply to this email directly or view it on GitHub.

manikrathee commented 11 years ago

I definitely wouldn't call myself a pro but I'm happy to help

On Thu, May 23, 2013 at 2:09 AM, Gabriel Eden notifications@github.com wrote:

Hi Manik, Thanks a lot of your reply! It really helps to be able to ask pro's like yourself questions. Thanks Gabriel On 23/05/2013, at 6:09 AM, Manik Rathee notifications@github.com wrote:

@gevvek I think it depends on the project. If you're working on something, maybe a side project or personal site, then I would suggest going the completely semantic route and use sass/less mixins to adjust styles.

However, for larger projects where multiple people will need to see/edit/understand your code, using classes is critical. The OOCSS methodology is best here. For example, if you're working on a web app, and an engineer noticed a little bug where a button needed to be a larger size for a call-to-action, he/she shouldn't have to create a bug for something that simple. Instead he could add .button-large (by consulting the styleguide that the front-end engineer so lovingly created) and be done with it.

This isn't to say that large projects shouldn't have semantic classes - even class-based styles like what I mentioned above can be semantic.

— Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub: https://github.com/manikrathee/feedback/issues/1#issuecomment-18331743