Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Intro Component W/Signup Form & Confirmation Page: HTML, CSS, JS

P
Jeff Guleserian•500
@jguleserian
A solution to the Intro component with sign-up form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Dear Community:

I chose this challenge specifically to practice form validation. In addition to the FM challenges, I also wanted to:

  • Test to confirm the form was validated as a whole and respond with with a confirmation
  • Create a confirmation/welcome page informing the user that their form submission was successful; provide a link back to the home page
  • Add an alternate error message for the email field in case it was left blank
  • Ensure page resizing was as responsive as possible and not just at breakpoints

For the most part, I am happy with the solution, though I feel like if I had spent more time, I could have found a way to reduce the JS (see README.md in the repository). I would appreciate some feedback regarding:

  1. A better strategy on the JavaScript to accomplish the same purpose
  2. A way to use JavaScript to save or update a .json file without creating a server first (is this something AJAX could do?)
  3. Readability, succinctness, accessibility, responsiveness

Thank you very much for taking the time to look through my submission. I would appreciate any constructive feedback you have.

Have a great weekend, Everyone!

Jeff

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Jeff Guleserian's solution.

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 1st-party linked stylesheets, and styles within <style> tags.

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.