Skip to content
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] Improve homepage rebranding #27663

Merged
merged 109 commits into from Aug 18, 2021
Merged

Conversation

siriwatknp
Copy link
Member

@siriwatknp siriwatknp commented Aug 9, 2021

Preview: https://deploy-preview-27663--material-ui.netlify.app/branding/home/, a follow-up on #27488

Screen Shot 2564-08-17 at 10 51 32

lighthouse run on 17 Aug

Important

  • No relative import, e.g. import ShowcaseContainer from './ShowcaseContainer'; is KO IMHO, make it harder to move code around.
  • Link strategy
  • Missing the <Head> component, it comes with <title>, description, social sharing card and SEO meta
  • HTML errors https://validator.w3.org/nu/?doc=https%3A%2F%2Fnext--material-ui.netlify.app%2Fbranding%2Fhome%2F
  • Fix issues from lighthouse audit
  • Layout shift between SSR and client-side hydrated
  • Headers sequence
  • Should we add h3 where they might be relevant?

Capture d’écran 2021-08-12 à 17 51 47

  • Change ThemeToggle UI according to design change
  • Wave extension reports

Capture d’écran 2021-08-10 à 11 59 08

  • Fix copy writing (from Matt's comments)

    • "Easily customizability" to "Easily customized"
    • "2k people open-source community." -> "2000 member open-source community." (I'm not sure about this)
    • "We care about making it good for everyone." -> "We care about making your UX great for everyone."
    • "Want more components?" -> "Need more components?"
  • Regarding the point of Matt, I think that it was related to something like this:

    Capture d’écran 2021-08-12 à 17 54 59

    With 1 new contributor on average a day, and a pace that is slowing down, it will take us a while to reach 3k. It wouldn't make sense to round to 3k if we are at 2,600 contributors. Maybe this otherwise?

    Capture d’écran 2021-08-12 à 18 30 17

Hero

  • Not enough space for the companies in mobile viewport (change to 2 columns)
  • Broken tabs indicator size, it's not fixed yet, see my previous fix proposal (in the core) I have removed transform: scale(0.9) for now, I think Tabs works just fine.

Capture d’écran 2021-08-08 à 00 17 11

  • @mui/core won't be a real package, @mui/core-material instead?

Products core

  • Something is off with the icon on smaller screens and with SSR only.

Capture d’écran 2021-08-06 à 13 04 55

  • Dark mode icons

Capture d’écran 2021-08-12 à 12 29 55

  • Fix the company logo alignment, dark mode, and color

  • Add more space at the bottom to match Figma

Capture d’écran 2021-08-12 à 19 33 53

Products Advanced X

  • display DataGrid with code preview

Our sponsors

  • Out of date sponsors
  • Updated layout
  • srcSet for the mages

Go live

  • The layout change based on the font loaded state.
Loaded (2 lines)Unloaded (1 lines)
Capture d’écran 2021-08-06 à 13 28 38 Capture d’écran 2021-08-06 à 13 29 44

Footer

Improvements

  • When first loading the page with an empty cache, the image loading UX is a bit weird at Products Templates & Products kits
  • tabs lowercase -> uppercase at What do you get?

Testimonials

  • Change contrast on the company logo to blue.200 in dark mode.
  • no h3 for the KPIs

Footer

  • Does it still make sense to mention the version and license? It's not scaling to more products. Maybe have this on the docs only?
  • Would it make more sense to link https://github.com/mui-org/ for the GitHub link? It's for instance what mongodb.com does

Defer

improve these points later if we have bandwidth after completing other important pages.

Hero

Capture d’écran 2021-08-17 à 11 24 25

Testimonials

  • Hardcoded KPIs: 2M, 70k, 2k, 13k
  • Should we add a link on the KPIs? Stars => GitHub, download => npm, etc.

material design components section

  • Make outlined text field custom theme different from material design (may be remove floating label)

Advanced X section

  • Unecessary default horizontal scrollbar

Capture d’écran 2021-08-17 à 11 25 43

sponsors

  • Match the layout in Figma, larger images for gold, and even bigger images for diamonds

Capture d’écran 2021-08-17 à 11 28 57

[technical] coding wise

  • Cleanup comments in MarkdownElement
  • No asset URL constructions

@mui-pr-bot
Copy link

mui-pr-bot commented Aug 9, 2021

No bundle size changes (experimental)

Generated by 🚫 dangerJS against d9b090d

@siriwatknp
Copy link
Member Author

@oliviertassinari Email subscribe is working but might need to revisit the flow (around confirmation page). Let's move that part out of this PR.

docs/pages/branding/home.tsx Outdated Show resolved Hide resolved
docs/pages/branding/home.tsx Outdated Show resolved Hide resolved
@github-actions github-actions bot added the PR: out-of-date The pull request has merge conflicts and can't be merged label Aug 11, 2021
@github-actions github-actions bot removed the PR: out-of-date The pull request has merge conflicts and can't be merged label Aug 11, 2021
@danilo-leal
Copy link
Contributor

danilo-leal commented Aug 17, 2021

  • The dark mode colors is wrong, it should use opacity with the background
  • The logos don't feel aligned on the same text baseline, a point raised by @michaldudak
  • The logos might be colored not grey, but we didn't really settle on this one. I'm personally worried about altering recognized brand images. a point raised by @mbrookes

@oliviertassinari I have tweaked a bit of the sizing + spacing and changed the company logos to use their original branding color. Let me know what you think! The one I'm still thinking is a bit off is Amazon... but overall, I'm ok with it!

@oliviertassinari
Copy link
Member

@danilo-leal It looks great. We might be able to compress the SVG paths, e.g. with https://jakearchibald.github.io/svgomg/

@danilo-leal
Copy link
Contributor

@danilo-leal It looks great. We might be able to compress the SVG paths, e.g. with https://jakearchibald.github.io/svgomg/

Done! :)

@oliviertassinari oliviertassinari mentioned this pull request Aug 17, 2021
53 tasks
@siriwatknp siriwatknp changed the title [WIP] Improve homepage rebranding [website] Improve homepage rebranding Aug 18, 2021
name: null,
target: null,
});
const debouncedSetData = React.useRef(debounce(setData, 200));
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@eps1lon The reason for debounce is to improve the ux when moving mouse between element. This demo is without debounce, https://codesandbox.io/s/element-pointer-j0p8q?file=/src/App.tsx

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then debounce the specific call. Not all state updates. Especially not with a ref.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason for debounce is to improve the ux when moving mouse between element.

