Chalarangelo
commented
7 years ago Update
Due to a super secret project I want to work on, I am sort of rushing the update so that it can be available as soon as possible. So far, it's coming along nicely and it's about 60% done already. Most of the new features had been tested before starting work on the update itself, so many of the quirks have already been ironed out. In order to actually get the update out as soon as possible, some compromises might be made, mainly in terms of changing the page layout and documentation (some navigational updates might be postponed until next week), but the quality of the framework is the same as usual. Apart from that, the two custom flavors, Nord and Sucroa are not fully updated (due to the changes in certain components such as .alerts) and they will either be updated by their authors/maintainers in a later patch or I will get around to fixing them sometime in June. They are still perfectly fine and work great, it's just that some of the new features and changes will not hit them until the end of the month or so. Sorry about that.
Estimated release date
Originally, I was going for a release around the end of the month, but right now I am aiming to release the update either tomorrow or the day after. Don't take my word for it, though, just yet!
mistakenelf
Overview
The release of v2.2.0 will change a lot of things around and it will also bring about some breaking changes. A list of changes, along with their progress is shown below.
Upcoming changes
.drawer(name is not finalized) component innavigation, allowing for slide-in menus and responsive navigation.calc()). This feature will most likely be opt-in, meaning that old flavors will not be affected, as the feature will be turned off by default.input_controlshould come beforenavigationat least) to improve style cascading and gzip compression.paddingandmarginvalues, making sure that no oddities and artifacts exist and that everything works quite well with fluid typography.utilitymodule will be revisited to make sure theirpaddingandmarginvalues are useful and!importantdeclarations will be added to make sure they are applied (found a bug where they do not apply properly)..alertclasses of thecontextualmodule will be retired (I will either move them to their own component module as an extra or flag-disable them). A.toastclass will take their place, making it easier to show toast messages on mobile devices..urgentand.criticalalerts will be added as.cardclasses..inverse.cardclass will be removed, as it serves no practical purpose except to showcase the specific card mixin..nanoclass will be removed from theprogressmodule, as it serves no real purpose right now..closeicon class will be revisited and redesigned to utilize a textual::beforepseudo-element with simpler rules, making it more lightweight. Also, extra rules might be added to make it compatible with<label>elements and the new.drawercomponent..shadow-noneclass will be probably gone as well).Compatibility
v2.2.0 will introduce a few new components and remove some older ones, in order to improve functionality and de-bloat the framework somewhat. Refer to the above list of changes for more details.
Release date
Worst case scenario is that v2.2.0 will take until mid-June, but that is highly unlikely. The most likely scenario is that it will be available sometime towards the end of May. Stay tuned for more updates!