Today marks a big milestone for the developer suite as we happily introduce the Beta version! 🎉
Beta Cometh
As of today we are feature complete for all of our packages! This means that from this point forward, we are focusing on delivering a stable "rc" release. In order to do this we need YOU, the early adopter, to test out migration and help us reveal the areas we can improve our packages. ⚡
Design Tokens
Thanks to Dan Davidson, we have an improvement for the Normalize.css file to support setting the background-color to help ease migration from Classic.
Interested in learning more about Migration? Check out the NEW Migration docs.
Mobile support
Thanks to Cassidy Swallow, we have full Android/Kotlin support for our Design Tokens! This is the first time in Pluralsight history that a design system has supported both mobile and web teams and it only gets better from here!
We also support iOS/Swift teams, but need some help verifying if there needs to be more work done. If you are a iOS developer, please check out this issue.
Headless Styles
A massive update in this package delivers all the style helpers for the components available to designers in the new Web UI Kit. Everything from Grid helpers to Tabs, Headless styles is now Web Kit complete!
Classic is not a 1:1 comparison to our current system. When Classic was created, Pluralsight was a single product brand. Now that we are multi-product, the new UI Kit acts as the "core" library allowing teams across all products to own their own custom solutions where needed.
New Style Objects
Most people wonder why we don't offer a Component library for our new system. The reason is quite simple: in a world full of Component libraries, we don't need another one. Let's face it, the reality is that for the people who use them, there are plenty of loyalists out there.
This is where Headless Styles shines. Instead of forcing another component library, we have built a system that allows people to easily extend the libraries they already love. 🎉
In Beta, we introduce a new export path that allows you to extend your library of choice even more easily! This means that your team can keep using the tech stack you already love and utilize the power of Headless Styles to customize the themes at your convenience!
Special thanks to Josh Degraw for testing out Headless Styles migration with v5 of MUI and helping us improve our library. ❤️
Interested in learning more about customizing 3rd party component libraries with Headless Styles? Check out the NEW Customization Docs.
React Utils
Beta introduces a ton of new hooks for people who are React users. Everything from Preloading Images to Autoformatting Dates, we have it covered!
Check out the latest hooks in the React Utils docs.
What's Next?
From this point until v1 it's all about the stabilizing and we need your help!
In order for us to make sure our system is ready for mass integration, we need more early adopters to test out migrating in their apps. This is the only way we can fix or improve our library before we release the official v1.
Early Adopter Questions
If you are someone that would like to test our migration with your team, ask yourself these questions during your experience:
- Is this easy to use for how we need to use it? If the answer is "no" or anything similar to "not really", start a new discussion to help us become aware of your experience.
- Is there something that feels buggy? Submit a new issue so we can fix it!
We value all feedback and keep a pulse on all of the above and want to make sure v1 has all the features or bugfixes needed to ensure a satisfactory experience with everyone! 🎉
Thanks 🎉
Some features in this release wouldn't be possible without the contribution of the following people:
Upgrading
# npm
npm install @pluralsight/{headless-styles,react-utils}@latest
# Yarn Classic
yarn upgrade @pluralsight/{headless-styles,react-utils}@latest
# Yarn Berry
yarn up @pluralsight/{headless-styles,react-utils}@latest
Installing
If it is your first time using any of our packages, check out our Installation Guide or the Intro Page of whichever package you are interested in using.
As always, if you have any questions or ideas, please drop us a thread in our Discussions Page.