I thought of that as an option.
But wouldn't this bring a bit of blur in identifying them afterwards in the controllers. Even if we use some slug to identify them.
We define pages as a model.
Then create controllers About, Services, Welcome.
In order to read the page our query should contain something as
Again we compromise the simple
Yes, it's again not that clear as there in the database design there should not be more than 1 about page allowed but to call the method from About object seems so more elegant ?