Scenario 2: Adding a new site area
This scenario covers the simple example of adding a new site area to a live site. It will be hidden by using security settings until it is ready to go live.
In this example, a company has decided that its News section has grown too large and they want to add an “Archived news” section as well. The following changes will be needed
- A new site area called Archived news
- A new content page called Archived news
- A new category called Archived news
- A new menu called Archived news
The company has two libraries as they have separated their content from the design.
- Internet Content – Contains content and workflows
- Internet Design – Contains the remaining elements, such as presentation and authoring templates, components & categories.
For this scenario a full analysis and design document may not be required due to the size of the change. For a larger project refer to Scenario 2. It is still important to document the changes that are required though in a simpler version of an analysis and design document. It may include the following.
- Where in the site structure will the new site area be created?
- What security is required on the site during development when it needs to be hidden?
- What security is required on the site once it is ready to be launched?
- Where in the taxonomy will the new category be created?
- What settings will the new menu need to display the archived news? Will it work from just the category?
- What authoring template and values will the new archived news web page need? Are there any new images required?
The developer will make all the required changes to the design library on the authoring server. By using security the changes can remain hidden until they are ready to be launched.
In our example the steps are:
1. Create the new site area. Set the Manager access to the website administrator
group. Set the Editor access to the website site developer
group. Ensure that the User and Contributor access is not set and that inheritance is turned off. When you preview the website only those people in the administrator and site developer groups will be able to see the site area.
2. Create a new piece of content that will be the landing page for the new site area. Save it into the new site area.
3. Change the default content of the new site area to the landing page.
4. Create the new archived news category and archived news menu.
5. Place the menu on the landing page (how to do this will be determined in the analysis and will be different for individual websites)
6. Change the category of some of the old news to have the new archived news category.
7. Test that everything is working and the content appears on the archived news page.
Roll-out & going live
Once all the changes have been completed and tested on the authoring server it is time to change the security. Since syndication hasn’t been stopped the changes will have been syndicated out to the live site already. They are just hidden due to the security settings.
The security on the new site area needs to be changed. In this example the inheritance just needs to be turned back on and the [All User] group will be inherited from the site.
Once the change has been syndicated to the production server the new site area will be live.