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

Newsletter Form Validation Challenge

DoomCrusher•120
@VADER900000
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?

my Form validation

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

i couldnt make the form validation work quite well then i just made the form validation with the button click instead of onkeyup

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

the javascript

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • M. Abubakr•250
    @m-abubakr1
    Posted 5 months ago

    You have done a great job there.

    Instead of relying solely on flexbox, consider using CSS Grid for centering key containers. For example, you can center the main sign-up form like this:

    body {
      display: grid;
      place-items: center; /* centers both horizontally and vertically */
      min-height: 100vh;
      background-color: #ffffff;
      font-family: "Manrope", serif;
    }
    

    This method is very concise and reliable for centering your content on the page.

    Your JavaScript toggles the display by directly changing inline styles. To better separate behavior from styling, you can toggle CSS classes. This makes your code more maintainable and easier to adjust later.

    Example:

    Define hidden/visible states in CSS:

    .hidden {
      display: none;
    }
    .visible {
      display: flex; /* or block, depending on your layout */
    }
    

    Update your JavaScript:

    document.addEventListener("DOMContentLoaded", function () {
      const form = document.querySelector("form");
      const emailField = document.getElementById("EmailField");
      const emailError = document.getElementById("EmailError");
      const mainerContainer = document.querySelector(".MainerContainer");
      const successPage = document.querySelector(".SuccessPage");
    
      function validateEmail(event) {
        const emailPattern = /^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}$/;
        
        // Check email validity
        if (!emailField.value.match(emailPattern)) {
          emailError.textContent = "Valid email required";
          emailField.classList.add("error");
          event.preventDefault();
          return;
        } else {
          emailError.textContent = "";
          emailField.classList.remove("error");
        }
    
        event.preventDefault();
        mainerContainer.classList.add("hidden");
        successPage.classList.remove("hidden");
        successPage.classList.add("visible");
      }
    
      form.addEventListener("submit", validateEmail);
    });
    

    And in your CSS, you might add styles for the error state:

    .error {
      border: 1px solid #e49e99;
      background-color: #ffe8e6;
    }
    

    This approach improves readability and makes it easier to update the presentation without touching your JavaScript.

    Avoid using inline style changes within JavaScript. By toggling classes (as shown above), you let CSS handle presentation and JavaScript focus solely on behavior.

    Try to group common styles or use CSS variables to avoid repeating similar declarations across media queries. This will make your stylesheet easier to maintain.

    Your naming (e.g., .MainerContainer, .SuccessPage) is clear. Just double-check consistency (e.g., sometimes main is spelled differently) to keep the codebase neat.

    Marked as helpful

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