So I am building my site with a client panel and an admin panel.
What I am trying to figure out, is if it would be easier if i made it where it was just a panel, for example:
https://site.com/panel or https://panel.site.com (either one don't matter) and then just give each user a role (whether isClient or isAdmin) but I will be the only admin on the website.
Or should I separate it out between an admin cp an a client cp, so:
site.com/admin & site.com/client.
Honestly, I am just aiming for the smarter route so I am not remaking a bunch of code that shouldn't have to be. I understand in the end it's my website, but I wanna hear from the experts of what you think I should do.
If you separate the routes i.e. have /admin then you can protect all /admin routes with an admin middleware. This allows you to easier separate views, controllers, etc..
If you use the same routes, controllers and views then you can add the admin features to the views the user sees. For example you could include some buttons in the view if the user is admin.
I think both have their use cases and you just need to decide which one that you like or fits better in your project.
PS. There are other methods as well, these two I think are the most common..
@Twoopa focus on releasing your project,.. if second option seems like a good idea for your project at this moment, go with it.. if and when your project grows out of it, you can then change it to whatever your needs are then..
