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

Huddle landing page - SASS and mobile first approach

Traz Davids•50
@Royal-tea
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


Any feedback welcome ! First time using SASS and tried a mobile first approach so any feedback on how to clean up anything related to that is also appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, awesome work on this one. Layout in desktop looks great, it is responsive and the mobile state looks great as well.

    Some suggestions would be:

    • Don't style the html element. Typically, you only set like box-sizing font-size on the html but not directly style it, move those to the body tag.
    • Avoid using height: 100vh as this limits the element's height based on the remaining viewport/screen's height. It is set on your html, actually remove this one since your body tag has a min-height.
    • The a tag that wraps the website-logo should either have aria-label or an screen-reader only element inside it. The value will be where the link would take the user. Since website logo usually points to homepage, use:
    <a href="/" aria-label="homepage">
      <img src="images/logo.svg" alt="Huddle "> # remove the word "logo" use huddle only
    </a>
    

    You do this method if there are no text-content inside the element. As you can see, lose the word "logo", avoid adding words that relates to "graphic" in the alt attribute.

    • Always have a main element to wrap the main content of the page. A typical structure would look like:
    <header />
    <main />
    <footer />
    

    This way, all elements are inside landmark element.

    • The social medias could be inside ul element since those are "list" of links.
    • Each a tag that wraps the social media should be using the method I mentioned above. The value will be where the link would take the user, on facebook, of course use the value facebook.
    • Each img on the social media should be hidden since they are only decoration so use alt="" and add aria-hidden="true" attribute on it as well.

    Aside from those, great work again on this one.

    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.

Oops! 😬

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

Log in with GitHub