Explore UAB

Preliminary Joomla Website Audit Checklist

As part of the migration from Joomla to Drupal, each unit is being asked to complete a preliminary website audit to help prepare their site for migration, while also identifying risks and understanding the cleanup required for each site.

The preliminary audit is focused on:

  • Identifying and completing easy website cleanup opportunities
  • Identifying stakeholders and assigning responsibilities for audit activities

A more detailed content audit will be required later in the project using the centralized Content Audit Dashboard. Additional communication will be shared regarding the timing.


1. Assign Migration Roles & Responsibilities

Assign roles and responsibilities for individuals who will support the content migration effort by completing the preliminary website audit, content cleanup activities, and ongoing content review work throughout the migration process.

Roles

  • Content Auditor(s)
    Identify 2–3 individuals responsible for reviewing website content and determining whether pages and files should be retained, updated, consolidated, archived, or removed. These individuals will also coordinate outreach efforts and gather input from additional stakeholders as needed during the audit process.
  • Content Editor(s)
    Individuals responsible for completing content updates, formatting corrections, accessibility improvements, and cleanup activities needed to prepare webpages and documents for migration.
  • Website Owner
    Individual responsible for overseeing the overall website audit and migration preparation effort, ensuring that all required reviews, cleanup activities, stakeholder feedback, and audit tasks are completed according to the assigned migration timeline and wave schedule.

2. Remove Outdated & Duplicated Content

Outdated and duplicate content creates confusion for users and increases the risk of inaccurate or conflicting information being displayed on the website. Users rely on site content to be current and trustworthy, and outdated information can reduce confidence in the user experience.

Checklist

Things to Consider

If content is no longer useful to users or no longer supports unit goals, it likely should not migrate. If the same information exists in multiple places, determine:

  • Which version should remain
  • Whether pages should be consolidated

Going through the process of content consolidation now will ensure a clean and efficient migration to the Drupal CMS.

A Note on Content Archival

Going through the process of content consolidation now will ensure a clean and efficient migration to the Drupal. The website will not be used as a content archival platform, so any unpublished content on your current site that you would like to save needs to be copy and pasted in an outside document or platform. You can copy and paste to a Word doc and save your documents to a Box folder that you manage. No pages that are unpublished will be migrated into the Drupal CMS.


3. Conduct a PDF & Document Cleanup

PDFs often become outdated quickly and may create accessibility issues for users. Reducing unnecessary PDFs improves usability, accessibility, and simplifies the overall migration effort.

Use the Document Audit Dashboard to conduct an audit of PDFs and documents currently used across your website, identify where documents are linked, and track document accessibility review status.

Checklist

Things to Consider

Whenever possible, important information should live directly on webpages instead of downloadable files.

The website will not be used as a content archival platform, so any PDFs that are not referenced on a webpage but still need to be retained should be saved outside of the website platform. You can use Box to save your documents in one place.


4. Review Images & Add Alt Text

Accessibility is a major goal of the Drupal migration.

Images without proper alt text create accessibility barriers for users relying on screen readers.

Checklist

Things to Consider

Only images that are referenced on a page will be migrated into Drupal.


5. Audit Users

Identify who will actively participate in maintaining content moving forward. Make a note of everyone who needs access to your website(s) moving forward, including their name, role and BlazerID email (uab.edu).