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

Stay updated using JavaScript!

pure-css
Chame "Guigui-chan"•290
@Guilherme-Porto-Silva
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?

For I re-created the basic concept of a form sumition had in my mind, I felt like I was doing something usefull, equal to what I had found to be "magic" before and, of course, updated!

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

The two sections have diferent shapes. On desktop, only. That was surprising and pattern breaking! Confortzone-kun doesn't like that sort of stuff °^°!

As usuall, I used ids to overcome it, by iding each section and setting the non-maching styles trough them. Sure it is easyer to understand than setting the style in DOM itself, but I would still like to learn a thirth way to do it that is better than both, since I literally set two ids to control a single slight diference.

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

I am extreamely new to forms and, as has our friend said in the suggested by the learningpath article, they are hard! Any little tip is winning.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mikhil Desai•600
    @mike15395
    Posted 5 months ago

    congratulations @Guilherme-Porto-Silva on completing this challenge! You need to improve a lot by making following changes: 1.Use email regex for checking valid email, you can check following function, function validateEmail(email) { const pattern = /^[^\s@]+@[^\s@]+\.[^\s@]+$/; return pattern.test(email); }

    the above function return a boolean value, based on which you can naviagte to success message or not.

    This is the major change in your code and rest are UI changes just look at design more carefully.

    Happy Coding!

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