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

Loopstudios page using BEM an Scss

accessibility, sass/scss, bem
Sylvain Web•380
@SylvainPS78
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?
  • Responsiveness of the page (even if not perfect yet)
  • First project using Live Sass Compiler
What specific areas of your project would you like help with?

Any comment will be welcomed !

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•9,250
    @MarziaJalili
    Posted 4 months ago

    Amazing job!

    Some tiny areas you can amend:

    • To make the change of the links (adding the bottom border), you can use the transition property.
    transition: border 0.3s;
    

    This will make sure the border will be added after 300 milliseconds, which makes it look even better.

    • The same goes with the See All button:
    transition: background-color 0.5s, color 0.5s;
    
    • Also, after minimizing the screen and then going back to the desktop mode the hamburger button is still there if not maximized manually and just by click the maximize button of the browser.

    To fix that, completely remove it from the DOM for the larger screen sizes:

    @media (min-width: 750px) {
      .open-navbar-button {
         display: none;
      }
    }
    

    You have put your head down on it, GREAT JOB!

    😎😎😎

    Marked as helpful
  • P
    Andrey•4,600
    @dar-ju
    Posted 4 months ago

    Hi SylvainPS78!

    Your work is great! Very close to the original. Hovers work well, mobile menu is great.

    SCSS

    I see you used SCSS, but you applied it not quite correctly - like regular css. BEM together with SCSS should give a tree structure. Let's take .card in your case and all elements of this component should be inside the tree.

    Here is an example of SCSS implementation:

    .card {
      max-width: 100%;
      padding:0 5vw;
      position: relative;
      &__img {
        max-width: 100%;
        min-width: 100%;
        height: auto;
        object-fit: cover;
      }
    }
    

    There is a main - .card and its components inside. The & - symbol replaces the parent name.

    BEM

    There are some errors in BEM. For example, .main__hero__img

    Imagine that there is a section that we can reuse somewhere else in the project, this is the first part of BEM - a block. A block consists of elements. A modifier is if there are similar elements, but differing in font color, background or something else.

    In this case, the block is hero, the img element, there is no modifier. Total: .hero__img.

    The next block is .card and so on...

    With the correct use of BEM and SCSS, your work will become easy and pleasant.

    Other

    • Before the release, always check the code in the validator, there are several errors that need to be fixed.
    • Keyboard accessibility works except for social media buttons. They also do not have a hover.

    Otherwise, everything is great, good luck with your development!

    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

Oops! 😬

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

Log in with GitHub