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

fix: Improve button layout responsiveness on home page #768

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

RosaErick
Copy link
Contributor

I encountered this issue while accessing the Mastodon website on my Samsung S20. The buttons in the hero section were overlapping and breaking the layout, prompting the need for this fix to ensure proper display on mobile devices. The update ensures that the buttons remain side-by-side on mobile devices, with a gap that dynamically adjusts based on screen size.

Changes

  • Applied responsive Tailwind CSS classes to adjust the gap between buttons.
  • Ensured that buttons maintain appropriate spacing and alignment across all screen sizes.
  • Improved the overall responsiveness of the hero section on the home page.

Testing

  • Tested across various screen sizes to ensure the layout remains intact and buttons are properly aligned.
  • Verified that the buttons do not overflow or break the layout, even on smaller screens.

This fix enhances the user experience by maintaining a consistent and visually appealing layout on all devices.

  • Adjusted gap between buttons to gap-4 on mobile and gap-12 on medium/wide screens.
  • Ensured that buttons remain side-by-side without breaking the layout on smaller screens.
  • Added responsive width adjustments to keep buttons aligned and properly spaced across different screen sizes.

before update

imag3e

after

image

@andypiper andypiper self-assigned this Sep 2, 2024
@andypiper andypiper merged commit c007405 into mastodon:main Sep 3, 2024
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.

2 participants