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

Loopstudios with Sass, JS, Parcel

Fluffy Kas•7,675
@FluffyKas
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey guys,

This was a trickier challenge than it looked like. Much trickier, actually. I know it's not a pixel perfect copy of the design but that even intentional in some places ^^ Please feel free to roast me, I'm sure I made some errors!

Have a great day!

edit: I couldn't figure out what's up with the fonts! They just look different than shown on the design. Any idea why?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted over 3 years ago

    Not sure about anything font related, but your solution looks good on desktop.

    • Give your solution a maximum width of 1440px to prevent it from stretching and becoming too wide on large screens.
    • On our creations I think it would have been better to go from 4 rows to 3 rows, because when you reach the first breakpoint and it switches to 2 rows it has a lot of empty space on the sides and it doesn't look good.
    • When you switch to desktop while the mobile menu is still active it gets carried over and does not get dismissed.

    Keep coding👍.

    Marked as helpful
  • SREEHARI P V•300
    @sreehariv-code
    Posted over 1 year ago

    I have a doubt. How are you switching the images in the cards in Our Creations section while switching between media queries ?

  • Joyal James•265
    @silkcoder
    Posted over 3 years ago

    Nice work.

  • Marlon Passos•920
    @MarlonPassos-git
    Posted over 3 years ago

    Hi, very nice at your job. I really liked the animation of the button on the hamburger menu, the transition between the elements was very smooth, nice. Now what I think could improve is:

    • On your h1 to position the element instead of using the margin I would use the following:
    .header-title {
        display: flex;
        justify-content: flex-start;
        align-items: center;
    }
    

    in my view it's not better to use gid or flex to position something instead of the margin itself. Then in each @media you would improve with flex to align instead of changing the margin

    • In the footer you could have placed the navigation items inside a <nav> tag like you did in the header

    • social-media items could be inside a <ul> instead of the <div>

    • I think that the footer breaks to a column very early, for me it should only stay that way when it reaches the size of a cell phone, in the tablet version I would place each of the content blocks one above the other, see https://prnt. sc/1tchs14. I've made some grotty changes to try and show how cool I think it would look in the tablet version, see https://prnt.sc/1tci55v

    • I particularly liked this "smoke" effect that you added to the photos, who knows if when the person hovers over it, this is a lightening in the photo, it would be really cool

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

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