Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 20 days ago

Solution Contact Form with React

react
Evellyn Lindoso•60
@EvellynL
A solution to the Contact form 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?

I think what I was most proud of was that I had no issues with responsiveness. Plus, I had used the form components correctly.

What challenges did you encounter, and how did you overcome them?

My only challenge was centering the container in the middle of the screen :)

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

Maybe how to center this container in the middle and any other feedback will also be of great help

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bernardo Poggioni•6,770
    @R3ygoski
    Posted 19 days ago

    Olá Evellyn, parabéns pela conclusão de mais um projeto aqui do FEM, ele está bem-feito.

    Sobre sua dúvida, tem diversas formas de fazer centralização, a melhor geralmente é utilizando flex ou grid, mostrarei dois exemplos aqui:

    A fim de Contexto, esse será o HTML:

    <main class="pai">
      <section class="filho"></section>
    </main>
    

    Exemplo com Flexbox:

    .pai {
      display: flex; /* Determina o elemento como Flex */
      justify-content: center; /* Centraliza horizontalmente */
      align-items: center; /* Centraliza verticalmente */
      
      width: 320px;
      height: 320px;
      background-color: #333;
    }
    
    .filho {
      width: 120px;
      height: 120px;
      background-color: #a9a9a9;
    }
    

    Exemplo com Grid:

    .pai {
      display: grid; /* Determina o elemento como Grid */
      place-items: center; /* Posiciona o filho ao centro */
      
      width: 320px;
      height: 320px;
      background-color: #333;
    }
    
    .filho {
      width: 120px;
      height: 120px;
      background-color: #a9a9a9;
    }
    

    Para verificar isso você pode utilizar o site CodePen.

    Eu particularmente utilizo o #root como o fundo da página, assim os elementos ficam centralizados no #root. Algo assim:

    #root {
      min-height: 100dvh;
      width: 100%;
      display: flex;
      justify-content: center;
      align-items: center;
    }
    

    E uma dica quanto ao seu projeto na parte de JS, ele não está fazendo validação de forma correta, isso está ocorrendo porque você não está utilizando o hook useState para armazenar o valor de texto e fazer a validação. E fica uma diga, você consegue validar todos os campos utilizando RegExp (Expressões Regulares).

    E sobre o HTML, ele está com muitas redundâncias e muito pouco semântico, como o React é um CSR (Client Side Render) a parte de SEO acaba sendo afetada, mas manter um HTML semântico ainda sim é importante para manutenibilidade, escalabilidade e acessibilidade do projeto.

    E é isso, caso tenha ficado qualquer dúvida por favor comente abaixo que tentarei ajudar da melhor forma possível.

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