[Feature]: Shadcn/vue extended

[zernonia]

Describe the feature

Shadcn/UI has a great community extension, listed on Awesome Shadcn UI. Inspired by this, we want to provide the same opportunities for the Vue community by introducing the shadcn-vue-extended repository.

With this initiative, you can:

• Suggest custom components and contribute via PRs
• Easily deploy the component registry and documentation
• Gain more visibility for your components
• Give back to the community

We will be moving the following components to the extended repository (and their relevant tickets):

1. AutoForm
2. Chart

We’d love to hear your thoughts! 😁

Additional information

• I intend to submit a PR for this feature.
• I have already implemented and/or tested this feature.

[productdevbook]

I like this idea

[zernonia]

Thanks @adiramardiani for the component suggestions. However in order to not flood this PR with requests, I've hidden them as off-topic (we can create the tickets in the new repo). Let's have this ticket focusing on thoughts and idea 💡

[ThimoDEV]

It would be really good to have it all in one repo, so the users can quickly grab what they see. Also I think it would be a good idea to have a link on the shadcn-vue site with a see more button or directly show the components on shadcn vue somehow

Slichtly off topic: To make it easier as an UI ecosystem it could be a good idea to have a reference on each site to alll the other options, so Reka UI, Inspira UI, Shadcn Vue having links to each other and to the shadcn extended

[zernonia]

@ThimoDEV we wanted to keep the shadcn/vue as close to main shadcn as possible. This allow for quick follow up to latest changes.

The idea of extended repo is to allow community to be creative, and take credit and ownership for the components they created. This would also improve the time to review PR.

[maelp]

will there be also a notion of registry like shadcn to make it easy to distribute / package / update components?

[mathieumagalhaes]

@maelp: will there be also a notion of registry like shadcn to make it easy to distribute / package / update components?

I think there is already a way through a repository schema, see Inspira Component Schema Example. Not sure where this is documented on the shadcn-vue website.

I think the original shadcn/ui docs around a repository should still be ported into shadcn-vue website.
See: https://ui.shadcn.com/docs/registry

A list of missing features for feature parity compared to shadcn/ui would also benefit this project in my opinion, but that might be off topic. I've requested this in #1105

[mathieumagalhaes]

@adiramardiani
I think origin-ui have some good extended version of shadcn-ui (react)
https://originui.com/timeline

These are other libraries to keep an eye on, for inspiration of future Shadcn/Vue blocks:

• https://nsui.irung.me (open source)
• https://ui.stackzero.co (open source)
• https://shadcn-ui-blocks.vercel.app (open source)
• https://www.simple-ai.dev/blocks (open source)
• https://www.stunningui.design/blocks (open source)

Note that we already have a popular project extending shadcn-vue :

• https://inspira-ui.com

---

@ThimoDEV: It would be really good to have it all in one repo
@zernonia: The idea of extended repo is to allow community to be creative, and take credit and ownership for the components they created

If I understand correctly, a shadcn-vue-extended would be maintained by the same maintainers of shadcn-vue, which is great.

I do believe that having an Awesome list, Awesome Shadcn Vue, is still also needed.

Examples for shadcn/ui:

• See: https://github.com/bytefer/awesome-shadcn-ui
• See: https://github.com/birobirobiro/awesome-shadcn-ui

Other developers' projects are showcased, which is a great way to build a healthy ecosystem of blocks, components, and extensions— while also making others aware of their existence through an official Awesome list.

[Saeid-Za]

this approach would be beneficial, as it would prevent shadcn-vue from being blocked by extra or custom components. It could also accelerate the development of core mainstream components.

However, one potential challenge is how maintainers would manage the extra-shadcn-vue repository.

I propose adopting a maintenance strategy similar to that of UnJS repositories. Each repository would be maintained by its original creator, but all would be guided by upstream maintainers.

This approach seems ideal, but I'm unsure if it's practical for maintaining smaller components compared to fully isolated JavaScript packages.

How UnJS packages are maintained.

[ijpatricio]

Hey hello,

Is this on the direction for a central point where we can get/publish components?

I think that is missing, and I am willing on collaborating on a solution.

I've read Registries have to be started by a user, and that's fantastic to be there.

BUT - without a low friction way, I don't believe it will be as spread.

Any thoughts?

[haayhappen]

Let's get some momentum back here. What's still needed to discuss or start with this project? @zernonia