These are simply customized versions of Bootstrap 4.1. They're meant to spice up your Bootstrap project by modifying the colors and looks of the existing components and typography.
Given the icon I expected it to do something with color. I don't know what given the context but the only time I have ever seen that icon is for color picking and usually not in a way that modifies my clipboard.
It's currently in beta. According to the developers there will be no more breaking changes, so that's something. It's also the default download version on getbootstrap.com now. For early adopters I think it's a good pick. If you need more stability, Bootstrap 3 will be maintained for some time as well.
Bootstrap 4 has some really good new features so I use it for my own projects.
That's not accurate on breaking changes, there will be additional ones in the future:
> We’ve done our best to prevent breaking changes, but we had to sneak some in. Regrettably, we’ll also have a few more coming in Beta 3, too. However, we’re clearly outlining all of them for you to make the upgrade and testing process as easy as possible.
What are those really good new features? How hard was it for you to transition from 3 to 4?
P.S. I'm really comfortable with B3 just not sure if I'm willing to invest the time and energy to learn 4 just yet.. Unless of course the new features are really that compelling :)
Not up to date with atom/electron but I kind of assumed that the whole point of building an editor in JavaScript was to be able to use it in some sort of browser context, for example on GitHub.
Why else would someone build an editor in JavaScript?
And, at the intersection of those two factors, the ability to easily make complicated editor plugins that Just Work without having to worry about the specifics of different OSes.
I don't think it's necessarily about using JavaScript as much as it is about using Chromium / Electron to easily create a consistent cross-platform experience.
It's not currently open source, but I will consider it in the future. Either in the state it is in or possibly some normalized scaffolding version to easily create a cheat sheet like this one.
In any case I would have to do some refactoring before feeling comfortable releasing the source code up for people to examine :-)
Well, don't over think it! I'm more just curious how something like this is done. I won't judge you over your source code! :P haha Thanks again, though, for putting this all together. It really is an awesome site/cheat sheet.
https://github.com/HackerThemes/theme-machine/blob/master/sc...
which is imported in the file that you linked. That's all in terms of SCSS. Then the gulp task runs the SCSS build and the autoprefixer.