Parodying the “Coke is it” saying may be a stupid way to title but there you go. Without a DRY (Don’t Repeat Yourself) approach the likelihood of content being wrong or time being wasted is significantly increased.
As with many rules, they are are best if applied via your thumb. I don’t start off a project by rushing to see how I can DRY my content, I instead keep a weather-eye for content that looks like it is going to need to be repeated[1]. Then I will see if a DRY content policy needs to be put in place. And again, such a policy need not be draconian.
If you would like to discuss the benefits of a DRY approach to content management, drop me a line.
[1]I do invariably ensure SSIs (Server Side Includes) are part of a design. This is an aspect of DRY design I hold dear. So while I may employ SSIs almost always to keep my sites scrummy, I am more open minded as to whether page content needs to be delivered by a DRY approach.
