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

Product landing page using shadcn/ui

react, shadcn, tailwind-css, zustand, vite
Kim Fransson•420
@kim-fransson
A solution to the E-commerce product page 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 mostly proud of the planning, did a rough sketch about how the page would be structured and what components/states would be needed. That helped me to think about the implemenation rather than to always think about the high level design.

This also helped me decide if shadcn/ui would be a good fit for the challenge (minimize the risk to create components from scratch).

The only risk I saw during the planning was that I didn't know how easy it would be to customize "shadcn/ui" components. And the lack of a "number input" component.

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

Without the figma design, making it "pixel perfect" is not really the goal, however I tried to make the layout as close as the design as possible.

Shadcn/ui made it fairly easy/fast to get a working prototype working. However customizing was a bit trickier (but possible). If I would spend more time on the challenge I would probably look into how the "shadcn/ui" components are designed/built and perhaps try to create more "variants".

I usually just dumped some tailwind classes on the "root" component, in order to override the styles, but I don't think this is the prefered way when you need to make heavy visual changes.

This was the case when I tried to have the "thumbnails images" as toggle buttons.

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

Not really looking for specific feedback, but it would be fun/interesting to know about what others think about shadcn/ui

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Kim Fransson'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
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.