Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Loopstudios landing page using SCSS and webpack [GRID + FLEX]

bem, sass/scss, webpack, accessibility
Aadvik•1,250
@Aadv1k
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Would love to get any input on the mid-section with the tricky overlay. I tried several "hacks" such as background-image, flex with relative positioning and some other solution, but I ended up just going with the position absolute.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shashree Samuel•8,860
    @shashreesamuel
    Posted over 3 years ago

    Hey Aadv1k good job completing this y. Keep up the good work

    Your solution looks great however in comparison however I have some suggestions

    • in comparison with the design the header section of your website is a bit misaligned.

    • The section with the cars that states "The leaders in VR" needs some margin from the top. You can achieve this using the margin-top property.

    • The section with the creations needs some margin from the top in addition the imagesi itself needs to be scaled up a little bit. You can achieve this using transform: scale()

    • Your footer social icons just needs some margin from the right using the margin-right property.

    In terms of your accessibility issues simply wrap all your content between <main> tags to get rid of all the issues

    In terms of your accessibility issues, this article should help below

    https://www.geeksforgeeks.org/minification-of-css-files/

    I hope it helps

    Cheers Happy coding 👍

    Marked as helpful
  • Aadvik•1,250
    @Aadv1k
    Posted over 3 years ago

    Alright WOW there are a lot of accessibility issues with this one! don't know why it is marking minified css generated by the sass compiler as a "error", the sass compiler would have told at compile time.

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