Discussion: How "Batteries-Included" Should PyWire Be? (Auth, ORMs, Components)

[reecelikesramen]

Currently, PyWire focuses primarily on the presentation and reactivity layer. However, many frameworks (like Django or Laravel) win by providing "batteries included" default ecosystems.

Potential Additions:

• Built-in Auth Declarations: A standardized way to define session management, permissions, and route guards.
• ORM Integration: Should PyWire provide official adapter packages for SQLAlchemy, SQLModel, or Prisma Python?
• Premade Component Suites: A fully supported component suite wrapping something like PicoCSS, Tailwind, or Radix.
• App Templates: Scaffolding out standard archetypes (SaaS, Blog, CMS, Portfolio).

Discussion:
Should PyWire stay focused as a UI library, or should we build out official pywire-auth, pywire-db packages? Where is the sweet spot between modularity and developer velocity?