1. Purpose of New Site. RCS 2.0. Create an online presence that revolutionizes the way stakeholders communicate with and within Richmond Community Schools.

6. I would like to see categories with drop-downs such as for students, staff, parents. Students drop-downs could include power school, media center, and search engines.

7. Students just type in google rather than scrolling down to the google link.

8. Home link is not easily identified on other pages. Several people have mentioned that they did not know that little icon was linked back to home.

9. Dates for upcoming events need to be front and center of page, and then the "pat on the back" stuff.

10. Events need to be taken down when they are done.

12. Analytics Google Analytics http://www.google.com/analytics

13. Design Phases. Seven Phases. Vision Blueprinting Development Quality Assurance Launch Publicity Maintenance

14. Key Areas. Target Audiences Primary visitor motivations

18. New Site Features Maintaining confidentiality of records. Maintaining confidentiality of conversations and correspondence within intra-school collaboration. Storage and archiving of all data and correspondence. Ease of use. Restructuring of the RCS Web site taxonomy. Creation of portals for faculty, staff, admin, community, and students. User dashboards. Sharing of files. Availability of embedded wikis and blogs. We want to be able to store and archive content from these systems. These environments would be for public and intra-district collaboration. Full-backup and restore capabilities within the district. Dynamic staff and faculty directory. These would include forward- and rear-facing features. For example, the public and staff could see pictures, general bios, and other public information about teachers and staff (forward-facing). For the rear-facing site, confidential and staff only features would be available. Integration with our corporate Active Directory system to ensure all user names and passwords are updated dynamically. This way we do not have to manually input user names and passwords. We have a central place to store that information (AD) and only have to do it once. Provide C3 security (the government uses this requirement as well) of user accounts and logins. Tracking of login attempts. Capabilities to include embedded video and sound. Platform to publish and retrieve podcasts done for and by students. Platform to publish and retrieve podcasts for professional development events. Platform for distributing corporate-wide video announcements. Enterprise search features. Centralized storage of all information within the web environment. Integration of SQL databases, including capabilities to interface with our PowerSchool student information system. Self-management of user dashboards and portals. In short, we want each user to control their own environment, either by using a template that is provided or be able to customize it. Integration of Web 2.0 and Web 3.0 features. Full integration of Exchange System e-mail services (e-mail). Document repository, including check-in check-out services, archiving, date stamps, and integration with Microsoft Office. Creation and maintenance of a robust corporate-wide calendar and scheduling feature.

19. Next Steps. PBWorkshttp://wertech.pbworks.com/ Site recommendations Vendor contract