Check your version

This video covers a topic in Drupal 7 which may or may not be the version you're using. We're keeping this tutorial online as a courtesy to users of Drupal 7, but we consider it archived.

Case Study: Our Media

Video loading...

  • 0:07
    Using Drupal: Managing Publishing Workflows Case Study: Our Media
  • 0:09
    with Addison Berry
  • 0:18
    For a project that has a lot of content
  • 0:21
    or a lot of different users involved in your content process,
  • 0:26
    getting your site structure set up initially is great,
  • 0:29
    but it's sort of only the beginning of the work.
  • 0:31
    When you have more than a few people who are involved
  • 0:34
    in your entire process for publication on a site,
  • 0:37
    things can get complicated really quickly.
  • 0:40
    Websites like newspapers or online magazines or honestly,
  • 0:44
    any site that has a lot of content or a lot of different people
  • 0:48
    involved, or in particular, a combination of the two,
  • 0:52
    are going to need some kind of tool to help with the review process.
  • 0:57
    They need to be able to review and edit and publish things
  • 1:00
    in a way that doesn't step on each other's toes.
  • 1:04
    So in this series, we're going to be building out
  • 1:06
    a full editorial workflow process for a new site.
  • 1:11
    In this lesson, we're going to look at the use case-- what
  • 1:14
    is the project that we're building, what
  • 1:15
    are the requirements that we need to meet?
  • 1:18
    And then we're going to talk about how we're going to implement-- what
  • 1:21
    contributed modules, what aspects of core
  • 1:24
    are we going to use so that we can meet the needs of our client
  • 1:28
    in this particular use case.
  • 1:30
    So let's get started and see what we're going to be building.
  • 1:34
    Ourmedia is a Vancouver based independent news website.
  • 1:38
    The content is mainly produced by volunteers,
  • 1:40
    and there's a small staff of paid editors who
  • 1:43
    actually manage the website for everything.
  • 1:45
    And they make sure the volunteers know where the next press
  • 1:49
    conference is taking place or things that
  • 1:51
    need to actually be reported on.
  • 1:54
    And they go ahead and do the process for reviewing, editing, publishing,
  • 1:57
    making sure everything actually works on the website.
  • 2:00
    Now, recently the site has grown.
  • 2:02
    It's gotten really popular.
  • 2:03
    And they've decided that they need to delegate some
  • 2:05
    of this editorial workflow because the small team is just not
  • 2:08
    able to actually keep the throughput going.
  • 2:11
    So after they've had a couple of meetings,
  • 2:12
    they've decided that they want to have a few upgrades to their site.
  • 2:16
    So the main things that they're going to want
  • 2:18
    is they want to be able to have each team who works on sort
  • 2:22
    of a general topic of content on the site,
  • 2:25
    to be able to manage that content themselves.
  • 2:27
    So we want to be able to have groups.
  • 2:30
    So if we have something that's say in the culture section of the site,
  • 2:35
    we want to be able to have the culture team be able to manage all
  • 2:38
    of that content without having to use all of the actual staff time
  • 2:43
    to manage all of that.
  • 2:45
    So as part of setting that up, they want
  • 2:47
    to be able to make it so that each team can see the stuff that's
  • 2:51
    in their section, and also be limited to that,
  • 2:54
    and not see all of the other things.
  • 2:55
    They could give everyone on the site access to everything,
  • 2:59
    but that would be a little bit overwhelming for a lot
  • 3:01
    of these volunteers.
  • 3:02
    And it could create confusion between various teams working
  • 3:05
    on things.
  • 3:06
    So we want to have an editorial interface that the volunteer
  • 3:10
    editors are going to be able to easily find
  • 3:12
    what it is that they need to work on.
  • 3:14
    And the editors should be able to review that content
  • 3:16
    and send it back to the reporter if needed,
  • 3:18
    and talk about what is happening there.
  • 3:21
    They need to be able to edit the content
  • 3:22
    and then move it through sort of a pipeline or a workflow
  • 3:26
    to know what state content is currently in,
  • 3:29
    and what the next step is, and when is
  • 3:31
    it actually ready to be published.
  • 3:34
    So in terms of actually implementing this,
  • 3:36
    one of the things that Drupal core does
  • 3:37
    is it allows administrators to change the default
  • 3:40
    publishing settings for each content type.
  • 3:43
    So we go into just a content type, say, and we edit.
  • 3:47
    If you scroll down, you can see that we have publishing options.
  • 3:50
    So is it published by default or not-- promoted
  • 3:53
    to the front page and that kind of a thing.
  • 3:55
    So core provides us with that stuff.
  • 3:57
    The process of actually checking whether something's published
  • 4:00
    or not, going into the individual piece of content,
  • 4:03
    checking the publish box, is kind of a pain.
  • 4:06
    And so what we're going to be looking at
  • 4:07
    is using the workbench module to help
  • 4:10
    us ease this entire workflow that we need.
  • 4:14
    One of the nice things that workbench module provides
  • 4:16
    is this My Workbench menu item.
  • 4:19
    And if I go here, I essentially get a dashboard of the content
  • 4:22
    that I'm responsible for or dealing with.
  • 4:25
    And I'm logged in as an admin, so I'm seeing kind of everything,
  • 4:28
    and sort of maybe something a staff member
  • 4:30
    would actually end up seeing.
  • 4:32
    So I have this wonderful little dashboard.
  • 4:34
    I can go here, I don't have to go into the content listing of Drupal
  • 4:39
    core and figure out what's happening there.
  • 4:41
    I get everything that I need that's pertinent to me
  • 4:44
    right here in this dashboard.
  • 4:46
    Workbench integrates really well with Drupal core,
  • 4:48
    so you don't have to necessarily use lots of different workbench-isms
  • 4:53
    as it were.
  • 4:53
    For example, Workbench integrates really well
  • 4:56
    with the Drupal core taxonomy module.
  • 4:59
    So we can use the taxonomy that we want
  • 5:02
    to have on the site for our sections.
  • 5:04
    And workbench will be able to use that,
  • 5:05
    instead of as having to also create something
  • 5:07
    else specific for Workbench.
  • 5:10
    One of the things that we want to be able to also do
  • 5:12
    is limit what people have access to in terms of their designated
  • 5:18
    section or their topic that they are allowed to be working on.
  • 5:22
    So once we set up the taxonomy on the site and we have Workbench,
  • 5:27
    we can use Workbench access to indicate what sections we have
  • 5:32
    on the site and who's going to have access to those.
  • 5:35
    In this site that we've built, we have
  • 5:37
    a new section-- this is a vocabulary.
  • 5:40
    And then these are the terms within that vocabulary.
  • 5:43
    Now again, as an admin I have access to the entire news section.
  • 5:47
    But we're going to create roles and users who only have access
  • 5:52
    to these individual topics within the news section.
  • 5:55
    And that's going to be able to give us that limited Workbench view.
  • 5:59
    For people who should only be able to access to culture,
  • 6:02
    that's all they're going to see.
  • 6:04
    The last big piece to this is actually creating a workflow,
  • 6:08
    so that we can actually see what states a particular piece
  • 6:12
    of content needs to move through in order
  • 6:14
    for it to get to be published.
  • 6:17
    So in addition to Workbench and Workbench access,
  • 6:20
    we're also going to be using Workbench moderation, which
  • 6:23
    is another part of that Workbench package when you download it.
  • 6:27
    This lets you create custom states.
  • 6:30
    And then lets you indicate which states a piece of content
  • 6:34
    is allowed to move between and who is allowed to move it.
  • 6:38
    So if I look at my drafts, this is my content
  • 6:41
    that I've actually had some activity on.
  • 6:45
    And you can see that I can moderate this.
  • 6:47
    It's currently in a Needs Review state.
  • 6:49
    And I can move it to any of the other states
  • 6:51
    that we have created on the site already.
  • 6:54
    So when it's finally ready for publication,
  • 6:56
    we can publish it from here.
  • 6:58
    Or if we need to bounce it up to a higher level of review,
  • 7:02
    I can do something like that.
  • 7:04
    And that changes the moderation state and whoever's access
  • 7:07
    to that will be able to see that.
  • 7:10
    So Workbench is definitely going to be the main tool that we're using.
  • 7:14
    And we're going to integrate that with taxonomy along with path auto
  • 7:18
    just to give us some nice URLs and some easy ways
  • 7:21
    to track where our taxonomy terms are
  • 7:24
    in terms of navigating around the site.

Case Study: Our Media

Loading...

When many people are involved in your site publication workflow, things can get complicated quickly. In this series, we’ll build out a full editorial workflow process for a new site.

In this lesson, we're going to look at the use case -- what is the project that we're building, and what are the requirements that we need to meet? Then we’ll discuss which contributed modules and aspects of the core we’ll use to meet the needs of our client in this use case. We’ll set up editorial teams so each team can work on its own section, and allow administrators to change the default publishing settings for each content type. We’ll use different parts of the Workbench module to help us ease this entire workflow that we need, and create roles and users who only have access to specific topics.