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

Newsletter Sign-up Form with Success Message

ylin320•200
@ylin320
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?

Proud of:

  1. Implementing a robust email validation system that combines multiple approaches:
    • Regex pattern matching for basic format validation
    • Validator.js library for comprehensive email validation
    • Custom domain validation for common email providers
  2. Creating a responsive design that works seamlessly across different screen sizes

Would do differently:

  1. Add more comprehensive email validation rules to handle edge cases
  2. Implement rate limiting to prevent form spam
  3. Add loading states during form submission for better UX
  4. Enhance accessibility features for better inclusivity
What challenges did you encounter, and how did you overcome them?

Challenges:

  1. Email Validation Complexity

    • Challenge: Creating a reliable email validation system that catches invalid formats while accepting valid ones
    • Solution: Combined multiple validation approaches (regex, Validator.js, and domain checking) to create a robust system
  2. Responsive Design Implementation

    • Challenge: Ensuring the form looks good and functions well across all device sizes
    • Solution: Used a mobile-first approach with CSS Grid and Flexbox, implementing media queries for different breakpoints
What specific areas of your project would you like help with?

Email Validation Enhancement

  • Looking for feedback on the current validation approach
  • Suggestions for handling more edge cases
  • Best practices for email validation in production
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • arthurns1•50
    @arthurns1
    Posted 5 months ago

    The smartphone screen its with a width too short, and the background color is looking different from the preview. Your Javascript code is very good, at rest it's all good, congratulations

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

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