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

Newsletter_sign-up_form_with_success_message( Javascript )

Thomas•550
@TomSif
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 started with the design of the mobile version, then the success message and then I adjusted the media queries for the desktop version, once the whole structure was perfectly finished, I started on the javascript part. At first I was really overwhelmed, I didn't know where to start but by listing my needs and how to proceed I was able to find a solution that wasn't too complex. I probably should have done things differently on how to hide the main container, I modified the display directly in the css with javascript, I probably should have added a .hidden class but I didn't have the courage to start again.

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

Figuring out how to change the border radius directly in the svg file so that it fits the design, I searched a bit. This is by far the most complex project I've done so far and yet it's really a small project on a single page, with little interaction, I realize how far I still have to go. travel and it feels like climbing Everest sometimes, but small steps by small steps, I progress at my own pace.

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

All advice is welcome, especially on how I structured the project, I am curious to see if there was simpler or how others have proceeded, I would perhaps look at other projects to learn an idea. The JavaScript approach is still a big gap, even if I understand the language, sometimes I have a lot of trouble articulating the functions together.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • petemac281•220
    @petemac281
    Posted 10 months ago

    You did great. I'm just starting out, but I look at some of what you did and it gives me thoughts about how I can make my own projects better.

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