-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Baklava #63
Comments
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
1 year later, we released our first stable version. Let's move forward with new tasks! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is an epic issue for tracking the roadmap to the first stable version of Baklava (previously named as Grace).
Motivation
After using Grace as one of the UI libraries inside Trendyol, now we decided having some major changes in next version because of some new requirements:
Design System
Project evolved from a UI library to a Design System to cover more generic use-cases then some specific areas inside Trendyol.
Multi-platform
Grace V2 will be a "web component" library written with Lit. The main motivation behind this decision is that we (in Trendyol) want to use the same UI library and design guidelines in both Vue and React projects.
More open
We want to maintain Grace project with regular open-source principles, fully managed in GitHub. So contribution guidelines, documentation, release pipelines will be more transparent and clear.
Accessibility in mind
One of the main purposes of Baklava Design System is to provide fully accessible UI elements. This will help to improve A11y all of our projects in Trendyol without repeating work.
Heavily automated
We'll focus on automating releases, tests, documentation generation, PR workflows, and so on, so we'll allow getting more contributions without blocking anyone because of a lack of human resources.
Plan
We are using
next
branch for the development of version 2. We'll fully re-write components with a refreshed design in this branch, then we'll release the first stable release of V2. On the road, we'll be able to start using alpha/beta releases.After creating core parts of the new version, we'll expect contributions to finish implementing all of the needed components in the new version.
We'll publish the library to CDN(s) as well as the NPM registry. We plan to promote consuming Grace V2 via CDN since this will give so much benefit for our users to cache the library on the browser.
Tasks
Here is the list of tasks that needs to be done for having the first stable release of V2.
You are very welcome to be part of this initiative. You can pick some tasks from the list and create a PR request by starting and targeting
next
branch. Please don't miss to check our new Contribution Guideline.The text was updated successfully, but these errors were encountered: