Administrator and Editor Roles
_____ Decide who will be the site's owner (this must be a faculty or staff member.)
_____ Decide who will be the site's technical lead (administrator), and who will be in charge of updating the site's content on an on-going basis (editor).
_____ Determine whether a workflow (approval process) is needed for content production if there are multiple site editors.
_____ The technical lead(s) should add and manage users, and give them appropriate permissions to contribute, edit, or publish content.
_____ Review Georgia Tech's Web Security Standards and policies.
_____ Determine who will update your website modules and apply security updates on a continual basis. Keeping your Georgia Tech modules and website up to date and secure from hackers is a crucial part of your website. OIT does not offer site maintenance or security patching services, so you will need to handle this yourself, or with an in-house or approved freelance web developer.
_____ Decide who will get security update emails (We recommend using a group email account, in addition to the technical lead's email address.)
_____ Decide on the "FROM" address when the site sends notification emails such as password resets (We recommend using a group email account instead of individual address.)
_____ Insert your department name in the site header, and make sure your footer contains your division's address.
_____ Upload your logo (if using) into the site header. If you need a custom logo, request one from Institute Communications.
Training and Support
_____ Familiarize yourself with the available Drupal Express training, support, and resources.
_____ Read the Drupal Express Editor Handbook to get an understanding of basic concepts and editing functions.
_____ Read and understand Georgia Tech's Accessibility Requirements.
_____ Sign up for Georgia Tech's Drupal listserv and learn how to use the community to get help and post questions.
_____ Schedule a Visual Identity Standards training for all editors through your Institute Communications client manager.
_____ Compare your old site to your new site. Did you cut any pages or change any web addresses (URLs)? If so, you'll need to set up redirects from the old URLs to your new site so that site visitors don't get error messages.
_____ Check that all files such as .pdfs have human-readable file names.
_____ Test that any embedded videos play correctly.
_____ Test all Web forms and ensure they work correctly.
_____ View the website on all the most common browsers (IE Firefox, Chrome, Safari).
Content and Navigation
Navigation and Site Structure
_____ Make sure your site structure is simple and makes sense.
_____ Check that all Web page have been added to a menu.
_____ Check that every Web page URL (web address) is user-friendly and follows your site structure.
_____ Make sure the title of each Web page is brief and clear.
_____ Unpublish any test pages or unnecessary pages.
_____ Be sure that all landing pages contain content.
_____ Check all pages for consistent layout.
_____ Review your text content to see if it follows the Writing for the Web Guide and is easy for web visitors to skim.
_____ Ensure that all content is up-to-date and accurate.
_____ Check that any subheadings used within a page are styled as a "Heading" or "Subheading."
_____ Review content and fix any spelling and grammatical errors.
_____ Ensure your writing style is consistent across the site and follows the Institute Editorial Style Guide.
_____ Check that capitalization (especially for pages, headings, and menus) is consistent across the site.
_____ Review the guidelines for Selecting and Formatting Images for the Web.
_____ Check that all images have alt-text.
_____ If using the GT Carousel, make sure any people that appear on a carousel slide are not covered by the text box.