Open to a way of standardising module UI?

[danieltharris]

First of all this is a great project, we are building out some modules on the .NET 10 version that we plan to incorporate into our products as re-usable.

Question for @iammukeshm on whether there's any plans, or are you open to suggestions as to how we could have a standard approach for shipping UI that accompanies custom modules?

It would be useful if the Identity module for example, made the Login page easier to drop into a totally new project, instead of relying on starting from Playground or copy and pasting. There's some key UI and BFF code that lives within playground itself.

There's the building blocks for general UI Components which are great and very quick and easy to use. But it would be great to make it quicker to go from project --> New to having the core FSH.

Last I checked the CLI tool didn't include the UI for login etc, so maybe that's somewhere it could go for now.

But a more holistic approach that could be applied as a standard across modules, giving us a way to ship module UI in addition to Endpoints feels like it would be really useful and provide nice DX

Happy to work on this or present possible options/ideas if it's something you are open to, but if this is not a direction you want the project to go towards then that is understandable.

I guess I am envisioning something where we can easily ship community built models in future with limited friction.