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

Huddle landing page with single introductory section

Aghla Abdo•340
@AghlaAbdo
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


🚀 Another challenge completed on @FrontendMentor! 💪

I'm steadily working my way through the challenges, starting with the easier ones to build a solid foundation. Excited to continue my learning journey and level up my frontend skills.

If you have any feedback or suggestions for improvement, I'd love to hear them! Let's grow together and create amazing web experiences.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted about 2 years ago

    In CSS there's a few really important things to learn too

    1. NEVER write font size in px
    2. Next time, work mobile first. This will be shorter and more performant, especially for mobile devices
    3. Don't use position absolute for the socials. There's really no need. Flex or grid on the parent would do
    4. Rather than using nested element selectors like .text a I recommend placing classes directly on what you want to style. Imagine this is a real site - you would want reusable button styles
    5. Generally consider using px less and leaning on other units like em, rem, ch etc. For example, I think your container will need a max width in rem - zoom right out on a large screen and id expe t everything to get way too wide at the moment. A max width would protect against that, and using rem wouod ensure it works for all users no matter what their font size settings
    Marked as helpful
  • Grace•32,130
    @grace-snow
    Posted about 2 years ago

    Hi

    I recommend you refocus learning on HTML as that's where the main issues are here.

    1. The logo should be in a header and not in a nav. There are no navigation elements in there
    2. What you currently have in a header should be in a main. The header landmark has a role of "banner" that means it's purpose is for repeating content across a whole site (like a logo, often a site navigation)
    3. The logo is really important content. It must have alt that says the same as the logo says
    4. The social links have no accessible names at the moment. They must have text content that communicates the link destination eg Facebook. You can do this with Sr-only text in a span inside the link, a span with a hidden attribute and unique ID inside the link along with aria-labelledby on the link pointing to the ID of that span, or with aria-label.
    5. You probably shouldnt be using inline styles on the social links. Overall I would not recommend using font awesome the way you are using it at the moment. You are importing a HUGE library for the sake of 3 tiny svgs. You can download the svgs you want and this would be much better for performance and more closely ailign with how you'd use font awesome in a real project. It also offers a learning opportunity - Look up how to manage svg colors - you can change their fill in the svg code to be currentColor and use css, or you can inline svg code in the html, add aria-hidden true and focusable false, and they would be controllable by css
    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.

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

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