Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Loopstudios Multi-Page Website using Flexbox and Mobile-First strategy

Robert Spatz•120
@rspatz
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 decided to build out this project as a complete multi-page website using a mobile-first approach. I expanded the original Figma design to create the extra pages, using stock images from Unsplash, which I optimized in Affinity Photo 2, and I wrote my own copy for the extra pages. For the Events page, I created a Slideshow with vanilla JS. I also tried using a mobile-first approach, employing media queries for the desktop version. I enjoyed turning the landing page into a complete website, and using my imagination to come up with ideas for each page.

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

This was my first time submitting a website using a mobile-first approach, and I was a little outside of my comfort-zone, but I tested the project using Chrome's web developer tools device simulator, then displaying the live website on my phone and laptop, and making corrections, until I got the results I wanted. Occasionally something in the mobile version took precedence over the widescreen design, and I would have to figure out where the problem was, but I believe everything is working properly now. If anyone sees an issue, please let me know about it!

Finally, I have a problem with the hero image on the landing page. I originally had the image positioned exactly as the figma file had it, but something happened and it no longer displays properly. If anyone can tell from my code what is wrong, I would like to correct the display.

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

If someone can please tell me what is causing the hero image on the landing page to only show a detail, rather than covering the whole background, I appreciate it. I used background-position: center; and background-size: cover; Also, what do you think of my code? I try to write as DRY and clean as I can, and I am always trying to improve. Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Robert Spatz'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

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.