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

Newsletter sign up form with success message solution using js

Isabela Fernanda•190
@Isabela-Fernanda
A solution to the Newsletter sign-up form with success message 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?

PT

Estou satisfeita de ter descoberto como fazer a validação do email no js corretamente, mas acho que há bastante a melhorar no quesito velocidade.

EN

I'm pleased to have figured out how to do email validation in js correctly, but I think there's a lot of room for improvement in terms of speed.

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

PT

Eu enfrentei alguns desafios no js para fazer a validação do email, mas depois de algumas tentativas e pesquisando um pouco eu descobri como fazer. Além disso, tive algumas dificuldades com a exibição no github pages, ela estava diferente da que eu obtinha no repositório local, alguns problemas eu consegui resolver alterando a forma que eu escrevi os caminhos outros não.

EN

I faced some challenges in js to do the email validation, but after some attempts and researching a little I figured out how to do it. In addition, I had some difficulties with the display in github pages, it was different from what I got in the local repository, some problems I managed to solve by changing the way I wrote the paths, others not.

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

PT

Eu gostaria de ajuda em como fazer aparecer as bolinhas que são o estilo de lista nas páginas do guthib, no meu repositório local elas aparecem normalmente como nas imagens que eu colocoi da minha resolução, mas nas páginas do github elas não aparecem de jeito nenhum. Alguém sabe o que eu preciso mudar para que elas possam ser aplicadas?

EN

I would like help on how to make the dots that are the list style appear on the guthib pages, in my local repository they appear normally as in the images I placed of my resolution, but on the github pages they do not appear at all. Does anyone know what I need to change so that they can be applied?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Isabela Fernanda's solution.

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.