Make sure you have the correct skill set
Get training or assistance from an experienced WCM Services resource. Many projects fail because customers attempt to use WCM out-of-the-box without obtaining the proper skilled resources.
Analysis, Design and Planning
Starting with good analysis and design is essential to the success of the project! Analysis and design saves time and money by uncovering gaps or problems when they can be more easily resolved as well as creating a more maintainable site. By considering longer term goals the site can be designed so that these can be easily implemented later. Creating a comprehensive project plan is also essential.
General considerations for a Web site include:
- Business objectives
- Operation objectives
- Long term needs
- Users and their objectives
- Site architecture and framework
Specific Web Content Management considerations include:
- Workflow model
- Library architecture
- Authoring and presentation templates
- Deployment architecture
- Security model
- Multiple-location architecture
- Personalization requirements
- Integration with other products
Ensure your WCM environment configuration is ready
Before creating Web Content Management objects, the following steps should be completed:
Apply all relevant fixes. See the support website for details
WebSphere Portal security must be on
The content repository must be configured.
Production environments require a more robust database than the default Cloudscape/derby database to store content.
Set up a workflow
For example, enable workflows on drafts in your library to enforce approval of content. Workflows do not restrict the creation of item types. Do not create workflows on other workflows, workflow stages, or workflow actions.
Create a Web content library
Instead of using the default content library, create a new one. When creating the new content library, assign library permissions and resource types. For example, content creators should not be able to see administration resources.
Use a naming convention
Naming conventions within the site maintain order and helps developers identify components for reuse. Reusing components reduces the number of components that must be maintained.
Use groups for security
It is more efficient to use groups to manage security, rather than assigning security to each individual user. For example, you can have a group for site developers and another for content creators. The site developers will have more control and access than the content creators. A basic group configuration would include, site developers, site administrators, content authors, and content approvers.
Things to consider
Planning for content creation
While the website is being built it is essential that someone is managing the gathering, writing and approval of content. The website can not be launched without it.
Prototype the site and perform usability studies
To validate the site design, conduct usability tests to ensure the site is appropriate for your intended audience. It is easier to identify and fix problems before the development has begun. Even a simple paper prototype is better than nothing at all.
Use a custom launch page
To streamline common authoring tasks during development, create a custom launch page. The custom page can include links to create common content types or to see documents waiting for approval.
Alternative Rich Text Editor (RTE)
Some customers need RTE capability that is not provided out-of-the-box. Consider sourcing an alternative RTE before content entry commences
Consider if the Portal search meets all of your requirements or if a third party search product is required
Guide to running a WCM Requirements workshop
Replacing the out of the box rich text editor
Searching web content