[RFC] Restructuring templUI Component Package Organization

[axzilla]

Hey templUI community! 👋

I'm considering a significant architecture change for templUI before we hit v1.0, and I'd love your input on this decision.

The Proposal

Current approach:

import "github.com/axzilla/templui/components"

components.Button(components.ButtonProps{...})

Proposed approach:

import "github.com/axzilla/templui/components/button"

button.Root(button.RootProps{...})

This was [previously suggested in issue #108](#108), and after further consideration, I think it makes a lot of sense for our project's direction.

Why Consider This Change?

1. Better for copy-paste approach: Clearer dependencies when users copy components directly into their projects
2. CLI-friendly: Future templui add button command could easily identify and include all required dependencies
3. Selective imports: Users only need to import components they actually use
4. Clearer dependency graph: Makes it obvious which components depend on others
5. Better aligned with shadcn/ui philosophy: Components as source code rather than black-box library

Potential Drawbacks

• More import statements required
• Slightly more complex package structure
• Requires a breaking change (but we're pre-1.0, so now is the time!)

Questions for the Community

• Do you prefer the current flat structure or the proposed component-specific imports?
• Would this change make templUI more or less convenient for your workflow?
• Any concerns about the migration process if you're already using templUI?

Since we're still pre-1.0, this is the ideal time to make such architectural decisions before too many users depend on the current structure.

Looking forward to your thoughts!

[DianaSuvorova]

I love the Components as source code rather than black-box library whether one choses to use it as a library or copy the source code, this totally makes sense as a guiding principle.

[axzilla]

Implement with #119