Imagine a thousands of real-world, ready-to-use, and themable components that you can copy & paste to your project. I believe that it will help boosting many projects that the founder want to prove their ideas to make this world a better place.
I would love to have anyone that believe that same thing as I believe. I am very excited about this project because I know that there is a lot of developers who are struggling at building ui and waiting for something like this to come true. I will take a lot of time for me alone to make it to thousand components. So if you want to do something great and fun, please read our contribution section
- Increase ui development productivity so that you can focus on other parts of your app.
- Make it dynamic for developers to customize (that's why we provide the code sandbox link for you).
- Help growing material-ui community because we love it.
- Open mui-treasury website (don't worry, it is not a spam)
- In the components panel, choose one that you like.
- Click search icon to copy theme and code sandbox for jsx => paste to your project.
Thank you for your interest in this project. let's do it.
Please keep your pull requests small. To give a PR the best chance of getting accepted, don't bundle more than one feature or bug fix per pull request. It's always best to create two smaller PRs than one big one.
- Please open new issue for every new component that you want to add, so that other people don't create the same component as your
- Title the issue with (New)-Category_Component. For Example,
(New)-Card_SimpleDashboardCard - Add image of the component that you want to product (if possible)
- Create branch name same as the issue title
- Follow component file guideline for consistency
- Please open new issue for every new component that you want to add, so that other people can see and help
- Title the issue with (Help)-Category_Component description. For Example,
(Help)-Card_SimpleDashboardCard Something is wrong! - Add image (if possible)
- Create branch name same as the issue title
- Follow component file guideline for consistency
All stable releases are tagged (view tags).
At any given time, develop represents the latest development version of the library. Patches or hotfix releases are prepared on an independent branch.
When develop is merged with new component or new page, it will be deployed to master with a tag of new release version
Only important bug fixes should be applied to master at this point. create hotfix branch from master if there is a critical bug.
Please create a new branch from an up to date master on your fork. (Note, urgent hotfixes should be branched off the latest stable release rather than master)
- Fork the Mui Treasury repository on Github
- Clone your fork to your local machine
git clone git@github.com:<yourname>/mui-treasury.git - Create a branch
git checkout -b my-topic-branch - Make your changes, lint, then push to to GitHub with
git push --set-upstream origin my-topic-branch. Visit GitHub and make your pull request. If you have an existing local repository, please update it before you start, to minimise the chance of merge conflicts.
git remote add upstream git@github.com:siriwatknp/mui-treasury.git
git checkout dev
git pull upstream dev
git checkout -b my-topic-branch
yarn
- copy everything in
src/contribution/PageTemplate.js - create new CategoryPage in
src/pages/components/and paste from (1) - rename the page
- add new page to
src/pages/components/.extensionRoutes.js - add new category folder to
src/components - copy everything in
src/contribution/ComponentTemplate.js - create new component in
src/components/<category>/and paste from (6) yarn startand check your component in the page
Follow step 6 from the above
This project is licensed under the terms of the MIT license.