Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I just started using css less and thinking about which way is better: include less file to page with less.js library or convert less into pure css and include that file to a page.
Which way do you use and think which way is better?
I would compile the less to css and implement the compiled file to my site. I think this is the usual way to do this.
There are a lot of tools for this task. Take a look at compass and/or scout.
Compiling process can also do with commmand line itself or Gruntjs.
All of these tool compiling the less files onthefly.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 months ago.
Improve this question
I started working on an app made with tsx. This app has a general stylesheet for everything and some of the components have inline styling. Personally it feels disorganized.
I'm a biginner at css so I don't know what would be the best way to aproach this. I thought of two options: do all inline styling or make a stylesheet for each component. The first feels wrong ,in the second I'm gonna end up with 30 stylesheets and the overrides are going to mess up everithing.
The styled-components library is universally popular and you'll find plenty of support from the large community that uses it. With this you can write your css inside your component files. I'd also recommend getting the VS-Code extension for it so that you get css intellisense.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I have just self taught SASS by studying the SASS documentation: http://sass-lang.com/documentation/file.SASS_REFERENCE.html. What practical work can I do now that can best demonstrate my SASS skill and experience to employers?
I am looking for a front-end or a web developer role around 70-80K. My current skill set is HTML5, CSS3, Bootstrap, JavaScript, jQuery, PHP, MySQL, WordPress, React, Angular, SVN and Photoshop. Thank you. :)
I think if you understand the basics listed in the Sass website you are pretty much ready to go :)
http://sass-lang.com/guide
To demonstrate your knowledge do some demos or websites using Sass and show the code to an employer.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am working on a new project which involves building a chat window. Normally, I would have no hesitation in using Flexbox for this project, however, a requirement of this project is that I support IE9.
I know that using tools like Modernizr can provide a fallback, but if I need to support this anyways is there much advantage of using this method?
No. Not worth it. You'll wind up doing everything twice to get the fallback support, so spend your effort doing it once, fully compatible with the oldest browser you need to support.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm learning SASS and now I'm only reading sometings about it. When I should use it in my projects?
Is there some tricks about it? For example,
If lines of CSS file(s) are more than X,
If small,medium,large project,
If there are more than X class, field, id etc.
Because now I'm using only CSS3 for my projects and it seems enough for me.
Because SASS compiles to CSS, it cannot style to any greater degree than will normal CSS.
The reason to use SASS is to structure your stylesheets. SASS allows you to use mixins, variables, and functions, which allow you to DRY (Don't repeat yourself) up your code.
In the beggining with precompilers like Sass I used only minimum of functionality like nesting, variables , imports , some mixins.
Preprocessors don't learn you to write better code, it only ease the structuring , organization and can help you DRY your code.
Allways check output when you starting with preprocessors because you can bloat your CSS if you are not careful enough.
I use Sass in all project big and small and my favourite functionality is importing.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
While moving on web I found normlize.css can be used to persist the css effect in various browser.
http://necolas.github.io/normalize.css/2.1.3/normalize.css
There are two approach to use it:
Approach 1: use normalize.css as a starting point for your own project’s base CSS, customising the values to match the design’s requirements.
Approach 2: include normalize.css untouched and build upon it, overriding the defaults later in your CSS if necessary.
I think 2nd is easy.
Does it mean including this css untouched and then working with our css in normal way, correct?