Wake Forest WordPress Team

Revised August 2024


General Overview

This document is a Service Level Agreement (SLA) between the Wake Forest University campus community (Clients) and the Wake Forest WordPress Team (WFWP), documenting the shared WordPress (WP) environment that WFWP provides. It outlines the services and levels of support one can expect from WFWP and the responsibility of those using the services.

The Wake Forest WordPress Governance Group (Governance Group) reviews this agreement each year in January.


Service Description

WFWP offers a shared WordPress environment for departments, organizations, and special interests across Wake Forest University (WFU).

Clients will be given access to their WordPress website with the following pre-configured for them:


Responsibilities

WFWP

Client


Plugin Subscriptions and Other Fees

WFWP

Client


Outside the Scope of This Agreement

WFWP

These guidelines apply to most situations in order to provide a stable, secure, maintainable, and performant environment. The Wake Forest WordPress Team and the WordPress Governance Group will consider outliers and special circumstances on a case-by-case basis. 


Service Commitment

Service Availability

The WFWP environment is available 24 hours a day, 365 days a year, with a target uptime of 99.9% (8,756.25 of 8,765 hours). Regularly scheduled maintenance windows may result in downtime and will be announced in advance to the Client using the WordPress Blog and by email through the WordPress Editors Google Group.

Incidents

In the event of an incident that disrupts WordPress functionality, WFWP and IS are committed to immediate coordination to resolve the issue. Our incident response involves promptly addressing any outage or service degradation until the issue is resolved.

Metrics & Reporting

This section outlines how WFWP will measure and report each commitment made in this SLA:


Service Requests

Please use the Web Request Form for service requests. Individuals making service requests via phone, email, or other methods will be redirected to the Web Request Form so that requests can be appropriately processed, tracked, and completed.

Standard business hours for service requests are between 8:30 a.m.–5 p.m., Monday through Friday, excluding University holidays.

Service Request Response and Resolution Times

For service requests, WFWP aims to provide efficient and timely responses to meet your needs. When a service request is submitted using the Web Request Form, our target response time is within two business days. This ensures that your request is acknowledged and initial steps are taken to promptly address the issue or fulfill the request.

Resolution times for service requests may vary based on their complexity. We strive to achieve resolution within five business days for straightforward requests that do not involve code development or deployment. However, the resolution time can extend from 10 business days to multiple months for more intricate requests, especially those involving code development or deployment. Rest assured, we will communicate estimated timelines as requests are evaluated.


Maintenance 

WFWP 

The WFWP environment will adhere to the following maintenance schedule:


Client

The Client is responsible for maintaining the following:

Archive Process

  1. Site Owners will be notified that they have 30 days to respond to WFWP’s inquiry before their site is archived.
  2. If no response is received within the first five business days, a second email will be sent to the Site Owner requesting a response. 
  3. If no response is received within the first 15 days, all users with Administrator privileges will be emailed together requesting a response. 
  4. If no response is received within five business days of the email to all Administrators, all Editors will be copied on the follow-up email.
  5. If no response is received within 30 days from the Site Owner, Administrators, or Editors, the site will be backed up and archived and public access to it will be cut off. 
  6. Clients may reach out to WFWP and have their sites restored.

Revisions Policy

  • WordPress is configured with a limit of 15 revisions per post or page. Only the 15 most recent revisions to a page will be retained. For more information about revisions, you can read the WordPress documentation here.

Backup Policy

IS manages backups of our AWS Relational Database Service (RDS) and Elastic File System (EFS) with the following standards:

  • Seventy-two hourly snapshots or production and pre-production environments are kept (3 days total).
  • Twenty-one daily snapshots are kept for all environments.
  • Restoring EFS files is a manual change/copy files process.
  • RDS can be restored in place, with no downtime to roll back.
  • S3 buckets are versioning-enabled. Deleted S3 objects are available for retrieval for 60 days before being permanently deleted.
  • Note: Restoring a WordPress website from a database backup can have several implications. Any changes or uploads made to the website after the backup date will be undone when undertaking such a restoration. This includes modifications to content, user interactions, and any updates to themes or plugins. Data generated or collected between the backup and the restoration may also be lost. Considering these factors and carefully assessing the impact on content, functionality, and user engagement is crucial before proceeding with a database restoration.