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

React TS Loopstudios Landing Page

typescript, react
Karen Lourenço•380
@KarenMascarenhasLourenco
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The handleClick on the Header component is working on localhost but stopped when I deployed.

Is my code understandable?

Did I use the semantic HTML tags correctly, should I add more or less?

In what areas of my code can I improve on?

All feedback is greatly appreciate. It helps me to improve as a frontend developer. Thanks!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Riki Wendri•1,380
    @F4YY
    Posted about 2 years ago

    Hi Karen Lourenço,

    Congratulations on successfully completing the challenge. Nicely done.

    Yes there is something about handleClick, I'm also still figuring it out how to solve it. However, there are few recommendations to further optimize and be more similar to the design if we look in more detail.

    • Creation item h3 color should turn black when hovering.
    • It's a custom underline of list items when hovering header/footer navbar. because the underline width is smaller than the text word. You might replace border-bottom with code such like:
       :hover{
           ::after{
              content:"";
              margin-top: 30px;
              heights: 2px;
              width: 20%;
              background: var(--White);
              position: absolute;
              left: 25%;
              top: 0;
           }
       }
    

    Hope all that could be Helpful. Keep happy coding..

    Marked as helpful

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