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

Responsive Landing page using CSS Flexbox

accessibility, bem, bootstrap, less
Jaybae•20
@Jenny3094
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 found making my texts fit into a box of a specified width. I also found it difficult to adjust my queries without having them clash.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kitty10206•100
    @Kitty10206
    Posted almost 3 years ago

    Hi Jaybae!

    I just had a quick look at your CSS and it looks like you did the same thing I did before. Your media queries are only covering 0 to 375px and 1440px+. I know it says in the challenge that the examples are 375px for mobile and 1440px for desktop. You started by setting up the mobile-layout, right? This means you already coded for the max-width of 375px, and you don't actually need a media query for this. Then you have to decide at what width the desktop design starts, and set up a media query for this. For example, a min-width of 700px (definitely experiment, some designs work better in higher widths than others). Then, every screen bigger than that would see your desktop design. You don't necessarily have to set both and min- and a max-width unless you also want a special tablet version. But if you put a media query at about 700px, it will make your transition work.

    Your media queries: @media screen and (min-width: 1440px) @media screen and (max-width: 375px)

    An example that might work (you would put this query where your current desktop query is): @media screen and (min-width: 700px)

    I hope this helps! Kitty :)

    Marked as helpful

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