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

Huddle landing page with alternating feature blocks

Abhijit Morye•120
@abhijitmorye
A solution to the Huddle landing page with alternating feature blocks challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello all,

I have completed this huddle landing page challenge..any feedback to improve it further are most welcome.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ramsay Sewell•585
    @ramsaysewell
    Posted almost 5 years ago

    Hi Abhijit,

    Great job on this solution, it looks really good and responsive.

    Here are a few tips for how we can make this look closer to the design:

    • For the .nav-logo image, I would wrap this in it's own <div> instead of using the <img> tag as a Flex Item. This will help make sure that the <img> retains it's aspect ratio and isn't stretched because of Flexbox.
    • The .intro-header-box-flex can have a max-width set of around 1200px and then margin: 0 auto;. This will make sure you keep the background stretched to the edges and the content is restricted to it's width, let me know if this works.
    • For the footer social images, these were given in your /images folder and so you should be able to insert the SVG into your HTML document, allowing you to change the fill property. Check out CSS-Tricks for help on styling SVGs.

    I hope these tips are useful and none of it confuses you.

    Let me know if there's anything I can help with.

    Ramsay

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