{"componentChunkName":"component---src-templates-post-js","path":"/blog/css-grid","result":{"data":{"markdownRemark":{"frontmatter":{"date":"05 de setembro de 2019","title":"CSS Grid","description":"The right way to build layouts on web"},"html":"

Intro

\n

For the first time (since 2017) CSS Grid is available directly in the browser! This means that any way to create layout structures will be disabled by a native system that is cleaner at the time of writing your HTML and CSS, consequently more semantic and considerably easier to learn.

\n

Classic way

\n

Until then, all that existed about browser layout was just an \"imitation\" of the true functionality of a grid. A widely used template is from the famous Bootstrap framework: <div> with classes: 'row', 'col-some-size', 'col-some-smaller-size', several and many tags defined in HTML and with classes that tend to grow even more according to the complexity of your project.

\n
<div class=\"navbar navbar-dark bg-dark shadow-sm\">\n  <div class=\"container d-flex justify-content-between\">\n    <a href=\"#\" class=\"navbar-brand d-flex align-items-center\">\n      <strong>Title</strong>\n    </a>\n    <button class=\"navbar-toggler\" type=\"button\" data-toggle=\"collapse\" data-target=\"#navbarHeader\" aria-controls=\"navbarHeader\" aria-expanded=\"false\" aria-label=\"Toggle navigation\">\n      <span class=\"navbar-toggler-icon\"></span>\n    </button>\n  </div>\n</div>
\n

The point is that this \"traditional\" model has worked very well and you will not be reinventing the wheel by choosing to use CSS Grid in layout construction, on the contrary, with CSS Grid you make your markup simpler and semantically correct (as I said before) and without dirt and divs and more divs defining rows and columns.

\n

CSS Grid Layout

\n

With a few lines of HTML and CSS we set up a responsive grid easily:

\n\n

Which replaces much larger files compared to the Bootstrap grid for example.

\n
\n

The more I use CSS Grid, the more convinced I am that there is no benefit to be had by adding a layer of abstraction over it. CSS Grid is the layout framework. Baked right into the browser.

\n

— Jen Simmons

\n
\n

CSS Grid ≠ Flexbox

\n

Yes, the two are different and each has its own purpose, but it does not replace the other, they complement each other!

\n

Flexbox

\n

Flexbox aims to organize items within a parent element. For example: I have a footer tag and need to place certain text in the center.

\n
footer {\n  display: flex;\n  justify-contents: center;\n  align-items: center;\n}
\n

That is, it is great for working with elements in a single dimension, whether row or column.

\n

You can also create two-dimensional flexbox layout, but that's not its purpose. CSS Grid works a lot better with this.

\n

CSS Grid

\n

With CSS Grid we define, for example, where this footer will be in the whole layout.

\n
#app {\n  display: grid;\n  grid-template-areas: \"header\" \"main\" \"footer\"\n}\n\nfooter {\n  grid-area: footer;\n}
\n

This is the best way to arrange elements in two dimensions, especially when you need to define the structure of a page.

\n

The best of both sides

\n

Using the same basic example to enjoy the best of both together:

\n
#app {\n  display: grid;\n  grid-template-areas: \"header\" \"main\" \"footer\"\n}\n  \nfooter {\n  display: flex;\n  align-items: center;\n  justify-content: center;\n  grid-area: footer;\n}
\n

Anyway, in this case we define the grid and the position of the footer with CSS Grid and centralize elements that are inside the footer. CSS Grid and flexbox are simple contexts but can confuse when and when to use both.

\n

Some links

\n

https://grid.layoutit.com/

\n

https://cssgrid-generator.netlify.com/

","timeToRead":3}},"pageContext":{"locale":"en","title":"CSS Grid"}},"staticQueryHashes":["1886018365","764694655"]}