I have never seen a debounce improve UX. It was always a crutch to fix performance bottlenecks.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@eps1lon Is the demo in codesandbox does not bother you when moving mouse between elements? then compare with debounce version.

Copy link
Member

@eps1lon eps1lon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lighthouse between / and /home/branding:

First Contentful Paint
-0.5 s
+0.6 s
Speed Index
-0.8 s
+0.6 s
Largest Contentful Paint
-0.5 s
+1.0 s
Time to Interactive
-1.0 s
+1.3 s
Total Blocking Time
-50 ms
+100 ms
Cumulative Layout Shift
-0.002
+0.017

Webpagetest between / and /home/branding:

https://webpagetest.org/video/compare.php?tests=210818_BiDcRH_d06896870ed06d5c4b55b40d0c3663f9,210818_AiDc0W_f10463bee949c269555722b53cc1ce1d

/ was visually complete after 3s, /branding/home/ takes 8.5. This is quite the slow down that needs to be adressed before release. Not a good look if the homepage loads slower on a major release.
There isn't even a single paint with the new branding when the old homepage is already at 90%.

There's just way more sent over the wire on the first load:
Page Size First Load JS
┌ λ / 16 kB 304 kB
├ λ /branding/home 53.5 kB 467 kB

-- https://app.netlify.com/sites/material-ui/deploys/611c86c0f968db00075fd6f4

This PR can be merged since it's already an improvement. But this is important to do before release since it was decided to ship this with 5.0 not after.

@siriwatknp siriwatknp merged commit b0c7b7a into mui:next Aug 18, 2021
@oliviertassinari
Copy link
Member

Regarding the slowdown, if we migrate the current homepage (v4 version) from JSS to emotion at 100%, would we also see a change in performance? Maybe some of it can be explained by the styling solution that is slower in v5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
website Pages that are not documentation-related, marketing-focused.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants