index
int64 0
0
| repo_id
stringlengths 16
181
| file_path
stringlengths 28
270
| content
stringlengths 1
11.6M
| __index_level_0__
int64 0
10k
|
|---|---|---|---|---|
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-product-comparison.md | ---
title: An introduction to the MUI ecosystem
description: MUI is more than just Material UI. Consider Joy UI, Base UI, MUI X, and Toolpad for your next project.
date: 2022-11-01T00:00:00.000Z
authors: ['samuelsycamore']
card: true
tags: ['Product']
---
<img src="/static/blog/mui-product-comparison/ecosystem.png" style="width: 692px; margin-bottom: 24px; aspect-ratio: 173/80;" alt="Logos for all the high-level MUI products." />
MUI is so much more than Material UI!
You'll be forgiven if you thought MUI was merely shorthand for our most popular product.
In fact, MUI as an organization was founded to meet the growing needs of the Material UI community, and is now responsible for a whole suite of related products.
Material UI is the flagship; but it's also the gateway to MUI's ever-expanding ecosystem of UI tools.
Though our roots are in [Material Design](https://material.io/), we're branching out well beyond those constraints these days to deliver a wider range of tools for developers to ship new features faster.
Our primary offerings fall into two product lines: Core and X.
MUI Core contains our foundational component libraries (like Material UI), while MUI X offers components that are significantly more complex (like the Data Grid).
We're also in the early stages of developing a low-code internal tool builder called [MUI Toolpad](https://mui.com/toolpad/), which enables you to build with every Core and X component in a drag-and-drop interface.
Read on for more details on each of our products.
## MUI Core
<img src="/static/blog/mui-product-comparison/mui-core.png" style="width: 692px; margin-bottom: 24px; aspect-ratio: 173/75;" loading="lazy" alt="Diagram with all the MUI Core sub-products." />
The Core is MUI's foundational product line.
It grew out of Material UI, and that library's legacy lives on in the name of the repo on GitHub: [`mui/material-ui`](https://github.com/mui/material-ui).
But this repo contains much more than just Material UI these days.
We've carefully deconstructed this library to expose its best parts as isolated open-source projects.
More recent additions include Joy UI and Base UI, as well as our in-house styling solution, MUI System.
MUI Core is open-source, and we invite you to contribute wherever you see fit!
### Material UI
Material UI is an open-source React component library that implements Google's Material Design.
It includes a comprehensive collection of prebuilt components that are ready for use in production right out of the box.
Material UI is beautiful by design and features a suite of customization options that make it easy to implement your own custom design system on top of our components.
Get started in the [Material UI docs](/material-ui/getting-started/).
#### Key features
- **Material Design:** Your app will look and feel excellent by default, thanks to our meticulous implementation of Material Design (currently MD2; Material You is on the way).
- **Comprehensiveness:** With over 50 foundational components and counting, you've got everything you need to ship new features fast.
- **Maturity:** Material UI's age and maturity rival that of React itself, with its origins spanning all the way back to 2014.
- **Community:** Over 2,500 open-source contributors have made this library what it is today.
#### Ideal use cases
- User interfaces that adhere closely to Material Design.
- Internal admin tools.
- Dev teams that need to ship features in hours rather than weeks.
### Joy UI
Joy UI is an open-source React component library that implements MUI's own in-house design principles.
It's intended to serve as an alternative to Material UI for designs that don't adhere to Material Design specifications.
Try Joy UI if you appreciate the comprehensiveness and reliability of Material UI, but don't need all of the additional baggage that comes along with Material Design.
Get started in the [Joy UI docs](/joy-ui/getting-started/).
#### Key features
- **Innovative design:** Free from the constraints of Material Design, Joy UI is where we can innovate and experiment with fresh new ideas in design, UX, and DX.
- **Flexibility:** Customize with ease, and leverage the power of CSS variables to ensure consistency when making pixel-perfect adjustments.
#### Ideal use cases
- Projects that don't involve Material Design.
- Design systems that would benefit from less opinionated defaults when customizing.
- Client-facing apps that need to look and feel distinctly like _your_ brand.
### Base UI
Base UI is an open-source library of headless ("unstyled") React UI components and hooks.
These components were extracted from Material UI, and are now available as a standalone package.
They feature the same robust engineering but without any default styling solution or theme.
Base UI includes prebuilt components with production-ready functionality, along with low-level hooks for transferring that functionality to other components.
Get started in the [Base UI docs](/base-ui/getting-started/).
#### Key features
- **Total control over styles:** Unlike Material UI and Joy UI, Base UI doesn't ship with any default styles or styling solution.
Write CSS however you'd prefer—vanilla, modules, styled-components—or integrate a styling library like Tailwind CSS or Emotion.
- **Hooks for fully custom components:** When pre-built components aren't flexible enough, low-level hooks enable you to quickly add sophisticated functionality to your custom components.
- **Accessibility:** Base UI components are built with accessibility in mind. We do our best to make all components screen reader-friendly, and offer suggestions for optimizing accessibility throughout our documentation.
- **The core of MUI Core:** Base UI serves as the scaffold for Joy UI components, and future versions Material UI will also be built with Base UI as the foundation.
#### Ideal use cases
- Implementing fully custom designs.
- Creating custom components within a Material UI or Joy UI app.
- Adding functionality to fully custom components.
### MUI System
MUI System is a set of CSS utilities to help you build custom designs more efficiently when working with MUI component libraries like Material UI, Joy UI, and Base UI.
The System gives you a set of flexible, generic wrapper components like Box and Container that can be quickly customized using the `sx` prop.
This prop lets you define styles directly within the components themselves, rather than creating bulky and redundant `const` definitions with styled-components.
It also gives you direct access to your theme's custom design tokens to ensure consistency in one-off styles.
Get started in the [MUI System docs](/system/getting-started/).
#### Key features
- **Faster prototyping:** The `sx` prop lets you apply styles directly to a component by writing the CSS you already know.
This makes it a great tool for quickly assembling a prototype or styling a one-off component that doesn't need to be reused.
- **Write less code:** `sx` lets you avoid writing unnecessary styled-components code, and as such it can replace dozens of lines of code.
Check out [Why use MUI System?](/system/getting-started/usage/#why-use-mui-system) for an example.
#### Ideal use cases
- Quickly prototyping custom styles in Material UI, Joy UI, or Base UI.
- Creating one-off custom components.
## MUI X
<img src="/static/blog/mui-product-comparison/mui-x.png" style="width: 692px; margin-bottom: 24px; aspect-ratio: 173/75;" loading="lazy" alt="Diagram with all the MUI X components." />
MUI X is a collection of advanced UI components, including the Data Grid and the Date and Time Pickers.
These components are significantly more complex than those found in the MUI Core libraries.
They feature advanced functionality for data-rich applications and a wide range of other use cases.
While X components natively integrate with MUI Core, they are kept separate so you can more easily implement custom design systems with them.
MUI X is open-core. Base components are MIT-licensed, while more advanced features require a Pro or Premium commercial license.
See [Licensing](/x/introduction/licensing/) for details.
### Data Grid
The MUI X Data Grid is a fast and extensible React data table with advanced features for power users and complex use cases in data management and analysis.
It features an intuitive UI and corresponding API to display different views of a data set, with support for real-time updates, accessibility, theming, and custom templates.
#### Key features
- **Data management:** Create, retrieve, update and delete your data with ease.
- **Sophisticated data analysis:** Pin rows and columns, group and aggregate values, export your view of the data to other formats. MUI X's Data Grid is one of the most feature-rich grids available on the market today.
- **Intuitive customization:** Customizing the Data Grid's styles and behaviors works just like you'd expect if you're familiar with Material UI—no new concepts to master along the way.
- **Accessibility:** It's notoriously difficult to optimize a data grid's accessibility, which is precisely why we make it a top priority—we obsess over these details so you don't have to.
#### Ideal use cases
- Applications that feature massive data sets.
- Data analytics tools inside your app, reducing the need to jump to Excel.
- Apps built with MUI Core libraries that need advanced functionality.
### Date and Time Pickers
The MUI X Date and Time Pickers are a collection of React UI components that let users select dates and times from dialogs and text fields.
Components include the Date Picker, Time Picker, Date Range Picker, and Date Time Picker, with more on the way.
#### Key features
- **Third-party date library support:** All components include support for many of the most popular date libraries, so you can pick whichever you prefer.
- **Localization:** The Pickers are optimized for use anywhere in the world, with support for all variations on date and time formatting.
#### Ideal use cases
- Forms requiring date and time input from the user.
- Booking apps using date and time ranges.
- Enterprise apps using advanced date and time validation with constraints.
- Apps built with MUI Core libraries that need date and time functionality.
## MUI Toolpad
<img src="/static/blog/mui-product-comparison/mui-toolpad.png" style="width: 692px; margin-bottom: 24px; aspect-ratio: 173/75;" loading="lazy" alt="Small screenshot of MUI Toolpad's interface." />
Toolpad is a self-hosted low-code admin builder designed to extend MUI's suite of React components.
It's designed for developers of all trades who want to save time building internal applications.
Drag and drop pre-built UI components, connect your data sources, and your app is ready for deployment.
### Key features
- **Build faster than ever:** With MUI Toolpad, your development time can be measured in minutes rather than hours or days. Skip the mindless busywork of UI development and get straight to the core business logic.
- **Use the components you already know:** Toolpad comes preloaded with both MUI Core and X libraries, giving you the full power of MUI's components in a drag-and-drop interface.
- **Extensible with code:** Start with only bare-bones JavaScript to get up and running, and then jump from "low code" to "pro code" as needed to add custom features and functionality.
### Ideal use cases
- Admin tools with a tight deadline.
- Rapid in-browser prototyping for front-end and full-stack development.
## What comes next
MUI is firmly committed to the React ecosystem for the long term—our [company mission](https://mui-org.notion.site/Direction-d8b8c142a6a44e3aa963f26edf4e03db) is measured in decades, because we believe in the staying power of this open-source community.
We envision a world in which MUI's component libraries are the industry standard for React developers worldwide, and we've defined some ambitious goals for growth to make this a reality in the years to come.
To keep up with all of our new products and features, you can sign up for our mailing list at the bottom of this page to receive monthly updates.
We can't wait to see what you create!
| 4,200 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-x-end-v6-features.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './mui-x-end-v6-features.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,201 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-x-end-v6-features.md | ---
title: MUI X v6.18.0 and the latest features before the next major
description: New components, polished features, better performance and more.
date: 2023-11-13T00:00:00.000Z
authors: ['josefreitas']
card: false
tags: ['MUI X', 'News']
---
<div style="max-width:680px;width: 100%; height: 170px; overflow: hidden; margin-bottom: 16px;">
<a href="https://github.com/mui/mui-x/releases/tag/v6.18.0">
<img src="/static/blog/mui-x-end-v6-features/intro.png" alt="open v6.18.0 release page" style="width: 100%; height: 100%; object-fit: cover; object-position: center;" />
</a>
</div>
We are happy to share the newest MUI X features, marking the release of [MUI X v6.18.0](https://github.com/mui/mui-x/releases/tag/v6.18.0) and sealing v6 with new components and solid functionalities.
As we gear up to develop the next major version, let's review the notable new features introduced since our last [blog post](/blog/mui-x-mid-v6-features/).
## Table of contents
- [New stable components 🎉](#new-stable-components)
- [Charts](#charts)
- [Tree view](#tree-view)
- [Date Pickers](#date-pickers)
- [Smoothened animations](#smoothened-animations)
- [Clearable Field](#clearable-field)
- [Customization Playgrounds](#customization-playgrounds)
- [Data Grid](#data-grid)
- [Column Autosizing](#column-autosizing) [<span class="plan-pro"></span>](/x/introduction/licensing/#pro-plan 'Pro plan')
- [New examples](#new-examples)
- [Sparkline as a column type](#sparkline-as-a-column-type)
- [Performance improvements](#performance-improvements)
- [What's next](#whats-next)
- [Feedback](#feedback)
## New stable components
### Charts
The stable version of MUI X charts supports the most commonly used chart plots you'll need in your day-to-day applications.
Featuring lines, areas, bars, pie charts and scatter plots, the latest versions also include:
- **Animations**
Animations on bars, pie charts, and more to come.
<video preload="metadata" style="margin-bottom: 16px;" autoplay muted loop playsinline width="680" height="306">
<source src="/static/blog/mui-x-end-v6-features/bar-chart-animations.mp4" type="video/mp4">
</video>
- **Horizontal Bar Chart Support**
Recently added, the horizontal bars can broaden your data visualization spectrum, especially when you need to display long labels for multiple categories.
Check out Bar's [layout documentation](/x/react-charts/bars/#layout) for more details.
- **Improved Text Customization**
Customize the legend text to your heart's content, making your charts more readable and visually
appealing.
Get started with charts [now](/x/react-charts/#getting-started)!
### Tree view
After an extensive period of development and refinement in the lab and pre-release packages, and with the invaluable feedback we've received from you, the community, we're happy to share that the package is now officially stable!
<video preload="metadata" style="margin-bottom: 10px;" autoplay muted loop playsinline width="680" height="400">
<source src="/static/blog/mui-x-end-v6-features/tree-view-gmail.mp4" type="video/mp4">
</video>
Get started with tree view [now](/x/react-tree-view/getting-started/)!
## Date Pickers
### Smoothened animations
The animations have been smoothened, especially on Android devices, ensuring a more fluid user experience.
### Clearable Field
A much-anticipated feature, the date and time fields now allow users to clear a selected date with a single click.
You can learn how to use it at the [clearable behavior documentation](/x/react-date-pickers/fields/#clearable-behavior).
<video preload="metadata" style="margin-bottom: 10px;" autoplay muted loop playsinline width="680" height="128">
<source src="/static/blog/mui-x-end-v6-features/clearable-fields.mp4" type="video/mp4">
</video>
### Customization Playgrounds
We're constantly improving our documentation and working to better communicate how to use our components effectively.
With the new customization playgrounds, you can now tailor the style of [Date Picker](/x/react-date-pickers/date-picker/#customization) and experiment with multiple combinations of [sub-components](/x/react-date-pickers/playground/) to achieve the look and feel you desire.
## Data Grid
### Column Autosizing [<span class="plan-pro"></span>](/x/introduction/licensing/#pro-plan 'Pro plan')
The new autosizing feature automatically adjusts the column width to accommodate the content within.
You can include or exclude both headers and outliers from the calculation and expand to use the entire area of the grid.
Learn more details at [column autosizing section](/x/react-data-grid/column-dimensions/#autosizing).
<video preload="metadata" style="margin-bottom: 10px;" autoplay muted loop playsinline width="680" height="128">
<source src="/static/blog/mui-x-end-v6-features/column-auto-sizing.mp4" type="video/mp4">
</video>
### New examples
We're continuously improving our docs, and we're starting to add more advanced examples like [bulk editing](/x/react-data-grid/recipes-editing/#bulk-editing) and [lazy loading for tree data](/x/react-data-grid/tree-data/#children-lazy-loading).
### Sparkline as a column type
Based on `@mui/x-charts` package, you can now add sparkline columns to your Data Grid.
<img src="/static/blog/mui-x-end-v6-features/sparkline-datagrid.png" alt="Sparkline on data grid" width="658" height="305" style="margin-bottom: 16px;" />
For more details on sparkline and other custom columns, please visit the [documentation page](/x/react-data-grid/custom-columns/#sparkline).
### Performance improvements
In our pursuit to enhance user experience, one of the most significant changes in latest v6 versions are related to performance boosts on filtering and scrolling.
To illustrate some of these improvements, the following table display a benchmark comparing the latest v5 (v5.17.26) with v6.18.0. The focus is to assess the raw filtering speed in a use case involving a one-column string filter over 100,000 rows.
<table border="0" style="text-align:center;width:100%;display:table">
<tr>
<th>Version</th>
<th>N# of Tests</th>
<th>Min time (ms)</th>
<th>Max time (ms)</th>
<th>Median (ms)</th>
<th>Average (ms)</th>
<th>Deviation</th>
</tr>
<tr>
<td>v5.17.26</td>
<td>22</td>
<td>396</td>
<td>409</td>
<td>400</td>
<td>400.7</td>
<td>3.96</td>
</tr>
<tr>
<td>v6.18.0</td>
<td>20</td>
<td>44</td>
<td>66</td>
<td>49.5</td>
<td>50.4</td>
<td>5.63</td>
</tr>
</table>
As we can see, the current version operates 7.9 times faster; the average time has dropped from 400.7 milliseconds in the previous version to just 50.4 milliseconds in the current one.
:::info
Note that these results are based on raw filtering speed, and not end-to-end operation (which includes user typing, filtering and rerender).
:::
## What's next?
We're now working on the next MUI X major, v7, which will include many new features and improvements.
Most notably:
- DateTime and TimeRangePicker
- Improved accessibility on date and time fields
- New UI for column management for the [`DataGrid`](/x/react-data-grid/)
- Pivoting for the [`DataGridPremium`](/x/react-data-grid/#premium-plan)
For the new components, we will keep expanding our portfolio with new chart types such as [Heat map](/x/react-charts/heat-map/), [Funnel](/x/react-charts/funnel/), [Gantt](/x/react-charts/gantt/), and explore virtualization and other advanced use cases for Tree view.
We encourage you to upvote issues on GitHub to help us prioritize. Your input directly influences our development schedule, so don't hesitate to let us know what matters most to you!
You can use the following list for quick access to each components issues.
- [Charts](https://github.com/mui/mui-x/issues?q=is%3Aissue+is%3Aopen+label%3A%22component%3A+charts%22+label%3A%22waiting+for+%F0%9F%91%8D%22)
- [Tree View](https://github.com/mui/mui-x/issues?q=is%3Aissue+is%3Aopen+label%3A%22component%3A+treeview%22+label%3A%22waiting+for+%F0%9F%91%8D%22)
- [Data Grid](https://github.com/mui/mui-x/issues?q=is%3Aissue+is%3Aopen+label%3A%22component%3A+data+grid%22+label%3A%22waiting+for+%F0%9F%91%8D%22)
- [Date and Time pickers](https://github.com/mui/mui-x/issues?q=is%3Aissue+is%3Aopen+label%3A%22component%3A+pickers%22+label%3A%22waiting+for+%F0%9F%91%8D%22)
The next major release (v7) will be available through alpha and beta versions until March 2024, when it's planned for it to be officially promoted to the new stable version. At the same time, v6 will transition to [Long-Term Support](/versions/#long-term-support-lts), while support for v5 will be discontinued.
## Feedback
As usual, we are happy to hear from you and get your feedback, so if you'd like to share your pain points and use cases, please leave your contact info through [this Google Form](https://forms.gle/vsBv6CLPz9h57xg8A).
Naturally, you're welcome to request new features, report bugs, and join any discussion in MUI X [GitHub repository](https://github.com/mui/mui-x/issues); additionally, we're trying to establish a community in the [MUI Discord server](https://mui.com/r/discord/), and we'd love to see you there.
Cheers!
| 4,202 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-x-mid-v6-features.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './mui-x-mid-v6-features.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,203 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-x-mid-v6-features.md | ---
title: MUI X v6.11.0. A roundup of all new features
description: Support for time zones, Charts in alpha, Data Grid filtering, and more.
date: 2023-08-14T00:00:00.000Z
authors: ['richbustos', 'josefreitas']
card: false
tags: ['MUI X', 'News']
---
<a href="https://github.com/mui/mui-x/releases/tag/v6.11.0">
<img src="/static/blog/mui-x-mid-v6-features/intro.png" alt="open release page" width="1384" height="346" style="margin-bottom: 16px;" />
</a>
Since the first v6 stable release, we've continuously rolled out new major features.
Now that we've reached [MUI X v6.11.0](https://github.com/mui/mui-x/releases/tag/v6.11.0), it's time to delve into the most recent additions to MUI X v6, and why you should get the latest version now.
## Table of contents
- [Date Pickers](#date-pickers)
- [Support for time zones](#support-for-time-zones)
- [Digital clock](#digital-clock)
- [Data Grid](#data-grid)
- [Filter on column headers](#filter-on-column-headers) [<span class="plan-pro"></span>](/x/introduction/licensing/#pro-plan 'Pro plan')
- [Copy and paste](#copy-and-paste) [<span class="plan-premium"></span>](/x/introduction/licensing/#premium-plan 'premium plan')
- [Charts - alpha version](#charts-alpha-version)
- [Tree View is moving to MUI X](#tree-view-is-moving-to-mui-x)
- [Feedback](#feedback)
## Date Pickers
### Support for time zones
No more hassle displaying dates in the time zones of your choice. 🌎
You can effortlessly display and select dates and times in different time zones, without worrying about conversion logic or maintaining consistency with your backend.
<video preload="metadata" style="margin-bottom: 16px;" autoplay muted loop>
<source src="/static/blog/mui-x-mid-v6-features/timezone.mp4" type="video/mp4">
</video>
Set the `timezone` prop to define which time zone the Date, Time, or DateTime should be displayed in.
```tsx
<TimePicker
value={value}
onChange={setValue}
timezone="Pacific/Honolulu" // Can be in any timezone of your choice
label={'Rendered in "Pacific/Honolulu"'}
/>
```
Check the [full instructions](https://mui.com/x/react-date-pickers/timezone/) for more information on using this feature in your application.
### Digital clock
The digital clock is an alternative to the Time Pickers' [analog clock](https://mui.com/x/react-date-pickers/time-clock/).
The original proposal was mainly focused on mobile devices, whereas the new interface is designed for a desktop experience for better time precision.
This new addition makes our Date Pickers even more versatile and user-friendly than before.
It's available as the default variant for desktops on both the [Time Picker](https://mui.com/x/react-date-pickers/time-picker/) and the [Date Time Picker](https://mui.com/x/react-date-pickers/date-time-picker/).
<video preload="metadata" style="margin-bottom: 16px;" autoplay muted loop>
<source src="/static/blog/mui-x-mid-v6-features/digital_clock.mov" type="video/mp4">
</video>
Check out all the possibilities in the [Date Pickers—Digital clock documentation](https://mui.com/x/react-date-pickers/digital-clock/), and let us know your thoughts!
## Data Grid
### Filter on column headers [<span class="plan-pro"></span>](/x/introduction/licensing/#pro-plan 'Pro plan')
Filtering on column headers gives users the ability to quickly filter data without any additional menu.
Use the the `unstable_headerFilters` prop to activate this feature.
The new filter fields are displayed below the headers, and are synchronized with the filter panel.
If you prefer more simplicity, you can disable the default filter panel using the `disableColumnFilter` prop, and set filters to use only the default operator.
<video preload="metadata" style="margin-bottom: 16px;" autoplay muted loop playsinline>
<source src="/static/blog/mui-x-mid-v6-features/header_filter.mp4" type="video/mp4">
</video>
For more details on how to use and customize the filters, check out its [documentation page](https://mui.com/x/react-data-grid/filtering/header-filters/).
### Copy and paste [<span class="plan-premium"></span>](/x/introduction/licensing/#premium-plan 'premium plan')
After setting the `experimentalFeatures={{ clipboardPaste: true }}` prop, you can copy and paste data directly to and from your Data Grid.
This new feature is extremely versatile, and you can exchange data from other fields, other grids, and even directly to and from the spreadsheet tool of your choice.
<video preload="metadata" style="margin-bottom: 16px;" autoplay muted loop playsinline>
<source src="/static/blog/mui-x-mid-v6-features/copy_paste.mov" type="video/mp4">
</video>
This feature is integrated with the editing API, so pasted data can be persisted using the `processRowUpdate` prop to update your data source through your usual editing validation process.
The callbacks `clipboardPasteStart` and `clipboardPasteEnd` are fired during the clipboard paste operation, which can be useful for extra customizations around the event.
For more details on how to use clipboard copy and paste, check out the [Data Grid—Clipboard documentation](https://mui.com/x/react-data-grid/clipboard/).
## Charts - alpha version
We are delighted to announce the upcoming expansion of MUI X: a brand-new suite of components for building and customizing charts.
With MUI X Charts, you can choose from a wide range of chart types, including line charts, bar charts, pie charts, area charts, scatter plots, and more.
Each chart type is thoughtfully crafted with attention to detail, ensuring that the visual representations are not only aesthetically pleasing, but also highly effective in conveying complex data.
And it ships with gorgeous palettes that were specially crafted by our designers!
Check out the video below, highlighting some of our Charts:
<video preload="metadata" style="margin-bottom: 16px;" autoplay muted loop playsinline>
<source src="/static/blog/mui-x-mid-v6-features/charts_final_v1.mov" type="video/mp4">
</video>
As we progress toward the stable version, we're committed to enhancing the overall experience for developers and users, so your feedback is fundamental!
We will also steadily expand our portfolio with new chart types such as [Heat map](https://mui.com/x/react-charts/heat-map/), [Funnel](https://mui.com/x/react-charts/funnel/), [Gantt](https://mui.com/x/react-charts/gantt/), and more.
If there's a specific chart visualization you'd like us to prioritize, we encourage you to upvote the respective [issue on GitHub](https://github.com/mui/mui-x/issues?q=is%3Aissue+is%3Aopen+label%3A%22component%3A+charts%22+label%3A%22waiting+for+%F0%9F%91%8D%22).
Your input can directly influence our development schedule, so don't hesitate to let us know what matters most to you!
[Get started with charts now!](https://mui.com/x/react-charts/)
## Tree View is moving to MUI X
Tree View is being migrated from the [lab](https://mui.com/material-ui/about-the-lab/) to MUI X, it will soon have a first Alpha release!
The Tree View is a component that represents hierarchical in a tree-like format.
Think of a file system navigator displaying folders and files or a navigation list.
<video preload="metadata" style="margin-bottom: 16px;" autoplay muted loop playsinline>
<source src="/static/blog/mui-x-mid-v6-features/treeview.mov" type="video/mp4">
</video>
Keep on the look out on our next blog for the Tree View migration.
We decided to migrate this component to MUI X as there are still many features that would be great to build (e.g. checkbox, drag & drop, virtualization) and it's usually not a significant component of a design system.
Head to [MUI Core vs. MUI X](https://mui-org.notion.site/X-FAQ-c33e9a7eabba4da1ad7f8c04f99044cc) if you would like to learn more about this decision.
## Feedback
We are always happy to get feedback, so if you'd like to share your pain points and use cases, please leave your contact info with us through [this Google Form](https://forms.gle/vsBv6CLPz9h57xg8A).
As usual, you're welcome to request new features, report bugs and join the discussion in MUI X [GitHub repository](https://github.com/mui/mui-x/issues).
If you haven't yet, join our growing community in the recently launched [MUI Discord server](https://mui.com/r/discord/).
Cheers!
| 4,204 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-x-v5.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './mui-x-v5.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,205 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-x-v5.md | ---
title: Introducing MUI X v5
description: We are excited to introduce MUI X v5.0.0!
date: 2021-11-22T00:00:00.000Z
authors:
['oliviertassinari', 'm4theushw', 'flaviendelangle', 'DanailH', 'alexfauquette']
card: true
tags: ['News']
---
We are excited to introduce [MUI X v5.0.0](https://github.com/mui/mui-x/releases/tag/v5.0.0)!
[MUI X](/x/) is our collection of advanced components (with both MIT and commercially licensed "Pro" features).
Currently, it only includes a data grid.
Soon it will include more components like date picker and tree view.
This release continues our focus on making the data grid the best in the industry.
Read on to learn more!
<img src="/static/blog/mui-x-v5/card.png" alt="" style="width: 100%; margin-bottom: 16px;" />
This release features some major highlights:
- [High-level goals for v5](#a-new-virtualization-engine)
- [A new virtualization engine](#a-new-virtualization-engine)
- [Improved state management](#improved-state-management)
- [Improved DX when using the state](#improved-dx-when-using-the-state)
- [Synchronous state initialization](#synchronous-state-initialization)
- [Simplified style customization](#simplified-style-customization)
- [Limitations](#limitations)
- [v4 migration](#v4-migration)
- [What's next?](#whats-next)
- [Public roadmap](#public-roadmap)
- [Thank you](#thank-you)
## High-level goals for v5
MUI develops different React components in two products: [MUI Core](/core/) and [MUI X](/x/).
This approach recognizes that the problems solved by the components in these two products are different.
The paths to success require different strategies.
Many of the developers using MUI X also use MUI Core, these users care a lot about consistency (design, docs, dependencies, etc.).
With the [release of MUI Core v5](/blog/mui-core-v5/) two months ago MUI X had to work on providing a cohesive experience.
The primary objective of this new major is to have MUI X provide a great **compatibility with MUI Core v5**.
## A new virtualization engine
`DataGrid` and `DataGridPro` now feature a brand-new virtualization engine!
We decided to rewrite it to address the many issues raised by the community and to make it easier to release new features that impact the rendering of rows and columns.
An advantage over the previous version is that we now use the native scroll.
This means that scrolling the grid is like scrolling a webpage,
so any jittering caused when the scroll is overridden is gone.
Talking about performance, one of the main problems we had was that scrolling horizontally was laggy compared to vertical scrolling.
After investigation we found that, although the columns were virtualized, a lot of unnecessary renders were occurring.
This can be seen in the top part of the screenshot below, where it compares `v5.0.0-beta.4` (the last version before the new virtualization engine) with `v5.0.0`.
On each scroll event it renders again, and each frame takes a long time to be drawn (some are even lost).
To address these problems, we took the following actions:
- Avoid rendering the entire grid during scroll.
- Pass the correct value to the `key` prop to ensure that React will reuse the existing DOM nodes.
- Reduced the number of event listeners attached to each cell.
- Increased the number of columns rendered in the overscan (the extra columns rendered to make scroll smoother).
- Delay the rendering of new columns whenever possible.
The result of these changes is shown in the bottom part of the comparison.
The number of frames that could be drawn in the same amount of time dramatically increased, compared to the previous virtualization approach.
In our [benchmark](https://github.com/mui/mui-x/pull/2673), the FPS (frames per second) went from 22 to 42, on average.
The time each frame takes to be rendered, indicated by the width of each block, was reduced.
The idea of delaying the re-rendering also can be seen in the large voids between the blocks.
Each void means that a re-render was not necessary since the required columns were already rendered by the overscan.
Some of the mentioned improvements were also applied to the rows, however the gains were more subtle.
Besides the better performance, the new virtualization engine also brings the following fixes:
- Horizontal and vertical scroll share the same logic.
- No more jumps when changing the rendered rows.
- Calling `apiRef.current.scrollToIndexes` works no matter where the cell is.
- Improved support for when `disableVirtualization` is used.
- Fixes keyboard navigation with arrow keys.
## Improved state management
Several enhancements were made to state management to improve developer experience, performance and consistency in the execution order.
### Improved DX when using the state
We have worked on simplifying the state structure and the tools to access it.
These changes improved the developer experience when using the `apiRef` methods:
- We removed the `state` structure from the public API. Access to data in the state should always be done through `apiRef` methods (`apiRef.current.getSelectedRows`) or selectors (`selectedGridRowsSelector`).
- We renamed most selectors to have a consistent naming convention, making it easier to deduce their name or infer purpose.
- We restructured our state so that each feature has a single sub-state, and the feature hook is the only one to update it (e.g. `state.filter` is only managed by the `useGridFilter` hook, which exposes methods for both internal and 3rd party code to interact with this state).
The work on this topic isn't over. We have several developments in progress or under discussion to improve the developer experience when using the advanced features of the grid.
Here are a few that should be release in the following months:
- Strict typing of event listeners and publishers.
- Examples for the event listeners.
- Documentation and examples for selectors.
- Add the ability to export and restore some parts of the grid state.
### Synchronous state initialization
In previous versions, the state was first populated with default values, and then in a `useEffect`, given the values provided as props (`props.pageSize` for instance), or derived from the props (the sorted and filtered rows derived from the `props.rows`, `props.sortModel` and `props.filterModel`).
This was causing an additional render with useless data, and then we had to be careful to avoid flickering between the fake and real data.
In v5, the state is initialized synchronously during the first render.
Note that for now, the state updates coming from controlled props are still asynchronous.
If you pass `props.pageSize`, we will apply it to the state in a `useEffect`, and therefore if you read the state just after the render (for instance in a `useLayoutEffect`), you will still see the old version.
## Simplified style customization
In previous versions, most of the built-in CSS of the `DataGrid` and `DataGridPro` components had a [CSS specificity](https://web.dev/learn/css/specificity/) of 2.
This means that the CSS you would normally add would have less priority than the built-in CSS of the data grid.
This was requiring you to open your dev tools, look at the DOM/CSSOM tree in order to use the correct CSS selector.
With MUI X v5 we have reduced the CSS specificity of most of the internal `DataGrid` and `DataGridPro` components to 1.
This enables developers to more easily change the look and feel of the grid's components.
**Before**
```jsx
const GridToolbarContainerStyled = styled(GridToolbarContainer)({
'&.MuiDataGrid-toolbarContainer': {
padding: 40,
},
});
function MyCustomToolbar() {
return (
<GridToolbarContainerStyled>My custom toolbar</GridToolbarContainerStyled>
);
}
export default function App() {
return (
<div style={{ height: 400, width: '100%' }}>
<DataGrid components={{ Toolbar: MyCustomToolbar }} />
</div>
);
}
```
**After**
```jsx
const GridToolbarContainerStyled = styled(GridToolbarContainer)({
padding: 40,
});
function MyCustomToolbar() {
return (
<GridToolbarContainerStyled>
My custom toolbar
</GridToolbarContainer>
);
};
export default function App() {
return (
<div style={{ height: 400, width: '100%' }}>
<DataGrid components={{ Toolbar: MyCustomToolbar }} />
</div>
);
}
```
Another way to customize this will be to use the `sx` prop.
```jsx
function MyCustomToolbar() {
// means "padding: theme.spacing(5)", NOT "5px"
return (
<GridToolbarContainer sx={{ p: 5 }}>My custom toolbar</GridToolbarContainer>
);
}
export default function App() {
return (
<div style={{ height: 400, width: '100%' }}>
<DataGrid components={{ Toolbar: MyCustomToolbar }} />
</div>
);
}
```
### Limitations
Although this was a clear improvement, we still had to keep a CSS specificity of 2 for some parts of the `DataGrid` and `DataGridPro`, specifically the `GridColumnHeaderItem`, `GridRow` and `GridCell` along with all of the components that are nested in them.
This is due to performance implications related to how [emotion](https://emotion.sh/) injects styles into the page,
and was necessary to keep the performance of our virtualization engine at its optimal.
## v4 migration
We strongly recommend you migrate MUI X to v5.
In MUI X v5 we have not only added additional features but also made significant internal improvements and performance optimizations that won't be included in v4.
All-new `DataGrid` and `DataGridPro` features will be only available in MUI X v5.
Please check [the v4 migration guide](/x/migration/migration-data-grid-v4/) to accelerate the transition.
## What's next?
More exciting things are coming! We have big plans for the rest of this quarter in terms of features we expect to release in both the `DataGrid` and `DataGridPro` components.
Features such as **[tree data](/x/react-data-grid/tree-data/)**, **[column pinning](/x/react-data-grid/column-pinning/)**, and **[variable row height](https://github.com/mui/mui-x/issues/438)** are part of our roadmap.
### Public roadmap
As a general rule, the data grid is the cornerstone of any application manipulating large amounts of data.
We plan to focus on it as long as necessary to deliver most of the advanced features.
Once we would have grown the team and made enough progress, we will expand to more components.
You can view our [public roadmap](https://github.com/mui/mui-x/projects/1) on GitHub to learn about what features we're working on, what stage they're at, and when we expect to bring them to you.
## Thank you
Finally, one last thank you to everyone who's contributed to MUI X v5.
We're very excited about this release, and we'll continue to push forward and deliver the next generation of Enterprise React UI components!
It's just the beginning.
| 4,206 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-x-v6-alpha-zero.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './mui-x-v6-alpha-zero.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,207 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-x-v6-alpha-zero.md | ---
title: A major update is coming for MUI X—and you can get involved
description: Let us know what you want to see in MUI X v6 as we begin the alpha phase of development.
date: 2022-09-30T00:00:00.000Z
authors: ['josefreitas']
tags: ['MUI X', 'News']
---
We're kicking off the development of [MUI X v6](https://github.com/mui/mui-x/releases/tag/v6.0.0-alpha.0).
Both the Data Grid and the Date and Time Pickers will get a new major version.
We want to share our plans and invite you to join us on this next step.
:::warning
It's important to note that only MUI X is getting a new version—MUI Core (including Material UI) will remain in v5 for now.
You can rest assured that all MUI X v6 components will be fully compatible with MUI Core v5.
::::
## What's the plan to get to a stable release?
Before officially releasing v6, we'll go through a few months with pre-releases.
We'll follow the current weekly release process and [semver versioning](https://semver.org/); the difference now is that instead of v5, we'll ship v6 pre-release packages.
First, in the alpha phase, we'll introduce all the breaking changes planned for this major.
We'll be exploring a bit, so it's expected that some APIs will be unstable—not in terms of functionality, but we may need to rename or adjust parameters.
This phase is planned to take about two months.
Next comes the beta phase, where the APIs will be more stable, and we'll focus on fixing bugs and polishing the hard edges.
This phase is planned to take about one month.
:::info
Disclaimer: This timeline—2 months in alpha, 1 month in beta—is purely for reference.
We operate in a dynamic environment that's subject to change, and the actual timeline could vary.
We may need to do more iterations in the interest of delivering the best possible product.
:::
Finally, we'll release the first `v6.0.0` stable, and we'll continue improving the components and adding features, but without making any new breaking changes until the next major version.
We hope to reach the stable release by the end of 2022.
We're establishing a one-year cycle for major versions, meaning the next major will arrive about one year after this release.
## What happens to v5?
During v6 pre-releases, v5 will continue to be the official current major, and it will remain supported during this time.
However, we will only release new v5 versions as needed to patch bugs or add community contributions.
All new features and enhancements will go to v6, and after its first stable release, v5 will officially transition to [long-term support](https://mui.com/versions/#long-term-support-lts) status.
## Where's the v6 documentation?
As mentioned above, v5 is still the official version, so by default, the documentation shows v5 features and API.
The next version's documentation is in the `next` subdomain.
- [https://next.mui.com/x/react-data-grid/](https://next.mui.com/x/react-data-grid/)
- [https://next.mui.com/x/react-date-pickers/](https://next.mui.com/x/react-date-pickers/)
## What's coming next?
The following is a list of enhancements in the pipeline for v6.
It contains the highlights that will be included in the first versions.
### Data Grid
- **Extended customization abilities**.\
We want to empower more users to employ the Data Grid for complex use cases.
- [ApiRef in the community package](https://github.com/mui/mui-x/issues/6147).
- [Filtering on header](https://github.com/mui/mui-x/issues/6247).
- [Use the Data Grid internal components outside the grid](https://github.com/mui/mui-x/issues/2522).
- **Improved look & feel**\
We're polishing edges in terms of design and usability.
- [New column menu](https://github.com/mui/mui-x/issues/4929).
- [New column visibility panel](https://github.com/mui/mui-x/issues/5700).
- [Column resize bar only on hover](https://github.com/mui/mui-x/issues/1623).
- **Rockstar feature**
- [Copy and paste from/to multiple cells](https://github.com/mui/mui-x/issues/199).
### Date and Time Pickers
- **Improved UX**\
In the previous version we focused on developer experience and overall stability of the components.
Now we're tackling ways to improve usability.
- [Remove the clock view on time pickers (for desktop)](https://github.com/mui/mui-x/issues/4483).
- [Visually edit a range by dragging date markers](https://github.com/mui/mui-x/issues/5311).
- [Range shortcuts](https://github.com/mui/mui-x/issues/4563).
- [A new text input for date and time values, retiring the mask solution (early preview)](https://next.mui.com/x/react-date-pickers/date-field/).
- **Improved Customization**\
v6 will be packed with new customization abilities and support for new use cases.
- [The new fields are based on a headless approach with custom hooks. (Documentation is coming soon)](https://next.mui.com/x/react-date-pickers/date-field/#headless-usage).
- [Single Input for Date Range](https://github.com/mui/mui-x/issues/5193).
- [Enable customization through component slots on every component](https://github.com/mui/mui-x/issues/4466).
:::info
You can check our [roadmap](https://github.com/mui/mui-x/projects/1) for the full live list.
:::
## How to migrate?
We've prepared a [migration guide](https://deploy-preview-6235--material-ui-x.netlify.app/x/react-data-grid/migration-v5/), and we'll continuously update it as we make any breaking changes during the pre-releases.
It lists every update you need to make to your code to use the most recent packages.
We highly encourage you to try the new version.
It is, after all, an improvement over the solid foundation we established with v5.
## How to get involved?
Please consider joining our alpha testers group channel and [connecting with us](https://forms.gle/vsBv6CLPz9h57xg8A) for a user interview.
You'll get an insider's perspective on the development, and you'll be able to help us iterate early on the new features.
As always, we're happy to get your feedback.
You can participate in the discussion by commenting on new features or reporting bugs in our [GitHub repository](https://github.com/mui/mui-x/issues/new/choose).
Finally, you can follow every step of the development through our [changelog](https://github.com/mui/mui-x/releases).
| 4,208 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-x-v6.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './mui-x-v6.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,209 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-x-v6.md | ---
title: Introducing MUI X v6
description: Introducing the new major version of the advanced components.
date: 2023-03-06T00:00:00.000Z
authors: ['josefreitas']
card: true
tags: ['MUI X', 'News']
---
<img src="/static/blog/mui-x-v6/card.png" alt="" style="margin-bottom: 16px;" width="2400" height="559" />
[MUI X v6.0.0](https://github.com/mui/mui-x/releases/tag/v6.0.0) is finally here with many improvements, new features, customization abilities, and a more robust foundation to accommodate the changes we want to deliver next.
## Table of contents
- [Data Grid - feature highlights ✨](#data-grid-features-highlights-✨)
- [ApiRef moved to the MIT (Community) version](#apiref-moved-to-the-mit-community-version)
- [Improved column menu](#improved-column-menu)
- [Row pinning is now stable](#row-pinning-is-now-stable) [<span class="plan-pro"></span>](/x/introduction/licensing/#pro-plan 'Pro plan')
- [Aggregation is now stable](#aggregation-is-now-stable) <a title="Premium plan" href="/x/introduction/licensing/#premium-plan"><span class="plan-premim"></span></a>
- [Cell selection](#cell-selection) <a title="Premium plan" href="/x/introduction/licensing/#premium-plan"><span class="plan-premim"></span></a>
- [Use web workers to export data to excel files](#use-web-workers-to-export-data-to-excel-files) <a title="Premium plan" href="/x/introduction/licensing/#premium-plan"><span class="plan-premim"></span></a>
- [Date and Time Pickers - feature highlights ✨](#date-and-time-pickers-features-highlights-✨)
- [Fields: the new default \<input\> for pickers](#fields-the-new-default-input-gt-for-pickers)
- [Improved layout customization](#improved-layout-customization)
- [Overhaul in the documentation](#overhaul-in-the-documentation)
- [Removed clock view on desktop Time Pickers](#removed-clock-view-on-desktop-time-pickers)
- [Shortcuts for picking specific dates in a calendar](#shortcuts-for-picking-specific-dates-in-a-calendar) [<span class="plan-pro"></span>](/x/introduction/licensing/#pro-plan 'Pro plan')
- [Edit date ranges with drag and drop](#edit-date-ranges-with-drag-and-drop) [<span class="plan-pro"></span>](/x/introduction/licensing/#pro-plan 'Pro plan')
- [Installation and migration](#installation-and-migration)
- [What's next](#whats-next)
- [Decoupling versions from MUI Core](#decoupling-versions-from-mui-core)
- [Feedback](#feedback)
## Data Grid - features highlights ✨
### ApiRef moved to the MIT (Community) version
Manage pagination, scrolling, state, and other attributes through the Data Grid's API object—previously only in commercial plans, now available to all users.
The `apiRef` enables developers to implement a whole new range of customizations that rely on programmatic control of the Grid's features.
```tsx
function CustomDataGrid(props) {
const apiRef = useGridApiRef();
return (
<div>
<Button onClick={() => apiRef.current.setPage(0)}>
Go to page first page
</Button>
<DataGrid apiRef={apiRef} {...other} />
</div>
);
}
```
See the [apiRef reference documentation](/x/react-data-grid/api-object/) for more details.
This is the first feature we ever move from the Pro plan to be MIT licensed.
We identified that this feature in the Pro plan was going against our objectives.
Our goal is for MUI X data grid to become the best grid for React developers, when compared to other standalone open-source grid.
To do such, developers need to have access to all the primitives required to customize it.
And if you want to understand more about our view of the open-source/commercial balance, check our [Stewardship page](https://mui-org.notion.site/Stewardship-542a2226043d4f4a96dfb429d16cf5bd).
### Improved column menu
Another significant step in terms of customization but also usability; the v6 [column menu](/x/react-data-grid/column-menu/) now provides support for icons, menu groups, custom items and actions, and more.
We've redesigned this sub-component to make it as extensible as possible.
<a href="/x/react-data-grid/column-menu/">
<img src="/static/blog/mui-x-v6/column-menu-custom-action.png" loading="lazy" alt="Column menu custom action" width="1636" height="808" />
</a>
<p class="blog-description">A demo of the column menu when open and with one item hovered.</p>
This improvement is part of an overarching effort throughout the life cycle of v6 to refactor all Data Grid panels.
### Row pinning is now stable [<span class="plan-pro"></span>](/x/introduction/licensing/#pro-plan 'Pro plan')
[Row pinning](/x/react-data-grid/row-pinning/) was previously released in a minor v5 version under the `experimentalFeatures={{ rowPinning: true }}` flag.
The API is now stable, thanks to the community for trying it out and reporting bugs.
<a href="/x/react-data-grid/row-pinning/">
<img src="/static/blog/mui-x-v6/row-pinning.png" style="width: 655px" loading="lazy" alt="Column menu custom action" width="1310" height="828" />
</a>
### Aggregation is now stable <a title="Premium plan" href="/x/introduction/licensing/#premium-plan"><span class="plan-premim"></span></a>
[Aggregation](/x/react-data-grid/aggregation/) was previously released in a minor v5 version under the `experimentalFeatures={{ aggregation: true }}` flag.
The API is now stable, thanks to the community for trying it out and reporting bugs.
<a href="/x/react-data-grid/aggregation/">
<img src="/static/blog/mui-x-v6/aggregation.png" style="width: 474px" loading="lazy" alt="Column menu custom action" width="948" height="964" />
</a>
<p class="blog-description">The footer of the second column is a sum all its cells.</p>
### Cell selection <a title="Premium plan" href="/x/introduction/licensing/#premium-plan"><span class="plan-premim"></span></a>
[Cell selection](/x/react-data-grid/cell-selection/) is a powerful and flexible way to select data in the Data Grid.
It allows end-users to select a cell or group of cells like in an Excel sheet.
<a href="/x/react-data-grid/cell-selection/">
<video autoplay muted loop playsinline width="1660" height="918">
<source src="/static/blog/mui-x-v6/cell-selection.mp4" type="video/mp4" />
</video>
</a>
<p class="blog-description">A demo of the cell selection.</p>
This feature will serve as the base for clipboard importing / bulk editing ([coming soon](https://github.com/mui/mui-x/issues/199)).
The API is unstable in this first release but you can enable it with:
```jsx
<DataGridPremium unstable_cellSelection />
```
### Use web workers to export data to excel files <a title="Premium plan" href="/x/introduction/licensing/#premium-plan"><span class="plan-premim"></span></a>
By default, the Excel file export is generated in the main thread. This can freeze the UI when exporting large datasets.
You can now [use a web worker](/x/react-data-grid/export/#using-a-web-worker) in the background to allow interactions with the grid while the data is exported.
## Date and Time Pickers - features highlights ✨
### Fields: the new default \<input\> for Pickers
#### Legacy mask input
In MUI X v5, the `<input>` behavior of the pickers components were implemented with a [mask approach](https://www.npmjs.com/package/rifm).
This had many UX downsides. for example, watch what happens when we edit the day on this masked input, you lose the year:
<a href="https://v5.mui.com/x/react-date-pickers/date-picker/#basic-usage">
<video style="width: 399px;" autoplay muted loop playsinline width="1268" height="540">
<source src="/static/blog/mui-x-v6/mask.mp4" type="video/mp4" />
</video>
</a>
<p class="blog-description">A demo of the date pickers on <a href="https://v5.mui.com/x/react-date-pickers/date-picker/#basic-usage">MUI X v5</a>.</p>
#### New "Fields"
This mask logic is now gone. ["Fields"](/x/react-date-pickers/fields/) implement the new rich text fields that solve the mask input limitations.
They are specialized for date and time logic and offer quick navigation and isolated interaction within each section of a date value.
See it in action:
<a href="/x/react-date-pickers/fields/">
<video style="width: 608px;" autoplay muted loop playsinline width="1216" height="310">
<source src="/static/blog/v6-beta-pickers/date-field-navigation.mp4" type="video/mp4" />
</video>
</a>
This design is heavily inspired by the [native date picker](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date) UIs provided by platforms like macOS and Windows on the web.
### Birthday picker
Up until MUI X v5, we were recommending the use of 3 separate inputs to implement a birthday picker, and especially not the use of a `<DatePicker>`; see this article for why [Designing Birthday Picker UX: Simpler Is Better](https://www.smashingmagazine.com/2021/05/frustrating-design-patterns-birthday-picker/).
Birthday pickers can now have a great UX thanks to the Fields.
They behave almost like 3 separate inputs and support full letter month which can be used so end-users don't confuse day and month.
<a href="https://mui.com/x/react-date-pickers/date-field/#customize-the-date-format">
<img src="/static/blog/mui-x-v6/birthday.png" style="width: 446px" loading="lazy" alt="Column menu custom action" width="892" height="182" />
</a>
### Standalone
The Fields are included in all the pickers, but they're also available as standalone improved version of a `<TextField>`:
```jsx
import { DateField } from '@mui/x-date-pickers/DateField';
<DateField label="My first field" />;
```
### Improved layout customization
Combining the slots concept with the grid layout, you can now rearrange, extend, and customize most of the sub-components used in the Pickers UI.
See [the documentation about it](/x/react-date-pickers/custom-layout/) and this quick overview:
```tsx
function MyCustomLayout(props) {
const { toolbar, tabs, content, actionBar } = usePickerLayout(props);
return (
<PickersLayoutRoot className={pickersLayout.root} ownerState={props}>
{toolbar}
{actionBar}
<PickersLayoutContentWrapper className={pickersLayout.contentWrapper}>
{tabs}
{content}
</PickersLayoutContentWrapper>
</PickersLayoutRoot>
);
}
export default function CustomStaticDatePicker() {
return <StaticDatePicker slots={{ layout: MyCustomLayout }} />;
}
```
### Overhaul in the documentation
[The Date and Time Pickers documentation](/x/react-date-pickers/) has drastically improved during pre-release, and it now features a more comprehensible navigation structure and many new examples.
### Removed clock view on desktop Time Pickers
Many end-users complained, and we completely agree, the [clock view](/x/react-date-pickers/time-clock/) is not the ideal time-picking experience on Desktop, so we removed it as a default view.
<img src="/static/blog/mui-x-v6/clock.png" loading="lazy" alt="Date Range shortcuts." width="518" height="496" style="width: 259px; margin-bottom: 24px;" />
<p class="blog-description">The clock picker, still present on mobile.</p>
You can still use the Clock if you like to, but [a replacement UI](https://github.com/mui/mui-x/issues/4483) for the time picker is coming shortly after this release.
### Shortcuts for picking specific dates in a calendar [<span class="plan-pro"></span>](/x/introduction/licensing/#pro-plan 'Pro plan')
You can now [add quick and customizable shortcuts](/x/react-date-pickers/shortcuts/) for your end-users.
While shortcuts are an MIT licensed, it's particularly useful for date range pickers.
You can display them on the left, right, bottom, or top.
<a href="/x/react-date-pickers/shortcuts/">
<img src="/static/blog/v6-beta-pickers/date-range-shortcuts.png" loading="lazy" alt="Date Range shortcuts." width="2222" height="1402" />
</a>
<p class="blog-description">A demo of a Pro plan date range picker with shortcuts on the left.</p>
### Edit date ranges with drag and drop [<span class="plan-pro"></span>](/x/introduction/licensing/#pro-plan 'Pro plan')
[Editing a date range](/x/react-date-pickers/date-range-calendar/) is even easier now with the new drag-and-drop interaction.
End-users can more easily change the start and end dates.
<a href="/x/react-date-pickers/date-range-calendar/">
<video autoplay muted loop playsinline width="1488" height="796">
<source src="/static/blog/v6-beta-pickers/edit-drag.mp4" type="video/mp4" />
</video>
</a>
## Installation and migration
If this is your first try with MUI X, you can jump in the getting started section:
- [Data Grid](/x/react-data-grid/getting-started/)
- [Date Pickers](/x/react-date-pickers/getting-started/)
If you're coming from previous versions, we recommend you check our migration guide from MUI X v5 with the complete list of breaking changes:
- [Data Grid](/x/migration/migration-data-grid-v5/)
- [Date Pickers](/x/migration/migration-pickers-v5/)
We also provide codemods to automate some of the necessary updates in your codebase.
```bash
npx @mui/x-codemod v6.0.0/preset-safe <path>
```
## What's next?
We operate in a continuous-delivery environment, so the plan is to keep rolling out new features in minor versions.
With the new base established in v6.0.0, we'll continue our efforts to improve UI/UX, bring more customization abilities, and support new use cases.
Here's a list of what you can expect to be delivered in the following months (what is next on our immediate roadmap).
### Data Grid
- Clipboard importing ([mui-x#199](https://github.com/mui/mui-x/issues/199))
- Filtering on header ([mui-x#6247](https://github.com/mui/mui-x/issues/6247))
- Row spanning ([mui-x#207](https://github.com/mui/mui-x/issues/207))
- Improved column management panel (column visibility, reordering, grouping, pinning, etc.) ([mui-x#5700](https://github.com/mui/mui-x/issues/5700))
- Improved filter panel ([mui-x#6419](https://github.com/mui/mui-x/issues/6419))
- Support for Joy UI
### Date Pickers
- Time Picker replacement for the clock on desktop ([mui-x#4483](https://github.com/mui/mui-x/issues/4483))
- Time Range Picker ([mui-x#4460](https://github.com/mui/mui-x/issues/4460))
- Date Time Range Picker ([mui-x#4547](https://github.com/mui/mui-x/issues/4547))
- Ability to select a month range in the Date Range Picker ([mui-x#4995](https://github.com/mui/mui-x/issues/4995))
- Support for Joy UI
### Charts 📊
- Preview of chart components 🔥 ([mui-x#1408](https://github.com/mui/mui-x/issues/1408))
You can get more details of our next steps in [MUI X public roadmap](https://github.com/mui/mui-x/projects/1).
## Decoupling versions from MUI Core
We have decoupled MUI X's versioning from MUI Core (including `@mui/material`: Material UI). We understand that this may cause confusion, so we'd like to explain the main reasons why we're moving in this direction:
1. Soften migration pains with a yearly release cycle.\
The MUI X codebase is dynamic, and the constant development of new features often requires a faster breaking changes pace than MUI Core. With a yearly release, we aim to deliver those in smaller, more digestible sizes, in a time window that you can rely on to make your plans and prepare for updates.
2. We aim to support not only Material UI but also Joy UI and, in the future, Base UI.
## Feedback
We appreciate all of your feedback throughout the development of this new version. It's been vital for our process and always will be, so please continue to share your thoughts as we work through our next steps.
We're continuously doing user interviews, so if you'd like to share your pain points and use cases, please [leave your contact](https://forms.gle/vsBv6CLPz9h57xg8A) info.
As usual, you're welcome to join the discussion by requesting or commenting on new features, or reporting bugs in our [GitHub repository](https://github.com/mui/mui-x/issues/new/choose).
Cheers!
| 4,210 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/november-2019-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './november-2019-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,211 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/november-2019-update.md | ---
title: November 2019 Update
description: Here are the most significant improvements in November.
date: 2019-12-12T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
Here are the most significant improvements in November:
- 🔍 We have polished the newly introduced Autocomplete component (October).
We have handled more than [100 related issues](https://github.com/mui/material-ui/issues?utf8=%E2%9C%93&q=label%3A%22lab%3A+Autocomplete%22+) in a single month.
- 👤 We have improved the Avatar's loading experience ([#1871](https://github.com/mui/material-ui/pull/18711)).
<p class="blog-description">Before</p>
<p class="blog-description">After</p>
- 🌎 We have introduced [localization](/material-ui/guides/localization/) support.
The framework supports [13 locales](/material-ui/guides/localization/#supported-locales), and growing. We would love to see your translation contribution ✨.
- 👨🎤 We have added Framer X support ([#17797](https://github.com/mui/material-ui/pull/17797)) (and now looking into Sketch, Figma and Adobe XD).
<img src="/static/blog/november-2019-update/framer.jpg" alt="Framer X" width="300" />
- ⚛️ We have completed the migration of the demos to TypeScript. A big thanks to all the contributors that participated in [this effort](https://github.com/mui/material-ui/issues/14897). Around 10% of the audience on the documentation uses this version of the demos and growing.
- 🏷 We have added arrow and [hysteresis](https://github.com/mui/material-ui/pull/18458) support to the Tooltip.
But this summary is just scratching the surface. We have accepted 200 commits from 73 different contributors. We have changed 1,142 files with 27,923 additions and 13,852 deletions.
## Our roadmap intent for December
_(We'll do our best, no guarantee!)_
We have three major efforts undergoing, we will likely need a couple of months to make significant progress. Stay tuned.
- 📅 We continue to work on a [major upgrade](https://github.com/mui/material-ui-pickers/issues/1293) of the date/time picker components.
- 🧮 We continue to work on a data grid component.
This is an effort [of our roadmap](/material-ui/discover-more/roadmap/) to better answer enterprise needs.
The most advanced features will use a non-MIT license.
To get a rough idea of what's coming, you can read [this blog post](https://uxdesign.cc/design-better-data-tables-4ecc99d23356).
- 💅 We might initiate an update of our styling solution.
We want to cover styled-component [#6115](https://github.com/mui/material-ui/pull/#6115), the system [#15561](https://github.com/mui/material-ui/issues/15561), dynamic props [#15573](https://github.com/mui/material-ui/issues/15573) and an unstyled version [#6218](https://github.com/mui/material-ui/pull/6218).
❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
| 4,212 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/october-2019-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './october-2019-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,213 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/october-2019-update.md | ---
title: October 2019 Update
description: Here are the most significant improvements in October.
date: 2019-11-08T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
Here are the most significant improvements in October:
- 🔍 We have introduced a new autocomplete / combo box / multi-select component [in the lab](/material-ui/react-autocomplete/).
<p class="blog-description">Combo box (limited options)</p>
- 📚 We have changed the demos to automatically inline a small code preview when possible.
- ♿️ We have fixed 9 accessibility issues ([#18141](https://github.com/mui/material-ui/pull/18141), [#18142](https://github.com/mui/material-ui/pull/18142), [#17972](https://github.com/mui/material-ui/pull/17972), [#18146](https://github.com/mui/material-ui/pull/18146), [#17939](https://github.com/mui/material-ui/pull/17939), [#17892](https://github.com/mui/material-ui/pull/17892), [#17897](https://github.com/mui/material-ui/pull/17897), [#17870](https://github.com/mui/material-ui/pull/17870), [#18204](https://github.com/mui/material-ui/pull/18204)).
- 📦 We have introduced [codesandbox-ci](https://ci.codesandbox.io/status/mui/material-ui/pr/18238). It can be useful when you want to live on the edge. For instance, you might want to rely on an unreleased commit that contains a bug fix.
But this summary is just scratching the surface. We have accepted 182 commits from 68 different contributors. We have changed 1,157 files with 31,312 additions and 9,771 deletions.
## Our roadmap intent for November
_(We'll do our best, no guarantee!)_
- 💅 We will initiate an update of our styling solution.
It should cover styled-component [#6115](https://github.com/mui/material-ui/pull/#6115), the system [#15561](https://github.com/mui/material-ui/issues/15561), dynamic props [#15573](https://github.com/mui/material-ui/issues/15573) and an unstyled version [#6218](https://github.com/mui/material-ui/pull/6218).
- 📅 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. The core will be open-source. The advanced features of the data grid will be behind an enterprise subscription ⭐️.
This is an effort [of our roadmap](/material-ui/discover-more/roadmap/) to better answer enterprise needs. To get a rough idea of what's coming, you can read: https://uxdesign.cc/design-better-data-tables-4ecc99d23356.
- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
These are three major efforts, we will likely need the whole quarter (Q4) to make significant progress. Stay tuned.
| 4,214 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/premium-plan-release.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './premium-plan-release.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,215 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/premium-plan-release.md | ---
title: Premium passengers, please proceed to the boarding gate 🚀
description: Introducing the MUI X Premium plan, and a new licensing model.
date: 2022-05-12T00:00:00.000Z
authors: ['josefreitas', 'alexfauquette']
tags: ['MUI X', 'News']
card: true
---
We're happy to announce that the Premium plan is [finally out](https://mui.com/pricing/)!
With it, MUI X officially steps up to the next level, supporting more advanced data grid use cases.
<img src="/static/blog/premium-plan-release/card.png" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" alt="Promotional image of MUI X Premium plan release showcasing Data Grid's new features (such as Download data as an Excel file) and Date Range Picker" />
You can use the new Premium features to provide your end users with the most sophisticated tools necessary to navigate and interpret massive amounts of data.
## The new features
### Row grouping
[Row grouping](https://mui.com/x/react-data-grid/row-grouping/) lets users group data based on repeating values in the grid.
For example, users can now group orders by buyers, movies by directors, or cities by the governing parties.
These kinds of use cases would usually be dealt with using a new query on the database—which might require a new service end-point, and maybe even a new front-end, along with all the UX challenges this would entail.
Now this functionality is available to your users with a single click.
<video autoplay muted loop playsinline controls>
<source src="/static/blog/premium-plan-release/row-grouping-example.mp4" type="video/mp4" />
</video>
<p class="blog-description">The feature in action, from the docs page.</p>
Users are encouraged to explore the data and create combinations with multiple grouping criteria,
and are then able to export these new views to Excel, with the next Premium feature: Excel export.
:::info
With the Premium release, we have made Row grouping available for production use in the `@mui/x-data-grid-premium` package.
This feature was previously available [as a preview](https://mui.com/blog/introducing-the-row-grouping-feature/#how-to-unlock-this-feature) for Pro users intending to migrate to the new plan.
:::
### Excel export
[Excel export](https://mui.com/x/react-data-grid/export/#excel-export) enables users to save the data from the grid as an Excel spreadsheet that mirrors the existing visualization in the data grid based on filters, sorting, and row grouping.
This is one of the most requested features to date, so we're excited to finally deliver.
In the future we intend to support all of the features impacting visualization of the data grid, but we'd love to hear from you if there's anything in particular you'd like to see in future releases.
<video autoplay muted loop playsinline>
<source src="/static/blog/premium-plan-release/excel-export-example.mp4" type="video/mp4" />
</video>
<p class="blog-description">The feature in action, from the docs page.</p>
### Aggregation (coming in late Q2)
Speaking of future releases: [aggregation functions](https://mui.com/x/react-data-grid/aggregation/) are coming next, as part of our ongoing efforts to build better tools for analyzing data.
Combined with row grouping, aggregation functions help users dive even deeper into their data for more granular insight.
Expanding on the use cases in the previous examples, users will be able to dynamically get the sum of orders for each customer, the minimum rating of each director, or the average crime rate for each governing party.
Aggregation functions open up an exponential number of new possibilities for organizing data—all with just a few clicks.
<video autoplay muted loop playsinline controls>
<source src="/static/blog/premium-plan-release/aggregation-example.mp4" type="video/mp4" />
</video>
<p class="blog-description">The feature in action, from the docs page.</p>
## The new licensing model
With the release of the Premium plan, we're also announcing a revised pricing and licensing model for MUI X Premium and Pro.
We're aiming for simplicity, restructuring the model to be as clear as possible, based on the recurrent questions we've had in our sales and other channels.
We'd also like to keep it within reach of individuals and small teams, while still capturing more of the value we generate for larger companies.
Here is a list of everything that has changed:
:::warning
The following **pricing** changes apply only to **new customers**.
Existing customers are grandfathered, they can renew their license under the [previous terms](https://mui.com/legal/mui-x-eula-2022-05-08/) once.
Their last renewal can have a support duration of up to 5 years.
:::
- **Cost per developer seat**
We're lowering our base price points, particularly for Pro users. Fees are billed annually.
- Pro: $249 → $180/year or $15/month
- Premium: $599 → $588/year or $49/month **($444/year - early bird)**
- **Removing volume and renewal discounts**
We aim to give a more transparent price based on the number of developer licenses while providing more predictable revenue for MUI X in the long term.
We believe that's best for both our long-standing customers and us as a company.
- **Perpetual in production**
Customers can use any licensed version perpetually in a production environment (deployed/published applications), but an active license will always be required during development.
We roll bug fixes, performance enhancements, and other improvements into new releases, so we want to encourage projects in active development to use the latest version.
- **Price cap for Premium plan**
Pro is still capped at 10 seats, but Premium doesn't have a license cap. We kindly ask you to [contact sales](mailto:[email protected]) if you wish to purchase a license for more than 50 developers.
Please feel free to read the [license agreement](https://mui.com/legal/mui-x-eula/) in detail.
## What can you expect next?
We mentioned the aggregation functions already,
but there's a [lot more coming](https://github.com/mui/mui-x/projects/1), and certainly not only for Premium users.
We're making continuous improvements to all X components, placing more emphasis on the overall experience for both the developer and the user.
A product designer is soon joining the team, and we aim to keep exploring the most advanced use cases for data-rich applications,
while working on bringing the best UX and DX in the market.
We're very excited about the possibilities the new Premium features will enable, and we hope you're excited too!
## FAQ 🔧
### How do I migrate?
To migrate to the premium version in your codebase, install the dedicated package `@mui/x-data-grid-premium` as follows:
With npm:
```js
npm install @mui/x-data-grid-premium
```
With yarn:
```js
yarn add @mui/x-data-grid-premium
```
All the features from Community and Pro plan are available in the Premium package. You can remove your previous data grid package without any concern.
The new package exports the component `<DataGridPremium />` which has basically the same API as `<DataGridPro />`. To use this package for development of a production product, and to remove the watermark, you must acquire a Premium license. If you wish to upgrade your existing Pro license, please [contact sales](mailto:[email protected]).
### Should I update my code?
You don't have to take any action here as a Community or Pro user, unless you're already using row grouping in your project.
Row grouping is now officially deprecated in the Pro package and will be removed from the experimental features [as planned](https://mui.com/blog/introducing-the-row-grouping-feature/#how-to-unlock-this-feature).
You must upgrade to the Premium plan to continue to use the row grouping feature.
### What can I do with the Excel export feature?
The free version of the data grid features a print export to give users a printable visualization, as well as a CSV export for migrating data to another application.
But CSV exports are basic and limited when the exported file is consumed by users instead of other applications. The Excel format provides more room for flexibility and customization.
#### Cell constraints
By setting a column type you prevent users from making errors, such as entering an invalid date, or using letters in a number column. The exported file will reflect those type constraints.
A special case is the `singleSelect` column type which provides an array of options. This constraint is also reflected in the exported file, meaning the singleSelect options will be available as field value options in the Excel spreadsheet.
#### Hierarchical structure
With tree data and row grouping, users can create a hierarchical structure between rows. This structure is also available in the exported file, and in Excel you can toggle the visibility of a row's children.
#### Brand customization
If you plan to generate spreadsheets to share, you may want to add headers, apply brand colors, or add extra details to the document.
To fully customize your Excel files, you can access their content before _and_ after the data is inserted.
## Share your feedback 🗣
We hope you find these new features useful and enjoyable to work with, both as a developer and a user.
Please don't hesitate to [open an issue](https://github.com/mui/mui-x/issues/new/choose) to share feedback, report bugs, or propose enhancements.
| 4,216 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/september-2019-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './september-2019-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,217 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/september-2019-update.md | ---
title: September 2019 Update
description: Here are the most significant improvements in September.
date: 2019-10-12T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
Here are the most significant improvements in September:
- 💄 Add `startIcon` and `endIcon` props for the button. It makes it simpler to append an icon:
```jsx
import DeleteIcon from '@mui/icons-material/Delete';
<Button startIcon={<DeleteIcon />}>Delete</Button>;
```
- 🔐 Add support for Chrome autofill. The `InputBase` component detects Chrome autofill events and updates the label position accordingly.
- 📊 Launch a [developer survey](https://www.surveymonkey.com/) as a precursor to a major Date Picker enhancement effort. We plan a new investment batch of between 100 and 500 hours.
- 📚 Change imports from `@mui/styles` to `@mui/material/styles`
The presence of two almost identical import paths has been a source of confusion: @mui/styles and @mui/material/styles.
Starting with v4.5.1, the documentation mentions @mui/material/styles as much as possible.
```diff
-import { makeStyles } from '@mui/styles';
+import { makeStyles } from '@mui/material/styles';
```
This change removes the need to install the `@mui/styles` package directly.
It prevents the duplication of `@mui/styles` in bundles and avoids confusion.
You can [learn more about the difference](https://v4.mui.com/styles/basics/#material-ui-core-styles-vs-material-ui-styles) in the documentation.
But this summary is just scratching the surface. We have accepted 199 commits from 61 different contributors. We have changed 1,219 files with 18,223 additions and 11,957 deletions.
## Our roadmap intent for October
_(We'll do our best, no guarantee!)_
- 🔍 We will provide a ready-to-use autocomplete, combo box, and multi-select components in the lab. You can already [preview it](https://deploy-preview-17037--material-ui.netlify.app/components/autocomplete/).
<p class="blog-description">Combo box (limited options)</p>
<p class="blog-description">Multi-select</p>
<p class="blog-description">Autocomplete (free options)</p>
- 📅 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](/material-ui/discover-more/roadmap/) to answer enterprise needs.
- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
| 4,218 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/siriwat-kunaporn-joining.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './siriwat-kunaporn-joining.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,219 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/siriwat-kunaporn-joining.md | ---
title: Siriwat Kunaporn joins MUI
description: We are excited to share that Siriwat Kunaporn has joined MUI.
date: 2021-05-17T00:00:00.000Z
authors: ['oliviertassinari']
card: true
tags: ['Company']
---
We are excited to share that [Siriwat Kunaporn](https://twitter.com/siriwatknp) (Jun) has joined MUI.
He started a couple of days ago full-time and is part of the core components team.
Before joining MUI, Jun worked as a software engineer at ThoughtWorks.
He has spent the last three years as a full-stack engineer, focusing more on React and the implementation of great-looking UIs. Jun is passionate about creating UIs that feel amazing.
We were impressed by his previous work on exploring the customization potential of MUI in [MUI Treasury](https://mui-treasury.com/).
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/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.
We have opened these positions as our revenue growth allows.
These new roles will help accelerate our mission, strengthen our existing offering, and initiate a new vertical.
We couldn't be more excited to have Jun on the team!
| 4,220 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/spotlight-damien-tassone.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './spotlight-damien-tassone.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,221 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/spotlight-damien-tassone.md | ---
title: A spotlight on Damien Tassone joining the team
description: Damien Tassone has joined MUI. He's the first full-time member to focus on enterprise components.
date: 2020-09-15T00:00:00.000Z
authors: ['oliviertassinari']
card: true
tags: ['Company']
---
A few months ago, right in the middle of the COVID-19 outbreak, [Damien Tassone](https://twitter.com/madKakoO) joined MUI. He's the first full-time member to focus on enterprise components. Back then, we only made a quick mention of it. It's never too late to introduce him properly.
Prior to joining MUI, Damien worked in the finance industry in London for a decade. Part of the initial Agile Market team at RBS, and more recently leading a large Commodity Trading application at Adaptive, Damien has developed his React experience as part of large projects where Components driven design plays a huge role in successfully delivering applications. He loves TypeScript.
Right from the start, Damien has made fast and significant progress. He has been an amazing addition to the team, and thanks to him, we are on the verge of releasing a new advanced component: the [Data Grid](https://v4.mui.com/components/data-grid).
<img src="/static/blog/spotlight-damien-tassone/data-grid.png" style="margin-bottom: 3rem;" alt="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/mui-x/projects/1).
You can follow Damien on [Twitter](https://twitter.com/madKakoO).
| 4,222 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/v6-beta-pickers.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './v6-beta-pickers.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,223 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/v6-beta-pickers.md | ---
title: Date and Time Pickers revamped
description: Check out the new features coming in v6 beta.
date: 2023-01-22T00:00:00.000Z
authors: ['josefreitas']
tags: ['MUI X', 'News']
---
There's a lot of exciting news in [MUI X v6.0.0-beta.0](https://github.com/mui/mui-x/releases/v6.0.0-beta.0), but there's hardly anything comparable to the revamp we're delivering for the Date and Time Pickers.
This is the result of our ongoing efforts to improve the usability and customizability of these components.
We kept the best aspects of the previous versions, and we're fleshing out the package with a [new documentation](https://next.mui.com/x/react-date-pickers/getting-started/), major new features and one fundamental change: a new input type to replace the masked text fields.
## The new date and time fields
These new input components are called [Fields](https://next.mui.com/x/react-date-pickers/fields/), and they provide massive improvements to the experience of editing the value with a keyboard.
The previous generation of pickers, whose text input is based on a [mask approach](https://www.npmjs.com/package/rifm), are often cumbersome and fall flat on edge cases as well simple cases like modifying dates.
For example, watch what happens when we edit the month on this masked input:
<video style="width: 608px;" autoplay muted loop playsinline>
<source src="/static/blog/v6-beta-pickers/masked-input-bad-ux.mp4" type="video/mp4" />
</video>
As you can notice, the day and year leak to the previous sections of the date, presenting a serious challenge to usability.
In contrast, the new fields are specialized in editing date and time values.
They recognize the values on the input (day, month, year, etc.) and respond accordingly.
<video style="width: 608px;" autoplay muted loop playsinline>
<source src="/static/blog/v6-beta-pickers/basic-date-field.mp4" type="video/mp4" />
</video>
The Fields are included in the pickers, but they're also available as standalone components.
You can import them from the latest v6 package.
```jsx
import { DateField } from '@mui/x-date-pickers/DateField';
<DateField label="My first field" />;
```
They're by default used in the new Pickers (you don't need to declare a text field anymore).
```jsx
import { DatePicker } from '@mui/x-date-pickers/DatePicker';
<DatePicker label="My first v6 picker" />;
```
## Enhanced keyboard usability
With the new Fields, the keyboard interaction is a first-class experience.
Not only can you type the date as text, but you can also use arrow keys to navigate and edit date and time values.
<video style="margin-bottom: 5px; width: 608px;" autoplay muted loop playsinline>
<source src="/static/blog/v6-beta-pickers/date-field-navigation.mp4" type="video/mp4" />
</video>
For a quick comparison, let's check out how the old and new approaches behave in typical scenarios.
<video style="margin-bottom:24px" autoplay muted loop playsinline >
<source src="/static/blog/v6-beta-pickers/quick-comparison-fields.mp4" type="video/mp4" />
</video>
Moreover, notice in the following example that as we edit the day, the component automatically navigates only in valid values.
<video style="margin-bottom: 5px; width: 608px;" autoplay muted loop playsinline >
<source src="/static/blog/v6-beta-pickers/smart-field-stable.mp4" type="video/mp4" />
</video>
:::info
**Behavior change alert**
During pre-releases, using <kbd class="key">Arrow Up</kbd> and <kbd class="key">Arrow Down</kbd> to update a date section would essentially update the entire field like you were navigating the calendar.
In the previous example, updating the day value from 28 to 1 would also update the month to March.
On the stable version, released after the original post, each date section is independent.
This behavior [has been changed](https://github.com/mui/mui-x/issues/7934) to be more consistent with native implementations.
:::
Please, try it out for yourself in the live demo below.
<iframe
src="https://codesandbox.io/embed/date-field-demo-pb87v0?fontsize=12&hidenavigation=1&module=%2F"
style="width:100%; height:200px; border:0; border-radius: 4px; overflow:hidden;"
allow="accelerometer; ambient-light-sensor; camera; encrypted-media; geolocation; gyroscope; hid; microphone; midi; payment; usb; vr; xr-spatial-tracking"
sandbox="allow-forms allow-modals allow-popups allow-presentation allow-same-origin allow-scripts"
></iframe>
### Fields roadmap
The Fields are still in beta, and there are many improvements on the way.
The following list describes some of the most notable features planned.
- **[Smart pasting](https://github.com/mui/mui-x/issues/7253)** \
Date strings pasted in Fields will be parsed and matched with the sections of the date.
- **[Support days of the week](https://github.com/mui/mui-x/issues/7254)** \
Users will be able to select a day in the week just like the can select a month.
We'd love to hear your [feedback](https://github.com/mui/mui-x/issues/new/choose) to help us improve these components even further.
## Other significant improvements
Now that you've seen what's fundamentally changed with the Pickers, let's briefly review some other noteworthy improvements.
- **[Customization of layout and internal components](https://next.mui.com/x/react-date-pickers/custom-layout/)** \
Combining the concept of slots with the grid layout, you now can rearrange, extend, and customize most of the components used internally by the Pickers' views.
- **Default render input**\
You don't need to provide the usual `TextField` on `renderInput` anymore unless you need it customized.
In which case you can do it by:
1. Customizing through props via `field` and `input` slots ([codebox example](https://codesandbox.io/s/customizing-fields-with-props-o66r1c?file=/demo.tsx)).
2. Build a new field component using the Field's headless API (documentation coming soon).
3. Use an entirely [custom text field](https://next.mui.com/x/react-date-pickers/date-picker/#custom-input-component) to suit your use case.
- **Drag to edit**\
Editing a date range is even easier now with the new drag-and-drop interface. Change `start` and `end` dates at will.
<video style="margin-bottom: 24px; max-height: 398px;" autoplay muted loop playsinline>
<source src="/static/blog/v6-beta-pickers/edit-drag.mp4" type="video/mp4" />
</video>
- **Range shortcuts** (available from v6.0.0-beta.1)\
Add quick and customizable shortcuts for your users. Choose to display them on the left, right, bottom or top.
<img src="/static/blog/v6-beta-pickers/date-range-shortcuts.png" style="width: 692px; margin-bottom: 24px;" loading="lazy" alt="Date Range shortcuts." />
## Should we retire the masked inputs?
We believe that after using the date fields, you'll have no reason to come back to the masked input approach.
It has a few irreparable usability issues, and it sets some hard limits on what we can do with the input.
Our plan is to replace them entirely, but you can help us steer our roadmap.
If you want to voice your opinions or get involved, please consider scheduling a [user interview](https://forms.gle/7uq8PzE26FgwkPs46) with us.
As always, you can get in touch by opening new bug reports or feature requests in our [GitHub repository](https://github.com/mui/mui-x/issues/new/choose).
| 4,224 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/ROLE_TEMPLATE.md | # XXXXXX
<p class="description">XXXXXX.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://link-to-public-notion-page.com).
- We're a **remote** company, operating mostly asynchronously.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
XXXXXX
### Why this is interesting
XXXXXX
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
## The role
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- XXXXXX
- XXXXXX
## About you
### Skills you should have
- XXXXXX
- XXXXXX
### What would be nice if you had, but isn't required
- XXXXXX
- XXXXXX
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/__ID__/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,225 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/accessibility-engineer.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/accessibility-engineer.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,226 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/accessibility-engineer.md | # Accessibility Engineer (future role)
<p class="description">You will become our go-to expert for accessibility, to ensure all products meet or exceed WCAG 2.1 level AA guidelines.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Accessibility is a strategic opportunity for MUI, across our products:
1. We are building Base UI for the developers that are looking for a relatively lower-level API while keeping a strong baseline to build on top of that saves them time. For them, it's about having a better customizability experience (style & behavior). The most exigent users of Base UI, the ones that are spreading the viral growth of the product in the community, have strong a11y requirements. So we have to meet them for Base UI to be successful.
2. Accessibility is mandated by law. For example, in the US, the Americans with Disabilities Act (ADA) is a US law enacted in 1990 to ensure people with disabilities are not discriminated against. In the EU, the European Accessibility Act (AEE) will soon be enacted. Our paid customers are increasingly asking about compliance with WCAG.
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
### Why this is interesting
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
So, by improving the accessibility of our components, you will help millions of end-users who use [the products built with our UI library](https://trends.builtwith.com/framework/Material-UI).
You will also be responsible to train the developers using MUI's products to a11y. For example, there might be an opportunity to create an eslint plugin aware of Material UI APIs to catch a11y issues before they go to production.
## The role
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- **Ensure the components are accessible.**
You will be the owner of the accessibility across all MUI products. First, you will be responsible to verify the level of accessibility the components comply with and then implementing improvements over time.
- **Respond to issues related to accessibility.**
The users of our products create issues related to a11y. You will be responsible to unlock the community, either by providing best practices, guiding them to contribute a fix, or by directly fixing the issues reported.
- **Intelligently apply accessibility testing tools**. You will use assistive technology and perform expert manual analysis of the MUI product lines.
Having a solid test framework that can help us make sure we stay compliant.
- **Lead the accessibility training across the company.**
You will be the go-to person for anything related to accessibility. You will mentor other team members.
## About you
### Skills you should have
- **Strong grasp of accessibility techniques in web development** applying HTML5, CSS, ARIA, and JavaScript. You should have held a Front-end Engineer (or closely related) role in the past.
- **A track record of accessibility experience with both consumer/enterprise products and assistive technologies, such as screen readers, eye control, and other accessibility technologies**.
If you've been the accessibility champ in a previous company, pushing towards making sure the user interfaces can be used by disabled people, we want you in our team!
- **Hands-on knowledge of accessibility guidelines and standards** (such as Section 508, WCAG, and EN 301 549) as well as technologies (such as UI Automation, IAccessible, ARIA, and related accessibility APIs)
You would be the one who the team can go to with any a11y topics/questions.
- **An advocate of continuous learning;** able to absorb and share new ideas, approaches, and techniques for achieving accessibility.
Continuous learning is one of the most important parts of this field.
- **Experience with assistive technologies across multiple platforms**, including screen readers, magnification, and read-aloud tools.
### What would be nice if you had, but isn't required
- **Certification in accessibility**, such as Trusted Tester, CPACC (Certified Professional in Accessibility Core Competencies), WAS (Web Accessibility Specialist).
This would be a clear indication that you went deep into the accessibility topics.
- **You've contributed to a design system before**.
You have worked on enterprise components in the past, maybe for internal use in your company.
You have built some features while making sure the accessibility was fully functional.
## Benefits and compensation
We offer competitive compensation depending on the profile and location.
We're ready to pay top market rates for a person who can clearly exceed the role's expectations. Learn more about perks and benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/ebc6db2a-fda9-431e-b45a-692377ef74aa/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,227 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/design-engineer-x-grid.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/design-engineer-x-grid.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,228 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/design-engineer-x-grid.md | # Design Engineer - xGrid
<p class="description">You will design and implement a great user and developer experience for the MUI X Data Grid.</p>
## Details of the role
- **Location**: Remote (strong preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub and has paved the way for the fully-fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
We are aiming to make high-end design accessible to the many, empowering developers who lack access to a designer as well as saving time for designers with a source they can trust.
[According to our last survey](https://mui.com/blog/2021-developer-survey-results/#what-are-your-most-important-criteria-for-choosing-a-ui-library), the quality of the design execution (UX & UI) is the most important criterion used by developers & designers to pick their next UI library.
### Why this is interesting
Developing and designing components for advanced use cases is not an easy feat.
It's an intricate challenge to craft customizable, feature-rich, and performative components while having them look great out of the box.
Within the MUI X team, you'll be facing this challenge head-on!
We want to serve demanding customers by making their experience building data-heavy and complex applications much smoother with reliable, advanced React components.
There aren't a lot of benchmarks out there.
So, by combining top-notch engineering with sleek product design, you'll be pioneering a whole different area of UI component development.
## The role
### What you'll do on a day-to-day basis
The Design Engineer role sits right at the intersection between product design and software engineering. So, depending on the initiative, your day can be entirely different! Here's what you'll be able to do:
- **Contribute to feature releases and deep refactors**.
MUI X is a complex codebase. Components we've shipped recently, such as the Data Grid and Date and Time Pickers, require months of dedicated, careful work.
- **Design for engineers and their end users**.
As an engineer yourself, you can understand the problems developers face, and you will help them overcome those problems by delivering amazing DX and enabling them to create powerful UX for their end users.
This might involve careful API design, identifying and fixing top bugs, creating easy-to-understand error messages, and writing documentation and blog posts about features you and your team ship.
- **Collaborate with the open-source community**.
The community contributes with many meaningful features and fixes. You'll guide and support them helping MUI X's growth while inspiring many others to join the ride, too.
- **Experiment and play**. Great, unexpected features and heisenbug fixes have come from a number of sources — relentlessly methodical processes of elimination, free-flowing team collaboration, inspiration from adjacent libraries and projects, and difficult-to-explain individual strokes of brilliance. Whatever your preferred style is for creating new things that others might not have thought of, you'll find a welcome home on the team.
- **Take ownership of features from idea/mockup to live deployment**.
You'll shape and guide the direction of crucial new features, including new components.
- **You'll be interacting with customers** regularly, handling inbound support and feature requests (every developer helps with developer requests).
- **Bridge the gap between design and engineering**.
Sometimes, you'll be sketching new features on Figma. On other days, you'll be prototyping them in code.
### Challenges you'll face
- **Context switching**.
As a small team, sometimes priorities shift fast, requiring you to dive into an entirely different feature you're unfamiliar with. It's challenging to get used to but rewarding.
- **Moving fast without sacrificing quality**.
Given our product is essentially code, our users and customers are incredibly demanding. To serve them the best way possible, we need to ship incredibly high-quality code quickly. However, sometimes we need to exchange going 100% into solving an issue, to instead aim for 50 to 70%, for a faster feedback cycle.
- **Open-source: The nonstop stream of bug reports and support requests**. You'll frequently have your attention challenged given community requests keep pouring in. It will require you to develop an intuition for when to ignore something for later vs. when to dig in immediately as it could be a valuable improvement opportunity.
## Who we're looking for
### Required
- 3+ years of web front-end development at product-driven companies
- Great understanding and taste in product design
- Experience with design systems
- You're highly empathetic
- Fluent written and spoken English skills
### Nice to have (but not required)
- Experience in open-source
- Experience with MUI products
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-amp-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/5a1c18de-e0b5-4253-aca1-e3f261112920/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,229 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/design-engineer.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/design-engineer.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,230 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/design-engineer.md | # Design Engineer (future role)
<p class="description">You will focus on design to implement great product experiences.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
We are aiming to make high-end design accessible to the many, empowering developers that lack access to a designer as well as saving time for designers with a source they can trust.
[According to our last survey](https://mui.com/blog/2021-developer-survey-results/#what-are-your-most-important-criteria-for-choosing-a-ui-library), the quality of the design execution (UX & UI) is the most important criteria used by developers & designers to pick their next UI library.
### Why this is interesting
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
But while we are [the leading](https://tsh.io/state-of-frontend/#over-the-past-year-which-of-the-following-design-systems-was-your-favorite-go-to-solution) UI design system in the frontend space, the adoption of MUI is only at 25%. More importantly, the challenges of developers and designers to solve when creating UIs go way beyond the ones of design systems.
We envision a future where MUI becomes the default toolkit for web developers to create UIs.
It's why we started Base UI, Joy UI, and MUI Toolpad. Design is key to achieving this goal.
## The role
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- Work closely with our designers to prototype and implement new components, features, and screens.
- Design and build entire experiences for sites like mui.com or products like MUI Toolpad.
- Concept and prototype UX components and motion studies for components like the date picker.
- Extend our different design systems (Material UI, Joy UI).
- Create appealing new demos in the docs.
## About you
### Skills you should have
- 3+ years of relevant web front-end development experience at a tech-forward, product-driven company.
- Advanced knowledge of modern React, HTML, and CSS.
- Experience designing and building public facing-sites that work elegantly.
### What would be nice if you had, but isn't required
- A good understanding of the formal elements of design, not just limited to the web and including typography, layout, balance, and proportion.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/c45a0b2d-aa37-4dec-8bcd-e70040f3af49/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,231 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/designer.md | # Designer
<p class="description">Design is critical to our success. We're looking for skills that complement those of our Lead Designer. You'll help to design the tools that enable our audience to build outstanding-looking UIs.</p>
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Material UI started as an open-source project.
Over time, the audience and usage grew considerably, and some of the library's early contributors became full-time maintainers.
A company was incorporated to support this growth, and more recently [was rebranded from Material UI to MUI](https://mui.com/blog/material-ui-is-now-mui/).
The new brand was fundamental to set the stage for MUI to become larger than Material Design, which was something we were already doing.
Currently, we have five main projects that are not at all related to MD:
- [MUI Core](https://mui.com/core/):
- [Base UI](https://mui.com/base-ui/getting-started/): the unstyled version of the components.
- [MUI System](https://mui.com/system/getting-started/): our most recent take on styling for React components.
- [MUI Joy (working title)](https://github.com/mui/material-ui/discussions/29024): a second design system as an alternative to Material Design.
- [MUI X](https://mui.com/x/): as mentioned, a growing set of advanced components.
Today, the flagship is the [Data Grid](https://mui.com/x/react-data-grid/), a game-changing component for presenting large amounts of data, which integrates perfectly with MUI Core.
- MUI Toolpad: 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.
We also know, especially due to [our annual developer survey](https://mui.com/blog/2021-developer-survey-results/), that design quality plays a huge part when developers are considering component library options.
Therefore, we need to grow the design team to help us push these initiatives further.
## The role
Some criteria for applying to this role:
- **Location**: fully remote (preference for UTC-6 to UTC +3).
- **Type of work**: full-time (as a contractor or employee, [depending primarily on location](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501)).
- **Level**: [3 or above](https://mui-org.notion.site/Design-levels-aa01996ca7e0481e80479ad47c8f28a4).
We need someone experienced enough to help two different teams with hard problems.
You'll be responsible for ensuring that the MUI Toolpad and MUI X teams have spot-on design and product work.
Given that each product is at a different stage, at this moment we believe that one person is enough to oversee the design function for both teams.
You'll have the freedom, trust, and help you need to balance and tackle all the work.
You'll also be the second designer of a growing design team, so we'll also need your help to shape this growth.
### Here are a few initiatives you might work on
- Help design the first version of MUI Toolpad, from early strategy to its look and feel.
- Evolve and refine the Data Grid UX for features such as filtering, column pinning, row editing, and more.
- Help set the bar higher for MUI X documentation, from visual design to copywriting.
- Support the design team growth by promoting design/product culture, and hiring new members.
### You might fit for this role if you
- See yourself as a generalist designer, tackling problems ranging from strategic thinking to execution. (More insight in the [first draft of our design philosophy](https://mui-org.notion.site/Design-philosophy-bdbef60d6fad4134a43870df3e452ebc), available in our public Handbook).
- Have excellent visual and interaction design skills.
- Consider yourself a great communicator, both written and verbal.
Designers are key players when it comes to creating alignment and shared understanding, whether with internal or external stakeholders.
- Feel comfortable around code and git (we use GitHub).
Developers are MUI's main audience, so it's very important to experience our technology for yourself, to empathize with our users.
You should be capable of tweaking JSX and CSS, ensuring that your designs are implemented with the highest fidelity.
But don't worry, you'll always have the support of your teams' developers.
Previous experience with design systems would be great but is not required.
## Benefits and compensation
We offer competitive compensation, aligned with your profile and location.
We're ready to pay top market rates for a designer that can significantly push the mission forward.
Other perks are described on [the careers page](https://mui.com/careers/#perks-and-benefits/).
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/__ID__/application?utm_source=ZNRrPGBkqO).
## What happens next?
We start by screening applications, looking for designers that showcase the desired skills and experience.
If your application stands out, we'll contact you for a get-to-know conversation, where we'll meet each other.
If that goes well, you'll be invited to up to four additional conversations, those being:
- A walkthrough of one or two selected projects that you believe demonstrate [comparable experience.](https://articles.uie.com/ux-hiring-lets-talk-about-comparable-experience/)
- A chat with one of the product managers or engineers that you will work closely with.
- A chat with one of MUI's founders.
- A possible follow-up chat if we missed addressing anything relevant in the previous conversations.
All these conversations will be 1:1 and over video chat.
Please ask as many questions as you wish throughout the whole process, it's a two-way discussion.
If you happen to need additional conversations as well, feel free to ask; we'll be happy to schedule them.
Lastly, please note that we're unable to offer individual feedback during the initial screening process, as we're a small team and don't have the bandwidth to do so.
We look forward to hearing from you! ☺️
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,232 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/developer-advocate.md | # Developer Advocate
<p class="description">You will build a thriving and connected developer community around our suite of products.</p>
## Details of the Role
- **Location**: Remote (strong requirement for UTC-8 to UTC+2).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## About the company
MUI started with Material UI, the most successful React implementation of Google's Material Design.
We have gained a large following, thanks to our focus on Material Design fidelity, our obsession with details, on offering a large number of components, our community engagement, and by carefully improving the DX.
Today, countless teams and organizations rely on our open-source libraries to build their design system.
A couple of years ago, we started to expand our suite of products.
We released [MUI X](https://mui.com/x/), a collection of advanced components; [MUI Design kits](https://mui.com/design-kits/), the MUI components available for Figma, Sketch, etc.; and also host [Templates](https://mui.com/templates/), a set of pre-built UI kits.
We've seen rapid growth with all of them (2x per year) and we have more to come.
We are building [a low-code platform](https://mui.com/toolpad/) for developers to significantly increase the speed and lower the barrier for creating simple CRUD/dashboard UIs with MUI's libraries.
We are a fully distributed team, spread across multiple time zones.
We work mainly asynchronously, relying mostly on written collaboration.
Every contributor has the freedom to define how they work — the rest of us won't know what you're doing day-to-day unless you tell us.
For additional details about the MUI team and culture, you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
In our [last developer survey](https://mui.com/blog/2021-developer-survey-results/#what-else-can-we-do-to-improve-mui-for-you), we learned that we have a long way to go in helping developers to be successful with our technology.
We have underinvested in this area for too long.
Your mission will be to be the voice of the developers of the community inside the company.
We are looking for someone that can contribute to the following outcomes:
- Create momentum in the React community and drive adoption of the library.
- Improve the overall developer experience, resulting in better NPS & CSAT scores, e.g., through educational content.
- Amplify the need of the community so the product direction aims at what people need the most.
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
## About the role
We are looking for a experienced developer to join us as a Developer Advocate to help the developers get familiar with and use MUI most effectively.
### Why this is interesting
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- **Content**.
- Produce high-quality technical "how-to" content (blogs, webinars, demos, talks) addressing common user needs, latest technology advances, and emerging best practices. Videos might go to [our YouTube channel](https://www.youtube.com/@MUI_hq).
- Distribute content and leverage pieces to broaden awareness of the MUI brand, via existing connections.
- Rework the pages of the documentation that are confusing, base on feedback.
- **Community**.
- Built our developer-focused community.
- Deliver presentations at meetups, conferences, and other ecosystem events.
- Create & produce events (podcasts, roundtables, hackathons).
- Manage the sponsorships of events, newsletters, etc.
- Help other team members grow at engaging with the community. For instance by encouraging and providing critical feedback on the blog posts they create, or by keeping track of the health of community contributions.
- **Relationship-building**.
- Create relationships with fellow ecosystem influencers and open-source leaders.
- Nurture ongoing connections with user group members to build personal relationships and deeply understand their needs, usage, journeys, and barriers to adoption.
- **Technical**.
- Write code where required to support how-to content, blog posts, and presentations.
- Create inspiring sample applications, documentation, and tutorials.
- Give feedback to product management, to influence the product roadmaps based on developers' needs.
- Follow GitHub issues to understand where developers face frustration and develop strategies to overcome these. This could be suggesting or implementing documentation updates, or proposing or contributing code changes that solve the core issue.
For the right candidate:
- Working with the Leadership to construct and execute on a hiring plan to grow the Developer Experience team.
### Here are a few initiatives you might work on
- Create a learning section in the documentation for hybrid written and video tutorials.
- Own the Algolia search experience, improving the content on the most frequent search queries.
- Take ownership of the company's Twitter account.
- Level up the showcase, cherry-picking the best websites and apps of the community.
- Revamp the blog post infrastructure to empower the rest of the team to create more content.
- Start a monthly newsletter to engage with the community.
- Organize a MUIConf (once we go >50 people)
- Think about creative ways to promote Base UI, Joy UI, MUI X, MUI X Pro, and new products.
## About you
### Skills you should have
- You are fluent in English (both written and spoken). You'll be the face of MUI in the world, and make everyone in the company proud of the Developer Experience team.
- You are a highly empathic person.
- You are passionate about helping other developers solve problems and have an educational mindset.
- You have some formal or informal experience in teaching: training, tutoring, mentoring, etc.
- Hands-on developer who is comfortable with full-stack development.
- You are passionate about UI development.
### What would be nice if you had, but isn't required
- Experience in building community across some of the following channels: Twitter, YouTube, Twitch, Discord, blogs, meetups, public speaking & events
- Experience working with open-source and/or with the open-source community.
- Experience working with/editing video.
- Experience using MUI.
## Benefits & Compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/28287eeb-88d2-465f-96d7-e7fd99fabd7d/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,233 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/developer-experience-engineer.md | # Developer Experience Engineer - Core
<p class="description">You will focus on providing experiences that delight developers using MUI. This role is mostly about MUI Core.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+2).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
Developer Experience matters, [a lot](https://future.com/the-case-for-developer-experience/).
We are looking for somebody to build the best developer experience ever created around a component library, earning the love of developers everywhere.
This is about focusing on the outcome: success, that developers can have a wonderful workflow with our product.
We are looking for someone that can contribute to the following outcomes:
- Amplify the need of the community so the product direction aims at what people need the most.
- Improve the overall developer experience, resulting in better NPS & CSAT scores.
- Create momentum in the React community and drive adoption of the library.
### Why this is interesting
You have a lot of feedback, more than we can process. It's an opportunity to challenge the state of the art in the React component dev tool space.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
## The role
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- You will collaborate with Developer Advocates, Designers, Product Managers, Engineering Managers, Marketing, and other stakeholders to identify opportunities for improvement.
- Inform the technical approach and architecture of MUI as it relates to developer experiences.
- Help contribute to the MUI community by providing code review, mentorship, and support to MUI employees, community members, and partners.
- Advocate and support improvements to MUI to improve development and integration of tools and plugins, e.g. Storybook, Tailwind CSS.
- Work on issues and improvements critical to the success of MUI users and the broader community.
- Foster a culture of learning through iterative improvements and strong collaboration with UX research.
For the right candidate:
- Working with the Leadership to construct and execute on a hiring plan to grow the Developer Experience team.
## About you
### Skills you should have
- **A track record of demonstrating an eye for product and solving real-world user problems.** If you have a knack for solving problems at the root cause, shipping beautiful user interfaces and intuitive APIs, we want you on our team.
- **Expertise in the modern JavaScript ecosystem**.
MUI is built on the shoulders of giants, making use of technologies such as ES2021, TypeScript, Node.js, React, Next.js, webpack, and Babel.
- **Strong written and verbal communication skills**.
As part of the team, you'll interface both directly and indirectly with community members and enterprise customers, and contribute to user documentation. Clear communication is fundamental in creating intuitive and compelling resources.
- **Ability to dive into complex problems**.
You should be able to quickly assess, understand, and iterate upon aspects of our codebase.
- **Ready and willing to ask and answer questions**.
If you're comfortable saying you're unsure, asking for help; but equally reaching out to assist others, you'll be an incredible addition to our team. We thrive because of continuous learning. First-time mistakes should be celebrated, not blamed.
- **Past work with front-end infrastructure**.
Perhaps you've created your company's design system, written a Babel plugin, or written complex React components.
It would be great if you could address this in your cover letter!
### What it would be nice if you had, but isn't required
- **You've contributed to a design system before**.
You have worked on enterprise components in the past, maybe for internal use in your company.
You have built complex and advanced features while making sure the accessibility was fully functional.
- **You've maintained an active repository before**.
Maybe you've helped maintain a popular open-source repository, or perhaps you've worked on internal repositories that saw contributions from multiple teams.
Previous experience with highly active repository workflows is a definite plus for this role.
- **You have contributed code to MUI before**. A history of contributing to MUI would be a definite plus.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/__ID__/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,234 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/engineering-manager.md | # Engineering Manager - Toolpad
<p class="description">You will grow the small engineering team currently working on MUI Toolpad.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
Our mission is to empower as many people as possible to build great UIs, faster.
The faster and simpler it is, and the broader the audience that can create custom UIs, the better.
We believe that the best way to improve on these dimensions is to eliminate [80%](https://www.youtube.com/watch?v=GnO7D5UaDig&t=2451s) of the code that has to be written.
A few months back we started to work on [MUI Toolpad](https://github.com/mui/mui-toolpad), an ambitious project to deliver on this objective.
We have found the beginning of a market fit in this low-code segment.
We need help to structure & grow the engineering team.
### Why this is interesting
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
Toolpad targets around half of this audience.
While the team is still very small (5), we believe that the headcount on this product has needs to grow +14% MoM until the end of 2023 (>70 people).
Growing the Toolpad engineering team will be full of challenges.
## The role
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- Hire and grow a diverse engineering team in a fast-scaling organization.
- Cultivate excellence in the craft of the software your team builds.
- Act as a servant leader for the engineers that report to you. You will support the career growth of individuals on your team.
- Develop a great work environment.
- Work directly with users and the engineering team to improve the product.
- Improve our processes, e.g. the lifecycle of feature development from design through testing and release.
For the right candidate:
- Working with the Leadership to construct and execute a hiring plan to grow the engineering team on toolpad from one to multiple
## About you
### Skills you should have
- You've managed or supported a diverse, distributed engineers on small or large teams.
- You have an interest in building a support structure for engineers to help them succeed.
- You have phenomenal communication skills for working across the organization, capable of building strong relationships with peers and leadership.
- You have had strong expertise and mastery of React or front-end development in the past.
- You have deep empathy for users. You have experience with customer support or OSS community support.
### What would be nice if you had, but isn't required
- **You've maintained an active repository before**. Maybe you've helped maintain a popular open-source repository, or perhaps you've worked on internal repositories that saw contributions from multiple teams. Previous experience with highly active repository workflows is a definite plus for this role.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/__ID__/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,235 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/full-stack-engineer.md | # Full-stack Engineer - Toolpad (future role)
<p class="description">You will join the MUI Toolpad team, to explore the role of MUI in the low code space and help bring the early prototype to a usable product.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## About the company
MUI started with Material UI, the most successful React implementation of Google's Material Design.
It has gained a large following, not only due to its fidelity to Material Design, but also because of the number of components, its carefully designed component API, its obsession with details, and community engagement.
Today, countless teams and organizations rely on our open-source projects to build their design system.
A couple of years ago, we started to expand our suite of products.
We released [MUI X](https://mui.com/x/), a collection of advanced components; [MUI Design kits](https://mui.com/design-kits/), the MUI components available for Figma, Sketch, etc.; and also host [Templates](https://mui.com/templates/), a set of pre-built UI kits.
We've seen rapid growth with all of them (2x per year) and we have more to come.
We are building [a low-code platform](https://mui.com/toolpad/) for developers to significantly increase the speed and lower the barrier for creating simple CRUD/dashboard UIs with MUI's libraries.
We are a fully distributed team, spread across multiple time zones.
We work mainly asynchronously, relying mostly on written collaboration.
Every contributor has the freedom to define how they work — the rest of us won't know what you're doing day-to-day unless you tell us.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
Our mission is to empower as many people as possible to build great UIs, faster.
The faster and simpler it is, and the broader the audience that can create custom UIs, the better.
We believe that the best way to improve on these dimensions is to eliminate [80%](https://www.youtube.com/watch?v=GnO7D5UaDig&t=2451s) of the code that has to be written.
We're in the early stages of exploring what our role could be in the currently emerging low-code space. We've assembled a team to work on a new product and plan to bring it to market in 2022. We have made our initial research and need help to accelerate the development of our MVP.
## The role
### Why this is interesting
The MUI Toolpad application offers a wide variety of engineering challenges. Including
- In-browser sandboxing and manipulation of live web applications
- Drag & drop visual editor
- Realtime collaborative editing
- Interfacing with many different types of backends
- Databinding and complex state management
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- **Help guide architectural decisions**. You'll join us in defining and refining the initial product and also help bring the conversation public as the MVP grows. You'll also interface with other teams at MUI as you'll be building on top of their work.
- **Contribute to implementing new features**. MUI is a complex codebase. It's built on top of cutting-edge web technologies to build the low-code tool for the future.
- **Reduce friction**. A large amount of the work on MUI Toolpad is reducing friction and making it easier to use. As our MVP grows, our focus will shift from "making it work" towards "making it easy to work with".
- **Collaborate with the community**. MUI Toolpad will be open-sourced. As the community grows you'll act as a steward to steer it towards success. This includes reviewing issues, pull requests and questions, and guiding aspiring contributors to make meaningful contributions.
- **Experiment and play**. Great, unexpected features and heisenbug fixes have come from a number of sources — relentlessly methodical processes of elimination, free-flowing team collaboration, inspiration by adjacent libraries and projects, and difficult-to-explain individual strokes of brilliance. Whatever your preferred style is for creating new things that others might not have thought of, you'll find a welcome home on the team.
- **Take ownership of features from idea/mockup to live deployment**. You'll shape and guide the direction of crucial new features.
- **Ship. Early and often**. You'll iterate and ship frequently. You'll have a real impact on the end-user experience and you'll love working on a team that builds stunning UIs and prioritizes delivering real user value as often as possible.
- **You'll be interacting with the users** on a regular basis, handling inbound support and feature requests (every developer helps with developer requests).
## The best parts of this job
- **You'll be at the cutting edge of application development** — working on one of the fastest-growing UI libraries on the market.
- **You'll be part of an active, open, friendly community** of developers that are excited about building awesome applications.
- **Your role will be key to making MUI Toolpad the go-to low code tool** for internal application building.
## The worst parts of this job
- **We move quickly but don't sacrifice quality**. We ship early, often, and quickly. You may not be initially comfortable with the cadence with which we ship high-quality features and improvements to end-users. By doing so, we sacrifice on solving each problem 100% in exchange for fast feedback. Solving 50-70% of the issue with quality should be enough for any given iteration. Our users quickly tell us when we haven't pushed a solution far enough.
- **In open-source, you're faced with a nonstop stream of bug reports and support requests**. That means you need to develop an intuition for when to ignore something, and when to dig in further.
- As **The product is in very early stages of development**, expect to enter an environment with incomplete and quickly changing requirements.
## About you
We're looking for someone with both strong front-end and back-end skills. More important than specific technical skills though is that you're a strong problem solver who loves to learn. Details matter to you.
### Skills you should have
- **Expertise in the modern JavaScript ecosystem**. MUI Toolpad is built on the shoulders of giants, making use of technologies such as ES2021, TypeScript, Node.js, React, Next.js, webpack, and Babel.
- **Expertise in backend development**. MUI Toolpad interfaces with multiple databases, both SQL and NoSQL, as well as APIs such as REST and GraphQL. You'll need to be comfortable in learning and integrating new backend technologies fast. You'll need to have a good understanding of distributed systems and some knowledge of CRDTs is a plus.
- **A track record of demonstrating an eye for product and solving real-world user problems**. If you have a knack for solving problems at the root cause, shipping beautiful user interfaces and intuitive APIs, we want you on our team.
- **Experience building and shipping production code in a team setting** with a passion for writing tested, performant, and high-quality code.
- **Strong written and verbal communication skills**. As part of the team, you'll interface both directly and indirectly with community members and enterprise customers, and contribute to user documentation. Clear communication is fundamental in creating intuitive and compelling resources.
- **Ability to dive into complex problems**. You should be able to quickly assess, understand, and iterate upon aspects of our codebase.
- **Ready and willing to ask and answer questions**. If you're comfortable saying you're unsure, asking for help; but equally reaching out to assist others, you'll be an incredible addition to our team. We thrive because of continuous learning. First-time mistakes should be celebrated, not blamed.
- **Avoid monolithic deliverables**. You scope and stage your work into well-defined milestones to ship.
### What would be nice if you had, but isn't required
- **You've maintained an active repository before**. Maybe you've helped maintain a popular open-source repository, or perhaps you've worked on internal repositories that saw contributions from multiple teams. Previous experience with highly active repository workflows is a definite plus for this role.
- **You have contributed code to MUI before**. A history of contributing to MUI would be a definite plus.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/4f76b45b-a18e-4bdb-8a34-8bb5a3c9c2ef/application?utm_source=ZNRrPGBkqO)
## What happens next?
We start by screening applications, looking for candidates that showcase the desired skills and experience. If your application stands out, we'll contact you for a get-to-know conversation, where we'll meet each other.
If that goes well, you'll be invited to up to four additional conversations, those being:
- A technical challenge.
- A chat with one of the product managers or engineers that you will work closely with.
- A chat with one of MUI's founders.
- A possible follow-up chat if we missed addressing anything relevant in the previous conversations.
All these conversations will be 1:1 and over video chat. Please ask as many questions as you wish throughout the whole process, it's a two-way discussion. If you happen to need additional conversations as well, feel free to ask; we'll be happy to schedule them. Lastly, please note that we're unable to offer individual feedback during the initial screening process, as we're a small team and don't have the bandwidth to do so.
We look forward to hearing from you! ☺️
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,236 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/fullstack-engineer.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/full-stack-engineer.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,237 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/head-of-operations.md | # Head of Operations
<p class="description">You will take ownership of designing, implementing, and overseeing most of the business operations to support MUI's growth.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- We're a **remote** company, operating mostly asynchronously.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
We have found market fit but we increasingly don't have the tools (in the broad sense) necessary to keep up with the requests from our users.
Up to recently, the founders of MUI were the only ones to work on business operations.
There is now a tiny team of two people working to support the operations needs.
But this isn't enough, the department is increasingly a bottleneck in growing the company.
We are looking for a Head of Operations to take ownership of designing, implementing, and overseeing most of the business operations to support MUI's growth.
### Why this is interesting
Our approach to business operations is centered around operational excellence.
It involves relying on automation and writing custom code where necessary.
We are even building a product dedicated to improving internal tools for companies: https://mui.com/toolpad/ which we increasingly rely on internally.
You will likely use it a lot to improve processes.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
## The role
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- Oversee and manage the day-to-day operations of the company, including finance, IT, support, and legal.
- Lead and manage the operations team, including recruiting, training, and developing team members.
- Build and develop KPI dashboards (writing code if necessary) to be able to measure business health and performance.
- Work on keeping the financial model up to date and on accurate forecasts.
- Figuring out what to work on: working with the CEO and other leadership team members to identify and prioritize key initiatives and projects.
- Support the CEO for investor relations and fundraising.
- Implement a replacement to Google Group to scale email notifications (we use emails for the tasks of the ops team).
- Work toward SOC 2 certification.
- Migrate from Sendinblue to SendGrid.
- Oversee our US flip.
- Develop and implement strategies to support the growth and success of the company
- Create new [Toolpad apps](https://mui.com/toolpad/) to streamline the operations (could require some SQL & JavaScript skills).
## About you
### Skills you should have
- Obsessive over the details, aiming for inbox zero.
- JavaScript & SQL code proficiency as a lot of our operations rely on it.
- Excellent written and verbal communication skills.
- Demonstrable competency in strategic planning and business development.
- Strong analytical, and problem-solving skills, with the ability to make data-driven decisions.
- A high sense of curiosity, enjoying self-learning to get things done. You are [versatile](https://review.firstround.com/the-adaptable-leader-is-the-new-holy-grail-become-one-hire-one).
- Excited about the ambiguity of an entrepreneurial, growing company, and able to juggle many projects and responsibilities.
- Bachelor's degree in a related field (e.g. computer science, business management).
- 1+ year of experience in a similar role.
### What would be nice if you had, but isn't required
- 3+ years of experience in a similar role.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/86ab11dc-0320-4e14-9b5b-7c8b3fb5bb71/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,238 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/people-operation-manager.md | # People Operations Manager
<p class="description">Build the HR function from the ground up at a high-growth tech company.</p>
## Details of the role
- **Location**: Remote (strong requirement for UTC-6 to UTC+4).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
At the current growth rate, we target 50 new hires in 2023. We would reach 75 people.
We need somebody to lead our HR strategy including hiring, onboarding, diversity & inclusion, learning & development, and employee happiness.
## The role
### Why this is interesting
You'll have the freedom to implement processes and to drive change across the organization.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- **Recruiting**. You will help scale recruiting and improve the employer brand. It might take up to 50% of the time in the early days, and we will quickly need to hire a Tech Recruiter.
- **Employees' experience**.
- You will work on the employee engagement survey results.
- You will reduce the admin burden.
- You will own the Retreat. Bring our remote team together. Being a fully distributed remote team has its challenges. You organize team events, make sure everybody has what they need to be productive, and find creative ways to engage as a team.
- **Employee development**. You will improve program for evaluating performance and providing feedback. Our team members need continual learning.
- **Culture development**. You will develop our remote and async-first culture. You will continue to train and mentor the team to update information in the handbook, for easy access to all.
- **Connecting individual performance with company goals**.
- You will help all individuals understand their primary role within the wider organization.
- You will partner with Finance for budgeting/compensation purposes. You will manage compensation, benefits, leave, and other people-related matters.
- You will shape a strategy that aligns and moves MUI towards continued growth, innovation, and improvement.
- **Legal compliance**. You will stay current on employee legislation and develop internal policies and procedures to support a scaling company; serve as the main point of contact for administrative matters.
## About you
You are a [manager of one](https://signalvnoise.com/posts/1430-hire-managers-of-one).
This role is perfect for you if you are curious, enjoy taking risks, and learning.
### Skills you should have
- 4+ years of experience as an HR business partner, preferably with experience at fast-growing technology companies.
- A great listener who enjoys interacting with others and is open to feedback.
- Excellent verbal and written communications skills that will enable you to develop relationships with all members of our team, regardless of tenure or position.
- Experience implementing HR programs such as compensation review process, HR compliance, and employee development/growth.
- Able to handle confidential information with discretion and deal with professionals inside and outside the company.
- Tech-savvy with the ability to learn new tools quickly and find tools to help automate workflows.
- A self-starter looking to grow and willing to own projects from start to finish with limited supervision.
### What would be nice if you had, but isn't required
- Basic knowledge of web development.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/b46968b7-dde3-4b91-9785-a05aa0a816d8/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,239 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/product-engineer.md | # Product Engineer - Store
<p class="description">You will lead the technical, product, and operational development of the store.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
The development and operations of the store are currently almost exclusively run by the executive team of the company (the co-founders).
This team doesn't have enough bandwidth, the store doesn't receive the care it deserves.
You will be responsible to step up and carry forward the development of the store on new fronts.
### Why this is interesting
You will get the opportunity to work on many different topics.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
## The role
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- Take initiatives to grow the sales of the templates
- Define the product direction
- Review new items submitted by the contributors to be hosted on the marketplace
- Fix root problems raised by store customers on the support channels
- Take care of operational needs, e.g. automate payouts, create sales reports
### Here are a few initiatives you might work on
Tasks that you might work on once you join:
- Explore ways to provide a theme builder/sell themes on the platform that deeply integrate with MUI Core and the documentation.
- Develop the SEA & SEO strategy, create new blog posts, try retargeting, Google Ads, etc.
- Improve the fulfillment workflow of MUI X Pro & Premium.
- Develop a Figma plugin & backend to push [MUI for Figma](https://mui.com/store/items/figma-react/) to reduce the collaboration friction between designers and developers.
- Add a search page to scale the hosting to more items from contributors.
- Revamp the design of the store to match the new brand of mui.com.
- Migrate the store from Gatsby to Next.js or Remix. Gatsby was introduced at a point in time when it had more downloads than Next.js. Our CEO has experience with Next.js since 2017 but wanted to ensure that MUI was supporting Gatsby well too.
This requirement [is no longer relevant](https://npm-stat.com/charts.html?package=next&package=gatsby), and since the DX of Next.js is significantly better, time to migrate.
## About you
We're looking for someone with strong development skills, and more important than specific technical skills a strong problem solver who loves to learn new things. Details matter to you.
This role is perfect for you if you are curious, have tenacity, enjoy tacking risk, and care about design.
You are a [manager of one](https://signalvnoise.com/posts/1430-hire-managers-of-one).
### Skills you should have
- **Expertise in modern JavaScript ecosystem.** The store is currently build on WooCommerce so expertise in WordPress/PHP could help. Our backend technology of choice is Node.js.
- **A track record of demonstrating an eye for product and solving real-world user problems**. If you have a knack for solving problems at the root cause, finding boring solutions, we want you on our team.
- **Strong written and verbal communication skills**.
As part of the team, you'll interface both directly and indirectly with community members and enterprise customers, and contribute to user documentation. Clear communication is fundamental in creating intuitive and compelling resources.
- **Ability to dive into complex problems**.
You should be able to quickly assess, understand, and iterate upon aspects of our codebase.
- **Ready and willing to ask and answer questions**.
If you're comfortable saying you're unsure, asking for help; but equally reaching out to assist others, you'll be an incredible addition to our team. We thrive because of continuous learning. First-time mistakes should be celebrated, not blamed.
- **Avoid monolithic deliverables**.
You scope and stage your work into well-defined milestones to ship.
### What it would be nice if you had, but isn't required
- **Has or is pursuing a business side project**. You owned a side project generating revenues on the side of your full-time job. You were doing whatever was necessary to solve people's pain.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/e641bac3-5538-4ec8-8d73-eaa1a03704d6/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,240 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/product-manager.md | # Product Manager
<p class="description">We are looking for a product manager to guide our roadmap and build a great product.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
Our mission is to empower as many people as possible to build great UIs, faster.
The faster and simpler it is, and the broader the audience that can create custom UIs, the better.
We believe that the best way to improve on these dimensions is to eliminate [80%](https://www.youtube.com/watch?v=GnO7D5UaDig&t=2451s) of the code that has to be written: low-code.
### Why this is interesting
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
But providing React components isn't enough.
In our [last developer survey](https://mui.com/blog/2021-developer-survey-results/), we learned that the majority of our audience are full-stack developers.
They are looking for ways to move faster.
They are working on a couple of new projects every year, and where the integration between the UI and the database is key.
You will initiate the exploration of a bold new product vertical.
## The role
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- You will coordinate with the engineering to ensure that the product being delivered at each iteration solves the problem.
This involves growing a deep understanding of our technical choices and constraints.
- You will drive the growth of the product by owning KPIs.
- You will grow and cultivate a deep understanding of the problems that developers have when they create simple applications (e.g. admins, prototypes). This means that you will observe and reach out to the community, run research interviews and share your insights with the team.
- You will keep a close eye on feature requests, issues, and general improvements, to curate opportunities based on our strategy.
- You will build a strategy for your product area and contribute to the overall product strategy, e.g. establishing a go-to-market strategy.
- You will assess the impact of initiatives through telemetry data and qualitative feedback to help us develop our understanding further, and decide on the next steps.
## About you
### Skills you should have
- 3+ years experience as Product Manager or closely related roles such as Product Owner, Program Manager, or Solutions Architect.
- Able to switch between the big picture and detailed view multiple times a day.
### What it would be nice if you had, but isn't required
- Experience building developer tools.
- Experience working with open-source and having interacted with open-source communities.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/__ID__/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,241 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/product-marketing-manager.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/product-marketing-manager.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,242 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/product-marketing-manager.md | # Product Marketing Manager (future role)
<p class="description">You will own the marketing efforts at MUI.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: _No ladders created yet_.
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
Up to this point we have operated:
- on the open-source side, through word of mouth and SEO
- on the commercial side, through inbound leads with $0 investment in marketing
We believe that we could do a lot better. This is a white canvas opportunity at the company, this role is critical to our growth plans. Product Marketing will be a cross-functional role at MUI, partnering with Design, Product, Developer Experience and Sales.
### Why this is interesting
In this role, you will be a founding member of the marketing team and a passionate voice of our users, customers and prospects. This is a full stack product marketing role in that you will support messaging and positioning, sales materials and training, web copy, customer collateral and presentations, and act as the subject matter expert for the value of our product among the enterprise and SMB audiences.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
## The role
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- **Own the commercial voice of MUI**. Define, document, and evolve the way we communicate with our customers, users, and the market/public.
- **Personas**. Build deep knowledge and understanding of MUI's technical buyer personas and the journey of our enterprise prospects via market research, prospect/customer conversations, and internal conversations.
- **Market research**. Use customer and competitive research to tailor effective messaging to our Enterprise audience.
- **Content**. Plan and create impactful marketing materials mapped to buying journey. Generate high-quality content for customers including website copy/landing pages, blogs, webinar content, use cases, customer stories, showcases, and more.
- **Paid channels**. Build and help execute marketing campaigns from the bottom up (identify goals, risks, audience, messages, and tactics), e.g. we can explore SEA & conference sponsoring.
- **Sales**. Partner with the Sales team to create effective sales enablement materials.
- **Events** Potentially: Lead corporate event programs that result in relationship building, lead/pipeline generation and acceleration, customer engagement, retention, and brand awareness.
## About you
### Skills you should have
- A technical background.
- Experience marketing to software developers.
- 2+ years experience of B2B product marketing.
- As the first role, you'll need to bring an entrepreneurial, iterative mindset and be comfortable driving for clarity in ambiguous situations. When this is a success, you'll have an opportunity to help build the team.
- Proven ability to be self-directed and work with limited supervision.
- Passionate, self-starter with a can-do attitude. You're eager to jump in and get things done but don't get flustered in a fast-paced and often changing environment. Always willing to roll up your sleeves and get scrappy.
- Strong critical thinker who feels comfortable pouring over analytics to make data-driven decisions, and explaining those decisions to leadership with the data.
- Empathy: for our customers, for the team, and for yourself.
- Outstanding written English communication skills. An ability to explain and translate complex technical concepts into simple and intuitive communications.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/7811fc99-08b2-4fb3-b6c3-6af15fc7467a/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,243 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-community-engineer.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/react-community-engineer.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,244 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-community-engineer.md | # React Community Engineer - X (future role)
<p class="description">You will provide guidance to the community and solve their struggle, working primarily in the advanced components team.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
We need a Community Engineer to solve friction points of users.
We face challenges on multiple fronts:
- As a result of this growth, we (will) have more users questions and feedback coming in than ever before.
- The commercial version of the library is growing, but our community of developers is still small and has a reduced incentive to contribute compared to the community plan.
- Software engineers at MUI are tasked with doing support, however, they could benefit from the help of a dedicated person in the company, for instance to improve the workflows and tooling.
- The MUI X Premium plan will offer a technical advisor service, we need a Community Engineer to help deliver it.
## The role
### Why this is interesting
You will be a key member of the Developer Experience's team and will directly impact customer satisfaction and success.
You will troubleshoot and depending on your bandwidth also fix complex issues related to MUI.
At MUI a Community Engineer is considered a developer, it's a person that enjoys optimizing what already exists but is also eager to help our users with features that are requested by the community.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
### What you'll do on a day-to-day basis
You will own the following responsibilities:
- **Build product knowledge**. You will continually research and learn the current and future best practices of using MUI.
- **Resolve users' issues**. You will solve these issues at two levels:
- On the surface, you will answer developers on GitHub, Zendesk, Twitter, email, Slack.
- At the root, you will create/update the documentation, fix bugs in collaboration with the relevant developer, implement community driven features and more.
- **Provide feedback**. You will work alongside product managers to define and shape the product goals, roadmap, priorities, and strategy based on your frontline knowledge of customer needs.
- **Operations**.
- You will establish key support metrics and identify how best to measure them.
- You will establish a workflow to reduce 'time to response' and 'time to fix' that can scale to multiple team members.
- You will identify where internal tooling might be developed or obtained to improve support efficiency.
For the right candidate:
- Working with the Leadership to construct and execute a hiring plan to grow the community team.
Depending on the day, you'll:
- **You'll be interacting with the users** on a regular basis, handling inbound support and feature requests (every developer helps with developer requests).
- **Reduce friction**.
A large amount of the work on MUI is reducing friction and making it easier to use.
This might involve careful API design, identifying and fixing top bugs, creating easier-to-understand error messages, and writing documentation and blog posts about features you ship.
- **Collaborate with the community**.
Many small, as well as meaningful fixes and features, have been contributed by the community. Your role is to draw the best out of the community — to inspire those across the world to create and contribute through your reviews of their issues and pull requests.
- **Experiment and play**. Great, unexpected features and heisenbug fixes have come from a number of sources — relentlessly methodical processes of elimination, free-flowing team collaboration, inspiration by adjacent libraries and projects, and difficult-to-explain individual strokes of brilliance. Whatever your preferred style is for creating new things that others might not have thought of, you'll find a welcome home on the team.
- **Ship. Early and often**. You'll iterate and ship frequently.
You'll have a real impact on the end-user experience and you'll love working on a team that builds stunning UIs and prioritizes delivering real user value as often as possible.
## About you
We're looking for someone with strong front-end skills. More important than specific technical skills though is that you're a strong problem solver who loves to learn. Details matter to you.
### Skills you should have
- **Expertise in the modern JavaScript ecosystem**.
MUI is built on the shoulders of giants, making use of technologies such as ES2021, TypeScript, Node.js, React, Next.js, webpack, and Babel.
- **A track record of demonstrating an eye for product and solving real-world user problems**. If you have a knack for solving problems at the root cause, shipping beautiful user interfaces and intuitive APIs, we want you on our team.
- **Strong written and verbal communication skills**.
As part of the team, you'll interface both directly and indirectly with community members and enterprise customers, and contribute to user documentation. Clear communication is fundamental in creating intuitive and compelling resources.
- **Ability to dive into complex problems**.
You should be able to quickly assess, understand, and iterate upon aspects of our codebase.
- **Ready and willing to ask and answer questions**.
If you're comfortable saying you're unsure, asking for help; but equally reaching out to assist others, you'll be an incredible addition to our team. We thrive because of continuous learning. First-time mistakes should be celebrated, not blamed.
- **Avoid monolithic deliverables**.
You scope and stage your work into well-defined milestones to ship.
- **Past work with front-end infrastructure**.
Perhaps you've created your company's design system, written a Babel plugin, or written complex React components.
It would be great if you could address this in your cover letter!
### What would be nice if you had, but isn't required
- **You've contributed to a design system before**.
You have worked on enterprise components in the past, maybe for internal use in your company.
You have built complex and advanced features while making sure the accessibility was fully functional.
- **You've maintained an active repository before**.
Maybe you've helped maintain a popular open-source repository, or perhaps you've worked on internal repositories that saw contributions from multiple teams.
Previous experience with highly active repository workflows is a definite plus for this role.
- **You have contributed code to MUI before**. A history of contributing to MUI would be a definite plus.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/e362a14c-6674-4ac9-8eee-bcf44a8767c8/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,245 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-engineer-core.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/react-engineer-core.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,246 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-engineer-core.md | # React Engineer - Core (future role)
<p class="description">You will strengthen the core components team by collaborating with the community to land contributions.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
The core components team (MUI Core) needs help.
They are working on 4 products (Material UI, Base UI, Joy UI, and MUI System) with a tiny team.
We also need help to continue to improve the health of the open-source product: make the core components easier to use, increase the contributions by engaging and collaborating with the community, polish all the details, make the components more accessible, guide developers to answers, and just generally be a positive presence in the open-source community.
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
## The role
### Why this is interesting
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
The core components are widely used, you will receive a lot of feedback on your work.
The community has high expectations, they will push you to do better, every day.
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- **Help guide architectural decisions**.
The future of MUI is discussed and planned in our public RFCs and issues.
You'll be helping drive these conversations and guiding MUI toward the best possible solutions.
- **Contribute to deep, meaningful refactors and feature releases**.
MUI is a complex codebase. Components we've shipped recently, such as the unstyled components have required months of dedicated, careful work.
- **Reduce friction**.
A large amount of the work at MUI is about reducing friction and making our products easier to use.
This might involve careful API design, identifying and fixing top bugs, creating error messages that are easier-to-understand, and writing documentation and blog posts about features you ship.
- **Collaborate with the community**.
Many small, as well as meaningful fixes and features, have been contributed by the community.
Your role is to draw the best out of the community — to inspire those across the world to create and contribute through your reviews of their issues and pull requests.
- **Experiment and play**.
Great, unexpected features and heisenbug fixes have come from a number of sources — relentlessly methodical processes of elimination, free-flowing team collaboration, inspiration by adjacent libraries and projects, and difficult-to-explain individual strokes of brilliance.
Whatever your preferred style is for creating new things that others might not have thought of, you'll find a welcome home on the team.
- **Take ownership of features from idea/mockup to live deployment**.
You'll shape and guide the direction of crucial new features, including new components.
- **Ship. Early and often**.
You'll iterate and ship frequently.
You'll have a real impact on the end-user experience and you'll love working on a team that builds stunning UIs and prioritizes delivering real user value as often as possible.
- **You'll be interacting with the users** on a regular basis, handling inbound support and feature requests (every developer helps with developer requests).
### The best parts of this job
- **You'll be at the cutting edge of application development** — working on one of the fastest-growing UI libraries on the market.
- **You'll be part of an active, open, friendly community** of developers that are excited about building awesome applications.
- **Your role will be key to making MUI the go-to UI framework** for building applications, websites, and design systems with React.
### The worst parts of this job
- **Shifting context.**
You will necessarily have to shift context and dive into a different feature before the current one is done.
It may even be in an area of the codebase you're unfamiliar with or don't have a ton of understanding about.
It's fun and rewarding work, but it can be very challenging.
- **We move quickly but don't sacrifice quality**.
We ship early, often, and quickly.
You may not be initially comfortable with the cadence with which we ship high-quality features and improvements to end users.
By doing so, we compromise on solving each problem 100% in favor of a shorter feedback loop.
Solving 50-70% of the issue with quality should be enough for any given iteration.
Our users quickly tell us when we haven't pushed a solution far enough.
- **MUI is a large codebase**.
You may bang your head against the wall at times, and then write tests to assist your future self. 😌
The work you will be doing is somewhat unique and idiosyncratic. You probably have not had a similar role before.
- **In open-source, you're faced with a nonstop stream of bug reports and support requests**.
That means you need to develop an intuition for when to ignore something, and when to dig in further.
## About you
We're looking for someone with strong front-end skills.
More important than specific technical skills, though, is that you're a strong problem solver who loves to learn.
Details matter to you.
### Skills you should have
- **Expertise in the modern JavaScript ecosystem**.
MUI is built on the shoulders of giants, making use of technologies such as ES2021, TypeScript, Node.js, React, Next.js, webpack, and Babel.
- **A track record of demonstrating an eye for product and solving real-world user problems**.
If you have a knack for getting to the root of a problem while shipping beautiful user interfaces and intuitive APIs, we want you on our team.
- **Experience building and shipping production code in a team setting** with a passion for writing tested, performant, and high-quality code.
- **Strong written and verbal communication skills**.
As part of the team, you'll interface both directly and indirectly with community members and enterprise customers, and contribute to user documentation.
Clear communication is fundamental for creating intuitive and compelling resources.
- **Ability to dive into complex problems**.
You should be able to quickly assess, understand, and iterate upon aspects of our codebase.
- **Ready and willing to ask and answer questions**.
You should be equally comfortable asking for _and_ offering help when needed.
We thrive because of continuous learning.
First-time mistakes should be celebrated, not blamed.
- **Avoid monolithic deliverables**.
You scope and stage your work into well-defined milestones to ship.
- **Past work with front-end infrastructure**.
Perhaps you've created your company's design system, written a Babel plugin, or written complex React components.
It would be great if you could address this in your cover letter!
### What it would be nice if you had, but isn't required
- **You've contributed to a design system before**.
You have worked on enterprise components in the past, maybe for internal use in your company.
You have built complex and advanced features while making sure the accessibility was fully functional.
- **You've maintained an active repository before**.
Maybe you've helped maintain a popular open-source repository, or perhaps you've worked on internal repositories that saw contributions from multiple teams.
Previous experience with highly active repository workflows is a definite plus for this role.
- **You have contributed code to MUI before**.
We would be thrilled to hire directly from our community contributors.
- **You have experience with accessibility**.
Maybe you've been involved in bringing a11y compliance to your company's design system or application.
We would greatly benefit from having someone on the team who could take ownership of this.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/e6d7cc26-3003-442f-bafb-464373fb2624/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,247 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-engineer-x-charts.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/react-engineer-x-charts.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,248 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-engineer-x-charts.md | # React Engineer - xCharts
<p class="description">You will help form the xCharts team, build ambitious and complex new features, work on strategic problems, and help grow adoption.</p>
## Details of the role
- **Location**: Remote (strong preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
The charts team (part of MUI X) needs your help.
The component is off to [a great start](https://npm-stat.com/charts.html?package=%40mui%2Fx-charts&from=2021-06-01), however we have only started to scratch the surface for the potential of this component. There is x10 more to build.
To be more specific in what we are aiming to achieve in the short to mid-term:
- A tighter integration with the rest of the MUI libraries including Material UI and MUI X Data Grid
- Faster iteration cycles compared to popular open-source alternatives such as chart.js and Recharts
This should allow us to reach 30% of the downloads of alternative React charting libraries, considering benchmark data in the short term. Developers value having a single touch point, but also one they trust, and one that integrates well into the rest of their application.
In the mid-term, we aspired for this charting library to become a standard in the React ecosystem, outgrowing Material UI or any other UI library.
We believe we can achieve this with an open-core model.
We will at least match the features available in the alternative open-source projects, licensed as MIT in MUI X Charts.
We will then provide extra paid features so developers can use a single charting library, without the need to juggle with paid alternatives as they do today.
In the long term, we envision using the pro-code charting API as a distribution channel for building more abstract charting primitives, using low-code and AI.
## The role
### Why this is interesting
The advanced components portfolio is still small, with a million interesting and challenging problems to solve.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- **Help guide architectural decisions**.
The future of MUI is discussed and planned in our public RFCs and issues.
You'll be helping drive these conversations and guiding MUI toward the best possible solutions.
- **Contribute to deep, meaningful refactors and feature releases**.
MUI is a complex codebase. Components we've shipped recently, such as the data grid and date pickers have required months of dedicated, careful work.
- **Reduce friction**.
A large amount of the work on MUI is reducing friction and making it easier to use.
This might involve careful API design, identifying and fixing top bugs, creating easier-to-understand error messages, and writing documentation and blog posts about features you ship.
- **Collaborate with the community**.
Many small, as well as meaningful fixes and features, have been contributed by the community. Your role is to draw the best out of the community — to inspire those across the world to create and contribute through your reviews of their issues and pull requests.
- **Experiment and play**. Great, unexpected features and heisenbug fixes have come from a number of sources — relentlessly methodical processes of elimination, free-flowing team collaboration, inspiration by adjacent libraries and projects, and difficult-to-explain individual strokes of brilliance. Whatever your preferred style is for creating new things that others might not have thought of, you'll find a welcome home on the team.
- **Take ownership of features from idea/mockup to live deployment**.
You'll shape and guide the direction of crucial new features, including new components.
- **Ship. Early and often**. You'll iterate and ship frequently.
You'll have a real impact on the end-user experience and you'll love working on a team that builds stunning UIs and prioritizes delivering real user value as often as possible.
- **You'll be interacting with the users** on a regular basis, handling inbound support and feature requests (every developer helps with developer requests).
### The best parts of this job
- **You'll be at the cutting edge of application development** — working on one of the fastest-growing UI libraries on the market.
- **You'll be part of an active, open, friendly community** of developers that are excited about building awesome applications.
- **Your role will be key to making MUI the go-to UI framework** for building applications, websites, and design systems with React.
### The worst parts of this job
- **Shifting context.**
You will necessarily have to shift context and dive into a different feature before the current one is done.
It may even be in an area of the codebase you're unfamiliar with or don't have a ton of understanding about.
It's fun, rewarding work, but it can be very challenging.
- **We move quickly but don't sacrifice quality**.
We ship early, often, and quickly. You may not be initially comfortable with the cadence with which we ship high-quality features and improvements to end-users. By doing so, we sacrifice on solving each problem 100% in exchange for fast feedback. Solving 50-70% of the issue with quality should be enough for any given iteration. Our users quickly tell us when we haven't pushed a solution far enough.
- **MUI is a large codebase**. You may bang your head against the wall at times, and then write tests to assist future you 😌.
The work you will be doing is somewhat unique and idiosyncratic. You probably have not had a similar role before.
- **In open-source, you're faced with a nonstop stream of bug reports and support requests**. That means you need to develop an intuition for when to ignore something, and when to dig in further.
## About you
We're looking for someone with strong front-end skills. More important than specific technical skills though is that you're a strong problem solver who loves to learn. Details matter to you.
### Skills you should have
- **Expertise in the modern JavaScript ecosystem**.
MUI is built on the shoulders of giants, making use of technologies such as ES2021, TypeScript, Node.js, React, Next.js, webpack, and Babel.
- **A track record of demonstrating an eye for product and solving real-world user problems**. If you have a knack for solving problems at the root cause, shipping beautiful user interfaces and intuitive APIs, we want you on our team.
- **Experience building and shipping production code in a team setting** with a passion for writing tested, performant, and high-quality code.
- **Strong written and verbal communication skills**.
As part of the team, you'll interface both directly and indirectly with community members and enterprise customers, and contribute to user documentation. Clear communication is fundamental in creating intuitive and compelling resources.
- **Ability to dive into complex problems**.
You should be able to quickly assess, understand, and iterate upon aspects of our codebase.
- **Ready and willing to ask and answer questions**.
If you're comfortable saying you're unsure, asking for help; but equally reaching out to assist others, you'll be an incredible addition to our team. We thrive because of continuous learning. First-time mistakes should be celebrated, not blamed.
- **Experience or interest in drawing technologies**.
Charts use SVG and canvas which implies using other API than HTML/CSS. Hope you know them or enjoy discovering new documentation.
- **Avoid monolithic deliverables**.
You scope and stage your work into well-defined milestones to ship.
- **Past work with front-end infrastructure**.
Perhaps you've created your company's design system, written a Babel plugin, or written complex React components.
It would be great if you could address this in your cover letter!
### What it would be nice if you had, but isn't required
- **You've experience with charts**.
You have contributed to building chart libraries, integrated charts in a design system, or contributed to chart intensive applications.
You have built complex and advanced features while making sure the accessibility was fully functional.
- **You've contributed to a design system before**.
You have worked on enterprise components in the past, maybe for internal use in your company.
You have built complex and advanced features while making sure the accessibility was fully functional.
- **You've maintained an active repository before**.
Maybe you've helped maintain a popular open-source repository, or perhaps you've worked on internal repositories that saw contributions from multiple teams.
Previous experience with highly active repository workflows is a definite plus for this role.
- **You have contributed code to MUI before**. A history of contributing to MUI would be a definite plus.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/2a1b0084-53aa-4aca-84ec-f8cfe25093ae/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,249 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-engineer-x-grid.md | # React Engineer - xGrid
<p class="description">You will strengthen the Data Grid team, build ambitious and complex new features, work on strategic problems, and help grow adoption.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
The data grid team (part of MUI X) needs help.
We have started with the [data grid](https://mui.com/x/react-data-grid/#commercial-version) component.
We need to build new features on it and introduce new components.
The enterprise version is built on the open-source version of the components.
We also need help to continue to improve the health of the open-source product: make the advanced components easier to use, make it support more use cases, improve performance, make it more accessible, increase the contributions by engaging and collaborating with the community, guide developers to answers, and just generally be a positive presence in the open-source community.
## The role
### Why this is interesting
The advanced components portfolio is still small, with a million interesting and challenging problems to solve.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- **Help guide architectural decisions**.
The future of MUI is discussed and planned in our public RFCs and issues.
You'll be helping drive these conversations and guiding MUI toward the best possible solutions.
- **Contribute to deep, meaningful refactors and feature releases**.
MUI is a complex codebase. Components we've shipped recently, such as the data grid have required months of dedicated, careful work.
- **Reduce friction**.
A large amount of the work on MUI is reducing friction and making it easier to use.
This might involve careful API design, identifying and fixing top bugs, creating easier-to-understand error messages, and writing documentation and blog posts about features you ship.
- **Collaborate with the community**.
Many small, as well as meaningful fixes and features, have been contributed by the community. Your role is to draw the best out of the community — to inspire those across the world to create and contribute through your reviews of their issues and pull requests.
- **Experiment and play**. Great, unexpected features and heisenbug fixes have come from a number of sources — relentlessly methodical processes of elimination, free-flowing team collaboration, inspiration by adjacent libraries and projects, and difficult-to-explain individual strokes of brilliance. Whatever your preferred style is for creating new things that others might not have thought of, you'll find a welcome home on the team.
- **Take ownership of features from idea/mockup to live deployment**.
You'll shape and guide the direction of crucial new features, including new components.
- **Ship. Early and often**. You'll iterate and ship frequently.
You'll have a real impact on the end-user experience and you'll love working on a team that builds stunning UIs and prioritizes delivering real user value as often as possible.
- **You'll be interacting with the users** on a regular basis, handling inbound support and feature requests (every developer helps with developer requests).
### The best parts of this job
- **You'll be at the cutting edge of application development** — working on one of the fastest-growing UI libraries on the market.
- **You'll be part of an active, open, friendly community** of developers that are excited about building awesome applications.
- **Your role will be key to making MUI the go-to UI framework** for building applications, websites, and design systems with React.
### The worst parts of this job
- **Shifting context.**
You will necessarily have to shift context and dive into a different feature before the current one is done.
It may even be in an area of the codebase you're unfamiliar with or don't have a ton of understanding about.
It's fun, rewarding work, but it can be very challenging.
- **We move quickly but don't sacrifice quality**.
We ship early, often, and quickly. You may not be initially comfortable with the cadence with which we ship high-quality features and improvements to end-users. By doing so, we sacrifice on solving each problem 100% in exchange for fast feedback. Solving 50-70% of the issue with quality should be enough for any given iteration. Our users quickly tell us when we haven't pushed a solution far enough.
- **MUI is a large codebase**. You may bang your head against the wall at times, and then write tests to assist future you 😌.
The work you will be doing is somewhat unique and idiosyncratic. You probably have not had a similar role before.
- **In open-source, you're faced with a nonstop stream of bug reports and support requests**. That means you need to develop an intuition for when to ignore something, and when to dig in further.
## About you
We're looking for someone with strong front-end skills. More important than specific technical skills though is that you're a strong problem solver who loves to learn. Details matter to you.
### Skills you should have
- **Expertise in the modern JavaScript ecosystem**.
MUI is built on the shoulders of giants, making use of technologies such as ES2021, TypeScript, Node.js, React, Next.js, webpack, and Babel.
- **A track record of demonstrating an eye for product and solving real-world user problems**. If you have a knack for solving problems at the root cause, shipping beautiful user interfaces and intuitive APIs, we want you on our team.
- **Experience building and shipping production code in a team setting** with a passion for writing tested, performant, and high-quality code.
- **Strong written and verbal communication skills**.
As part of the team, you'll interface both directly and indirectly with community members and enterprise customers, and contribute to user documentation. Clear communication is fundamental in creating intuitive and compelling resources.
- **Ability to dive into complex problems**.
You should be able to quickly assess, understand, and iterate upon aspects of our codebase.
- **Ready and willing to ask and answer questions**.
If you're comfortable saying you're unsure, asking for help; but equally reaching out to assist others, you'll be an incredible addition to our team. We thrive because of continuous learning. First-time mistakes should be celebrated, not blamed.
- **Avoid monolithic deliverables**.
You scope and stage your work into well-defined milestones to ship.
- **Past work with front-end infrastructure**.
Perhaps you've created your company's design system, written a Babel plugin, or written complex React components.
It would be great if you could address this in your cover letter!
### What it would be nice if you had, but isn't required
- **You've contributed to a design system before**.
You have worked on enterprise components in the past, maybe for internal use in your company.
You have built complex and advanced features while making sure the accessibility was fully functional.
- **You've maintained an active repository before**.
Maybe you've helped maintain a popular open-source repository, or perhaps you've worked on internal repositories that saw contributions from multiple teams.
Previous experience with highly active repository workflows is a definite plus for this role.
- **You have contributed code to MUI before**. A history of contributing to MUI would be a definite plus.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/77584e4c-9379-45f3-a294-6e50bf250383/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,250 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-engineer-x.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/react-engineer-x.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,251 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-engineer-x.md | # React Engineer - X
<p class="description">You will strengthen the MUI X product, build ambitious and complex new features, work on strategic problems, and help grow adoption.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [4 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
We also need help to continue to improve the health of the open-source product: make the advanced components easier to use, make it support more use cases, improve performance, make it more accessible, increase the contributions by engaging and collaborating with the community, guide developers to answers, and just generally be a positive presence in the open-source community.
## The role
### Why this is interesting
The advanced components portfolio is still small, with a million interesting and challenging problems to solve.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- **Help guide architectural decisions**.
The future of MUI is discussed and planned in our public RFCs and issues.
You'll be helping drive these conversations and guiding MUI toward the best possible solutions.
- **Contribute to deep, meaningful refactors and feature releases**.
MUI is a complex codebase. Components we've shipped recently, such as the data grid and date pickers have required months of dedicated, careful work.
- **Reduce friction**.
A large amount of the work on MUI is reducing friction and making it easier to use.
This might involve careful API design, identifying and fixing top bugs, creating easier-to-understand error messages, and writing documentation and blog posts about features you ship.
- **Collaborate with the community**.
Many small, as well as meaningful fixes and features, have been contributed by the community. Your role is to draw the best out of the community — to inspire those across the world to create and contribute through your reviews of their issues and pull requests.
- **Experiment and play**. Great, unexpected features and heisenbug fixes have come from a number of sources — relentlessly methodical processes of elimination, free-flowing team collaboration, inspiration by adjacent libraries and projects, and difficult-to-explain individual strokes of brilliance. Whatever your preferred style is for creating new things that others might not have thought of, you'll find a welcome home on the team.
- **Take ownership of features from idea/mockup to live deployment**.
You'll shape and guide the direction of crucial new features, including new components.
- **Ship. Early and often**. You'll iterate and ship frequently.
You'll have a real impact on the end-user experience and you'll love working on a team that builds stunning UIs and prioritizes delivering real user value as often as possible.
- **You'll be interacting with the users** on a regular basis, handling inbound support and feature requests (every developer helps with developer requests).
### The best parts of this job
- **You'll be at the cutting edge of application development** — working on one of the fastest-growing UI libraries on the market.
- **You'll be part of an active, open, friendly community** of developers that are excited about building awesome applications.
- **Your role will be key to making MUI the go-to UI framework** for building applications, websites, and design systems with React.
### The worst parts of this job
- **Shifting context.**
You will necessarily have to shift context and dive into a different feature before the current one is done.
It may even be in an area of the codebase you're unfamiliar with or don't have a ton of understanding about.
It's fun, rewarding work, but it can be very challenging.
- **We move quickly but don't sacrifice quality**.
We ship early, often, and quickly. You may not be initially comfortable with the cadence with which we ship high-quality features and improvements to end-users. By doing so, we sacrifice on solving each problem 100% in exchange for fast feedback. Solving 50-70% of the issue with quality should be enough for any given iteration. Our users quickly tell us when we haven't pushed a solution far enough.
- **MUI is a large codebase**. You may bang your head against the wall at times, and then write tests to assist future you 😌.
The work you will be doing is somewhat unique and idiosyncratic. You probably have not had a similar role before.
- **In open-source, you're faced with a nonstop stream of bug reports and support requests**. That means you need to develop an intuition for when to ignore something, and when to dig in further.
## About you
We're looking for someone with strong front-end skills. More important than specific technical skills though is that you're a strong problem solver who loves to learn. Details matter to you.
### Skills you should have
- **Expertise in the modern JavaScript ecosystem**.
MUI is built on the shoulders of giants, making use of technologies such as ES2021, TypeScript, Node.js, React, Next.js, webpack, and Babel.
- **A track record of demonstrating an eye for product and solving real-world user problems**. If you have a knack for solving problems at the root cause, shipping beautiful user interfaces and intuitive APIs, we want you on our team.
- **Experience building and shipping production code in a team setting** with a passion for writing tested, performant, and high-quality code.
- **Strong written and verbal communication skills**.
As part of the team, you'll interface both directly and indirectly with community members and enterprise customers, and contribute to user documentation. Clear communication is fundamental in creating intuitive and compelling resources.
- **Ability to dive into complex problems**.
You should be able to quickly assess, understand, and iterate upon aspects of our codebase.
- **Ready and willing to ask and answer questions**.
If you're comfortable saying you're unsure, asking for help; but equally reaching out to assist others, you'll be an incredible addition to our team. We thrive because of continuous learning. First-time mistakes should be celebrated, not blamed.
- **Avoid monolithic deliverables**.
You scope and stage your work into well-defined milestones to ship.
- **Past work with front-end infrastructure**.
Perhaps you've created your company's design system, written a Babel plugin, or written complex React components.
It would be great if you could address this in your cover letter!
### What it would be nice if you had, but isn't required
- **You've contributed to a design system before**.
You have worked on enterprise components in the past, maybe for internal use in your company.
You have built complex and advanced features while making sure the accessibility was fully functional.
- **You've maintained an active repository before**.
Maybe you've helped maintain a popular open-source repository, or perhaps you've worked on internal repositories that saw contributions from multiple teams.
Previous experience with highly active repository workflows is a definite plus for this role.
- **You have contributed code to MUI before**. A history of contributing to MUI would be a definite plus.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/77584e4c-9379-45f3-a294-6e50bf250383/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,252 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-tech-lead-core.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/react-tech-lead-core.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,253 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-tech-lead-core.md | # React Tech Lead - Core (future role)
<p class="description">You will lead the development of MUI Core, positioning the library as the industry standard for design teams while doubling its adoption.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [6 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
The core components team (MUI Core) needs help.
They are working on 4 products (Material UI, Base UI, Joy UI, and MUI System) with a tiny team.
We also need help to continue to improve the health of the open-source product: make the core components easier to use, increase the contributions by engaging and collaborating with the community, polish all the details, make the components more accessible, guide developers to answers, and just generally be a positive presence in the open-source community.
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
### Why this is interesting
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
The core components are widely used, you will receive a lot of feedback on your work. The community has high expectations, they will push you to do better, every day.
The [results of the latest survey](https://mui.com/blog/2021-developer-survey-results/) can give you a great sense of where we will need to push the open-source library in the coming months.
## The role
### What you'll do on a day-to-day basis
You will extend the [React Engineer](https://mui-org.notion.site/Software-Engineer-fe310cfb22e34fc7881318f9cb1cf023#5f2967e6c60d411ea09ab8a108d95702) responsibilities. Depending on the day, you'll:
- **Lead**. You will lead by inspiring and setting the bar for code quality for the engineering team, and cracking the hard problems:
- Guide the approach and execution.
- Guide people in making the right technical decisions themselves over imposing them.
- Be aware of the current technical landscape and knows where the wind blows.
- **Nurture community contributions**. You will provide guidance and direction to unlock the contributions of the community. Your time will often be way better spent doing this than fixing the problems yourself.
- **Shape the product**. You will be laser-focused on the end goal. It's not about solving technical challenges but about the problem solved for the users.
- **Enable quality work**. You will:
- Embody and foster the engineering culture, e.g. rigorousness, push for small single-purpose PRs, encourage peer reviews, create strong feedback loops between decision and outcome.
- Empower the team to aim for high-quality outputs. By doing such it aims for the success of delivered solutions.
- Push for consistency, follow what's going on in the other teams.
- **Keep technical debt in check**. You will make sure we can keep shipping features at a reasonable pace, align the team on "one way" of doing things and make sure engineers follow the conventions.
- **Be a solver**. You will dig deep into arbitrarily complex problems and find an appropriate path forward. Some focus on a given area for long periods, others bounce from hotspot to hotspot as guided by organizational leadership.
### The best parts of this job
- **You'll be at the cutting edge of application development** — working on one of the fastest-growing UI libraries on the market.
- **You'll be part of an active, open, friendly community** of developers that are excited about building awesome applications.
- **Your role will be key to making MUI the go-to UI framework** for building applications, websites, and design systems with React.
### The worst parts of this job
- **Shifting context.**
You will necessarily have to shift context and dive into a different feature before the current one is done.
It may even be in an area of the codebase you're unfamiliar with or don't have a ton of understanding about.
It's fun, rewarding work, but it can be very challenging.
- **We move quickly but don't sacrifice quality**.
We ship early, often, and quickly. You may not be initially comfortable with the cadence with which we ship high-quality features and improvements to end-users. By doing so, we sacrifice on solving each problem 100% in exchange for fast feedback. Solving 50-70% of the issue with quality should be enough for any given iteration. Our users quickly tell us when we haven't pushed a solution far enough.
- **MUI is a large codebase**. You may bang your head against the wall at times, and then write tests to assist future you 😌.
The work you will be doing is somewhat unique and idiosyncratic. You probably have not had a similar role before.
- **In open-source, you're faced with a nonstop stream of bug reports and support requests**. That means you need to develop an intuition for when to ignore something, and when to dig in further.
## About you
We're looking for someone with strong front-end skills. More important than specific technical skills though is that you're a strong problem solver who loves to learn. Details matter to you.
### Skills you should have
- **Expertise in the modern JavaScript ecosystem**.
MUI is built on the shoulders of giants, making use of technologies such as ES2021, TypeScript, Node.js, React, Next.js, webpack, and Babel.
- **A track record of demonstrating an eye for product and solving real-world user problems**. If you have a knack for solving problems at the root cause, shipping beautiful user interfaces and intuitive APIs, we want you on our team.
- **Experience building and shipping production code in a team setting** with a passion for writing tested, performant, and high-quality code.
- **Strong written and verbal communication skills**.
As part of the team, you'll interface both directly and indirectly with community members and enterprise customers, and contribute to user documentation. Clear communication is fundamental in creating intuitive and compelling resources.
- **Ability to dive into complex problems**.
You should be able to quickly assess, understand, and iterate upon aspects of our codebase.
- **Ready and willing to ask and answer questions**.
If you're comfortable saying you're unsure, asking for help; but equally reaching out to assist others, you'll be an incredible addition to our team. We thrive because of continuous learning. First-time mistakes should be celebrated, not blamed.
- **Avoid monolithic deliverables**.
You scope and stage your work into well-defined milestones to ship.
- **Past work with front-end infrastructure**.
Perhaps you've created your company's design system, written a Babel plugin, or written complex React components.
It would be great if you could address this in your cover letter!
- **You've contributed to a design system before**.
You have worked on enterprise components in the past, maybe for internal use in your company.
You have built complex and advanced features while making sure the accessibility was fully functional.
### What it would be nice if you had, but isn't required
- **You've maintained an active repository before**.
Maybe you've helped maintain a popular open-source repository, or perhaps you've worked on internal repositories that saw contributions from multiple teams.
Previous experience with highly active repository workflows is a definite plus for this role.
- **You have contributed code to MUI before**. A history of contributing to MUI would be a definite plus.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/73e07586-d3aa-43b3-bfef-8eec52884e2a/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,254 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-tech-lead-x-grid.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/react-tech-lead-x-grid.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,255 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/react-tech-lead-x-grid.md | # React Tech Lead - xGrid
<p class="description">You will lead the development of the MUI X Data Grid, positioning the component as the next industry standard.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [6 or above](https://mui-org.notion.site/Engineering-levels-25b2fba9dd1f4b43a1b28f47f0170f23).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
The data grid team (part of MUI X) needs your help.
The component is off [a great start](https://npm-stat.com/charts.html?package=%40mui%2Fx-data-grid&package=react-table&package=ag-grid-community&from=2021-06-01), however we have only started to scratch the surface for the potential of this component. There is x10 more to build.
We need to:
- build an headless version for Base UI.
- build advanced, in browsers, data analysis features like pivoting and charts integration.
- build a strong integration with backend APIs, e.g. to handle >100M rows.
We also need help to continue to make the components easier to use, make it more customizable, [improve performance](https://www.causal.app/blog/react-perf), make it more accessible, improve the health of the open-source by engaging and collaborating with the community, guide developers to answers, and just generally being a positive presence in the community.
## The role
### Why this is interesting
The advanced components portfolio is still small, with a million interesting and challenging problems to solve.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
### What you'll do on a day-to-day basis
You will extend the [React Engineer](https://mui-org.notion.site/Software-Engineer-fe310cfb22e34fc7881318f9cb1cf023#5f2967e6c60d411ea09ab8a108d95702) responsibilities. Depending on the day, you'll:
- **Lead**. You will lead by inspiring and setting the bar for code quality for the engineering team, and cracking the hard problems:
- Guide the approach and execution.
- Guide people in making the right technical decisions themselves over imposing them.
- Be aware of the current technical landscape and knows where the wind blows.
- **Nurture community contributions**. You will provide guidance and direction to unlock the contributions of the community. Your time will often be way better spent doing this than fixing the problems yourself.
- **Shape the product**. You will be laser-focused on the end goal. It's not about solving technical challenges but about the problem solved for the users.
- **Enable quality work**. You will:
- Embody and foster the engineering culture, e.g. rigorousness, push for small single-purpose PRs, encourage peer reviews, create strong feedback loops between decision and outcome.
- Empower the team to aim for high-quality outputs. By doing such it aims for the success of delivered solutions.
- Push for consistency, follow what's going on in the other teams.
- **Keep technical debt in check**. You will make sure we can keep shipping features at a reasonable pace, align the team on "one way" of doing things and make sure engineers follow the conventions.
- **Be a solver**. You will dig deep into arbitrarily complex problems and find an appropriate path forward. Some focus on a given area for long periods, others bounce from hotspot to hotspot as guided by organizational leadership.
### The best parts of this job
- **You'll be at the cutting edge of application development** — working on one of the fastest-growing UI libraries on the market.
- **You'll be part of an active, open, friendly community** of developers that are excited about building awesome applications.
- **Your role will be key to making MUI the go-to UI framework** for building applications, websites, and design systems with React.
### The worst parts of this job
- **Shifting context.**
You will necessarily have to shift context and dive into a different feature before the current one is done.
It may even be in an area of the codebase you're unfamiliar with or don't have a ton of understanding about.
It's fun, rewarding work, but it can be very challenging.
- **We move quickly, but don't sacrifice quality**.
We ship early, often, and quickly. You may not be initially comfortable with the cadence with which we ship high-quality features and improvements to end-users. By doing so, we sacrifice on solving each problem 100% in exchange for fast feedback. Solving 50-70% of the issue with quality should be enough for any given iteration. Our users quickly tell us when we haven't pushed a solution far enough.
- **MUI is a large codebase**. You may bang your head against the wall at times, and then write tests to assist future you 😌.
The work you will be doing is somewhat unique and idiosyncratic. You probably have not had a similar role before.
- **In open-source, you're faced with a nonstop stream of bug reports and support requests**. That means you need to develop an intuition for when to ignore something, and when to dig in further.
## About you
We're looking for someone with strong front-end skills. More important than specific technical skills though is that you're a strong problem solver who loves to learn. Details matter to you.
### Skills you should have
- **Expertise in the modern JavaScript ecosystem**.
MUI is built on the shoulders of giants, making use of technologies such as ES2021, TypeScript, Node.js, React, Next.js, webpack, and Babel.
- **A track record of demonstrating an eye for product and solving real-world user problems**. If you have a knack for solving problems at the root cause, shipping beautiful user interfaces and intuitive APIs, we want you on our team.
- **Experience building and shipping production code in a team setting** with a passion for writing tested, performant, and high-quality code.
- **Strong written and verbal communication skills**.
As part of the team, you'll interface both directly and indirectly with community members and enterprise customers, and contribute to user documentation. Clear communication is fundamental in creating intuitive and compelling resources.
- **Ability to dive into complex problems**.
You should be able to quickly assess, understand, and iterate upon aspects of our codebase.
- **Ready and willing to ask and answer questions**.
If you're comfortable saying you're unsure, asking for help; but equally reaching out to assist others, you'll be an incredible addition to our team. We thrive because of continuous learning. First-time mistakes should be celebrated, not blamed.
- **Avoid monolithic deliverables**.
You scope and stage your work into well-defined milestones to ship.
- **Past work with front-end infrastructure**.
Perhaps you've created your company's design system, written a Babel plugin, or written complex React components.
It would be great if you could address this in your cover letter!
### What it would be nice if you had, but isn't required
- **You've contributed to a design system before**.
You have worked on enterprise components in the past, maybe for internal use in your company.
You have built complex and advanced features while making sure the accessibility was fully functional.
- **You've maintained an active repository before**.
Maybe you've helped maintain a popular open-source repository, or perhaps you've worked on internal repositories that saw contributions from multiple teams.
Previous experience with highly active repository workflows is a definite plus for this role.
- **You have contributed code to MUI before**. A history of contributing to MUI would be a definite plus.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/dffc8ead-fab1-4a07-8b44-a932e2838e0e/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,256 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/senior-designer.md | # Senior Designer
<p class="description">You will be responsible for pushing MUI's component design bar higher.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: [3 or above](https://mui-org.notion.site/Design-levels-aa01996ca7e0481e80479ad47c8f28a4).
- We're a **remote** company, operating mostly asynchronously (written communication over meetings).
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
We are aiming to make high-end design accessible to the many, empowering developers that lack access to a designer as well as saving time for designers with a source they can trust.
[According to our last survey](https://mui.com/blog/2021-developer-survey-results/#what-are-your-most-important-criteria-for-choosing-a-ui-library), the quality of the design execution (UX & UI) is the most important criteria used by developers & designers to pick their next UI library.
### Why this is interesting
Our products empower React developers to build amazing applications faster – we see millions of developers on MUI's docs every year, one million a month.
However, despite Material UI – our biggest library – being [the leading](https://tsh.io/state-of-frontend/#over-the-past-year-which-of-the-following-design-systems-was-your-favorite-go-to-solution) UI design system in the frontend space, its adoption is only at 25%.
More importantly, our challenges go way beyond the ones of design systems.
We envision a future where MUI becomes the default toolkit for web developers to create UIs.
It's why we've been expanding our offering with Joy UI, Base UI, and MUI Toolpad.
Design is foundational to achieving this goal.
## The role
Designers at MUI are essentially _team leaders_.
That means you'll be working closely with your engineering lead counterpart to shape work and scope targeting a set of problems revolving around our component area, either on MUI Core or MUI X (to be further defined).
As our [design philosophy](https://mui-org.notion.site/Design-philosophy-bdbef60d6fad4134a43870df3e452ebc) states, you'll be conducting and guiding the whole team, making sure everything we do is adding a special design spice that only you can add.
We imagine a world where design execution is a definitive product differentiator.
### What you'll do in your first month
- Understand how your role fits into the organization and get acquainted with team members and processes
- Learn about MUI's products, business, goals, and how users experience the MUI ecosystem
- Make your first contribution to either MUI Core or MUI X on an approachable, simple problem
### What you'll do in your first 3 months
- Conduct one-on-one user interviews with community members
- Review and give feedback to work from other designers on the team
- Understand the MUI Core and MUI X library patterns to improve existing components' UX & UI
- Open your first PR improving documentation or demos
### What you'll do in your first 6 months
- Design a new component for one of the MUI Core libraries from scratch in partnership with a developer
- Design new templates for either Joy UI or Material UI and support their implementation
- Review new Figma Design kit versions and coordinate their next release
### What you'll have done in your first year
Aside from all of the above, by the time you complete your first year, you should be able to:
- Proactively identify improvement opportunities across MUI's ecosystem
- Help your team structure and follow a plan to tackle user pain points that you help to discover
- Foster an even more design-oriented, user-centered culture at MUI
- Contribute in a code capacity more confidently, with the ability to tweak and improve your own designs
## About you
If you get excited by thinking about design systems, high-level of craftsmanship, accessible components, and joyful experiences, then we're looking for you!
We're looking for designers who are generalists, meaning they can navigate from very high-level product strategy discussions to low-level implementation work.
As a company that develops code-based products, it's important that you have a grasp of development to be effective.
Concretely, that means you can at least picture how a given CSS snippet looks like just by reading it.
Being able to contribute to the codebase yourself, open pull requests, and improve documentation or components is very valuable.
We strongly believe designers should code to ensure the level of detail they've wished for is really being implemented.
So, if you're this designer, either already able to code or growing in this direction, we're looking for you.
### Other skills you should have
- **Excellent written and verbal communication skills.** You will communicate both in writing and verbally with our globally-distributed team, community members, and enterprise customers. English is the primary language we interact in.
- **Experience building and evaluating UI/UX.** You can design attractive UIs with well-thought-out interaction patterns that solve practical user problems.
- **Design systems experience.** You have previously worked on or contributed to the creation of a design system. You are meticulous about component APIs, standards, and organization.
- **Relative development autonomy.** Ability to read HTML/JSX and CSS is a requirement. Being able to code and contribute to the codebase would be a significant advantage, but isn't required for the role.
### It would be nice if you had but it isn't required
- **Past experience with open-source projects.** You understand the unique dynamics of products in an open-source environment as well as common challenges that arise.
## Benefits and compensation
We are ready to pay competitive, top market rates, for a person that can clearly exceed the role's expectations.
Therefore, we consider profile and location.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## Interview steps
Here's a brief overview of how this role's process will be carried through:
- **Introduction call** (20 to 25 min): A short call to quickly introduce each other.
- **Career deep dive** (40 to 60 min ⎯ with a designer): We'll go through your career a bit more in-depth and will be interested in understanding your trajectory up to the point where you've applied to this role.
- **Comparable experience review** (40 to 60 min ⎯ with a designer, product manager or tech lead): We'll deep dive into a presentation of relevant past experiences to understand your approach to problem-solving and design.
- **Conversation with the CEO** (60 min): A quick call so you get to know each other, and talk about vision, future, history, etc.
We like to encourage candidates to also see all of these conversations as opportunities for you to interview us as well.
It's highly encouraged to bring whatever questions you see fit to make sure we are also a great role for you.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/4ea9d324-3350-48d5-bfab-706ebfc23ed2/application?utm_source=ZNRrPGBkqO)
Don't tick every bullet? **Apply anyway!** Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you. We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,257 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/support-agent.md | # Support Agent - Store (future role)
<p class="description">You will provide support for the customers of MUI Store. You will directly impact customers' satisfaction and success.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
The support on the store is currently almost exclusively done by the executive team of the company (e.g. CSO). This team does no longer has enough bandwidth. You will be responsible to step up and carry forward the support provided to customers of the store on multiple fronts: answering license questions, processing purchase orders, granting refunds, identifying recurring problems, and a lot more.
## The role
### Why this is interesting
You will be in the tech industry. We offer flexibility in your work day.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- Respond to customer inquiries via email in a clear, concise, and comprehensive manner.
You might provide refunds, answer license questions, process purchase-orders, etc.
- Assist in writing and maintaining the FAQs and guides.
- Suggest opportunities to make customers happier for our product team.
- Suggest opportunities to improve the quality and efficiency of our customer service operation.
## About you
### Skills you should have
- 1+ years' experience in a Customer Support role.
- Exceptional writing skills (be clear and concise).
- Experience working remotely.
### What it would be nice if you had, but isn't required
- Basic knowledge of web development.
## Benefits and compensation
Competitive compensation depending on the profile and location of up to $20/h.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/79a9b5ec-6fb3-41ec-b48b-0a792ced7c19/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,258 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/technical-product-manager.md | # Technical Product Manager
<p class="description">You will define and maintain the product roadmap for the advanced components, identify opportunities, define specs, and work with engineers to execute on the features. Experience as an engineer is essential for this role, as you will also contribute to development work in the beginning.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
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](https://mui.com/x/react-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/mui-x/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc).
## The role
### Why this is interesting
Our enterprise components portfolio is still small, with a million interesting and challenging problems to solve.
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- You will coordinate with the engineering to ensure that the product being delivered at each iteration solves the problem.
This involves growing a deep understanding of our technical choices and constraints.
- If time allows you to, you will assist the engineering team and implement some of the items in the backlog, up to part-time.
- You will drive the revenue and community growth by owning KPIs.
- You will grow and cultivate a deep understanding of the problems that developers have when they deal with enterprise applications. This means that you will observe and reach out to the community, run research interviews and share your insights with the team.
- You will keep a close eye on feature requests, issues, and general improvements (mostly through GitHub issues and occasionally Zendesk), to curate opportunities based on our strategy.
- You will build a strategy for your product area and contribute to the overall product strategy, e.g. establishing a go-to-market strategy.
- You will assess the impact of initiatives through telemetry data and qualitative feedback to help us develop our understanding further, and decide on the next steps.
## About you
### Skills you should have
- 3+ years prior experience working as a Front-end engineer, with React ideally.
- 1+ years experience as Product Manager or closely related roles such as Product Owner, Program Manager, or Solutions Architect.
- Able to switch between the big picture and detailed view multiple times a day.
### What it would be nice if you had, but isn't required
- Experience building developer tools.
- Experience working with open-source and having interacted with open-source communities.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/__ID__/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,259 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/technical-recruiter.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/pages/careers/technical-recruiter.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,260 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/careers/technical-recruiter.md | # Technical Recruiter (future role)
<p class="description">You will hire the next engineers, among other roles, joining the team.</p>
## Details of the role
- **Location**: Remote (preference for UTC-6 to UTC+5).
- **Type of work**: Full-time (contractor or employee [depending on circumstances](https://mui-org.notion.site/Hiring-FAQ-64763b756ae44c37b47b081f98915501#494af1f358794028beb4b7697b5d3102)).
- **Level**: _No ladders created yet_.
- We're a **remote** company, we prefer asynchronous communication over meetings.
## The company
MUI's story began in 2014 with Material UI, the most successful React implementation of Google's Material Design.
Today, Material UI stands as one of the most popular open-source libraries on GitHub, and has paved the way for the fully fledged startup known as MUI (founded in 2019), which now boasts an ever-expanding ecosystem of React UI products.
We're a company of 35+ people as of late 2023, and we're growing.
## The products
MUI is best known for our flagship product, Material UI—but this is just one of three core component libraries we maintain.
Base UI is our headless component library, and Joy UI is a sister library to Material UI that implements our own in-house Joy Design system.
We also host Design Kits and pre-built Templates.
Beyond the core libraries, MUI X offers advanced components like the Data Grid, Date and Time Pickers, and Charts, for more complex user interactions and data visualization needs.
We're also making ambitious moves to incorporate our full suite of components into Toolpad, a low-code admin builder tool for assembling full-stack apps faster than ever.
Learn more about MUI's products in this blog post: [An introduction to the MUI ecosystem](https://mui.com/blog/mui-product-comparison/).
## The culture
MUI is a fully remote company with a team that spans the globe.
The majority of our work is asynchronous, and we rely on written communication to collaborate.
We're radically transparent: nearly all of our work happens in public.
Each contributor has the freedom to decide how and when they work, and that work is primarily self-directed: it's your responsibility to define and complete your own tasks in a timely manner.
For additional details about the culture you can check our [careers](https://mui.com/careers/) and [about](https://mui.com/about/) pages and also our [public Handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
## Why we're hiring
Both our open-source community and our premium products are growing fast (x2 YoY).
We need talented people to keep that going!
We anticipate the need to hire >5 people/month in 2023. This is not an outcome that the managers at MUI can deliver on their own.
### Why this is interesting
// TODO
Our products empower React developers to build awesome applications faster – we see millions of developers on MUI's docs every year, one million a month.
## The role
You'll be primarily responsible for managing all recruiting-related activities.
The role will be a mix of sourcing/recruiting directly, as well as managing a number of external recruiting resources such as agencies and recruiting platforms.
This role is best suited for someone who will be able to handle the dynamic nature of a high-growth technology company, and have creativity around how/where to source strong engineering talent.
We're looking for someone who is comfortable in a fast-paced environment and passionate about growing teams remotely.
The ideal candidate will be able to balance long-term focus with practical day-to-day execution.
### What you'll do on a day-to-day basis
Depending on the day, you'll:
- Design, execute and own full life-cycle recruiting.
- Attract and engage top talent in creative, targeted, and meaningful ways.
- Manage candidates through the entire interview process (sourcing, updating candidate pipeline, coordinating interviews, setting expectations, etc.) while maintaining an excellent candidate experience.
- Collaborate with internal team members on recruiting best practices and ways to improve hiring.
- Actively work towards building a diverse team and ensure fairness in hiring practices.
- Regularly manage pipeline activity and analyze KPIs for recruiting.
- Scale a lean team to support growth.
## About you
### Skills you should have
- 5-8 years of recruiting experience, with a strong background in technical R&D hiring.
- Previous experience recruiting and scaling an early-stage team.
- Demonstrated success in establishing credibility and trust with diverse groups.
## Benefits and compensation
Competitive compensation depending on the profile and location.
We are ready to pay top market rates for a person that can clearly exceed the role's expectations.
You can find the other perks & benefits on the [careers](https://mui.com/careers/#perks-and-benefits) page.
## How to apply
[Apply now for this position 📮](https://jobs.ashbyhq.com/MUI/b0f83db9-709d-4259-bad9-ec155efa46bf/application?utm_source=ZNRrPGBkqO)
Don't meet every requirement?
Apply anyway!
Research shows that certain folx are less likely to apply for a role than others [unless they meet 100%](https://hbr.org/2014/08/why-women-dont-apply-for-jobs-unless-theyre-100-qualified) of the outlined qualifications.
If this role excites you, we want to hear from you.
We'd love for you to share the unique skills, passion, and experience you could bring to MUI.
| 4,261 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/company/contact.js | import * as React from 'react';
import TopLayoutCareers from 'docs/src/modules/components/TopLayoutCareers';
import * as pageProps from 'docs/src/pages/company/contact/contact.md?@mui/markdown';
export default function Page() {
return <TopLayoutCareers {...pageProps} />;
}
| 4,262 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/experiments/index.js | import * as React from 'react';
import { capitalize } from '@mui/material/utils';
import Box from '@mui/material/Box';
import CssBaseline from '@mui/material/CssBaseline';
import List from '@mui/material/List';
import ListItem from '@mui/material/ListItem';
import ListItemButton from '@mui/material/ListItemButton';
import Container from '@mui/material/Container';
import Typography from '@mui/material/Typography';
import KeyboardArrowRightRounded from '@mui/icons-material/KeyboardArrowRightRounded';
import GradientText from 'docs/src/components/typography/GradientText';
import Link from 'docs/src/modules/components/Link';
export default function Experiments({ experiments }) {
const categories = {};
experiments.forEach((name) => {
const paths = name.split('/');
const categoryName = paths.length === 1 ? 'Uncategorized' : capitalize(paths[0] || '');
if (!categories[categoryName]) {
categories[categoryName] = [];
}
categories[categoryName].push({
name: name
.replace(/^\//, '')
.replace(/\/$/, '')
.replace(`${categoryName.toLowerCase()}/`, ''),
pathname: `/experiments/${name}`,
});
});
return (
<React.Fragment>
<CssBaseline />
<Box sx={{ display: 'flex', flexFlow: 'column nowrap', minHeight: '100vh' }}>
<Container>
<Box
sx={{
minHeight: 300,
display: 'flex',
flexDirection: 'column',
justifyContent: 'center',
alignItems: 'center',
maxWidth: 600,
mx: 'auto',
textAlign: 'center',
}}
>
<Typography variant="body2" color="primary.600" fontWeight="bold">
Welcome to
</Typography>
<Typography component="h1" variant="h2" sx={{ my: 1 }}>
MUI <GradientText>Experiments</GradientText>
</Typography>
<Box sx={{ textAlign: 'left' }}>
<ul>
<Typography component="li">
The files under <code>/experiments/*</code> are committed to git.
</Typography>
<Typography component="li">
These URLs (start with <code>/experiments/*</code>) are not accessible in
production.
</Typography>
</ul>
</Box>
</Box>
</Container>
<Box
sx={{
bgcolor: (theme) => (theme.palette.mode === 'dark' ? 'primaryDark.900' : 'grey.50'),
flexGrow: 1,
}}
>
<Container sx={{ py: { xs: 4, md: 8 } }}>
<Typography
variant="body2"
color="grey.600"
fontWeight="bold"
textAlign="center"
sx={{ mb: 2 }}
>
All Experiments ({experiments.length})
</Typography>
{experiments.length > 0 && (
<Box
sx={{
display: 'grid',
gap: 2,
gridTemplateColumns: 'repeat(auto-fill, minmax(200px, 1fr))',
}}
>
{Object.entries(categories).map(([categoryName, children]) => (
<Box key={categoryName} sx={{ pb: 2 }}>
<Typography
component="h2"
variant="body2"
sx={{
fontWeight: 500,
color: 'grey.600',
px: 1,
}}
>
{categoryName}
</Typography>
<List>
{(children || []).map((aPage) => {
return (
<ListItem key={aPage.pathname} disablePadding>
<ListItemButton
component={Link}
noLinkStyle
href={aPage.pathname}
sx={{
px: 1,
py: 0.5,
fontSize: '0.84375rem',
fontWeight: 500,
'&:hover, &:focus': { '& svg': { opacity: 1 } },
}}
>
{aPage.name}
<KeyboardArrowRightRounded
sx={{
ml: 'auto',
fontSize: '1.125rem',
opacity: 0,
color: 'primary.main',
}}
/>
</ListItemButton>
</ListItem>
);
})}
</List>
</Box>
))}
</Box>
)}
</Container>
</Box>
</Box>
</React.Fragment>
);
}
Experiments.getInitialProps = () => {
const experiments = [];
const req = require.context('./', true, /^\.\/.*(?<!index)\.(js|tsx)$/);
req.keys().forEach((k) => {
experiments.push(k.replace(/^\.\/(.*)\.(js|tsx)$/, '$1'));
});
return {
experiments,
};
};
| 4,263 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/base/components-gallery.tsx | import * as React from 'react';
import Stack from '@mui/system/Stack';
import { Transition } from 'react-transition-group';
import { Badge } from '@mui/base/Badge';
import { Button } from '@mui/base/Button';
import { Input } from '@mui/base/Input';
import { Menu } from '@mui/base/Menu';
import { MenuItem } from '@mui/base/MenuItem';
import { MenuButton } from '@mui/base/MenuButton';
import { Dropdown } from '@mui/base/Dropdown';
import { Popper } from '@mui/base/Popper';
import { Unstable_Popup as Popup } from '@mui/base/Unstable_Popup';
import { Unstable_NumberInput as NumberInput } from '@mui/base/Unstable_NumberInput';
import { Select, SelectRootSlotProps } from '@mui/base/Select';
import UnfoldMoreRoundedIcon from '@mui/icons-material/UnfoldMoreRounded';
import { Option } from '@mui/base/Option';
import { Slider } from '@mui/base/Slider';
import { Snackbar } from '@mui/base/Snackbar';
// TODO: re-export from the @mui/base/Snackbar, if developer only uses the component
// it is not intuitive to import types from a different module
import { SnackbarCloseReason } from '@mui/base/useSnackbar';
import CheckRoundedIcon from '@mui/icons-material/CheckRounded';
import CloseIcon from '@mui/icons-material/Close';
import { Switch } from '@mui/base/Switch';
import { TablePagination } from '@mui/base/TablePagination';
import { Tabs } from '@mui/base/Tabs';
import { TabsList } from '@mui/base/TabsList';
import { TabPanel } from '@mui/base/TabPanel';
import { Tab } from '@mui/base/Tab';
import { TextareaAutosize } from '@mui/base/TextareaAutosize';
// Snackbar demo
const positioningStyles = {
entering: 'translateX(0)',
entered: 'translateX(0)',
exiting: 'translateX(500px)',
exited: 'translateX(500px)',
unmounted: 'translateX(500px)',
};
const SelectButton = React.forwardRef(function SelectButton<
TValue extends {},
Multiple extends boolean,
>(props: SelectRootSlotProps<TValue, Multiple>, ref: React.ForwardedRef<HTMLButtonElement>) {
const { ownerState, ...other } = props;
return (
<button type="button" {...other} ref={ref}>
{other.children}
<UnfoldMoreRoundedIcon />
</button>
);
});
export default function ComponentsGallery() {
// Popper demo
const [anchorEl, setAnchorEl] = React.useState<null | HTMLElement>(null);
const handleClick = (event: React.MouseEvent<HTMLElement>) => {
setAnchorEl(anchorEl ? null : event.currentTarget);
};
const open = Boolean(anchorEl);
const id = open ? 'simple-popper' : undefined;
// Popup demo
const [popupAnchor, setPopupAnchor] = React.useState<null | HTMLElement>(null);
const popupButtonHandleClick = (event: React.MouseEvent<HTMLElement>) => {
setPopupAnchor(popupAnchor ? null : event.currentTarget);
};
const popupOpen = Boolean(popupAnchor);
const popupId = open ? 'simple-popup' : undefined;
// Snackbar demo
const [snackbarOpen, setSnackbarOpen] = React.useState(false);
const [exited, setExited] = React.useState(true);
const nodeRef = React.useRef(null);
const handleClose = (_: any, reason: SnackbarCloseReason) => {
if (reason === 'clickaway') {
return;
}
setSnackbarOpen(false);
};
const handleSnackbarButtonClick = () => {
setSnackbarOpen(true);
};
const handleOnEnter = () => {
setExited(false);
};
const handleOnExited = () => {
setExited(true);
};
// switch demo
const label = { 'aria-label': 'Demo switch' };
// table pagination demo
const [page, setPage] = React.useState(0);
const [rowsPerPage, setRowsPerPage] = React.useState(5);
const handleChangePage = (event: React.MouseEvent<HTMLButtonElement> | null, newPage: number) => {
setPage(newPage);
};
const handleChangeRowsPerPage = (
event: React.ChangeEvent<HTMLInputElement | HTMLTextAreaElement>,
) => {
setRowsPerPage(parseInt(event.target.value, 10));
setPage(0);
};
return (
<Stack gap={2} style={{ padding: '8px' }}>
<div>
<Badge
slotProps={{
root: { className: 'GalleryBadge' },
badge: { className: 'GalleryBadge-badge' },
}}
badgeContent={5}
>
<span className="GalleryBadge-content" />
</Badge>
</div>
<div>
<Button className="GalleryButton">Button</Button>
<Button className="GalleryButton" disabled>
Disabled
</Button>
</div>
<div>
<Input placeholder="Write your name here" className="GalleryInput" />
</div>
<div>
<Dropdown>
<MenuButton className="GalleryButton">My account</MenuButton>
<Menu
className="GalleryMenu"
slotProps={{
listbox: { className: 'GalleryMenu-listbox' },
}}
>
<MenuItem className="GalleryMenu-item">Profile</MenuItem>
<MenuItem className="GalleryMenu-item">Language settings</MenuItem>
<MenuItem className="GalleryMenu-item">Log out</MenuItem>
</Menu>
</Dropdown>
</div>
<div style={{ maxWidth: '350px' }}>
<NumberInput
slotProps={{
root: { className: 'GalleryNumberInput' },
input: { className: 'input' },
decrementButton: { className: 'btn decrement', children: '▾' },
incrementButton: { className: 'btn increment', children: '▴' },
}}
aria-label="Demo number input"
placeholder="Type a number…"
/>
</div>
<div>
<button type="button" aria-describedby={id} className="GalleryButton" onClick={handleClick}>
Toggle Popper
</button>
<Popper id={id} open={open} anchorEl={anchorEl}>
<div className="GalleryPopper">The content of the Popper.</div>
</Popper>
</div>
<div>
<button
type="button"
aria-describedby={id}
className="GalleryButton"
onClick={popupButtonHandleClick}
>
Toggle Popup
</button>
<Popup id={popupId} open={popupOpen} anchor={popupAnchor}>
<div className="GalleryPopup">The content of the Popup.</div>
</Popup>
</div>
<div>
<Select
className="GallerySelect"
slots={{
root: SelectButton,
}}
slotProps={{
listbox: { className: 'GallerySelect-listbox' },
popper: { className: 'GallerySelect-popper' },
}}
defaultValue={10}
>
<Option className="GallerySelect-option" value={10}>
Documentation
</Option>
<Option className="GallerySelect-option" value={20}>
Components
</Option>
<Option className="GallerySelect-option" value={30}>
Features
</Option>
</Select>
</div>
<div style={{ width: 320 }}>
<Slider
slotProps={{
root: { className: 'GallerySlider' },
rail: { className: 'GallerySlider-rail' },
track: { className: 'GallerySlider-track' },
thumb: { className: 'GallerySlider-thumb', tabIndex: 0 },
}}
defaultValue={50}
/>
<Slider
slotProps={{
root: { className: 'GallerySlider' },
rail: { className: 'GallerySlider-rail' },
track: { className: 'GallerySlider-track' },
thumb: { className: 'GallerySlider-thumb' },
}}
defaultValue={10}
disabled
/>
</div>
<div>
<button className="GalleryButton" type="button" onClick={handleSnackbarButtonClick}>
Open snackbar
</button>
<Snackbar
autoHideDuration={5000}
open={snackbarOpen}
onClose={handleClose}
exited={exited}
className="GallerySnackbar"
>
<Transition
timeout={{ enter: 400, exit: 400 }}
in={snackbarOpen}
appear
unmountOnExit
onEnter={handleOnEnter}
onExited={handleOnExited}
nodeRef={nodeRef}
>
{(status) => (
<div
className="GallerySnackbar-content"
style={{
transform: positioningStyles[status],
transition: 'transform 300ms ease',
}}
ref={nodeRef}
>
<CheckRoundedIcon
sx={{
color: 'success.main',
flexShrink: 0,
width: '1.25rem',
height: '1.5rem',
}}
/>
<div className="snackbar-message">
<p className="snackbar-title">Notifications sent</p>
<p className="snackbar-description">
Everything was sent to the desired address.
</p>
</div>
<CloseIcon onClick={handleClose} className="snackbar-close-icon" />
</div>
)}
</Transition>
</Snackbar>
</div>
<div>
<Switch
slotProps={{
root: { className: 'GallerySwitch' },
input: { ...label, className: 'GallerySwitch-input' },
thumb: { className: 'GallerySwitch-thumb' },
track: { className: 'GallerySwitch-track' },
}}
defaultChecked
/>
<Switch
slotProps={{
root: { className: 'GallerySwitch' },
input: { ...label, className: 'GallerySwitch-input' },
thumb: { className: 'GallerySwitch-thumb' },
track: { className: 'GallerySwitch-track' },
}}
/>
<Switch
slotProps={{
root: { className: 'GallerySwitch' },
input: { ...label, className: 'GallerySwitch-input' },
thumb: { className: 'GallerySwitch-thumb' },
track: { className: 'GallerySwitch-track' },
}}
defaultChecked
disabled
/>
<Switch
slotProps={{
root: { className: 'GallerySwitch' },
input: { ...label, className: 'GallerySwitch-input' },
thumb: { className: 'GallerySwitch-thumb' },
track: { className: 'GallerySwitch-track' },
}}
disabled
/>
</div>
<div className="TablePaginationDemo">
<table aria-label="custom pagination table">
<tfoot>
<tr>
<TablePagination
className="GalleryTablePagination"
rowsPerPageOptions={[5, 10, 25, { label: 'All', value: -1 }]}
colSpan={3}
count={13}
rowsPerPage={rowsPerPage}
page={page}
slotProps={{
select: {
'aria-label': 'rows per page',
},
actions: {
showFirstButton: true,
showLastButton: true,
},
}}
onPageChange={handleChangePage}
onRowsPerPageChange={handleChangeRowsPerPage}
/>
</tr>
</tfoot>
</table>
</div>
<div style={{ maxWidth: '550px' }}>
<Tabs defaultValue={0}>
<TabsList className="GalleryTabsList">
<Tab className="GalleryTab" value={0}>
My account
</Tab>
<Tab className="GalleryTab" value={1}>
Profile
</Tab>
<Tab className="GalleryTab" value={2}>
Language
</Tab>
</TabsList>
<TabPanel className="GalleryTabPanel" value={0}>
My account page
</TabPanel>
<TabPanel className="GalleryTabPanel" value={1}>
Profile page
</TabPanel>
<TabPanel className="GalleryTabPanel" value={2}>
Language page
</TabPanel>
</Tabs>
</div>
<div>
<TextareaAutosize
className="GalleryTextarea"
aria-label="empty textarea"
placeholder="Empty"
/>
</div>
</Stack>
);
}
| 4,264 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/base/listbox.tsx | /* eslint-disable react/no-danger */
import * as React from 'react';
import clsx from 'clsx';
import { useList, ListContext, useListItem } from '@mui/base/useList';
const styles = `
body {
padding: 0;
margin: 0;
font-family: IBM Plex Sans, sans-serif;
}
.list {
display: flex;
gap: 16px;
align-items: center;
justify-content: flex-start;
max-height: 70vh;
padding: 16px;
width: 100vw;
flex-wrap: wrap;
background: linear-gradient(-30deg, #009245, #FCEE21);
box-sizing: border-box;
margin: 0;
}
.list:focus-visible {
outline: none;
}
.item {
width: 50px;
height: 50px;
flex: 0 0 auto;
display: flex;
align-items: center;
justify-content: center;
border: 1px solid rgba(255, 255, 255, 0.3);
border-radius: 4px;
box-sizing: border-box;
background: linear-gradient(-30deg, #f5f5f5, #fff);
font-size: 18px;
color: #333;
user-select: none;
box-shadow: 0 0 10px 0 rgba(0, 0, 0, 0.1), 0 4px 4px -2px rgba(0, 0, 0, 0.15);
}
.item.highlighted:not([tabindex]),
.item:focus-visible
{
outline: 2px solid #fff;
outline-offset: 4px;
}
.item.selected {
background: linear-gradient(-30deg, #363636, #666);
color: #fff;
}
.controls {
padding: 16px;
}
.controls > div {
margin-bottom: 8px;
}
.controls button {
border: 1px solid #999;
background: #fff;
padding: 8px 16px;
border-radius: 4px;
font-family: inherit;
margin: 0 4px;
box-shadow: 0 0 10px 0 rgba(0, 0, 0, 0.1), 0 4px 4px -2px rgba(0, 0, 0, 0.15);
}
.controls button.active {
background: #73bc34;
color: #fff;
}
.state {
padding: 16px;
background: #202020;
color: #fff;
}`;
const items = Array.from({ length: 200 }, (_, i) => i + 1);
const Item = React.forwardRef(function Item(
props: React.PropsWithChildren<{ value: number; id?: string }>,
ref: React.ForwardedRef<HTMLDivElement>,
) {
const { value: item, id } = props;
const { getRootProps, selected, highlighted } = useListItem({ item });
const itemProps = getRootProps();
const classes = clsx('item', {
highlighted,
selected,
});
return (
<div {...itemProps} className={classes} id={id} ref={ref}>
{item}
</div>
);
});
function List() {
const [orientation, setOrientation] = React.useState<
'horizontal-ltr' | 'horizontal-rtl' | 'vertical'
>('horizontal-ltr');
const [focusManagement, setFocusManagement] = React.useState<'activeDescendant' | 'DOM'>(
'activeDescendant',
);
let flexDirection: React.CSSProperties['flexDirection'];
switch (orientation) {
case 'horizontal-ltr':
flexDirection = 'row';
break;
case 'horizontal-rtl':
flexDirection = 'row-reverse';
break;
default:
flexDirection = 'column';
break;
}
const itemRefs = React.useRef(new Map<number, HTMLElement>());
const listbox = useList({
items,
getItemDomElement: React.useCallback((item: number) => itemRefs.current.get(item) || null, []),
getItemId: React.useCallback((item: number) => `item-${item}`, []),
orientation,
focusManagement,
selectionMode: 'single',
});
const {
getRootProps,
contextValue,
state: { selectedValues, highlightedValue },
} = listbox;
const handleItemRef = React.useCallback((item: number, node: HTMLElement | null) => {
if (node) {
itemRefs.current.set(item, node);
} else {
itemRefs.current.delete(item);
}
}, []);
return (
<React.Fragment>
<div className="controls">
<div>
Orientation:
<button
type="button"
onClick={() => setOrientation('horizontal-ltr')}
className={orientation === 'horizontal-ltr' ? 'active' : ''}
>
horizontal-ltr
</button>
<button
type="button"
onClick={() => setOrientation('horizontal-rtl')}
className={orientation === 'horizontal-rtl' ? 'active' : ''}
>
horizontal-rtl
</button>
<button
type="button"
onClick={() => setOrientation('vertical')}
className={orientation === 'vertical' ? 'active' : ''}
>
vertical
</button>
</div>
<div>
Focus management:
<button
type="button"
onClick={() => setFocusManagement('activeDescendant')}
className={focusManagement === 'activeDescendant' ? 'active' : ''}
>
activeDescendant
</button>
<button
type="button"
onClick={() => setFocusManagement('DOM')}
className={focusManagement === 'DOM' ? 'active' : ''}
>
DOM
</button>
</div>
</div>
<div className="state">
<pre>Selected: {selectedValues.join(', ')}</pre>
<pre>Highlighted: {highlightedValue ?? '(none)'}</pre>
</div>
<div {...getRootProps()} className="list" style={{ flexDirection }}>
<ListContext.Provider value={contextValue}>
{items.map((item) => (
<Item
key={item}
value={item}
ref={(node) => handleItemRef(item, node)}
id={`item-${item}`}
/>
))}
</ListContext.Provider>
</div>
</React.Fragment>
);
}
export default function Demo() {
return (
<React.Fragment>
<style dangerouslySetInnerHTML={{ __html: styles }} />
<List />
</React.Fragment>
);
}
| 4,265 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/base/menu.tsx | import * as React from 'react';
import { Menu } from '@mui/base/Menu';
import { MenuButton } from '@mui/base/MenuButton';
import { MenuItem, menuItemClasses } from '@mui/base/MenuItem';
import { Dropdown } from '@mui/base/Dropdown';
import { styled } from '@mui/system';
const blue = {
100: '#DAECFF',
200: '#99CCF3',
400: '#3399FF',
500: '#007FFF',
600: '#0072E5',
900: '#003A75',
};
const grey = {
50: '#f6f8fa',
100: '#eaeef2',
200: '#d0d7de',
300: '#afb8c1',
400: '#8c959f',
500: '#6e7781',
600: '#57606a',
700: '#424a53',
800: '#32383f',
900: '#24292f',
};
const StyledListbox = styled('ul')(
({ theme }) => `
font-family: -apple-system,BlinkMacSystemFont,"Segoe UI","Noto Sans",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";
font-size: 0.875rem;
box-sizing: border-box;
padding: 6px;
margin: 12px 0;
min-width: 200px;
border-radius: 12px;
overflow: auto;
outline: 0px;
background: ${theme.palette.mode === 'dark' ? grey[900] : '#fff'};
border: 1px solid ${theme.palette.mode === 'dark' ? grey[700] : grey[200]};
color: ${theme.palette.mode === 'dark' ? grey[300] : grey[900]};
box-shadow: 0 1px 3px rgba(31,35,40,0.12), 0 8px 24px rgba(66,74,83,0.12);
z-index: 1;
`,
);
const StyledMenuItem = styled(MenuItem)(
({ theme }) => `
list-style: none;
padding: 6px;
margin: 2px 0;
border-radius: 8px;
cursor: default;
user-select: none;
&:last-of-type {
border-bottom: none;
}
&.${menuItemClasses.focusVisible} {
outline: 3px solid ${theme.palette.mode === 'dark' ? blue[600] : blue[200]};
background-color: ${theme.palette.mode === 'dark' ? grey[800] : grey[100]};
color: ${theme.palette.mode === 'dark' ? grey[300] : grey[900]};
}
&.${menuItemClasses.disabled} {
color: ${theme.palette.mode === 'dark' ? grey[700] : grey[400]};
}
&:hover:not(.${menuItemClasses.disabled}) {
background-color: ${theme.palette.mode === 'dark' ? grey[800] : grey[100]};
color: ${theme.palette.mode === 'dark' ? grey[300] : grey[900]};
}
`,
);
const StyledMenuButton = styled(MenuButton)(
({ theme }) => `
font-family: -apple-system,BlinkMacSystemFont,"Segoe UI","Noto Sans",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";;
font-size: 0.875rem;
box-sizing: border-box;
min-height: calc(1.5em + 22px);
border-radius: 12px;
padding: 12px 16px;
line-height: 1.5;
background: ${theme.palette.mode === 'dark' ? grey[900] : '#fff'};
border: 1px solid ${theme.palette.mode === 'dark' ? grey[700] : grey[200]};
color: ${theme.palette.mode === 'dark' ? grey[300] : grey[900]};
transition-property: all;
transition-timing-function: cubic-bezier(0.4, 0, 0.2, 1);
transition-duration: 120ms;
&:hover {
background: ${theme.palette.mode === 'dark' ? grey[800] : grey[50]};
border-color: ${theme.palette.mode === 'dark' ? grey[600] : grey[300]};
}
&:focus {
border-color: ${blue[400]};
outline: 3px solid ${theme.palette.mode === 'dark' ? blue[500] : blue[200]};
}
`,
);
const Page = styled('div')(`
max-width: 800px;
min-height: calc(100vh - 40px);
box-sizing: border-box;
margin: 20px auto;
padding: 20px;
border-radius: 4px;
`);
function UnstyledSeparator(props: React.HTMLAttributes<HTMLLIElement>) {
return <li {...props} role="separator" />;
}
const Separator = styled(UnstyledSeparator)(`
height: 0;
margin: 8px -6px;
border-bottom: 1px solid rgba(0, 0, 0, 0.1);
list-style: none;
`);
export default function UnstyledMenuIntroduction() {
const [isOpen, setOpen] = React.useState(false);
const handleOpenChange = (event: React.SyntheticEvent | null, open: boolean) => {
setOpen(open);
};
const createHandleMenuClick = (menuItem: string) => {
return () => {
// eslint-disable-next-line no-console
console.log(`Clicked on ${menuItem}`);
};
};
return (
<Page>
<Dropdown open={isOpen} onOpenChange={handleOpenChange}>
<StyledMenuButton>Create new...</StyledMenuButton>
<Menu
slots={{ listbox: StyledListbox }}
slotProps={{ root: { placement: 'bottom-start', id: 'simple-menu' } }}
>
<StyledMenuItem onClick={createHandleMenuClick('New repository')}>
New repository
</StyledMenuItem>
<StyledMenuItem onClick={createHandleMenuClick('Import repository')}>
Import repository
</StyledMenuItem>
<Separator />
<StyledMenuItem onClick={createHandleMenuClick('New codespace')}>
New codespace
</StyledMenuItem>
<StyledMenuItem onClick={createHandleMenuClick('New gist')}>New gist</StyledMenuItem>
<Separator />
<StyledMenuItem onClick={createHandleMenuClick('New organization')}>
New organization
</StyledMenuItem>
</Menu>
</Dropdown>
</Page>
);
}
| 4,266 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/base/popup.tsx | import * as React from 'react';
import { Unstable_Popup as BasePopup, PopupProps } from '@mui/base/Unstable_Popup';
import Button from '@mui/joy/Button';
import { CssVarsProvider } from '@mui/joy/styles';
import { styled } from '@mui/system';
import Fade from '@mui/material/Fade';
const StyledPopup = styled(BasePopup)`
width: max-content;
`;
const PopupBody = styled('div')`
padding: 16px;
background-color: white;
box-shadow: 0 0 10px 0 rgb(0 0 0 / 0.05), 0 3px 2px -2px rgb(0 0 0 / 0.1);
border-radius: 4px;
font-family: var(--joy-fontFamily-body);
font-size: var(--joy-fontSize-sm);
z-index: 1;
`;
const Section = styled('div')`
padding: 8px;
width: 150px;
`;
function Animated(
props: React.PropsWithChildren<{
className?: string;
requestOpen: boolean;
onExited: () => void;
onEnter: () => void;
}>,
) {
const { requestOpen, onEnter, onExited, children, className } = props;
const handleAnimationEnd = React.useCallback(() => {
if (!requestOpen) {
onExited();
}
}, [onExited, requestOpen]);
React.useEffect(() => {
if (requestOpen) {
onEnter();
}
}, [onEnter, requestOpen]);
return (
<div
onAnimationEnd={handleAnimationEnd}
className={className + (requestOpen ? ' open' : ' close')}
>
{children}
</div>
);
}
const PopAnimation = styled(Animated)`
@keyframes open-animation {
0% {
opacity: 0;
transform: translateY(-8px) scale(0.95);
}
50% {
opacity: 1;
transform: translateY(4px) scale(1.05);
}
100% {
opacity: 1;
transform: translateY(0) scale(1);
}
}
@keyframes close-animation {
0% {
opacity: 1;
transform: scale(1) rotate(0deg);
filter: blur(0);
}
100% {
opacity: 0;
transform: scale(1.2) rotate(4deg);
filter: blur(3px);
}
}
&.open {
animation: open-animation 0.2s ease-out forwards;
}
&.close {
animation: close-animation 0.4s ease-out forwards;
}
`;
function PopupWithTrigger(props: PopupProps & { label: string }) {
const [anchor, setAnchor] = React.useState<HTMLButtonElement | null>(null);
const [open, setOpen] = React.useState(false);
const { label, children, ...other } = props;
return (
<Section>
<Button ref={setAnchor} onClick={() => setOpen((o) => !o)} fullWidth>
{open ? 'Close' : 'Open'} {label}
</Button>
<StyledPopup anchor={anchor} open={open} {...other}>
{children ?? <PopupBody>This is a {label} popup</PopupBody>}
</StyledPopup>
</Section>
);
}
const Container = styled('div')`
display: flex;
flex-wrap: wrap;
`;
export default function PopupPlayground() {
return (
<CssVarsProvider>
<Container>
<PopupWithTrigger label="default" />
<PopupWithTrigger label="placed to the right" placement="right" />
<PopupWithTrigger label="always mounted" keepMounted />
<PopupWithTrigger label="non-portaled" disablePortal />
<PopupWithTrigger label="with offset" offset={20} />
<PopupWithTrigger label="with Material UI transition" withTransition>
{({ requestOpen, onExited, onEnter }) => (
<Fade in={requestOpen} onExited={onExited} onEnter={onEnter} timeout={250}>
<PopupBody>This is an animated popup</PopupBody>
</Fade>
)}
</PopupWithTrigger>
<PopupWithTrigger label="with custom transition" withTransition>
{({ requestOpen: open, onExited, onEnter }) => (
<PopAnimation requestOpen={open} onExited={onExited} onEnter={onEnter}>
<PopupBody>This is an animated popup</PopupBody>
</PopAnimation>
)}
</PopupWithTrigger>
</Container>
</CssVarsProvider>
);
}
| 4,267 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/base/tabs.tsx | import * as React from 'react';
import { styled } from '@mui/system';
import { Tabs } from '@mui/base/Tabs';
import { TabsList } from '@mui/base/TabsList';
import { TabPanel } from '@mui/base/TabPanel';
import { Tab, tabClasses } from '@mui/base/Tab';
const blue = {
50: '#F0F7FF',
100: '#C2E0FF',
200: '#80BFFF',
300: '#66B2FF',
400: '#3399FF',
500: '#007FFF',
600: '#0072E5',
700: '#0059B2',
800: '#004C99',
900: '#003A75',
};
const grey = {
50: '#f6f8fa',
100: '#eaeef2',
200: '#d0d7de',
300: '#afb8c1',
400: '#8c959f',
500: '#6e7781',
600: '#57606a',
700: '#424a53',
800: '#32383f',
900: '#24292f',
};
const StyledTab = styled(Tab)`
font-family: 'IBM Plex Sans', sans-serif;
color: #fff;
cursor: pointer;
font-size: 0.875rem;
font-weight: 600;
background-color: transparent;
width: 100%;
padding: 10px 12px;
margin: 6px;
border: none;
border-radius: 7px;
display: flex;
justify-content: center;
&:hover {
background-color: ${blue[400]};
}
&:focus {
color: #fff;
outline: 3px solid ${blue[200]};
}
&.${tabClasses.selected} {
background-color: #fff;
color: ${blue[600]};
}
&.${tabClasses.disabled} {
opacity: 0.5;
}
`;
const StyledTabPanel = styled(TabPanel)(
({ theme }) => `
width: 100%;
font-family: IBM Plex Sans, sans-serif;
font-size: 0.875rem;
padding: 20px 12px;
background: ${theme.palette.mode === 'dark' ? grey[900] : '#fff'};
border: 1px solid ${theme.palette.mode === 'dark' ? grey[700] : grey[200]};
border-radius: 12px;
box-sizing: border-box;
margin-bottom: 16px;
`,
);
const StyledTabsList = styled(TabsList)(
({ theme }) => `
min-width: 400px;
background-color: ${blue[500]};
border-radius: 12px;
margin-bottom: 16px;
display: flex;
align-items: center;
justify-content: center;
align-content: space-between;
box-shadow: 0px 4px 30px ${theme.palette.mode === 'dark' ? grey[900] : grey[200]};
`,
);
function MoreTabs() {
return (
<React.Fragment>
<Tab value="settings">Settings</Tab>
<Tab disabled value="notifications">
Notifications
</Tab>
<Tab value="nested">Nested tabs</Tab>
</React.Fragment>
);
}
function MoreTabPanels() {
return (
<React.Fragment>
<TabPanel value="settings">Settings page</TabPanel>
<TabPanel value="notifications">Notifications page</TabPanel>
<TabPanel value="nested">
<Tabs defaultValue="my-account">
<TabsList>
<Tab value="my-account">My account</Tab>
<Tab value="profile">Profile</Tab>
<Tab value="language">Language</Tab>
<MoreTabs />
</TabsList>
<TabPanel value="my-account">My account page</TabPanel>
<TabPanel value="profile">Profile page</TabPanel>
<TabPanel value="language">Language page</TabPanel>
<MoreTabPanels />
</Tabs>
</TabPanel>
</React.Fragment>
);
}
export default function UnstyledTabsIntroduction() {
const [selectionFollowsFocus, setSelectionFollowsFocus] = React.useState(false);
const [selectedTab, setSelectedTab] = React.useState<string | number>('profile');
const handleTabChange = (
event: React.SyntheticEvent | null,
newValue: string | number | null,
) => {
setSelectedTab(newValue!);
};
return (
<React.Fragment>
<label>
<input
type="checkbox"
checked={selectionFollowsFocus}
onChange={(e) => setSelectionFollowsFocus(e.target.checked)}
/>{' '}
Selection follows focus
</label>
<Tabs
value={selectedTab}
onChange={handleTabChange}
selectionFollowsFocus={selectionFollowsFocus}
>
<StyledTabsList>
<StyledTab value="my-account">My account</StyledTab>
<StyledTab value="profile">Profile</StyledTab>
<StyledTab value="language">Language</StyledTab>
<MoreTabs />
</StyledTabsList>
<StyledTabPanel value="my-account">My account page</StyledTabPanel>
<StyledTabPanel value="profile">Profile page</StyledTabPanel>
<StyledTabPanel value="language">Language page</StyledTabPanel>
<MoreTabPanels />
<StyledTabsList>
<StyledTab value="my-account">My account</StyledTab>
<StyledTab value="profile">Profile</StyledTab>
<StyledTab value="language">Language</StyledTab>
<MoreTabs />
</StyledTabsList>
</Tabs>
</React.Fragment>
);
}
| 4,268 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/blog/blog.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './blog.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,269 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/blog/blog.md | ---
title: Blog post title
description: Our internationally distributed startup gathered on a remote island to get to know each other better. Here's what happened!
date: 2022-07-28T00:00:00.000Z
authors: ['samuelsycamore']
card: false
tags: ['Company']
---
## Description
### Image
<img alt="Satellite image of Tenerife" src="/static/blog/2022-tenerife-retreat/tenerife.jpeg" width="2560" height="1920" loading="lazy" />
<p class="blog-description">An image description <a href="https://en.wikipedia.org/wiki/Tenerife">with a link</a>.</p>
More text below.
### Code
```jsx
// add margin: 8px 0px;
<Slider sx={{ my: 1 }} />
```
<p class="blog-description"><a href="https://codesandbox.io/s/nostalgic-williams-zmo5r?file=/src/App.js">CodeSandbox</a></p>
More text below.
| 4,270 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/DemoInDocs.js | import * as React from 'react';
import Alert from '@mui/material/Alert';
import Stack from '@mui/material/Stack';
export default function DemoInDocs() {
return (
<Stack sx={{ width: '100%' }} spacing={2}>
<Alert severity="error">This is an error alert — check it out!</Alert>
<Alert severity="warning">This is a warning alert — check it out!</Alert>
<Alert severity="info">This is an info alert — check it out!</Alert>
<Alert severity="success">This is a success alert — check it out!</Alert>
</Stack>
);
}
| 4,271 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/DemoInDocs.tsx.preview | <Alert severity="error">This is an error alert — check it out!</Alert>
<Alert severity="warning">This is a warning alert — check it out!</Alert>
<Alert severity="info">This is an info alert — check it out!</Alert>
<Alert severity="success">This is a success alert — check it out!</Alert> | 4,272 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/callouts.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from './callouts.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,273 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/callouts.md | # Callouts
<p class="description">Type of callouts.</p>
## Info
:::info
One-liner info callout.
:::
:::info
This is an info callout.
It says, "Here's a bit of extra insight to help you understand this feature."
- emphasised: **bold text**
- some code `<div/>`
- a [link](#link).
:::
```markup
:::info
This is an info callout.
It says, "Here's a bit of extra insight to help you understand this feature."
- emphasised: **bold text**
- some code `<div/>`
- a [link](#link).
:::
```
## Success
:::success
One-liner success callout.
:::
:::success
This is a success callout.
It says, "Here's an actionable suggestion to help you succeed."
- emphasised: **bold text**
- some code `<div/>`
- a [link](#link).
:::
```markup
:::success
This is a success callout.
It says, "Here's an actionable suggestion to help you succeed."
- emphasised: **bold text**
- some code `<div/>`
- a [link](#link).
:::
```
## Warning
:::warning
One-liner warning callout.
:::
:::warning
This is a warning callout.
It says, "Be careful! Keep this detail in mind to avoid potential issues."
- emphasised: **bold text**
- some code `<div/>`
- a [link](#link).
:::
```markup
:::warning
This is a warning callout.
It says, "Be careful! Keep this detail in mind to avoid potential issues."
- emphasised: **bold text**
- some code `<div/>`
- a [link](#link).
:::
```
## Error
:::error
One-liner error callout.
:::
:::error
This is an error callout.
It says, "You will fail if you don't heed this dire warning."
- emphasised: **bold text**
- some code `<div/>`
- a [link](#link).
:::
```markup
:::error
This is an error callout.
It says, "You will fail if you don't heed this dire warning."
- emphasised: **bold text**
- some code `<div/>`
- a [link](#link).
:::
```
## Empty
Should not be used, here just to ensure forgetting the token is not a big deal.
:::
This is a callout.
It says, "You will fail if you don't heed this dire warning."
- emphasised: **bold text**
- some code `<div/>`
- a [link](#link).
:::
```markup
:::
This is a callout.
It says, "You will fail if you don't heed this dire warning."
- emphasised: **bold text**
- some code `<div/>`
- a [link](#link).
:::
```
## With code
:::info
This is a callout.
```jsx
import * as React from 'react';
import Stack from '@mui/material/Stack';
export default function BasicAlerts() {
return <Stack sx={{ width: '100%' }} spacing={2} />;
}
```
:::
| 4,274 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/codeblock.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from './codeblock.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,275 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/codeblock.md | # Codeblock
<p class="description">Installation component.</p>
## Tabs
<codeblock storageKey="package-manager">
```bash npm
npm install @mui/material @emotion/react @emotion/styled
# `@emotion/react` and `@emotion/styled` are peer dependencies
```
```bash yarn
yarn add @mui/material @emotion/react @emotion/styled
# `@emotion/react` and `@emotion/styled` are peer dependencies
```
```bash pnpm
pnpm add @mui/material @emotion/react @emotion/styled
# `@emotion/react` and `@emotion/styled` are peer dependencies
```
</codeblock>
<codeblock storageKey="license">
```bash MIT
npm install @mui/data-grid
```
```bash Pro
npm install @mui/data-grid-pro
```
```bash Premium
npm install @mui/data-grid-premium
```
</codeblock>
## Component
{{"component": "modules/components/HighlightedCodeWithTabs", "tabs": [{"tab":"JS", "code":"<div>Hello</div>", "language": "jsx"}, {"tab": "TS", "code": "type A = {}"}]}}
| 4,276 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/data-grid-premium-translation.json | {
"componentDescription": "",
"propDescriptions": {
"aggregationFunctions": {
"description": "Aggregation functions available on the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"aggregationModel": {
"description": "Set the aggregation model of the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"aggregationRowsScope": {
"description": "Rows used to generate the aggregated value. If <code>filtered</code>, the aggregated values are generated using only the rows currently passing the filtering process. If <code>all</code>, the aggregated values are generated using all the rows.",
"deprecated": "",
"typeDescriptions": {}
},
"apiRef": {
"description": "The ref object that allows grid manipulation. Can be instantiated with <code>useGridApiRef()</code>.",
"deprecated": "",
"typeDescriptions": {}
},
"aria-label": {
"description": "The label of the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"aria-labelledby": {
"description": "The id of the element containing a label for the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"autoHeight": {
"description": "If <code>true</code>, the grid height is dynamic and follow the number of rows in the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"autoPageSize": {
"description": "If <code>true</code>, the pageSize is calculated according to the container size and the max number of rows to avoid rendering a vertical scroll bar.",
"deprecated": "",
"typeDescriptions": {}
},
"cellModesModel": {
"description": "Controls the modes of the cells.",
"deprecated": "",
"typeDescriptions": {}
},
"checkboxSelection": {
"description": "If <code>true</code>, the grid get a first column with a checkbox that allows to select rows.",
"deprecated": "",
"typeDescriptions": {}
},
"checkboxSelectionVisibleOnly": {
"description": "If <code>true</code>, the "Select All" header checkbox selects only the rows on the current page. To be used in combination with <code>checkboxSelection</code>. It only works if the pagination is enabled.",
"deprecated": "",
"typeDescriptions": {}
},
"classes": {
"description": "Override or extend the styles applied to the component.",
"deprecated": "",
"typeDescriptions": {}
},
"clipboardCopyCellDelimiter": {
"description": "The character used to separate cell values when copying to the clipboard.",
"deprecated": "",
"typeDescriptions": {}
},
"columnBuffer": {
"description": "Number of extra columns to be rendered before/after the visible slice.",
"deprecated": "",
"typeDescriptions": {}
},
"columnHeaderHeight": {
"description": "Sets the height in pixel of the column headers in the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"columns": {
"description": "Set of columns of type GridColDef[].",
"deprecated": "",
"typeDescriptions": {}
},
"columnThreshold": {
"description": "Number of rows from the <code>columnBuffer</code> that can be visible before a new slice is rendered.",
"deprecated": "",
"typeDescriptions": {}
},
"columnVisibilityModel": {
"description": "Set the column visibility model of the grid. If defined, the grid will ignore the <code>hide</code> property in <a href=\"/x/api/data-grid/grid-col-def/\">GridColDef</a>.",
"deprecated": "",
"typeDescriptions": {}
},
"components": {
"description": "Overridable components.",
"deprecated": "",
"typeDescriptions": {}
},
"componentsProps": {
"description": "Overridable components props dynamically passed to the component at rendering.",
"deprecated": "",
"typeDescriptions": {}
},
"defaultGroupingExpansionDepth": {
"description": "If above 0, the row children will be expanded up to this depth. If equal to -1, all the row children will be expanded.",
"deprecated": "",
"typeDescriptions": {}
},
"density": {
"description": "Set the density of the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"detailPanelExpandedRowIds": {
"description": "The row ids to show the detail panel.",
"deprecated": "",
"typeDescriptions": {}
},
"disableAggregation": {
"description": "If <code>true</code>, aggregation is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableChildrenFiltering": {
"description": "If <code>true</code>, the filtering will only be applied to the top level rows when grouping rows with the <code>treeData</code> prop.",
"deprecated": "",
"typeDescriptions": {}
},
"disableChildrenSorting": {
"description": "If <code>true</code>, the sorting will only be applied to the top level rows when grouping rows with the <code>treeData</code> prop.",
"deprecated": "",
"typeDescriptions": {}
},
"disableClipboardPaste": {
"description": "If <code>true</code>, the clipboard paste is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableColumnFilter": {
"description": "If <code>true</code>, column filters are disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableColumnMenu": {
"description": "If <code>true</code>, the column menu is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableColumnPinning": {
"description": "If <code>true</code>, the column pinning is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableColumnReorder": {
"description": "If <code>true</code>, reordering columns is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableColumnResize": {
"description": "If <code>true</code>, resizing columns is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableColumnSelector": {
"description": "If <code>true</code>, hiding/showing columns is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableDensitySelector": {
"description": "If <code>true</code>, the density selector is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableMultipleColumnsFiltering": {
"description": "If <code>true</code>, filtering with multiple columns is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableMultipleColumnsSorting": {
"description": "If <code>true</code>, sorting with multiple columns is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableMultipleRowSelection": {
"description": "If <code>true</code>, multiple selection using the Ctrl or CMD key is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableRowGrouping": {
"description": "If <code>true</code>, the row grouping is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableRowSelectionOnClick": {
"description": "If <code>true</code>, the selection on click on a row or cell is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"disableVirtualization": {
"description": "If <code>true</code>, the virtualization is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"editMode": {
"description": "Controls whether to use the cell or row editing.",
"deprecated": "",
"typeDescriptions": {}
},
"experimentalFeatures": {
"description": "Unstable features, breaking changes might be introduced. For each feature, if the flag is not explicitly set to <code>true</code>, then the feature is fully disabled, and neither property nor method calls will have any effect.",
"deprecated": "",
"typeDescriptions": {}
},
"filterDebounceMs": {
"description": "The milliseconds delay to wait after a keystroke before triggering filtering.",
"deprecated": "",
"typeDescriptions": {}
},
"filterMode": {
"description": "Filtering can be processed on the server or client-side. Set it to 'server' if you would like to handle filtering on the server-side.",
"deprecated": "",
"typeDescriptions": {}
},
"filterModel": {
"description": "Set the filter model of the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"getAggregationPosition": {
"description": "Determines the position of an aggregated value.",
"deprecated": "",
"typeDescriptions": {
"groupNode": "The current group.",
"GridAggregationPosition | null": "Position of the aggregated value (if <code>null</code>, the group isn't aggregated)."
}
},
"getCellClassName": {
"description": "Function that applies CSS classes dynamically on cells.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-cell-params/\">GridCellParams</a>.",
"string": "The CSS class to apply to the cell."
}
},
"getDetailPanelContent": {
"description": "Function that returns the element to render in row detail.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-row-params/\">GridRowParams</a>.",
"React.JSX.Element": "The row detail element."
}
},
"getDetailPanelHeight": {
"description": "Function that returns the height of the row detail panel.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-row-params/\">GridRowParams</a>.",
"number | string": "The height in pixels or "auto" to use the content height."
}
},
"getEstimatedRowHeight": {
"description": "Function that returns the estimated height for a row. Only works if dynamic row height is used. Once the row height is measured this value is discarded.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridRowHeightParams.",
"number | null": "The estimated row height value. If <code>null</code> or <code>undefined</code> then the default row height, based on the density, is applied."
}
},
"getRowClassName": {
"description": "Function that applies CSS classes dynamically on rows.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-row-class-name-params/\">GridRowClassNameParams</a>.",
"string": "The CSS class to apply to the row."
}
},
"getRowHeight": {
"description": "Function that sets the row height per row.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridRowHeightParams.",
"GridRowHeightReturnValue": "The row height value. If <code>null</code> or <code>undefined</code> then the default row height is applied. If "auto" then the row height is calculated based on the content."
}
},
"getRowId": {
"description": "Return the id of a given GridRowModel.",
"deprecated": "",
"typeDescriptions": {}
},
"getRowSpacing": {
"description": "Function that allows to specify the spacing between rows.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-row-spacing-params/\">GridRowSpacingParams</a>.",
"GridRowSpacing": "The row spacing values."
}
},
"getTreeDataPath": {
"description": "Determines the path of a row in the tree data. For instance, a row with the path ["A", "B"] is the child of the row with the path ["A"]. Note that all paths must contain at least one element.",
"deprecated": "",
"typeDescriptions": {
"row": "The row from which we want the path.",
"Array<string>": "The path to the row."
}
},
"groupingColDef": {
"description": "The grouping column used by the tree data.",
"deprecated": "",
"typeDescriptions": {}
},
"hideFooter": {
"description": "If <code>true</code>, the footer component is hidden.",
"deprecated": "",
"typeDescriptions": {}
},
"hideFooterPagination": {
"description": "If <code>true</code>, the pagination component in the footer is hidden.",
"deprecated": "",
"typeDescriptions": {}
},
"hideFooterRowCount": {
"description": "If <code>true</code>, the row count in the footer is hidden. It has no effect if the pagination is enabled.",
"deprecated": "",
"typeDescriptions": {}
},
"hideFooterSelectedRowCount": {
"description": "If <code>true</code>, the selected row count in the footer is hidden.",
"deprecated": "",
"typeDescriptions": {}
},
"initialState": {
"description": "The initial state of the DataGridPremium. The data in it is set in the state on initialization but isn't controlled. If one of the data in <code>initialState</code> is also being controlled, then the control state wins.",
"deprecated": "",
"typeDescriptions": {}
},
"isCellEditable": {
"description": "Callback fired when a cell is rendered, returns true if the cell is editable.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-cell-params/\">GridCellParams</a>.",
"boolean": "A boolean indicating if the cell is editable."
}
},
"isGroupExpandedByDefault": {
"description": "Determines if a group should be expanded after its creation. This prop takes priority over the <code>defaultGroupingExpansionDepth</code> prop.",
"deprecated": "",
"typeDescriptions": {
"node": "The node of the group to test.",
"boolean": "A boolean indicating if the group is expanded."
}
},
"isRowSelectable": {
"description": "Determines if a row can be selected.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-row-params/\">GridRowParams</a>.",
"boolean": "A boolean indicating if the cell is selectable."
}
},
"keepColumnPositionIfDraggedOutside": {
"description": "If <code>true</code>, moving the mouse pointer outside the grid before releasing the mouse button in a column re-order action will not cause the column to jump back to its original position.",
"deprecated": "",
"typeDescriptions": {}
},
"keepNonExistentRowsSelected": {
"description": "If <code>true</code>, the selection model will retain selected rows that do not exist. Useful when using server side pagination and row selections need to be retained when changing pages.",
"deprecated": "",
"typeDescriptions": {}
},
"loading": {
"description": "If <code>true</code>, a loading overlay is displayed.",
"deprecated": "",
"typeDescriptions": {}
},
"localeText": {
"description": "Set the locale text of the grid. You can find all the translation keys supported in <a href=\"https://github.com/mui/mui-x/blob/HEAD/packages/grid/x-data-grid/src/constants/localeTextConstants.ts\">the source</a> in the GitHub repository.",
"deprecated": "",
"typeDescriptions": {}
},
"logger": {
"description": "Pass a custom logger in the components that implements the Logger interface.",
"deprecated": "",
"typeDescriptions": {}
},
"logLevel": {
"description": "Allows to pass the logging level or false to turn off logging.",
"deprecated": "",
"typeDescriptions": {}
},
"nonce": {
"description": "Nonce of the inline styles for <a href=\"https://www.w3.org/TR/2016/REC-CSP2-20161215/#script-src-the-nonce-attribute\">Content Security Policy</a>.",
"deprecated": "",
"typeDescriptions": {}
},
"onAggregationModelChange": {
"description": "Callback fired when the row grouping model changes.",
"deprecated": "",
"typeDescriptions": {
"model": "The aggregated columns.",
"details": "Additional details for this callback."
}
},
"onCellClick": {
"description": "Callback fired when any cell is clicked.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-cell-params/\">GridCellParams</a>.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onCellDoubleClick": {
"description": "Callback fired when a double click event comes from a cell element.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-cell-params/\">GridCellParams</a>.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onCellEditStart": {
"description": "Callback fired when the cell turns to edit mode.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-cell-params/\">GridCellParams</a>.",
"event": "The event that caused this prop to be called."
}
},
"onCellEditStop": {
"description": "Callback fired when the cell turns to view mode.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-cell-params/\">GridCellParams</a>.",
"event": "The event that caused this prop to be called."
}
},
"onCellKeyDown": {
"description": "Callback fired when a keydown event comes from a cell element.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-cell-params/\">GridCellParams</a>.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onCellModesModelChange": {
"description": "Callback fired when the <code>cellModesModel</code> prop changes.",
"deprecated": "",
"typeDescriptions": {
"cellModesModel": "Object containing which cells are in "edit" mode.",
"details": "Additional details for this callback."
}
},
"onClipboardCopy": {
"description": "Callback called when the data is copied to the clipboard.",
"deprecated": "",
"typeDescriptions": { "data": "The data copied to the clipboard." }
},
"onClipboardPasteEnd": {
"description": "Callback fired when the clipboard paste operation ends.",
"deprecated": "",
"typeDescriptions": {}
},
"onClipboardPasteStart": {
"description": "Callback fired when the clipboard paste operation starts.",
"deprecated": "",
"typeDescriptions": {}
},
"onColumnHeaderClick": {
"description": "Callback fired when a click event comes from a column header element.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridColumnHeaderParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onColumnHeaderDoubleClick": {
"description": "Callback fired when a double click event comes from a column header element.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridColumnHeaderParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onColumnHeaderEnter": {
"description": "Callback fired when a mouse enter event comes from a column header element.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridColumnHeaderParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onColumnHeaderLeave": {
"description": "Callback fired when a mouse leave event comes from a column header element.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridColumnHeaderParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onColumnHeaderOut": {
"description": "Callback fired when a mouseout event comes from a column header element.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridColumnHeaderParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onColumnHeaderOver": {
"description": "Callback fired when a mouseover event comes from a column header element.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridColumnHeaderParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onColumnOrderChange": {
"description": "Callback fired when a column is reordered.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridColumnOrderChangeParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onColumnResize": {
"description": "Callback fired while a column is being resized.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridColumnResizeParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onColumnVisibilityModelChange": {
"description": "Callback fired when the column visibility model changes.",
"deprecated": "",
"typeDescriptions": {
"model": "The new model.",
"details": "Additional details for this callback."
}
},
"onColumnWidthChange": {
"description": "Callback fired when the width of a column is changed.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridColumnResizeParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onDetailPanelExpandedRowIdsChange": {
"description": "Callback fired when the detail panel of a row is opened or closed.",
"deprecated": "",
"typeDescriptions": {
"ids": "The ids of the rows which have the detail panel open.",
"details": "Additional details for this callback."
}
},
"onExcelExportStateChange": {
"description": "Callback fired when the state of the Excel export changes.",
"deprecated": "",
"typeDescriptions": { "inProgress": "Indicates if the task is in progress." }
},
"onFetchRows": {
"description": "Callback fired when rowCount is set and the next batch of virtualized rows is rendered.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridFetchRowsParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onFilterModelChange": {
"description": "Callback fired when the Filter model changes before the filters are applied.",
"deprecated": "",
"typeDescriptions": {
"model": "With all properties from <a href=\"/x/api/data-grid/grid-filter-model/\">GridFilterModel</a>.",
"details": "Additional details for this callback."
}
},
"onMenuClose": {
"description": "Callback fired when the menu is closed.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridMenuParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onMenuOpen": {
"description": "Callback fired when the menu is opened.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridMenuParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onPaginationModelChange": {
"description": "Callback fired when the pagination model has changed.",
"deprecated": "",
"typeDescriptions": {
"model": "Updated pagination model.",
"details": "Additional details for this callback."
}
},
"onPinnedColumnsChange": {
"description": "Callback fired when the pinned columns have changed.",
"deprecated": "",
"typeDescriptions": {
"pinnedColumns": "The changed pinned columns.",
"details": "Additional details for this callback."
}
},
"onPreferencePanelClose": {
"description": "Callback fired when the preferences panel is closed.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridPreferencePanelParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onPreferencePanelOpen": {
"description": "Callback fired when the preferences panel is opened.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridPreferencePanelParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onProcessRowUpdateError": {
"description": "Callback called when <code>processRowUpdate</code> throws an error or rejects.",
"deprecated": "",
"typeDescriptions": { "error": "The error thrown." }
},
"onResize": {
"description": "Callback fired when the grid is resized.",
"deprecated": "",
"typeDescriptions": {
"containerSize": "With all properties from ElementSize.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onRowClick": {
"description": "Callback fired when a row is clicked. Not called if the target clicked is an interactive element added by the built-in columns.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-row-params/\">GridRowParams</a>.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onRowDoubleClick": {
"description": "Callback fired when a double click event comes from a row container element.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from RowParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onRowEditCommit": {
"description": "Callback fired when the row changes are committed.",
"deprecated": "",
"typeDescriptions": {
"id": "The row id.",
"event": "The event that caused this prop to be called."
}
},
"onRowEditStart": {
"description": "Callback fired when the row turns to edit mode.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-row-params/\">GridRowParams</a>.",
"event": "The event that caused this prop to be called."
}
},
"onRowEditStop": {
"description": "Callback fired when the row turns to view mode.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from <a href=\"/x/api/data-grid/grid-row-params/\">GridRowParams</a>.",
"event": "The event that caused this prop to be called."
}
},
"onRowGroupingModelChange": {
"description": "Callback fired when the row grouping model changes.",
"deprecated": "",
"typeDescriptions": {
"model": "Columns used as grouping criteria.",
"details": "Additional details for this callback."
}
},
"onRowModesModelChange": {
"description": "Callback fired when the <code>rowModesModel</code> prop changes.",
"deprecated": "",
"typeDescriptions": {
"rowModesModel": "Object containing which rows are in "edit" mode.",
"details": "Additional details for this callback."
}
},
"onRowOrderChange": {
"description": "Callback fired when a row is being reordered.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridRowOrderChangeParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onRowSelectionModelChange": {
"description": "Callback fired when the selection state of one or multiple rows changes.",
"deprecated": "",
"typeDescriptions": {
"rowSelectionModel": "With all the row ids GridSelectionModel.",
"details": "Additional details for this callback."
}
},
"onRowsScrollEnd": {
"description": "Callback fired when scrolling to the bottom of the grid viewport.",
"deprecated": "",
"typeDescriptions": {
"params": "With all properties from GridRowScrollEndParams.",
"event": "The event object.",
"details": "Additional details for this callback."
}
},
"onSortModelChange": {
"description": "Callback fired when the sort model changes before a column is sorted.",
"deprecated": "",
"typeDescriptions": {
"model": "With all properties from GridSortModel.",
"details": "Additional details for this callback."
}
},
"pageSizeOptions": {
"description": "Select the pageSize dynamically using the component UI.",
"deprecated": "",
"typeDescriptions": {}
},
"pagination": {
"description": "If <code>true</code>, pagination is enabled.",
"deprecated": "",
"typeDescriptions": {}
},
"paginationMode": {
"description": "Pagination can be processed on the server or client-side. Set it to 'client' if you would like to handle the pagination on the client-side. Set it to 'server' if you would like to handle the pagination on the server-side.",
"deprecated": "",
"typeDescriptions": {}
},
"paginationModel": {
"description": "The pagination model of type GridPaginationModel which refers to current <code>page</code> and <code>pageSize</code>.",
"deprecated": "",
"typeDescriptions": {}
},
"pinnedColumns": {
"description": "The column fields to display pinned to left or right.",
"deprecated": "",
"typeDescriptions": {}
},
"pinnedRows": {
"description": "Rows data to pin on top or bottom.",
"deprecated": "",
"typeDescriptions": {}
},
"processRowUpdate": {
"description": "Callback called before updating a row with new values in the row and cell editing.",
"deprecated": "",
"typeDescriptions": {
"newRow": "Row object with the new values.",
"oldRow": "Row object with the old values.",
"Promise<R> | R": "The final values to update the row."
}
},
"rowBuffer": {
"description": "Number of extra rows to be rendered before/after the visible slice.",
"deprecated": "",
"typeDescriptions": {}
},
"rowCount": {
"description": "Set the total number of rows, if it is different from the length of the value <code>rows</code> prop. If some rows have children (for instance in the tree data), this number represents the amount of top level rows.",
"deprecated": "",
"typeDescriptions": {}
},
"rowGroupingColumnMode": {
"description": "If <code>single</code>, all the columns that are grouped are represented in the same grid column. If <code>multiple</code>, each column that is grouped is represented in its own grid column.",
"deprecated": "",
"typeDescriptions": {}
},
"rowGroupingModel": {
"description": "Set the row grouping model of the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"rowHeight": {
"description": "Sets the height in pixel of a row in the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"rowModesModel": {
"description": "Controls the modes of the rows.",
"deprecated": "",
"typeDescriptions": {}
},
"rowReordering": {
"description": "If <code>true</code>, the reordering of rows is enabled.",
"deprecated": "",
"typeDescriptions": {}
},
"rows": {
"description": "Set of rows of type GridRowsProp.",
"deprecated": "",
"typeDescriptions": {}
},
"rowSelection": {
"description": "If <code>false</code>, the row selection mode is disabled.",
"deprecated": "",
"typeDescriptions": {}
},
"rowSelectionModel": {
"description": "Sets the row selection model of the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"rowsLoadingMode": {
"description": "Loading rows can be processed on the server or client-side. Set it to 'client' if you would like enable infnite loading. Set it to 'server' if you would like to enable lazy loading. * @default "client"",
"deprecated": "",
"typeDescriptions": {}
},
"rowSpacingType": {
"description": "Sets the type of space between rows added by <code>getRowSpacing</code>.",
"deprecated": "",
"typeDescriptions": {}
},
"rowThreshold": {
"description": "Number of rows from the <code>rowBuffer</code> that can be visible before a new slice is rendered.",
"deprecated": "",
"typeDescriptions": {}
},
"scrollbarSize": {
"description": "Override the height/width of the grid inner scrollbar.",
"deprecated": "",
"typeDescriptions": {}
},
"scrollEndThreshold": {
"description": "Set the area in <code>px</code> at the bottom of the grid viewport where onRowsScrollEnd is called.",
"deprecated": "",
"typeDescriptions": {}
},
"showCellVerticalBorder": {
"description": "If <code>true</code>, the vertical borders of the cells are displayed.",
"deprecated": "",
"typeDescriptions": {}
},
"showColumnVerticalBorder": {
"description": "If <code>true</code>, the right border of the column headers are displayed.",
"deprecated": "",
"typeDescriptions": {}
},
"slotProps": {
"description": "Overridable components props dynamically passed to the component at rendering.",
"deprecated": "",
"typeDescriptions": {}
},
"slots": { "description": "Overridable components.", "deprecated": "", "typeDescriptions": {} },
"sortingMode": {
"description": "Sorting can be processed on the server or client-side. Set it to 'client' if you would like to handle sorting on the client-side. Set it to 'server' if you would like to handle sorting on the server-side.",
"deprecated": "",
"typeDescriptions": {}
},
"sortingOrder": {
"description": "The order of the sorting sequence.",
"deprecated": "",
"typeDescriptions": {}
},
"sortModel": {
"description": "Set the sort model of the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"sx": {
"description": "The system prop that allows defining system overrides as well as additional CSS styles.",
"deprecated": "",
"typeDescriptions": {}
},
"throttleRowsMs": {
"description": "If positive, the Grid will throttle updates coming from <code>apiRef.current.updateRows</code> and <code>apiRef.current.setRows</code>. It can be useful if you have a high update rate but do not want to do heavy work like filtering / sorting or rendering on each individual update.",
"deprecated": "",
"typeDescriptions": {}
},
"treeData": {
"description": "If <code>true</code>, the rows will be gathered in a tree structure according to the <code>getTreeDataPath</code> prop.",
"deprecated": "",
"typeDescriptions": {}
},
"unstable_cellSelection": {
"description": "If <code>true</code>, the cell selection mode is enabled.",
"deprecated": "",
"typeDescriptions": {}
},
"unstable_cellSelectionModel": {
"description": "Set the cell selection model of the grid.",
"deprecated": "",
"typeDescriptions": {}
},
"unstable_headerFilters": {
"description": "If <code>true</code>, enables the data grid filtering on header feature.",
"deprecated": "",
"typeDescriptions": {}
},
"unstable_ignoreValueFormatterDuringExport": {
"description": "If <code>true</code>, the grid will not use <code>valueFormatter</code> when exporting to CSV or copying to clipboard. If an object is provided, you can choose to ignore the <code>valueFormatter</code> for CSV export or clipboard export.",
"deprecated": "",
"typeDescriptions": {}
},
"unstable_onCellSelectionModelChange": {
"description": "Callback fired when the selection state of one or multiple cells changes.",
"deprecated": "",
"typeDescriptions": {
"cellSelectionModel": "Object in the shape of GridCellSelectionModel containing the selected cells.",
"details": "Additional details for this callback."
}
},
"unstable_splitClipboardPastedText": {
"description": "The function is used to split the pasted text into rows and cells.",
"deprecated": "",
"typeDescriptions": { "text": "The text pasted from the clipboard." }
}
},
"classDescriptions": {
"actionsCell": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the root element of the cell with type=\"actions\""
},
"aggregationColumnHeader": {
"description": "Styles applied to {{nodeName}} when {{conditions}}.",
"nodeName": "the root element of the column header",
"conditions": "aggregated"
},
"aggregationColumnHeader--alignLeft": {
"description": "Styles applied to {{nodeName}} when {{conditions}}.",
"nodeName": "the root element of the header",
"conditions": "aggregation if <code>headerAlign=\"left\"</code>"
},
"aggregationColumnHeader--alignCenter": {
"description": "Styles applied to {{nodeName}} when {{conditions}}.",
"nodeName": "the root element of the header",
"conditions": "aggregation if <code>headerAlign=\"center\"</code>"
},
"aggregationColumnHeader--alignRight": {
"description": "Styles applied to {{nodeName}} when {{conditions}}.",
"nodeName": "the root element of the header",
"conditions": "aggregation if <code>headerAlign=\"right\"</code>"
},
"aggregationColumnHeaderLabel": {
"description": "Styles applied to {{nodeName}} when {{conditions}}.",
"nodeName": "the aggregation label in the column header",
"conditions": "aggregated"
},
"autoHeight": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the root element",
"conditions": "<code>autoHeight={true}</code>"
},
"booleanCell": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the icon of the boolean cell"
},
"cell--editable": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the cell element",
"conditions": "the cell is editable"
},
"cell--editing": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the cell element",
"conditions": "the cell is in edit mode"
},
"cell--textCenter": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the cell element",
"conditions": "<code>align=\"center\"</code>"
},
"cell--textLeft": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the cell element",
"conditions": "<code>align=\"left\"</code>"
},
"cell--textRight": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the cell element",
"conditions": "<code>align=\"right\"</code>"
},
"cell--withRenderer": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the cell element",
"conditions": "the cell has a custom renderer"
},
"cell--rangeTop": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the cell element",
"conditions": "it is at the top edge of a cell selection range"
},
"cell--rangeBottom": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the cell element",
"conditions": "it is at the bottom edge of a cell selection range"
},
"cell--rangeLeft": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the cell element",
"conditions": "it is at the left edge of a cell selection range"
},
"cell--rangeRight": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the cell element",
"conditions": "it is at the right edge of a cell selection range"
},
"cell": { "description": "Styles applied to {{nodeName}}.", "nodeName": "the cell element" },
"cellContent": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the element that wraps the cell content"
},
"cellCheckbox": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the cell checkbox element"
},
"cellSkeleton": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the skeleton cell element"
},
"checkboxInput": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the selection checkbox element"
},
"columnHeader--alignCenter": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header",
"conditions": "<code>headerAlign=\"center\"</code>"
},
"columnHeader--alignLeft": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header",
"conditions": "<code>headerAlign=\"left\"</code>"
},
"columnHeader--alignRight": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header",
"conditions": "<code>headerAlign=\"right\"</code>"
},
"columnHeader--dragging": {
"description": "Styles applied to {{nodeName}} when {{conditions}}.",
"nodeName": "the floating column header element",
"conditions": "it is dragged"
},
"columnHeader--moving": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header",
"conditions": "it is being dragged"
},
"columnHeader--numeric": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header",
"conditions": "the type of the column is <code>number</code>"
},
"columnHeader--sortable": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header",
"conditions": "the column is sortable"
},
"columnHeader--sorted": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header",
"conditions": "the column is sorted"
},
"columnHeader--filtered": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header",
"conditions": "the column has a filter applied to it"
},
"columnHeader": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column header element"
},
"columnGroupHeader": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column group header element"
},
"columnHeaderCheckbox": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the header checkbox cell element"
},
"columnHeaderDraggableContainer": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column header's draggable container element"
},
"rowReorderCellPlaceholder": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the row's draggable placeholder element inside the special row reorder cell"
},
"columnHeaderDropZone": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column headers wrapper",
"conditions": "a column is being dragged"
},
"columnHeaderTitle": { "description": "Styles applied to the column header's title element;" },
"columnHeaderTitleContainer": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column header's title container element"
},
"columnHeaderTitleContainerContent": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column header's title excepted buttons"
},
"columnHeader--filledGroup": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column group header cell",
"conditions": "not empty"
},
"columnHeader--emptyGroup": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the empty column group header cell"
},
"columnHeader--showColumnBorder": {
"description": "Styles applied to {{nodeName}} when {{conditions}}.",
"nodeName": "the column group header cell",
"conditions": "show column border"
},
"columnHeaders": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column headers"
},
"columnHeadersInner": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column headers's inner element"
},
"columnHeadersInner--scrollable": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column headers's inner element",
"conditions": "there is a horizontal scrollbar"
},
"columnSeparator--resizable": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header separator",
"conditions": "the column is resizable"
},
"columnSeparator--resizing": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header separator",
"conditions": "the column is being resized"
},
"columnSeparator--sideLeft": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header separator",
"conditions": "the side is \"left\""
},
"columnSeparator--sideRight": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the column header separator",
"conditions": "the side is \"right\""
},
"columnSeparator": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column header separator element"
},
"columnsPanel": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the columns panel element"
},
"columnsPanelRow": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the columns panel row element"
},
"detailPanel": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the detail panel element"
},
"detailPanels": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the detail panels wrapper element"
},
"detailPanelToggleCell": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the detail panel toggle cell element"
},
"detailPanelToggleCell--expanded": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the detail panel toggle cell element",
"conditions": "expanded"
},
"footerCell": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the root element of the cell inside a footer row"
},
"panel": { "description": "Styles applied to {{nodeName}}.", "nodeName": "the panel element" },
"panelHeader": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the panel header element"
},
"panelWrapper": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the panel wrapper element"
},
"panelContent": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the panel content element"
},
"panelFooter": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the panel footer element"
},
"paper": { "description": "Styles applied to {{nodeName}}.", "nodeName": "the paper element" },
"editBooleanCell": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "root of the boolean edit component"
},
"filterForm": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the root of the filter form component"
},
"filterFormDeleteIcon": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the delete icon of the filter form component"
},
"filterFormLogicOperatorInput": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the link operator input of the filter form component"
},
"filterFormColumnInput": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column input of the filter form component"
},
"filterFormOperatorInput": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the operator input of the filter form component"
},
"filterFormValueInput": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the value input of the filter form component"
},
"editInputCell": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the root of the input component"
},
"filterIcon": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the filter icon element"
},
"footerContainer": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the footer container element"
},
"iconButtonContainer": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column header icon's container"
},
"iconSeparator": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column header separator icon element"
},
"headerFilterRow": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the column header filter row"
},
"main": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the main container element"
},
"menu": { "description": "Styles applied to {{nodeName}}.", "nodeName": "the menu element" },
"menuIcon": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the menu icon element"
},
"menuIconButton": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the menu icon button element"
},
"menuOpen": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the menu icon element",
"conditions": "the menu is open"
},
"menuList": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the menu list element"
},
"overlayWrapper": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the overlay wrapper element"
},
"overlayWrapperInner": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the overlay wrapper inner element"
},
"overlay": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the overlay element"
},
"virtualScroller": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the virtualization container"
},
"virtualScrollerContent": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the virtualization content"
},
"virtualScrollerContent--overflowed": {
"description": "Styles applied to {{nodeName}} when {{conditions}}.",
"nodeName": "the virtualization content",
"conditions": "its height is bigger than the virtualization container"
},
"virtualScrollerRenderZone": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the virtualization render zone"
},
"pinnedColumns": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the pinned columns"
},
"pinnedColumns--left": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the left pinned columns"
},
"pinnedColumns--right": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the right pinned columns"
},
"pinnedColumnHeaders": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the pinned column headers"
},
"pinnedColumnHeaders--left": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the left pinned column headers"
},
"pinnedColumnHeaders--right": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the right pinned column headers"
},
"root": { "description": "Styles applied to the root element." },
"root--densityStandard": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the root element",
"conditions": "density is \"standard\" (default)"
},
"root--densityComfortable": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the root element",
"conditions": "density is \"comfortable\""
},
"root--densityCompact": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the root element",
"conditions": "density is \"compact\""
},
"root--disableUserSelection": {
"description": "Styles applied to {{nodeName}} when {{conditions}}.",
"nodeName": "the root element",
"conditions": "user selection is disabled"
},
"row--editable": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the row element",
"conditions": "the row is editable"
},
"row--editing": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the row element",
"conditions": "the row is in edit mode"
},
"row--dragging": {
"description": "Styles applied to {{nodeName}} when {{conditions}}.",
"nodeName": "the floating special row reorder cell element",
"conditions": "it is dragged"
},
"row--lastVisible": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the last visible row element on every page of the grid"
},
"row--dynamicHeight": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the row",
"conditions": "it has dynamic row height"
},
"row--detailPanelExpanded": {
"description": "Styles applied to {{nodeName}} if {{conditions}}.",
"nodeName": "the row",
"conditions": "its detail panel is open"
},
"row": { "description": "Styles applied to {{nodeName}}.", "nodeName": "the row element" },
"rowCount": {
"description": "Styles applied to {{nodeName}}.\nOnly works when pagination is disabled.",
"nodeName": "the footer row count element to show the total number of rows"
},
"rowReorderCellContainer": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the row reorder cell container element"
},
"rowReorderCell": {
"description": "Styles applied to the root element of the row reorder cell"
},
"rowReorderCell--draggable": {
"description": "Styles applied to the root element of the row reorder cell when dragging is allowed"
},
"scrollArea": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "both scroll area elements"
},
"scrollArea--left": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the left scroll area element"
},
"scrollArea--right": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the right scroll area element"
},
"selectedRowCount": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the footer selected row count element"
},
"sortIcon": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the sort icon element"
},
"toolbarContainer": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the toolbar container element"
},
"toolbarFilterList": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the toolbar filter list element"
},
"withBorderColor": {
"description": "Styles applied to {{nodeName}}, {{conditions}}.\nSets border color only.",
"nodeName": "cells",
"conditions": "column header and other elements that have border"
},
"cell--withRightBorder": {
"description": "Styles applied the cell if `showColumnVerticalBorder={true}`."
},
"columnHeader--withRightBorder": {
"description": "Styles applied the column header if `showColumnVerticalBorder={true}`."
},
"treeDataGroupingCell": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the root of the grouping column of the tree data"
},
"treeDataGroupingCellToggle": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the toggle of the grouping cell of the tree data"
},
"groupingCriteriaCell": {
"description": "Styles applied to the root element of the grouping criteria cell"
},
"groupingCriteriaCellToggle": {
"description": "Styles applied to the toggle of the grouping criteria cell"
},
"pinnedRows": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the pinned rows container"
},
"pinnedRows--top": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the top pinned rows container"
},
"pinnedRows--bottom": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "the bottom pinned rows container"
},
"pinnedRowsRenderZone": {
"description": "Styles applied to {{nodeName}}.",
"nodeName": "pinned rows render zones"
}
},
"slotDescriptions": {
"baseButton": "The custom Button component used in the grid.",
"baseCheckbox": "The custom Checkbox component used in the grid for both header and cells.",
"baseChip": "The custom Chip component used in the grid.",
"baseFormControl": "The custom FormControl component used in the grid.",
"baseIconButton": "The custom IconButton component used in the grid.",
"baseInputAdornment": "The custom InputAdornment component used in the grid.",
"baseInputLabel": "The custom InputLabel component used in the grid.",
"basePopper": "The custom Popper component used in the grid.",
"baseSelect": "The custom Select component used in the grid.",
"baseSelectOption": "The custom SelectOption component used in the grid.",
"baseSwitch": "The custom Switch component used in the grid.",
"baseTextField": "The custom TextField component used in the grid.",
"baseTooltip": "The custom Tooltip component used in the grid.",
"booleanCellFalseIcon": "Icon displayed on the boolean cell to represent the false value.",
"booleanCellTrueIcon": "Icon displayed on the boolean cell to represent the true value.",
"cell": "Component rendered for each cell.",
"columnFilteredIcon": "Icon displayed on the column header menu to show that a filter has been applied to the column.",
"columnHeaderFilterIconButton": "Filter icon component rendered in each column header.",
"columnHeaders": "Component responsible for rendering the column headers.",
"columnMenu": "Column menu component rendered by clicking on the 3 dots "kebab" icon in column headers.",
"columnMenuAggregationIcon": "Icon displayed in column menu for aggregation",
"columnMenuClearIcon": "Icon displayed in column menu for clearing values",
"columnMenuFilterIcon": "Icon displayed in column menu for filter",
"columnMenuGroupIcon": "Icon displayed in column menu for grouping",
"columnMenuHideIcon": "Icon displayed in column menu for hiding column",
"columnMenuIcon": "Icon displayed on the side of the column header title to display the filter input component.",
"columnMenuManageColumnsIcon": "Icon displayed in column menu for showing all columns",
"columnMenuPinLeftIcon": "Icon displayed in column menu for left pinning",
"columnMenuPinRightIcon": "Icon displayed in column menu for right pinning",
"columnMenuSortAscendingIcon": "Icon displayed in column menu for ascending sort",
"columnMenuSortDescendingIcon": "Icon displayed in column menu for descending sort",
"columnMenuUngroupIcon": "Icon displayed in column menu for ungrouping",
"columnReorderIcon": "Icon displayed on the column reorder button.",
"columnResizeIcon": "Icon displayed in between two column headers that allows to resize the column header.",
"columnSelectorIcon": "Icon displayed on the column menu selector tab.",
"columnSortedAscendingIcon": "Icon displayed on the side of the column header title when sorted in ascending order.",
"columnSortedDescendingIcon": "Icon displayed on the side of the column header title when sorted in descending order.",
"columnUnsortedIcon": "Icon displayed on the side of the column header title when unsorted.",
"columnsPanel": "GridColumns panel component rendered when clicking the columns button.",
"densityComfortableIcon": "Icon displayed on the "comfortable" density option in the toolbar.",
"densityCompactIcon": "Icon displayed on the compact density option in the toolbar.",
"densityStandardIcon": "Icon displayed on the standard density option in the toolbar.",
"detailPanelCollapseIcon": "Icon displayed on the detail panel toggle column when expanded.",
"detailPanelExpandIcon": "Icon displayed on the detail panel toggle column when collapsed.",
"exportIcon": "Icon displayed on the open export button present in the toolbar by default.",
"filterPanel": "Filter panel component rendered when clicking the filter button.",
"filterPanelAddIcon": "Icon displayed for deleting the filter from filter panel.",
"filterPanelDeleteIcon": "Icon displayed for deleting the filter from filter panel.",
"filterPanelRemoveAllIcon": "Icon displayed for deleting all the active filters from filter panel.",
"footer": "Footer component rendered at the bottom of the grid viewport.",
"footerRowCount": "Row count component rendered in the footer",
"groupingCriteriaCollapseIcon": "Icon displayed on the grouping column when the children are expanded",
"groupingCriteriaExpandIcon": "Icon displayed on the grouping column when the children are collapsed",
"headerFilterCell": "Component responsible for showing menu adornment in Header filter row",
"headerFilterMenu": "Component responsible for showing menu in Header filter row",
"loadIcon": "Icon displayed on the input while processing.",
"loadingOverlay": "Loading overlay component rendered when the grid is in a loading state.",
"moreActionsIcon": "Icon displayed on the <code>actions</code> column type to open the menu.",
"noResultsOverlay": "No results overlay component rendered when the grid has no results after filtering.",
"noRowsOverlay": "No rows overlay component rendered when the grid has no rows.",
"openFilterButtonIcon": "Icon displayed on the open filter button present in the toolbar by default.",
"pagination": "Pagination component rendered in the grid footer by default.",
"panel": "Panel component wrapping the filters and columns panels.",
"preferencesPanel": "PreferencesPanel component rendered inside the Header component.",
"quickFilterClearIcon": "Icon displayed on the quick filter reset input.",
"quickFilterIcon": "Icon displayed on the quick filter input.",
"row": "Component rendered for each row.",
"rowReorderIcon": "Icon displayed on the <code>reorder</code> column type to reorder a row.",
"skeletonCell": "Component rendered for each skeleton cell.",
"toolbar": "Toolbar component rendered inside the Header component.",
"treeDataCollapseIcon": "Icon displayed on the tree data toggling column when the children are expanded",
"treeDataExpandIcon": "Icon displayed on the tree data toggling column when the children are collapsed"
}
}
| 4,277 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/data-grid-premium.js | import * as React from 'react';
import ApiPage from 'docs/src/modules/components/ApiPage';
import jsonPageContent from './data-grid-premium.json';
import descriptions from './data-grid-premium-translation.json';
export default function Page() {
return <ApiPage descriptions={{ en: descriptions }} pageContent={jsonPageContent} />;
}
| 4,278 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/data-grid-premium.json | {
"props": {
"columns": {
"type": { "name": "arrayOf", "description": "Array<object>" },
"required": true
},
"rows": {
"type": { "name": "arrayOf", "description": "Array<object>" },
"required": true
},
"aggregationFunctions": {
"type": { "name": "object" },
"default": "GRID_AGGREGATION_FUNCTIONS"
},
"aggregationModel": { "type": { "name": "object" } },
"aggregationRowsScope": {
"type": { "name": "enum", "description": "'all'<br>| 'filtered'" },
"default": "\"filtered\""
},
"apiRef": { "type": { "name": "shape", "description": "{ current: object }" } },
"aria-label": { "type": { "name": "string" } },
"aria-labelledby": { "type": { "name": "string" } },
"autoHeight": { "type": { "name": "bool" } },
"autoPageSize": { "type": { "name": "bool" } },
"cellModesModel": { "type": { "name": "object" } },
"checkboxSelection": { "type": { "name": "bool" } },
"checkboxSelectionVisibleOnly": {
"type": { "name": "custom", "description": "bool" },
"default": "false"
},
"classes": { "type": { "name": "object" }, "additionalInfo": { "cssApi": true } },
"clipboardCopyCellDelimiter": { "type": { "name": "string" }, "default": "'\\t'" },
"columnBuffer": { "type": { "name": "number" }, "default": "3" },
"columnHeaderHeight": { "type": { "name": "number" }, "default": "56" },
"columnThreshold": { "type": { "name": "number" }, "default": "3" },
"columnVisibilityModel": { "type": { "name": "object" } },
"components": {
"type": { "name": "object" },
"deprecated": true,
"deprecationInfo": "Use the <code>slots</code> prop instead."
},
"componentsProps": {
"type": { "name": "object" },
"deprecated": true,
"deprecationInfo": "Use the <code>slotProps</code> prop instead."
},
"defaultGroupingExpansionDepth": { "type": { "name": "number" }, "default": "0" },
"density": {
"type": {
"name": "enum",
"description": "'comfortable'<br>| 'compact'<br>| 'standard'"
},
"default": "\"standard\""
},
"detailPanelExpandedRowIds": {
"type": { "name": "arrayOf", "description": "Array<number<br>| string>" }
},
"disableAggregation": { "type": { "name": "bool" } },
"disableChildrenFiltering": { "type": { "name": "bool" } },
"disableChildrenSorting": { "type": { "name": "bool" } },
"disableClipboardPaste": { "type": { "name": "bool" } },
"disableColumnFilter": { "type": { "name": "bool" } },
"disableColumnMenu": { "type": { "name": "bool" } },
"disableColumnPinning": { "type": { "name": "bool" } },
"disableColumnReorder": { "type": { "name": "bool" } },
"disableColumnResize": { "type": { "name": "bool" } },
"disableColumnSelector": { "type": { "name": "bool" } },
"disableDensitySelector": { "type": { "name": "bool" } },
"disableMultipleColumnsFiltering": { "type": { "name": "bool" } },
"disableMultipleColumnsSorting": { "type": { "name": "bool" } },
"disableMultipleRowSelection": { "type": { "name": "bool" } },
"disableRowGrouping": { "type": { "name": "bool" } },
"disableRowSelectionOnClick": { "type": { "name": "bool" } },
"disableVirtualization": { "type": { "name": "bool" } },
"editMode": {
"type": { "name": "enum", "description": "'cell'<br>| 'row'" },
"default": "\"cell\""
},
"experimentalFeatures": {
"type": {
"name": "shape",
"description": "{ ariaV7?: bool, clipboardPaste?: bool, columnGrouping?: bool, lazyLoading?: bool, warnIfFocusStateIsNotSynced?: bool }"
}
},
"filterDebounceMs": { "type": { "name": "number" }, "default": "150" },
"filterMode": {
"type": { "name": "custom", "description": "'client'<br>| 'server'" },
"default": "\"client\""
},
"filterModel": {
"type": {
"name": "shape",
"description": "{ items: Array<{ field: string, id?: number<br>| string, operator: string, value?: any }>, logicOperator?: 'and'<br>| 'or', quickFilterExcludeHiddenColumns?: bool, quickFilterLogicOperator?: 'and'<br>| 'or', quickFilterValues?: array }"
}
},
"getAggregationPosition": {
"type": { "name": "func" },
"default": "`(groupNode) => groupNode == null ? 'footer' : 'inline'`",
"signature": {
"type": "function(groupNode: GridGroupNode) => GridAggregationPosition | null",
"describedArgs": ["groupNode"],
"returned": "GridAggregationPosition | null"
}
},
"getCellClassName": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridCellParams) => string",
"describedArgs": ["params"],
"returned": "string"
}
},
"getDetailPanelContent": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowParams) => React.JSX.Element",
"describedArgs": ["params"],
"returned": "React.JSX.Element"
}
},
"getDetailPanelHeight": {
"type": { "name": "func" },
"default": "\"() => 500\"",
"signature": {
"type": "function(params: GridRowParams) => number | string",
"describedArgs": ["params"],
"returned": "number | string"
}
},
"getEstimatedRowHeight": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowHeightParams) => number | null",
"describedArgs": ["params"],
"returned": "number | null"
}
},
"getRowClassName": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowClassNameParams) => string",
"describedArgs": ["params"],
"returned": "string"
}
},
"getRowHeight": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowHeightParams) => GridRowHeightReturnValue",
"describedArgs": ["params"],
"returned": "GridRowHeightReturnValue"
}
},
"getRowId": { "type": { "name": "func" } },
"getRowSpacing": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowSpacingParams) => GridRowSpacing",
"describedArgs": ["params"],
"returned": "GridRowSpacing"
}
},
"getTreeDataPath": {
"type": { "name": "func" },
"signature": {
"type": "function(row: R) => Array<string>",
"describedArgs": ["row"],
"returned": "Array<string>"
}
},
"groupingColDef": { "type": { "name": "union", "description": "func<br>| object" } },
"hideFooter": { "type": { "name": "bool" } },
"hideFooterPagination": { "type": { "name": "bool" } },
"hideFooterRowCount": {
"type": { "name": "custom", "description": "bool" },
"default": "false"
},
"hideFooterSelectedRowCount": { "type": { "name": "bool" } },
"initialState": { "type": { "name": "object" } },
"isCellEditable": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridCellParams) => boolean",
"describedArgs": ["params"],
"returned": "boolean"
}
},
"isGroupExpandedByDefault": {
"type": { "name": "func" },
"signature": {
"type": "function(node: GridGroupNode) => boolean",
"describedArgs": ["node"],
"returned": "boolean"
}
},
"isRowSelectable": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowParams) => boolean",
"describedArgs": ["params"],
"returned": "boolean"
}
},
"keepColumnPositionIfDraggedOutside": { "type": { "name": "bool" } },
"keepNonExistentRowsSelected": { "type": { "name": "bool" } },
"loading": { "type": { "name": "bool" } },
"localeText": { "type": { "name": "object" } },
"logger": {
"type": {
"name": "shape",
"description": "{ debug: func, error: func, info: func, warn: func }"
},
"default": "console"
},
"logLevel": {
"type": {
"name": "enum",
"description": "'debug'<br>| 'error'<br>| 'info'<br>| 'warn'<br>| false"
},
"default": "\"error\" (\"warn\" in dev mode)"
},
"nonce": { "type": { "name": "string" } },
"onAggregationModelChange": {
"type": { "name": "func" },
"signature": {
"type": "function(model: GridAggregationModel, details: GridCallbackDetails) => void",
"describedArgs": ["model", "details"]
}
},
"onCellClick": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridCellParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onCellDoubleClick": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridCellParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onCellEditStart": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridCellParams, event: MuiEvent<React.KeyboardEvent | React.MouseEvent>) => void",
"describedArgs": ["params", "event"]
}
},
"onCellEditStop": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridCellParams, event: MuiEvent<MuiBaseEvent>) => void",
"describedArgs": ["params", "event"]
}
},
"onCellKeyDown": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridCellParams, event: MuiEvent<React.KeyboardEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onCellModesModelChange": {
"type": { "name": "func" },
"signature": {
"type": "function(cellModesModel: GridCellModesModel, details: GridCallbackDetails) => void",
"describedArgs": ["cellModesModel", "details"]
}
},
"onClipboardCopy": {
"type": { "name": "func" },
"signature": { "type": "function(data: string) => void", "describedArgs": ["data"] }
},
"onClipboardPasteEnd": { "type": { "name": "func" } },
"onClipboardPasteStart": { "type": { "name": "func" } },
"onColumnHeaderClick": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridColumnHeaderParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onColumnHeaderDoubleClick": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridColumnHeaderParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onColumnHeaderEnter": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridColumnHeaderParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onColumnHeaderLeave": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridColumnHeaderParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onColumnHeaderOut": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridColumnHeaderParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onColumnHeaderOver": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridColumnHeaderParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onColumnOrderChange": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridColumnOrderChangeParams, event: MuiEvent<{}>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onColumnResize": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridColumnResizeParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onColumnVisibilityModelChange": {
"type": { "name": "func" },
"signature": {
"type": "function(model: GridColumnVisibilityModel, details: GridCallbackDetails) => void",
"describedArgs": ["model", "details"]
}
},
"onColumnWidthChange": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridColumnResizeParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onDetailPanelExpandedRowIdsChange": {
"type": { "name": "func" },
"signature": {
"type": "function(ids: Array<GridRowId>, details: GridCallbackDetails) => void",
"describedArgs": ["ids", "details"]
}
},
"onExcelExportStateChange": {
"type": { "name": "func" },
"signature": {
"type": "function(inProgress: string) => void",
"describedArgs": ["inProgress"]
}
},
"onFetchRows": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridFetchRowsParams, event: MuiEvent<{}>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onFilterModelChange": {
"type": { "name": "func" },
"signature": {
"type": "function(model: GridFilterModel, details: GridCallbackDetails) => void",
"describedArgs": ["model", "details"]
}
},
"onMenuClose": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridMenuParams, event: MuiEvent<{}>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onMenuOpen": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridMenuParams, event: MuiEvent<{}>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onPaginationModelChange": {
"type": { "name": "func" },
"signature": {
"type": "function(model: GridPaginationModel, details: GridCallbackDetails) => void",
"describedArgs": ["model", "details"]
}
},
"onPinnedColumnsChange": {
"type": { "name": "func" },
"signature": {
"type": "function(pinnedColumns: GridPinnedColumns, details: GridCallbackDetails) => void",
"describedArgs": ["pinnedColumns", "details"]
}
},
"onPreferencePanelClose": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridPreferencePanelParams, event: MuiEvent<{}>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onPreferencePanelOpen": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridPreferencePanelParams, event: MuiEvent<{}>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onProcessRowUpdateError": {
"type": { "name": "func" },
"signature": { "type": "function(error: any) => void", "describedArgs": ["error"] }
},
"onResize": {
"type": { "name": "func" },
"signature": {
"type": "function(containerSize: ElementSize, event: MuiEvent<{}>, details: GridCallbackDetails) => void",
"describedArgs": ["containerSize", "event", "details"]
}
},
"onRowClick": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onRowDoubleClick": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowParams, event: MuiEvent<React.MouseEvent>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onRowEditCommit": {
"type": { "name": "func" },
"signature": {
"type": "function(id: GridRowId, event: MuiEvent<MuiBaseEvent>) => void",
"describedArgs": ["id", "event"]
}
},
"onRowEditStart": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowParams, event: MuiEvent<React.KeyboardEvent | React.MouseEvent>) => void",
"describedArgs": ["params", "event"]
}
},
"onRowEditStop": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowParams, event: MuiEvent<MuiBaseEvent>) => void",
"describedArgs": ["params", "event"]
}
},
"onRowGroupingModelChange": {
"type": { "name": "func" },
"signature": {
"type": "function(model: GridRowGroupingModel, details: GridCallbackDetails) => void",
"describedArgs": ["model", "details"]
}
},
"onRowModesModelChange": {
"type": { "name": "func" },
"signature": {
"type": "function(rowModesModel: GridRowModesModel, details: GridCallbackDetails) => void",
"describedArgs": ["rowModesModel", "details"]
}
},
"onRowOrderChange": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowOrderChangeParams, event: MuiEvent<{}>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onRowSelectionModelChange": {
"type": { "name": "func" },
"signature": {
"type": "function(rowSelectionModel: GridRowSelectionModel, details: GridCallbackDetails) => void",
"describedArgs": ["rowSelectionModel", "details"]
}
},
"onRowsScrollEnd": {
"type": { "name": "func" },
"signature": {
"type": "function(params: GridRowScrollEndParams, event: MuiEvent<{}>, details: GridCallbackDetails) => void",
"describedArgs": ["params", "event", "details"]
}
},
"onSortModelChange": {
"type": { "name": "func" },
"signature": {
"type": "function(model: GridSortModel, details: GridCallbackDetails) => void",
"describedArgs": ["model", "details"]
}
},
"pageSizeOptions": {
"type": {
"name": "arrayOf",
"description": "Array<number<br>| { label: string, value: number }>"
},
"default": "[25, 50, 100]"
},
"pagination": { "type": { "name": "bool" } },
"paginationMode": {
"type": { "name": "enum", "description": "'client'<br>| 'server'" },
"default": "\"client\""
},
"paginationModel": {
"type": { "name": "shape", "description": "{ page: number, pageSize: number }" }
},
"pinnedColumns": {
"type": {
"name": "shape",
"description": "{ left?: Array<string>, right?: Array<string> }"
}
},
"pinnedRows": {
"type": {
"name": "shape",
"description": "{ bottom?: Array<object>, top?: Array<object> }"
}
},
"processRowUpdate": {
"type": { "name": "func" },
"signature": {
"type": "function(newRow: R, oldRow: R) => Promise<R> | R",
"describedArgs": ["newRow", "oldRow"],
"returned": "Promise<R> | R"
}
},
"rowBuffer": { "type": { "name": "number" }, "default": "3" },
"rowCount": { "type": { "name": "number" } },
"rowGroupingColumnMode": {
"type": { "name": "enum", "description": "'multiple'<br>| 'single'" },
"default": "'single'"
},
"rowGroupingModel": { "type": { "name": "arrayOf", "description": "Array<string>" } },
"rowHeight": { "type": { "name": "number" }, "default": "52" },
"rowModesModel": { "type": { "name": "object" } },
"rowReordering": { "type": { "name": "bool" } },
"rowSelection": { "type": { "name": "bool" }, "default": "true" },
"rowSelectionModel": {
"type": {
"name": "union",
"description": "Array<number<br>| string><br>| number<br>| string"
}
},
"rowsLoadingMode": {
"type": { "name": "enum", "description": "'client'<br>| 'server'" }
},
"rowSpacingType": {
"type": { "name": "enum", "description": "'border'<br>| 'margin'" },
"default": "\"margin\""
},
"rowThreshold": { "type": { "name": "number" }, "default": "3" },
"scrollbarSize": { "type": { "name": "number" } },
"scrollEndThreshold": { "type": { "name": "number" }, "default": "80" },
"showCellVerticalBorder": { "type": { "name": "bool" } },
"showColumnVerticalBorder": { "type": { "name": "bool" } },
"slotProps": { "type": { "name": "object" } },
"slots": { "type": { "name": "object" } },
"sortingMode": {
"type": { "name": "enum", "description": "'client'<br>| 'server'" },
"default": "\"client\""
},
"sortingOrder": {
"type": { "name": "arrayOf", "description": "Array<'asc'<br>| 'desc'>" },
"default": "['asc', 'desc', null]"
},
"sortModel": {
"type": {
"name": "arrayOf",
"description": "Array<{ field: string, sort?: 'asc'<br>| 'desc' }>"
}
},
"sx": {
"type": {
"name": "union",
"description": "Array<func<br>| object<br>| bool><br>| func<br>| object"
},
"additionalInfo": { "sx": true }
},
"throttleRowsMs": { "type": { "name": "number" }, "default": "0" },
"treeData": { "type": { "name": "bool" } },
"unstable_cellSelection": { "type": { "name": "bool" } },
"unstable_cellSelectionModel": { "type": { "name": "object" } },
"unstable_headerFilters": { "type": { "name": "bool" } },
"unstable_ignoreValueFormatterDuringExport": {
"type": {
"name": "union",
"description": "{ clipboardExport?: bool, csvExport?: bool }<br>| bool"
},
"default": ": false"
},
"unstable_onCellSelectionModelChange": {
"type": { "name": "func" },
"signature": {
"type": "function(cellSelectionModel: GridCellSelectionModel, details: GridCallbackDetails) => void",
"describedArgs": ["cellSelectionModel", "details"]
}
},
"unstable_splitClipboardPastedText": {
"type": { "name": "func" },
"signature": { "type": "function(text: string) => void", "describedArgs": ["text"] }
}
},
"slots": [
{
"class": null,
"name": "baseButton",
"description": "The custom Button component used in the grid.",
"default": "Button"
},
{
"class": null,
"name": "baseCheckbox",
"description": "The custom Checkbox component used in the grid for both header and cells.",
"default": "Checkbox"
},
{
"class": null,
"name": "baseChip",
"description": "The custom Chip component used in the grid.",
"default": "Chip"
},
{
"class": null,
"name": "baseFormControl",
"description": "The custom FormControl component used in the grid.",
"default": "FormControl"
},
{
"class": null,
"name": "baseIconButton",
"description": "The custom IconButton component used in the grid.",
"default": "IconButton"
},
{
"class": null,
"name": "baseInputAdornment",
"description": "The custom InputAdornment component used in the grid.",
"default": "InputAdornment"
},
{
"class": null,
"name": "baseInputLabel",
"description": "The custom InputLabel component used in the grid.",
"default": "InputLabel"
},
{
"class": null,
"name": "basePopper",
"description": "The custom Popper component used in the grid.",
"default": "Popper"
},
{
"class": null,
"name": "baseSelect",
"description": "The custom Select component used in the grid.",
"default": "Select"
},
{
"class": null,
"name": "baseSelectOption",
"description": "The custom SelectOption component used in the grid.",
"default": "MenuItem"
},
{
"class": null,
"name": "baseSwitch",
"description": "The custom Switch component used in the grid.",
"default": "Switch"
},
{
"class": null,
"name": "baseTextField",
"description": "The custom TextField component used in the grid.",
"default": "TextField"
},
{
"class": null,
"name": "baseTooltip",
"description": "The custom Tooltip component used in the grid.",
"default": "Tooltip"
},
{
"class": null,
"name": "booleanCellFalseIcon",
"description": "Icon displayed on the boolean cell to represent the false value.",
"default": "GridCloseIcon"
},
{
"class": null,
"name": "booleanCellTrueIcon",
"description": "Icon displayed on the boolean cell to represent the true value.",
"default": "GridCheckIcon"
},
{
"class": null,
"name": "cell",
"description": "Component rendered for each cell.",
"default": "GridCell"
},
{
"class": null,
"name": "columnFilteredIcon",
"description": "Icon displayed on the column header menu to show that a filter has been applied to the column.",
"default": "GridFilterAltIcon"
},
{
"class": null,
"name": "columnHeaderFilterIconButton",
"description": "Filter icon component rendered in each column header.",
"default": "GridColumnHeaderFilterIconButton"
},
{
"class": null,
"name": "columnHeaders",
"description": "Component responsible for rendering the column headers.",
"default": "DataGridColumnHeaders"
},
{
"class": null,
"name": "columnMenu",
"description": "Column menu component rendered by clicking on the 3 dots "kebab" icon in column headers.",
"default": "GridColumnMenu"
},
{
"class": null,
"name": "columnMenuAggregationIcon",
"description": "Icon displayed in column menu for aggregation",
"default": "GridFunctionsIcon"
},
{
"class": null,
"name": "columnMenuClearIcon",
"description": "Icon displayed in column menu for clearing values",
"default": "GridClearIcon"
},
{
"class": null,
"name": "columnMenuFilterIcon",
"description": "Icon displayed in column menu for filter",
"default": "GridFilterAltIcon"
},
{
"class": null,
"name": "columnMenuGroupIcon",
"description": "Icon displayed in column menu for grouping",
"default": "GridGroupWorkIcon"
},
{
"class": null,
"name": "columnMenuHideIcon",
"description": "Icon displayed in column menu for hiding column",
"default": "GridVisibilityOffIcon"
},
{
"class": null,
"name": "columnMenuIcon",
"description": "Icon displayed on the side of the column header title to display the filter input component.",
"default": "GridTripleDotsVerticalIcon"
},
{
"class": null,
"name": "columnMenuManageColumnsIcon",
"description": "Icon displayed in column menu for showing all columns",
"default": "GridViewColumnIcon"
},
{
"class": null,
"name": "columnMenuPinLeftIcon",
"description": "Icon displayed in column menu for left pinning",
"default": "GridPushPinLeftIcon"
},
{
"class": null,
"name": "columnMenuPinRightIcon",
"description": "Icon displayed in column menu for right pinning",
"default": "GridPushPinRightIcon"
},
{
"class": null,
"name": "columnMenuSortAscendingIcon",
"description": "Icon displayed in column menu for ascending sort",
"default": "GridArrowUpwardIcon"
},
{
"class": null,
"name": "columnMenuSortDescendingIcon",
"description": "Icon displayed in column menu for descending sort",
"default": "GridArrowDownwardIcon"
},
{
"class": null,
"name": "columnMenuUngroupIcon",
"description": "Icon displayed in column menu for ungrouping",
"default": "GridWorkspacesIcon"
},
{
"class": null,
"name": "columnReorderIcon",
"description": "Icon displayed on the column reorder button.",
"default": "GridDragIcon"
},
{
"class": null,
"name": "columnResizeIcon",
"description": "Icon displayed in between two column headers that allows to resize the column header.",
"default": "GridSeparatorIcon"
},
{
"class": null,
"name": "columnSelectorIcon",
"description": "Icon displayed on the column menu selector tab.",
"default": "GridColumnIcon"
},
{
"class": null,
"name": "columnSortedAscendingIcon",
"description": "Icon displayed on the side of the column header title when sorted in ascending order.",
"default": "GridArrowUpwardIcon"
},
{
"class": null,
"name": "columnSortedDescendingIcon",
"description": "Icon displayed on the side of the column header title when sorted in descending order.",
"default": "GridArrowDownwardIcon"
},
{
"class": null,
"name": "columnUnsortedIcon",
"description": "Icon displayed on the side of the column header title when unsorted.",
"default": "GridColumnUnsortedIcon"
},
{
"class": null,
"name": "columnsPanel",
"description": "GridColumns panel component rendered when clicking the columns button.",
"default": "GridColumnsPanel"
},
{
"class": null,
"name": "densityComfortableIcon",
"description": "Icon displayed on the "comfortable" density option in the toolbar.",
"default": "GridViewStreamIcon"
},
{
"class": null,
"name": "densityCompactIcon",
"description": "Icon displayed on the compact density option in the toolbar.",
"default": "GridViewHeadlineIcon"
},
{
"class": null,
"name": "densityStandardIcon",
"description": "Icon displayed on the standard density option in the toolbar.",
"default": "GridTableRowsIcon"
},
{
"class": null,
"name": "detailPanelCollapseIcon",
"description": "Icon displayed on the detail panel toggle column when expanded.",
"default": "GridRemoveIcon"
},
{
"class": null,
"name": "detailPanelExpandIcon",
"description": "Icon displayed on the detail panel toggle column when collapsed.",
"default": "GridAddIcon"
},
{
"class": null,
"name": "exportIcon",
"description": "Icon displayed on the open export button present in the toolbar by default.",
"default": "GridSaveAltIcon"
},
{
"class": null,
"name": "filterPanel",
"description": "Filter panel component rendered when clicking the filter button.",
"default": "GridFilterPanel"
},
{
"class": null,
"name": "filterPanelAddIcon",
"description": "Icon displayed for deleting the filter from filter panel.",
"default": "GridAddIcon"
},
{
"class": null,
"name": "filterPanelDeleteIcon",
"description": "Icon displayed for deleting the filter from filter panel.",
"default": "GridDeleteIcon"
},
{
"class": null,
"name": "filterPanelRemoveAllIcon",
"description": "Icon displayed for deleting all the active filters from filter panel.",
"default": "GridDeleteForeverIcon"
},
{
"class": null,
"name": "footer",
"description": "Footer component rendered at the bottom of the grid viewport.",
"default": "GridFooter"
},
{
"class": null,
"name": "footerRowCount",
"description": "Row count component rendered in the footer",
"default": "GridRowCount"
},
{
"class": null,
"name": "groupingCriteriaCollapseIcon",
"description": "Icon displayed on the grouping column when the children are expanded",
"default": "GridExpandMoreIcon"
},
{
"class": null,
"name": "groupingCriteriaExpandIcon",
"description": "Icon displayed on the grouping column when the children are collapsed",
"default": "GridKeyboardArrowRight"
},
{
"class": null,
"name": "headerFilterCell",
"description": "Component responsible for showing menu adornment in Header filter row",
"default": "GridHeaderFilterCell"
},
{
"class": null,
"name": "headerFilterMenu",
"description": "Component responsible for showing menu in Header filter row",
"default": "GridHeaderFilterMenu"
},
{
"class": null,
"name": "loadIcon",
"description": "Icon displayed on the input while processing.",
"default": "GridLoadIcon"
},
{
"class": null,
"name": "loadingOverlay",
"description": "Loading overlay component rendered when the grid is in a loading state.",
"default": "GridLoadingOverlay"
},
{
"class": null,
"name": "moreActionsIcon",
"description": "Icon displayed on the <code>actions</code> column type to open the menu.",
"default": "GridMoreVertIcon"
},
{
"class": null,
"name": "noResultsOverlay",
"description": "No results overlay component rendered when the grid has no results after filtering.",
"default": "GridNoResultsOverlay"
},
{
"class": null,
"name": "noRowsOverlay",
"description": "No rows overlay component rendered when the grid has no rows.",
"default": "GridNoRowsOverlay"
},
{
"class": null,
"name": "openFilterButtonIcon",
"description": "Icon displayed on the open filter button present in the toolbar by default.",
"default": "GridFilterListIcon"
},
{
"class": null,
"name": "pagination",
"description": "Pagination component rendered in the grid footer by default.",
"default": "Pagination"
},
{
"class": null,
"name": "panel",
"description": "Panel component wrapping the filters and columns panels.",
"default": "GridPanel"
},
{
"class": null,
"name": "preferencesPanel",
"description": "PreferencesPanel component rendered inside the Header component.",
"default": "GridPreferencesPanel"
},
{
"class": null,
"name": "quickFilterClearIcon",
"description": "Icon displayed on the quick filter reset input.",
"default": "GridCloseIcon"
},
{
"class": null,
"name": "quickFilterIcon",
"description": "Icon displayed on the quick filter input.",
"default": "GridSearchIcon"
},
{
"class": null,
"name": "row",
"description": "Component rendered for each row.",
"default": "GridRow"
},
{
"class": null,
"name": "rowReorderIcon",
"description": "Icon displayed on the <code>reorder</code> column type to reorder a row.",
"default": "GridDragIcon"
},
{
"class": null,
"name": "skeletonCell",
"description": "Component rendered for each skeleton cell.",
"default": "GridSkeletonCell"
},
{
"class": null,
"name": "toolbar",
"description": "Toolbar component rendered inside the Header component.",
"default": "null"
},
{
"class": null,
"name": "treeDataCollapseIcon",
"description": "Icon displayed on the tree data toggling column when the children are expanded",
"default": "GridExpandMoreIcon"
},
{
"class": null,
"name": "treeDataExpandIcon",
"description": "Icon displayed on the tree data toggling column when the children are collapsed",
"default": "GridKeyboardArrowRight"
}
],
"name": "DataGridPremium",
"imports": [
"import { DataGridPremium } from '@mui/x-data-grid-premium/DataGridPremium';",
"import { DataGridPremium } from '@mui/x-data-grid-premium';"
],
"styles": {
"classes": [
"actionsCell",
"aggregationColumnHeader",
"aggregationColumnHeader--alignLeft",
"aggregationColumnHeader--alignCenter",
"aggregationColumnHeader--alignRight",
"aggregationColumnHeaderLabel",
"autoHeight",
"booleanCell",
"cell--editable",
"cell--editing",
"cell--textCenter",
"cell--textLeft",
"cell--textRight",
"cell--withRenderer",
"cell--rangeTop",
"cell--rangeBottom",
"cell--rangeLeft",
"cell--rangeRight",
"cell",
"cellContent",
"cellCheckbox",
"cellSkeleton",
"checkboxInput",
"columnHeader--alignCenter",
"columnHeader--alignLeft",
"columnHeader--alignRight",
"columnHeader--dragging",
"columnHeader--moving",
"columnHeader--numeric",
"columnHeader--sortable",
"columnHeader--sorted",
"columnHeader--filtered",
"columnHeader",
"columnGroupHeader",
"columnHeaderCheckbox",
"columnHeaderDraggableContainer",
"rowReorderCellPlaceholder",
"columnHeaderDropZone",
"columnHeaderTitle",
"columnHeaderTitleContainer",
"columnHeaderTitleContainerContent",
"columnHeader--filledGroup",
"columnHeader--emptyGroup",
"columnHeader--showColumnBorder",
"columnHeaders",
"columnHeadersInner",
"columnHeadersInner--scrollable",
"columnSeparator--resizable",
"columnSeparator--resizing",
"columnSeparator--sideLeft",
"columnSeparator--sideRight",
"columnSeparator",
"columnsPanel",
"columnsPanelRow",
"detailPanel",
"detailPanels",
"detailPanelToggleCell",
"detailPanelToggleCell--expanded",
"footerCell",
"panel",
"panelHeader",
"panelWrapper",
"panelContent",
"panelFooter",
"paper",
"editBooleanCell",
"filterForm",
"filterFormDeleteIcon",
"filterFormLogicOperatorInput",
"filterFormColumnInput",
"filterFormOperatorInput",
"filterFormValueInput",
"editInputCell",
"filterIcon",
"footerContainer",
"iconButtonContainer",
"iconSeparator",
"headerFilterRow",
"main",
"menu",
"menuIcon",
"menuIconButton",
"menuOpen",
"menuList",
"overlayWrapper",
"overlayWrapperInner",
"overlay",
"virtualScroller",
"virtualScrollerContent",
"virtualScrollerContent--overflowed",
"virtualScrollerRenderZone",
"pinnedColumns",
"pinnedColumns--left",
"pinnedColumns--right",
"pinnedColumnHeaders",
"pinnedColumnHeaders--left",
"pinnedColumnHeaders--right",
"root",
"root--densityStandard",
"root--densityComfortable",
"root--densityCompact",
"root--disableUserSelection",
"row--editable",
"row--editing",
"row--dragging",
"row--lastVisible",
"row--dynamicHeight",
"row--detailPanelExpanded",
"row",
"rowCount",
"rowReorderCellContainer",
"rowReorderCell",
"rowReorderCell--draggable",
"scrollArea",
"scrollArea--left",
"scrollArea--right",
"selectedRowCount",
"sortIcon",
"toolbarContainer",
"toolbarFilterList",
"withBorderColor",
"cell--withRightBorder",
"columnHeader--withRightBorder",
"treeDataGroupingCell",
"treeDataGroupingCellToggle",
"groupingCriteriaCell",
"groupingCriteriaCellToggle",
"pinnedRows",
"pinnedRows--top",
"pinnedRows--bottom",
"pinnedRowsRenderZone"
],
"globalClasses": {},
"name": "MuiDataGrid"
},
"forwardsRefTo": "GridRoot",
"filename": "/packages/grid/x-data-grid-premium/src/DataGridPremium/DataGridPremium.tsx",
"demos": "<ul><li><a href=\"/x/react-data-grid/#commercial-version\">DataGridPremium</a></li></ul>"
}
| 4,279 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/demos.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from './demos.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,280 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/demos.md | # Demos
<p class="description">Demos</p>
## Standard demo
{{"demo": "DemoInDocs.js"}}
## "bg": "inline" demo
{{"demo": "DemoInDocs.js", "bg": "inline"}}
## "bg": true
{{"demo": "DemoInDocs.js", "bg": true}}
## "hideToolbar": true
{{"demo": "DemoInDocs.js", "hideToolbar": true}}
## "hideToolbar": true, "bg": true
{{"demo": "DemoInDocs.js", "hideToolbar": true, "bg": true}}
## "hideToolbar": true, "bg": "inline"
{{"demo": "DemoInDocs.js", "hideToolbar": true, "bg": "inline"}}
| 4,281 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/headers.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from './headers.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,282 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/headers.md | # Headers
<p class="description">Headers.</p>
## What is Lorem Ipsum?
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.
### Where does it come from?
Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old.
#### Why do we use it?
It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to using 'Content here, content here', making it look like readable English.
## Header with Pro plan [<span class="plan-pro"></span>](/x/introduction/licensing/#pro-plan 'Pro plan')
## Header with Premium plan [<span class="plan-premium"></span>](/x/introduction/licensing/#premium-plan 'premium plan')
| 4,283 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/markdown.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from './markdown.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,284 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/docs/markdown.md | # Markdown
<p class="description">Markdown.</p>
## Nested lists
- First item
- First item
- Second item
- Second item
- First item
- Second item
## Tight lists
https://spec.commonmark.org/0.30/#tight
- First item
- Second item
- Third item
## Loose lists
https://spec.commonmark.org/0.30/#loose
- Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Id semper risus in hendrerit gravida rutrum quisque non tellus.
- Rhoncus dolor purus non enim praesent. Turpis egestas sed tempus urna et pharetra pharetra massa.
- Leo vel orci porta non pulvinar neque. Faucibus interdum posuere lorem ipsum dolor sit amet consectetur.
## Link
https://spec.commonmark.org/0.30/#links
- Link [with a title](#link 'Stay on the same page').
## kbd tag
Make sure to include the `class="key"` declaration in each individual `kbd` element.
That's because when referring to two keys that should be pressed together－for example, <kbd><kbd class="key">Ctrl</kbd>+<kbd class="key">N</kbd></kbd>－the `kbd` elements are wrapped by a parent `kbd`, and we don't add styles to just the tag.
## This item is here to test a long table of contents instance
### And here is another one right below it to see how it feels like one level down
### Wordwithoutspaceasitwouldhappenwithapropdeclaration
Table of contents word wrap test.
| 4,285 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/joy/style-guide.tsx | import * as React from 'react';
import Container from '@mui/joy/Container';
import Box from '@mui/joy/Box';
import Button from '@mui/joy/Button';
import Typography from '@mui/joy/Typography';
import {
CssVarsProvider,
useColorScheme,
useTheme,
TypographySystem,
createGetCssVar,
} from '@mui/joy/styles';
const getCssVar = createGetCssVar();
const rgb2hex = (rgb: string) =>
`#${(rgb.match(/^rgb\((\d+),\s*(\d+),\s*(\d+)\)$/) || [])
.slice(1)
.map((n) => parseInt(n, 10).toString(16).padStart(2, '0'))
.join('')}`;
function ColorSchemePicker() {
const { mode, setMode } = useColorScheme();
const [mounted, setMounted] = React.useState(false);
React.useEffect(() => {
setMounted(true);
}, []);
if (!mounted) {
return null;
}
return (
<Box
sx={(theme) => ({
position: 'relative',
display: 'inline-flex',
alignItems: 'center',
border: '1px solid',
borderRadius: theme.vars.radius.md,
...theme.variants.outlined.neutral,
})}
>
<Box sx={{ display: 'flex', gap: '8px', p: '4px' }}>
{(['light', 'dark'] as const).map((modeId) => {
return (
<Button
key={modeId}
size="sm"
variant={mode === modeId ? 'solid' : 'plain'}
onClick={() => {
setMode(modeId);
}}
>
{modeId}
</Button>
);
})}
</Box>
</Box>
);
}
function ColorToken({ name, value }: { name: string; value: string }) {
const [color, setColor] = React.useState('');
const ref = React.useRef<HTMLDivElement | null>(null);
React.useEffect(() => {
if (ref.current && typeof window !== 'undefined') {
const style = window.getComputedStyle(ref.current);
setColor(rgb2hex(style.backgroundColor));
}
}, []);
return (
<div>
<Box
ref={ref}
sx={{
borderRadius: 'sm',
bgcolor: value,
width: 64,
height: 64,
mb: 1,
boxShadow: 'sm',
}}
/>
<Typography level="body-xs">{name}</Typography>
<Typography level="body-xs">{color}</Typography>
</div>
);
}
function PaletteTokens() {
const { colorScheme } = useColorScheme();
const { palette } = useTheme();
const [mounted, setMounted] = React.useState(false);
React.useEffect(() => {
setMounted(true);
}, []);
return (
<React.Fragment>
{mounted && (
<Typography level="title-md" sx={{ mb: 1 }}>
Palette ({colorScheme})
</Typography>
)}
<div>
{Object.entries(palette).map(([key, nestedObj]) => {
if (typeof nestedObj === 'string' && mounted) {
return <ColorToken key={key} name={key} value={nestedObj} />;
}
return (
<details key={key} style={{ padding: '0.5rem 0' }}>
<summary
style={{
marginBottom: '0.5rem',
fontFamily: getCssVar('fontFamily-body'),
cursor: 'pointer',
}}
>
{key}
</summary>
{key !== 'mode' && key !== 'colorScheme' && (
<Box
sx={{
display: 'grid',
gridTemplateColumns: 'repeat(auto-fill, minmax(120px, 1fr))',
gap: 2,
}}
>
{Object.entries(nestedObj).map(([nestedKey, value]) => (
<ColorToken key={nestedKey} name={nestedKey} value={value as string} />
))}
</Box>
)}
</details>
);
})}
</div>
</React.Fragment>
);
}
function TypographyScale() {
const { typography } = useTheme();
return (
<React.Fragment>
<Typography level="title-md" sx={{ mb: 1 }}>
Typography
</Typography>
{(Object.keys(typography) as Array<keyof TypographySystem>).map((level) => {
return (
<Typography key={level} level={level}>
{level}
</Typography>
);
})}
</React.Fragment>
);
}
export default function JoyStyleGuide() {
return (
<CssVarsProvider defaultMode="system">
<Container>
<Box
sx={{
position: 'sticky',
top: 0,
minHeight: 56,
borderBottom: '1px solid',
borderColor: 'neutral.outlinedBorder',
display: 'flex',
alignItems: 'center',
justifyContent: 'center',
bgcolor: 'background.body',
}}
>
<ColorSchemePicker />
</Box>
<Box sx={{ p: 2 }}>
<PaletteTokens />
</Box>
<Box sx={{ p: 2, display: 'flex', gap: 3 }}>
<Box sx={{ minWidth: 300 }}>
<TypographyScale />
</Box>
<div>
<Typography level="title-md" sx={{ mb: 1 }}>
UI Patterns
</Typography>
<Box sx={{ display: 'flex', gap: 2 }}>
<Box sx={{ width: 48, height: 48, bgcolor: 'background.level2' }} />
<div>
<Typography>List item title</Typography>
<Typography level="body-sm">Secondary text.</Typography>
</div>
</Box>
<hr />
<Box sx={{ display: 'flex', gap: 2, minWidth: 300 }}>
<Box sx={{ width: 48, height: 48, bgcolor: 'background.level2' }} />
<Box sx={{ flexGrow: 1 }}>
<Typography>List item title</Typography>
<Typography level="body-sm">Secondary text.</Typography>
</Box>
<Typography level="body-xs">metadata</Typography>
</Box>
<hr />
<Box sx={{ display: 'flex', gap: 2 }}>
<Box sx={{ width: 64, height: 64, bgcolor: 'background.level2' }} />
<Box sx={{ flexGrow: 1 }}>
<Typography>List item title</Typography>
<Typography level="body-sm">Secondary text.</Typography>
<Typography level="body-xs">metadata</Typography>
</Box>
</Box>
</div>
</Box>
</Container>
</CssVarsProvider>
);
}
| 4,286 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/joy/toggle-button.tsx | import * as React from 'react';
import { CssVarsProvider, useColorScheme } from '@mui/joy/styles';
import Button from '@mui/joy/Button';
import CssBaseline from '@mui/joy/CssBaseline';
import Box from '@mui/joy/Box';
import IconButton, { IconButtonProps } from '@mui/joy/IconButton';
import ToggleButtonGroup from '@mui/joy/ToggleButtonGroup';
import FormatAlignCenterIcon from '@mui/icons-material/FormatAlignCenter';
import FormatAlignJustifyIcon from '@mui/icons-material/FormatAlignJustify';
import DarkMode from '@mui/icons-material/DarkMode';
import LightMode from '@mui/icons-material/LightMode';
function ColorSchemeToggle({ onClick, sx, ...props }: IconButtonProps) {
const { mode, setMode } = useColorScheme();
const [mounted, setMounted] = React.useState(false);
React.useEffect(() => {
setMounted(true);
}, []);
if (!mounted) {
return <IconButton size="sm" variant="outlined" color="neutral" {...props} sx={sx} disabled />;
}
return (
<IconButton
id="toggle-mode"
size="sm"
variant="outlined"
color="neutral"
{...props}
onClick={(event) => {
if (mode === 'light') {
setMode('dark');
} else {
setMode('light');
}
onClick?.(event);
}}
sx={[
{
'& > *:first-of-type': {
display: mode === 'dark' ? 'none' : 'initial',
},
'& > *:last-of-type': {
display: mode === 'light' ? 'none' : 'initial',
},
},
...(Array.isArray(sx) ? sx : [sx]),
]}
>
<DarkMode />
<LightMode />
</IconButton>
);
}
export default function JoyToggleButton() {
const [alignment, setAlignment] = React.useState<Array<'left' | 'center'>>(['left']);
return (
<CssVarsProvider>
<CssBaseline />
<ColorSchemeToggle sx={{ my: 3 }} />
<Box sx={{ display: 'grid', gridTemplateColumns: 'repeat(4, 1fr)', gap: 2 }}>
{(['primary', 'neutral', 'danger', 'success', 'warning'] as const).map((color) =>
(['plain', 'outlined', 'soft', 'solid'] as const).map((variant) => (
<ToggleButtonGroup
key={`${variant}-${color}`}
variant={variant}
color={color}
// spacing={0.5}
value={alignment}
onChange={(event, newValue) => {
setAlignment(newValue);
}}
>
<Button value="left">Left Aligned</Button>
<IconButton value="center" aria-label="centered">
<FormatAlignCenterIcon />
</IconButton>
<IconButton value="justify" aria-label="justified" disabled>
<FormatAlignJustifyIcon />
</IconButton>
</ToggleButtonGroup>
)),
)}
</Box>
</CssVarsProvider>
);
}
| 4,287 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/material-next/menu.tsx | import * as React from 'react';
import { ThemeProvider, createTheme } from '@mui/material/styles';
import Button from '@mui/material/Button';
import Divider from '@mui/material/Divider';
import { useDropdown, DropdownContext } from '@mui/base/useDropdown';
import Menu, { MenuProps } from '@mui/material-next/Menu';
import MenuItem from '@mui/material-next/MenuItem';
import StableMenu from '@mui/material/Menu';
import StableMenuItem from '@mui/material/MenuItem';
import StableList from '@mui/material/List';
import StableListItem from '@mui/material/ListItem';
import StableListItemText from '@mui/material/ListItemText';
import { useMenuButton } from '@mui/base/useMenuButton';
const theme = createTheme();
const MenuButton = React.forwardRef<HTMLButtonElement, React.PropsWithChildren<{ id?: string }>>(
function MenuButton(
props: React.PropsWithChildren<{}>,
forwardedRef: React.ForwardedRef<HTMLButtonElement>,
) {
const { getRootProps: getButtonProps } = useMenuButton({ rootRef: forwardedRef });
return <Button type="button" {...props} {...getButtonProps()} />;
},
);
function DropdownUsage(props: MenuProps) {
const { contextValue: dropdownContextValue } = useDropdown();
return (
<DropdownContext.Provider value={dropdownContextValue}>
<MenuButton
id="basic-button"
// aria-controls={open ? 'basic-menu' : undefined}
aria-haspopup="true"
// aria-expanded={open ? 'true' : undefined}
>
Dropdown
</MenuButton>
<Menu
id="basic-menu"
{...props}
MenuListProps={{
'aria-labelledby': 'basic-button',
...props.MenuListProps,
}}
>
<MenuItem /* onClick={handleClose} */>Profile</MenuItem>
<MenuItem /* onClick={handleClose} */>My account</MenuItem>
<MenuItem /* onClick={handleClose} */ disabled>Subscription</MenuItem>
<Divider />
<MenuItem /* onClick={handleClose} */>Logout</MenuItem>
</Menu>
</DropdownContext.Provider>
);
}
function LegacyUsage(props: MenuProps) {
const [anchorEl, setAnchorEl] = React.useState<Element | null>(null);
const open = Boolean(anchorEl);
const handleClick = (event: React.MouseEvent) => {
setAnchorEl(event.currentTarget);
};
const handleClose = () => {
setAnchorEl(null);
};
return (
<div>
<Button
id="basic-button-legacy"
aria-controls={open ? 'basic-menu-legacy' : undefined}
aria-haspopup="true"
aria-expanded={open ? 'true' : undefined}
onClick={handleClick}
>
Legacy
</Button>
<Menu
id="basic-menu-legacy"
anchorEl={anchorEl}
open={open}
onClose={handleClose}
{...props}
MenuListProps={{
'aria-labelledby': 'basic-button-legacy',
...props.MenuListProps,
}}
>
<MenuItem onClick={handleClose}>Profile</MenuItem>
<MenuItem onClick={handleClose}>My account</MenuItem>
<MenuItem disabled>Subscription</MenuItem>
<Divider />
<MenuItem onClick={handleClose}>Logout</MenuItem>
</Menu>
</div>
);
}
function StableComponentUsage(props: {
MenuListProps?: { disabledItemsFocusable?: boolean };
autoFocus?: boolean;
}) {
const [anchorEl, setAnchorEl] = React.useState<Element | null>(null);
const open = Boolean(anchorEl);
const handleClick = (event: React.MouseEvent) => {
setAnchorEl(event.currentTarget);
};
const handleClose = () => {
setAnchorEl(null);
};
return (
<div>
<Button
id="basic-button-legacy-1"
aria-controls={open ? 'basic-menu-legacy-1' : undefined}
aria-haspopup="true"
aria-expanded={open ? 'true' : undefined}
onClick={handleClick}
>
Stable
</Button>
<StableMenu
id="basic-menu-legacy-1"
anchorEl={anchorEl}
open={open}
onClose={handleClose}
{...props}
MenuListProps={{
'aria-labelledby': 'basic-button-legacy-1',
...props.MenuListProps,
}}
>
<StableMenuItem onClick={handleClose}>Profile</StableMenuItem>
<StableMenuItem onClick={handleClose}>My account</StableMenuItem>
<StableMenuItem disabled>Subscription</StableMenuItem>
<Divider />
<StableMenuItem onClick={handleClose}>Logout</StableMenuItem>
</StableMenu>
</div>
);
}
const selectedMenuOptions = [
'Show some love to MUI',
'Show all notification content',
'Hide sensitive notification content',
'Hide all notification content',
];
function SelectedMenuLegacy() {
const [anchorEl, setAnchorEl] = React.useState<Element | null>(null);
const [selectedIndex, setSelectedIndex] = React.useState(1);
const open = Boolean(anchorEl);
const handleClickListItem = (event: React.MouseEvent) => {
setAnchorEl(event.currentTarget);
};
const handleMenuItemClick = (event: React.MouseEvent, index: number) => {
setSelectedIndex(index);
setAnchorEl(null);
};
const handleClose = () => {
setAnchorEl(null);
};
return (
<div>
<StableList component="nav" aria-label="Device settings" sx={{ bgcolor: 'background.paper' }}>
<StableListItem
button
id="lock-button"
aria-haspopup="listbox"
aria-controls="lock-menu"
aria-label="when device is locked"
aria-expanded={open ? 'true' : undefined}
onClick={handleClickListItem}
>
<StableListItemText
primary="When device is locked"
secondary={selectedMenuOptions[selectedIndex]}
/>
</StableListItem>
</StableList>
<Menu
id="lock-menu"
anchorEl={anchorEl}
open={open}
onClose={handleClose}
MenuListProps={{
'aria-labelledby': 'lock-button',
role: 'listbox',
}}
>
{selectedMenuOptions.map((option, index) => (
<MenuItem
key={option}
disabled={index === 0}
selected={index === selectedIndex}
onClick={(event) => handleMenuItemClick(event, index)}
>
{option}
</MenuItem>
))}
</Menu>
</div>
);
}
function SelectedMenuDropdown() {
const { contextValue: dropdownContextValue } = useDropdown();
const [selectedIndex, setSelectedIndex] = React.useState(1);
const handleMenuItemClick = (event: React.MouseEvent, index: number) => {
setSelectedIndex(index);
};
return (
<DropdownContext.Provider value={dropdownContextValue}>
<MenuButton
id="basic-button"
// aria-controls={open ? 'basic-menu' : undefined}
aria-haspopup="true"
// aria-expanded={open ? 'true' : undefined}
aria-label="Device settings"
>
{selectedMenuOptions[selectedIndex]}
</MenuButton>
<Menu
id="lock-menu"
MenuListProps={{
'aria-labelledby': 'lock-button',
role: 'listbox',
}}
>
{selectedMenuOptions.map((option, index) => (
<MenuItem
key={option}
disabled={index === 0}
selected={index === selectedIndex}
onClick={(event) => handleMenuItemClick(event, index)}
>
{option}
</MenuItem>
))}
</Menu>
</DropdownContext.Provider>
);
}
function SelectedMenuStable() {
const [anchorEl, setAnchorEl] = React.useState<Element | null>(null);
const [selectedIndex, setSelectedIndex] = React.useState(1);
const open = Boolean(anchorEl);
const handleClickListItem = (event: React.MouseEvent) => {
setAnchorEl(event.currentTarget);
};
const handleMenuItemClick = (event: React.MouseEvent, index: number) => {
setSelectedIndex(index);
setAnchorEl(null);
};
const handleClose = () => {
setAnchorEl(null);
};
return (
<div>
<StableList component="nav" aria-label="Device settings" sx={{ bgcolor: 'background.paper' }}>
<StableListItem
button
id="lock-button"
aria-haspopup="listbox"
aria-controls="lock-menu"
aria-label="when device is locked"
aria-expanded={open ? 'true' : undefined}
onClick={handleClickListItem}
>
<StableListItemText
primary="When device is locked"
secondary={selectedMenuOptions[selectedIndex]}
/>
</StableListItem>
</StableList>
<StableMenu
id="lock-menu"
anchorEl={anchorEl}
open={open}
onClose={handleClose}
MenuListProps={{
'aria-labelledby': 'lock-button',
role: 'listbox',
}}
>
{selectedMenuOptions.map((option, index) => (
<StableMenuItem
key={option}
disabled={index === 0}
selected={index === selectedIndex}
onClick={(event) => handleMenuItemClick(event, index)}
>
{option}
</StableMenuItem>
))}
</StableMenu>
</div>
);
}
export default function BasicMenu() {
return (
<ThemeProvider theme={theme}>
<LegacyUsage />
<DropdownUsage />
<StableComponentUsage />
<h4>Disabled item focusable</h4>
<LegacyUsage MenuListProps={{ disabledItemsFocusable: true }} />
<DropdownUsage MenuListProps={{ disabledItemsFocusable: true }} />
<StableComponentUsage MenuListProps={{ disabledItemsFocusable: true }} />
{/* This is not working at this point */}
<h4>Auto focus false</h4>
<LegacyUsage autoFocus={false} />
<DropdownUsage autoFocus={false} />
<StableComponentUsage autoFocus={false} />
{/* This is not working at this point */}
<h4>Varaiant selectedMenu</h4>
<div>Legacy</div>
<SelectedMenuLegacy />
<div>Dropdown</div>
<SelectedMenuDropdown />
<div>Stable</div>
<SelectedMenuStable />
</ThemeProvider>
);
}
| 4,288 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/md3/buttons.tsx | import * as React from 'react';
import TextField from '@mui/material/TextField';
import Stack from '@mui/material/Stack';
import MD2Button, { ButtonProps as MD2ButtonProps } from '@mui/material/Button';
import { unstable_capitalize as capitalize } from '@mui/utils';
import DeleteIcon from '@mui/icons-material/Delete';
import SendIcon from '@mui/icons-material/Send';
import Button, { ButtonProps } from '@mui/material-next/Button';
import { CssVarsProvider, extendTheme } from '@mui/material-next/styles';
import CssBaseline from '@mui/material/CssBaseline';
import { customPalette, ModeSwitcher } from '.';
const variants: ButtonProps['variant'][] = [
'elevated',
'filled',
'filledTonal',
'outlined',
'text',
];
const colors: ButtonProps['color'][] = ['primary', 'secondary', 'tertiary'];
const sizes: ButtonProps['size'][] = ['small', 'medium', 'large'];
const md2Variants: MD2ButtonProps['variant'][] = ['contained', 'outlined', 'text'];
const md2Colors: MD2ButtonProps['color'][] = [
'primary',
'secondary',
'success',
'error',
'info',
'warning',
];
function DemoComponents() {
const [radius, setRadius] = React.useState<string>('10');
const [gap, setGap] = React.useState<string>('0.5');
return (
<Stack direction="column" gap={1}>
<h4>Enabled</h4>
<Stack direction="row" gap={1}>
{variants.map((variant) => (
<Button key={variant} variant={variant}>
{capitalize(variant as string)}
</Button>
))}
</Stack>
<h4>Enabled without a ripple effect</h4>
<Stack direction="row" gap={1}>
{variants.map((variant) => (
<Button key={variant} variant={variant} disableRipple>
{capitalize(variant as string)}
</Button>
))}
</Stack>
<h4>Disabled</h4>
<Stack direction="row" gap={1}>
{variants.map((variant) => (
<Button key={variant} variant={variant} disabled>
{capitalize(variant as string)}
</Button>
))}
</Stack>
<h4>Colors</h4>
<Stack direction="row" gap={1}>
{colors.map((color) => (
<Button key={color} variant="filled" color={color}>
{capitalize(color as string)}
</Button>
))}
</Stack>
<Stack direction="row" gap={1}>
{colors.map((color) => (
<Button key={color} variant="outlined" color={color}>
{capitalize(color as string)}
</Button>
))}
</Stack>
<Stack direction="row" gap={1}>
{colors.map((color) => (
<Button key={color} variant="text" color={color}>
{capitalize(color as string)}
</Button>
))}
</Stack>
<h4>Extended buttons</h4>
<Stack direction="row" gap={1}>
{colors.map((color) => (
<Button key={color} variant="filled" color={color} endIcon={<SendIcon />}>
Send
</Button>
))}
<Button variant="filled" disabled endIcon={<SendIcon />}>
Send
</Button>
</Stack>
<Stack direction="row" gap={1}>
{colors.map((color) => (
<Button key={color} variant="outlined" color={color} startIcon={<DeleteIcon />}>
Delete
</Button>
))}
<Button variant="outlined" disabled startIcon={<DeleteIcon />}>
Delete
</Button>
</Stack>
<h4>Sizes</h4>
<Stack direction="row" gap={1} alignItems="end">
{sizes.map((size) => (
<Button key={size} variant="filled" size={size} endIcon={<SendIcon />}>
{capitalize(size as string)}
</Button>
))}
</Stack>
<Stack direction="row" gap={1} alignItems="end">
{sizes.map((size) => (
<Button key={size} variant="outlined" size={size} startIcon={<DeleteIcon />}>
{capitalize(size as string)}
</Button>
))}
</Stack>
<h4>sx prop showcase</h4>
<Stack>
<Stack direction="row" gap={1} sx={{ py: 1 }}>
<Button
sx={{
color: 'onError',
bgcolor: 'error',
border: 1,
borderColor: 'tertiary',
borderRadius: 'medium',
}}
>
Button
</Button>
<Button
sx={{
color: 'error.100',
bgcolor: 'error.40',
border: 1,
borderColor: 'tertiary.40',
borderRadius: 2,
}}
>
Button
</Button>
<MD2Button sx={{ borderRadius: 2, color: 'error.main' }}>MD2 Button</MD2Button>
</Stack>
</Stack>
<h4>CSS vars playground</h4>
<Stack>
<Stack direction="row" gap={1} sx={{ py: 1 }}>
<TextField
label="--Button-radius"
value={radius}
type="number"
onChange={(e) => {
setRadius(e.target.value);
}}
/>
<TextField
label="--Button-gap"
value={gap}
type="number"
onChange={(e) => {
setGap(e.target.value);
}}
/>
</Stack>
<Stack direction="row" gap={1} alignItems="end">
{sizes.map((size) => (
<Button
sx={{ '--Button-radius': `${radius}px`, '--Button-gap': `${gap}rem` }}
key={size}
variant="outlined"
size={size}
startIcon={<DeleteIcon />}
>
{capitalize(size as string)}
</Button>
))}
</Stack>
</Stack>
<h4>Material Design 2 Buttons</h4>
<Stack direction="row" gap={1} alignItems="end">
{md2Variants.map((variant) => (
<MD2Button key={variant} variant={variant}>
{capitalize(variant as string)}
</MD2Button>
))}
</Stack>
<Stack direction="row" gap={1} alignItems="end">
{md2Colors.map((color) => (
<MD2Button key={color} variant="contained" color={color}>
{capitalize(color as string)}
</MD2Button>
))}
</Stack>
</Stack>
);
}
// custom MD3 theme
const cssVarsTheme = extendTheme({
colorSchemes: {
light: {
ref: {
palette: customPalette,
},
},
dark: {
ref: {
palette: customPalette,
},
},
},
});
export default function App() {
return (
<CssVarsProvider theme={cssVarsTheme}>
<CssBaseline />
<Stack sx={{ p: 1 }} alignItems="flex-start">
<ModeSwitcher />
<DemoComponents />
</Stack>
</CssVarsProvider>
);
}
| 4,289 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/md3/index.tsx | import * as React from 'react';
import Tooltip from '@mui/material/Tooltip';
import IconButton from '@mui/material/IconButton';
import DarkIcon from '@mui/icons-material/DarkModeOutlined';
import LightIcon from '@mui/icons-material/LightModeOutlined';
import { useColorScheme } from '@mui/material-next/styles';
export const customPalette = {
primary: {
'0': '#000000',
'10': '#3e001f',
'20': '#640036',
'30': '#8d004e',
'40': '#b70b68',
'50': '#d83181',
'60': '#fa4d9b',
'70': '#ff83b3',
'80': '#ffb0ca',
'90': '#ffd9e3',
'95': '#ffecf0',
'99': '#fffbff',
'100': '#ffffff',
},
secondary: {
'0': '#000000',
'10': '#2b151d',
'20': '#422932',
'30': '#5a3f48',
'40': '#74565f',
'50': '#8e6f78',
'60': '#a98892',
'70': '#c5a2ac',
'80': '#e2bdc7',
'90': '#ffd9e3',
'95': '#ffecf0',
'99': '#fffbff',
'100': '#ffffff',
},
tertiary: {
'0': '#000000',
'10': '#2f1500',
'20': '#48290c',
'30': '#623f21',
'40': '#7d5636',
'50': '#996e4c',
'60': '#b58763',
'70': '#d2a17c',
'80': '#f0bc95',
'90': '#ffdcc3',
'95': '#ffede3',
'99': '#fffbff',
'100': '#ffffff',
},
neutral: {
'0': '#000000',
'10': '#201a1c',
'17': '#2e282a',
'20': '#352f30',
'22': '#393335',
'30': '#4c4546',
'40': '#645c5e',
'50': '#7e7577',
'60': '#988e90',
'70': '#b3a9aa',
'80': '#cfc4c5',
'90': '#ebe0e1',
'92': '#f1e5e6',
'95': '#faeef0',
'96': '#f7f2fa',
'99': '#fffbff',
'100': '#ffffff',
},
neutralVariant: {
'0': '#000000',
'10': '#23191c',
'20': '#392d31',
'30': '#514347',
'40': '#695b5e',
'50': '#837377',
'60': '#9e8c91',
'70': '#b9a7ab',
'80': '#d5c2c6',
'90': '#f2dde2',
'95': '#ffecf0',
'99': '#fffbff',
'100': '#ffffff',
},
error: {
'0': '#000000',
'10': '#410002',
'20': '#690005',
'30': '#93000a',
'40': '#ba1a1a',
'50': '#de3730',
'60': '#ff5449',
'70': '#ff897d',
'80': '#ffb4ab',
'90': '#ffdad6',
'95': '#ffedea',
'99': '#fffbff',
'100': '#ffffff',
},
};
export function ModeSwitcher() {
const { mode, setMode } = useColorScheme();
const [mounted, setMounted] = React.useState(false);
React.useEffect(() => {
setMounted(true);
}, []);
if (!mounted) {
return null;
}
return (
<Tooltip title={`Change to ${mode === 'light' ? 'dark' : 'light'} mode`}>
<IconButton
onClick={() => {
if (mode === 'light') {
setMode('dark');
} else {
setMode('light');
}
}}
>
{mode === 'light' ? <DarkIcon /> : <LightIcon />}
</IconButton>
</Tooltip>
);
}
export default function Page() {
return <div>Empty</div>;
}
| 4,290 |
0 | petrpan-code/mui/material-ui/docs/pages/experiments | petrpan-code/mui/material-ui/docs/pages/experiments/md3/inputs.tsx | import * as React from 'react';
import Stack from '@mui/material/Stack';
import {
FilledInput as Md2FilledInput,
FormControl as Md2FormControl,
InputLabel as Md2InputLabel,
InputAdornment as Md2InputAdornment,
FormHelperText as Md2FormHelperText,
} from '@mui/material';
import { ThemeProvider, createTheme } from '@mui/material/styles';
import { FilledInput, FormControl, InputLabel, FormHelperText } from '@mui/material-next';
import { CssVarsProvider, extendTheme } from '@mui/material-next/styles';
import SearchIcon from '@mui/icons-material/Search';
import HighlightOffIcon from '@mui/icons-material/HighlightOff';
import { ModeSwitcher } from '.';
const md2Theme = createTheme();
const md3Theme = extendTheme();
export default function MaterialYouInputs() {
return (
<Stack spacing={4}>
<ThemeProvider theme={md2Theme}>
<Stack direction="column" gap={4} sx={{ p: 4 }}>
<pre>MD2</pre>
<Stack display="inline-flex" direction="row" gap={4}>
<Md2FormControl color="primary" variant="filled">
<Md2InputLabel htmlFor="md2-primary">Primary</Md2InputLabel>
<Md2FilledInput
id="md2-primary"
defaultValue="primary"
aria-describedby="md2-primary-helper-text"
/>
<Md2FormHelperText id="md2-primary-helper-text">
md2 primary helper text
</Md2FormHelperText>
</Md2FormControl>
<Md2FormControl color="secondary" variant="filled">
<Md2InputLabel htmlFor="md2-secondary">Secondary</Md2InputLabel>
<Md2FilledInput
id="md2-secondary"
defaultValue="secondary"
aria-describedby="md2-secondary-helper-text"
/>
<Md2FormHelperText id="md2-secondary-helper-text">
md2 secondary helper text
</Md2FormHelperText>
</Md2FormControl>
</Stack>
<Stack display="inline-flex" direction="row" gap={4}>
<Md2FormControl color="primary" variant="filled">
<Md2InputLabel htmlFor="md2-primary">Primary adornments</Md2InputLabel>
<Md2FilledInput
id="md2-primary"
defaultValue="primary"
startAdornment={
<Md2InputAdornment position="start">
<SearchIcon />
</Md2InputAdornment>
}
/>
</Md2FormControl>
<Md2FormControl color="secondary" variant="filled">
<Md2InputLabel htmlFor="md2-secondary">Secondary adornments</Md2InputLabel>
<Md2FilledInput
id="md2-secondary"
defaultValue="secondary"
startAdornment={<Md2InputAdornment position="start">$</Md2InputAdornment>}
/>
</Md2FormControl>
</Stack>
</Stack>
</ThemeProvider>
<CssVarsProvider theme={md3Theme}>
<Stack
direction="column"
gap={4}
sx={{ backgroundColor: 'background', p: 4, color: 'onBackground' }}
>
<Stack direction="row" gap={1}>
<pre>MD3</pre>
<ModeSwitcher />
</Stack>
<Stack display="inline-flex" direction="row" gap={4}>
<FormControl color="primary" variant="filled">
<InputLabel htmlFor="md3-primary">Primary</InputLabel>
<FilledInput
id="md3-primary"
defaultValue="primary"
aria-describedby="md3-primary-helper-text"
/>
<FormHelperText id="md3-primary-helper-text">Primary helper text</FormHelperText>
</FormControl>
<FormControl color="secondary" variant="filled">
<InputLabel htmlFor="md3-secondary">Secondary</InputLabel>
<FilledInput
id="md3-secondary"
defaultValue="secondary"
aria-describedby="md3-secondary-helper-text"
/>
<FormHelperText id="md3-secondary-helper-text">Secondary helper text</FormHelperText>
</FormControl>
<FormControl color="tertiary" variant="filled">
<InputLabel htmlFor="md3-tertiary">Tertiary</InputLabel>
<FilledInput
id="md3-tertiary"
defaultValue="tertiary"
aria-describedby="md3-tertiary-helper-text"
/>
<FormHelperText id="md3-tertiary-helper-text">Tertiary helper text</FormHelperText>
</FormControl>
</Stack>
<Stack display="inline-flex" direction="row" gap={4}>
<FormControl color="primary" variant="filled" disabled>
<InputLabel htmlFor="md3-primary">Primary disabled</InputLabel>
<FilledInput
id="md3-primary"
defaultValue="primary disabled"
aria-describedby="md3-primary-helper-text"
/>
<FormHelperText id="md3-primary-helper-text">Primary helper text</FormHelperText>
</FormControl>
<FormControl color="secondary" variant="filled" disabled>
<InputLabel htmlFor="md3-secondary">Secondary disabled</InputLabel>
<FilledInput
id="md3-secondary"
defaultValue="secondary disabled"
aria-describedby="md3-secondary-helper-text"
/>
<FormHelperText id="md3-secondary-helper-text">Secondary helper text</FormHelperText>
</FormControl>
<FormControl color="tertiary" variant="filled" disabled>
<InputLabel htmlFor="md3-tertiary">Tertiary disabled</InputLabel>
<FilledInput
id="md3-tertiary"
defaultValue="tertiary disabled"
aria-describedby="md3-tertiary-helper-text"
/>
<FormHelperText id="md3-tertiary-helper-text">Tertiary helper text</FormHelperText>
</FormControl>
</Stack>
<Stack display="inline-flex" direction="row" gap={4}>
<FormControl color="primary" variant="filled" error>
<InputLabel htmlFor="md3-primary">Primary error</InputLabel>
<FilledInput
id="md3-primary"
defaultValue="primary error"
aria-describedby="md3-primary-helper-text"
/>
<FormHelperText id="md3-primary-helper-text">Primary helper text</FormHelperText>
</FormControl>
<FormControl color="secondary" variant="filled" error>
<InputLabel htmlFor="md3-secondary">Secondary error</InputLabel>
<FilledInput
id="md3-secondary"
defaultValue="secondary error"
aria-describedby="md3-secondary-helper-text"
/>
<FormHelperText id="md3-secondary-helper-text">Secondary helper text</FormHelperText>
</FormControl>
<FormControl color="tertiary" variant="filled" error>
<InputLabel htmlFor="md3-tertiary">Tertiary error</InputLabel>
<FilledInput
id="md3-tertiary"
defaultValue="tertiary error"
aria-describedby="md3-tertiary-helper-text"
/>
<FormHelperText id="md3-tertiary-helper-text">Tertiary helper text</FormHelperText>
</FormControl>
</Stack>
<Stack display="inline-flex" direction="row" gap={4} mt={8}>
<FormControl color="primary" variant="filled">
<InputLabel htmlFor="md3-primary-adornment">WIP Primary adornments</InputLabel>
<FilledInput
id="md3-primary-adornment"
defaultValue="WIP primary adornment"
startAdornment={
<Md2InputAdornment position="start">
<SearchIcon />
</Md2InputAdornment>
}
/>
</FormControl>
<FormControl color="secondary" variant="filled">
<InputLabel htmlFor="md3-secondary-adornment">WIP Secondary adornments</InputLabel>
<FilledInput
id="md3-secondary-adornment"
defaultValue="WIP secondary adornment"
startAdornment={
<Md2InputAdornment position="start">
<SearchIcon />
</Md2InputAdornment>
}
endAdornment={
<Md2InputAdornment position="end">
<HighlightOffIcon />
</Md2InputAdornment>
}
/>
</FormControl>
</Stack>
</Stack>
</CssVarsProvider>
</Stack>
);
}
| 4,291 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/joy-ui/react-accordion.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from 'docs/data/joy/components/accordion/accordion.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,292 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/joy-ui/react-alert.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from 'docs/data/joy/components/alert/alert.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,293 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/joy-ui/react-aspect-ratio.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from 'docs/data/joy/components/aspect-ratio/aspect-ratio.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,294 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/joy-ui/react-autocomplete.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from 'docs/data/joy/components/autocomplete/autocomplete.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,295 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/joy-ui/react-avatar.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from 'docs/data/joy/components/avatar/avatar.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,296 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/joy-ui/react-badge.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from 'docs/data/joy/components/badge/badge.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,297 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/joy-ui/react-box.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from 'docs/data/joy/components/box/box.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,298 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/joy-ui/react-breadcrumbs.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocs';
import * as pageProps from 'docs/data/joy/components/breadcrumbs/breadcrumbs.md?@mui/markdown';
export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
| 4,299 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.