Newsletter Signup Form

Solution retrospective
Hey
What challenges did you encounter, and how did you overcome them?With learning exercises, I often find it's easy to get tempted to add quick features, or test out new animations/syntax without putting in the proper planning or taking a step back and looking at the bigger picture. I found myself doing this with the project and adding/overwriting code and losing track of the scope of the project.
I found that implementing animations without proper planning makes it very difficult to track the state of items, repeated styles, and makes keeping a clean codebase much more difficult.
In the future, if I am doing any animation beyond a simple transition, I will create a diagram or storyboard it before.
What specific areas of your project would you like help with?I was mostly focused on the HTML/CSS but I feel like the logic in the newsletter form class could be split up and abstracted in a better way, such as creating new functions, sub-classes, etc. At present, there is a lot going on here, and it feels like I am putting everything in main.
Still matching the design and implementing some localState, if anyone spots any differences would appreciate the feedback/advice.
All feedback welcome.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Carl'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