-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
refactor(website): styling cleanups for hero sections #660
Conversation
…ork". Added German translations and made small design changes for a better look and feel. Deleted contact selection as it had the same content as footer, which followed after section. Added important data in hero section, such as contact email and registration number. Left contact section in the code as it's interlinked with another sections and might be reused later (but fine for me when deleted).
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Visit the preview URL for this PR (updated for commit f82906f): https://si-admin-staging--pr660-sandino-adapted-hero-n9c7tw2k.web.app (expires Thu, 07 Dec 2023 11:50:31 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: b7b0969384059dce6ea8fad1ee1d1737e54e6676 |
…ork". Added German translations and made small design changes for a better look and feel. Deleted contact selection as it had the same content as footer, which followed after section. Added important data in hero section, such as contact email and registration number. Left contact section in the code as it's interlinked with another sections and might be reused later (but fine for me when deleted).
…nto sandino/adapted-hero-sections
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 great🙌🏼 We should move some styling to components though and not use UI components and then restyle them.
If a file or some code is not needed anymore, please remove it. We can always dig it back up from the repository if we need it again.
<Typography size="md" lineHeight="normal"> | ||
{translator.t('landing-page.registration-duns')} | ||
</Typography> | ||
<a href="https://www.dnb.com/duns/what-is-a-DUNS-number.html"> |
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 should always use Link
components for links.
<PopoverTrigger> | ||
<Badge | ||
variant="outline" | ||
className="hover:bg-muted-foreground text-muted-foreground hover:text-secondary-foreground transition-transform duration-300 hover:scale-105" |
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 think it's not so nice to have these configurations here in className
. They should go into the Badge component so that it behaves the same every time we use it.
{translator.t('landing-page.registration-uid')} | ||
</Typography> | ||
<a href="https://www.uid.admin.ch/Detail.aspx?uid_id=CHE-289.611.695&lang=en"> | ||
<Button variant="link" className="m-0 p-0"> |
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.
Remove className="m-0 p-0"
# Conflicts: # website/src/app/[lang]/[region]/(website)/our-work/(sections)/our-work.tsx
@mkue it would be OK to also delete the now unused
contact.tsx
(or to keep it if you want to reuse it later, i.e. on a specific contact page – not planned yet)