-
Notifications
You must be signed in to change notification settings - Fork 9
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
careers page, various minor fixes #784 #786
Conversation
const finalLayout = isMobile ? 'squeezed' : layout | ||
className = `testimonial ${finalLayout} ${className || ''}` | ||
|
||
return finalLayout === 'squeezed' ? ( |
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't this be done with css + a media query?
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, that was what I thought at first, but the layouts are just different. Like the puzzle doesn't fit. I can't articulate why, just look at the different versions and you can see what I mean.
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.
that's unfortunate, but happens. @melissasamworth it's all your fault!!
@@ -0,0 +1,650 @@ | |||
import Card from '../Card' |
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.
you're going to have to move this to app/routes/how-can-i-help.career.tsx
, which will be a bit of a problem - sorry about that
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.
All good, the change was needed. I've fixed it all now
@@ -48,7 +48,7 @@ const Button = ({ | |||
const LinkComponent = !action.startsWith('http') | |||
? Link | |||
: ({to, children, ...props}: {[k: string]: any}) => ( | |||
<a href={to} {...props}> | |||
<a href={to} rel="noreferrer" target="_blank" {...props}> |
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.
@bryceerobertson I switched it here so that by default links to other pages open in a new tab. @mruwnik is that ok?
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.
not according to me. That's what the control button is for... But there was a whole discussion about this and I think the external links faction won :/ @melissasamworth is that correct?
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.
I'd prefer the LinkCard to accept a className
param, otherwise this looks good (other than the css, of course - I didn't check that)
@@ -48,7 +48,7 @@ const Button = ({ | |||
const LinkComponent = !action.startsWith('http') | |||
? Link | |||
: ({to, children, ...props}: {[k: string]: any}) => ( | |||
<a href={to} {...props}> | |||
<a href={to} rel="noreferrer" target="_blank" {...props}> |
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.
not according to me. That's what the control button is for... But there was a whole discussion about this and I think the external links faction won :/ @melissasamworth is that correct?
{links?.map((link) => <LinkCard key={link.title} action={link.action || '#'} {...link} />)} | ||
{links?.map((link) => ( | ||
<div key={link.title} className="padding-bottom-16"> | ||
<LinkCard action={link.action || '#'} {...link} /> |
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.
why not apply the class directly to the LinkCard
?
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.
Because we are spacing with padding, and the padding would go inside the button
const finalLayout = isMobile ? 'squeezed' : layout | ||
className = `testimonial ${finalLayout} ${className || ''}` | ||
|
||
return finalLayout === 'squeezed' ? ( |
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.
that's unfortunate, but happens. @melissasamworth it's all your fault!!
No description provided.