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

Loopstudios - Pixel Perfect | HTML | SCSS | JS | GSAP

Akash Sharma•170
@aakash19090
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello folks! 👋

  • Its an almost Pixel Perfect landing page with beautiful animations with the help of GSAP animation library.

  • Header is resized & fixed on top on scroll with smooth transitions to provide better usability & UI.

  • The "Creations" cards section have & glassmorphism tilt effect on hover.

Is there anything else that could be done better to provide better UI experience ? A **feedback ** or any suggestion for this awesome effort would be appreciated ! 😊

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Agata Liberska•4,075
    @AgataLiberska
    Posted about 4 years ago

    Hi @aakash19090 :) I think we watched the same GSAP video! The load animations look great, well done!

    However, I wouldn't personally animate the whole page, just some elements to make it look interesting. I think the animation in the hero section is fantastic, but I get a bit dizzy scrolling down from there (this is of course my subjective opinion - and if you want to keep the animation throughout, it may be a good idea to look into reduced motion media queries

    I would also add some hover styles to links in the footer, and correct the social media links - when they scale up on hover, they overflow the container and get cut off a little bit. Adding focus styles is a must, too - if you remove the default outline, you need to provide a good alternative (an underline would look good I think).

    Overall your solution is very impressive I think :)

  • Roc Tanweer•2,500
    @RocTanweer
    Posted about 4 years ago

    Arey bhai kya kam liya hai aapne, WAHH!! happy coding bhai jan..!

  • Aw•530
    @kido5285
    Posted about 4 years ago

    wow this looks 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 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

Oops! 😬

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

Log in with GitHub