Rachel Lovinger:

It’s impor­tant to under­stand that most CMSs have a bias. They’re often designed around a cer­tain “unit” of con­tent and that’s what they’re opti­mized to cre­ate. For blog appli­ca­tions, the unit is a post. For Share­point, a unit is a doc­u­ment. For most web con­tent man­age­ment tools a unit is a web­page, even though we’re more likely to be mak­ing dynamic sites that use (and reuse) con­tent in a vari­ety of configurations.

Most CMSs, but not all. There are many rea­sons to love Sym­phony CMS, but this is one of the eas­i­est for new users to grasp: there are no pre­con­ceived notions of con­tent struc­ture, and Sym­phony makes it dead sim­ple to quickly cre­ate a model to match your exact needs. If your CMS is forc­ing you to use its markup or its data model, it’s doing it wrong.