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

Huddle landing page with flexbox

Andrew Talle•10
@ogAndrew
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


Having trouble getting this to work on mobile. Some advice on how to get started for mobile would be welcomed.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Web Frog•1,840
    @MasterDev333
    Posted over 4 years ago

    Hi, @Andrew. Great work. You may make mobile responsive following the above comments. It would be great if you add transitions for buttons to make it more smooth. transition: all .3s ease-in-out; Hope it helps :)

  • Grace•32,130
    @grace-snow
    Posted over 4 years ago

    Hi Andrew, you need to use a media query to make this mobile responsive.

    In future challenges you'll find layouts a lot easier if you do mobile styles/layout first and then put the changes needed for larger screen layouts inside a min-width media query.

    But as you've already done the desktop version of this one, you can add a max-width media query instead.

    Top tips are to let block items be block, so you shouldn't need widths and heights on everything. Use max-widths if you need to, and simply add whatever styles you need to make the content stack on mobile.

    Good luck

  • Vytas•435
    @vytkuklys
    Posted over 4 years ago

    Hi Andrew, Good job at desktop version. As for mobile version there is an important aspect to keep in mind that would be useful for you.

    That aspect is media queries which is basically a css technique that allows you to style a page at different widths. The important trick to remember here is that it is always easier to start with a styling for mobile version first (narrower width) and build up from there (other way around could prove an interesting and educational challenge, too, yet it is typically not as time efficient).

    Hope this helps, best of luck!

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

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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