D9 content review and entry processes

This information is for content writers to transition website content from Drupal 7 to Drupal 9 during the upgrade project.

Content entry checklist

Do all work in the production environments (not dev).

Every page already exists in the production sites, so you should not have to create any new pages. Use the Content list in Drupal to find the page you need to enter. If you cannot find it, let Domini know.

Steps

1. Enter all page content. Refer to the Drupal 9 documentation as needed.

   • Make sure to enter the meta description in Drupal. You may need to write a meta description if there is not one in the sitemap. Guidelines for writing meta descriptions is available in the search and findability section of the content strategy.

   • Check the "Notes" column in the sitemap to see if there are any special things to note about the page. Update notes as needed.

   • If you need to link to an internal page containing a how-to guide but aren't sure which page, see the OS how-to guide tracking spreadsheet to find the D7 name and the new D9 page. Do not link directly to the visual guide.

2. Document the D7 and D9 URLs in the sitemap.

3. Update the sitemap with any other changes.

   • Indicate on the sitemap if the page has a link to a PDF form.

Content review process

This is the general process for pages that need to be updated due to a navigation change, layout change, or other significant update. This does not apply to every page on the website.

At a high level, we need to:

• Assess what changes are needed

• Design the pages

• Enter the content into the production sites

In more detail:

1. Start with a page table (use existing or create new). Page tables are a tool that’s useful if the majority of the information needs to be rewritten, it’s a new page, or you’re not sure the page is meeting user needs. Focus on identifying the page’s purpose, user needs, and SMEs.

2. Based on the information on the page table, mock up the new page (you choose the medium based on the content—could be Google Doc, could be Drupal 9).

3. If necessary, review the changes with SMEs and establish when and what you need from them. Depending on the changes, you may need them to review for accuracy, or you may only need to make them aware of the changes. You may also determine that the changes aren’t significant enough to warrant SME review at this time.

4. Enter the content in the production site, making sure to complete the content entry steps.