-
Notifications
You must be signed in to change notification settings - Fork 4
Upgrade to Bootstrap v4 #4
Comments
I have not decided whether I'm going to support Bootstrap 4, but if I will, I won't start before it's stable (or at least beta) |
I have a suggestion: Is it possible to turn this into a fork of bootstrap and use their source files, and add our styles to them so we aren't duplicating classes? |
As I've said elsewhere, v4 will be very different from v3, since my interests have shifted. I will recreate it from scratch, with some huge differences.
Classes are overwritten, not duplicated. Also, as of the current Bootstrap 4 alpha, customization has become even easier. |
I updated bootstrap-theme, bootswatch and material design themes to bootstrap 4. The biggest change is that oficial bootstrap 4 does not provide `bootstrap-theme` as separate stylesheet rather we have to enable two properties in sass source and compile it. I added shell script that automates this process, similarly to scripts in other themes. Remaining themes are in different state of migration: * M8tro - No sign of upgrade to 4 (idleberg/m8tro-bootstrap#4) * Vegibit - No sign of upgrade to 4 * Google - Upgrade in progress (todc/todc-bootstrap#172) What do you think is the best approach here? Can we just delete them? Or should we wait until todc releases new version of Google theme before we merge this to upstream branch?
It would be cool to start making a new version that is based on Bootstrap 4.0.0 since it's in Alpha stage right now, so your release of m8tro-bootstrap can be released as soon as it is released.
The text was updated successfully, but these errors were encountered: