-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
[blog] Q3 2021 Update #28970
[blog] Q3 2021 Update #28970
Conversation
2bfceb8
to
48c65da
Compare
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.
(or to group the "To:"...)
docs/pages/blog/2021-q3-update.md
Outdated
|
||
<a href="/components/masonry/"><img loading="lazy" src="/static/blog/2021-q3-update/masonry.png" style="width: 700px; margin-bottom: 16px;" /></a> | ||
|
||
- We introduced a new [unstyled package](https://www.npmjs.com/package/@mui/core), laying the foundations for supporting multiple design systems with headless components. |
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.
Do you think it's worth mentioning the material-next package?
I'm not sure.
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.
From what I understand this package is mostly for us, maintainers. I think that its prime time will be once active development moved to @mui/material-next over @mui/material. I'm OK with keeping it quiet for a while.
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.
Just a few tweaks, nothing major, and all optional.
Co-authored-by: Marija Najdova <mnajdova@gmail.com>
Co-authored-by: Marija Najdova <mnajdova@gmail.com>
Co-authored-by: Matt <github@nospam.33m.co>
Co-authored-by: Matt <github@nospam.33m.co>
Co-authored-by: Matt <github@nospam.33m.co>
0de9967
to
c6cb7f9
Compare
3309db6
to
99ee113
Compare
I guess we need to remember a notification update once this is live. And do we send something to "newsletter" subscribers? |
Regarding the newsletter, we don't. As far as I can see on the Sendinblue console, we have only used it 3 times for sending updates regarding the Design Kits and that's it. And it seems like ever since the v5 release, we got a whole bunch of new subscribers, which shows that the new website pages did attract people in :) So we probably should actually set up the newsletter and use it to promote not only the quarterly updates but whatever else we have on cooking around here. There will be people listening! |
200 new subscribers in a month when we saw almost 1M users on the docs. So most people don't care or we didn't train them to care or the subscription pipeline is a bit broken. There are no subscription input at the bottom of the blog post pages to be the first one to know about the next ones, they do https://www.hashicorp.com/blog/consul-learning-journey. Instead, we taught them to subscribe to the release on GitHub and the Twitter account. I think that many people wait for their friends/trusted network to share the news. I subscribe to literally zero newsletters (non MUI related), it's overwhelming otherwise 😁. |
Preview: https://deploy-preview-28970--material-ui.netlify.app/blog/2021-q3-update/