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

Loopstudios landing page (React, TypeScript, Tailwind)

react, tailwind-css, typescript, accessibility
Flavio Gomes•720
@flaviogp
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?

Hi there 👋, I’m Flavio and this is my solution for this challenge. 🚀

🛠️ Built With:

  • ReactJs
  • TypeScript
  • Tailwind

Any suggestions on how I can improve and reduce unnecessary code are welcome!

Thank you. 😊✌️

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Luciano Lima•1,270
    @LucianoDLima
    Posted over 1 year ago

    Opa, salve, Flavio! Sempre bom ver mais BR por aqui! Ficou muito bom o projeto!

    Feedback:

    • Ao invés de h-[100vh] você pode usar h-screen
    • O texto IMMERSIVE EXPERIENCES THAT DELIVER poderia ser um <h1>. É importante que sempre siga o nível correto das headings. Começando sempre pelo 1.
    • Os atributos alt das suas imagens possuem textos genéricos, que dificultam que usuários com tecnologias assistivas (tipo cegos que usam screen readers) saibam do que se trata. É importante adicionar uma boa descrição para imagens como essa. Por exemplo: alt="A man wearing a virtual reality headset, his mouth open in a scream of anticipation as he reaches out as if to grasp something.". A mesma coisa vale para as outras
    • Sobre os links de redes sociais no footer. É importante ter uma descrição para esse link já que ele possui apenas uma imagem, e nenhum texto. Então poderia fazer assim, por exemplo: <a href="http://facebook.com" target="_blank" aria-label="Visit our facebook page." />. Assim se alguém que possui problema de visão e usa um screen reader chegar nessa parte do site, o screen reader vai ler "Visit our facebook page. Link", e o usuário vai saber que esse link vai levar ele para outra página, sem isso, o screen reader leria apenas "Link"

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