Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

flexbox huddle landing page

Adam M•550
@AdamMzkr
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


Hi this is my next solution after short break:) It's responsive and quite look like the design. I used simple css and flexbox, for icons i used the "font awesome kit".

If you see some thing to fix or improve in this website I will really appreciate.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi Adam, welcome back! 😊 I think this was well put together, and the two suggestions I have are, on a wide screen (which is what I'm viewing it with), the contents look really stretched out. You can try using a container in both the header and main sections to keep things from stretching past a certain width. This is also the suggestion I gave someone else earlier regarding this challenge, and this is the code I gave:

    HTML:
    
    <header>
       <div class="container">
        // rest of your content
       </div>
    </header>
    <main>
       <div class="container">
        // rest of your content
       </div>
    </main>
    
    CSS:
    .container {
       max-width: 1440px; // this is just a suggested value, do experiment!
    }
    

    The other suggestion also concerns screen sizes and breakpoints; at around the 1000 and 900px browser width, the text starts to get really squished, and I can also see the image being a bit distorted while it pushes the text off the screen. I also see the scroll bar, which probably is another sign that things are being pushed out. For the img, try adding object-fit: contain firstly, and then to handle the flexbox columns, you can leverage flexbox's flex property on the children:

    // feel free to experiment with these values!
    
    .illustration {
       flex: 1 0 50%;
       width: min(50%, 40rem);
       object-fit: contain;
    }
    .content {
       flex: 1 1 50%; 
    }
    

    You may also want to decrease some of the padding you have on the sides. Hope you have a chance to test this out on a big screen first also, and then maybe you'd see what I'm trying to describe here. Anyway, other than that, great work!

    Marked as helpful
  • Adam M•550
    @AdamMzkr
    Posted almost 3 years ago

    Thank' s a loot for your comment. I know about breakpoints but i don't focus on it. I want to finish all newbie level challenges.( I FINISHED 17 chellenges) and in the next level I will more focus on all aspect of design. But your comment it's really important for me, because you are experience user.👋. I am still amateur 😉.

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
Frontend Mentor logo

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

Frontend Mentor

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub