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

Huddle Landing Page - HTML/CSS

P
Julie•150
@jclegg31
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


Had a tough time with the background lining up and the size of the desktop version overall. Not sure how to build without the figma files, it's just really a guess? Do you all have the same struggles? I think it looks ok but felt a little wobbly building it vs the component challenges.

Would love any feedback or suggestions. Thanks!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Divine Ugorji•350
    @DivineUgorji
    Posted over 1 year ago

    Hello, @jclegg31 this challenge is a little tricky even though it looks simple, and congratulations on completing it 🙌

    I can relate to all the struggles you mentioned on a personal level 😊 and it can be overwhelming at times, which is part of what informed my decision to get the premium plan and get the Figma files for the challenges. Even at that, it takes a lot to make pixel-perfect designs.

    You can check out this Chrome extension and learn how to use it if you are very much interested in pixel perfection.

    From what I can see, you are doing absolutely well 👍

    • Your solution to this project is nice and thoughtfully implemented ✅
    • Your solution is responsive across multiple screen sizes
    • Your code is semantic, well-structured, and readable.

    Keep up the good work, and may the force be with you.

    All the best, and Happy coding 🙏

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