Skeleton v3 (Next) - Proposal, RFC, and Updates #2375
Replies: 5 comments 9 replies
-
|
amazing. the design system is already awesome and has made life so much easier for me. excited to see all the other possibilities with runes, shallow routing, and the standalone theme generator is a big step as well. 👏 |
Beta Was this translation helpful? Give feedback.
-
Fyi, the Snippets link points to Runes |
Beta Was this translation helpful? Give feedback.
-
|
Fixed, thank you! |
Beta Was this translation helpful? Give feedback.
-
|
I have a slight concern that Skeleton will focus on working for all the frameworks and not be something I love that specifically works well with Svelte. With that said I love the product and the team that surrounds it so here are just a few things to think about. AgnosticSomething that we might want to consider moving forward is that to be truly framework agnostic we wouldn't want to rely as much on the framework's specific tools like including Runes directly into the codebase. We could instead take the approach like Ionic did with Stencil. If you want to go the route of creating framework specific components like Papanasi did with Mitosis this would be another route. This would allow us to tap into the work being done with the Figma plugin that Builder has created as well. Cross Platform Stateshould we consider anything around state? Chakra UI went through some pain from a state aspect and built Zag.js. There are other frameworks like Xoid |
Beta Was this translation helpful? Give feedback.
-
|
Great feedback Alex, I would like to think of this as more of embracing the best of each framework, rather than aiming for the lowest common denominator. That's why we're very intentionally introducing new frameworks very slowly over time. With only the addition of React coming in v3. To address a few concerns you have specifically:
Thank you for sharing the links to those other libraries though. We have definitely looked at several of those already, and will keep the others in mind going forward. Also I would very highly recommend reviewing our prototype. Which shows how we're implementing components between Svelte and React. The common conventions, and where things diverge: Note that I have plans to release another progress update for "Next" alongside the new release this upcoming Tuesday. That will cover two topics:
The latter provides a great breakdown of how we're aiming to keep standard conventions and paradigms between multiple frameworks. I'm very pleased with where this currently stands. But as always feedback is welcome! |
Beta Was this translation helpful? Give feedback.
-
|
@codercatdev those updates I mentioned above are now available here: |
Beta Was this translation helpful? Give feedback.
-
|
My one nitpick that I've got with skeleton is the system for things like toasts and drawers. I personally do not like having to use a singular thing for drawers, and would appreciate if we could revisit how those are setup. |
Beta Was this translation helpful? Give feedback.
-
|
I personally do not like having to use a store to show a drawer, especially since I use them fairly heavily in my application. In the current setup I'd have to have huge if/else blocks. Some of the drawers are very specific in what they do, and it makes more sense for those to be their own thing that are controlled outside of the current singular store. That, by far, has been my biggest issue with Skeleton so far. I created a drawer component myself by |
Beta Was this translation helpful? Give feedback.
-
|
So if the Drawers work like Modals where you can either pass in a component reference or pre-register specific views with specific components, it would work for your usecase? |
Beta Was this translation helpful? Give feedback.
-
|
I'm not huge on the way the modals currently work. I would really rather just be able to <script>
import { Drawer } from '@skeleton/pkg';
let open = false;
</script>
<button on:click={() => open = true }>Open</button>
<Drawer {open}>
<!-- W/E here -->
</Drawer>And personally, the same for Modals as well. It's nice that the modal store can at least accept a component to render instead but I'd really rather not have to use the store setup at all. |
Beta Was this translation helpful? Give feedback.
-
|
I think with Svelte 5 this would be doable - the drawer component would save its |
Beta Was this translation helpful? Give feedback.
-
|
It's still too early to give a definitive answer to how we're going to handle modals/drawers/toasts in Skeleton v3, but we have been noting LOTS of ideas here: I'd encourage any additional feedback to directed to these threads. Likewise if you wish to check any other v3 milestone features, you can do so here: |
Beta Was this translation helpful? Give feedback.
-
|
Just sharing in case you missed it everyone - but the new Skeleton v3 pre-release is now available! |
Beta Was this translation helpful? Give feedback.
-
Hey everyone, Chris here from the Skeleton crew. To help celebrate the new year, the team and I wanted to take a moment of your time to share some exciting details about the next major version of Skeleton.
In short, we’ve decided that version 3.x of Skeleton will represent a much larger step forward than any previous release to date. In fact, over the last few months, the team and I have internally dubbed this “Skeleton Next” - as in the “next major version of Skeleton”. In order to help convey the scope and scale of these changes, we’ve shared a detailed proposal below covering the scope of changes:
Progress Updates
As we march forward I will plan to update this section periodically with the latest changes.
View our YouTube playlist of progress updates or review our written updates below.
Video Walkthrough
Summary of Changes
Again, we strongly recommend you read the proposal to understand the extent of the updates. However, let's review some of the most exciting changes:
FAQ
{insert feature}coming in Skeleton v3?v3branch of Skeleton. Expect periodic updates as we hit certain milestones and features and documentation are flushed out.{some other framework}. When can I start?Where can I submit comments?
The whole purpose of an RFC is to gather comments from folks like you, our wonderful community. We encourage you to review our proposal and FAQ in full. Then please leave your feedback in one of the two following locations:
#skeleton-nextchannel on Skeleton's Discord.Let's keep it constructive
Please note that Skeleton does provide and enforce a Code of Conduct. We take this very seriously. While we understand that major changes and be disruptive and frustrating for some users, we please ask you to keep discourse civil and constructive. Any users being rude or abrasive towards our team or other members of the community will be subject to moderation. That said, we're very excited about the possibilities this unlocks, and really want to hear what you think. Please do share!
Beta Was this translation helpful? Give feedback.
All reactions