In the previous example you created a web project folder and imported the SomeCo web site. For some sites, that may be enough. In a bare bones implementation, once the site is migrated to the repository, life continues pretty much as normal. Content providers use authoring tools to save content via CIFS or edit content directly in the web client, and the system handles review and approval, snapshots, and deployment.
The next step for many people, however, is to identify subsections of the site that lend themselves to being managed through web forms. Web forms allow non-technical content owners to manage, approve, and deploy their own web content. Good candidates for web forms include content that:
Is managed by non-technical content owners. Technical people such as designers, developers, and technical writers are not the target audience for web forms.
Changes fairly often. You don't want to go to the trouble of creating templates if the content is created once and never changed...