Thank you for the kind word. Great question! In short we see little to no benefit for such a simple presentational feature. The card elements created via utility classes require nearly the same amount of boilerplate, zero imports, and allow for endless customization and adjustment through Tailwind utility classes. See the v2 docs covered here: www.skeleton.dev/elements/cards We take a similar approach for other key elements, such as form elements as well: www.skeleton.dev/elements/forms
Is this intended to be an introduction to Skeleton? I have watched this video for 8 minutes before pausing to write this comment. What does Skeleton do? Given this is an introduction video, I don’t know what Skeleton does or what problems it is supposed to solve. I hoped on clicking this video that this question was answered in the first 5 minutes (or less)! I’m merely a hobbyist dev coming across this video. Probably behind the times in the JS ecosystem, but interested anyway. I would like to know why I should consider using Skeleton in my project. I feel your passion in Skeleton. I believe you think it solves a problem. But what problem does it solve and how?
Hey @kompy386, sorry for the confusion. This video is revealing some of our plans for "Next" (aka Skeleton v3.0), our next major iteration of Skeleton. If you're looking for an introduction to the Skeleton as a whole, we have a video for this here: ua-cam.com/video/tHzVyChDuyo/v-deo.html I'd also highly encourage checking out our intro on our doc site, which does a great job of explaining what Skeleton is and does: www.skeleton.dev/docs/introduction FYI I've updated the title of this video as well to help avoid confusion for others going forward.
Appreciate the reply! Hoping I don’t come off as antagonistic - wanted to provide my perspective as someone outside the ecosystem. The link provided (intro docs) doesn’t give me any additional information on getting started or how to use Skeleton. I didn’t watch the video embedded on the page. Do I have to watch a video to see examples on using it?! After writing ^, I watched the video on the intro page (your second link). Halfway through the video I get a bit of useful info about starting to use Skeleton. Does not feel practical: I cannot use this to get started. Do I have to read the docs more? Spend a few hours evaluating if I even need this framework? Book a 1-1 session to understand intricate details? A slow-moving explanation of “here is how to integrate Skeleton in a simple example project” could be useful. Does this exist? After writing all of the above, I clicked your first link - then realized it is the same as the embedded video on your second link. Again - want to emphasize that I only want to provide my perspective as someone outside the ecosystem. To reiterate, I can feel your passion and I wish you all the best. Maybe I haven’t yet put in the requisite effort but I still don’t understand CLEARLY what the goals of this project are and, more importantly, how they can be applied
@@Kompy386 If the video linked, the doc site, and the handful of other videos linked on that page doesn't provide what you need, then I'd say the best elevator pitch for Skeleton is this: it's a combination of web-based frontend web UI elements built around TailwindCSS (tailwindcss.com/) paired with UI web components created using Svelte (svelte.dev/), with React (react.dev/) support coming soon. If you're not familiar with these technologies then Skeleton is probably going to come across a bit foreign. That said, if you're looking for a hands-on approach building a small app with Skeleton, then Huntabyte's video is pretty much exactly that. It was also linked on the page I shared: ua-cam.com/video/P_A0qQ7AuK8/v-deo.html
Great work team. Keep going. Also why no card component?
Thank you for the kind word. Great question! In short we see little to no benefit for such a simple presentational feature. The card elements created via utility classes require nearly the same amount of boilerplate, zero imports, and allow for endless customization and adjustment through Tailwind utility classes. See the v2 docs covered here:
www.skeleton.dev/elements/cards
We take a similar approach for other key elements, such as form elements as well:
www.skeleton.dev/elements/forms
Is this intended to be an introduction to Skeleton?
I have watched this video for 8 minutes before pausing to write this comment. What does Skeleton do? Given this is an introduction video, I don’t know what Skeleton does or what problems it is supposed to solve. I hoped on clicking this video that this question was answered in the first 5 minutes (or less)!
I’m merely a hobbyist dev coming across this video. Probably behind the times in the JS ecosystem, but interested anyway. I would like to know why I should consider using Skeleton in my project.
I feel your passion in Skeleton. I believe you think it solves a problem. But what problem does it solve and how?
Hey @kompy386, sorry for the confusion. This video is revealing some of our plans for "Next" (aka Skeleton v3.0), our next major iteration of Skeleton. If you're looking for an introduction to the Skeleton as a whole, we have a video for this here:
ua-cam.com/video/tHzVyChDuyo/v-deo.html
I'd also highly encourage checking out our intro on our doc site, which does a great job of explaining what Skeleton is and does:
www.skeleton.dev/docs/introduction
FYI I've updated the title of this video as well to help avoid confusion for others going forward.
Appreciate the reply! Hoping I don’t come off as antagonistic - wanted to provide my perspective as someone outside the ecosystem.
The link provided (intro docs) doesn’t give me any additional information on getting started or how to use Skeleton. I didn’t watch the video embedded on the page. Do I have to watch a video to see examples on using it?!
After writing ^, I watched the video on the intro page (your second link).
Halfway through the video I get a bit of useful info about starting to use Skeleton. Does not feel practical: I cannot use this to get started. Do I have to read the docs more? Spend a few hours evaluating if I even need this framework? Book a 1-1 session to understand intricate details?
A slow-moving explanation of “here is how to integrate Skeleton in a simple example project” could be useful. Does this exist?
After writing all of the above, I clicked your first link - then realized it is the same as the embedded video on your second link.
Again - want to emphasize that I only want to provide my perspective as someone outside the ecosystem. To reiterate, I can feel your passion and I wish you all the best. Maybe I haven’t yet put in the requisite effort but I still don’t understand CLEARLY what the goals of this project are and, more importantly, how they can be applied
@@Kompy386 If the video linked, the doc site, and the handful of other videos linked on that page doesn't provide what you need, then I'd say the best elevator pitch for Skeleton is this: it's a combination of web-based frontend web UI elements built around TailwindCSS (tailwindcss.com/) paired with UI web components created using Svelte (svelte.dev/), with React (react.dev/) support coming soon. If you're not familiar with these technologies then Skeleton is probably going to come across a bit foreign. That said, if you're looking for a hands-on approach building a small app with Skeleton, then Huntabyte's video is pretty much exactly that. It was also linked on the page I shared:
ua-cam.com/video/P_A0qQ7AuK8/v-deo.html
😡 *Promo SM*