Vuestic 2.0 - No Shame Edition #3732
Description
This issue is about things that are over the top for vuestic 1. So think about whatever excites you and bring that to this issue.
Think about vuestic as an ecosystem, not as a vuestic-ui framework. You don't have to provide any details to the idea right now (whether it's breaking or not). You can also just mention existing issues. Let's go:
- Expose and document all composables. So that users can reuse logic without relying on component.
- Polished test coverage for all deliverables and docs. So that we can catch most of the bugs before they land to prod.
- Stories integrated into docs.
- Design integrated into stories.
- Make release script into separate library.
- Type tests/snapshots.
- Changelog system #3634
- Changelog autogeneration.
- Ability to align strictly with semver. So that we can avoid breaking changes.
- Tree-shaking below the level of component. So that user can have slimmer bundle.
- Development mode for docs. So that contributors can see things that are only relevant for them.
- Indicators for all automated checks.
- Indicators for financial metrics.
- Easy to undertand icons config.
- Make vuestic admin modular and allow the flow similar to
create vuestic. - Ability to use tailwind styles for components.
- Full featured data-table.
- Modular services. So that users can use colors, icons, config etc without pulling along full vuestic core.
- On demand environment.
- Camel case bem classes - to simplify renames
- Full featured calendar