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

Clipboard landing page with scss, flexbox and grid

Gabriel Monsalve•320
@Gabrieldev-web-coder
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi, here with other challenge of this plataform.

In general i want that someone give me tips for improve my sass code.

I do my best trying to make it the closer as possible with the design, i used sass, if someone can show that and say me how i can improve the sass code will be great, and in general best practices also be great.

Any other feedback always is helpful, have a nice day guys <3

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roc Tanweer•2,500
    @RocTanweer
    Posted about 4 years ago

    This is what codercoder at YouTube taught me. Hope this confirms that my help is relevant 🤠

    $breakPoints : (
        'small' : 24rem,
        'medium' : 40rem,
        'large' : 64rem
    );
    
    @mixin responsive($size) {
         $breakPoint : map-get($breakPoints, $size);
         @media(max-width : $breakPoint) {
        @content
    };
    };
    

    Hope it helps(happy coding..!)

  • Roc Tanweer•2,500
    @RocTanweer
    Posted about 4 years ago

    Ah yes about sass....I love it Lol Watch Sass tutorial of 2 hours with a project to understand basics of sass on freecodecamp YouTube channel

    You can also read documentation...it's pretty simple

    Hope it helps

  • Roc Tanweer•2,500
    @RocTanweer
    Posted about 4 years ago

    There are some minor issues but overall great 👌 work really @Ippotech

    Keep coding and happy coding 😉

  • Chris•740
    @chrisbailey85
    Posted about 4 years ago

    I'm only just getting started sass myself but I think as a best practice you shouldn't use capital letters on your class names, it makes it a bit more difficult to read. I also just learnt about something called BEM, which is a set of rules for when writing classes, it looks like you were using it in places but I did only learn about it today so I wasn't 100% sure.

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

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

Oops! 😬

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

Log in with GitHub