Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 8 months ago

huddle Landing Page using css flex

pure-css
Yahaya Auwalu•80
@yauwalu84
A solution to the Huddle landing page with a single introductory section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I’m proud of the following: How the layout adapts seamlessly from mobile to desktop. Starting with a mobile-first approach helped me structure the CSS in a scalable way.

The subtle hover effects on the social media icons and the “Register” button add interactivity and polish — small details that make a difference.

Organising colours using root variables made the styling process more efficient and reusable.

What challenges did you encounter, and how did you overcome them?

Getting the layout to look good on both mobile and desktop screens was initially challenging, particularly with image scaling and spacing. I started with a mobile-first approach and then used media queries to adjust layout, spacing, and font sizes for larger screens. Testing the design in the browser's responsive mode was very helpful.

Some elements, such as the social icons and description section, were not aligning properly within the flex container. I utilised Flexbox properties, such as justify-content and align-items, more effectively and ensured that I defined proper widths for containers. Adding margin and adjusting the text-align property helped fine-tune the layout.

What specific areas of your project would you like help with?

Are there any improvements I can make to ensure the site is more accessible, particularly for users with screen readers and those who use keyboard navigation?

While I’ve implemented a mobile-first design and added media queries, I would love feedback on how to further improve the responsiveness.

Is my use of semantic tags (main, footer, etc.) appropriate?

Should I restructure parts of the content to improve readability and semantics?

Does the way I’ve structured the CSS make sense and follow best practices?

Are there any suggestions for cleaning up or refactoring the style rules, particularly within the media query section?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Yahaya Auwalu's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner
  • Use cases

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License