A shadcn/ui-inspired Component Registry for RazorConsole

[LittleLittleCloud]

I am thinking about create a curated component registry inspired by shadcn/ui, where user and pull/publish their components to the community

Benefits:
• You Own the Code: Components (.razor, .cs) are part of your source tree.
• Full Customization: Edit the files directly. No black boxes or dependency conflicts.
• Unopinionated: Use components without adopting a heavy-handed framework.

Proposed Architecture

1. The Registry Website: A showcase of components with previews (GIFs/screenshots), source code, and CLI commands.
2. The CLI Tool: A .NET Global Tool (e.g., dotnet-razorui add table) that fetches component code and places it directly into your project.
3. The Components: High-quality, self-contained components. I propose these be RazorConsole wrappers that leverage Spectre.Console for rendering, combining Razor's component model with Spectre's powerful rendering.

Questions for the community:
• What are your thoughts on this component sharing model?
• What potential hurdles or design decisions should we consider?
• Would this be valuable to you?

[TeseySTD]

1. "What are your thoughts on this component sharing model?" - I think it's a good approach, all TUI libs that I found didn't something like that, so it will be a really valuable feature of our project.

2. "What potential hurdles or design decisions should we consider":

   1. Dependency Management
   • RazorConsole version conflicts: Should components declare minimum/maximum
     compatible versions?
   • CLI should definitely check compatibility before adding - failing after
     copying files would be frustrating
   2. Component Discovery & Quality Control
   • Will we curate all components yourself, or allow community submissions?
   • If community-driven: how do you ensure quality, security, and maintainability?
   • Code review process? Automated testing requirements?
   3. Versioning & Updates
   • Once a component is copied into a project, how does the user update it?
   • Do you track which version was installed? (Some metadata maybe?)
   4. Documentation & Previews
   • Optional: Static GIFs are okay, but interactive previews would be amazing (maybe terminal emulator in browser using web assembly?)
   • Each component needs: examples, props documentation, customization guide

3. "Would this be valuable to you?" - Yeah, TUI is getting more popular and this approach is time tested in web component development, so I think our project will increase the accessibility for new ones that came from web dev.

[LittleLittleCloud]

Optional: Static GIFs are okay, but interactive previews would be amazing (maybe terminal emulator in browser using web assembly?)

terminal emulator in browser sounds interesting, I think we should target to that approach if it's doable.

[TeseySTD]

Optional: Static GIFs are okay, but interactive previews would be amazing (maybe terminal emulator in browser using web assembly?)

terminal emulator in browser sounds interesting, I think we should target to that approach if it's doable.

I'm not sure, but it seems to me that something like that did Spectre.Console in their docs, using web assembly.

[LittleLittleCloud]

Might be doable

• https://github.com/[phil-scott-78/try-spectre](https://github.com/phil-scott-78/try-spectre)

This approach consumes https://github.com/BattlefieldDuck/XtermBlazor

[TeseySTD]

Might be doable

* [https://github.com/[phil-scott-78/try-spectre](https://github.com/phil-scott-78/try-spectre)](https://github.com/%5Bphil-scott-78/try-spectre%5D(https://github.com/phil-scott-78/try-spectre))

This approach consumes BattlefieldDuck/XtermBlazor

I looked up at html code of Spectre.Console - they used an asciinema-player, the tool for recording terminal sessions and play them, but yeah, it is possible to simulate terminal sessions using web assembly with xterminal.

[ParadiseFallen]

I think we should target to that approach if it's doable

Its defenety doable https://play.avaloniaui.net. It's c# app that runs and even compiles in web. So we can even make repl.

Components can provide it's own dependencies and even services which make life a bit harder.

I would like to focus on RazorConsole itself and impl more features. Running c# in web is doable but consumes much time.
Right now there is not enough building blocks in RazorConsole itself to take time on shadcn like component registry.

[TeseySTD]

I would like to focus on RazorConsole itself and impl more features. Running c# in web is doable but consumes much time.
Right now there is not enough building blocks in RazorConsole itself to take time on shadcn like component registry.

Agree. It is not necessary right now, but as a future goal I think it is great.

[ParadiseFallen]

It can be. yes. Seems like need a roadmap