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

pettik--loopstudios-landing-page

pettik•600
@pettik
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 am most proud of successfully implementing the CSS Grid and Flexbox layout, ensuring a fully responsive design for various screen sizes. The hover effects on the product images turned out great, adding a nice interactive touch. If I were to do it again, I would improve the mobile navigation menu to make it smoother and enhance accessibility. Additionally, I would optimize the font sizes and spacing more carefully for smaller screens. Lastly, I might experiment with CSS animations to make the page more dynamic.

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

One of the biggest challenges was aligning the section's content box properly on different screen sizes. Initially, it overlapped incorrectly, but I solved this by adjusting relative and absolute positioning and tweaking media queries. Another challenge was ensuring the navigation bar transition works smoothly on mobile—after struggling with the display toggle, I refined it by adjusting CSS display properties and JavaScript event listeners. Finally, handling image scaling on hover required fine-tuning the property to prevent layout shifts.transform

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

I would appreciate feedback on mobile responsiveness, especially how the banner heading scales on smaller devices. Additionally, I am unsure if my CSS custom properties ( variables) are structured efficiently—are there better ways to manage them? Finally, I’d love to hear suggestions on optimizing image loading performance, particularly for the background and product images, without compromising quality.:root

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on pettik's solution.

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.