DEV Community

Cover image for Why I Built This Open Source Shadcn Tool After 15 Years of Building Templates
Sunil Joshi for Shadcn Space

Posted on • Edited on

Why I Built This Open Source Shadcn Tool After 15 Years of Building Templates

For the past 15 years, I’ve built web templates, dashboards, components, and figma ui kits. Through products like Wrappixel, AdminMart, Tailwindadmin, and Get Nextjs Templates, we’ve worked on hundreds of layouts across famous frameworks and UI libraries.

One thing has always stayed the same:

Every project begins with the same UI foundation work.

  • Menu.
  • Sidebar layout.
  • Dashboard structure.
  • Landing page sections.
  • Forms.
  • Tables.

No matter how modern the tools become, the starting work repeats itself.

In recent years, UI blocks have become more popular. Developers don’t want heavy frameworks anymore. They want flexible building blocks that work with the tools they already use.

That’s when we started paying close attention to shadcn/ui.

It became widely adopted by React and Next.js developers because it gives control back to the developer. Clean components. Editable code. No hidden layers.

So we decided to build on top of that ecosystem.

That’s how Shadcn Space started.

What I Wanted to Fix

When building products, most of the early time goes into layout work.

  1. Spacing.
  2. Structure.
  3. Responsive behavior.
  4. Empty states.
  5. Page flow.

It’s important work; But it’s also repetitive.

I didn’t want another framework.

I didn’t want something that hides the code.

I didn’t want a system that forces design decisions.

I wanted a clean starting point that I could fully edit.


From Open Source to a Larger Shadcn Library

Shadcn Space began as an open-source collection of useful UI library built around shadcn/ui.

While building real products, we kept creating new layouts and reusable patterns internally. Instead of keeping them private, we decided to organize them properly.

Recently, we crossed 300+ stars on GitHub, which has been encouraging to see. It tells us developers find this useful in real projects.

If you’re using it or find it helpful, you can support us
giving it a star here ⭐ https://github.com/shadcnspace/shadcnspace

Community support helps us continue improving and maintaining it.

What’s Inside Shadcn Space Pro

Today, it includes:

  • 180+ Shadcn Blocks

  • 8 Shadcn Templates

  • 130+ Shadcn Components

Let me explain what that really means.

Not because we wanted a large number, but because real projects require real patterns.

Why Shadcn Blocks Matter

Blocks solve a practical problem.

Instead of designing and structuring the same hero section or pricing layout again, you start with something already structured.

Shadcn Blocks include:

  • Landing page sections

  • Feature layouts

  • Pricing tables

  • Testimonials

  • Navigation patterns

  • Dashboard sections

Shadcn Blocks

They are written in clean React and Tailwind.

You copy the code. You adjust it. You move forward.

This removes the repetitive setup phase that slows down many web projects.

Components That Stay Editable

Shadcn Components inside Space are simple and readable.

  • Buttons.
  • Badges.
  • Cards.
  • Tables.
  • Sidebars.

Everything remains fully editable.

Shadcn UI Components

We’ve spent years working with developers who dislike locked systems. So keeping code ownership was important to us.

If your product grows or changes direction, you’re not forced to rebuild everything.

Templates for Real Products

Our Shadcn Templates are different from other shadcn resources.

They provide a full layout structure something you can build on immediately.

These are helpful when building:

  • Agency Websites
  • Real Estate Sites
  • Crypto Landing Pages

Shadcn UI Templates

Instead of thinking about layout decisions from scratch, you begin with a solid template and focus on your actual product logic.

What We’re Trying to Do Long Term

We don’t see Shadcn Space as just another templates collection.

We see it as part of the growing Shadcn ecosystem.

As more developers adopt shadcn/ui, there’s a need for structured blocks, layouts, and real-world patterns that stay flexible.

Our goal is to continue contributing to that ecosystem both open source and premium in a way that respects developer control.


Final Thoughts

After 15 years of building admin dashboards and website templates, one thing is clear:

Developers don’t want more complexity.

They want a better starting point.

Shadcn Space exists to provide that structured UI foundations built around tools developers already trust.

If you’re already using shadcn/ui with React or Next.js, this simply helps you move forward without rebuilding the same blocks & components again.

That’s the intention behind it.

Top comments (0)