Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a multi tenant ASP.NET MVC website and all client specific text is stored in resource files. Every time someone wants to change text I have to jump through hoops and fill out forms and let someone else put it in production. This was fine with 2 clients, but now we have 6 and are looking to roll out to 40+. I can't spend all day making text changes!

Does anyone have any advice on how to make life eaiser? I was thinking a CMS may not work because as far as i know most CMS's idea of multitenancy is to add an additional independent site. We frequently roll out new features and I fear I'll be in the same boat adding modules and updating 40+ sites. I prefer one site with different text if I can.

Any help is most appreciated!

share|improve this question

migrated from Oct 4 '11 at 20:29

This question came from our site for professional and enthusiast programmers.

There are CMS's that support multi-tenancy. It's also sometimes called multi-site management. Here is a related StackOverflow question:… – Gabe Oct 4 '11 at 2:46
It doesn't have to be a database - it needs to be a shared store, be it a relational database, NoSQL or XML file. – CodeART Oct 31 '12 at 0:16
up vote 5 down vote accepted

Yes, you certainly should store all client modifiable content into the database (or accessed via the database) so that the clients can maintain this for themselves.

You will need to spend some time writing the admin functions but you will reap the rewards in the long run. You are right you cannot have the situation where all changes need to go through the developers. You will end up spending all your time updating the sites.

You can, and probably should, introduce the changes gradually. Each time someone wants to change something add it (and a few related things) to the admin pages. That way you'll only have admin for the things that people actually want to change and not for the rest.

A few years ago I worked for a company producing themed sites for local papers and when I started there were few admin pages for these sites and my team were in the same position as you. I gradually introduced admin pages and everybody was happy. The team was happy as they could concentrate on development, the clients were happy as they could get their site updated when they wanted, the management were happy as the clients were happy.

share|improve this answer
This sounds like the direction we are going. That's a great tip about introducing the changes gradually, it's something I can take to management! – Gary Green Oct 4 '11 at 22:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.