Skip to content

Commit ac78312

Browse files
[docs] Start to update the roadmap, remove legacy content
1 parent d7a49a0 commit ac78312

File tree

1 file changed

+57
-55
lines changed

1 file changed

+57
-55
lines changed

docs/src/pages/discover-more/roadmap/roadmap.md

Lines changed: 57 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -4,20 +4,19 @@
44

55
## Methodology
66

7-
Material-UI is community driven – issues that resonate most with the community get the most attention.
7+
Material-UI is community-driven – issues that resonate most with the community get the most attention.
88
Please **upvote** (👍) on GitHub the issues you are most interested in.
9-
Thank you for participating [in the developer survey](https://material-ui.com/blog/2019-developer-survey-results/).
9+
Thank you for participating [in the developer survey](https://material-ui.com/blog/2020-developer-survey-results/).
1010

1111
## Priorities
1212

1313
Here are the top priorities:
1414

1515
- 1.0 - **More components**. 🧰 This is challenging to address, as developing a fully-fledged component takes a considerable amount of time.
16-
We are going to try the following strategy:
17-
- Identify frequently needed components. There are many resources we can leverage for this: the developer survey answers, GitHub issue upvotes, Algolia search volume, Google search volume, documentation usage, npm downloads, etc.
16+
We apply the following strategy:
17+
- Identify frequently needed components. There are many resources we leverage for this: the developer survey answers, GitHub issue upvotes, Algolia search volume, Google search volume, documentation usage, npm downloads, etc.
1818
- Prioritize the creation of frequently needed components.
1919
- Encourage the usage of third-party components if they already exist and are well maintained.
20-
- Offer an option to the highly used and well maintained components to move to the official organization: mui-org/x on GitHub, @material-ui/x on npm and x.material-ui.com for the documentation.
2120
- 0.5 - **Better customization.** 💅 We want to make our component customization intuitive, no matter if you are using global CSS or styled-components:
2221
- Use styled-components by default: [#6115](https://github.com/mui-org/material-ui/issues/6115).
2322
- Allow the use of the Box props in all the core components: [#15561](https://github.com/mui-org/material-ui/issues/15561).
@@ -29,12 +28,7 @@ Here are the top priorities:
2928
- Page documentation rating 🥇🥈🥉. We will integrate a rating module in all our documentation pages. This way, we can collect high-quality data points and prioritize the pages that need the most to be improved.
3029
- Templates. They get people started really quickly, we need more of them!
3130
- Beginner tutorials & Video lessons.
32-
- 0.3 - **TypeScript.** 📏 There are two dimensions to this problem:
33-
- The documentation. We want to provide a TypeScript variant of most of our demos.
34-
You can help us out in [#14897](https://github.com/mui-org/material-ui/issues/14897), we have already covered +90% of them.
35-
- The definitions. We are **continuously** improving them. For instance, we are working on moving the props descriptions to TypeScript, so you can access them directly from your IDE.
36-
The codebase is written in JavaScript, we don't plan on migrating it to TypeScript in the near future. Upvote [#15984](https://github.com/mui-org/material-ui/issues/15984) if you want us to rewrite the core in a future version.
37-
- 0.3 - **Performance.** 🚀 React abstraction has a cost. The more components you render, the slower your page will be. You will notice stark differences when rendering a large table or list.
31+
- 0.2 - **Performance.** 🚀 React abstraction has a cost. The more components you render, the slower your page will be. You will notice stark differences when rendering a large table or list.
3832
Performance is all about doing less work. We can leverage the following:
3933
- Make the core faster.
4034
- Avoid re-rendering. It's the responsibility of the user to prune the React rendering tree efficiently,
@@ -44,57 +38,65 @@ Here are the top priorities:
4438
- 0.2 - **Bundle size.** 📦 You can keep track of our progress [following bundlephobia.com report](https://bundlephobia.com/result?p=@material-ui/core).
4539
It's a continuous effort – v4 was [18% smaller](https://bundlephobia.com/result?p=@material-ui/[email protected]) than v3, while adding new features.
4640
We are eager to find new bundle size reduction opportunities. We hope we can leverage these two in the future:
47-
- A JSS to styled-component migration should help. Compare [JSS v10.0.0-alpha.24](https://bundlephobia.com/[email protected]) with [styled-components v5.0.0-beta.8](https://bundlephobia.com/[email protected]). We could save ~6 kB gzipped.
48-
- Popper.js is working [on a smaller v2](https://bundlephobia.com/[email protected]) version. We could save ~4 kB gzipped.
41+
- 0.2 - **TypeScript.** 📏 There are two dimensions to this problem:
42+
- The definitions. We are **continuously** improving them. For instance, we are working on moving the props descriptions to TypeScript, so you can access them directly from your IDE.
43+
The codebase is written in JavaScript, we don't plan on migrating it to TypeScript in the near future. Upvote [#15984](https://github.com/mui-org/material-ui/issues/15984) if you want us to rewrite the core in a future version.
4944
- 0.2 - **Accessibility.** ♿️ We have relatively [few accessibility issues](https://darekkay.com/blog/accessible-ui-frameworks/), but we are eager to address them all. We would appreciate the help of accessibility experts.
5045
- 0.2 - **Material Design Update.** 🎀 We are relatively up-to-date but the material design specification [is evolving](https://material.io/whats-new/), so should we.
5146

5247
## New components
5348

54-
Here are the components we will work on being supported in the Material-UI ecosystem, no matter if they are from @material-ui/core, a third-party project or a paid source:
49+
Here are the components we will work on being supported in the Material-UI ecosystem, no matter if they are part of the [community edition](https://github.com/mui-org/material-ui) (MIT license) or [Material-UI X](https://github.com/mui-org/material-ui-x), a paid extension for enterprises:
5550

56-
- 🧪 In the lab, in progress to move into the core
57-
- 🛠 Work in progress, will likely land in the lab
51+
- 🧪 Close to become stable, already released as unstable
52+
- 🛠 Work in progress, will or already released as unstable
5853
- ⏳ Planning to build
59-
- ⭐️ We will consider making some of the features paid (non MIT)
54+
- ⭐️ We will make some of the features available in [Material-UI X](https://github.com/mui-org/material-ui-x) (non-MIT)
6055

61-
| Name | Status |
62-
| ----------------------- | ------ |
63-
| Rating | 🧪 |
64-
| Skeleton | 🧪 |
65-
| Speed Dial | 🧪 |
66-
| Toggle Button | 🧪 |
67-
| Tree View | 🧪 |
68-
| Autocomplete | 🧪 |
69-
| Combo Box | 🧪 |
70-
| Multiselect | 🧪 |
71-
| Alert | 🧪 |
72-
| Pagination | 🧪 |
73-
| Date Picker (& range) | 🛠 |
74-
| Data Table | 🛠⭐️ |
75-
| Carousel ||
76-
| Dropdown ||
77-
| Dropzone ||
78-
| File Upload ||
79-
| Image ||
80-
| Navbar ||
81-
| Nested Menu ||
82-
| Numeric Input ||
83-
| Scrollspy ||
84-
| TopLayout ||
85-
| Big Calendar | ⏳⭐️ |
86-
| Charts | ⏳⭐️ |
87-
| Sparkline | ⏳⭐️ |
88-
| Color Picker | ⏳⭐️ |
89-
| Gantt Chart | ⏳⭐️ |
90-
| Gauge | ⏳⭐️ |
91-
| Masonry | ⏳⭐️ |
92-
| Pivot Grid | ⏳⭐️ |
93-
| Rich Text Editor | ⏳⭐️ |
94-
| Scheduler | ⏳⭐️ |
95-
| Splitter | ⏳⭐️ |
96-
| Tree View - Checkbox | ⏳⭐️ |
97-
| Tree View - Drag & Drop | ⏳⭐️ |
98-
| TreeSelect | ⏳⭐️ |
56+
| Name | Status |
57+
| :------------------------- | ------ |
58+
| Rating | 🧪 |
59+
| Skeleton | 🧪 |
60+
| Speed Dial | 🧪 |
61+
| Toggle Button | 🧪 |
62+
| Autocomplete | 🧪 |
63+
| Combo Box | 🧪 |
64+
| Multiselect | 🧪 |
65+
| Alert | 🧪 |
66+
| Pagination | 🧪 |
67+
| Timeline | 🧪 |
68+
| Date Picker | 🛠 |
69+
| Date Range Picker | 🛠⭐ |
70+
| Data Grid | 🛠⭐️ |
71+
| Data Grid - Column pinning | ⏳⭐️ |
72+
| Data Grid - Nested row | ⏳⭐️ |
73+
| Tree View | 🛠 |
74+
| Tree View - Multiselect | 🛠⭐️ |
75+
| Tree View - Checkbox | ⏳⭐️ |
76+
| Tree View - Drag & Drop | ⏳⭐️ |
77+
| Tree View - Virtualization | ⏳⭐️ |
78+
| Carousel ||
79+
| Dropdown ||
80+
| Dropzone ||
81+
| File Upload ||
82+
| Image ||
83+
| Stack ||
84+
| Navbar ||
85+
| NProgress ||
86+
| Nested Menu ||
87+
| Numeric Input ||
88+
| Scrollspy ||
89+
| TopLayout ||
90+
| Splitter | ⏳⭐️ |
91+
| Masonry | ⏳⭐️ |
92+
| Pivot Grid | ⏳⭐️ |
93+
| Big Calendar | ⏳⭐️ |
94+
| Sparkline | ⏳⭐️ |
95+
| Gauge | ⏳⭐️ |
96+
| Charts | ⏳⭐️ |
97+
| TreeSelect | ⏳⭐️ |
98+
| Rich Text Editor | ⏳⭐️ |
99+
| Gantt Chart | ⏳⭐️ |
100+
| Color Picker | ⏳⭐️ |
99101

100102
> ⚠️ **Disclaimer**: We operate in a dynamic environment, and things are subject to change. The information provided is intended to outline the general framework direction. It's intended for informational purposes only. We may decide to add/remove new items at any time depending on our capability to deliver while meeting our quality standards. The development, releases and timing of any features or functionality of Material-UI remains at the sole discretion of Material-UI. The roadmap does not represent a commitment, obligation or promise to deliver at any time.

0 commit comments

Comments
 (0)