Skip to content

Varkopat/enhancement/644/update site footer to match figma designs#654

Open
Varkopat wants to merge 13 commits into
devfrom
Varkopat/enhancement/644-update-site-footer-to-match-figma-designs
Open

Varkopat/enhancement/644/update site footer to match figma designs#654
Varkopat wants to merge 13 commits into
devfrom
Varkopat/enhancement/644-update-site-footer-to-match-figma-designs

Conversation

@Varkopat
Copy link
Copy Markdown

@Varkopat Varkopat commented May 20, 2026

📄 Pull Request Overview

Closes #644

🔧 Changes Made

  1. Added FooterContact, FooterInfo, and FooterLinks components with styles
  • Implemented FooterContact component for displaying contact information with email links and a "Work With Us" section.

  • Created FooterInfo component to present additional information with links to relevant pages.

  • Developed FooterLinks component to manage navigation links in the footer.

  • Added corresponding SCSS styles for each component to ensure proper layout and design.

  • Embedded FeedbackCard to FooterMobile and made it responsive in FooterMobile.module.scss.


Checklist Before Submission

  • Functionality: I have tested my code, and it works as expected.
  • JSDoc: I have added or updated JSDoc comments for all relevant code.
  • Debugging: No console.log() or other debugging statements are left.
  • Clean Code: Removed commented-out or unnecessary code.
  • Tests: Added new tests or updated existing ones for the changes made.
  • Documentation: Documentation has been updated (if applicable).

📝 Additional Information

Provide any additional context or information that reviewers may need to know:

  • Screenshots: [Include any screenshots or videos if the changes affect the UI]
screenshot

Varkopat added 4 commits May 20, 2026 16:38
…styles

- Implemented FooterContact component for displaying contact information with email links and a "Work With Us" section.
- Created FooterInfo component to present additional information with links to relevant pages.
- Developed FooterLinks component to manage navigation links in the footer.
- Added corresponding SCSS styles for each component to ensure proper layout and design.
Copy link
Copy Markdown
Member

@Skoivumaki Skoivumaki left a comment

Choose a reason for hiding this comment

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

Routing, i18n, UI/layout changes have been done as requested. However there are still some small styles fixes needed. Comments are much better this time. Overall you have improved since last issue, good work 👍
Todo:

  1. Incorrect dimensions: In Figma there are 3 clear columns with 64px padding for each column that their content fills centered on all directions. Instead of using pixels to set sizes, apply responsive units instead that match the 64px of padding etc. (If needed create style cases for desktop and mobile, since flex can differ alot)
  2. Logo is incorrect size on desktop and not center aligned.
  3. You applied max-width for mobile, which causes feedback component to break because of the shrinking. (let feedback component ignore max-width for now, since it will eventually need updating too)
  4. Fonts are not loading or are missing.
  5. On desktop footer has unnecessary top property, that causes alot of spacing.
  6. Footer has set width of 1920px that denies it expanding past FullHD screens, breaking footer for 2k and 4k devices.

See comments.

flex-direction: column;
position: relative;
z-index: 20;
width: 1920;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Depending on the browser, these properties are invalid and do nothing.

width: 1920;
height: 482;
gap: 30px;
opacity: 1;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

You added alot of opacity properties that do nothing. Default is always 1 anyway: https://www.w3schools.com/cssref/css3_pr_opacity.php

What changed:

- Added wide-screen variables at min-width: 1920px.
- Footer inner layout can now expand from 120rem up to 160rem on very wide screens.
- Column padding scales from the normal 4rem up to 8rem.
- Logo scales beyond the standard 275 x 270 proportion on 4k, capped at 24rem x 23.5rem.
- Social bar height, social icon size, icon gap, footer text blocks, and copyright size also scale gently for 4k.
- Kept standard desktop sizing intact at normal desktop widths.

Other changes:

- Removed max-width from mobile.
- Fixed fonts. Fonts are now loading hopefully.
- Removed unnecessary properties and opacities.

Tests passed:

- Focused footer tests
- npm.cmd run lint passed with only existing unrelated warnings.
@Varkopat Varkopat requested a review from Skoivumaki May 27, 2026 20:54
Copy link
Copy Markdown
Member

@Skoivumaki Skoivumaki left a comment

Choose a reason for hiding this comment

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

All good 👍

Copy link
Copy Markdown
Contributor

@Rutjake Rutjake left a comment

Choose a reason for hiding this comment

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

Great work!
Just one small thing: the link fonts should be DM Sans.
Also, regarding the mobile footer, there should be a button for feedback. However, since we don't know yet what it's supposed to open, let's leave that change for the next issue.

color: #faf9f6;
text-decoration: none;
font-family: var(--font-dm-s);
font-family: 'DM Sans';
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Fonts are set like so: font: var(--font-dm-s);
S size, since its nearest to 0.9em which is set in AppLink. Meaning your font-size: clamp(0.875rem, 0.75vw, 1.25rem); is being overridden.

See: https://github.com/Alt-Org/Altzone-WebPages/wiki/9.-Css-rules#fonts

@Varkopat Varkopat requested a review from Rutjake June 3, 2026 18:20
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.

3 participants