Page MenuHomePhabricator

[landing] change text content on HeroContent component
ClosedPublic

Authored by ginsu on May 22 2023, 6:39 AM.
Tags
None
Referenced Files
F3408884: D7911.id29674.diff
Wed, Dec 4, 2:18 PM
F3407402: D7911.diff
Wed, Dec 4, 6:02 AM
Unknown Object (File)
Sun, Nov 17, 2:19 AM
Unknown Object (File)
Sun, Nov 17, 1:38 AM
Unknown Object (File)
Sun, Nov 17, 1:38 AM
Unknown Object (File)
Sun, Nov 17, 1:38 AM
Unknown Object (File)
Sat, Nov 16, 11:27 PM
Unknown Object (File)
Sun, Nov 10, 8:55 PM
Subscribers

Details

Summary

As part of the landing redesign we are completely redesigning our Hero section. This diff updates the header and subheader of the hero section. Subsequent diffs will handle the Hero image, the email form, and the layout of the hero

Here is the Figma design for reference:

Screenshot 2023-05-22 at 4.45.54 PM.png (2×3 px, 2 MB)

Depends on D7898

Test Plan

Please see the screenshots below:

Desktop:

Screenshot 2023-05-22 at 4.31.35 PM.png (2×3 px, 1 MB)

Tablet:

Screenshot 2023-05-22 at 4.32.05 PM.png (2×3 px, 923 KB)

Phone:

Screenshot 2023-05-22 at 4.31.58 PM.png (2×3 px, 907 KB)

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

ginsu edited the test plan for this revision. (Show Details)
ginsu added reviewers: atul, kamil.
ginsu edited the summary of this revision. (Show Details)
ginsu added inline comments.
landing/hero-content.css
8–9

This style is supported by all modern browsers (browsers from the last 10 years)

https://developer.mozilla.org/en-US/docs/Web/CSS/background-clip

10
landing/hero-content.react.js
4

The next diff will remove this dependency from our package.json

ginsu edited the summary of this revision. (Show Details)
ginsu requested review of this revision.May 22 2023, 6:57 AM
atul added inline comments.
landing/hero-content.css
9

Annoying that so many browsers still have this "Implemented with the vendor prefix: -webkit-" so we can't just go w/ background-clip

Oh well

landing/hero-content.react.js
16–17

We aren't "separating" subheading2 into subHeading2 w/ camelCase, should we just do css.subheader for consistency

This revision is now accepted and ready to land.May 22 2023, 9:10 AM
landing/hero-content.css
9

We should probably try to avoid having explicit vendor prefixes. Is there a tool in our environment that can do it for us? Maybe something around our css-loader? Or we can introduce something from e.g. postcss.
Still, probably not worth exploring at this point.

landing/hero-content.css
9

I agree having explicit vendor prefixes is not the most ideal; however, since every modern browser (from the last 10 years) supports these styles I think there is no risk to include this right now. If I have time at the end I will do some digging into an implementation w/o these vendor prefixes.

ginsu edited the test plan for this revision. (Show Details)

rebase before landing