The use of grid classes tends to bring about the placement of numerous non-semantic class names all through a document, such as a “row” or “column”. Let’s say you wanted a different number of columns, well, that won’t be possible. The design becomes restricted to working only those widths.Īlready calculated grid classes normally uses 12 or 16 columns. Grids are already calculated, they tend to have set widths that are difficult to change, e.g. Grid classes could be anywhere from 200 to 700 lines of code, but even in a simple design, most of the codes may never be used. Some of the downsides of using CSS Grids include: But as a tool you will be using consistently in your codes, you should be able to know the pros and cons, to determine if it is right for a specific project. You should not think that using the CSS grid is bad because it isn’t. Using CSS grid systems to create layouts on a website can be really easy, and of course, there are many values you can get from using CSS grid systems, but there are also downsides to using the CSS grid system. Nesting And Increasing Layout ComplexityĪ grid system is usually made up of a specific number of columns, normally 12 or 16 columns, and the ability to set an element, like the div or class element, to a width of X columns. Fortunately for us, the answer is “Yes!’, all thanks to CSS preprocessors such as LESS and SASS/SCSS that can work with CSS variables, and perform calculations and output CSS via ‘mixins’. But the question is “can the generation of layouts be made easier and faster, and still overcome these problems?”. The main reason designers and web developers use CSS grid systems is to make the generation of layouts easier and faster. Using CSS grid to generate layouts in a design provides developers with value, and makes things a lot easier for developers, but there are still some problems or downsides of using the CSS grid systems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |