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

Alternative Huddle landing page. Using flexbox, grid and CSS position

Hassia Issah•50,410
@Hassiai
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


Feedbacks are welcome !!!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Precious Nkwor•440
    @Jeen-Presh
    Posted over 2 years ago

    Hello Hassia, congratulations on completing the fem challenge.

    Some tips to help improve your project

    • best naming convention for classes and id's, is to separate the names using "-" instead of "_"

    more info naming conventions

    • you should use the address element to wrap the address section instead of article

    more info address element MDN link

    • it's not best practice to use an article element inside a footer. wrap them with divs instead

    Happy coding. if you found this helpful, make sure to mark as helpful thanks.

  • Mohmed elshaarawy•830
    @MohmedElshaarawy
    Posted over 2 years ago

    Hello Hassia, congratulations on completing the fem challenge.

    Some tips to help improve your project

    best naming convention for classes and id's, is to separate the names using "-" instead of "_" more info naming conventions

    you should use the address element to wrap the address section instead of article more info address element MDN link

    it's not best practice to use an article element inside a footer. wrap them with divs instead Happy coding. if you found this helpful, make sure to mark as helpful thanks.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub