Understanding and Documentation around Shadcn Style and version

[KenticoDevTrev]

@sean0205

Firstly, Thanks for a previous answer on switching the style to radix-nova (although radix-vera was missing some of the patterns).

Can you help share some answers to the following, and possibly update documentation to help?

1. Why is there a disconnect between the 'style' and what's on the github repo? Is radix-nova the official version that's shown in the Main branch? What style is used on the site?
2. Is it the eventual goal that all the REUI elements will exist with all the styles, but there's a timeline that it will take to update them all?
3. Is it even your responsibility to create all the styles, or is this suppose to be a community lead thing?
4. How often, when updates are made to the main branch, is the shadcdn updated that we can 'pull' those in?
5. On the reui.io site, docs only shows about 17 components documented, and but on Patterns has a TON of elements (with varying degrees of ability to pull and use). Can you speak on how we should use these? Are the ones in Docs "Done" and the rest are still in development? Are the patterned ones largely done on some style, and documentation is still catching up? etc.

Overall, we're looking for guidance on how to use the most up to date version and be able to dev on it. It's very difficult right now with trying to adopt this, and we need to finish migrating our components by week's end so we can push and update.

[sean0205]

@KenticoDevTrev

1. shadcn Compatibility

ReUI 2.0 is fully compatible with the latest shadcn/ui setup, including the new create workflow:
https://ui.shadcn.com/create

You can generate your own component library, choose your preferred style, and any component or pattern you use from ReUI will work seamlessly within that setup.

3. Style Support
   ReUI currently supports 5 styles. These are already implemented and aligned for use within a standard shadcn-based architecture.

4. Style Alignment
   By default, ReUI aligns with the official styles provided via shadcn/create. We follow their structure and conventions to ensure smooth integration and no architectural conflicts.

5. Update Frequency
   We regularly update ReUI to stay in sync with upstream shadcn/ui changes. Updates are rolled out in stable iterations to maintain compatibility.

6. Docs vs Patterns
   The Docs section highlights unique, in-house components built specifically by the ReUI team.

So basically you can copy and paste ReUI patterns directly into your project and use them just like standard shadcn components. ReUI is built on top of shadcn not parallel to it.

If anything needs deeper clarification, feel free to share specifics and we’ll walk through it with you.

[KenticoDevTrev]

@sean0205

While that sounds great, not much of what you said is ACTUALLY reality, or at least not what i've been seeing and experiencing.

3. Style support: We are seeing Different Component .tsx content when on different styles. Switching to radix-nova produced at least closer to up to date component tsx files that matched.

But even with that, we are still getting components that are broken or not in line with V2:

