Web site advisory panel meeting 1


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Web site advisory panel meeting 1

  1. 1. Purpose of New Site.<br />RCS 2.0.<br />Create an online presence that revolutionizes the way stakeholders communicate with and within Richmond Community Schools.<br />
  2. 2. Five Key Roles<br />Key Principals:<br /><ul><li>What do YOU want?
  3. 3. Built with End User in mind</li></ul>Student<br /><ul><li>Any Time Learning
  4. 4. E-Portfolios</li></ul>Community<br /><ul><li>Immerse in our culture
  5. 5. Bring your student here!</li></ul>Parent<br /><ul><li>Do you know…</li></ul>Faculty<br /><ul><li>What do you want to do…</li></ul>Staff and Administration<br /><ul><li>How can we serve you…</li></li></ul><li>RCS Site Concerns<br />Goals.<br />New Taxonomy<br />Main categories<br />From Linden Dennis<br /> <br /><ul><li>Website has become so very very cluttered and unorganized.Staff links are in several places - such as email, paystub. There does not seem to be any pattern of grouping of links. 
  6. 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. 7. Students just type in google rather than scrolling down to the google link. 
  8. 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. 9. Dates for upcoming events need to be front and center of page, and then the "pat on the back" stuff. 
  10. 10. Events need to be taken down when they are done.
  11. 11. I am curious - where do most of the hits come from - inside or out?  And how long is the average stay?</li></li></ul><li>Analytics<br />Google Analytics http://www.google.com/analytics<br />
  12. 12. Analytics <br />Google Analytics http://www.google.com/analytics<br />
  13. 13. Design Phases.<br />Seven Phases.<br />Vision<br />Blueprinting<br />Development<br />Quality Assurance<br />Launch<br />Publicity<br />Maintenance<br />
  14. 14. Key Areas.<br />Target Audiences<br />Primary visitor motivations<br />
  15. 15. Site Reviews<br />Goals.<br />Identify sites<br />Identify Web parts<br />Plano Independent School District<br />http://www.pisd.edu/<br /> <br /><ul><li>This is my favorite. Big, clear pictures that rotate, all positive messages on the home page, easy to find tabs for more information. Lots of white space to 'lighten' the look.
  16. 16. RCS site has so much red and black and waaaay too much info on each page.</li></ul>Vail Mountain School<br />http://www.vms.edu/default.aspx<br /> <br /><ul><li>Cool movement feature 
  17. 17. The page is simple, but drop down menus contain info</li></li></ul><li>Site Reviews<br />Goals.<br />Identify sites<br />Identify Web parts<br />HamiltonSoutheastern<br />http://www.hse.k12.in.us/<br />Greenwood Central<br />http://www.cg.wnyric.org/cg/site/default.asp<br /> I like the shortcuts<br />Greenville City<br />http://www.greenville.k12.oh.us/<br />I don't like the overall site... but I like the blogspot!<br />
  18. 18. New Site Features<br />Maintaining confidentiality of records.<br />Maintaining confidentiality of conversations and correspondence within intra-school collaboration.<br />Storage and archiving of all data and correspondence.<br />Ease of use.<br />Restructuring of the RCS Web site taxonomy.<br />Creation of portals for faculty, staff, admin, community, and students.<br />User dashboards.<br />Sharing of files.<br />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.<br />Full-backup and restore capabilities within the district.<br />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.<br />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.<br />Provide C3 security (the government uses this requirement as well) of user accounts and logins. <br />Tracking of login attempts.<br />Capabilities to include embedded video and sound.<br />Platform to publish and retrieve podcasts done for and by students.<br />Platform to publish and retrieve podcasts for professional development events.<br />Platform for distributing corporate-wide video announcements.<br />Enterprise search features.<br />Centralized storage of all information within the web environment.<br />Integration of SQL databases, including capabilities to interface with our PowerSchool student information system.<br />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.<br />Integration of Web 2.0 and Web 3.0 features.<br />Full integration of Exchange System e-mail services (e-mail).<br />Document repository, including check-in check-out services, archiving, date stamps, and integration with Microsoft Office.<br />Creation and maintenance of a robust corporate-wide calendar and scheduling feature.<br />
  19. 19. Next Steps.<br />PBWorkshttp://wertech.pbworks.com/<br />Site recommendations<br />Vendor contract<br />