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

Responsive company subscription page

Code-S1•210
@Code-S1
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?

The thing that I used JavaScript and this is my first ever project with JavaScript

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

1-The JavaScript is hard for me as I am a newbie. I got a little help from AI to find methods like .value, .textContent, trim(), etc. 2-The buttons somehow just don’t have the transition, or is it just me? The transition only works when the mouse moves out of the button. I don’t know why. 3-I couldn’t think of making a whole other file and linking it to show after submitting. Instead, I just went for the modal. Someone said it was easy. 4-I couldn’t get the button to stop working whenever the email is not valid. That’s my weakness, and I want to improve that. But I just don’t seem to find the logic or a plan on how to do so.

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

JavaScript definitely and how to plan the planning

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    JiaHe35354•190
    @JiaHe35354
    Posted about 1 month ago

    Hi! You're doing a great job so far. One suggestion — the success message currently appears alongside the form. You could improve the user experience by hiding the form when the success message is shown. This can be done easily using CSS in combination with JavaScript.

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