CMS Storage Systems

CMS Storage Systems

How do you prefer to manage the contents of your site ,

XSLT , SQL , Sharepoint or ... or maybe a mixed version ,

For example you have articles , products , blogs

I saw in different codes that every developer used a different mechanism to store their data , What is yours ? what do you prefer in different cases ? what is the reason ?

Maybe I use Databases for all kind of data , if so what will be the weaknesses of doing so ?

With using databases as a whole solution for everything in the site , we can search our data , analyze the data from any point that we want , getting the statistics and any kind of processing through our data will be possible .

I'm not very familiar with sharepoint because I was busy with other technologies , just I had a glance look at it

thanks for your participation

Edited : -------------- I hope more people to come and give their point of views , thanks

Emulate IDispatchEx in C#


How does the Presentation-/ViewModel for a Task or Dialog look like?
I have designed a bespoke CMS system that holds data in a database then 'publishes' it to xml.

Are design patterns something you invent as you go
The XML is then used with xslt templates to display the pages which are then cached for speed..
How many types should be implementing the Repository pattern?
I'd be interesting to know if anyone else is doing something similar..
Trouble with Factory and dynamic allocation in C++
Is the Factory pattern useful outside a framework without Visitor?

How to extend this simple DataMapper?

How to remove objects from an Enumerable collection in a loop [duplicate]


I think a database offers the best overall solution for storing data in a CMS.

It does have some drawbacks, but so do all the other storage alternatives on the market.. I've blogged a bit about content modeling and how the different storage technologies impact how you can define your content model:

94 out of 100 based on 74 user ratings 574 reviews