[ROADMAP] Update the roadmap #11606
Merged
[ROADMAP] Update the roadmap #11606
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oliviertassinari
force-pushed
the
docs-update-roadmap
branch
2 times, most recently
from
a0a93bc
to
fb5b5e9
Compare
oliviertassinari
force-pushed
the
docs-update-roadmap
branch
from
fb5b5e9
to
6c69933
Compare
| this.mounted = true; | ||
|
|
||
| // Prevent search engines from indexing the notification. |
| @@ -15,9 +15,9 @@ import WarningIcon from '@material-ui/icons/Warning'; | |||
| import { withStyles } from '@material-ui/core/styles'; | |||
|
|
|||
| const variantIcon = { | |||
There was a problem hiding this comment.
Only filled icons for consistency.
oliviertassinari
force-pushed
the
docs-update-roadmap
branch
from
6c69933
to
43bbb99
Compare
oliviertassinari
force-pushed
the
docs-update-roadmap
branch
from
43bbb99
to
6965de0
Compare
mbrookes
reviewed
May 27, 2018
ROADMAP.md
Outdated
| 1. **More utils**. We want to work on new utility components: Spacing, Display, Color, etc. | ||
| 1. **Performance**. We can’t optimize something we can’t measure, and we don’t currently have a CI performance benchmark, so we will need to build one and start investigating bottlenecks. | ||
| 1. **Learning materials**. The quality of the documentation is equally as important as the quality of the implementation, and while the reference documentation is comprehensive, we could author a learning tutorial like Next.js has done, or an egghead.io course. | ||
| Themes. We want to provide common layouts example to make getting started even easier. We also plan on adding more premium themes. |
|
I guess you meant to piggy-back on this PR for misc. other changes? (I normally only do it by mistake! 😆) |
mbrookes
reviewed
May 27, 2018
ROADMAP.md
Outdated
| @@ -1,3 +1,13 @@ | |||
| # Roadmap | |||
|
|
|||
| The roadmap is a living document, and it is likely that priorities will change, but the list below should give some indication of our plans for the next major release, and for the future. | |||
|
|
|||
| Our priorities: | |||
| 1. **Material Design**. The Google Design team has recently released a new iteration on the Material Design specification, it’s focused on *themability*. This is great news! We will do our best to be up to date. It also confirms that heavily investing in customizability for v1 was a good call. We will continue our efforts. | |||
There was a problem hiding this comment.
'specification which is focused'
'to keep up to date'
'It also validates that'
'was a good call. We will continue our efforts in this area.'
ROADMAP.md
Outdated
| 1. **Performance**. We can’t optimize something we can’t measure, and we don’t currently have a CI performance benchmark, so we will need to build one and start investigating bottlenecks. | ||
| 1. **Learning materials**. The quality of the documentation is equally as important as the quality of the implementation, and while the reference documentation is comprehensive, we could author a learning tutorial like Next.js has done, or an egghead.io course. | ||
| 1. **Themes**. We want to provide common layouts example to make getting started even easier. We also plan on adding more premium themes. | ||
| 1. **Documentation**. We want to translate the documentation into Chinese and more languages. Any help is welcomed! |
ROADMAP.md
Outdated
| 1. **Learning materials**. The quality of the documentation is equally as important as the quality of the implementation, and while the reference documentation is comprehensive, we could author a learning tutorial like Next.js has done, or an egghead.io course. | ||
| 1. **Themes**. We want to provide common layouts example to make getting started even easier. We also plan on adding more premium themes. | ||
| 1. **Documentation**. We want to translate the documentation into Chinese and more languages. Any help is welcomed! | ||
| 1. **Bundle size**. The library needs to be as small as possible, so we need to work on solutions to further reduce the bundle size, for instance, supporting Preact or Nerv can help. |
There was a problem hiding this comment.
'for example, supporting Preact or Nerv.'
ROADMAP.md
Outdated
| 1. **Themes**. We want to provide common layouts example to make getting started even easier. We also plan on adding more premium themes. | ||
| 1. **Documentation**. We want to translate the documentation into Chinese and more languages. Any help is welcomed! | ||
| 1. **Bundle size**. The library needs to be as small as possible, so we need to work on solutions to further reduce the bundle size, for instance, supporting Preact or Nerv can help. | ||
| 1. **Type checking**. We will continue to improve the TypeScript and maybe the Flow coverage of the library. |
mbrookes
approved these changes
May 27, 2018
pelotom
approved these changes
May 28, 2018
This was referenced Dec 28, 2020
This was referenced Mar 14, 2021
This was referenced Mar 15, 2021
This was referenced Nov 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have more or less copy & paste what I have put into the v1 release blog post. It's a first draft to initiate the discussion.
It's high level. I think that it should be used to communicate and give an idea around where the project is going to focus its effort on. I don't think that we need to go into the details. Issues & milestones can be used for that. I have ordered the list.
Also, we need to keep in mind that at the end of the day, the majorities of our contributors (the long tail) work on what they care for, they completely ignore the roadmap. So, no pressure, this document is a best-effort guideline, nothing more.