Refresh, Restore, Rescue

Restore, Refresh, Rescue: Group Contract

  • Mission Statement
  1. Organize, recover, and update old digital history projects to enhance accessibility and technology while working to create a central hub to access previous and current projects.
    1. Organize: Sort the old digital history sites into 4 major categories: Fredericksburg, Campus History, and Legacy: which includes Alumni and Historical Figures. These will all be housed on a central “hub” in the form of a new wordpress site we will create
    2. Recover: Identify past sites in need of repair: broken links, html code errors, missing images, etc.
    3. Update: Revisit past sites with accessibility issues and make minor updates to enhance the accessibility: update/add ALT text to images, make sure text and color contrast are reader and screen-reader friendly. 
    4. Expansion: Create a form to enable current and future students to request the addition of their digital history project/site to the hub. [Link to form]
  2. For a full list of the sites we are working with, visit our ADH Spreadsheet.
  • Tools
  • WordPress 
        1. The main site is hosted at:
        2. This site will serve as the central organizational space, or hub, for each of the individual digital history sites. The site will act as an about page and directory for past and present digital history sites to make them more accessible to a wider audience.
  • TimelineJS
        1. We will be using TimelineJS in order to visually demonstrate when the projects were created. Each digital history site is connected to a specific iteration of Dr. McClurken’s Digital History class. The Timeline will be used to show those iterations as well as the evolution of the first digital history sites created for this class until now. 
        1. We will use WAVE to access the accessibility of each website.
  • Audience Plan
  • Spring 2022 History Symposium
        1. This project will be presented at the Spring 2022 History Symposium at the end of the semester. This symposium gathers an audience of fellow history majors as well as staff from the history department, however the symposium is open to the wider campus community as well.
        2. Create QR codes and flyers for students to access the central site during and after the symposium.
  • UMW Library Website
        1. Will contact the library and propose having the organizational hub linked on LibGuides to gather a student audience doing research.
          1. Contact Angie Kemp (
  • Social Media & Email:
        1. Create a Google Form allowing submissions and website requests
        2. Spread awareness via Social Media:
          1. UMW History & American Studies (@umwhisaclub – Instagram)
          2. CDS (@umwcommanddigitalstudies – Instagram)
          3. Historic Preservation (@umwhistoricpresclub – Instagram)
          4. UMW Libraries (@umwlibraries – Twitter)
          5. DKC?
        3. Spread awareness via websites:
          1. History Department Site – Dr. Fernsebner (
          2. Digital Knowledge Center – (
          3. James Farmer Multicultural Center – (
        4. Reach out to above departments to send out our site and Google Form via email to encourage students to explore and contribute to the site
  • Schedule

(Feb 15/Feb17)

  • Complete First Draft of About The Project Page
  • Complete WAVE Assessment of websites
  • Gain full access to websites/Assess how to fix websites
    • Questions to Consider: Will we make separate websites? Will we create subdirectories for the fix? Are these direct fixes? How will we archive the old websites? 
  • Begin adding unbroken websites to website

(Feb 22/Feb 24)

    • Feb 22: Establish more detailed division of labor. 
    • Contact DKC/Faculty about New Websites
      • Potentially create submissions page
    • Feb 24: Begin fixing SubDirectory Websites
    • Feb 24: Begin Contacting Google Form Applicants
    • Feb 24: Complete First Draft of Home Page
  • Feb 24: 7-8 minute progress report

(Feb 27-March 5)

  • Wild Card. 
  • Find other websites to display

(Mar 8/Mar 10)

    • Mar 8: Finish adding unbroken websites 
    • Mar 8: Begin adding fixed websites
    • Mar 8: Begin adding Google Form Websites
    • Mar 8: Begin fixing Direct Websites
    • Mar 10: Check-in on Website Progress. Reassess Fixes.
  • Mar 10: Present 7-8 minute progress report

(Mar 15/Mar 17)

  • Mar 15: Finish Fixing SubDirectory Websites
  • Mar 15: Finish Fixing Direct Websites
  • Mar 17: Finish adding New Websites
WEEK 10 

(Mar 22/Mar 24)

    • Mar 22: Finish TimelineJS of Websites
  • Mar 22: Present 7-8 minute progress report
WEEK 11 

(Mar 29/Mar31)

    • Mar 29: Finish adding New Websites
  • Mar 31: Present 10 minute progress report
WEEK 12 

(Apr 5/Apr 7)

    • Apr 5: Finish adding New Websites
  • April 7th: Project Due
WEEK 13 

(Apr 12/Apr 14)

    • Apr 12: Discuss Revisions by 12th 
  • Apr 14: Present 10 minute progress report
WEEK 14 

(Apr 19/Apr 21)

    • Apr 19: Work on revisions
  • April 21st: Final Revisions Due

(Apr 22)

  • Present full project at the History Symposium


  1. Benchmark 1: Week 8 (3/8)
    1. Make sure functions and is ready to host the other sites
    2. Have at least 2 past project sites recovered; have these placed onto hub: connecting them via link/post on our website under their respective category
      1. Recovered: restoring access to the site, links, and images, fixing any major/critical errors.
    3. Complete the first draft of the “About this Project” page
  2. Benchmark 2: Week 9 (3/15)
    1. Have all *working* past project sites recovered and linked onto site
    2. Evaluate accessibility through Wave
  3. Benchmark 3: Week 10 (5/3)
    1. Supplement the main hub with some analytics and interactive tools (TimelineJS, etc.)
      1. Utilizing Timeline JS to track the projects temporally: both when they were made and what time periods they cover.
      2. Provide a space on the website for students to access the form to add their site to the website
    2. Gain access to other group projects from this semester, load them onto the new hub site
  4. Stretch goals: 
    1. Create analytics about the sites, projects, etc. (Explained in Benchmark 3)
      1. We will tackle this stretch goal if we successfully finish uploading and recovering the previous sites with enough time to begin working on them. 
    2. Potentially house and compile some sites’ information into new websites that organize and combine the original information
      1. Websites that would need major overhaul to make accessible 

  • Division of Labor
Group Member Roles & Responsibilities
Carson Berrier Create the main hub site, once finished, begin to do light work on ADH websites that have not been fixed. Create GoogleForm to have other projects added. Compile and create the information for the “About this Project” page.
Ashley Dimino Create the main hub site, once finished, begin to do light work on ADH websites that have not been fixed. 
Lyndsey Clark Work on recovering old ADH websites, collaborate with DKC on fixing sites, potentially recreate sites to recover old data, and provide feedback on the main hub site.
Eugene Hlaing Work on recovering old ADH websites, collaborate with DKC on fixing sites, potentially recreate sites to recover old data, and provide feedback on the main hub site.