From 3d54ff26ff1192d37b0fc892c792b6ff09c1f623 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 25 Jan 2020 20:03:43 +0100 Subject: [PATCH 01/47] [blog] 2019 in review and beyond --- docs/pages/blog/2019.js | 7 ++ docs/pages/blog/2019.md | 102 ++++++++++++++++++ docs/pages/company/jobs.js | 10 ++ docs/pages/company/software-engineer.js | 14 +++ docs/src/modules/components/AppFooter.js | 5 + docs/src/pages.js | 4 - docs/src/pages/company/jobs/jobs.md | 6 ++ .../software-engineer/software-engineer.md | 87 +++++++++++++++ .../pages/discover-more/roadmap/roadmap.md | 2 +- 9 files changed, 232 insertions(+), 5 deletions(-) create mode 100644 docs/pages/blog/2019.js create mode 100644 docs/pages/blog/2019.md create mode 100644 docs/pages/company/jobs.js create mode 100644 docs/pages/company/software-engineer.js create mode 100644 docs/src/pages/company/jobs/jobs.md create mode 100644 docs/src/pages/company/software-engineer/software-engineer.md diff --git a/docs/pages/blog/2019.js b/docs/pages/blog/2019.js new file mode 100644 index 00000000000000..2400f3a6f80c62 --- /dev/null +++ b/docs/pages/blog/2019.js @@ -0,0 +1,7 @@ +import React from 'react'; +import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog'; +import markdown from './2019.md'; + +export default function Page() { + return ; +} diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md new file mode 100644 index 00000000000000..4445e4debd5778 --- /dev/null +++ b/docs/pages/blog/2019.md @@ -0,0 +1,102 @@ +--- +description: The year 2019 was a great one for Material-UI. It puts us on an exciting path to solve even greater challenges in the coming years! +--- + +# 2019 in review and beyond + +The core team. January 25, 2020. + +The year 2019 was a great one for Material-UI. +It puts us on an exciting path to solve even greater challenges in the coming years! + +## Growth + +- 📦 From 2.2M to [3.2M](https://www.npmjs.com/package/@material-ui/core) downloads per month +- 📈 From 1.6M to 3.1M unique visitors per year on the documentation. +- ⭐️ From 43.1k to 53.3k stars, leave us [yours 🌟](https://github.com/mui-org/material-ui) +- 👨‍👩‍👧‍👦 From 1,064 to [1,581](https://github.com/mui-org/material-ui/graphs/contributors) contributors +- 💰 Grew financial support by 76% in 2019, compared to 2018. +- 🏢 From 1.5 to 3 full-time equivalent developers, spread among multiple financially supported [core team members](https://material-ui.com/discover-more/team/). + +The numbers speak for themselves. 2019 was super exciting and made Material-UI one of the most advanced open-source, React-based, UI component library! + +## In review + +When we started 2019, we were celebrating the launch of the **first stable release** of the framework and iterating to polish it (looking at the list of breaking changes, v3 is almost identical to v1). +We thought we were almost done, that we did the hardest part with the release of the stable version. We thought that all we would need to do going forward was to keep up with the Material Design specification and fix a couple of bugs. + +We have quickly realized that we could do way way more. It was just the beginning :D. +Some of the key factors: + +- The results of the [2019 Developer Survey](https://medium.com/material-ui/2019-material-ui-developer-survey-results-c9589434bbcf) have highlighted the immense potential for working on advanced components and features, especially for enterprise users. +Developers are craving for a UI framework that they can learn once (e.g. few breaking changes, only one solution per problem) and use everywhere (e.g. comprehensive, customizable, high-quality). +- Bootstrap has successfully released [a premium store](https://themes.getbootstrap.com/). +The approach opens an opportunity to capture a fraction of the value Material-UI creates for its users and fuel it back into R&D on the framework. +- The market for paid UI components is in the order of a couple of $100m/year. +They are dozens of companies positioned in this market. +While React is only one technology to build UI among others (jQuery, Angular, ASP.NET, Blazor, Vue, WPF, UWP, etc), we believe that Web and React will become the dominant technology in the next 5 years for enterprises. Material-UI is uniquely positioned to address this market with non-MIT features. +- Building UIs should be simpler, it still too slow and complex. +Designers and developers should benefit from a more integrated experience. +- Every now and then, we witness the appearance of a new React UI component library built from scratch ([UXPin](https://adele.uxpin.com/) keeps track of some of them). +And every time we asked ourselves, What could have we done differently to empower this library? +We believe that starting from scratch, while maximizing freedom, is incredibly inefficient. +Most of UI libraries out there need the same features but are implemented with a wide spectrum of accessibility, API and overall design quality. +We won't rest until we successfully unify these efforts. It's a long term mission and will probably take years. This will likely mean releasing an unstyled version of our components. + +## Achievements + +- We have released [v4](/blog/material-ui-v4-is-out/). +- We have introduced many new components (some in the core, some in the lab): + - [Autocomplete](/components/autocomplete/) + - [Backdrop](/components/backdrop/) + - [Breadcrumbs](/components/breadcrumbs/) + - [ButtonGroup](/components/button-group/) + - [Container](/components/container/) + - [Link](/components/links/) + - [Rating](/components/rating/) + - [Skeleton](/components/skeleton/) + - [Slider](/components/slider/) + - [TextareaAutosize](/components/textarea-autosize/) + - [TreeView](/components/tree-view/) +- We have fixed a significant number of [accessibility issues](https://github.com/mui-org/material-ui/issues?q=is%3Aissue+label%3Aaccessibility+is%3Aclosed). +- We have introduced global class names. +- We have migrated the whole codebase to hooks. +- We have migrated all the demos to TypeScript (source of truth). +- We have introduced [native tree-shaking](/guides/minimizing-bundle-size/) support. +- We have introduced [built-in localization](/guides/localization/). +- We have remove a good chunk of external dependencies and increased the `features/bundle size` density. +- We have introduced an [icon search page](/components/material-icons/). +- We have released a [store for Material-UI](https://themes.material-ui.com/). + +## Looking at 2020 + +2019 was great, 2020 is going to be even more exciting! +We will continue in the same direction. + +### Survey + +The developer survey we ran [last year](/blog/2019-developer-survey-results/) was so insightful that we plan to run it every year. +It's a great opportunity for us to adjust the strategy and to pause to analyse the outcome of the actions we took the previous year. + +### Open source roadmap + +Most of the time, we work in the open, you can find our [public roadmap](/discover-more/roadmap). +We plan to release a new major around the end of the year (v5). +We will promote components that are in the lab to the core, migrate to styled-components, and more. + +### Store + +We will increase the depth of content available with more themes and templates. +We are looking into the support of Sketch, Figma, and Adobe XD. + +### Enterprise + +We will start an enterprise offering, for advanced use cases, with the data grid. +The enterprise features will be built on the open source version of the components. + +### Hiring + +We are looking for a [full-time software developer](/company/software-engineer/) to join us! + +If you want to help us onboard more full-time developers in the team, we document [a couple of ways](/getting-started/faq/#material-ui-is-awesome-how-can-i-support-the-project). +For instance, spreading the word to other developers that are looking for a great UI framework is extremely useful 🙌. diff --git a/docs/pages/company/jobs.js b/docs/pages/company/jobs.js new file mode 100644 index 00000000000000..5c0ba8c946a517 --- /dev/null +++ b/docs/pages/company/jobs.js @@ -0,0 +1,10 @@ +import React from 'react'; +import TopLayoutCompany from 'docs/src/modules/components/TopLayoutCompany'; + +const req = require.context('docs/src/pages/company/jobs', false, /\.(md|js|tsx)$/); +const reqSource = require.context('!raw-loader!../../src/pages/company/jobs', false, /\.(js|tsx)$/); +const reqPrefix = 'pages/company/jobs'; + +export default function Page() { + return ; +} diff --git a/docs/pages/company/software-engineer.js b/docs/pages/company/software-engineer.js new file mode 100644 index 00000000000000..8a2d172c56f5b2 --- /dev/null +++ b/docs/pages/company/software-engineer.js @@ -0,0 +1,14 @@ +import React from 'react'; +import TopLayoutCompany from 'docs/src/modules/components/TopLayoutCompany'; + +const req = require.context('docs/src/pages/company/software-engineer', false, /\.(md|js|tsx)$/); +const reqSource = require.context( + '!raw-loader!../../src/pages/company/software-engineer', + false, + /\.(js|tsx)$/, +); +const reqPrefix = 'pages/company/software-engineer'; + +export default function Page() { + return ; +} diff --git a/docs/src/modules/components/AppFooter.js b/docs/src/modules/components/AppFooter.js index ec72bd635aca49..44a9afedfc6123 100644 --- a/docs/src/modules/components/AppFooter.js +++ b/docs/src/modules/components/AppFooter.js @@ -137,6 +137,11 @@ function AppFooter(props) { Contact Us +
  • + + Jobs + +
    • diff --git a/docs/src/pages.js b/docs/src/pages.js index 5ebdfe60be1482..249fd4644a01d4 100644 --- a/docs/src/pages.js +++ b/docs/src/pages.js @@ -214,11 +214,7 @@ const pages = [ { pathname: '/discover-more/languages' }, ], }, - { pathname: '/versions', displayNav: false }, - { pathname: '/', displayNav: false, disableDrawer: true }, { pathname: 'https://medium.com/material-ui', title: 'Blog' }, - { pathname: '/company/about', displayNav: false, disableDrawer: true }, - { pathname: '/company/contact', displayNav: false, disableDrawer: true }, ]; export default pages; diff --git a/docs/src/pages/company/jobs/jobs.md b/docs/src/pages/company/jobs/jobs.md new file mode 100644 index 00000000000000..c89b52c96056b5 --- /dev/null +++ b/docs/src/pages/company/jobs/jobs.md @@ -0,0 +1,6 @@ +# Work with us! + +

    Join our team!

    + +- [Software Engineer](/company/software-engineer/) • Remote or Paris
    + We are looking for a software engineer to help support our open source team, assist the Material-UI community and grow our premium products. Join us in our mission to make React application development fun by making it simple. diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md new file mode 100644 index 00000000000000..2c6cb6106c9df9 --- /dev/null +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -0,0 +1,87 @@ +# Software Engineer + +

    We are looking for a software engineer to help support our open source team, assist the Material-UI community and grow our premium products. Join us in our mission to make React application development fun by making it simple.

    + +## About Us + +Material-UI is a community and developer focused team that makes it easy to build amazing user interfaces, for any device, with React. + +Our core values include transparency (our work is public most of the time); creating a safe, high-trust team; building incredible developer experiences; maintaining a healthy working environment; and helping to deliver web experiences that feel amazing to use on every device and connection type. + +Material-UI started back in 2015 to unify React and Material Design. Today, Material-UI has grown to become one of the world's most popular React UI libraries – backed by a vibrant community of more than 1M developers in over 180 countries. + +## Details of the Role + +- Type of work: Contractor (long mission, full-time, convertible to an employee position) +- Start date: Immediately +- Location: Remote (preference for UTC-5 to UTC+4) or Paris + +## Why we’re hiring + +Both our open source products / community and our premium products are [growing fast](https://www.rank2traffic.com/material-ui.com) and we need talented engineers to keep that going! + +We need help improving the health of Material-UI open source: make the library easier to use, make it support more use cases, improve performance, make it more accessible, make it easier to customize. We also need help keeping up with the community, guiding developers to answers, and just generally being a positive presence in the open source community. + +We also need to develop our premium content. We have a premium themes and templates marketplace, and soon premium components bundled under a Material-UI Pro offering. + +## Why this is interesting + +Our solution is empowering React developers to build awesome applications. It should be easy, it shouldn’t require any advanced technical skills. Hundreds of thousands of developers use Material-UI every month. Let’s reach the full potential. + +Our premium products portfolio is still small, with a million interesting and challenging problems to solve. + +## What you’ll do on a day-to-day basis + +Depending on the day, you’ll: + +On the open source side: + +- **Help guide architectural decisions**. From modernizing the way we handle styles to build new components, the future of Material-UI is discussed and planned in our public RFCs and issues. You’ll be helping drive these conversations and guiding Material-UI toward the best possible solutions. +- **Contribute to deep, meaningful refactors and feature releases**. Material-UI is a complex codebase. Meaningful features we’ve shipped recently, like a Tree View component, Slider component, they have often required a couple weeks to a month of dedicated, careful work. +- **Reduce friction**. A large amount of the work of Material-UI is reducing friction and making it easier to use. This might involve careful API design, identifying and fixing top bugs, creating easier-to-use 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 as a core team maintainer 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 on the team 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. + +On the premium side: + +- **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. + +## Experience you should have + +- **Expertise in the modern JavaScript ecosystem**. Material-UI is built on the shoulders of giants, making use of technologies like ES2015+, TypeScript, Node.js, React, Next.js, webpack, and Babel. +- **A track record demonstrating an eye for design and solving real world user problems**. If you have a knack for shipping beautiful, intuitive software, 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 our open source team, you’d interface both directly and indirectly with community members, 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, and reaching out to assist others, you’ll be an incredible addition to our team. Our team thrives 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 frontend 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! + +## Experience 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 repo, or maybe you’ve worked on internal repos that saw contributions from multiple teams. Previous experience with highly active repo workflows is a definite plus for this role. +- **You have used Material-UI before**. You have built a non trivial application with Material-UI in the past. You know the limitations of the library, you know a few areas that could be improved. +- **You have contributed code to Material-UI before**. A history of contributing to Material-UI would be a definite plus. + +## The best parts of this job + +- **You’ll be at the cutting edge of application development** — working on one of the fastest-growing UI frameworks on the market. +- **You’ll be part of an active, open, friendly community** of developers that are really excited about building awesome applications. +- **Your role will be key to making Material-UI the go to UI framework solution** for building applications and design systems with React. + +## The worst parts of this job + +- **Shifting context.** You may 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 code base 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 give up on solving each problem at 100%. Solving 50-70% with quality should be enough for any given iteration. Our users manifest themselves, they quickly tell us when we don’t push a solution far enough. +- **Material-UI 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 would 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 of when to ignore something and when to dig in further. + +## Benefits for you + +- A competitive compensation. + +## Apply + +[Apply for this position 📮](https://airtable.com/shrHB2jnnhdtsGkEN) diff --git a/docs/src/pages/discover-more/roadmap/roadmap.md b/docs/src/pages/discover-more/roadmap/roadmap.md index 766b7aee6e5d40..4c353ed1939391 100644 --- a/docs/src/pages/discover-more/roadmap/roadmap.md +++ b/docs/src/pages/discover-more/roadmap/roadmap.md @@ -19,7 +19,7 @@ Here are the top priorities: - Encourage the usage of third-party components if they already exist and are well maintained. - Offer an option to the highly used and well maintained components to move to the official organization: mui-org/x on GitHub, @material-ui/x on npm and x.material-ui.com for the documentation. - 0.5 - **Better customization.** 💅 We want to make our component customization intuitive, no matter if you are using global CSS or styled-components: - - Better support for styled-components: [#6115](https://github.com/mui-org/material-ui/issues/6115). + - Use styled-components by default: [#6115](https://github.com/mui-org/material-ui/issues/6115). - Allow the use of the Box props in all the core components: [#15561](https://github.com/mui-org/material-ui/issues/15561). - Allow the usage of dynamic theme variants and colors: [#15573](https://github.com/mui-org/material-ui/issues/15573) & [#13875](https://github.com/mui-org/material-ui/issues/13875). - Allow the use of the components without any styles: [#6218](https://github.com/mui-org/material-ui/issues/6218). From edfb229cc4ae7053481a9c0b303aeab1d00dac22 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Thu, 30 Jan 2020 17:20:45 +0100 Subject: [PATCH 02/47] fix build --- docs/src/modules/components/AppDrawer.js | 2 +- docs/src/modules/components/AppDrawerNavItem.js | 4 +--- docs/src/modules/components/MarkdownDocs.js | 2 +- docs/src/modules/components/TopLayoutBlog.js | 3 ++- docs/src/modules/components/TopLayoutCompany.js | 4 ++++ docs/src/modules/components/useMarkdownDocs.js | 2 +- docs/src/pages.js | 2 ++ 7 files changed, 12 insertions(+), 7 deletions(-) diff --git a/docs/src/modules/components/AppDrawer.js b/docs/src/modules/components/AppDrawer.js index ff73c60354b0f4..5135d19664f03e 100644 --- a/docs/src/modules/components/AppDrawer.js +++ b/docs/src/modules/components/AppDrawer.js @@ -99,7 +99,7 @@ function reduceChildRoutes({ props, activePage, items, page, depth, t }) { if (page.children && page.children.length > 1) { const title = pageToTitleI18n(page, t); - const topLevel = !activePage || activePage.pathname.indexOf(`${page.pathname}/`) === 0; + const topLevel = activePage ? activePage.pathname.indexOf(`${page.pathname}/`) === 0 : false; items.push( ({ }, })); -function AppDrawerNavItem(props) { +export default function AppDrawerNavItem(props) { const { children, depth, @@ -112,5 +112,3 @@ AppDrawerNavItem.propTypes = { title: PropTypes.string.isRequired, topLevel: PropTypes.bool, }; - -export default AppDrawerNavItem; diff --git a/docs/src/modules/components/MarkdownDocs.js b/docs/src/modules/components/MarkdownDocs.js index dda8810b812c58..3ca29a85c7fede 100644 --- a/docs/src/modules/components/MarkdownDocs.js +++ b/docs/src/modules/components/MarkdownDocs.js @@ -43,7 +43,7 @@ const styles = theme => ({ }, }, toc: { - [theme.breakpoints.up('md')]: { + [theme.breakpoints.up('sm')]: { width: 'calc(100% - 175px)', }, [theme.breakpoints.up('lg')]: { diff --git a/docs/src/modules/components/TopLayoutBlog.js b/docs/src/modules/components/TopLayoutBlog.js index 9d94126e1fac21..f673c7dd5cf043 100644 --- a/docs/src/modules/components/TopLayoutBlog.js +++ b/docs/src/modules/components/TopLayoutBlog.js @@ -19,8 +19,9 @@ const styles = theme => ({ }, container: { marginBottom: theme.spacing(20), - maxWidth: 680 + 64, + maxWidth: 680 + theme.spacing(8 + 4), '& .markdownElement': { + paddingRight: theme.spacing(4), fontSize: 18, lineHeight: 1.7, }, diff --git a/docs/src/modules/components/TopLayoutCompany.js b/docs/src/modules/components/TopLayoutCompany.js index 0e01b0ddfadc48..b72bafa1351808 100644 --- a/docs/src/modules/components/TopLayoutCompany.js +++ b/docs/src/modules/components/TopLayoutCompany.js @@ -14,6 +14,10 @@ const styles = theme => ({ }, container: { marginBottom: theme.spacing(20), + maxWidth: 680 + theme.spacing(8 + 4), + '& .markdownElement': { + paddingRight: theme.spacing(4), + }, }, }); diff --git a/docs/src/modules/components/useMarkdownDocs.js b/docs/src/modules/components/useMarkdownDocs.js index 5f50b206ff2417..1b50ca568060c1 100644 --- a/docs/src/modules/components/useMarkdownDocs.js +++ b/docs/src/modules/components/useMarkdownDocs.js @@ -140,7 +140,7 @@ ${headers.components return ( Date: Fri, 31 Jan 2020 13:38:44 +0100 Subject: [PATCH 03/47] fix typo --- docs/src/modules/components/Ad.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/modules/components/Ad.js b/docs/src/modules/components/Ad.js index 9ba041029edd89..b7a0887255d6b4 100644 --- a/docs/src/modules/components/Ad.js +++ b/docs/src/modules/components/Ad.js @@ -61,7 +61,7 @@ const inHouseAds = [ 'https://themes.material-ui.com/?utm_source=material_ui&utm_medium=referral&utm_campaign=in-house-2', img: '/static/in-house/themes-2.jpg', description: - 'Premium Templates
    Sart your project with the best themes for admins, dashboards and more.', + 'Premium Templates
    Start your project with the best themes for admins, dashboards and more.', }, { name: 'themes', From 96b10e9fb90e73eb6f71d4b652e70f742003f849 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 21:19:57 +0100 Subject: [PATCH 04/47] flexibility --- docs/src/pages/company/software-engineer/software-engineer.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 2c6cb6106c9df9..76d2ba2405c768 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -81,6 +81,7 @@ The work you would be doing is somewhat unique and idiosyncratic. You probably h ## Benefits for you - A competitive compensation. +- Flexible workplace, hours, holidays. ## Apply From ace378317f21b0dffc2880a4b980523c37ef55a0 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:43:37 +0100 Subject: [PATCH 05/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 4445e4debd5778..a35735e940450e 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -1,5 +1,5 @@ --- -description: The year 2019 was a great one for Material-UI. It puts us on an exciting path to solve even greater challenges in the coming years! +description: 2019 was a great year for Material-UI. It puts us on an exciting path to solve even greater challenges in the coming years! --- # 2019 in review and beyond From a81e1bde8860f8ef1876d9bc353a606d94303cd4 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:43:48 +0100 Subject: [PATCH 06/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index a35735e940450e..da06d52ba0d914 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -6,7 +6,7 @@ description: 2019 was a great year for Material-UI. It puts us on an exciting pa The core team. January 25, 2020. -The year 2019 was a great one for Material-UI. +2019 was a great year for Material-UI. It puts us on an exciting path to solve even greater challenges in the coming years! ## Growth From f2e261239363fc9b16439ffc9e6d5d456fdfb858 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:44:01 +0100 Subject: [PATCH 07/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index da06d52ba0d914..dfe9bc4b736298 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -11,7 +11,7 @@ It puts us on an exciting path to solve even greater challenges in the coming ye ## Growth -- 📦 From 2.2M to [3.2M](https://www.npmjs.com/package/@material-ui/core) downloads per month +- 📦 From 2.2M to [3.2M](https://www.npmjs.com/package/@material-ui/core) downloads per month. - 📈 From 1.6M to 3.1M unique visitors per year on the documentation. - ⭐️ From 43.1k to 53.3k stars, leave us [yours 🌟](https://github.com/mui-org/material-ui) - 👨‍👩‍👧‍👦 From 1,064 to [1,581](https://github.com/mui-org/material-ui/graphs/contributors) contributors From 551bb19921c092124c088030d78b26b349eff238 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:44:18 +0100 Subject: [PATCH 08/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 76d2ba2405c768..7684b2b9fb0306 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -60,7 +60,7 @@ On the premium side: ## Experience 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 repo, or maybe you’ve worked on internal repos that saw contributions from multiple teams. Previous experience with highly active repo workflows is a definite plus for this role. +- **You’ve maintained an active repository before**. Maybe you’ve helped maintain a popular open source repo, or perhaps you’ve worked on internal repos that saw contributions from multiple teams. Previous experience with highly active repo workflows is a definite plus for this role. - **You have used Material-UI before**. You have built a non trivial application with Material-UI in the past. You know the limitations of the library, you know a few areas that could be improved. - **You have contributed code to Material-UI before**. A history of contributing to Material-UI would be a definite plus. From 0af20e2ef69ac377d2517c4a5895b7f86c6e921a Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:46:46 +0100 Subject: [PATCH 09/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index dfe9bc4b736298..761895cb4209f2 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -14,7 +14,7 @@ It puts us on an exciting path to solve even greater challenges in the coming ye - 📦 From 2.2M to [3.2M](https://www.npmjs.com/package/@material-ui/core) downloads per month. - 📈 From 1.6M to 3.1M unique visitors per year on the documentation. - ⭐️ From 43.1k to 53.3k stars, leave us [yours 🌟](https://github.com/mui-org/material-ui) -- 👨‍👩‍👧‍👦 From 1,064 to [1,581](https://github.com/mui-org/material-ui/graphs/contributors) contributors +- 👨‍👩‍👧‍👦 From 1,064 to [1,581](https://github.com/mui-org/material-ui/graphs/contributors) contributors. - 💰 Grew financial support by 76% in 2019, compared to 2018. - 🏢 From 1.5 to 3 full-time equivalent developers, spread among multiple financially supported [core team members](https://material-ui.com/discover-more/team/). From def2b61e51ec424e256eafe5521d24460e51c3ae Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:47:02 +0100 Subject: [PATCH 10/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 761895cb4209f2..d09c92f1dcecfe 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -13,7 +13,7 @@ It puts us on an exciting path to solve even greater challenges in the coming ye - 📦 From 2.2M to [3.2M](https://www.npmjs.com/package/@material-ui/core) downloads per month. - 📈 From 1.6M to 3.1M unique visitors per year on the documentation. -- ⭐️ From 43.1k to 53.3k stars, leave us [yours 🌟](https://github.com/mui-org/material-ui) +- ⭐️ From 43.1k to 53.3k stars, leave us [yours 🌟](https://github.com/mui-org/material-ui). - 👨‍👩‍👧‍👦 From 1,064 to [1,581](https://github.com/mui-org/material-ui/graphs/contributors) contributors. - 💰 Grew financial support by 76% in 2019, compared to 2018. - 🏢 From 1.5 to 3 full-time equivalent developers, spread among multiple financially supported [core team members](https://material-ui.com/discover-more/team/). From 04028408e8983971aa8bc1cb0d121a2439236628 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:47:17 +0100 Subject: [PATCH 11/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index d09c92f1dcecfe..855127eda17243 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -18,7 +18,7 @@ It puts us on an exciting path to solve even greater challenges in the coming ye - 💰 Grew financial support by 76% in 2019, compared to 2018. - 🏢 From 1.5 to 3 full-time equivalent developers, spread among multiple financially supported [core team members](https://material-ui.com/discover-more/team/). -The numbers speak for themselves. 2019 was super exciting and made Material-UI one of the most advanced open-source, React-based, UI component library! +The numbers speak for themselves. 2019 was super exciting and made Material-UI one of the most advanced open-source, React-based, UI component libraries! ## In review From 825bab5f0469f20ab099da1692ff64e1237f8f62 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:47:33 +0100 Subject: [PATCH 12/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 7684b2b9fb0306..07932385cf1bec 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -68,7 +68,7 @@ On the premium side: - **You’ll be at the cutting edge of application development** — working on one of the fastest-growing UI frameworks on the market. - **You’ll be part of an active, open, friendly community** of developers that are really excited about building awesome applications. -- **Your role will be key to making Material-UI the go to UI framework solution** for building applications and design systems with React. +- **Your role will be key to making Material-UI the go to UI framework** for building applications and design systems with React. ## The worst parts of this job From 77aa4446b0c86be49d3623de894fa9cc5e1f10eb Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:47:56 +0100 Subject: [PATCH 13/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 855127eda17243..2b529c79d0b51a 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -30,7 +30,7 @@ Some of the key factors: - The results of the [2019 Developer Survey](https://medium.com/material-ui/2019-material-ui-developer-survey-results-c9589434bbcf) have highlighted the immense potential for working on advanced components and features, especially for enterprise users. Developers are craving for a UI framework that they can learn once (e.g. few breaking changes, only one solution per problem) and use everywhere (e.g. comprehensive, customizable, high-quality). -- Bootstrap has successfully released [a premium store](https://themes.getbootstrap.com/). +- Bootstrap had successfully released [a theme store](https://themes.getbootstrap.com/). The approach opens an opportunity to capture a fraction of the value Material-UI creates for its users and fuel it back into R&D on the framework. - The market for paid UI components is in the order of a couple of $100m/year. They are dozens of companies positioned in this market. From cf897c42f9557b1220177e4f4ce35b990984bfd4 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:48:21 +0100 Subject: [PATCH 14/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 2b529c79d0b51a..f35d043260decb 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -31,7 +31,7 @@ Some of the key factors: - The results of the [2019 Developer Survey](https://medium.com/material-ui/2019-material-ui-developer-survey-results-c9589434bbcf) have highlighted the immense potential for working on advanced components and features, especially for enterprise users. Developers are craving for a UI framework that they can learn once (e.g. few breaking changes, only one solution per problem) and use everywhere (e.g. comprehensive, customizable, high-quality). - Bootstrap had successfully released [a theme store](https://themes.getbootstrap.com/). -The approach opens an opportunity to capture a fraction of the value Material-UI creates for its users and fuel it back into R&D on the framework. +Following this approach opened an opportunity to capture a fraction of the value Material-UI creates for its users, and funnel it back into R&D on the framework. - The market for paid UI components is in the order of a couple of $100m/year. They are dozens of companies positioned in this market. While React is only one technology to build UI among others (jQuery, Angular, ASP.NET, Blazor, Vue, WPF, UWP, etc), we believe that Web and React will become the dominant technology in the next 5 years for enterprises. Material-UI is uniquely positioned to address this market with non-MIT features. From e4246543bcec4172fcbf792ba09811abce27cf4e Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:48:46 +0100 Subject: [PATCH 15/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index f35d043260decb..59e1e7c2a42af4 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -33,7 +33,7 @@ Developers are craving for a UI framework that they can learn once (e.g. few bre - Bootstrap had successfully released [a theme store](https://themes.getbootstrap.com/). Following this approach opened an opportunity to capture a fraction of the value Material-UI creates for its users, and funnel it back into R&D on the framework. - The market for paid UI components is in the order of a couple of $100m/year. -They are dozens of companies positioned in this market. +with dozens of companies positioned in this market. While React is only one technology to build UI among others (jQuery, Angular, ASP.NET, Blazor, Vue, WPF, UWP, etc), we believe that Web and React will become the dominant technology in the next 5 years for enterprises. Material-UI is uniquely positioned to address this market with non-MIT features. - Building UIs should be simpler, it still too slow and complex. Designers and developers should benefit from a more integrated experience. From f9df403299d02b088ab17627845eff8625d779db Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:49:20 +0100 Subject: [PATCH 16/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 07932385cf1bec..0daf2a8016f2a2 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -73,7 +73,7 @@ On the premium side: ## The worst parts of this job - **Shifting context.** You may 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 code base 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 give up on solving each problem at 100%. Solving 50-70% with quality should be enough for any given iteration. Our users manifest themselves, they quickly tell us when we don’t push a solution far enough. +- **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. - **Material-UI 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 would 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 of when to ignore something and when to dig in further. From 4ca6fd70aca6c07295dab195057840ca9f819fda Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:49:48 +0100 Subject: [PATCH 17/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 59e1e7c2a42af4..688e4d9f547c93 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -23,7 +23,7 @@ The numbers speak for themselves. 2019 was super exciting and made Material-UI o ## In review When we started 2019, we were celebrating the launch of the **first stable release** of the framework and iterating to polish it (looking at the list of breaking changes, v3 is almost identical to v1). -We thought we were almost done, that we did the hardest part with the release of the stable version. We thought that all we would need to do going forward was to keep up with the Material Design specification and fix a couple of bugs. +We thought we were almost done, and that we had done the hardest part with the release of the stable version. All we would need to do going forward was to keep up with the Material Design specification and fix a couple of bugs. We have quickly realized that we could do way way more. It was just the beginning :D. Some of the key factors: From 9172fd98f7192ffb4bcb6f81636b4f186e83ae05 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:50:22 +0100 Subject: [PATCH 18/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 688e4d9f547c93..3fc14bd20255c7 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -34,7 +34,7 @@ Developers are craving for a UI framework that they can learn once (e.g. few bre Following this approach opened an opportunity to capture a fraction of the value Material-UI creates for its users, and funnel it back into R&D on the framework. - The market for paid UI components is in the order of a couple of $100m/year. with dozens of companies positioned in this market. -While React is only one technology to build UI among others (jQuery, Angular, ASP.NET, Blazor, Vue, WPF, UWP, etc), we believe that Web and React will become the dominant technology in the next 5 years for enterprises. Material-UI is uniquely positioned to address this market with non-MIT features. +While React is only one technology among many (jQuery, Angular, ASP.NET, Blazor, Vue, WPF, UWP, etc) with which to build a UI, but we believe that Web and React will become the dominant technology in the next 5 years for enterprises. Material-UI is uniquely positioned to address this market with non-MIT features. - Building UIs should be simpler, it still too slow and complex. Designers and developers should benefit from a more integrated experience. - Every now and then, we witness the appearance of a new React UI component library built from scratch ([UXPin](https://adele.uxpin.com/) keeps track of some of them). From 7b3749eee2d3c5758fa7def5fd3e235ea0c839ae Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:50:39 +0100 Subject: [PATCH 19/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 3fc14bd20255c7..85bf35265233b7 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -32,7 +32,7 @@ Some of the key factors: Developers are craving for a UI framework that they can learn once (e.g. few breaking changes, only one solution per problem) and use everywhere (e.g. comprehensive, customizable, high-quality). - Bootstrap had successfully released [a theme store](https://themes.getbootstrap.com/). Following this approach opened an opportunity to capture a fraction of the value Material-UI creates for its users, and funnel it back into R&D on the framework. -- The market for paid UI components is in the order of a couple of $100m/year. +- The market for paid UI components is in the order of a couple of $100m/year, with dozens of companies positioned in this market. While React is only one technology among many (jQuery, Angular, ASP.NET, Blazor, Vue, WPF, UWP, etc) with which to build a UI, but we believe that Web and React will become the dominant technology in the next 5 years for enterprises. Material-UI is uniquely positioned to address this market with non-MIT features. - Building UIs should be simpler, it still too slow and complex. From aeb5d0246df531c02b31efd181d6050fdcf617f4 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:51:01 +0100 Subject: [PATCH 20/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 85bf35265233b7..5bfcf009309dc7 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -38,7 +38,7 @@ While React is only one technology among many (jQuery, Angular, ASP.NET, Blazor, - Building UIs should be simpler, it still too slow and complex. Designers and developers should benefit from a more integrated experience. - Every now and then, we witness the appearance of a new React UI component library built from scratch ([UXPin](https://adele.uxpin.com/) keeps track of some of them). -And every time we asked ourselves, What could have we done differently to empower this library? +And every time we asked ourselves, "what could have we done differently to empower this library"? We believe that starting from scratch, while maximizing freedom, is incredibly inefficient. Most of UI libraries out there need the same features but are implemented with a wide spectrum of accessibility, API and overall design quality. We won't rest until we successfully unify these efforts. It's a long term mission and will probably take years. This will likely mean releasing an unstyled version of our components. From caf16551217d6cb6ab4abe3efffa59b0fb845ba8 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:53:15 +0100 Subject: [PATCH 21/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 0daf2a8016f2a2..46a3c152133433 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -74,7 +74,7 @@ On the premium side: - **Shifting context.** You may 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 code base 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. -- **Material-UI is a large codebase**. You may bang your head against the wall at times, and then write tests to assist future you. +- **Material-UI 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 would 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 of when to ignore something and when to dig in further. From e93e9957a4fa5181deae9e5994e0221a9128a160 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:53:43 +0100 Subject: [PATCH 22/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 5bfcf009309dc7..18ed110c9f4db5 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -40,7 +40,7 @@ Designers and developers should benefit from a more integrated experience. - Every now and then, we witness the appearance of a new React UI component library built from scratch ([UXPin](https://adele.uxpin.com/) keeps track of some of them). And every time we asked ourselves, "what could have we done differently to empower this library"? We believe that starting from scratch, while maximizing freedom, is incredibly inefficient. -Most of UI libraries out there need the same features but are implemented with a wide spectrum of accessibility, API and overall design quality. +Most UI libraries need the same features but are implemented with a wide spectrum of accessibility, developer experience, and overall design quality. We won't rest until we successfully unify these efforts. It's a long term mission and will probably take years. This will likely mean releasing an unstyled version of our components. ## Achievements From f11cb7ed4e1e2270afd19228264e1d05892cfc7a Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:54:20 +0100 Subject: [PATCH 23/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 18ed110c9f4db5..fb633e289bfa14 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -41,7 +41,7 @@ Designers and developers should benefit from a more integrated experience. And every time we asked ourselves, "what could have we done differently to empower this library"? We believe that starting from scratch, while maximizing freedom, is incredibly inefficient. Most UI libraries need the same features but are implemented with a wide spectrum of accessibility, developer experience, and overall design quality. -We won't rest until we successfully unify these efforts. It's a long term mission and will probably take years. This will likely mean releasing an unstyled version of our components. +We won't rest until we successfully unify these efforts. It's a long term mission and will probably take years. The foundation will be the release of an un-styled version of our components. ## Achievements From 7b39dfbd93ee157faaa834ceeb0d66be666a5196 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:55:09 +0100 Subject: [PATCH 24/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 46a3c152133433..8e0e0674823dcb 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -72,7 +72,7 @@ On the premium side: ## The worst parts of this job -- **Shifting context.** You may 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 code base you’re unfamiliar with or don’t have a ton of understanding about. It’s fun, rewarding work, but it can be very challenging. +- **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 code base 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. - **Material-UI 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 would be doing is somewhat unique and idiosyncratic. You probably have not had a similar role before. From 1fcd8b9c3a55f36a452595219156c213d3a1de43 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:55:36 +0100 Subject: [PATCH 25/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index fb633e289bfa14..2d350a1882e887 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -61,7 +61,7 @@ We won't rest until we successfully unify these efforts. It's a long term missio - We have fixed a significant number of [accessibility issues](https://github.com/mui-org/material-ui/issues?q=is%3Aissue+label%3Aaccessibility+is%3Aclosed). - We have introduced global class names. - We have migrated the whole codebase to hooks. -- We have migrated all the demos to TypeScript (source of truth). +- We have migrated all the demos to TypeScript (while also offering transpiled JS demos). - We have introduced [native tree-shaking](/guides/minimizing-bundle-size/) support. - We have introduced [built-in localization](/guides/localization/). - We have remove a good chunk of external dependencies and increased the `features/bundle size` density. From 897ca65fab1e88438c50728ae669f1e415de79b1 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Fri, 31 Jan 2020 23:59:16 +0100 Subject: [PATCH 26/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 2d350a1882e887..8f4e766390880b 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -64,7 +64,7 @@ We won't rest until we successfully unify these efforts. It's a long term missio - We have migrated all the demos to TypeScript (while also offering transpiled JS demos). - We have introduced [native tree-shaking](/guides/minimizing-bundle-size/) support. - We have introduced [built-in localization](/guides/localization/). -- We have remove a good chunk of external dependencies and increased the `features/bundle size` density. +- We have remove a good number of external dependencies and increased the `features/bundle size` density. - We have introduced an [icon search page](/components/material-icons/). - We have released a [store for Material-UI](https://themes.material-ui.com/). From b24e2ed55e8e7d7c7a63fd2f687909cd6544f8d1 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:00:35 +0100 Subject: [PATCH 27/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 8f4e766390880b..b0030677eba41a 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -76,7 +76,7 @@ We will continue in the same direction. ### Survey The developer survey we ran [last year](/blog/2019-developer-survey-results/) was so insightful that we plan to run it every year. -It's a great opportunity for us to adjust the strategy and to pause to analyse the outcome of the actions we took the previous year. +It's a great opportunity for us to adjust the strategy and to pause to analyse the outcome of the actions we took in the previous year. ### Open source roadmap From debe2fe6eb93760b0ac460ae96cc1240c9bff7f8 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:01:15 +0100 Subject: [PATCH 28/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index b0030677eba41a..0f01bc01f09ec4 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -80,7 +80,7 @@ It's a great opportunity for us to adjust the strategy and to pause to analyse t ### Open source roadmap -Most of the time, we work in the open, you can find our [public roadmap](/discover-more/roadmap). +Most of the time we work in the open. Here's our our [public roadmap](/discover-more/roadmap). We plan to release a new major around the end of the year (v5). We will promote components that are in the lab to the core, migrate to styled-components, and more. From d21aeb53c6713136d342497f16c3f3d99ec9d2ab Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:04:30 +0100 Subject: [PATCH 29/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 0f01bc01f09ec4..8bcbd703c8ace7 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -87,7 +87,7 @@ We will promote components that are in the lab to the core, migrate to styled-co ### Store We will increase the depth of content available with more themes and templates. -We are looking into the support of Sketch, Figma, and Adobe XD. +We have recently released a Sketch design library, and are planning to support Figma, and Adobe XD too. For Framer, we have made the key components available as a [Framer package](https://packages.framer.com/package/material-ui/material-ui). ### Enterprise From e52eb340b295b430522e25f5cdc7395afbd72332 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:04:51 +0100 Subject: [PATCH 30/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 8bcbd703c8ace7..b5196e74bc8130 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -91,7 +91,7 @@ We have recently released a Sketch design library, and are planning to support F ### Enterprise -We will start an enterprise offering, for advanced use cases, with the data grid. +We plan to release an enterprise class offering, starting with the data grid. The enterprise features will be built on the open source version of the components. ### Hiring From 981ac72549d70ad7a2580a7e5276bf4326922e18 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:05:17 +0100 Subject: [PATCH 31/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index b5196e74bc8130..e900d196f9dd52 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -92,7 +92,7 @@ We have recently released a Sketch design library, and are planning to support F ### Enterprise We plan to release an enterprise class offering, starting with the data grid. -The enterprise features will be built on the open source version of the components. +Enterprise features will build on the open source version of the components. ### Hiring From 931cc7208b225b2bd89d2bf0e5cd3bead88819c8 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:05:43 +0100 Subject: [PATCH 32/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index e900d196f9dd52..5614d689845b54 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -98,5 +98,5 @@ Enterprise features will build on the open source version of the components. We are looking for a [full-time software developer](/company/software-engineer/) to join us! -If you want to help us onboard more full-time developers in the team, we document [a couple of ways](/getting-started/faq/#material-ui-is-awesome-how-can-i-support-the-project). +If you want to help us onboard more full-time developers in the team, [here are a couple of ways](/getting-started/faq/#material-ui-is-awesome-how-can-i-support-the-project). For instance, spreading the word to other developers that are looking for a great UI framework is extremely useful 🙌. From eea64e80cadec9ee548a600204242383675d088f Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:06:05 +0100 Subject: [PATCH 33/47] Update docs/pages/blog/2019.md Co-Authored-By: Matt --- docs/pages/blog/2019.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/blog/2019.md b/docs/pages/blog/2019.md index 5614d689845b54..239e562f7f8d57 100644 --- a/docs/pages/blog/2019.md +++ b/docs/pages/blog/2019.md @@ -99,4 +99,4 @@ Enterprise features will build on the open source version of the components. We are looking for a [full-time software developer](/company/software-engineer/) to join us! If you want to help us onboard more full-time developers in the team, [here are a couple of ways](/getting-started/faq/#material-ui-is-awesome-how-can-i-support-the-project). -For instance, spreading the word to other developers that are looking for a great UI framework is extremely useful 🙌. +Spreading the word to other developers that are looking for a great UI framework is also extremely helpful 🙌. From 97b53d426cef67ff068bdd79531812f80015de32 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:06:29 +0100 Subject: [PATCH 34/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 8e0e0674823dcb..eee4d59f0ecf24 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -8,7 +8,7 @@ Material-UI is a community and developer focused team that makes it easy to buil Our core values include transparency (our work is public most of the time); creating a safe, high-trust team; building incredible developer experiences; maintaining a healthy working environment; and helping to deliver web experiences that feel amazing to use on every device and connection type. -Material-UI started back in 2015 to unify React and Material Design. Today, Material-UI has grown to become one of the world's most popular React UI libraries – backed by a vibrant community of more than 1M developers in over 180 countries. +Material-UI started back in 2014 to unify React and Material Design. Today, Material-UI has grown to become one of the world's most popular React UI libraries, backed by a vibrant community of more than 1M developers in over 180 countries. ## Details of the Role From ca9769f946347179e58bb02db264394818a922d7 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:07:05 +0100 Subject: [PATCH 35/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index eee4d59f0ecf24..96ceb0d09be7f7 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -14,7 +14,7 @@ Material-UI started back in 2014 to unify React and Material Design. Today, Mate - Type of work: Contractor (long mission, full-time, convertible to an employee position) - Start date: Immediately -- Location: Remote (preference for UTC-5 to UTC+4) or Paris +- Location: Remote (preference for UTC-5 to UTC+4), or Paris ## Why we’re hiring From a0bcb6e375deb406f7f108526f801156863f46b9 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:07:37 +0100 Subject: [PATCH 36/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 96ceb0d09be7f7..4a75d86f88e787 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -18,7 +18,7 @@ Material-UI started back in 2014 to unify React and Material Design. Today, Mate ## Why we’re hiring -Both our open source products / community and our premium products are [growing fast](https://www.rank2traffic.com/material-ui.com) and we need talented engineers to keep that going! +Both our open source products and community, and our premium products are [growing fast](https://www.rank2traffic.com/material-ui.com) and we need talented engineers to keep that going! We need help improving the health of Material-UI open source: make the library easier to use, make it support more use cases, improve performance, make it more accessible, make it easier to customize. We also need help keeping up with the community, guiding developers to answers, and just generally being a positive presence in the open source community. From e4c98fc2c578517df8fefa7c3b7c1406d3fd6e3f Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:08:22 +0100 Subject: [PATCH 37/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 4a75d86f88e787..23b841147471c6 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -20,7 +20,7 @@ Material-UI started back in 2014 to unify React and Material Design. Today, Mate Both our open source products and community, and our premium products are [growing fast](https://www.rank2traffic.com/material-ui.com) and we need talented engineers to keep that going! -We need help improving the health of Material-UI open source: make the library easier to use, make it support more use cases, improve performance, make it more accessible, make it easier to customize. We also need help keeping up with the community, guiding developers to answers, and just generally being a positive presence in the open source community. +We need help to continue to improve the health of Material-UI open source: make the library easier to use, make it support more use cases, improve performance, make it more accessible, and make it easier to customize. We also need help keeping up with the community, guiding developers to answers, and just generally being a positive presence in the open source community. We also need to develop our premium content. We have a premium themes and templates marketplace, and soon premium components bundled under a Material-UI Pro offering. From 253f59cfe9b1bb3aac7ab0f93f40929d60682615 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:08:51 +0100 Subject: [PATCH 38/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 23b841147471c6..7919bb8e144568 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -36,7 +36,7 @@ Depending on the day, you’ll: On the open source side: -- **Help guide architectural decisions**. From modernizing the way we handle styles to build new components, the future of Material-UI is discussed and planned in our public RFCs and issues. You’ll be helping drive these conversations and guiding Material-UI toward the best possible solutions. +- **Help guide architectural decisions**. From modernizing the way we handle styles to building new components, the future of Material-UI is discussed and planned in our public RFCs and issues. You’ll be helping drive these conversations and guiding Material-UI toward the best possible solutions. - **Contribute to deep, meaningful refactors and feature releases**. Material-UI is a complex codebase. Meaningful features we’ve shipped recently, like a Tree View component, Slider component, they have often required a couple weeks to a month of dedicated, careful work. - **Reduce friction**. A large amount of the work of Material-UI is reducing friction and making it easier to use. This might involve careful API design, identifying and fixing top bugs, creating easier-to-use 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 as a core team maintainer 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. From f28450d357927ba19d70de614888590cfae1e5ec Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:09:51 +0100 Subject: [PATCH 39/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 7919bb8e144568..edfc540aab8dad 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -49,7 +49,7 @@ On the premium side: ## Experience you should have -- **Expertise in the modern JavaScript ecosystem**. Material-UI is built on the shoulders of giants, making use of technologies like ES2015+, TypeScript, Node.js, React, Next.js, webpack, and Babel. +- **Expertise in the modern JavaScript ecosystem**. Material-UI is built on the shoulders of giants, making use of technologies such as ES2015+, TypeScript, Node.js, React, Next.js, webpack, and Babel. - **A track record demonstrating an eye for design and solving real world user problems**. If you have a knack for shipping beautiful, intuitive software, 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 our open source team, you’d interface both directly and indirectly with community members, and contribute to user documentation. Clear communication is fundamental in creating intuitive and compelling resources. From 98680ac7dd2f0027128edf212431aa4806158397 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:16:59 +0100 Subject: [PATCH 40/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index edfc540aab8dad..e6a6ce0aed5b7d 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -37,7 +37,7 @@ Depending on the day, you’ll: On the open source side: - **Help guide architectural decisions**. From modernizing the way we handle styles to building new components, the future of Material-UI is discussed and planned in our public RFCs and issues. You’ll be helping drive these conversations and guiding Material-UI toward the best possible solutions. -- **Contribute to deep, meaningful refactors and feature releases**. Material-UI is a complex codebase. Meaningful features we’ve shipped recently, like a Tree View component, Slider component, they have often required a couple weeks to a month of dedicated, careful work. +- **Contribute to deep, meaningful refactors and feature releases**. Material-UI is a complex codebase. Components we’ve shipped recently, such as the Tree View and Slider have required weeks of dedicated, careful work. - **Reduce friction**. A large amount of the work of Material-UI is reducing friction and making it easier to use. This might involve careful API design, identifying and fixing top bugs, creating easier-to-use 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 as a core team maintainer 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 on the team 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. From bd5fd2a548bd17de3a73c634924d8b513a9891d0 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:17:31 +0100 Subject: [PATCH 41/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index e6a6ce0aed5b7d..c63fdad785231b 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -38,7 +38,7 @@ On the open source side: - **Help guide architectural decisions**. From modernizing the way we handle styles to building new components, the future of Material-UI is discussed and planned in our public RFCs and issues. You’ll be helping drive these conversations and guiding Material-UI toward the best possible solutions. - **Contribute to deep, meaningful refactors and feature releases**. Material-UI is a complex codebase. Components we’ve shipped recently, such as the Tree View and Slider have required weeks of dedicated, careful work. -- **Reduce friction**. A large amount of the work of Material-UI is reducing friction and making it easier to use. This might involve careful API design, identifying and fixing top bugs, creating easier-to-use error messages, and writing documentation and blog posts about features you ship. +- **Reduce friction**. A large amount of the work on Material-UI 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 as a core team maintainer 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 on the team 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. From d35b00d99d6e57790c365a15e3689ae637bc9dee Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:18:14 +0100 Subject: [PATCH 42/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index c63fdad785231b..17787841337048 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -40,7 +40,7 @@ On the open source side: - **Contribute to deep, meaningful refactors and feature releases**. Material-UI is a complex codebase. Components we’ve shipped recently, such as the Tree View and Slider have required weeks of dedicated, careful work. - **Reduce friction**. A large amount of the work on Material-UI 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 as a core team maintainer 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 on the team 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. +- **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. On the premium side: From ffc5f318e40af974ae341c32da7024f59a780290 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:20:04 +0100 Subject: [PATCH 43/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 17787841337048..fb3b0cf36f4ef7 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -50,7 +50,7 @@ On the premium side: ## Experience you should have - **Expertise in the modern JavaScript ecosystem**. Material-UI is built on the shoulders of giants, making use of technologies such as ES2015+, TypeScript, Node.js, React, Next.js, webpack, and Babel. -- **A track record demonstrating an eye for design and solving real world user problems**. If you have a knack for shipping beautiful, intuitive software, we want you on our team. +- **A track record of demonstrating an eye for design and solving real world user problems**. If you have a knack for shipping beautiful, intuitive software, 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 our open source team, you’d interface both directly and indirectly with community members, 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. From fdeb8327447f3652a181dd493339a47cf99c45b0 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:21:35 +0100 Subject: [PATCH 44/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index fb3b0cf36f4ef7..11095743411f73 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -54,7 +54,7 @@ On the premium side: - **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 our open source team, you’d interface both directly and indirectly with community members, 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, and reaching out to assist others, you’ll be an incredible addition to our team. Our team thrives because of continuous learning. First time mistakes should be celebrated, not blamed. +- **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 frontend 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! From 1174266765355dee909054a2b79dba5d2f46c37f Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:22:15 +0100 Subject: [PATCH 45/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 11095743411f73..224aba16d2be95 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -52,7 +52,7 @@ On the premium side: - **Expertise in the modern JavaScript ecosystem**. Material-UI is built on the shoulders of giants, making use of technologies such as ES2015+, TypeScript, Node.js, React, Next.js, webpack, and Babel. - **A track record of demonstrating an eye for design and solving real world user problems**. If you have a knack for shipping beautiful, intuitive software, 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 our open source team, you’d interface both directly and indirectly with community members, and contribute to user documentation. Clear communication is fundamental in creating intuitive and compelling resources. +- **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. From 950640d2282af0208138b525659b064bc6c32921 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 00:42:09 +0100 Subject: [PATCH 46/47] Update docs/src/pages/company/software-engineer/software-engineer.md Co-Authored-By: Matt --- docs/src/pages/company/software-engineer/software-engineer.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 224aba16d2be95..499db18357bb33 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -42,7 +42,7 @@ On the open source side: - **Collaborate with the community**. Many small as well as meaningful fixes and features have been contributed by the community. Your role as a core team maintainer 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. -On the premium side: +Premium components: - **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. @@ -81,7 +81,7 @@ The work you would be doing is somewhat unique and idiosyncratic. You probably h ## Benefits for you - A competitive compensation. -- Flexible workplace, hours, holidays. +- Flexible workplace & hours. ## Apply From 199290f3970e6143c8707586900a71ab4f67d31e Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sat, 1 Feb 2020 01:11:58 +0100 Subject: [PATCH 47/47] polish premium description --- .../src/pages/company/software-engineer/software-engineer.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/src/pages/company/software-engineer/software-engineer.md b/docs/src/pages/company/software-engineer/software-engineer.md index 499db18357bb33..09d14b6eff2339 100644 --- a/docs/src/pages/company/software-engineer/software-engineer.md +++ b/docs/src/pages/company/software-engineer/software-engineer.md @@ -22,11 +22,12 @@ Both our open source products and community, and our premium products are [growi We need help to continue to improve the health of Material-UI open source: make the library easier to use, make it support more use cases, improve performance, make it more accessible, and make it easier to customize. We also need help keeping up with the community, guiding developers to answers, and just generally being a positive presence in the open source community. -We also need to develop our premium content. We have a premium themes and templates marketplace, and soon premium components bundled under a Material-UI Pro offering. +We also need to develop our premium content. We have a premium store, and soon an enterprise class offering, starting with the data grid. +Enterprise features will build on the open source version of the components. ## Why this is interesting -Our solution is empowering React developers to build awesome applications. It should be easy, it shouldn’t require any advanced technical skills. Hundreds of thousands of developers use Material-UI every month. Let’s reach the full potential. +Our solution is empowering React developers to build awesome applications. It should be easy, it shouldn’t require any advanced technical skills. Hundreds of thousands of developers use Material-UI every month. Let’s reach the full potential :D! Our premium products portfolio is still small, with a million interesting and challenging problems to solve.