Instead of a big flat file and some classes there will be a true layout template, itself making use of "slots", "partials" (template parts), and "components" ... much more modular and maintainable.

Until now I had some administration features, such as editing news posts, as part of the main site. Having a completely separate "backend" application is much better now as the administration parts do not rely on the main site style and layout, I can edit the main site's design without worrying about breaking the admin parts. The backend has basic CRUD features to create and edit entries in the database:



This CRUD doesn't use "scaffolding", which is the generation of form code, but instead generates a configuration at run time based on the database meta data for the tables; and then passes that configuration to the "data table" component which you may already have seen in the Trinity website.



Since the backend uses the same authentication features as the main site, I will be able to add more "credentials" and allow other people to help me manage parts of the site in the future (perhaps moderating the Study area, or editing content in the next version of Trinity).