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

Huddle landing page with a single introductory section challenge hub

Dev Rathore•2,540
@GitHub-dev12345
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


Finally i complete my challenge and i Update my project using SASS/SCSS Wrap all the CSS Code into SCSS Code 😎😊, and then upgrade my Projects. Best Way to learn new technologies update your projects and used new technologies in your projects and time to time update the projects. Then Your skills improved 😊😊 in this process

#html #SCSS #SASS #frontenddeveloper.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted over 3 years ago

    Hi

    This css is not good any more - you've nested selectors very deeply, which is extremely problematic once it's a real project. When using scss your resulting css should look exactly how you would have written it from scratch. You would not write css like this. Remove all the nesting and use single class selectors just like you would if you were writing nice clean low specificity css

    Additionally, your code is.longer and less performant because you're using max width media queries. Work mobile first and use min width media queries instead

    Good luck

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted over 3 years ago

    Hi there! 👋

    Congratulations on improving this solution! 🎉

    You have received incredible feedback from @grace-snow. I would recommend applying all the feedback that she has given to you before doing another challenge.

    Some feedback from me:

    • Accessibility
      • Usually, the logo is wrapped by an anchor tag that will navigate the user to the home page (href="/").
      • Don't use br elements for presentational purposes. Read what MDN documentation says about it.
      • For any decorative images, each img tag should have empty alt="" and aria-hidden="true" attributes to make all web assistive technologies such as screen reader ignore those images. In this case, the illustration is decorative only.
      • Create a custom :focus-visible styling to any interactive elements (button, links, input, textarea). This will make the users can navigate this website using keyboard (by using Tab key) easily.
    • Styling
      • What is the purpose of doing this? I would recommend removing it if you have no reason.
    body footer {
      /* In footer tag attribution scss code */
    }
    
    • On 1280px width, the layout is still in a mobile layout and the illustration looks so big.
    • The register button has a very dark box shadow.
    • Each social media icon should be white and have a white circle border.
    • Best Practice (Recommended)
      • I would also recommend writing the styling using the mobile-first approach. It often leads to shorter and better performance code. As a result, mobile users will no longer be required to process all of the desktop styles.
      • Don't nest selectors too much! The stylesheet has a high level of specificity at the moment, which will make it difficult to maintain, especially on larger projects.

    That's it! I hope this information is useful! 😁

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

Oops! 😬

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

Log in with GitHub