Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 25 days ago

Intro-component-with-signup-form with TS, React, Tailwind, Shadcn, Zod

shadcn, tailwind-css, typescript, zod, react-hook-form
Akiz-Ivanov•430
@Akiz-Ivanov
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


What are you most proud of, and what would you do differently next time?

I'm proud that I took on this challenge using a modern tech stack — TypeScript, React, Tailwind CSS, Shadcn/UI, Zod, and React Hook Form. It was a great opportunity to solidify how these tools work together in a real-world project.

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

The biggest challenge was replicating the transparent shadow behind the cards, which I ended up solving using an absolutely positioned div behind the card elements. It took a bit of trial and error to get it looking right.

What specific areas of your project would you like help with?

I'd love feedback on the transparent shadow effect — is there a more effective or semantic way to achieve that look without resorting to an absolutely positioned div? If anyone has suggestions or alternative approaches, I'd be glad to hear them.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ahmed Ali•550
    @qayoommunawar
    Posted 25 days ago

    Hi hope you are doing well, your design is doing well. For transparent shadows you can play along with box shadows changing the hsla value of red color. Give it a try. Thank you, keep designing best of luck..

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