The scenario in this chapter involves the creation a fictional website for Plutonia Incorporated . Stan has been appointed the task of creating the public website for Plutonia to give the public online information on its products, research, and news. Stan is also busy as head of the Products department and does not want to presume anything about the Research and Public Relations (PR) departments, so he needs to delegate responsibility for content to the departments themselves. Yet, he also needs to make sure that the site looks and behaves similarly at all points, and some common, consistent information needs to be displayed on all pages. He also needs the ability to make any change at any location.
Each department is responsible for its own content. Each department has varied groups and committees overseeing different areas of that department. Finally, each department requires individual control over who can be assigned privileges to add and manage contents in their sub-areas.
Stan has already installed Zope at http://plutonia.com/Plutonia . As of now, the objects contained in the Plutonia Folder are those standard to the particular Zope installation.
For the purposes of this tutorial, let us shorten the URL. That is, presuming that your Zope is installed at http://your.place.com/Objects and its management screen is at http://your.place.com/Objects/manage , you will use /manage as shorthand for the latter. So follow along as we do the following with Stan:
Design and implement a skeleton site: In this step, Stan creates the basic elements that the site will be built on: documents, images, and folders. Since a skeleton site needs to be seen by others quickly, Stan gives only enough to show what will be coming.
Set up access rights and create basic content: In this step, we start a Session. A session allows Stan to work directly on the site in private. None of the changes he makes to the site will be seen by the public until he says so. Now, he can start working on the real content of the site and assigning security privileges without worrying about exposing broken and in-progress work. Right away, Stan organizes some of the basic content that all of the sites will be able to use. He also gives access to the PR and Research departments for their respective folders.
Previous Chapter | Next Chapter | Up | Next Section | Contents