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

Huddle Landing Page Single Section with HTML and CSS

accessibility
Kauã de Souza•260
@SouzaSantosK
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


This challenge was quite difficult, probably because it was the first landing page that I submit here. It worked smoothly on the mobile layout, but when it came to adapting the page for the desktop version, the responsiveness was terrible. After several attempts, I managed to achieve a result that I hope you like. Do you have any tips on creating landing pages, or anything that could make the challenge easier? Feel free to comment down below. Happy coding😃

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • BrunoMoleta•700
    @brunomoleta
    Posted about 2 years ago

    Hey Kauã, I'm also from Brazil (Curitiba/PR).

    When you write in English next time, you can rely on Grammarly to correct your spelling errors ;)

    About the social media links on the bottom, I saw you used the <i> for the social media links:

          <footer>
            <div class="socials">
              <i class="fa-brands fa-facebook-f"></i>
              <i class="fa-brands fa-twitter"></i>
              <i class="fa-brands fa-instagram"></i>
            </div>
          </footer>
    

    Though, according to MDN, <i> it stands for The Idiomatic Text element. A french words in a text written in Portuguese, for example.

    And since these are hyperlinks to a page elsewhere on the web, I would recommend: <a> wrapped in a <li> inside an <ul<(instead of <div>).

    I also included svg to display the icons. The following snippet of code is what I did:

    <footer>
            <ul>
              <li>
                <a
                  href="https://www.facebook.com/"
                  target="_blank"
                  class="a-social-media"
                  aria-label=" Facebook Icon."
                >
                  <svg
                    id="facebook"
                  </svg>
                </a>
              </li>
              <li class="icon">
                <a
                  aria-label="Instagram Icon."
                  href="https://www.instagram.com/"
                  target="_blank"
                  class="a-social-media"
                >
                  <svg>
                    <path>
                  </svg>
                </a>
              </li>
              <li>
                <a
                  aria-label=" Twitter Icon."
                  href="https://twitter.com/"
                  target="_blank"
                  class="a-social-media"
                >
                  <svg>
                    <path>
                  </svg>
                </a>
              </li>
            </ul>
    </footer>
    
    

    Further, the aria-label inside the <a> is for the screen-reader accessibility, something you said on Github that you would like to improve.

    And hey, you've worked hard congrats on that.

    I see you have already done quite a few challenges around here. I suggest that you do a few project reviews for other folks. A person can learn a lot by giving feedback on someone else's code.

    Boa sorte :)

    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 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