Skeleton Roadmap to v1.0

[endigo9740]

Tip

See our latest plans here:

• Skeleton v3 (Next) - Proposal, RFC, and Updates #2375

---

The Skeleton core team recently met and gathered our ideas for what Skeleton v1.0 might look like. This document represents the key items for that goal. Please note that priority is not set in stone, things may change, but generally speaking the most critical items are listed towards the top. If it's not immediately clear, our focus is on quality and stability over quantity of features.

Have we missed something? Curious to learn more about an item listed here? Let us know in the comments below!

NOTE: checked = released

v1.0 Roadmap

• Refactors to Major Features:
  • Refactor and improve the Dialog utility #197
  • Refactor and improve the Toast utility #198
  • Data Table refactor and cleanup #217
• Onboarding & Docs
  • Onboarding documentation updates #512
  • Skeleton CLI #552
• i18n - remove hardcoded text within components #465
• Update Drawers to include their own store #528
• Design
  • Accessibility (a11y) improvements for visual disabilities and color contrast #151
  • Implement @tailwind directives for stylesheets #467
  • Improve the Design Token system #553
  • Theme System Overhaul #598
  • Implement icon library into doc site #493
• Improve events and documentation #389
• Recommended components (we'll use these in the Docs)
  • New Component: Color Picker #376 → needed for the theme generator
  • New Component: Chips #375 → requested multiple times, useful for docs
  • New Component: Table of Contents #357 → used throughout the docs
• Plugin & Bundle Optimizations
  • Update Plugin to support Tailwind Intellisense #650
• SEO
  • Doc Site SEO + Open Graph #355
  • Replace Google Analytics #736
• Community & Support
  • Introduce the new Blog #551
  • Introduce a new Code of Conduct on Discord #780
  • Various Discord and Community Updates #781
• Polish & Refinement
  • Polish Pass: Tailwind Elements #837
  • Polish Pass: Components & Actions #857
  • Polish Pass: Utility Features #922
  • Documentation Updates #783

Post v1.0

Note the Skeleton core team will be meeting shortly after the v1.0 launch to regroup and evaluate and set expectations for upcoming releases. This will also define key goals leading up to the next major milestone release (v2.0)

• Begin promoting to news sources and influencers
• Improve automated test coverage and depth #150
• New Component: Autocomplete #377 → needed for doc search
• Implement Purge CSS #732

Proposals

• Improve project CI/CD
• Move to monorepo structure - if relevant
• Implement Changesets
• Framework agnostic proposal
• I18n support - RTL, data/time, numeric, plurals, etc (leave this to upstream?)
• Premium services - templates/support/etc
• Husky Hooks - to improve automation

[geoffkendall]

This looks excellent. One addition that would be great is to have more fully-functional menus, specifically to allow nesting (where specific menu items can themselves show sub-menus), and for menus to appear on hover rather than click. This will enable more desktop-like navigation of complex options. I don't think there's a way to do these things right now, but please correct me if I'm wrong! Thanks a lot,
Geoff

[endigo9740]

@geoffkendall, the proposals above are the "big stuff" to keep ourselves focused and organized. However, there's plenty of other small updates I anticipate we'll see over time. For example, your feature request for hover menus is open here:

• Enhanced menu: ability to show/hide menu based on mouseover (rather than click). #470

Just because it's not on the list above doesn't mean it's not something we'll get to sooner or later. Overall you might notice the goal is less "add a thousand features" and more "improve what we have". That way we can create a solid foundation to build off of, then new features can come in a much more rapid fashion.

If the basics aren't well established, then we'll end up with breaking changes over and over, which is the antithesis of stability. And stability is our north star when it comes to a full launch.

[geoffkendall]

Ah gotcha, thanks for the clarification! :-)

[524c]

I'm loving using Skeleton. This looks excellent!! 🤩🚀

[ghost]

Based on the docs, this project looks pretty interesting. May I ask if there are any planned breaking changes for this library? I want to be a beta tester, but I don't know how stable Skeleton is...

[endigo9740]

Hey @IRod22, the project is currently in "pre-release" status per the homepage on our website. We've been working on the project for a year, open source since August, with new releases dropping every two weeks. This upcoming Tuesday will be our next release and the first "release candidate". Meaning the library itself will be stable enough that we can finally recommend it for production use.

Our v1.0 release is scheduled to come shortly after that (no firm ETA yet), but is dependent on updates such as this one being completed:

• Documentation Updates #783

If you're interested in contributing, I'd recommend reading through the ticket above, other tickets under Issues, and perhaps joining our Discord and browsing the #contributor channel - this should get you caught up on where we are on things. If you think you can help with any ongoing tasks let us know. The first we'll need is folks helping read through and fix issues in the documentation.

Also see our contribution guidelines here:
https://www.skeleton.dev/docs/contributions