Tuesday, May 18. 2010Creating Content Site RequirementsCore site content management system projects are incredibly common, but they are also often drawn out and painful. They're complicated projects because they often have a large number of stakeholders across different parts of the company. They can be a key part of digital or broader strategies, but also used for the most minor parts of day-to-day business. This mix makes it very difficult to tease out the essential aspects of the site, leading to a series of disappointing upgrades and replacements. A successful CMS project begins with a good vision for the end result, which is expressed as a good set of requirements. Where most projects fall down is not in gathering enough requirements, but in gathering the right ones - and that's all about finding the real business value. Continue reading "Creating Content Site Requirements"
Posted by Ian Barber
at
10:03
| Comments (2)
| Trackbacks (0)
Defined tags for this entry: business, cms, cms selection, compatibility, content management, content management system, enterprise, project, project management, requirements, technology choice
Thursday, February 7. 2008Backward compatibility, bane of the developer
Recently 'A List Apart' posted an article about the new X-UA-Compatible switch that Microsoft will be implementing in Internet Explorer 8.
In short, you can target versions of the IE renderer with the switch; you can say: I want this page to be rendered like IE7 would render it and then IE8 (and IE9 and IE10 presumably) would render it similarly to IE7. Now this provoked a lot of reactions, and it got me thinking about one of the most painful subjects among developers (PHP and in general): backward compatibility. Continue reading "Backward compatibility, bane of the developer"
Posted by Boy Baukema
at
13:41
| Comment (1)
| Trackback (1)
Defined tags for this entry: api, architecture, compatibility, development, php, release management, unittest
(Page 1 of 1, totaling 2 entries)
|
Blog
