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

Newsletter Sign Up Form with vanilla javascript

saccoViola•90
@saccoViola
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?

I'm proud of the final design and that it took less time to finish the graphic part, compared to my last challenge.

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

It was challenging to set the javascript part to verify the email address, I'm not sure that I verified all the parameters, if not, please tell me and I'll be happy to listen! In this process, Google was my first ally, I also asked chatGPT in some moments in which I was stuck, just copying/partying my code asking if there were syntax errors

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

For sure there is a faster way to verify that the input email address is actually a valid email address, I would like to know also different ways to do it!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Facundo Andrés De Los Rios•360
    @FacundoDLR
    Posted 7 months ago

    Hi! I´ve already saw your code and I had some comments for you. I hope they are helpful to you.

    • I've seen you are using id's for apply styles and this is bad practice. It's always recommended use class atributte to apply CSS styles. The id's only using for javascript.
    • One alternative for your Javascript code is using Regex (Regular expresion) for email validation, it is more simple and you can test in HTML without necessitie javascript. Once your validation is working, you can use it in javascript as a constant to use in validation. Everything I've already told you can search on Google or ask ChatGPT he.

    Lastly, I apologize if my English is wrong (I'm practicing my English writing), I hope you can understand me. If you have any doubts or questions, you can tell me.

    Marked as helpful
  • sediqa•210
    @Hasani-Sediqa
    Posted 7 months ago

    Nice job! I think you forgot to add a box shadow to the buttons, You can use something like: box-shadow: 0 4px 8px -1px rgba(255, 0, 0, 0.5); to achieve the effect.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub