| |
| |
Foreword | |
| |
| |
| |
ForewordPeng T. Ong | |
| |
| |
Preface | |
| |
| |
Acknowledgments | |
| |
| |
| |
Motivation for Content Management | |
| |
| |
| |
The Internet Changes the Rules of the Game | |
| |
| |
Executive Summary | |
| |
| |
Introduction | |
| |
| |
Overview | |
| |
| |
Fear and Greed | |
| |
| |
Rules of the Game | |
| |
| |
| |
It's the Assets, Stupid! | |
| |
| |
| |
Experiment. Iterate. Grow | |
| |
| |
| |
Respond to Customers Quickly and Frequently, or Lose Them! | |
| |
| |
| |
Enable the Masses! | |
| |
| |
| |
Make It Manageable and Reproducible | |
| |
| |
Summary | |
| |
| |
Roadmap | |
| |
| |
| |
Overview of Content Management | |
| |
| |
Executive Summary | |
| |
| |
From Prototype to Enterprise | |
| |
| |
2 A.M. Software | |
| |
| |
The Pioneers | |
| |
| |
The Tornado | |
| |
| |
Go Dot-com | |
| |
| |
Terminology | |
| |
| |
Universality of Assets | |
| |
| |
Managing Web Assets | |
| |
| |
Live Editing | |
| |
| |
Staging the Web Site | |
| |
| |
Independent Edit Areas | |
| |
| |
Content Management | |
| |
| |
Content Management Architecture | |
| |
| |
Content Creation/Editing Subsystem | |
| |
| |
Repository Subsystem | |
| |
| |
Workflow Subsystem | |
| |
| |
Deployment and Operations Management | |
| |
| |
Summary | |
| |
| |
| |
Concepts and Principles | |
| |
| |
| |
Principles of Collaborative Web Development | |
| |
| |
Executive Summary | |
| |
| |
Introduction | |
| |
| |
Basic Concepts | |
| |
| |
Stakeholder Identification | |
| |
| |
Are We in the Chaos Zone? | |
| |
| |
Development and Production Separation | |
| |
| |
Asset Identification | |
| |
| |
Direct Feedback (WYSIWYG) | |
| |
| |
Parallel Development | |
| |
| |
Versioning | |
| |
| |
Control Mechanisms: Auditing and Enforcement | |
| |
| |
Summary | |
| |
| |
| |
Best Practices for Collaborative Web Development | |
| |
| |
Executive Summary | |
| |
| |
The WSE Paradigm | |
| |
| |
Collaboration Strategies | |
| |
| |
Collaboration Operations | |
| |
| |
Submit Operation | |
| |
| |
Compare Operation | |
| |
| |
Update Operation | |
| |
| |
Merge Operation | |
| |
| |
Publish Operation | |
| |
| |
Work Cycles | |
| |
| |
Version Snapshots | |
| |
| |
Common Work Cycles in Web Development | |
| |
| |
Real-Time Development Work Cycle | |
| |
| |
Compare-Update Work Cycle | |
| |
| |
Review Work Cycle | |
| |
| |
Major Test Work Cycle | |
| |
| |
Summary | |
| |
| |
| |
Templating Empowers Content Contributors | |
| |
| |
Executive Summary | |
| |
| |
Background | |
| |
| |
The Freshness Imperative | |
| |
| |
The Challenge of Change | |
| |
| |
Enabling Change | |
| |
| |
A Template System | |
| |
| |
Example: ezSuggestionBox.com | |
| |
| |
Advantages of a Template System | |
| |
| |
Summary | |
| |
| |
Practitioner's Checklist | |
| |
| |
| |
Workflow Speeds Work Cycles | |
| |
| |
Executive Summary | |
| |
| |
Using Workflow | |
| |
| |
Characteristics of Web Development | |
| |
| |
People Factors | |
| |
| |
Project Factors | |
| |
| |
Process Factors | |
| |
| |
Business Factors | |
| |
| |
Virtual Assembly Line | |
| |
| |
Workflow Concepts | |
| |
| |
Interaction Pattern | |
| |
| |
Tasks | |
| |
| |
Job | |
| |
| |
Transition Links | |
| |
| |
Active and Inactive Tasks | |
| |
| |
Building a Workflow | |
| |
| |
Notification | |
| |
| |
Designing a Workflow | |
| |
| |
| |
Identify Interaction Sequences | |
| |
| |
| |
Identify Candidate Workflow | |
| |
| |
| |
Sketch the Steps | |
| |
| |
| |
Identify Known and Not-Yet-Known Parameters | |
| |
| |
| |
Add Remaining Transitions | |
| |
| |
| |
Add Notification Steps | |
| |
| |
Summary | |
| |
| |
Practitioner's Checklist | |
| |
| |
| |
Deploying Content | |
| |
| |
Executive Summary | |
| |
| |
Introduction | |
| |
| |
Concept Review | |
| |
| |
The Release Agreement | |
| |
| |
Common Pitfalls | |
| |
| |
Continuous Change | |
| |
| |
Database Assets | |
| |
| |
Design Considerations | |
| |
| |
Incremental Changes | |
| |
| |
Making Changes Transactional | |
| |
| |
What Initiates Deployment? | |
| |
| |
Script Integration | |
| |
| |
Rollback | |
| |
| |
Designing a Deployment Infrastructure | |
| |
| |
Enterprise Deployment Architecture | |
| |
| |
Summary | |
| |
| |
Practitioner's Checklist | |
| |
| |
| |
Multiple Web Initiatives | |
| |
| |
Executive Summary | |
| |
| |
Introduction | |
| |
| |
Overview | |
| |
| |
Concepts | |
| |
| |
Logically Independent Web Site | |
| |
| |
Task Overlap | |
| |
| |
Basic Branch Patterns | |
| |
| |
Single-Branch Pattern | |
| |
| |
Agency Pattern | |
| |
| |
Short-Term/Long-Term Branch Pattern | |
| |
| |
Dependent Branch Pattern | |
| |
| |
Identifying Branch Patterns | |
| |
| |
Example--Using Branches in a Dot-Com Company | |
| |
| |
Dependent Web Sites | |
| |
| |
Summary | |
| |
| |
Practitioner's Checklist | |
| |
| |
| |
Design and Implementation | |
| |
| |
| |
Using Web Content Management for Globalization | |
| |
| |
Executive Summary | |
| |
| |
Introduction | |
| |
| |
A Globalization Initiative | |
| |
| |
The Easy Path Leads to Trouble | |
| |
| |
Design a Solid Platform for International Development | |
| |
| |
Branch Structure | |
| |
| |
Work Area Structure | |
| |
| |
Special Situations | |
| |
| |
Workflow Design | |
| |
| |
Template System Design | |
| |
| |
Deployment Design | |
| |
| |
Summary | |
| |
| |
| |
Summary and Conclusions | |
| |
| |
Executive Summary | |
| |
| |
Introduction | |
| |
| |
Revisiting the Rules | |
| |
| |
It's the Assets, Stupid! | |
| |
| |
Experiment. Iterate. Grow | |
| |
| |
Respond to Customers Quickly and Frequently, or Lose Them! | |
| |
| |
Enable the Masses! | |
| |
| |
Make It Manageable and Reproducible | |
| |
| |
Future Trends | |
| |
| |
Content Becomes More Structured | |
| |
| |
Content Contributors and Their Tools Become More Specialized | |
| |
| |
Blurring the Distinction between Web Operations and the Rest of Business | |
| |
| |
More Distributed and Flow-based Handling of Assets, Tasks, and Jobs | |
| |
| |
More Emphasis on Content Tagging to Enable Storage, Retrieval, Search, Reuse, and Routing | |
| |
| |
Emphasize 24 x 7 Management Infrastructure | |
| |
| |
Conclusion | |
| |
| |
| |
Appendices | |
| |
| |
| |
A Smart File System | |
| |
| |
| |
A Workflow Design for Formal Hand Off Between Groups | |
| |
| |
Executive Summary | |
| |
| |
Introduction | |
| |
| |
Requirements | |
| |
| |
QA Hand-off Workflow | |
| |
| |
Summary | |
| |
| |
| |
A Workflow Design for Predetermined Time Schedules | |
| |
| |
Executive Summary | |
| |
| |
Problem Scenario | |
| |
| |
Background | |
| |
| |
Time-Slot Technique | |
| |
| |
Time-Slot Techniques--Detailed Example | |
| |
| |
Discussion | |
| |
| |
Variations on the Time-Slot Technique | |
| |
| |
| |
Basic Process Steps of a Best-Practice Content Management Process | |
| |
| |
Executive Summary | |
| |
| |
Example: Web Site | |
| |
| |
A Best-Practice Development Process | |
| |
| |
Example: Rebranding Initiative | |
| |
| |
Summary | |
| |
| |
Resources | |
| |
| |
Index | |