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

Newsletter sign-up form with success message using HTML, CSS, JS.

bem
Josephine Fitalvo•260
@fitalvojosephine
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 am proud that I finally finished this challenge. Next time, I will do more research and dig deeper into learning the structure of the DOM, validation, and submission. Honestly, this is where I got stuck. But with the help of YouTube and ChatGPT, I made it. Thank you, Google, YouTube, and ChatGPT.

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

First, I encountered challenges in the layout and figuring out how to structure my HTML and CSS to implement the DOM. So, I researched it, read some other developers' code, and tried applying it to my own code, eventually finding my own way. I am happy that I overcame it all, including mobile responsiveness, which I managed with the help of reading documentation and implementing it in my CSS code.

The hardest part was the JS fundamentals of form validation. I researched it to understand how it works, including the functionality of addEventListener, using if statements for error messages, displaying elements using the DOM, toggling state to hide the form, and the regex for invalid email validation. This was really challenging, but I had fun and didn't give up. I must learn more and apply this knowledge to other challenging projects.

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

So far none. #HappyCodingEveryone

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dipesh•430
    @Dipesh-sapkota1
    Posted 11 months ago

    Congratulation on completion of your project

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, SASS, 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