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

Loopstudios landing page

Bunchydo•640
@Bunchydo
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'm proud of how the overall design of the project came together. It was challenging to balance the layout, responsiveness, and interactivity, but I feel the outcome is visually appealing and functional across different devices.

I was able to implement a flexible grid system for the "creation section," which adapts well to both desktop and mobile views, allowing for smooth transitions between different screen sizes.

The hover effects and overlays were a nice touch, improving the user experience by adding interactivity to the design.

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

I would better structure my CSS by separating the layout, styles, and media queries into different files or sections for better organization.

I would spend more time refining the mobile version's performance, making sure images load correctly in a way that doesn't slow down the site.

I would also take more time to optimize the use of flexbox and grid. In the future, I would attempt to avoid relying too much on fixed widths and heights for responsive elements.

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

One of the biggest challenges was dealing with the responsiveness of the grid layout. Initially, the grid didn't behave as expected when switching from desktop to mobile views. Items weren't stacking as they should, and there were issues with elements not resizing correctly.

Another issue was trying to make the hover effects and background overlays work seamlessly across different screen sizes. Ensuring the visual effects appeared correctly on both mobile and desktop required several adjustments and testing.

Managing the content property and pseudo-elements correctly was tricky, as I initially tried to apply content to the main elements instead of pseudo-elements, which led to confusion.

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 Bunchydo'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

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner
  • Use cases

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