Abstract the entire package into headless components for usability in an existing codebase

[KieronWiltshire]

Preflight Checklist

• I could not find a solution in the existing issues, docs, nor discussions
• I have joined the ZITADEL chat

Describe your problem

The modern component ecosystem seems to be going the route of developing fully functional headless components where the styling of which can be provided by the developer. This is a fully featured hosted platform which when cloned will likely be modified making it harder for developers to update ensuring security long-term.

Describe your ideal solution

As a developer, I want to be able to follow a quick and easy installation guide similar to AuthJS where I can define a route, provide a config and have everything loaded for me.

I believe this could easily be achieved but would require a radical shift in how this repository is developed. I think the solution would be to create a separate SDK which contains all of the utility functions and core functionality which also provides headless UI components. Then this repository could in fact depend on that repository allowing for the self-hosted UI to be extremely configurable, maintainable and also allow others to easily implement it into their existing codebases.

Version

No response

Environment

Self-hosted

Additional Context

No response

[elinashoko]

Thanks for getting in touch @KieronWiltshire I have added it into the product backlog to collect more feedback, we'll be in touch if more community members find this useful.