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

Footer refresh #13825

Merged
merged 6 commits into from May 10, 2024
Merged

Footer refresh #13825

merged 6 commits into from May 10, 2024

Conversation

mtruj013
Copy link
Contributor

@mtruj013 mtruj013 commented Apr 29, 2024

Done

QA

Issue / Card

Fixes https://warthogs.atlassian.net/browse/WD-10375

@webteam-app
Copy link

@mtruj013 mtruj013 marked this pull request as draft April 29, 2024 16:02
@lyubomir-popov
Copy link
Contributor

lyubomir-popov commented Apr 30, 2024

hi @mtruj013 mostly looks good, a few things I noticed (review not finished):

  • the orignal idea for small screens was to have a horizontally scrollable inline list of links , not just the top level links:

https://www.figma.com/file/Le4TTzyOFbcbqTPJ1tVoZT/U.com---Home-and-footer-(rebranding)?type=design&node-id=3304%3A13136&mode=design&t=jMHZQ4Fgbeh3nAl7-1

  • links are for some reason bold - they should be regular font weight:

image

  • back to top is broken

image

  • anchors outside paragraphs, leading to misalignments:
    image

@mtruj013
Copy link
Contributor Author

@lyubomir-popov thanks for the feedback! I'll let you know once I've pushed, but just wanted to note that the original design I was given is this one https://www.figma.com/file/Le4TTzyOFbcbqTPJ1tVoZT/U.com---Home-and-footer-(rebranding)?type=design&node-id=2910-7036&mode=design&t=WBcXnLD5p0YuILNN-0

@mtruj013 mtruj013 changed the base branch from main to landing-feature April 30, 2024 11:31
@mtruj013
Copy link
Contributor Author

A few questions/comments for you @lyubomir-popov:

links are for some reason bold - they should be regular font weight

They are h5s (styling wise) as per both versions of the design, there's nothing else affecting font weight. This still seems to be the most appropriate heading styling from what I can see, but please let me know what you'd like it to be changed to.

back to top is broken

I fixed the alignment, there were some old footer styles that were messing with the padding, but other than that the functionality should be unaffected (tested and passed locally). Let me know if it's still not working for you.

anchors outside paragraphs, leading to misalignments

They're not wrapped in paragraphs because they're list elements, inline ones at that. Surely these should not be wrapped in a p tag which is a block level element. Could you please clarify?

@juanruitina
Copy link
Contributor

juanruitina commented Apr 30, 2024

And here my feedback for the footer "MVP":

  • I'm happy to just link to the bubbles' homes on mobile for the MVP; but please remove u-hide--small from the links under the last three items, Solutions, Sectors, More: they don't make sense otherwise
  • Let's add the "u-responsive-realign" class that we used in https://ubuntu.com/download/desktop to the "p-inline-list" lists, that way they will wrap nicely
  • Remove "Canonical" from "Canonical Embedding Programme" so we avoid wrapping on large screens.
  • I see all other links below (About us, Community, Careers... Legal information, Data privacy...) are small, but they aren't on Figma

Accessibility concern: I think on the next iteration we will need to make sure we turn this navigation into a single list; navs should be lists and not contain headings. Headings pollute the accessibility tree but without the nav being a list we can't convey hierarchy otherwise. But I think we can address this later, the heading thing is a problem in the live version so it's not a regression.

@juanruitina
Copy link
Contributor

I pushed some changes for better responsiveness, thank you MariaPaula for letting me indulge in a bit of coding :) Feel free to tweak as needed.

All links that are not bubble subitems are now visible on smaller viewports too, there's no reason why we shouldn't show them (particularly the legal ones). I also changed the spacing of the sections as per the design (regular instead of shallow).

I see some misalignments in the top margin of links, but I noticed @lyubomir-popov flagged it up and it's a visual matter anyway.

This is OK UX-wise now.

@lyubomir-popov
Copy link
Contributor

lyubomir-popov commented May 8, 2024

They are h5s (styling wise) as per both versions of the design, there's nothing else affecting font weight. This still seems to be the most appropriate heading styling from what I can see, but please let me know what you'd like it to be changed to.

sorry my bad, you're right - bold is correct here.

They're not wrapped in paragraphs because they're list elements, inline ones at that. Surely these should not be wrapped in a p tag which is a block level element. Could you please clarify?

this is what we need to achieve: baseline alignement between h5s on the left and the rest:
image

Atm, they do not quite align. Discussing this with @bartaz, ideally we should have a version of the inline list that matches text (paragraph, h5, h6) in terms of top and bottom padding. This is something we can upstream to vanilla, but for now can we try something like that locally? You'd need to extend the inline list and apply paddin-top and padding-bottom on the items. The values can be found here for padding-bottom, and here for padding-top:

Copy link
Contributor

@lyubomir-popov lyubomir-popov left a comment

Choose a reason for hiding this comment

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

one small p-rule class we've forgot to add

@mtruj013 mtruj013 marked this pull request as ready for review May 8, 2024 11:17
@akbarkz akbarkz merged commit d47b57a into canonical:landing-feature May 10, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants