Work on the web long enough, and you’ll eventually need a workflow: a system that allows some users to make certain changes, and other users to review those changes before they’re live for all the world to see. Maybe you even need some automatic notifications along the way. Sounds pretty basic, right? Unfortunately, it’s always been hard to set up a true workflow in WordPress. None of the plugins out in the wild seem to solve every aspect and bring WP’s permissions up to par with the capabilities of other CMSs.
Case study #1: There are some significant pitfalls when running stock WordPress in a multi-author environment for HE. Nathan runs an agency that helps universities overcome problems like this, but it became so common, that it birthed a plugin that now helps universities implement content governance for their websites. Nathan talks about the problems and how the plugin attacks them.
Case study #2: St. Mary’s needed a “simple” workflow for a new website. WP Core fell short in several areas - from lack of notifications to lack of ability to keep published content live when edits are pending. Elaine will talk through her attempts so far to solve these problems.
See how two different approaches to solving the same problems are similar, yet unique. Hear the questions we’ve wrestled with, the lessons we’ve learned, and our hopes for Gutenberg phase 3, when workflow is planned to be tackled in Core.
Elaine is a web developer for St. Mary’s University who loves to look at the whole picture. She specializes in designing and building solutions that work well for both end users and the people who maintain the web.
- General Lecture Session: Connect the dots: bridging silos of information
- General Lecture Session: Ready for review: workflows in WordPress