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

Newsletter Sign-up Form with Success Message

Leanne Keenan•140
@leannekeenan
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 project was hard for me but I am very proud of completing it. The most difficult part for me was trying to get the functionality of the email component to test if: A. a proper email was entered B. If not, do not directly go to the success page but instead show the email error message on the main page.

I eventually figured out that it wasn't what I was or was not missing in my code, but rather the order in which the commands were placed which was causing the issue. I always wondered why in some tutorials, some developers will place commands in a specific order but never explain why, and the reason is the same as the cascade in CSS - things have to be placed in a specific order to take effect, or else it is just bloated code and takes up space.

Having learned this lesson, I will make a conscious effort to organize my code based on what I call the "cart before the horse" concept, ensuring I am not calling elements before they are defined or using defined elements outside of their function unless defined as global.

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

As previously mentioned, I found this exercise quite difficult. The organization of the JavaScript to ensure the use of the elements in their proper cascade was one issue, I also ran into styling issues with the email-error element and the checkmark list-icon styling. I am not too familiar with the pseudo codes outside of hover, so the use of "li:before" was a challenge to understand, but from what I gathered, the ":before" and ":after" pseudo-classes allow for developers to insert additional content to an existing element like an image or icon, allowing them to modify the appearance of the defined content -which is how I got the background if the white checkmarks to be the defined tomato color.

For the email error message, I needed to create a validation function to check the value of what the user entered into the DOM input. from there, I needed to check to see if the value contained elements that aren't normally allowed in email addresses like asterisks and dollar signs. If those elements are found, a message requesting a valid email is shown, as well as ensuring there is a clause to catch if there is no email at all and returning a request message to enter an email in the same span.

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

I appreciate anyone willing to look at my work and provide feedback. All help is 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 Leanne Keenan'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.