-
Notifications
You must be signed in to change notification settings - Fork 2
Home #107
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
Home #107
Conversation
Ready for review. Should be reviewed after #106, but can (and probably should) be merged at the same time. Just have 1 outstanding question: @thekaveman The design calls for removing the Capabilities Statement button. But since we don't have the #44 yet, we don't have any other way for people to get to it. Should I keep the button there? Should I remove the Get in touch button, so at least the design is the same with 1 button? There is a contact email link right below it. @segacy1 If we do need 2 buttons, what should the 2nd button look like? I guessed what an outline button might look like, but I'm not sure about how it looks on hover. |
Created a version of the homepage with both buttons in figma too so we have it here For the secondary button hover, updated to this: In Figma here Also, two additional notes:
|
c084661
to
9c05f2e
Compare
63819c8
to
f02bdb1
Compare
Marking this back as |
f02bdb1
to
90c673a
Compare
@segacy1 It won't affect the home page, but it will affect the job post page. The job post page has a ![]()
|
5e09e43
to
3875804
Compare
--bs-font-sans-serif: "Roboto", system-ui,-apple-system,"Segoe UI","Helvetica Neue","Noto Sans","Liberation Sans",Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Noto Color Emoji"; | ||
--bs-font-monospace: "Source Code Pro Bold",monospace; | ||
--focus-box-shadow: 0 0 0 calc(2.5rem / 16) var(--brand-primary-black), 0 0 0 calc(4rem / 16) var(--brand-primary-green); |
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.
This code creates this effect as a box-shadow:
How to read this code:
0 0 0 calc(2.5rem / 16) var(--brand-primary-black)
: Create a 2.5px-thick black line, the same color as the background color.0 0 0 calc(4rem / 16) var(--brand-primary-green)
: Below that first line, starting from the same point, add another 4px of green line. Only 1.5px of green will actually show up. That's calculated like this: 4-2.5 = 1.5.
li>a { | ||
text-decoration: none; |
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.
No longer necessary because all a
elements have text-decoration: none
now.
h1 { | ||
font-size: 2rem; | ||
margin-top: 1.5rem; | ||
margin-bottom: 1.5rem; | ||
} |
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.
h3 { | ||
font-size: 1.17rem; | ||
h3, | ||
.posting h2 { |
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.
Since each Job Post is created from Markdown, and we can't declare CSS classes in Markdown, this .posting h2
declares that all H2s on a job post should actually use h3
styles, which is what Figma calls for.
.btn-primary:focus, | ||
.btn-primary:focus-visible, | ||
.btn-outline-primary:focus, | ||
.btn-outline-primary:focus-visible { | ||
background-color: var(--bs-btn-bg); | ||
border-color: var(--bs-btn-border-color); |
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.
This is a really, really neat nesting CSS Variable feature.
The underlying Figma logic calls for: For btn-primary
and btn-outline-primary
, the background color on focus should be the same as the default background color. Same with the border color. Bootstrap code has these values set to the hover colors instead - which is brighter - instead of the default color.
In the design, the background color for Primary is green, and the background color for Outline is black.
In the code, this is how those values are set:
.btn-primary {
--bs-btn-bg: var(--button-primary-default);
--bs-btn-border-color: var(--button-primary-default);
}
.btn-outline-primary {
--bs-btn-bg: transparent;
--bs-btn-border-color: var(--button-primary-default);
In this code below, I'm able to set the background-color to be the var(--bs-btn-bg)
in each class's context. Even though var(--bs-btn-bg)
is set to different values for .btn-primary
and .btn-outline-primary
, the CSS figures out what value is being scoped. Saves time and lines of code.
.btn-primary:focus,
.btn-primary:focus-visible,
.btn-outline-primary:focus,
.btn-outline-primary:focus-visible {
background-color: var(--bs-btn-bg);
border-color: var(--bs-btn-border-color);
}
Added a bunch of explanatory comments. @thekaveman @angela-tran Ready for review. Ideally, both this PR and the #106 PR can go out at the same time, so that the Home Page looks in sync with the new Footer. |
<h2 class="mt-5 fs-6">Past roles</h2> | ||
<ul id="closed" class="list-unstyled"></ul> | ||
<h2 class="mt-5 fs-6 pb-1 mb-2">Past roles</h2> | ||
<ul id="closed" class="list-unstyled d-flex flex-column gap-2"></ul> |
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.
Use d-flex flex-column gap-2
to create a 8px vertical gap (as in, padding) between the list items. d-flex flex-column
sets the links to flow vertically, rather than horizontally and tells gap
to create the gap vertically.
Let's leave both buttons there for now, until we have the nav from #44. /cc @AnthonyRollins |
✅ Deploy Preview for compilerla ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@segacy1 There's a Netlify preview link now, so you can check out how the buttons look: https://deploy-preview-107--compilerla.netlify.app/ |
f804eed
to
473534d
Compare
Rebased with latest |
Hi @machikoyasuda - 2 quick notes from reviewing on Netlify
I'll make sure that's reflected in Figma as well |
@segacy1 These 2 fixes are now out here: https://deploy-preview-107--compilerla.netlify.app/ |
assets/compiler-la--pattern-sm.svg
Outdated
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.
Can we please avoid using compiler-la
as an ID or engineering string whenever possible? Either compiler
or compiler-llc
if you need a longer version. For this is could even be like brand-pattern
or shapes-brand-pattern
or something.
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.
Got it. I put the company name in there for SEO reasons 😅
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.
But Compiler LA is not the official company name anymore right? It's Compiler LLC.
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.
renamed 52b9c66
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.
@thekaveman need a re-review for this! thank u
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.
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 good to me 👍
#107 changed the class names for the button styles
fix #65
Note: This PR was created off of
fix/footer
#106. These 2 changes can go out together in sync, so the Home page doesn't look disjointed.What this PR does
- Home page: Adds new home headline, paragraph text, image. Upload new brandmark. New cyan/teal color.
- Header: Removes the large logo logic. Add the box-shadow.
- Whole app: Set correct background color
Components
btn-primary
,btn-outline-primary
with:hover
,:focus
,:disabled
modes all designed..h2
h2
and.h3
. The home page has ah1
that uses a.h2
style class. The job posting page uses a.h3
class style on itsh2
s. This PR does not re-do all the headline font sizes. That will come in a separate PR Fix: Font weights #116text-info
to be gray color.Screenshots
Home
Jobs (Ensure no regressions)
Posting (Ensure no regressions)
Perf / A11y