Help useAutocomplete hook example, 4.5 kB gzipped.
- If you wish to make your first contribution to open source, the component has a couple of ["good first issues"](https://github.com/mui-org/material-ui/labels/lab%3A%20Autocomplete) that can be taken.
- If you have TypeScript expertise, the component could [benefit from it](https://github.com/mui-org/material-ui/issues?q=is%3Aopen+label%3A%22lab%3A+Autocomplete%22+label%3Atypescript).
+ If you wish to make your first contribution to open source, the component has a couple of ["good first issues"](https://github.com/mui/material-ui/labels/lab%3A%20Autocomplete) that can be taken.
+ If you have TypeScript expertise, the component could [benefit from it](https://github.com/mui/material-ui/issues?q=is%3Aopen+label%3A%22lab%3A+Autocomplete%22+label%3Atypescript).
- 📆 We have made a first [alpha release](https://next.material-ui-pickers.dev/demo/daterangepicker) of the date range picker. It's not ready to be used in production but you can start playing. We might release some of the new features of the date picker under the upcoming Enterprise offering.
@@ -93,20 +93,20 @@ We'll do our best, no guarantee!
For illustration purposes only.
- 📆 We will polish the date picker. We will work on: providing a comprehensive set of features, to unify the experience with the core package, to improve the overall quality. The objective is to make these components stable in the next major (v5).
-- ❓ Please upvote our [GitHub issues](https://github.com/mui-org/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
+- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
diff --git a/docs/pages/blog/2020-q2-update.md b/docs/pages/blog/2020-q2-update.md
index bd0ae316a554d2..f0a977d3f5f876 100644
--- a/docs/pages/blog/2020-q2-update.md
+++ b/docs/pages/blog/2020-q2-update.md
@@ -12,9 +12,9 @@ This update covers our progress over the last three months, and what we aim to a
Here are the most significant improvements since March 2020:
-- 🚧 Work has started on [the next major version: v5](https://github.com/mui-org/material-ui/issues/20012).MUI's repository
- On the other hand, we started using TypeScript from day one for _mui-org/material-ui-x_.
+ On the other hand, we started using TypeScript from day one for _mui/mui-x_.
MUI X's repository
- 🐙 We have migrated large parts of the test suite to react-testing-library.Slider powered by styled-components
-- ♿︎ We have kept investing in accessibility, we have fixed [13 bugs](https://github.com/mui-org/material-ui/pulls?q=is%3Apr+label%3Aaccessibility+is%3Aclosed+sort%3Aupdated-desc).
-- 🗓 We have introduced public quarterly roadmaps, both for [community](https://github.com/mui-org/material-ui/projects) and [enterprise](https://github.com/mui-org/material-ui-x/projects).
+- ♿︎ We have kept investing in accessibility, we have fixed [13 bugs](https://github.com/mui/material-ui/pulls?q=is%3Apr+label%3Aaccessibility+is%3Aclosed+sort%3Aupdated-desc).
+- 🗓 We have introduced public quarterly roadmaps, both for [MUI Core](https://github.com/mui/material-ui/projects/25) and [MUI X](https://github.com/mui/mui-x/projects/1).
## Company
@@ -141,7 +141,7 @@ We are thrilled to welcome two new full-time developers to MUI:
% of download relative to react-dom
-- ⭐️ From 59.0k to 61.6k stars, leave us yours [🌟](https://github.com/mui-org/material-ui).
+- ⭐️ From 59.0k to 61.6k stars, leave us yours [🌟](https://github.com/mui/material-ui).
- 👨👩👧👦 From 1,825 to 1,934 contributors on GitHub. We add on average 1 new contributor every day.
- 🏢 We have welcomed two new full-time developers to MUI.
@@ -151,20 +151,20 @@ We'll do our best, no guarantee!
### Community
-- 🗓 Execute on all the items of the [public roadmap](https://github.com/mui-org/material-ui/projects/25).
+- 🗓 Execute on all the items of the [public roadmap](https://github.com/mui/material-ui/projects/25).
- 👩🎨 Simplify the migration experience from v4 to v5.
-- ❓ Please upvote [GitHub issues](https://github.com/mui-org/material-ui/issues) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
+- ❓ Please upvote [GitHub issues](https://github.com/mui/material-ui/issues) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
### Enterprise
- 👩🎨 Complete the collaboration we started with a design agency last quarter to update the branding of the company, redesign the homepage, and design the marketing pages for the enterprise package.
-- 🗓 Execute on all the items in the [public roadmap](https://github.com/mui-org/material-ui-x/projects/1).
-- ❓ Please upvote [GitHub issues](https://github.com/mui-org/material-ui-x/issues) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
+- 🗓 Execute on all the items in the [public roadmap](https://github.com/mui/mui-x/projects/1).
+- ❓ Please upvote [GitHub issues](https://github.com/mui/mui-x/issues) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
### Company
These are objectives, no guarantees:
-- 🏢 We might hire a full-time designer that has coding skills. One of the objectives would be to solve [#22485](https://github.com/mui-org/material-ui/issues/22485).
+- 🏢 We might hire a full-time designer that has coding skills. One of the objectives would be to solve [#22485](https://github.com/mui/material-ui/issues/22485).
- 🏝 We have put the company-wide team retreat on hold because of the continued risk presented by COVID-19.
Hopefully, we will be able to hold it in Q2 2021.
diff --git a/docs/pages/blog/2020.md b/docs/pages/blog/2020.md
index 30a4b482d74e27..9cb5688bb030f6 100644
--- a/docs/pages/blog/2020.md
+++ b/docs/pages/blog/2020.md
@@ -16,8 +16,8 @@ It's only with your trust that we could achieve the following outcomes in 2020.
- 📦 From 3.2M to [6.4M](https://npm-stat.com/charts.html?package=%40material-ui%2Fcore&from=2019-11-30&to=2020-12-31) downloads per month (from 14% to [18%](https://docs.google.com/spreadsheets/d/1l5j3Xjtvm9XZtmb4ulLiWElQaXSlZlyCWT5ONrQMpBo/edit?usp=sharing) share of the React ecosystem).
- 📈 From 3.1M to 4.6M unique visitors per year on the documentation.
-- ⭐️ From 53.3k to 63.8k stars, leave us [yours 🌟](https://github.com/mui-org/material-ui).
-- 👨👩👧👦 From 1,581 to [2,052](https://github.com/mui-org/material-ui/graphs/contributors) contributors.
+- ⭐️ From 53.3k to 63.8k stars, leave us [yours 🌟](https://github.com/mui/material-ui).
+- 👨👩👧👦 From 1,581 to [2,052](https://github.com/mui/material-ui/graphs/contributors) contributors.
- 💰 Grew financial support by 2.1X in 2020, compared to 2019.
- 🏢 From 3 to 6 full-time equivalent developers, spread among multiple financially supported [core team members](/about/).
@@ -83,15 +83,15 @@ We will release the next major iteration of the library. A highlight of the key
- Improve customizability. Add new powers to the theme with dynamic color & [variant](https://mui.com/customization/typography/#adding-amp-disabling-variants) support. Add a new [`sx` prop](https://mui.com/system/basics/) for quick customizations to all the components. Expose global class names. Deprecate the `makeStyles` and `withStyles` API.
- Breaking changes on the API to make it more intuitive.
- Add full support for React strict mode. We recommend to enable it.
-- Improve the performance of the system by a x3-x5 [factor](https://github.com/mui-org/material-ui/issues/21657#issuecomment-707140999).
-- Reduce bundle size: split IE11 into a different bundle [-6kB](https://github.com/mui-org/material-ui/pull/22814#issuecomment-700995216), migrate to emotion [-5kB](https://github.com/mui-org/material-ui/pull/23308#issuecomment-718748835), Popper.js v2 upgrade [-700B](https://github.com/mui-org/material-ui/pull/21761#issuecomment-657135498).
+- Improve the performance of the system by a x3-x5 [factor](https://github.com/mui/material-ui/issues/21657#issuecomment-707140999).
+- Reduce bundle size: split IE11 into a different bundle [-6kB](https://github.com/mui/material-ui/pull/22814#issuecomment-700995216), migrate to emotion [-5kB](https://github.com/mui/material-ui/pull/23308#issuecomment-718748835), Popper.js v2 upgrade [-700B](https://github.com/mui/material-ui/pull/21761#issuecomment-657135498).
- Improve the documentation website: search shortcut, page rating, fast material icons copy button, etc.
-And [much more](https://github.com/mui-org/material-ui/issues/20012).
+And [much more](https://github.com/mui/material-ui/issues/20012).
### A second theme
-While Material Design is a predominant design choice for building rich client-side applications, it's not the only popular design trend. We plan to provide a [second theme](https://github.com/mui-org/material-ui/issues/22485) to expand the range of use cases for MUI, striking a balance between:
+While Material Design is a predominant design choice for building rich client-side applications, it's not the only popular design trend. We plan to provide a [second theme](https://github.com/mui/material-ui/issues/22485) to expand the range of use cases for MUI, striking a balance between:
- alignment with the best-looking design trends of hot startups in the US.
- optimization of its usage for rich client-side applications while keeping it good enough for landing pages.
@@ -104,7 +104,7 @@ It will be built on top of the unstyled components.
While the completion of the unstyled components was originally part of the v5 milestone,
we will likely finish this effort independently.
-Outside of the requirement to introduce breaking changes on the component customization API, e.g. from `PaperProps` to `componentsProps`, [RFC #20012](https://github.com/mui-org/material-ui/issues/21453), we can work on unstyled at the same time we make progress with the second theme. The two efforts should go hand in hand.
+Outside of the requirement to introduce breaking changes on the component customization API, e.g. from `PaperProps` to `componentsProps`, [RFC #20012](https://github.com/mui/material-ui/issues/21453), we can work on unstyled at the same time we make progress with the second theme. The two efforts should go hand in hand.
### Scale
diff --git a/docs/pages/blog/2021-q1-update.md b/docs/pages/blog/2021-q1-update.md
index 70c0f0cd56f9ec..7dc729565a84a7 100644
--- a/docs/pages/blog/2021-q1-update.md
+++ b/docs/pages/blog/2021-q1-update.md
@@ -18,13 +18,13 @@ Here are the most significant improvements since December 2020.
- 👩🎤 We have worked on rolling out and scaling the new **styling engine** to all the components.
At this point, we have migrated 129 out of 167 components to emotion/styled-components.
Most of the components left to be migrated are in the lab.
- We are almost done! You can subscribe to [material-ui#24405](https://github.com/mui-org/material-ui/issues/24405) to be notified once finished.
+ We are almost done! You can subscribe to [material-ui#24405](https://github.com/mui/material-ui/issues/24405) to be notified once finished.
The community has provided invaluable assistance.
- 📚 To complement the migration of the components, we have worked on the migration of the code examples in the documentation,
favoring the `sx` prop where possible.
When a component needs to render styles based on the provided props, we have used the `styled` API.
Effectively, `makeStyle` and `withStyles` have been removed from the demos (we will deprecate these modules later on).
- You can subscribe to [material-ui#16947](https://github.com/mui-org/material-ui/issues/16947) to be notified once finished.
+ You can subscribe to [material-ui#16947](https://github.com/mui/material-ui/issues/16947) to be notified once finished.
- 📚 We have used the update of the documentation as an opportunity to break down the demos into smaller **single-focus** ones, with inline previews.
For instance:
@@ -47,7 +47,7 @@ Here are the most significant improvements since December 2020.
You can find [more details](https://mui.com/components/stack/) in the documentation.
- 🎨 We have improved the support for custom colors and variants.
- This is [one](https://github.com/mui-org/material-ui/issues/13875) of the most upvoted issues in the GitHub issue tracker.
+ This is [one](https://github.com/mui/material-ui/issues/13875) of the most upvoted issues in the GitHub issue tracker.
The migration to the new style engine allows us to fully rely on dynamic styles.
Developers can now do the following:
@@ -135,7 +135,7 @@ The date picker is at the border between the advanced components and the design
- 🌏 We have introduced support for [custom locales](/components/data-grid/localization/).
- 🚨 We have started to work on breaking changes to reach a stable state.
- 💾 We have extended the support of @mui/material to handle v4 and v5 at the same time.
- In the future, we might desynchronize the release version of _mui/material-ui_ and _mui/material-ui-x_.
+ In the future, we might desynchronize the release version of _mui/material-ui_ and _mui/mui-x_.
For MUI X, we will likely need to release breaking changes at a higher frequency: every six months.
- 🎛 We have added a column selector.
@@ -179,7 +179,7 @@ This Handbook is the single **source of truth**. It's meant to be updated by any
Most indicators point to it: [StackOverflow questions](https://insights.stackoverflow.com/trends?tags=vue.js%2Creactjs%2Cangular), [stars](https://bestofjs.org/projects?sort=monthly), [downloads](https://npm-stat.com/charts.html?package=react-dom,@angular/core,vue), [Traffic on the documentation](https://www.similarweb.com/website/reactjs.org/?competitors=vuejs.org).
Our strategy to focus on React only seems to be paying off.
-- ⭐️ From 63.8k to 67.2k stars, leave us yours [🌟](https://github.com/mui-org/material-ui).
+- ⭐️ From 63.8k to 67.2k stars, leave us yours [🌟](https://github.com/mui/material-ui).
We have seen a significant influx of stars this quarter.
- 👨👩👧👦 From 2,052 to 2,141 contributors on GitHub. We add on average one new contributor every day.
- 💰 Grew gross revenue at +4%/week on average during the period.
@@ -205,15 +205,15 @@ We have the following objectives:
- 🚀 Get v5-beta (no more breaking changes) out! The development of this new version started almost a year ago. It's time to aim for the stable release.
- 📅 Start handling the issues with the date picker reported by developers.
-- 🗓 Execute on all the items of the [public roadmap](https://github.com/mui-org/material-ui/projects/25).
-- ❓ Please upvote [GitHub issues](https://github.com/mui-org/material-ui/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
+- 🗓 Execute on all the items of the [public roadmap](https://github.com/mui/material-ui/projects/25).
+- ❓ Please upvote [GitHub issues](https://github.com/mui/material-ui/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
### Advanced components
- ✍️ Release the Data Grid cell edit feature we have been working on for the last two months. [A preview](https://deploy-preview-1287--material-ui-x.netlify.app/components/data-grid/editing/).
- 📅 Start dedicating time to the date range picker.
-- 🗓 Execute on all the items in the [public roadmap](https://github.com/mui-org/material-ui-x/projects/1).
-- ❓ Please upvote [GitHub issues](https://github.com/mui-org/material-ui-x/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
+- 🗓 Execute on all the items in the [public roadmap](https://github.com/mui/mui-x/projects/1).
+- ❓ Please upvote [GitHub issues](https://github.com/mui/mui-x/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
### Design kits
diff --git a/docs/pages/blog/2021-q2-update.md b/docs/pages/blog/2021-q2-update.md
index f0b9335777dbe9..59519416713c91 100644
--- a/docs/pages/blog/2021-q2-update.md
+++ b/docs/pages/blog/2021-q2-update.md
@@ -25,12 +25,12 @@ Here are the most significant improvements since March 2021.
### Core components
-- 🔥 We've made enough progress to ship [v5.0.0-beta.0](https://github.com/mui-org/material-ui/releases/tag/v5.0.0-beta.0). Here are a few statistics to give an idea of the effort that went into it:
+- 🔥 We've made enough progress to ship [v5.0.0-beta.0](https://github.com/mui/material-ui/releases/tag/v5.0.0-beta.0). Here are a few statistics to give an idea of the effort that went into it:
- [12 months](/blog/2020-q2-update/#product) of dedicated focus.
We stopped work on v4 early on to fully dedicate to v5.
- 3,475 pull requests.
- - 5,092 commits (the extra commits came from the merge of [material-ui-pickers](https://github.com/mui-org/material-ui-pickers))
+ - 5,092 commits (the extra commits came from the merge of [material-ui-pickers](https://github.com/mui/material-ui-pickers))
- 398 new contributors.
- The equivalent of four full-time developers working on it on average (core team + community).
- 38 alpha releases, we release once a week.
@@ -40,7 +40,7 @@ Here are the most significant improvements since March 2021.
In v5, we have standardized on the `styled()` API as the styling foundation we build on top of, and introduced the [the `sx` prop](https://mui.com/system/the-sx-prop/) for one-off customizations.
The `styled()` API is loved by the community, and implemented by a number of styling libraries: styled-components, emotion, stitches, goober, etc. It allows us to support them all with [adapters](https://mui.com/guides/styled-engine/#how-to-switch-to-styled-components).
-- ⚒️ We added a [codemod CLI](https://github.com/mui-org/material-ui/tree/HEAD/packages/mui-codemod) and 17 transformations (so far) to automatically migrate codebases from v4 to v5.
+- ⚒️ We added a [codemod CLI](https://github.com/mui/material-ui/tree/HEAD/packages/mui-codemod) and 17 transformations (so far) to automatically migrate codebases from v4 to v5.
If you're not familiar with what a codemod is, check out [Effective Refactoring with Codemods by Edd Yerburgh](https://www.youtube.com/watch?v=H9qtLutnT_g).
- 💄 We have [updated the style of the Slider](https://mui.com/components/slider/#sizes) to better match the Material Design guidelines, and kept a similar style as before under `size="small"`:
@@ -168,18 +168,18 @@ After considering [different](https://basecamp.com/shapeup) [alternatives](https
### Growth between Q1 2021 and Q2 2021
- 📦 From 8.6M to 9.1M downloads per month on npm. We have 21.03% of market share inside the React ecosystem, up from 6.68%, 5 years ago.
-- ⭐️ From 67.2k to 69.1k stars. [Leave us yours 🌟](https://github.com/mui-org/material-ui)!
+- ⭐️ From 67.2k to 69.1k stars. [Leave us yours 🌟](https://github.com/mui/material-ui)!
- 👨👩👧👦 From 2,141 to 2,223 contributors on GitHub. We add on average one new contributor every day.
### New members
We have welcomed four new members to the company 🏢:
-- [Jun](/blog/siriwat-kunaporn-joining/), leads the implementation of a [second design system](https://github.com/mui-org/material-ui/issues/22485).
+- [Jun](/blog/siriwat-kunaporn-joining/), leads the implementation of a [second design system](https://github.com/mui/material-ui/issues/22485).
[ MUI Core v5.3.0](https://github.com/mui-org/material-ui/releases/tag/v5.3.0) introduces the ability to write a callback in style overrides (global theming), giving you full control of component customization at the theme level.
+[ MUI Core v5.3.0](https://github.com/mui/material-ui/releases/tag/v5.3.0) introduces the ability to write a callback in style overrides (global theming), giving you full control of component customization at the theme level.
Why is using a callback better than the existing plain object? Let me explain from the beginning…
## The problems
In v4, the style engine library was JSS which had some limitations.
-Style overrides were not able to support dynamic props via a callback so we relied on using classes. Take a look at the [`Chip` classes](https://github.com/mui-org/material-ui/blob/97d32b0ff3fae4537c20c79e619f132f4a5c5cbb/packages/mui-material/src/Chip/chipClasses.ts) for example – there are more than 20 classes that are incomplete if we count the permutation of elements (`root | avatar | icon | label | deleteIcon`), size (`small | medium | large`), and color (`primary | secondary | ...`).
+Style overrides were not able to support dynamic props via a callback so we relied on using classes. Take a look at the [`Chip` classes](https://github.com/mui/material-ui/blob/97d32b0ff3fae4537c20c79e619f132f4a5c5cbb/packages/mui-material/src/Chip/chipClasses.ts) for example – there are more than 20 classes that are incomplete if we count the permutation of elements (`root | avatar | icon | label | deleteIcon`), size (`small | medium | large`), and color (`primary | secondary | ...`).
This leads to a poor theming experience because developers need to know which specific key to customize.
We believe it would be better for developers if they could create custom styles by reading the component props, without ever needing to know what key they should use.
diff --git a/docs/pages/blog/danail-hadjiatanasov-joining.md b/docs/pages/blog/danail-hadjiatanasov-joining.md
index db42370f195d47..2a82f71fa4838a 100644
--- a/docs/pages/blog/danail-hadjiatanasov-joining.md
+++ b/docs/pages/blog/danail-hadjiatanasov-joining.md
@@ -21,6 +21,6 @@ Danail has already landed his first feature in the data grid: [column reordering
He's now actively working on new features for the data grid.
-The enterprise team will continue developing the data grid component, and progressively extend to new advanced components as we grow the team. Here's a quick view of [the enterprise roadmap](https://github.com/mui-org/material-ui-x/projects/1).
+The enterprise team will continue developing the data grid component, and progressively extend to new advanced components as we grow the team. Here's a quick view of [the enterprise roadmap](https://github.com/mui/mui-x/projects/1).
We couldn't be more excited to have Danail on the team! You can follow him on [Twitter](https://twitter.com/danail_h).
diff --git a/docs/pages/blog/danilo-leal-joining.md b/docs/pages/blog/danilo-leal-joining.md
index 238c9d2ba99f39..a4611e259a510c 100644
--- a/docs/pages/blog/danilo-leal-joining.md
+++ b/docs/pages/blog/danilo-leal-joining.md
@@ -22,7 +22,7 @@ We believe there are two high potential opportunities to explore: 1. how designe
His design [challenge assignment](https://www.figma.com/file/UPgXH2mdWqV8QzAuN5VM37/Danilo-assignment) (done under a few hours) gave us confidence that Danilo is exactly who the role needs.
While we can't predict the future, he's initially leading the design rebranding effort.
-Then, he will likely focus on a [second design system](https://github.com/mui-org/material-ui/issues/22485).
+Then, he will likely focus on a [second design system](https://github.com/mui/material-ui/issues/22485).
We couldn't be more excited to have Danilo on the team! He's the first designer to join us, ever.
A focus area with high potential 🌈 and that we have underinvested in for too long.
diff --git a/docs/pages/blog/december-2019-update.md b/docs/pages/blog/december-2019-update.md
index fd1638354905f7..eed8d7b5056968 100644
--- a/docs/pages/blog/december-2019-update.md
+++ b/docs/pages/blog/december-2019-update.md
@@ -8,7 +8,7 @@ tags: ['Company update']
Here are the most significant improvements in December:
-- 🚨 We have introduced a new [Alert](https://mui.com/components/alert/) component in the lab, thanks to **[@dimitropoulos](https://github.com/dimitropoulos)** ([#18702](https://github.com/mui-org/material-ui/pull/18702)). The component also supports composition with a [Snackbar](/components/snackbars/#customized-snackbars).
+- 🚨 We have introduced a new [Alert](https://mui.com/components/alert/) component in the lab, thanks to **[@dimitropoulos](https://github.com/dimitropoulos)** ([#18702](https://github.com/mui/material-ui/pull/18702)). The component also supports composition with a [Snackbar](/components/snackbars/#customized-snackbars).
@@ -26,7 +26,7 @@ Here are the most significant improvements in December:
-- 🌎 We have almost doubled the number of supported [locales](/guides/localization/#localization) from 13 to 22, thanks to our awesome contributors. [Help us](https://github.com/mui-org/material-ui/blob/next/packages/material-ui/src/locale/index.js) double this number next month 🚀!
+- 🌎 We have almost doubled the number of supported [locales](/guides/localization/#localization) from 13 to 22, thanks to our awesome contributors. [Help us](https://github.com/mui/material-ui/blob/next/packages/material-ui/src/locale/index.js) double this number next month 🚀!
But this summary is just scratching the surface. We have accepted 168 commits from 73 different contributors. We have changed 1,059 files with 13,468 additions and 8,584 deletions.
@@ -34,16 +34,16 @@ But this summary is just scratching the surface. We have accepted 168 commits fr
_(We'll do our best, no guarantee!)_
-- 💄 We will keep working on a new [pagination](https://github.com/mui-org/material-ui/pull/19049) component. You can already [preview it](https://deploy-preview-19049--material-ui.netlify.app/components/pagination/) (lead by [**@mbrookes**](https://github.com/mbrookes)).
+- 💄 We will keep working on a new [pagination](https://github.com/mui/material-ui/pull/19049) component. You can already [preview it](https://deploy-preview-19049--material-ui.netlify.app/components/pagination/) (lead by [**@mbrookes**](https://github.com/mbrookes)).
-- 📅 We will keep working on a major upgrade of the [date/time picker](https://github.com/mui-org/material-ui-pickers/issues/1293) components. We are working on desktop and range support (lead by [**@dmtrKovalenko**](https://github.com/dmtrKovalenko)).
+- 📅 We will keep working on a major upgrade of the [date/time picker](https://github.com/mui/material-ui-pickers/issues/1293) components. We are working on desktop and range support (lead by [**@dmtrKovalenko**](https://github.com/dmtrKovalenko)).
-- 🧮 We will keep working on a new [data grid](https://github.com/mui-org/material-ui/pull/18872) component. You can already [preview it](https://deploy-preview-18872--material-ui.netlify.app/components/data-grid/) (lead by [**@oliviertassinari**](https://github.com/oliviertassinari)).
+- 🧮 We will keep working on a new [data grid](https://github.com/mui/material-ui/pull/18872) component. You can already [preview it](https://deploy-preview-18872--material-ui.netlify.app/components/data-grid/) (lead by [**@oliviertassinari**](https://github.com/oliviertassinari)).
-❓ Please upvote our [GitHub issues](https://github.com/mui-org/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
+❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
diff --git a/docs/pages/blog/introducing-the-row-grouping-feature.md b/docs/pages/blog/introducing-the-row-grouping-feature.md
index 68ba49fe196bba..6c2394ea0e17e6 100644
--- a/docs/pages/blog/introducing-the-row-grouping-feature.md
+++ b/docs/pages/blog/introducing-the-row-grouping-feature.md
@@ -7,7 +7,7 @@ tags: ['MUI X', 'News']
---
A lot of you were asking about it, and we are pleased to announce that the Premium plan is on the road.
-After an incredible year fully focused on improving the DataGrid, we are moving forward by launching the first feature of the Premium plan: the [row grouping](/components/data-grid/group-pivot/#row-grouping) which is released in [v5.3.0](https://github.com/mui-org/material-ui-x/releases/tag/v5.3.0).
+After an incredible year fully focused on improving the DataGrid, we are moving forward by launching the first feature of the Premium plan: the [row grouping](/components/data-grid/group-pivot/#row-grouping) which is released in [v5.3.0](https://github.com/mui/mui-x/releases/tag/v5.3.0).
Let me introduce this new feature.
@@ -88,5 +88,5 @@ groupingValueGetter: ({ value }) => `${Math.floor(value.getFullYear() / 10)}0's`
More details about customization can be found in the [documentation](/components/data-grid/group-pivot/#disable-the-row-grouping)
-Thanks for reading. To get more information about the v5.3.0 release, visit the [changelog](https://github.com/mui-org/material-ui-x/releases/tag/v5.3.0).
-We hope you will enjoy this new feature. Do not hesitate to open [issues](https://github.com/mui-org/material-ui-x/issues/new/choose) to share feedback, report bugs, or propose enhancements.
+Thanks for reading. To get more information about the v5.3.0 release, visit the [changelog](https://github.com/mui/mui-x/releases/tag/v5.3.0).
+We hope you will enjoy this new feature. Do not hesitate to open [issues](https://github.com/mui/mui-x/issues/new/choose) to share feedback, report bugs, or propose enhancements.
diff --git a/docs/pages/blog/july-2019-update.md b/docs/pages/blog/july-2019-update.md
index 4684d0e94eb997..06bca8d48152fc 100644
--- a/docs/pages/blog/july-2019-update.md
+++ b/docs/pages/blog/july-2019-update.md
@@ -39,4 +39,4 @@ _(We'll do our best, no guarantee!)_
-- ❓ Please upvote our [GitHub issues](https://github.com/mui-org/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
+- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
diff --git a/docs/pages/blog/june-2019-update.md b/docs/pages/blog/june-2019-update.md
index c131b994cf8429..a580c3158dc588 100644
--- a/docs/pages/blog/june-2019-update.md
+++ b/docs/pages/blog/june-2019-update.md
@@ -31,4 +31,4 @@ _(We'll do our best, no guarantee!)_
You can already [preview it](https://deploy-preview-16455--material-ui.netlify.app/components/rating/).
-- ❓ Please upvote our [GitHub issues](https://github.com/mui-org/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
+- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
diff --git a/docs/pages/blog/march-2019-update.md b/docs/pages/blog/march-2019-update.md
index d3d7f94cb8487d..25409668f7752f 100644
--- a/docs/pages/blog/march-2019-update.md
+++ b/docs/pages/blog/march-2019-update.md
@@ -9,15 +9,15 @@ tags: ['Company update']
Here are the most significant improvements in March:
- We have removed the old styles modules 💅.
- Be aware [of the difference](/customization/default-theme/#material-ui-core-styles-vs-material-ui-styles) between `@mui/material/styles` and `@mui/styles`.
+ Be aware of the difference between `@material-ui/core/styles` and `@material-ui/styles`.
- The community has helped us to add many TypeScript demo variants. In order to minimize the overhead of handling two variants per demo (JavaScript & TypeScript), the JavaScript variant is generated from the TypeScript variant. If you are using TypeScript, you can ignore the `.propTypes =` assignations.
- We have migrated a few demos from the `withStyles()` API to the `makeStyles()` API.
If you are wondering which you should use, we would encourage the use of `makeStyles()` where possible. `withStyles()` is interesting for overriding component styles or for handling legacy class logics.
- We have made the [Box API](/system/basics/) stable 🥳.
```diff
- -import { unstable_Box as Box } from '@mui/material/Box';
- +import Box from '@mui/material/Box';
+ -import { unstable_Box as Box } from '@material-ui/core/Box';
+ +import Box from '@material-ui/core/Box';
```
- We have committed to [a new Roadmap](/discover-more/roadmap/) (prioritized) for the next 6 months.
@@ -28,11 +28,11 @@ Here are the most significant improvements in March:
_(We'll do our best, no guarantee!)_
-- We are almost done with [the v4.0.0-alpha breaking changes](https://github.com/mui-org/material-ui/issues/13663). You can already find [the upgrade path](/guides/migration-v3/) from v3 to v4 in the documentation. Next, we will release the first beta version (no more breaking changes).
+- We are almost done with [the v4.0.0-alpha breaking changes](https://github.com/mui/material-ui/issues/13663). You can already find [the upgrade path](/guides/migration-v3/) from v3 to v4 in the documentation. Next, we will release the first beta version (no more breaking changes).
The results of the MUI developer survey suggested that there are too many breaking changes.
Don't worry, it's almost over! We will focus on providing more components once we have released v4 stable.
- We will continue, and hopefully complete, the tasks we undertook:
- TypeScript demo variants.
- Migration from Classes to Hooks, removal of unnecessary internal components.
- Removal of `findDOMNode()`, support of `StrictMode`, forward of references.
-- ❓ Please upvote our [GitHub issues](https://github.com/mui-org/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
+- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
diff --git a/docs/pages/blog/marija-najdova-joining.md b/docs/pages/blog/marija-najdova-joining.md
index 6c7b345ed20ec1..bab62e59273039 100644
--- a/docs/pages/blog/marija-najdova-joining.md
+++ b/docs/pages/blog/marija-najdova-joining.md
@@ -13,8 +13,8 @@ Before joining MUI, Marija worked on the React implementation of [Fluent UI](htt
Marija is off to a running start, having made important changes happen during her free time, even before starting! These include a new structure for the theme object, as well as the ability to [add custom variants](https://mui.com/customization/theme-components/#adding-new-component-variants) in v5:
-She is now actively working on the unstyled components and [the update of the style engine](https://github.com/mui-org/material-ui/issues/22342). These are two items we've been eager to push forward since the release of v1 but that required someone to be dedicated to tackling them.
+She is now actively working on the unstyled components and [the update of the style engine](https://github.com/mui/material-ui/issues/22342). These are two items we've been eager to push forward since the release of v1 but that required someone to be dedicated to tackling them.
-The community team will continue developing the foundations on which to build great design systems. Here's a quick view of [the community roadmap](https://github.com/mui-org/material-ui/projects/25).
+The community team will continue developing the foundations on which to build great design systems. Here's a quick view of [the community roadmap](https://github.com/mui/material-ui/projects/25).
We couldn't be more excited to have Marija on the team! You can follow her on [Twitter](https://twitter.com/marijanajdova).
diff --git a/docs/pages/blog/material-ui-is-now-mui.md b/docs/pages/blog/material-ui-is-now-mui.md
index 61a517fe7f5046..23379efd71ee82 100644
--- a/docs/pages/blog/material-ui-is-now-mui.md
+++ b/docs/pages/blog/material-ui-is-now-mui.md
@@ -11,10 +11,10 @@ card: true
Starting today we are evolving our brand identity to clarifying the difference between our company and our products.
-- Material-UI: the organization is now called [**MUI**](https://github.com/mui-org/).
-- Material-UI: the set of foundational MIT React components is now called [**MUI Core**](https://github.com/mui-org/material-ui).
+- Material-UI: the organization is now called [**MUI**](https://github.com/mui/).
+- Material-UI: the set of foundational MIT React components is now called [**MUI Core**](https://github.com/mui/material-ui).
- Material UI: the Material Design components developed by MUI. Also, we ditched the hyphen!
-- Material-UI X: the set of advanced React components is now called [**MUI X**](https://github.com/mui-org/material-ui-x).
+- Material-UI X: the set of advanced React components is now called [**MUI X**](https://github.com/mui/mui-x).
Our previous name was no longer serving our areas of focus.
We have grown our product offering.
@@ -87,7 +87,7 @@ To better identify, market, and promote each product, we're introducing logos fo
### New package names
The package names have changed in v5, which is a **breaking change**.
-You can find more details in the [release](https://github.com/mui-org/material-ui/releases/tag/v5.0.0) [notes](https://github.com/mui-org/material-ui-x/releases/tag/v4.0.0).
+You can find more details in the [release](https://github.com/mui/material-ui/releases/tag/v5.0.0) [notes](https://github.com/mui/mui-x/releases/tag/v4.0.0).
The npm organization name (scope) has moved from @material-ui to [@mui](https://www.npmjs.com/org/mui).
### A new website & documentation
diff --git a/docs/pages/blog/material-ui-v1-is-out.md b/docs/pages/blog/material-ui-v1-is-out.md
index f0521b9ca02fa5..b6bb25f4a3cae2 100644
--- a/docs/pages/blog/material-ui-v1-is-out.md
+++ b/docs/pages/blog/material-ui-v1-is-out.md
@@ -15,7 +15,7 @@ tags: ['Company update']
It has taken us two years to do it, but Material-UI v1 has finally arrived!
We are so excited about this release, as it's setting a new course for the project. Thank you to _everyone_, especially to [the team](/about/), and to everyone who's contributed code, issue triage, and support. **Thank you.**
-✨✨✨ See the [**1.0.0 Release Note**](https://github.com/mui-org/material-ui/releases/tag/v1.0.0) on GitHub. ✨✨✨
+✨✨✨ See the [**1.0.0 Release Note**](https://github.com/mui/material-ui/releases/tag/v1.0.0) on GitHub. ✨✨✨
@@ -23,15 +23,15 @@ We are so excited about this release, as it's setting a new course for the proje
## High-level Goals for v1
-Material-UI was started [3 years ago](https://github.com/mui-org/material-ui/commit/28b768913b75752ecf9b6bb32766e27c241dbc46) by [@hai-cea](https://github.com/hai-cea). The React ecosystem has evolved considerably since then, and we have also learned along the way. Two years ago, [@nathanmarks](https://github.com/nathanmarks/) [started](https://github.com/mui-org/material-ui/commit/cf0934dda2ef83852ca094ac7250e2d562ce6156) an ambitious task to rebuild Material-UI from the ground-up, taking advantage of this knowledge to address long-standing issues in customizability, ease of use, and code quality.
+Material-UI was started [3 years ago](https://github.com/mui/material-ui/commit/28b768913b75752ecf9b6bb32766e27c241dbc46) by [@hai-cea](https://github.com/hai-cea). The React ecosystem has evolved considerably since then, and we have also learned along the way. Two years ago, [@nathanmarks](https://github.com/nathanmarks/) [started](https://github.com/mui/material-ui/commit/cf0934dda2ef83852ca094ac7250e2d562ce6156) an ambitious task to rebuild Material-UI from the ground-up, taking advantage of this knowledge to address long-standing issues in customizability, ease of use, and code quality.
### Customizability
-Material-UI v1 is our second stab at the execution of [the vision](https://material-ui-next.com/discover-more/vision/).
+Material-UI v1 is our second stab at the execution of [the vision](/discover-more/vision/).
We want Material-UI to become whatever is generally useful for application development, all in the spirit of the Material Design guidelines. Material-UI is not only an implementation of the Material Design guidelines, but a general use UI library of components that are needed by many. We are even allowing developers to build non Material themes on top of Material-UI components. We will soon open source examples of this.
-- **CSS-in-JS**. We have seen [a great potential for **inline-styles** in the past](https://github.com/mui-org/material-ui/issues/30). It was an opportunity to solve four problems at once: removing the LESS toolchain dependency, allowing dynamic styles, allowing style code splitting and make overrides simpler.
- Unfortunately, the [**execution didn't deliver**](https://github.com/mui-org/material-ui/issues/4066). We were lacking key features only available in CSS: media queries, pseudo selectors, pseudo elements, browser prefixes. Debugging was much harder. Overriding styles was very challenging – developers always had to look the implementation, and couldn't use CSS without relying on !important.
+- **CSS-in-JS**. We have seen [a great potential for **inline-styles** in the past](https://github.com/mui/material-ui/issues/30). It was an opportunity to solve four problems at once: removing the LESS toolchain dependency, allowing dynamic styles, allowing style code splitting and make overrides simpler.
+ Unfortunately, the [**execution didn't deliver**](https://github.com/mui/material-ui/issues/4066). We were lacking key features only available in CSS: media queries, pseudo selectors, pseudo elements, browser prefixes. Debugging was much harder. Overriding styles was very challenging – developers always had to look the implementation, and couldn't use CSS without relying on !important.
Two years ago, we decided to move away [from inline-styles toward **CSS-in-JS**](https://github.com/oliviertassinari/a-journey-toward-better-style). We are very happy with the outcome. We would like to thank [@kof](https://github.com/kof) for the awesome work he has done with [JSS](https://github.com/cssinjs/jss), the internal solution we use. It's allowing us to be [interoperable](/guides/interoperability/) with all the other styling solutions.
- **Theme**. You can't have a good customizability story without a good theming story. We have been redesigning the theme. It's a [JavaScript object](/customization/default-theme/) that contains all the variables and utility functions you might need to style your components: a palette, a typography, breakpoints helpers, transition helpers, etc.
@@ -44,7 +44,7 @@ We know the ease of use is a critical part of user acquisition. The more user we
- **Onboarding**. We have reduced the onboarding friction as much as possible. We know the onboarding is a critical step for user acquisition. The onboarding friction comes in different flavors:
We have reduced the number of installation steps needed. It should be as simple as 1. npm install @mui/material and 2. import Button from '@mui/material/Button'; . We don't ask for polyfill, custom webpack plugin or any specific build tool. The usage of MuiThemeProvider is no longer mandatory.
-- **Examples**. We are hosting [example projects](https://github.com/mui-org/material-ui/tree/master/examples) with the most popular solutions to start a project: [create-react-app](https://github.com/facebook/create-react-app), [Next.js](https://github.com/vercel/next.js), [Gatsby](https://github.com/gatsbyjs/gatsby), and CDN.
+- **Examples**. We are hosting [example projects](https://github.com/mui/material-ui/tree/master/examples) with the most popular solutions to start a project: [create-react-app](https://github.com/facebook/create-react-app), [Next.js](https://github.com/vercel/next.js), [Gatsby](https://github.com/gatsbyjs/gatsby), and CDN.
- **Isolation**. Our components now work in isolation. You should be able to use a single Material-UI component in an existing codebase without any side effect. No global CSS override needed, no bundle size bloat.
@@ -62,19 +62,19 @@ Many people discover web development through Material-UI but it's also used in p
Lighthouse report of the Material-UI documentation homepage
-- **Continuous integration.** Every single line of code is tested. We have an impressive [💯% test coverage](https://codecov.io/gh/mui-org/material-ui/branch/master). With more than 700 contributors, it's really important. All these tests allow us to quickly iterate and with confidence. We run the test suite runs on all the supported platforms. We also run more than [180 visual regression tests](https://www.argos-ci.com/mui-org/material-ui) thanks to [Argos-CI](https://www.argos-ci.com/).
+- **Continuous integration.** Every single line of code is tested. We have an impressive [💯% test coverage](https://codecov.io/gh/mui/material-ui/branch/master). With more than 700 contributors, it's really important. All these tests allow us to quickly iterate and with confidence. We run the test suite runs on all the supported platforms. We also run more than [180 visual regression tests](https://www.argos-ci.com/mui/material-ui) thanks to [Argos-CI](https://www.argos-ci.com/).
 build](https://cdn-images-1.medium.com/max/2000/1*bnWGqotk36ivrYTp3dY7fA.png)
An example BrowserStack build
-- **Bundle size**. If you take all the Material-UI components, your bundle will weight more than 100 kB gzipped. Material-UI looks like a huge dependency but it's fine in practice with code splitting. You will most likely use ~40% of the library on a given page/screen. The bundle size is important. It's [constantly monitored](https://github.com/mui-org/material-ui/blob/ca69253843208c21593fff230151e1fffd93a566/.size-limit), which prevents us from introducing size regressions, and allows us to recognize positive efforts.
+- **Bundle size**. If you take all the Material-UI components, your bundle will weight more than 100 kB gzipped. Material-UI looks like a huge dependency but it's fine in practice with code splitting. You will most likely use ~40% of the library on a given page/screen. The bundle size is important. It's [constantly monitored](https://github.com/mui/material-ui/blob/ca69253843208c21593fff230151e1fffd93a566/.size-limit), which prevents us from introducing size regressions, and allows us to recognize positive efforts.
 output](https://cdn-images-1.medium.com/max/2000/1*AQoyq9OvjFZJE2Ep0UtCzA.png)
An example of size-limit
-- **Development warnings**. Because the API surface of UI components is so large, it's easy to leave the beaten path. We have condensed a large number of the issues raised into a number of informative development mode warnings to help you stay on the right track. Aside from [propTypes](https://reactjs.org/docs/typechecking-with-proptypes.html), we have added more than [20 warnings](https://github.com/mui-org/material-ui/search?p=1&q=warning&type=&utf8=%E2%9C%93), and the list will grow as we discover more edge cases.
+- **Development warnings**. Because the API surface of UI components is so large, it's easy to leave the beaten path. We have condensed a large number of the issues raised into a number of informative development mode warnings to help you stay on the right track. Aside from [propTypes](https://reactjs.org/docs/typechecking-with-proptypes.html), we have added more than [20 warnings](https://github.com/mui/material-ui/search?p=1&q=warning&type=&utf8=%E2%9C%93), and the list will grow as we discover more edge cases.
## What's new in v1?
@@ -95,7 +95,7 @@ There are so many new things, we can't be exhaustive. Aside from what we have al
- **More utils.** We want to work on new utility components: Spacing, Display, Color, etc.
- **Documentation.** We want to host multiple version of the documentation. Each minor release will bring a new hosted version of our documentation. Right now, we have v1.0.0, and come v1.1.0's release, we'll add that too. Prior releases will continue to be linked from our navigation as is already the case for v0.x.
- We want to translate the documentation into Chinese and more languages. [Any help is welcomed!](https://github.com/mui-org/material-ui/issues/9511)
+ We want to translate the documentation into Chinese and more languages. [Any help is welcomed!](https://github.com/mui/material-ui/issues/9511)
- **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](https://learnnextjs.com/) like Next.js has done, or an [egghead.io](https://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.
- **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.
@@ -126,5 +126,5 @@ Material-UI is an MIT-licensed open source project. It's an independent project
Our gold sponsors
-- GitHub: https://github.com/mui-org/material-ui ⭐
+- GitHub: https://github.com/mui/material-ui ⭐
- Twitter: https://twitter.com/MUI_hq
diff --git a/docs/pages/blog/material-ui-v4-is-out.md b/docs/pages/blog/material-ui-v4-is-out.md
index fef651aa112ddb..f3127f1d36f937 100644
--- a/docs/pages/blog/material-ui-v4-is-out.md
+++ b/docs/pages/blog/material-ui-v4-is-out.md
@@ -10,7 +10,7 @@ tags: ['Company update']
Material-UI v4 has finally arrived. We are so excited about this release, as it defines better foundations for the UI components. Thank you to everyone, especially to [the team](/about/), and to everyone who's contributed code, issue triage, and support. **Thank you.**
-✨✨✨ See the **[4.0.0 Release Note](https://github.com/mui-org/material-ui/releases/tag/v4.0.0)** on GitHub. ✨✨✨
+✨✨✨ See the **[4.0.0 Release Note](https://github.com/mui/material-ui/releases/tag/v4.0.0)** on GitHub. ✨✨✨
@@ -157,14 +157,14 @@ import {
A -15% bundle size reduction. ⚠️ Please don't use the absolute number to compare different UI libraries. Nobody should import the whole barrel index.js file. What matters is the cost of the individual modules you import.
-- **Continuous bundle size tracking**. This bundle size reduction is only possible because we track this metric in each pull request. We have improved our strategy moving from [size-limit](https://github.com/ai/size-limit) to a React [inspired solution](https://github.com/mui-org/material-ui/pull/14662).
+- **Continuous bundle size tracking**. This bundle size reduction is only possible because we track this metric in each pull request. We have improved our strategy moving from [size-limit](https://github.com/ai/size-limit) to a React [inspired solution](https://github.com/mui/material-ui/pull/14662).
Fine level tracking
-- **Preact X.** We have introduced a working [integration example with Preact](https://github.com/mui-org/material-ui/blob/HEAD/examples/preact/README.md). Preact is a fast, 1/10 smaller alternative to React, with the same modern API. We will do our best to support it.
-- **Runtime performance**. We have heard that some people struggle with the runtime cost of using Material-UI. We have solved a few problems reported, but nothing systematic. We have observed [a slight gain](https://github.com/mui-org/material-ui/pull/15023) by moving from the classes API to the hooks API. However, it's hard to make progress as we lack a properly setup performance bench. It's something to consider for v5.
+- **Preact X.** We have introduced a working [integration example with Preact](https://github.com/mui/material-ui/blob/HEAD/examples/preact/README.md). Preact is a fast, 1/10 smaller alternative to React, with the same modern API. We will do our best to support it.
+- **Runtime performance**. We have heard that some people struggle with the runtime cost of using Material-UI. We have solved a few problems reported, but nothing systematic. We have observed [a slight gain](https://github.com/mui/material-ui/pull/15023) by moving from the classes API to the hooks API. However, it's hard to make progress as we lack a properly setup performance bench. It's something to consider for v5.
### Preparing for the future
@@ -193,7 +193,7 @@ function MyButton() {
- React Dev Tools output for one Typography element in production (this POC might further improve the situation).
+ React Dev Tools output for one Typography element in production (this POC might further improve the situation).
- **Concurrent mode**. React has shared its [release timeline](https://reactjs.org/blog/2018/11/27/react-16-roadmap.html#react-16x-q2-2019-the-one-with-concurrent-mode) for the important features coming into React. [Concurrent mode](https://reactjs.org/blog/2018/11/27/react-16-roadmap.html#react-16x-q2-2019-the-one-with-concurrent-mode) should be released within the next few months. Concurrent Mode lets React apps be more responsive by rendering component trees without blocking the main thread. We have worked on getting ready for it. Most of the work was related to fixing the [](https://reactjs.org/docs/strict-mode.html) warnings. You should soon be able to leverage it 🔥.
- **Shallow tests.** We have removed the majority of our internal shallow tests to rely on [full mount tests](https://twitter.com/dan_abramov/status/1109461529227866112).
@@ -239,7 +239,7 @@ An application example of the Box component.
An example of the new spacing helper API.
-- A new [@material-ui/pickers](https://github.com/mui-org/material-ui-pickers) package created and supported by [Dmitriy Kovalenko](https://github.com/dmtrKovalenko) 📅.
+- A new [@material-ui/pickers](https://github.com/mui/material-ui-pickers) package created and supported by [Dmitriy Kovalenko](https://github.com/dmtrKovalenko) 📅.
diff --git a/docs/pages/blog/matheus-wichman-joining.md b/docs/pages/blog/matheus-wichman-joining.md
index cafc8512914b7a..a0f5bd824a2beb 100644
--- a/docs/pages/blog/matheus-wichman-joining.md
+++ b/docs/pages/blog/matheus-wichman-joining.md
@@ -15,7 +15,7 @@ He has spent the last three years focusing on React and the frontend world - his
Matheus is passionate about software development, so much so that he started his career very early on, coding in PHP and JavaScript, at age 14.
We were impressed by his capability to quickly jump into an unknown codebase and solve problems at their root.
-In a couple of days, he has managed to report and fix bugs, both in the core components (_mui-org/material-ui_) and in the advanced components repository (_mui-org/material-ui-x_).
+In a couple of days, he has managed to report and fix bugs, both in the core components (_mui/material-ui_) and in the advanced components repository (_mui/mui-x_).
While we can't predict the future, Matheus will initially help us deliver the planned breaking changes of MUI v5, increase the pace of development of the date range picker, and push the data grid forward.
diff --git a/docs/pages/blog/may-2019-update.md b/docs/pages/blog/may-2019-update.md
index 0af8a828a08352..9def9c6280c105 100644
--- a/docs/pages/blog/may-2019-update.md
+++ b/docs/pages/blog/may-2019-update.md
@@ -9,7 +9,7 @@ tags: ['Company update']
Here are the most significant improvements in May:
- 🎉 We released MUI v4 stable during the React Europe conference.
- You can find the details in our [blog post 📝](https://mui.com/blog/material-ui-v4-is-out/) and a quick introduction in this [5 minutes talk](https://www.youtube.com/watch?v=m54_CPfbWow).
+ You can find the details in our [blog post 📝](/blog/material-ui-v4-is-out/) and a quick introduction in this [5 minutes talk](https://www.youtube.com/watch?v=m54_CPfbWow).
- 🐛 We have made two subsequent releases after v4.0.0, containing a significant number of fixes (v4.0.1 and v4.0.2).
But this summary is just scratching the surface. We have accepted 206 commits from 78 different contributors. We have changed 3,031 files with 96,616 additions and 85,768 deletions.
@@ -35,4 +35,4 @@ _(We'll do our best, no guarantee!)_
You can contact us at contact@mui.com.
-- ❓ Please upvote our [GitHub issues](https://github.com/mui-org/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
+- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
diff --git a/docs/pages/blog/mui-core-v5.md b/docs/pages/blog/mui-core-v5.md
index 3471e5543f8277..2613e95982d6ae 100644
--- a/docs/pages/blog/mui-core-v5.md
+++ b/docs/pages/blog/mui-core-v5.md
@@ -16,7 +16,7 @@ card: true
tags: ['News']
---
-After over 400 days of development and over 40 canary releases, we are excited to introduce [MUI Core v5.0.0](https://github.com/mui-org/material-ui/releases/tag/v5.0.0)!
+After over 400 days of development and over 40 canary releases, we are excited to introduce [MUI Core v5.0.0](https://github.com/mui/material-ui/releases/tag/v5.0.0)!
` component is [x5-x10 more performant](https://codesandbox.io/s/zlh5w?file=/src/App.js) in v5, compared to v4.
-We would like to thank all the community contributors that made the migration of the components and documentation possible in [#24405](https://github.com/mui-org/material-ui/issues/24405) and [#16947](https://github.com/mui-org/material-ui/issues/16947): [@natac13](https://github.com/natac13), [@vicasas](https://github.com/vicasas), [@mngu](https://github.com/mngu), [@kodai3](https://github.com/kodai3), [@xs9627](https://github.com/xs9627), [@povilass](https://github.com/povilass), [@duganbrett](https://github.com/duganbrett), [@queengooborg](https://github.com/queengooborg), and more.
+We would like to thank all the community contributors that made the migration of the components and documentation possible in [#24405](https://github.com/mui/material-ui/issues/24405) and [#16947](https://github.com/mui/material-ui/issues/16947): [@natac13](https://github.com/natac13), [@vicasas](https://github.com/vicasas), [@mngu](https://github.com/mngu), [@kodai3](https://github.com/kodai3), [@xs9627](https://github.com/xs9627), [@povilass](https://github.com/povilass), [@duganbrett](https://github.com/duganbrett), [@queengooborg](https://github.com/queengooborg), and more.
It was a major undertaking!
Going forward, developers can either keep using JSS with the legacy `@mui/styles` package [or migrate from JSS](https://mui.com/guides/migration-v4/#migrate-from-jss).
@@ -194,7 +194,7 @@ It's how developers have extended the core components up until v4. However:
3. It adds a boilerplate.
For this reason, v5 comes with the capability to extend the built-in behavior of the components, right from the theme.
-This was one of the most upvoted GitHub issues: [#13875](https://github.com/mui-org/material-ui/issues/13875).
+This was one of the most upvoted GitHub issues: [#13875](https://github.com/mui/material-ui/issues/13875).
In practice, this change makes the MUI Core components extendable placeholders.
**First**, you can use the [existing style mapping](/customization/palette/#adding-new-colors) of the components.
@@ -375,8 +375,8 @@ const CustomButton = React.forwardRef(function CustomButton(
Codesandbox
-We discuss the effort in [#6218](https://github.com/mui-org/material-ui/issues/6218).
-You can use [#27170](https://github.com/mui-org/material-ui/issues/27170) to follow our progress.
+We discuss the effort in [#6218](https://github.com/mui/material-ui/issues/6218).
+You can use [#27170](https://github.com/mui/material-ui/issues/27170) to follow our progress.
## Improved DX
@@ -384,7 +384,7 @@ You can use [#27170](https://github.com/mui-org/material-ui/issues/27170) to fol
We have used the migration of the demos from JSS to emotion as an opportunity to rework them.
Many of the demos were originally added taking into account how they would help maintainers work on the components.
-Instead, we have reversed the priority, putting the developers using them [first](https://github.com/mui-org/material-ui/issues/22484).
+Instead, we have reversed the priority, putting the developers using them [first](https://github.com/mui/material-ui/issues/22484).
In practice, this means breaking down complex demos into smaller ones.
We aim to have as many "inline previews" as possible. It saves one click to expand the demo, and the mental overhead of figuring out what part of the code maps with what of interest you saw on the screen.
@@ -416,7 +416,7 @@ The migration has even allowed us to rethink some of the implementations, making
### TypeScript migration
-The MUI Core codebase is not completely written in TypeScript yet but we have been coming a long way ([MUI X](https://github.com/mui-org/material-ui-x) is).
+The MUI Core codebase is not completely written in TypeScript yet but we have been coming a long way ([MUI X](https://github.com/mui/mui-x) is).
In v4, we have written all the demos TypeScript first.
With v5, we have made new steps toward the adoption of TypeScript:
@@ -438,14 +438,14 @@ Overall, the language stats of GitHub give some qualitative measure of the progr
Autocomplete (free options)
-- 📅 We will start to work on a [major upgrade](https://github.com/mui-org/material-ui-pickers/issues/1293) of the date/time picker components.
+- 📅 We will start to work on a [major upgrade](https://github.com/mui/material-ui-pickers/issues/1293) of the date/time picker components.
- 🧮 We will start to work on a Data Table component.
⭐️ Notice that the advanced features of the data grid will be paid, behind an enterprise subscription. This is an effort part of [our roadmap](/discover-more/roadmap/) to answer enterprise needs.
-- ❓ Please upvote our [GitHub issues](https://github.com/mui-org/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
+- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
diff --git a/docs/pages/blog/siriwat-kunaporn-joining.md b/docs/pages/blog/siriwat-kunaporn-joining.md
index 5576db7863e85c..b606fe85169bf1 100644
--- a/docs/pages/blog/siriwat-kunaporn-joining.md
+++ b/docs/pages/blog/siriwat-kunaporn-joining.md
@@ -18,7 +18,7 @@ He's has demonstrated his care of the details and interest in design.
While we can't predict the future, Jun will initially help us get MUI v5 down the finish line.
Then, he will be focusing almost exclusively on pushing MUI further in the design realm.
-We might start with a [second theme](https://github.com/mui-org/material-ui/issues/22485), a rebranding, a revamp of the documentation or the implementation of ["blocks"](https://deploy-preview-16--material-ui-blocks.netlify.app/).
+We might start with a [second theme](https://github.com/mui/material-ui/issues/22485), a rebranding, a revamp of the documentation or the implementation of ["blocks"](https://deploy-preview-16--material-ui-blocks.netlify.app/).
Jun is the second of a series of 5 new positions we have recently opened and filled.
We will cross the 10 person milestone in the coming weeks.
diff --git a/docs/pages/blog/spotlight-damien-tassone.md b/docs/pages/blog/spotlight-damien-tassone.md
index e7a01a28b86fa4..4e8b635bfa4fce 100644
--- a/docs/pages/blog/spotlight-damien-tassone.md
+++ b/docs/pages/blog/spotlight-damien-tassone.md
@@ -15,6 +15,6 @@ Right from the start, Damien has made fast and significant progress. He has been
For product-related problems, please open
-
diff --git a/docs/src/layouts/AppFooter.tsx b/docs/src/layouts/AppFooter.tsx
index 59698eb18b820f..79df26a66e8917 100644
--- a/docs/src/layouts/AppFooter.tsx
+++ b/docs/src/layouts/AppFooter.tsx
@@ -143,7 +143,7 @@ export default function AppFooter() {
diff --git a/docs/src/modules/components/DemoErrorBoundary.js b/docs/src/modules/components/DemoErrorBoundary.js
index e0e7a5c5cb5c8d..fdc9bd29b46dec 100644
--- a/docs/src/modules/components/DemoErrorBoundary.js
+++ b/docs/src/modules/components/DemoErrorBoundary.js
@@ -38,13 +38,13 @@ export default class DemoErrorBoundary extends React.Component {
const title = `[docs] Demo ${name} crashes`;
const searchQuery = encodeURIComponent(`is:issue ${title}`);
const issueLink = newGithubIssueUrl({
- user: 'mui-org',
+ user: 'mui',
repo: 'material-ui',
title,
body: `
-- [ ] I have [searched for similar issues](https://github.com/mui-org/material-ui/issues?q=${searchQuery}) in this repository and believe that this is not a duplicate.
+- [ ] I have [searched for similar issues](https://github.com/mui/material-ui/issues?q=${searchQuery}) in this repository and believe that this is not a duplicate.
## Steps to Reproduce
1. Visit ${window.location.href}
diff --git a/docs/src/modules/components/Notifications.js b/docs/src/modules/components/Notifications.js
index 198d90e04aabd5..ea0ed16a8fdb12 100644
--- a/docs/src/modules/components/Notifications.js
+++ b/docs/src/modules/components/Notifications.js
@@ -93,7 +93,7 @@ export default function Notifications() {
// Soften the pressure on the main thread.
const timeout = setTimeout(() => {
- fetch('https://raw.githubusercontent.com/mui-org/material-ui/master/docs/notifications.json')
+ fetch('https://raw.githubusercontent.com/mui/material-ui/master/docs/notifications.json')
.then((response) => {
return response.json();
})
diff --git a/docs/src/modules/utils/helpers.test.js b/docs/src/modules/utils/helpers.test.js
index 630c56a56b2deb..654abd3f017ca7 100644
--- a/docs/src/modules/utils/helpers.test.js
+++ b/docs/src/modules/utils/helpers.test.js
@@ -3,7 +3,7 @@ import { getDependencies, pageToTitle } from './helpers';
describe('docs getDependencies helpers', () => {
before(() => {
- process.env.SOURCE_CODE_REPO = 'https://github.com/mui-org/material-ui';
+ process.env.SOURCE_CODE_REPO = 'https://github.com/mui/material-ui';
});
after(() => {
@@ -179,14 +179,14 @@ import * as Utils from '@mui/utils';
'react-dom': 'latest',
'@emotion/react': 'latest',
'@emotion/styled': 'latest',
- '@mui/material': 'https://pkg.csb.dev/mui-org/material-ui/commit/2d0e8b4d/@mui/material',
+ '@mui/material': 'https://pkg.csb.dev/mui/material-ui/commit/2d0e8b4d/@mui/material',
'@mui/icons-material':
- 'https://pkg.csb.dev/mui-org/material-ui/commit/2d0e8b4d/@mui/icons-material',
- '@mui/lab': 'https://pkg.csb.dev/mui-org/material-ui/commit/2d0e8b4d/@mui/lab',
- '@mui/styles': 'https://pkg.csb.dev/mui-org/material-ui/commit/2d0e8b4d/@mui/styles',
- '@mui/system': 'https://pkg.csb.dev/mui-org/material-ui/commit/2d0e8b4d/@mui/system',
- '@mui/utils': 'https://pkg.csb.dev/mui-org/material-ui/commit/2d0e8b4d/@mui/utils',
- '@mui/base': 'https://pkg.csb.dev/mui-org/material-ui/commit/2d0e8b4d/@mui/base',
+ 'https://pkg.csb.dev/mui/material-ui/commit/2d0e8b4d/@mui/icons-material',
+ '@mui/lab': 'https://pkg.csb.dev/mui/material-ui/commit/2d0e8b4d/@mui/lab',
+ '@mui/styles': 'https://pkg.csb.dev/mui/material-ui/commit/2d0e8b4d/@mui/styles',
+ '@mui/system': 'https://pkg.csb.dev/mui/material-ui/commit/2d0e8b4d/@mui/system',
+ '@mui/utils': 'https://pkg.csb.dev/mui/material-ui/commit/2d0e8b4d/@mui/utils',
+ '@mui/base': 'https://pkg.csb.dev/mui/material-ui/commit/2d0e8b4d/@mui/base',
});
});
diff --git a/docs/src/modules/utils/helpers.ts b/docs/src/modules/utils/helpers.ts
index 3993867bd474e8..c77da8dfa3fb20 100644
--- a/docs/src/modules/utils/helpers.ts
+++ b/docs/src/modules/utils/helpers.ts
@@ -123,13 +123,13 @@ function includePeerDependencies(
function getMuiPackageVersion(packageName: string, commitRef?: string): string {
if (
commitRef === undefined ||
- process.env.SOURCE_CODE_REPO !== 'https://github.com/mui-org/material-ui'
+ process.env.SOURCE_CODE_REPO !== 'https://github.com/mui/material-ui'
) {
// #default-branch-switch
return 'latest';
}
const shortSha = commitRef.slice(0, 8);
- return `https://pkg.csb.dev/mui-org/material-ui/commit/${shortSha}/@mui/${packageName}`;
+ return `https://pkg.csb.dev/mui/material-ui/commit/${shortSha}/@mui/${packageName}`;
}
/**
diff --git a/docs/src/pages/company/careers/designer.md b/docs/src/pages/company/careers/designer.md
index e39fba489984ef..f15055ac849448 100644
--- a/docs/src/pages/company/careers/designer.md
+++ b/docs/src/pages/company/careers/designer.md
@@ -28,7 +28,7 @@ Currently, we have five main projects that are not at all related to MD:
- [MUI Core](/core/):
- [MUI Base](/customization/unstyled-components/): the unstyled version of the components.
- [MUI System](/system/basics/): our most recent take on styling for React components.
- - [MUI Joy (working title)](https://github.com/mui-org/material-ui/discussions/29024): a second design system as an alternative to Material Design.
+ - [MUI Joy (working title)](https://github.com/mui/material-ui/discussions/29024): a second design system as an alternative to Material Design.
- [MUI X](/x): as mentioned, a growing set of advanced components.
Today, the flagship is the [Data Grid](/components/data-grid/), a game-changing component for presenting large amounts of data, which integrates perfectly with MUI Core.
- MUI Studio: a very recent endeavor aimed at exploring how our users can visually create apps 10x faster with the power of low-code and the flexibility of pro-code.
diff --git a/docs/src/pages/company/careers/technical-product-manager.md b/docs/src/pages/company/careers/technical-product-manager.md
index 5048ee0ff273e5..661aee3266f700 100644
--- a/docs/src/pages/company/careers/technical-product-manager.md
+++ b/docs/src/pages/company/careers/technical-product-manager.md
@@ -32,7 +32,7 @@ We need talented people to keep that going!
The advanced components team (X) needs help to build its best features.
We have started with the [data grid](/components/data-grid/) a year ago, but it's the beginning.
-Our users are continuously providing feedback on the most important [pains they face](https://github.com/mui-org/material-ui-x/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc).
+Our users are continuously providing feedback on the most important [pains they face](https://github.com/mui/mui-x/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc).
## About the role
diff --git a/docs/src/pages/production-error/ErrorDecoder.js b/docs/src/pages/production-error/ErrorDecoder.js
index f37343417a264c..1fd250d07b4c1b 100644
--- a/docs/src/pages/production-error/ErrorDecoder.js
+++ b/docs/src/pages/production-error/ErrorDecoder.js
@@ -99,7 +99,7 @@ export default function ErrorDecoder() {
Seems like we're having some issues loading the original message. Try
reloading the page. If the error persists please report this isse on our{' '}
- You can follow our progress at https://github.com/mui-org/material-ui/issues/27170.
+ You can follow our progress at https://github.com/mui/material-ui/issues/27170.
- 💄 We have updated the default `info` `success` `warning` color to be more accessible (#26817) @siriwatknp.
You can find the new [default values](https://mui.com/customization/palette/#default-values) in the documentation.
@@ -2062,9 +2062,9 @@ _Jul 01, 2021_
A big thanks to the 13 contributors who made this release possible. Here are some highlights ✨:
-- 🎉 This is the first beta release of v5! A huge thanks to everyone who helped to make this happen! We're targeting the 1st of September for a stable release, and will use the next two months to polish v5, and ease the migration from v4. You can follow [the v5 stable milestone](https://github.com/mui-org/material-ui/milestone/44) for more details. We now encourage any new projects to start on v5.
+- 🎉 This is the first beta release of v5! A huge thanks to everyone who helped to make this happen! We're targeting the 1st of September for a stable release, and will use the next two months to polish v5, and ease the migration from v4. You can follow [the v5 stable milestone](https://github.com/mui/material-ui/milestone/44) for more details. We now encourage any new projects to start on v5.
- 🚀 We have completed all the planned breaking changes.
-- ⚒️ We added the codemod CLI to simplify migration to v5 (#26941) @eps1lon. You can find it at [`@material-ui/codemod`](https://github.com/mui-org/material-ui/tree/HEAD/packages/mui-codemod).
+- ⚒️ We added the codemod CLI to simplify migration to v5 (#26941) @eps1lon. You can find it at [`@material-ui/codemod`](https://github.com/mui/material-ui/tree/HEAD/packages/mui-codemod).
- 🐛 The majority of other changes in this release were bug fixes, test utilities and docs.
### `@material-ui/core@5.0.0-beta.0`
@@ -2073,7 +2073,7 @@ A big thanks to the 13 contributors who made this release possible. Here are som
- [Tabs] Remove unnecessary wrapper from Tab (#26926) @siriwatknp
- `span` element that wraps children has been removed. `wrapper` classKey is also removed. More details about [this change](https://github.com/mui-org/material-ui/pull/26666).
+ `span` element that wraps children has been removed. `wrapper` classKey is also removed. More details about [this change](https://github.com/mui/material-ui/pull/26666).
```diff