Deploying Contribute for a single website with one web server

In this example, Contribute is deployed to a simple intranet consisting of a single web server hosting a departmental website. The website has a single, common root folder with subfolders for individual departments. The site uses Dreamweaver® templates and CSS styles to enforce the look and feel of the website and SSIs to maintain page elements such as navigation menus, headers, and footers.

The key to this arrangement is that all users have the same Contribute site connection. In other words, a single connection point for all users controls the behavior of Contribute when editing the website. To restrict users to editing content in their workgroup’s folder, you would need to create a role that limits access to a specific folder.

An advantage to this type of Contribute deployment is that users in all departments can collaborate by sending pages for review to one another. If separate connections had been created for each department (as in the example Deploying Contribute for multiple websites on one web server), then only the users with access to that folder could receive and edit drafts sent to them for review.

It is important that the Templates folder, which is located at the same level as the Contribute shared settings folder (_mm), is accessible by all users, and the site’s CSS (CSS folder), and server side includes (SSI folder) are protected by role settings that restrict access to those folders. Web pages and associated files stored in these folders cannot be edited using Contribute, preventing them from being inadvertently modified or damaged. To restrict users to editing content in their workgroup’s folder, create a role that limits access to a specific folder.

View full size graphic