neroswim.blogg.se - Devdocs vs bootstrap

#Devdocs vs bootstrap series#

Often, things like display, margin or padding are defined at the component level on a component class. Using layout utility classes properly is trickier, and comes with some practice. Generally, grid layouts are defined as follows:įor more documentation on grids, refer to Bootstrap’s Grid System overview. When building a site, grid structure and layout modifiers should always rely on Bootstrap.

Margin and padding alterations (like mb-1 for adding some margin on the bottom of something).

Display property alterations (using classes like d-flex for flexbox).

Layout Constructsįor layout purposes, we use Bootstrap to do the following: Other components can be used at the author’s discretion if they fit the needs of a given site. The components listed in the following sections we would like to ALWAYS rely on. Otherwise, a component like Jumbotron would be created as a custom component, with markup and styles that served out needs exactly. We would only use the Jumbotron component if it fit our needs closely for a specific project. btn, and they do not rely on any particular markup (though button styles should generally be applied to elements)Ĭonversely, the “Jumbotron” component requires some specific markup structure and may be harder to naturally work into a specific design.

In pursuit of these goals, we only use the parts of Bootstrap that do not require javascript and that are not highly opinionated in terms of markup structure.įor example, the button styles in Bootstrap provide some great defaults and can be customized to match the theme of a site.īutton styles require only one class. Providing base styling for common components.Generally, we like to leverage Bootstrap to accomplish 2 major tasks: It will be beneficial to take a look through the Bootstrap Docs to get familiar with the framework.įocus on the following sections, as they are used the most often in our sites: Using Bootstrap does require knowing about Bootstrap. Because of the predictability in the code, sites can be mutually understood, allowing for better collaboration.We know that common classes will always produce the same output and don’t have to spend time learning one-off approaches unique to each site.We can assume a basic set of patterns and elements are available to us in every site we build.Using Bootstrap on multiple projects is beneficial for our development team in several ways. There are merits to other frameworks, Bootstrap is just the one we like best. Our choice to use Bootstrap is preferential. It is worth noting, this article focuses primarily on how we use Bootstrap in the context of building a “designed” or “brochure” siteĪs opposed to an application. In this article, we will discuss Bootstrap as our framework of choice and in what ways we lean on Bootstrap to style a site.

#Devdocs vs bootstrap series#

The purpose of this series will be to define some standardized best practices for how CSS is composed and organized in our projects. CSS Standards and Normalization Part 2: Framework | Josh Boland Purpose