Hi guys,
In the process of building a modular cms I have come to a point where I am standardising certain parts of the system into the "core" and leaving all extras as modules.
I never had any issues when I was accessing content pages via example.com/content/about-us however it looks a little messy to have the content at a url removed from the root.
So I have created a route that takes the first part after the home url and treats that as a page identifier such as example.com/about-us.
This again works fine but the issue is obviously that any other single part url will be treated as a page. I have a news module which lives at example.com/news however when I access that, the framework treats the /news as a page identifier and on not finding a "news" page it redirects to the homepage.
example.com/news/article/1 etc work fine but any urls with just a single part after the home url are buggered.
What is the standard means of overcoming this. I have tried to explicitly route requests in the respective modules bootstraps but it always uses the default modules routing which invokes the cms instead of a module.
Any help would be massively appreciated.