Responsibilities

The web team supports content on the WSB website, https://business.wisc.edu/. Partners are responsible for maintaining their own event, blog/news, and advisory board content. Documentation and video trainings are available in this wiki under WordPress Site.

Policies & Limits

Users expect a website that is up-to-date, accurate, and relevant. Users also expect a fast and high-performing website. To meet these expectations and create a positive user experience, the following policies are in place:

  1. The web team does not support content that is older than 3 years.
  2. Partners should remove any content older than 5 years on the website. We suggest reviewing your content annually and removing anything older than 5 years or anything no longer accurate or relevant.
    1. There may be a small number of exceptions. For example, if you have a blog post that is older than 5 years that is performing well in organic search or is still shared regularly on social media, then keep it so it continues to drive traffic to the site.
  3. Events are automatically deleted after 2 years.
  4. The WordPress website is not a storage space or archive solution. Do not use WordPress as the only storage place for your content. A copy of your content (text, images, video) should always should be stored in one of campus’s approved storage solutions, such as Google Drive or Box.
  5. View policies specifically for blogs.
  6. All content must follow UW-Madison's digital accessibility policy. All website contributors are responsible for following this policy. If they do not, their access may be removed.
    1. Learn digital accessibility fundamentals.
    2. View UW's Make it Accessible guides.

Making a Request

  1. Reach out to a marketing strategist/manager to initiate a larger project or submit a web ticket for smaller content updates.
  2. Smaller content updates have a two-week turn-around time. All copy and assets must be included in the ticket when you submit it. The team works on requests in the order they are submitted to ensure tickets are completed fairly and in a timely manner for all partners. There is no “skipping the line”, so partners must plan ahead.
  3. Larger web projects can take a month or longer depending on the scope of the project. So plan ahead and reach out to your strategist/manager as early as possible.


  • No labels