Before our migration to Contribute 3, the College Web Redesing team had a meeting to design our Contribute roles and key structure, with the following results for our key/role design. It illustrates some of the issues involved in designing keys/roles.

COE Keys, Roles, and Naming Convention

 

Key Naming Convention:  EdWebs[<unitName>]<platform><basic|admin|power>

1.  Have folder specific keys for all standard unit users.  These would be called EdWebs<unitName><Win|Mac>Basic and would have the unit home page as the starting point.  Users who could only edit subfolders of a unit, would have AD permissions control that.
2. For advanced users, have one mac and windows power user key that would be used by everyone with the College home page as the starting point.  EdWebs<Mac|Win>Power. This avoids making a separate key with thier unit home page for each unit and assumes power users will have no trouble navigating to their unit's site.
3. Have one mac and windows basic user key that would be used by everyone that has more than one site to edit.  This would have the college home page as the user’s home page, but the user would only be able to edit certain folders.

The only thing power users could do that basic users couldn’t would be create a blank page.  We may never have a power user, but we have it in the design.  It may also be used in the future for people with more library/assets available to them.

Contribute Role Configuration Dialog Boxes

 

This is what a typical unit author would have as their Contribute 3 role configuration. 

General Dialog Box

 

 

 

• Allow User to Publish Files = Checked

• Role Description = descriptive narrative of role

• Home Page for users in this role = generally their unit home page, unless they have more than one unit such as pub specialist, then the coe home page should be used even if they don’t have rights to edit it.

 

Folder/File Access Dialog Box

 

 

• Only Allow editing within these folder = list of folders user has access to.

• Allow users to delete files they have permissions to edit = checked

• Remove rollback versions on delete = unchecked

 

Editing Dialog Box

 

 

• Allow Unrestricted Editing = true

• Protect Scripts and Forms = true

• Paragraphs > Two Lines, as in web page editors = True

• Allow Users to edit web page source in external application = checked

• Allow Users to insert third-party objects = unchecked

• Require Alt Tags = checked

• Use Strong and EM = Checked

• Line Break type = Windows CR LF

 

Styles And Fonts Dialog Box

 

 

• Style Support: Document Level-CSS

• Allow Users to Apply Styles = checked

• Include HTML Heading Styles = checked

• Include CSS in the styles menu = checked

• Show Only CSS in CSS file = /library/css/common_user_applied_styles.css

• Allow Users to apply fonts and sizes = unchecked

• Allow Users to apply bold italic, underline, strikethrough, and fixed width styles = checked

• Allow users to apply font color and background color = unchecked

 

 

New Pages Dialog Box

 

Only check the following:

• Create a new page by copying any page on the web site

• Use dreamweaver templates, show users all templates. 

• Power users and administrators could create a blank page.

 

File Placement Dialog Box

This is a new dialog box for Contribute 3.  These setting say all files go next to the html document they are associated with except images which go in an images subfolder.

 

 

 

All Images Rule:

 

 

All Microsoft and PDF Files Rule:

 

 

All other files Rule:

 

 

 

Shared Assets Dialog Box

 

 

This will contain a list of all shared assets such as image and library items.  To simplify administration, use this list for all roles will be checked.  We may end up explicitly listing assets when assets that only belong to certain users come up.

 

New Images Dialog Box

 

 

These are the default settings except the jpeg quality.  This should not be restricted.