Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Newsletter subscription form with dynamic success message using JS and

Maximo•160
@xmaxishh
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 am very proud to have completed the Frontend Mentor challenge and implemented a dynamic message with a responsive and functional design. Next time, I would like to focus more on the initial project planning to further optimize my time and resources. I also think I could have improved the CSS code structure to make it more modular and easier to maintain.

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

I encountered several challenges during the Frontend Mentor challenge. One of the main challenges was implementing a complex responsive design with dynamic messaging. To overcome this, experimented with different CSS techniques for layout and responsiveness. Additionally, managing my time effectively while maintaining code quality was another challenge. I addressed this by setting clear milestones and conducting regular reviews to ensure I stayed on track. Utilizing resources such as online tutorials and the Frontend Mentor community also provided valuable insights and support.

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

I would appreciate help with optimizing the performance of my project, particularly in refining the CSS structure to make it more modular and easier to maintain. Additionally, I'm interested in learning best practices for enhancing accessibility features and ensuring compatibility across different browsers. Any guidance on improving overall user experience through smooth interactions and responsive design would also be valuable.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Purvi Porwal•180
    @purviporwal1812
    Posted about 1 year ago

    You can make it responsive, else it is good

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