Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Huddle Landing page using Grid, Flex and Media Queries

Tharun Raj•1,330
@Code-Beaker
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?

Completed it and learned how to google for things that you find difficult. That's all :)

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

I didn't know how to get the rounded borders around the icons. So did a bit of Googling and Luckily, Stack Overflow helped me solve it.

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

I'm not really confident about its responsiveness. It might not be perfect for bigger displays because it is my first time trying mobile-first workflow completely.

I would like to know if I did well with the CSS. Thank you!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • John•410
    @MiyaoCat
    Posted over 1 year ago

    You have <main class='main'>. I think that's redundant. You'll only have one <main> element so you don't necessarily need to give it a class. If you do, maybe make it more descriptive of the element.

    The site only covers the top half of the screen when viewed on desktop. To fill out the page so the content covers the entire height of the screen you could do main { display: flex; flex-direction: column; } then header { flex-grow: 1}

    You have most of the content in the <div='header'>. You can use the official <header> tag for the logo and have the meat of the content in <main>. Then put the social icons in the <footer>.

    Otherwise, looks great!

    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