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

Validation form

Daniele Ercoli•170
@DanieleErcoli243
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'm proud because I found all the solutions by myself when I had a problem of layout or so and I'm proud because I've been able to apply something I read on an article. Next time I would like to be faster at finding those solutions.

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

I had troubles handling the dimensions of the cards in the different breakpoints. I overcame them using the inpsector of the browser and all my knowledge and experience.

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

I would really like to master Javascript, because on html and css I'm confident.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Kiara•310
    @Kiara523
    Posted 5 months ago

    Hey I took a look at your solution and all looks great, semantic HTML, well organized and structured.

    The improvement on the HTML could be to use a <picture> tag which allows you to use the <source> tag to switch in between the two main images. It works a bit as a media query where you can set a break point <source media"(width: 650px)" srcset="...">

    In the message page you could also show the actual email address of the user using a span in the HTML and then display it with javascript.

    I hope this was useful.

    Marked as helpful
  • Edina Karsai Sztanojev•260
    @sztedina
    Posted 5 months ago

    Great job!

    Marked as helpful

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