Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

loopstudios-landing-page

accessibility, react, react-testing-library, tailwind-css, airtable
Yusuf•170
@whalay
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


i find the process of designing the site so fun and interesting

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Wendy•2,150
    @wendyhamel
    Posted 8 months ago

    Hi, nice to see you try this challenge.

    I noticed a few points you could improve.

    Match to the design

    • In the design the hero image has a subtile darker overlay
    • The fonts in your project are not a match to the design in some places: header menu and the body text)
    • The colors in your project are not a match to the design in some places: (active indicator line under the header navigation, body text)
    • The padding and margin is different from the design: (mostly padding and margin around the sections)

    Semantic HTML

    • I do not see a <main> tag
    • I noticed a lot of <div>'s. There are many more semantic html elements you can use. Try the use of <section> or <article> elements. You can read about it on MDN for example.

    Responsive You did a good job here for the mobile layout. But you might want to tweek some in-between states and the larger screens. There is some content overlapping (body text overlaps the button) or cramped together (header logo and menu) on some in-between sizes. If you look at your project on a larger screen, the site kind of falls apart because there is a lot of space between. (the body text stretches out a lot, the button gets very far away to the right from the grid that stays on the left) You could contain the width the content is allowed to take and center it, to make it all look good on a greater veriety of screen sizes.

    I hope this will help you.

    Happy coding!

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