Master Table of Contents for
Redbooks wiki - Building a website using WCM 6.1
Part
I – Introduction
1.
Introduction
1.1.
Web Site Fundamentals
1.2.
Why am I building a web site?
1.2.1.1.
Setting objectives and measuring them
1.2.2.
People involved in a web site
1.2.2.1.
Business Owners
1.2.2.2.
Corporate Communications and Marketing
1.2.2.3.
Graphic Designers
1.2.2.4.
Information Architects
1.2.2.5.
Infrastructure Engineers and Operations
1.2.2.6.
Content Authors and Approvers
1.2.2.7.
Consumers
1.2.3.
Why web sites fail?
1.3.
Web Content Management within the greater context
of Content Management
1.3.1.
What is WCM?
1.3.2.
Do you need a WCM system?
1.4.
Overview of Key new features in WCM 6.1
Part
II – Architecture and Design
2. Architecture and Design
2.1. Architectural Frameworks for Content
2.1.1. Pre-rendering introduction
2.2. Information Architecture (IA)
2.2.1. Defining the Information Architecture
- What is IA, or why websites don’t fall down
2.2.1.1. Base examples of good Information Architecture
2.2.1.1.1. Analysis of the wireframe diagrams
for River Bend Tea and Coffee sample site
2.2.1.2. Results of an inadequate Information
Architecture
2.2.2. Key Considerations and Decision Processes
- Matching Consumer Needs to your Website
2.2.2.1. Understanding the goals
2.2.2.2. Understand Your Audience
2.2.2.3. Consider objectives and key success
factors
2.2.2.4. Find the killer app
2.2.2.5. Consider a user-centric design
2.2.2.6. Define use case scenarios
2.2.2.7. Plan the site framework and site areas
2.2.2.8. Metadata, keywords, and categories
2.2.2.9. Determining the components of the Web
site
2.2.2.10. Using Workflow and Syndication
2.2.2.11. Using Syndication
2.2.3. Information Design
2.2.3.1. Using Presentation Templates
2.2.3.2. Using Site Navigators
2.2.3.3. Using Menus
2.2.3.4. Using Direct Feature Links
2.2.3.5. Using Embedded HyperLinks
2.2.3.6. Using Search
2.2.4. Site Acceptance
2.2.5. Workshop Approach
2.3. Introduction to Personalization
2.4. Search Optimization (Considerations in
IA)
2.5. Design and layout
2.5.1. Usability
2.5.2. Accesibility
2.5.2.1. Why it's important for everyone
2.5.2.2. Standards: W3C WAI, Section 508, etc
2.5.2.3. Testing tools
2.5.3. Navigational Wireframes – more than
just pretty PhotoShop screenshots
2.6. Environment Types
2.7. Sample physical architectures
2.8. Example Infrastructure for the River Bend
Tea and Coffee Company Vasu
Part
III – Building a sample site
3. Building a Site
3.1. Basic steps to Content Creation
3.1.1. End2End overview of the sample site to
be created
3.1.2. Overview of key concepts and terminology
for WCM Components
3.2. Site Dissection
3.2.1. Creating an IA in WCM
3.2.2. Working with libraries
3.2.3. The site framework
3.2.4. Taxonomies and categories
3.2.5. Introduction to Workflow for the River
Bend site
3.2.6. Authoring templates
3.2.7. Creating Components
3.2.7.1. Image Components
3.2.7.2. HTML Component
3.2.7.3. Authoring Tool Component
3.2.7.4. Navigator Component
3.2.7.5. Menu Component
3.2.7.6. Personalization Component
3.2.7.7. Page Navigation Component
3.2.8. Using StyleSheets
3.3. Defining style and navigation
3.3.1. Presentation templates
3.3.2. Navigator and Menus
3.3.3. Navigators and Portal integration
3.4. Managing the publishing process
3.4.1. Understanding Security in WCM
3.4.1.1. Security levels in WCM
3.4.2. Workflow - creating a basic workflow
for River Bend
3.4.2.1. Creating a basic workflow
3.4.2.2. Custom workflow actions
3.4.3. Using collaborative editing tools -
versioning, link management and locks
3.4.4. Previewing content
3.4.5. Managing components
3.4.5.1. Sample usages for each component type
3.5. Personalizing your site
3.5.1. Creating a personalization rule
3.5.2. Configuring the Personalized List portal
3.5.3. Creating the Personalization Component
3.5.4. Using campaigns
3.6. Internationalization
3.6.1. Sites, content authoring, workflow
3.7. Search Functionality in Portal and WCM
3.7.1. Making RiverBend Content Searchable
3.7.2. Adding Search Components to the RiverBend
Site
Part
IV – Expand your WCM Environment
4. Expand your WCM environment
4.1. Personalize your authoring tools
4.1.1. In-line editing
4.1.2. Remote actions
4.1.3. Launch jsp
4.1.4. Custom content elements
4.1.5. Rich-text editors
4.2. Integrating with other systems
4.2.1. Portal document manager and WCM 6.1
4.2.2. ECM integration
4.3. WCM and beyond
4.3.1. WCM APIs introduction
4.3.1.1. WCM API
4.3.1.2. Library API
4.3.1.3. Syndication API
4.3.2. API samples
4.3.3. WCM tag libraries
4.3.4. API Best practices
Part
V – Site Administration and Operations
5. Site Administration and Operations
5.1. Site Administration
5.1.1. Library management
5.1.1.1. Access control
5.1.1.2. Version management
5.1.1.3. Exporting and importing libraries
5.1.1.4. Deleting libraries
5.1.2. Syndication
5.1.2.1. How syndication works
5.1.2.2. Setting up syndication
5.1.2.3. Scheduling
5.1.2.4. Monitoring progress
5.1.2.5. Managing different LDAPs
5.2. Deployment
5.2.1. Rendering Environments
5.2.1.1. Local Rendering
5.2.1.2. Remote Rendering
5.2.2. Authoring Environments
5.2.2.1. Typical Authoring environment
5.2.2.2. Separating Content and Design Editing
with optional design review
5.2.2.3. Advanced Previewing of draft content
in the context of WebSphere Portal
5.2.2.4. Combined Separate Design Editing and
In-Context Draft Preview
5.2.2.5. Geographically distributed authoring
5.2.3. Delivery Environments
5.2.3.1. Dynamic vs. Prerendering – environment
5.2.4. Multiple LDAP Environments
5.2.5. User Partitioning
5.2.6. Best practices
5.2.7. Go live Preparation
5.2.7.1. Tuning considerations – River
Bend example
5.2.7.2. Other WCM Tuning Best Practices
5.2.7.3. Caching