-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[website] Close the open engineering roles #28428
[website] Close the open engineering roles #28428
Conversation
4f10391
to
ec051a7
Compare
docs/pages/careers.tsx
Outdated
)} | ||
</React.Fragment> | ||
))} | ||
{Object.values(openRolesData).map((category) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like you never use their keys so you might as well use an array to ensure IE11 compat. Bad look in general if people audit IE11 compat.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah ok, we don't need an object, an array is good enough, and will better scale if we move to a CMS, I'm updating.
I have just tried on BrowserStack, all the pages are broken on http://mui.com/, docs included with IE 11. I would vote for ignoring it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing the links 👍
Preview: https://deploy-preview-28428--material-ui.netlify.app/careers/
The PR started with a straightforward objective: to close the open engineering roles. We have done enough. Time to focus on the product.
Bonus:
Stack divider
feature, such a time saver! At some point, I think that we should push this to a CMS. It's frustrating/slow to have to open a PR to change the content.