I currently have a WinForms app that uses XML documents to drive dynamic content that is shown to the user. I call these XML documents template files.
The template file determines the features the user sees, the properties, what type of control to use for the property, the drop items in the combo boxes and how to validate the input. I could go on with the dynamic content the template determines but you get the picture. The template drives the app, and the template file that is used by the program is determined when the user indicates which county they are interested in.
This is done because the app helps users submit engineering data to individual councils or counties. Each county has their own set of requirements, the information they need from the user and how best to validate that date.
So to solve this I put the information for each county in their own template file, the user selects the county they are working for and then from that point forward the program uses that county's template file to dynamically build the content in the forms and displays it to the user.
I am now moving the app to the web. My question is: is this technique of using an XML template file for each county to dynamically build the content the best way to do this for websites? I was wondering if anyone knows of a popular design pattern for websites to generate dynamic content for many different counties without having to build a different set of concrete web pages for each county? Or should I stay with the template file paradigm (i.e. if it ain't broken ...)?