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

Responsive Newsletter Sign Up - HTML, CSS, JavaScript with Validator

Tharun Raj•1,330
@Code-Beaker
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?

This is my 3rd JavaScript project as well as my 6th Junior project!

What I've used to build this project:

  • HTML
  • CSS - grid and flex
  • Javascript
  • Validator.js

I'm not very good when it comes to JavaScript. Since my knowledge is limited, I had to go through Google and read MDN Docs and many other websites for the email validation to work.

I have learned some things throughout the project:

  • learned to make images responsive with the help of the srcset attribute of HTML.
  • learned some more concepts of JavaScript for the form's working such as:
    • taking the value of input fields and storing them inside a variable.
    • updating the states of the input fields as well as the error text whenever the entered value does not meet the requirements.
    • I think I have improved a bit of my CSS too. Sadly, I forgot to use grid for this one.

I had lot of fun making this one. It was very challenging to me...

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

As I mentioned, I'm not very good at JavaScript. I don't know much about it.

E-mail validation was a bit of a challenge to me. It made me go through various MDN and GeeksForGeeks articles to implement.

Things I did easily:

  • the error state when email input is empty.
  • the success modal inheriting the input email address.
  • switching back and forth between the modal and the form when clicking on the buttons.

How I overcame the issue: I spent hours to create it and, in the end, I had to use Validator.js library. It was pretty easy to use and implement.

But it didn't work. It just leads to the modal despite me not entering a valid email. I don't know understand how to fix it. Here's my code snippet:

  • In the HTML, I imported the library using CDN:
What specific areas of your project would you like help with?
  • Next time, I will learn more of JavaScript concepts to make sure things work as they're intended to.
  • I will start with mobile-first workflow to make things responsive in a better way.
  • Learn more about useful libraries to make things easier and better.

Any suggestions are welcome! 😃

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Tharun Raj'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 1st-party linked stylesheets, and styles within <style> tags.

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.