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

Refactor footer #1561 #1572

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

Conversation

JabaDUDE
Copy link
Contributor

Summary

  • Reorganized footer links
  • Removed external link styled component
  • Created new styled component for non-navbar drop items to match styling

Checklist

  • On the frontend, I've made my strings translate-able.
  • If I've added shared components, I've added a storybook story.
  • I've made pages responsive and look good on mobile.

Screenshots

image_2024-06-18_194543716
refactor-footer1

Known issues

Only caveat is the spacing of the footer on desktop. Might need to redo footer in columns and rows to create even spaces between bottom and top half of footer

Steps to test/reproduce

For each feature or bug fix, create a step by step list for how a reviewer can test it out. E.g.:

  1. Go to the home page
  2. Go to footer

Copy link

vercel bot commented Jun 18, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
maple-dev ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 20, 2024 2:21am

Copy link
Collaborator

@Mephistic Mephistic left a comment

Choose a reason for hiding this comment

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

Looking good! Just want to see some f f the two comments before

@@ -193,13 +168,13 @@ const LearnLinks = () => {
return (
<>
<StyledInternalLink href="/learn/writing-effective-testimony">
{t("links.learnWriting")}
{t("To Writing Effective Testimony")}
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: The param passed to the t translate function should be a key pointing to the relevant text in the locales/** language files, not the english text itself. The goal is to have no user-visible text in component files, including the english text, and we only reference user-visible text based on their translation keys.

e.g. Instead of t("To Writing Effective Testimony"), this should be something like t("common.footer.writingTestimony") - and the locales/en/common.json file should contain a key for common.footer.writingTestimony with the value of `"To Writing Effective Testimony".

micro nit: To Writing Effective Testimony should probably just be Writing Effective Testimony


&:hover {
Copy link
Collaborator

Choose a reason for hiding this comment

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

In the Desktop view, the Browse Bills text gets unreadably dark when hovered over - we should probably add a hover style to make this more visible, not less when a user is ready to interact with it.

Copy link
Collaborator

Choose a reason for hiding this comment

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

On hover, this is what the Browse Bills link looks like:
Screenshot 2024-06-18 at 8 35 55 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants