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

Mobile-first approach using CSS Grid and Flexbox, Loopstudios

Teri Eyenike•20
@Terieyenike
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Your positive feedback and criticism are highly welcomed.

Do you like the overall look and feel of the Loopstudios landing page and how can I improve on the project if you found something missing?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    The Burrito Doggie•1,260
    @BurritoDoggie
    Posted over 4 years ago

    Hello Terieyenike,

    I love it! It is super nice! Especially because of the hamburger menu. I absolutely Love them. And yours is even cooler with the transactions and the way it covers the rest of the page is also cool. Something that makes this project special is that the hamburger menu follows you. Another special thing that I like is when you press the buttons or icons at the bottom of the web page they make you scroll back up instead of teleporting you there.

    Keep Coding!

                           (@@)
                            \__/
    
  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hey there, Teri Eyenike! 👋

    Congratulations on completing your first Frontend Mentor challenge! 🎉 Nice effort on this one! 👏 I like the smooth transition of the mobile menu and the mobile menu icon! 👍

    I suggest,

    • Darkening the hero image (such as by using the linear-gradient function and the background property) so that the content inside it stands out more against the background (as in the original design).
    • Making sure all of the navigation links in the footer of the page are clickable (I think some of them seem to be covered up by the div.nav__row--header in the desktop layout).

    Keep coding (and happy coding, too)! 😁

  • Chris-Ann C.•300
    @cdc2021
    Posted over 4 years ago

    Great job on this project! Looks and feels good. One thing your burger menu disappears when scrolling so maybe think about the colour scheme as it dissolves into the white background.

    Haappy coding !

  • Teri Eyenike•20
    @Terieyenike
    Posted over 4 years ago

    I had the same thought in my mind. I would definitely work on refining the whole page and make it better in the subsequent iteration. Thanks

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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