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

Loopstudios Landing Page SCSS, BEM methodology, Grid

Aljon De Lumen•100
@aljonnnnn
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback is appreciated =)

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    The Burrito Doggie•1,260
    @BurritoDoggie
    Posted over 4 years ago

    Hello Alimonnnn,

    Excellent work! I love yours for a special reason. Many people also have the effect that when your mouse hovers over the words at the top, a line appears at the bottom. Or when it hovers over the pictures they fade slightly. But yours is special. It's different. Yours actually 'fades' it in for the line at the bottom. And fades out for the pictures. When I see other peoples solution it just appears rather than fading in or out like yours does . That's what I like about yours.

    Keep Coding!

                                        (@@)
                                         \__/
    
  • Elise Rousseau•685
    @SarahHenriette
    Posted over 4 years ago

    Hi Aljon De Lumen 🙂

    The realization of this project is really good. The responsive is great and I really like the effect you put on the responsive menu 👍

    Maybe just put:

    • the "cursor: pointer" on the creations of "our creation"
    • the hover that you put on the links of the nav puts it back on the links of the footer

    Good continuation

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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