<p dir="auto">I really like the new callouts in the docs, but ask myself why they are reserved for the docs?<br>
They look way better than the default alerts, imo they can be replaced by callouts.</p>
<h3 dir="auto">What about modularity in bootstrap 4?</h3>
<p dir="auto">I mean separation bootstrap into modules, for example: bootstrap-buttons, bootstrap-navbar, bootstrap-grid etc</p>
<h4 dir="auto">Motivation</h4>
<p dir="auto">I have worked on some not big projects which needed customized subset of bootstrap: grid, bottons, icons.</p>
<p dir="auto">I solved this problem in different ways:</p>
<ol dir="auto">
<li>Downloading "compiled" bootstrap (css, one js file) and customizing by my scripts - very hacky =(</li>
<li>Building custom bootstrap (by customizing variables). It requires to keep own fork of bootstrap or integrate build stage of bootstrap into build stage of project. It did not solve the problem that custom bootstrap had unnecessary modules.</li>
<li>Building necessary part of bootstrap in build stage of project (only necessary less and js files). I faced with errors when mixins was moved to subdirectory.</li>
</ol>
<p dir="auto">I think that separation bootstrap into modules will make easier the creation of custom builds without unnecessary parts and without unnecessary hacks.</p>
<p dir="auto">Bootstrap itself can depend on all its "modules" (bower have "devDependencies" feeld) and I think that bootstrap should have compiled (css, one js) version of all its modules in "dist" folder. It allows to prototype something without build tool.</p>