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

Form with Client-Side Input Checking and Transition

P
Austin•430
@astnio
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 challenges did you encounter, and how did you overcome them?

This project was fine for the most part. I learned a lot about styling forms and setting up displays for errors.

The biggest challenge I had was actually self-inflicted, as I wanted the elements to move across the screen as a transition from submitting your email to having the success message. Before this point, everything was styled and working fine, but in order to get the transition to work I had to change everything to absolute positioning. I'm sure there was a better way to handle this, but this was just how I figured it out. One of the major issues with this is the fact that the major sections are no longer easily centered on the screen, and I had to use some magic numbers to get them to look right. It also messed up the views from desktop to mobile, which required some more magic numbers to get to look right on mobile view.

Overall I cannot say I am particularly proud of the solution I made, but it looks well enough so long as the format doesn't change too much. I would like to invest in researching better solutions for transitioning elements around like that in the future.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    KMS56135•160
    @KMS56135
    Posted 9 months ago

    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
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.

Oops! 😬

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

Log in with GitHub