Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Responsive landing page using CSS flexbox

Alicia Laborda•20
@alicialaborda
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


I am still learning about media queries, so any advice on that would be so welcome. Other problem I had was that some components would lay over others, I don't know why...

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • bunee•2,020
    @buneeIsSlo
    Posted over 2 years ago

    Hey! @alicialaborda, Congratulations on completing your first challenge here. You've put some solid effort into this one!

    To solve your issues, I recommend you take the "Conquering responsive layouts" course(free) by Kevin Powell. I learned a lot about responsive layouts by going through this course and I'm sure you will too. However, if you don't have the time to go through it, this video by him should help too.

    Hope this helps :)

  • Absorberend•390
    @Absorberend
    Posted over 2 years ago

    Hey!

    A tip: you should look up "mobile first design" ( https://medium.com/@Vincentxia77/what-is-mobile-first-design-why-its-important-how-to-make-it-7d3cf2e29d00 ) . I noticed that the media query is for mobile (smaller resolutions) and the "normal css" is for the pc version. It's easier if you start mobile first and work your way up the resolutions.

    I added a max-width of 350px to the .hero .text-section class for the big resolution. This makes it so that the text doesn't spread out all over the screen (on widescreen like I have). I also added the following media query to make the design more "fluent".

    @media screen and (max-width: 900px) {
    
        .mockup{
          width: 500px;
        }
    
      }
    

    Als to the mobile version I added the following code to the .hero class: min-height: 600px;

    and to the .header class: min-height: 50px;

    By giving a min-height to these classes you make it so they can't shrink below certain px, which means no overlap!

    Hope this helps!

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

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