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

Frontend Mentor | Loopstudios landing page

Moundjid Machghour•490
@PxMach
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

Any suggestions on how I can improve are welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chamu•13,860
    @ChamuMutezva
    Posted 2 months ago

    Hi Moundjid Machghour

    Here are some of the issues that you need to look at:

    • first things first, you need to get your HTML right. Among other things, there is duplication of code where you have HTML for Mobile and then HTML for desktop. Probably that can be done in very complex layouts( I cannot think of a case scenario where you would need to do that). You may need to practice more on your CSS.
    • always use semantic elements - elements that have been designed for a specific purpose. In one example like the button that toggle the mobile menu , well , it has to be a button. But in this case you have used images (icon-close and icon-hamburger). Images are not meant for interactive purposes - that is an image can not have click events. You can wrap around the image with a button as the image is just a decorative item.
    • the alt value for an image should carry the message that is carried by the image . If the image is decorative then it should just be alt="" , words such as image, picture, logo etc should not be included in the alt value .
    • the CSS too has issues which are listed below:
    • font sizes should not be in px but preferably use rems.
    • A lot of elements have fixed sizes which will make the site unresponsive

    There is definately a need to start with a smaller challenge and cement the basics. It will be easier to guide you on a smaller challenge fo that it will be helpfull in your future projects.

    Good lucky

    Marked as helpful
  • Getahune Alemayhu•100
    @getishe
    Posted 2 months ago

    Great landing page! Make it responsive.

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.

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