 Support re-use of organizational assets. |
| Capitalizing on the current infrastructure increases the payback from previous investments |
| |
| Integrate out-of-the-box with existing technologies. |
| Precious time can be lost when integration requires a lengthy customization process |
| |
| Be built on industry standard technologies with open interfaces. |
| Keep your options open, because new solutions are always forthcoming |
| |
| Support for evolving business needs |
When change is the only constant, it is important to plan accordingly. Solutions that cannot accommodate new site features and functionality will quickly have to be replaced. Support for such things as multiple browser devices, a greater degree of personalization, or yet-to-be developed Web technologies are all important considerations. |
| |
To plan for the future, select a Web content management solution that: |
| |
| Has content component architecture. |
When content is separated from format, it is easier to re-use. |
| |
| Uses an open, Object-based API. |
An open interface provides compatibility with new or emerging technologies |
| |
| Avoids using proprietary technologies. |
A proprietary technology limits your organization's site enhancements to those supported by your vendor. Why be limited by the capabilities and interests of a single vendor. s development team? |
| |
| Supports diverse browsing devices |
Soon Web browsing will take many forms, from PDAs to cell phones. You’ll want to ensure that your site looks right regardless of how a user accesses it |
| |
