Skip to content

fix(homepage): improve responsiveness on small screens #848

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

Conversation

edwinperaza99
Copy link

Summary

This PR fixes a content misalignment issue on small screens caused by a min-width constraint from base.css, which prevented the page from properly adapting to smaller viewports.

Related to #847

Changes Made:

  • Fixed main content overflow issue by setting min-width: 0; on body.
  • Properly centered .home-page__down-arrow__container using left: 50% and transform: translateX(-50%).
  • Improved mobile spacing by adjusting .home-page__content__container padding across different breakpoints.
  • Increased visibility and usability of the down arrow by making it slightly larger at smaller screen sizes.

Remaining Areas for Improvement

While this PR fixes the most noticeable layout issues, some responsiveness inconsistencies remain—especially in .home-page__content__tools-panel and other lower sections of the page. If the maintainers are open to further improvements, I’d be happy to iterate based on feedback.


Before:

before

After:
after

Resolved an issue where a `min-width` constraint from `base.css` caused content misalignment
on small screens.
@edwinperaza99 edwinperaza99 requested a review from a team as a code owner January 29, 2025 13:22
Copy link

linux-foundation-easycla bot commented Jan 29, 2025

CLA Signed

  • ✅login: edwinperaza99 / (3ef44f2)

The committers listed above are authorized under a signed CLA.

@finos-admin
Copy link
Member

This PR is stale because it has been open for 30 days with no activity. Please remove stale label or add any comment to keep this open. Otherwise this will be closed in 5 days.

@edwinperaza99
Copy link
Author

commenting regarding PR being marked as stale

@finos-admin finos-admin removed the Stale label Mar 5, 2025
@finos-admin
Copy link
Member

This PR is stale because it has been open for 30 days with no activity. Please remove stale label or add any comment to keep this open. Otherwise this will be closed in 5 days.

@finos-admin
Copy link
Member

This PR was closed because it has been inactive for 35 days. Please re-open if this PR is still relevant.

@finos-admin finos-admin closed this Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants