Updated

Editing content

Content is edited in WordPress. It uses a what-you-see-is-what-you-get (WYSIWYG) editor that automatically applies formatting like bold and hyperlinks without needing to know how to code.

If something is not working the way you expect, your best bet is to select that block of text and choose the vertical ellipsis (three dots) to select Edit as HTML. This shows you the code view. Many times there’s leftover code that’s creating the problem.

The right menu

On the right side of a WordPress post is a menu.

The Document tab is selected by default. In this tab you can:

  • Use the Revisions button to look at past versions of the page and undo changes
  • Use the URL Slug to create the page URL after https://covid19.ca.gov/
  • Add tags

In the Block tab, you’ll mostly work in the Advanced section where you can:

  • Create anchor links
    • Generally, only create anchor links to H2 header content.
    • Use lowercase letters and hyphens for spaces (the hyphens help screen readers).
  • Add classes in Additional CSS class(es)
    • Separate classes with commas.
    • Two of the most commonly used classes are wp-accordion (the class for the title text of an accordion) and wp-accordion-content. Remember to add wp-accordion-content to every paragraph inside the accordion.
    • Only use wp-accordion on headers. Follow the regular header rules to decide what level of header to use. No matter what header level is used, the wp-accordion class will give the header a uniform visual appearance.

Tags

The two main tags to know about are:

  • staging-only - This publishes the page only on the staging server. Use this to test how content appears or preview it for others.
    • Try to only stage content right before publication. It’s easy to forget that content is staged and is not ready for publication. It also makes things complicated if the page needs other changes made but new content has been staged.
  • translate - This tells our translation vendor to check the page for changes and push them to the translated versions of the page. This tag should be on every page unless otherwise specified.

Always check the tags before publishing. Sometimes tags drop off or do not load before publishing. It’s especially important to check for staging-only if changes are not ready to be published.

Publishing

Use the Update button to publish. If you have made changes, but are not ready to publish to the live site, use the staging-only tag. Do not use Switch to draft. This unpublishes the page from the site.

After a post is submitted for publishing, you can track its progress in the github Actions. It usually takes a few minutes after the action completes before the change appears on the site. If you see in Actions that publishing for your page failed in, ask a developer to take a look at what happened.

Archiving content

To archive a page:

  1. Save the content (and any special code) in a Google Doc in case you need it later.
  2. Remove the page from the menu navigation.
  3. Search WordPress for the page URL to see if it’s linked to by any other page on the site. If so, remove or change the link.
    a. Search using only the slug (for example, /vaccines/) instead of the full URL (like https://covid19.ca.gov/vaccines). Many links do not use the full URL, just the slug.
  4. Create a redirect for the page (and any translated versions).
    a. If there is a page that has replacement content, set the redirect to that page.
    b. If there is no replacement content, leave the destination column blank. This prevents the site from getting a Soft 4040 penalty.
    c. Create redirects for any anchor links on the page too.
    d. Check the redirect table to see if the page you’re archiving is the destination of any redirects. Update those destinations as appropriate.
  5. Find the page in the Posts section of WordPress.
  6. Hover your cursor over the row with the post. You’ll see a set of options appear.
  7. Select Trash. The post will move to the trash immediately without a confirmation screen.
  8. Create a Jira ticket the engineers that the page has been removed to:
    a. Remove translated page files
    b. Do a recrawl of quick answer questions (if needed)
    c. Remove URL from uptime monitoring check
  9. Remove the page from the per page feedback filter code on github.
  10. Move the folder of draft Google Docs to the Archived content folder.

To restore a post:

  1. Go to the Posts section of WordPress.
  2. At the top, underneath the word Posts, you’ll see a list starting with All and a number in parentheses. Select Trash at the end of the list.
  3. Underneath the name of archived page, select Restore.
Created and maintained by Office of Digital Innovation