For example, i just yesturday used the create to pull in some components, and the avatar.tsx pulled in. When i compare against what is in your repo, it's VASTLY different. See below where the left is what pulled in, and the right which is what's in github. Your github file was updated 2 weeks ago on the "pre-v2 release" (so #5 on the update frequency needs clarification)

When i look at others, it's the same story - missing class names, different styles, etc. We have started to just copy and paste from the repo because whatever is up on the "https://reui.io/r/{style}/{name}.json" registry is NOT what's on main.

#6: This also makes things an issue with Docs vs. Patterns, because i don't know if you're pushing up what's on Main to the site for the demo, but the repo is still out of sync, or vice versa where the repo won't match reui.io docs.

So what I want to understand is, i understand the ideal is that updates on the repo will be in the CDN within X Time (and what that time is i would love to know, so we know), the reality is the repo that the npx shadcn@latest add @reui/xxxxx patterns is currently useless : /

Developer to Developers - can you give us a realistic picture of the reality of things so we can proceed knowing what should be done. Do we trust docs yet or no? Do we use npx shadcn@latest add or no? Do we do that first so the variables update but pull in the latest from main or no?

Thanks Sean, sorry to be a little more critical, it's not because of you, but Metronics that uses this has changed their structure 3-4 times and we NEED stability as we are starting the next major wave of front end development.

[sean0205]

@KenticoDevTrev

In ReUI 1.x, we shipped and maintained our own core components (Button, Input, Avatar, etc.).

With ReUI 2.0, we’ve moved away from maintaining a separate core and now rely entirely on the original shadcn components for Button, Input, Avatar, and other fundamentals. ReUI now focuses purely on providing higher-level patterns built on top of the shadcn core.

This shift keeps everything aligned with the shadcn ecosystem, reduces duplication, and ensures full compatibility with its styles and base libraries going forward.

For Metronic, we’ll be releasing a complete revamp powered by ReUI 2.0 and the shadcn core components in the coming weeks.

This update aligns Metronic with the new architecture, using shadcn for all core primitives and ReUI for higher-level patterns — ensuring better consistency, easier customization, and long-term maintainability.

More details will be shared soon.

[KenticoDevTrev]

@sean0205

So is the reui.io repository still on v1, but the github main is on v2? Is that why there's such a difference? Is what's on this repo's main component .tsx files v2 or v1?

How big is this 'revamp' going to mess things up in the next coming weeks? Documentation doesn't mention ANY of this...and if we have to rebuild ALL our tools AGAIN in a couple weeks, i'm going to cry.

Please provide some clarity, or update the readme on the repo or site at least please.

What do we need to do to make sure we are using ShadCN's components, and developing off of what will be REUI 2.0?

[sean0205]

@KenticoDevTrev appreciate your feedback as a Metronic user.

Please note that ReUI is evolving as an open-source project with its own independent roadmap. Metronic, on the other hand, remains stable on the ReUI 1.x component foundation. Upcoming updates will introduce a new Metronic version powered by ReUI 2.0, bringing additional features and improvements.

We also noticed that we missed pointing Metronic to v1.reui.io, and we will correct this right away. Thank you for highlighting it.

A complete Metronic roadmap will be released soon. In the meantime, Metronic remains stable, fully supported, and aligned with ReUI 1.x.

[KenticoDevTrev]

@sean0205

I think "Metronics to v1.reui.io" is a BIG part of this confusion.

I took a look at Shadcn's components and they are much closer to what we are seeing when we do the shadcn@latest add.

Let me see if i understand this now, please confirm or correct any of the below:

• Version 1 of REUI.IO had their own components (and is what is shown in the main branch of this repo), and Metronics is currently on Version 1
• Version 2 of REUI.IO will ultimately be just a Pattern library that uses ShadCN, with some small theming tweaks. It is not complete yet though.
• When we do a Shadcn@latest add @reui/p-xxxx-x we are pulling in ShadCN components and REUI.IO's V2 patterns (which are not complete yet so may be buggy)
• Metronics will eventually be moving to use v2 of REUI.IO and have all the components rebuilt and skinned to match the theme, using ShadCN's components

If So, please:

• Update documentation both on REUI (https://reui.io/) and this repo (https://github.com/keenthemes/reui/blob/main/README.md) to reflect that Version 2 is not complete and maybe indicate that the components found in this repo are Version 1 (perhaps the patterns are really the v2?) (https://reui.io/)
• Update the installation instructions to specify v1 vs. v2, and the design pattern changes possibly, maybe even a better summary of how REUI.IO interacts with Shadcn in V2, and how it did things in V1?
• Update https://docs.keenthemes.com/metronic-react/getting-started/changelog to perhaps point to v1 or mention it's on V1

And I want to know:

1. We are already using the "@reui": "https://reui.io/r/{style}/{name}.json" registration, are the patterns pulling in from there v1 or v2 patterns?
2. If we develop using these components (ShadCN), i assume we are still 'safe' to do so, because we ultimately are using a stable product, and eventually when REUI.io v2 / Metronics v2 comes out, there may be just some styling variations we can elect to apply, as well as some new patterns?
3. If we do find a bug in a component, if it's a ShadCN component that gets pulled in, i assume we should look to do a pull request with them vs. REUI?

Thanks for being responsible, this is extremely confusing...

[sean0205]

@KenticoDevTrev

Thanks for the feedback.We’ll update the Metronic changelog and documentation accordingly.

1. "@reui": "https://reui.io/r/{style}/{name}.json" pulls shadcn components based on your selected style, along with ReUI 2.0 patterns aligned to the same style configuration.
   If you encounter any issues, please report them, we’ll review and fix them promptly.

Based on our testing, ReUI 2.0 patterns are fully compatible with the latest components from shadcn. That said, there are a few known issues in the latest shadcn updates, and official fixes are already in progress by their maintainers.

2. We recommend using shadcn + ReUI 2.0 patterns together.
   In addition to core components, ReUI 2.0 provides advanced and unique components such as Filter, Data Grid, and Kanban, which extend the base system.

3. Please report any issues via GitHub Issues. We’ll investigate and determine whether it’s related to shadcn or ReUI. If it’s a shadcn issue, we’ll confirm it. If it’s on our side, we’ll fix the pattern immediately.

So far, ReUI 2.0 patterns are stable with the latest shadcn components:
https://reui.io/patterns

If you notice anything in your local setup, please let us know your feedback helps us continuously improve ReUI.

Thanks