Now that we can create and edit templates from the UI and serve them with our own resolver, we’re ready to take it to the next level. Let’s use our templater tooling as a simple content-management system (CMS).
We already can create, update, and delete templates by accessing /sql_templates; now we need to expose them depending on the accessed URL.
To achieve this, let’s map all requests under /cms/* to a controller that will use our resolver to find the template in the database, and render them back to the client. A request at /cms/about should render a SqlTemplate stored in the database with path equals to about.
We can implement this functionality with a few lines of code. Let’s start ...