Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

HTML CSS SCSS Bem Vanilla Javascript Mobile firts

bem, sass/scss
P
RF13•640
@rf1303
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?

*I'm most proud of having built a fully responsive landing page using modular SCSS, with a design that respects the original mockups in both mobile and desktop versions. I also focused a lot on accessibility, incorporating aria-label attributes, avoiding position: fixed when necessary, and adjusting the tab order.

One of the things I liked the most was working with clamp() and min() to achieve a fluid design without relying exclusively on media queries.

Next time, I would like to better organize the SCSS files from the beginning and apply a clearer naming convention (like pure BEM ). I would also spend more time improving the HTML semantics from the beginning, making sure to use landmarks correctly (<main>, <nav>, <section>, etc.), which was a fix that I implemented in later stages of the project.*

What challenges did you encounter, and how did you overcome them?

One of the main challenges was managing the darkened background of the hero with ::before without covering the header content. Initially, the text appeared behind the filter, but I solved the issue by correctly adjusting the z-index and applying position: relative only to the necessary elements.

I also encountered issues with SCSS modularization using @use and @forward, particularly with missing imports or name conflicts. After reviewing the structure, I ensured that all files were properly connected using namespaces and organizing utilities, variables, and mixins correctly.

It was also challenging to make the mobile menu buttons accessible. I received warnings about buttons without visible labels or aria-label, so I added clear descriptions for screen readers.

In the future, I would spend more time improving HTML semantics from the start, making sure to use landmarks correctly (main, nav, section, etc.). This was a fix that I implemented in the later stages of the project.

What specific areas of your project would you like help with?

El contenido y como estoy ordenndo todo con SCSS y la parte de accessibility

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Temesgen Adane•510
    @temesgen-982
    Posted about 1 month ago

    First of all, the menu looks stunning on smaller devices👌 but you're supposed to align it horizontally on larger devices.
    The other improvement you can consider is the grey background on the main area of the page because it is white (transparent) on the design file.
    Your main.scss file is more than 500 lines, it is unsearchable (you are using & selector), and it may be difficult to look back into it later in time, so consider implementing the SCSS 7 in 1 architecture. Even I don't implement it fully, but it helps.

    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

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