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

Newsletter Sign-Up Form – React, Styled-Components

react, vite, styled-components
P
Mars - Martiniano Leguizamon•255
@martinianol
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 most proud of successfully implementing a responsive and accessible Newsletter Sign-Up Form using React, Vite, and Styled-Components. The project effectively handles user interactions such as focusing the input, triggering errors, and providing helpful feedback messages. Additionally, deploying the project to GitHub Pages was a great learning experience, especially figuring out how to use import.meta.env.BASE_URL to handle dynamic paths.

Next time, I would focus on enhancing the user experience by adding subtle animations and refining the form validation logic with a dedicated library like yup or react-hook-form. Additionally, I would consider using TypeScript for better type safety and a more robust development experience.

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

The biggest challenges I faced were: 1. Handling file paths for images and fonts when deploying to GitHub Pages. • Solution: Learning to use import.meta.env.BASE_URL and properly structuring my project by moving static assets to the public/ folder. 2. Managing focus and blur states for the input field to provide a smooth user experience. • Solution: Using React useRef and useEffect to handle click events, keyboard accessibility, and input focus/blur management. 3. Displaying images within styled-components using dynamic paths. • Solution: Moving assets to the public/ folder and referencing them correctly for both development and production modes.

What specific areas of your project would you like help with?
  1. Accessibility improvements: Making sure the form is fully accessible via keyboard and screen readers. 2. Animation techniques: Adding shake animations or subtle transitions to improve user feedback. The gradient background did not allow me to transition the way I wanted
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Yonerfy•210
    @Yonerfy
    Posted 3 months ago

    Great very well done.

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