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

responsive article signup page

Belamana-Harshitha•150
@Belamana-Harshitha
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 specific areas of your project would you like help with?

I want help in the local storage method and the error while handling the email input

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harold-chn•770
    @chanwinharold
    Posted 6 months ago
    1. you should use semantics tags in your HTML
    2. you don't need to nest all the tags of your container in the form tag, just nest the input, the label and the button
    3. you don't need to create another page for the success message. Just set the display of this div to "none". if you do all in a single page using the display: none you'll be able to display the email value in the success message more easily in your form.addEventListener instead of using the local storage.
    4. try to review your css code for the responsiveness.

    I hope this comment helps you Good Luck😉

  • P
    Deepa Subramanian•200
    @sdkdeepa
    Posted 6 months ago
    1. HTML is not semantic. Please use <main>, <section> etc to make it semantic. You can take a look at this : https://www.w3schools.com/html/html5_semantic_elements.asp
    2. Use "alt" for images to make it accessible
    3. The image is not responsive for mobile and the image overflows.

    Resources:

    • https://utopia.fyi/
    • https://www.joshwcomeau.com/css/interactive-guide-to-flexbox/
    1. For error message you can use css to display: none; using the class name.

    Good luck! you are in the right track.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub