Does your app have an admin site?

On my part it depends.

There could be applications which need admin area or moderator area or lets call it role specific areas.

I tread those as separate applications because each of them have a different target audiences.

On the other hand there could also be valid reasons to have admin features.. technically I tread those features the same as premium features.

Basically: a user with a specific permission or role sees more than without it.

A valid reason could be:

• sharing specific admin features with non tech partners.
• having a repeated task where a visual representation in the browser can help (which can not be extracted into a Grafana dashboard).
• something else?

If there is no valid reason I'd skip that instead focus on the applications CLI.

There could be simple commands for:

• managing (create/edit/delete) users.
• managing orders.
• anything.

The benefits I see in CLIs over admin features:

• There is no frontend code, yet which could be exploited. So it feels more secure and due it doesn't need styles it takes less time to build.
• Its much faster to automate commands than API's.
• Anyways once its time to scale (for example one of the valid reasons pop up) its easy to extract CLI tasks into API endpoints.

Sum up:

• CLI for administrative tasks unless there is a valid reason.
• Role specific pages are treated as separate applications because each has its own target audience.
• For dashboard functionalities I recommend Grafana.

I build my own admin.

I am building web app from scratch with Laravel and Vue. I have 3 roles Normal user, Creator(Teacher) and me(Admin). Not everything is ready yet for Admin permissions so sometimes I am using PHPmyAdmin to view data or delete some ugly comments.

I'm building my app using NUXT and building the admin site from scratch. It's very simple at the moment (change user permissions/status). Reminds me that I still need to add management for flagged content.

CHeers!