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

Newsletter sign-up form with success message using CSS Flexbox

pure-css, accessibility
Muhamad Rukhul Kirom•380
@rukhulkirom
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’m most proud of the clean, responsive, and user-friendly design of the newsletter sign-up form. The combination of a well-structured HTML layout, organized CSS styles, and interactive JavaScript validation creates a seamless experience for users. The success modal also enhances usability by providing clear feedback after form submission. Additionally, I like how the form includes email validation, error handling, and real-time feedback to improve user experience.

What would you do differently next time?

  • Enhance Form Validation: The current email validation is functional, but I would implement more comprehensive validation using the browser's built-in validation APIs and provide better feedback messages.

  • Store User Data: If this were a real-world application, I’d integrate it with a backend API to store email addresses and send confirmation emails.

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

Challenge: Ensuring users enter a valid email while providing clear error feedback was a bit tricky. Initially, the error message was always displayed, making the form look broken even before user interaction.

Solution: I implemented event listeners to show and hide the error message dynamically. Now, the error appears only when the user enters an invalid email and disappears as soon as they type a correct one.

What specific areas of your project would you like help with?
  1. The email validation works well, but are there better ways to handle it?

  2. Should I use the browser's built-in validation (pattern attribute) instead of custom JavaScript regex?

  3. Is my JavaScript clean and efficient, or could it be refactored for better performance?

  4. Are there any unnecessary styles in the CSS that could be optimized?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Annalyza106•190
    @Annalyza106
    Posted 4 months ago

    I like the responsiveness of the website. Great work!

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