Site Framework Questions

I am starting to create a project roadmap, and have realized that I am unsure of the different parts of the whole. My future needs might (might not) scale beyond the current method I am using. This project started as a single page website showcasing a map on one side of the page and video associated with it on the other. Now, we have multiple clients that need their own version of this. We started using fat free framework for the application routing and templating. This was fine with two or three sites, because we just copy/pasted the site template and modified links/titles/etc appropriately. Now, though, looking at the potential growth of the project, I would like to upgrade my entire project and make it more sustainable to future growth and changes.

I think I should plan on implementing some sort of cms type backend that lets me set up new sites using variables and fields and select templates and modules as appropriate, while at the same time generating the new routes, groups and memberships automatically. That seems like a quick way to spin up copies of the same site, or even just replace the necessary template/modules/paths/variables/etc based on the user's permissions. However, I don't truly have an understanding of my needs in relationship to today's app development techniques and best practices. I feel like copy/pasting the entire site template folder is dummy proof, but it doesn't feel very conducive to implementing future changes.

I would appreciate any input or guidance on finding resources to help me understand my needs better.

Civil-LInk
I am starting to create a project roadmap, and have realized that I am unsure of the different parts of the whole. My future needs might (might not) scale beyond the current method I am using. This project started as a single page website showcasing a map on one side of the page and video associated with it on the other. Now, we have multiple clients that need their own version of this. We started using fat free framework for the application routing and templating. This was fine with two or three sites, because we just copy/pasted the site template and modified links/titles/etc appropriately. Now, though, looking at the potential growth of the project, I would like to upgrade my entire project and make it more sustainable to future growth and changes.

I think I should plan on implementing some sort of cms type backend that lets me set up new sites using variables and fields and select templates and modules as appropriate, while at the same time generating the new routes, groups and memberships automatically. That seems like a quick way to spin up copies of the same site, or even just replace the necessary template/modules/paths/variables/etc based on the user's permissions. However, I don't truly have an understanding of my needs in relationship to today's app development techniques and best practices. I feel like copy/pasting the entire site template folder is dummy proof, but it doesn't feel very conducive to implementing future changes.

I would appreciate any input or guidance on finding resources to help me understand my needs better.

I can help you in this project. You can consult it with me any time, directly fill your query on the form: https://www.amazing7.com/contact-us.php. I am not pitching you a sale, it's just a consultation method only if you want to discuss with me. And one more thing its not chargeable.