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

Huddle Landing Page using HTML, Sass

Siddhesh Kamble•350
@Sk7867
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 is my first time using Sass instead of CSS3. I enjoyed using it and will continue to do so. Any suggestions or improvements are welcome.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted about 4 years ago

    Hey, Siddhesh Kamble! 👋

    Nice work on this challenge! 🙌 Your solution looks pretty good! 😀 Also, kudos for trying out Sass (it is very nice and makes writing CSS easier). 👍

    I'd just like to suggest adding background-size: cover to the background image so that it fills the entire area of the screen but doesn't get stretched or squeezed when the size of the screen changes. 😉

    You could also try allowing the width of the image to be determined by the size of the screen in the mobile layout (by adding width: 100% to the image or its container or something) so that you don't have to use a media query to change the size of the image twice for the mobile layout. 🙂

    Keep coding (and happy coding, too)! 😁

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted about 4 years ago

    👋Hi Siddhesh Kamble! My name is Vanza!

    One thing on your style.scss, in my opinion, next time you can just do:

    background: url(../images/bg-mobile.svg), $violet;
    

    Rather than this:

    background: url(./../images/bg-mobile.svg), $violet;
    

    Because in my opinion, it's just kinda redundant, since it's just doing the same thing.

    That's it! Hopefully this little tip may useful for you!

    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

Oops! 😬

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

Log in with GitHub