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

Newsletter Sign Up with React Typescript and Tailwindcss

Mr Rainman•130
@phantomgizmo
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?

Able to use react typescript and tailwindcss for this challenge.

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

For this challenge i decided to use react with typescript and tailwindcss solely because i want to start learning those stacks.

Challenges:

  1. Setting up project:
    • I learnt you can use tools like vite to generate a project starter.
    • Learnt about tsconfig and quite a bit about its properties.
    • Learn a bit about vite config and how you can create aliases.
    • Learn a few things about tailwindcss setup with postcss and few extensions for vscode to make your development with tailwind more pleasant.
    • Since we are dealing with form, i come across react-hook-form and zod for handling form and validation.
    • Learnt about project structures.
  2. Learn about typescript type, interface and type narrowing.
  3. Learn a bit about how to use react router for routing your pages.
  4. Learn about seperating your code into smaller piece of code by moving a few components (button and input) to be its own module.
  5. Learn a lot about react hooks.
  6. Learn about providers on react.
What specific areas of your project would you like help with?
  1. I struggle about z-index when creating shadow for a button. I learnt about an element will create stacking context if it has position other than static and z-index other than auto or 0. I set the button position to relative and z-index to 1 and before pseudo-element position to absolute and z-index of -1. But it only move the before pseudo-element below button text and stil on top of button background color.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • uheron96•230
    @uheron96
    Posted 5 months ago

    Everything looks and works as expected. I see you wrote it in React, great job! If this is the first time you used React, keep it up. If you are already familiar with React, then I would challenge you to try to recreate this website using vanilla JavaScript. As a person who works with React Native for my work, I found using Vanilla JS pretty challenging.

    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

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