-
-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Admin site #819
Comments
You're correct. the big question is, what UI to use on the admin.
|
The Apis are the important part here imo. Together with the OpenAPI implementation it will be fairly easy to implement yourself no matter if you do backend templating or use a frontend framework. I think it’s too early to generate Ui parts. |
I agree with @Sillyvan here. I think focusing our efforts on getting the API generation right is more important than creating a frontend first. I think there can be lots of opinions on how the frontend should be created, but all that is easier to handle once we have a robust API. I think going with the API generation first should also allow us to get a part of this feature out sooner? I.e. an endpoint for admins to access. At least in my mind I think it should be simpler than creating a proper UI generation framework that would work across all data types. |
+1 for the API implementation providing a free OpenAPI spec generation; if there's a standard endpoint like Fastapis OpenAPI endpoint then putting in a useful UI such as swagger or redoc is as simple as a cdn link. |
Hi! I think a lot of people want to know whether an autogenerated admin site is in the cards for this. It's a huge feature that makes a lot of difference when getting something off the ground.
(A lot of the views on the site I'm working on right now would have been unnecessary if there had been something of an admin).
The text was updated successfully, but these errors were encountered: