After defining the project and creating an analysis document, you define the requirements of web content system in a design document. The design document outlines what types of content will be needed for site, how they will be structured, how content will be authored, and what the final website will look like.
Your technical architects define what web content environments are required for system and the servers required for each environment. This information ensures that you have fully resourced the hardware required to support web content system
The security architecture describes what groups are required for site and what access is required for different groups to the authoring portlet and rendered website.
The authoring architecture describes what types of content will be required for the site and what change management strategies will be applied when updating content and design. You will need to define what authoring templates are required for system, what workflows will be used to manage changes and what folders will be used to group items in the authoring portlet.
The content acquisition architecture is used to define what existing content will be imported into web content system, how it will be imported, and what content will need to be created.
There are a set of tasks that you need to plan for that will maintain the health and integrity of web content system. Your technical architect and database architect need to define what maintenance procedures are required for system, and when and how often they need to be run.