@nWidart So know I know for sure that the CMS wasn't build in the way I was asking. You are right about the code duplicationm, usually read models should be different than write models (like a CQRS flavor).

Tx for all the patiance

@nWidart OK. So why do say I do not know how HTTP API works? For me it looks to be a little overhead as you you have two php apps that can read MySQL directly

@nWidart I have no idea what are you talking about. So you are not talking about api over HTTP ? Because I saw writing about JWT auth. Those tokens are not for wiring over http? Sorry for miss interpreting your message

I know how a HTTP API works. I do no see why a php APP should conect to mysql through HTTP calls. Why can't we use PHP models that already the framework has?

@nWidart I know JWT auth, I used it for rest api.

So your advice is that my php app should connect to database throught REST API over HTTP?

Ussualy CMS and WEBSITE ar different project. They might be installed on different servers having a common database. The cms might be scaled on some servers with write permission (to MySQL and file repository) . Also authentification might be different on website than the cms.

How would you make this requests "o requests from www to cms API routes for data."?

so in my project I would have: two folders

cms - asgardcms project
www - a different laravel project.

How do I import the models and repositories in my www project?

Is there a way to have the fronent and the backeend as different apps? How do I include my models in my front end app?