Elements may have different steps in creation, review, revision, approval, integration, test, and deployment. Workflow varies depending on the data type, time period, and operational status. Each individual on the Web team has an automated work list of assigned tasks and components. Different classes of development-time users are given sets of privileges to view, edit, or approve components, and create new processes. These enable the separation of form from content to allow for management of the site's look and feel.
Templates enable design changes to a class of pages without having to manually edit each one.
At run time, pages can be dynamically assembled from components retrieved from the repository. Deployment and replication. Large Web-site operations not only have many developers and authors, but also many runtime systems, sometimes in multiple locations. Replicating and updating the finished content from development systems to multiple runtime systems is a subject unto itself. Content must be deployed in a secure, scheduled process that can be rolled back if an error occurs during transfer.