Skip to content

Commit b1321ea

Browse files
asynclizcopybara-github
authored andcommitted
docs: update roadmap for maintenance mode
PiperOrigin-RevId: 747972511
1 parent 3b64e3b commit b1321ea

File tree

1 file changed

+46
-50
lines changed

1 file changed

+46
-50
lines changed

docs/roadmap.md

Lines changed: 46 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ order: 3
1010

1111
<!--*
1212
# Document freshness: For more information, see go/fresh-source.
13-
freshness: { owner: 'lizmitchell' reviewed: '2024-01-19' }
13+
freshness: { owner: 'lizmitchell' reviewed: '2025-04-15' }
1414
*-->
1515

1616
<!-- [TOC] -->
@@ -22,87 +22,83 @@ Components.
2222

2323
## Current
2424

25-
### Build new components
25+
**MWC is currently in maintenance mode,
26+
[see this announcement](https://github.com/material-components/material-web/discussions/5642)
27+
for more details.**
2628

27-
*Planned for 2024*
29+
There is no current work planned for new features or components. Bug fixes or
30+
other contributions may be added on a case-by-case basis.
2831

29-
One of our core goals is to provide Material Design components for the web.
30-
These are the components we are currently working on.
32+
## Future
33+
34+
**Note: No future work is planned while MWC is in
35+
[maintenance mode](https://github.com/material-components/material-web/discussions/5642).**
36+
These roadmap items represent what used to be planned.
37+
38+
### New components
3139

40+
These are components we have not built yet.
41+
42+
* Autocomplete
43+
* Badge
44+
* Banner
45+
* Bottom app bar
46+
* Bottom sheet
3247
* Card
48+
* Data table
49+
* Date picker
50+
* Navigation bar
3351
* Navigation drawer
52+
* Navigation rail
53+
* Search
54+
* Segmented button
3455
* Snackbar
56+
* Time picker
57+
* Top app bar
58+
* Tooltip
3559

3660
### Expand Material Design tokens
3761

38-
*Planned for Q1 2024*
39-
4062
We are adding shape and motion system tokens to support building expressive
4163
Material experiences.
4264

4365
We also want to make it easier to use Material Design tokens, such as applying
4466
Material typescale, shape, and color to your own components.
4567

46-
### Create TSX components
68+
### Density and spacing tokens
4769

48-
*Planned for Q1 2024*
70+
Density allows components to take up less vertical space for larger displays.
71+
While we have some spacing tokens already, we need a comprehensive spacing
72+
system to fully support density across components.
73+
74+
### Create TSX components
4975

5076
[TSX](https://www.typescriptlang.org/docs/handbook/jsx.html) is a popular
5177
language extension for frameworks like [React](https://reactjs.org/). We want to
5278
make it easier and more seamless to use Material Web Components in TSX.
5379

54-
### Follow accessibility best practices
55-
56-
*Planned for Q2 2024*
57-
58-
Everyone should be able to access and enjoy the web. We want our components to
59-
help others build accessible experiences.
60-
61-
We are working on supporting all of the following screen readers:
62-
63-
* VoiceOver
64-
* Talkback
65-
* ChromeVox
66-
* JAWS
67-
* NVDA
68-
6980
### Explore Material Design layouts
7081

71-
*Planned for Q4 2024*
72-
7382
Components are only part of the story to build fully expressive Material Design
7483
applications. We want to explore ways to support building applications that
7584
follow
7685
[Material's layout patterns](https://m3.material.io/foundations/layout/understanding-layout/overview).
7786

78-
## Future
79-
80-
### Planned new components
81-
82-
These are components we want to build next.
87+
## Past
8388

84-
* Autocomplete
85-
* Badge
86-
* Banner
87-
* Bottom app bar
88-
* Bottom sheet
89-
* Data table
90-
* Date picker
91-
* Navigation bar
92-
* Navigation rail
93-
* Search
94-
* Segmented button
95-
* Time picker
96-
* Top app bar
97-
* Tooltip
89+
### Follow accessibility best practices
9890

99-
### Density and spacing tokens
91+
*Completed in Q1 2024*
10092

101-
Density allows components to take up less vertical space for larger displays.
102-
While we have some spacing tokens already, we need a comprehensive spacing
103-
system to fully support density across components.
93+
Everyone should be able to access and enjoy the web. We want our components to
94+
help others build accessible experiences. The following screen readers are fully
95+
supported:
10496

105-
## Past
97+
* VoiceOver
98+
* Talkback
99+
* ChromeVox
100+
* JAWS
101+
* NVDA
106102

107103
### Cards and more
108104

0 commit comments

Comments
 (0)