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

Meet Landing Page with Sass

sass/scss
P
Leonard Cohen•180
@lenny131
A solution to the Meet landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Michael•180
    @Networksentinel
    Posted about 1 month ago

    Hi Leonard!

    Your solution looks awesome, and the responsiveness is totally on point—really great job!

    I especially liked how you used @media queries inside your @mixins for text presets. It honestly never occurred to me that I could do that 😄.

    I went with a different approach and used clamp() for font sizing, so it adapts based on screen width. Something like this:

    $font-size-xl: clamp(2.5rem, 4.1666vw + 1rem, 4rem); // desktop: 64px, tablet: 48px, mobile: 40px
    

    I think my version works well for typography when only one or two properties need to adjust, but your method looks much more scalable—definitely something I’ll keep in mind for larger projects. So thanks for the inspiration!

    Also, your code is really well-organized and easy to read—nice job there too.

    Just two small suggestions I'd like to share:

    1. Modular SCSS – Right now, everything is in one big file. Even though your code is spaced out nicely, it can still be a bit much to scroll through. You’ve already used presets.scss, so you could break the rest down into partials like:

    • hero.scss
    • main-content.scss
    • footer.scss

    It’s a great way to separate concerns and make things more maintainable.

    2. SCSS Imports Tip – For smaller projects, you can import SCSS files like this: @use "presets" as *; That way, you don’t have to reference the file name every time and can just do something like: @include text-preset-4;

    Anyway, I hope some of this was helpful! And if not (since you posted this a month ago 😄), at least I learned something new from your code—so thanks again, and keep up the great work!

    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