Skeleton Progress Update - April 2025 #3498
endigo9740
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey everyone, Chris here from Skeleton. Now that Skeleton v3 has been out for a while, we're going to be making a few changes to how we communicate information going forward. Our goal will be to aim for a least a monthly summary covering the most notable changes. This kicks off today, and we have a lot to cover, so let's dive right in!
Skeleton on "This Week in Svelte"
I'll soon be making an appearance on This Week in Svelte to talk with host Paolo Ricciuti about all things Skeleton. We'll follow up with specific date and time soon, but for now don't miss out on this week's episode featuring Q&A with Svelte creator Rich Harris!
New Toast Component
As promised during the v3.0 release, we are beginning to roll out new first-party components for Skeleton. This starts today with the introduction of the brand new Toast component for Svelte and React. Similar to other Skeleton components, this is based on Zag.s primitives, meaning a universal API and set of features. And as with most Skeleton components, it should be both easy to use and flexible to style.
Headless Component Integration Guides
We're also rolling out three brand new integration guides for open source headless component libraries. This includes, Bits UI and Melt UI for Svelte, and Radix UI for React. While we love the flexibility of Zag.js in our first-party components, we understand some users wish for more finite control, more power-user features, or to lean further on framework-specific conventions.
These primitives can not only serves as an alternative to our components, but also help augment and extend your toolkit. As such, each guide focuses on a specific components not currently available in Skeleton's component library.
Let's quickly review what each brings to the table.
Bits UI
https://www.skeleton.dev/docs/headless/bits-ui
Bits UI is the newest option provided today, created and maintained by Svelte YouTuber and community contributor Huntabyte. Hunter has provided a really solid headless framework containing highly composable components, top-notch documentation, with support for Svelte 5. Each component comes with pre-styled examples utilizing Tailwind primitives, making it trivial to integrate Skeleton. Just swap out a few classes.
Melt UI
https://www.skeleton.dev/docs/headless/melt-ui
Melt UI has been a mainstay in the Svelte community for a while now, created by Svelte Ambassador Thomas G. Lopes. A new Svelte 5 version is on the way that continues to refine the powerful Builder concept. Note that this is still in development, so you may see a few gaps in the documentation. However, we hope this provides a great excuse to kick the tires and preview what's coming leading up to the Melt UI v1 release!
Radix UI
https://www.skeleton.dev/docs/headless/radix-ui
Last but not least we also have support for Radix UI, provided by WorkOS as part of their extensive design system ecosystem - which also includes themes, icons, and colors. Radix has garnered a lot of extra attention lately due to its inclusion in the hugely popular Shadcn component library.
Docs and Example Improvements
Additionally, we've recently rolled out a number of documentation and example improvements. These cover a lot of last minute gaps we couldn't address before launch, while also helping improve how you consume and learn about Skeleton. Expect more improvements like this going forward as well.
New Release Process
As many of you may know, Skeleton has maintained a rigorous release schedule, dropping new updates every 2 weeks. Barring a few exceptions such as holidays, we've maintained this for nearly three years now. However, with the release of Skeleton v3, we've began to revise our internal workflows and will be moving to a continuous release strategy. This means you'll see much more frequent updates, including faster turn around for bugfixes!
As always, you can browse the latest releases here:
What's Next for Skeleton
Survey Results
Per our last update, we included a community survey with a number of questions regarding the future of Skeleton. We appreciate everyone that participated. If you're curious, you can view the results here. The team and I have been analyzing these results internally, and many of the updates you see today and going forward will be based around your feedback - including prioritizing new components and new integration guides.
Internal Roadmap
Additionally, the team and I had our annual group meeting where we discussed the future of Skeleton. We're not quite ready to pull back the curtains on everything, but wanted to at least provide a high level overview of what you may expect. As with most roadmaps, everything here is a proposal and subject to change:
As always, we'll continue to update you on these initiatives as things develop.
Alpha and Beta Features
To help provide a safety net for new features introduced in our production branch, you may see features tagged with
[Alpha]or[Beta]next to their name, starting with the new Toast component. This gives you an indication of the overall status of the feature. Our hope is to get new features into your hands quicker, so you can provide feedback right away. Just be wary of using these features in production until the tag is removed. At which point the component will be considered stable.Skeleton v4 (Next) and Component RFC
Finally, as we begin progress on the next major version of Skeleton, you may notice a pattern - we're aiming for major updates to be more frequent but smaller in scope going forward. The goal being to provide a more simpler path forward for migration rather than the huge jump from v2 to v3.
The first major release will likely revolve around some new component API changes we're proposing today. As such, we've created an RFC to allow you to review the changes and provide your feedback. Feedback from the community is critical to ensure we're staying on track and providing the best library we can for you, so please consider reviewing and leaving feedback as soon as possible!
Beta Was this translation helpful? Give feedback.
All reactions