 Hi everyone, I know there's still a few folks trickling in but we're gonna go ahead and get underway and Folks can just kind of find seats as they as they can Hi, welcome to workbench managing content management My name is George to Matt. I'm the founder and CEO of Palantir net And this is Ken record. He's one of our Senior engineers and technical leads at Palantir and we're here today to talk about workbench for Drupal 7 So before you go ahead before before we talk about workbench talk about ourselves a little bit George said he yeah He's the CEO and the founder of Palantir I have a little more complicated role and my wife is quite the social butterfly So I find myself a lot of cocktail parties and people are being polite and ask what do you do? And I finally boiled it down to a one sentence answer and I say oh I work for company and we build websites for institutional non-profits Right, which is a good answer, but I think it's really only kind of part of the full answer We definitely we do a lot of work with institutional not-profits that would be Higher education folks like colleges universities. We do a lot of work with museums cultural institutions media organizations We work with corporations. I mean essentially We do a lot of work with Folks whose org charts might look like that very large very complicated org charts and So I'm going to start off by telling the story of a couple of different clients Basically essentially for whom the first version of workbench was actually built and the first one of those clients is Barnard College in New York and They're one of the seven sisters colleges there and they had a Few challenges when they when they came to us to redo their web presence It's an enterprise level Drupal 7 implementation So they have we were working they had an electronic communications department That was kind of responsible for the content Administration of their website an IT department is responsible for the infrastructure behind their website 50 different academic departments and programs 30 what they call section owners people who are responsible in some way for the content on some section of their website And actually to a couple hundred folks who were responsible for directly editing Content directly on their website. So that's Kind of example number one. This is the site. We ended up building for them Example number two is the Field Museum of Natural History in Chicago This photo is from the Drupal con Chicago from the opening night party. We had in the main hall there they they're also they're an organization that that had their own set of Challenges that they were looking to to solve with their new web presence The Field Museum in addition to being a place where visitors can kind of go and You know see exhibitions and works in their collection They're one of the leading natural history museums in the world, but they're also a major research institution And so they actually have hundreds of different scientists and researchers who are spread across dozens of departments Their website has just massive amounts of content and digital assets part of the project was actually tying into Their digital asset management system which had you know literally millions of items in the collection But like many institutions large institutions, it was a very small centralized web staff So the issue of course is that when folks wanted to update content on the website There was this bottleneck that they were dealing with This is the the website again in Drupal 7 that we ended up building for them So in talking about these kinds of Institutions and organizations. We see some common challenges Access and permissions that you have people who need to be able to edit content on the site by Section not just by content type, which is kind of Drupal's default MO And hierarchical permission inheritance. We'll talk a little bit more about that Extensible workflow states things going from draft being edited published a Single repository for media management and the ability to modify published content without it going live immediately That you might have a page that is published on the site Somebody might need to make edits to it. Those edits would need to be reviewed before They are put live and I should ask how many of you are new to Drupal in this room Okay, Drupal by default only has published and not published So if you want to make an edit you you end up taking the content offline Or you just edit live which is always dangerous. It's scary. Yeah So talking a little bit about that idea of the content sections This is a kind of an example a sample example of what you might have in a museum setting for example You might have folks who are responsible for you know the collection You might have folks who are responsible for the library. You might have somebody who's responsible for You know editorial content however that spans different sections of the site hierarchy So there you might have somebody who's responsible for both the gift shop and the library section for example So what we often see is that content editing and content Publishing privileges are not necessarily Do not necessarily correspond to the information hierarchy of the website What we also see is different levels of hierarchal access So you might have somebody who's kind of at the top who's responsible for everything under a particular branch of the hierarchy, but you might also have folks Underneath that who are just responsible for specific sections, or you might have somebody who's responsible for content in one area Responsible for a content in another area That the person at the top is not necessarily part of so there's a there's a It's the ability to basically identify the different editorial groups within your site right we have Raise your hand if this sounds common we had a lot of cases in Drupal 6 where we'd have people say things like well I have an intern who's responsible for Publishing information to visitors to the gift shop and only that Information right and we don't want them to even know that there's other content in the CMS All right. I saw one hand go okay see yeah, okay So this is the kind of scenario that that we're seeing over and over again and in fact I'll say as a developer got really tired of trying to solve over and over again So there with these Questions and problems comes kind of an implicit set of client expectations, which are and assumptions which are often unstated You know so some of the issues we have to deal with are of course, you know the Drupal learning curve That that in many cases the folks who are responsible for Maintaining and editing content on the site are not familiar with Drupal at all They're not interested in learning more about Drupal They really just want to edit the content on the site and specifically they want to edit their content They're really only interested in seeing and dealing with the content that is their responsibility and You know as kind of saying Don't want to or shouldn't even in many cases be aware of content that they're not directly responsible for They want content to be able to be reviewed before publications before it's published They want again as we said before Content that's live on the site to be able to be reviewed before it's changed There's an assumption that Media is should be treated the same way as any other kind of content is treated, right? Whether it's images or video files or whatever and a lot of these Assumptions and expectations come from the fact that well, that's the way our old CMS did it So but it's not the way that Drupal does it, you know, so we see these things and You know, we all know right? Hey Drupal can do everything, right? There's there's a module for that Right and and that's how you sell it isn't it? Absolutely. Yeah, so so as a developer I mean I'd say that these unstated assumptions can really bite you if you're not careful this idea that what do you mean? After you've delivered a project you spent, you know six months on and someone says what do you mean? I can't preview the the change that I just made without it going live to the world Because a lot of people come out of a system that publish flat HTML files so, yeah The typical response when when sales manager George goes out and says oh sure we can do this You just go oh well We can use a module for that and some of the features and functions that I'm going to show you in the workbench workbench Demo you're going to go well wait doesn't x module do that and doesn't y module do that And there was a there was an issue posted in the queue last week where someone said why don't you just integrate with these other things? To which I responded by posting this document This is the original punch list of features for workbench We're going to get into the sort of technical part of the conversation now, and then I'll do the demo But we actually did this presentation for the first time at Drupal con San Francisco before Drupal 7 was even out And what we basically did is we went through the common scenarios That our clients were faced with every single time we did a site build and this is actually not the entire list Because it won't fit on the screen at a readable size Right, and this is me mapping actual features to actual modules that existed in Drupal 6 some of which we had to write in order to get them to work I think the final count is 28 separate modules So number one you have to have the knowledge of those 28 modules and how they work and how they fit together But one of the other really big challenges that drives people crazy when they implement a Drupal site is that these 28 modules Might have 14 different names for the same thing Right, we use the term section to describe an area of the website that someone can edit That might be called a context in some other module. It might be called, you know a Widget in a third module these kind of things really plague Drupal and make for a lot of complexity So we wanted this functionality We really wanted us to do two things as developers when we looked at work bench number one We wanted to stop solving the same problems over and over again Right and number two we wanted to try to simplify the interfaces that were being presented to the end user So this is a very instructive list to me And some of this stuff still exists in Drupal 7 and has integrated into work bench and we'll talk about that when it comes up So Workbench at its core has three modules There's a fourth that's that's really in the works that I'll talk about the three fundamental pieces are workbench access Which is about partitioning? Sections of your site so that certain people can edit them and certain people cannot it also will partition where content can be created And that's a very very useful feature for a lot of folks And we'll talk about that in some great detail because I wrote it and I can talk about it workbench files, which is Really it's sort of a very nascent stage right now and is about providing better file management tools We're actually also in very very active Discussion active development on the media module which has a lot of integration points with what we're doing Workbench files is really just a view into your file system Designed to make your your editor's jobs easier and then workbench moderation, which is the piece that lets you Set up workflow states that says you know this piece of content has to go this editorial review process before it gets on the site We'll take a look at all of these in just a second because you folks want to see a demo I assume a Pretty safe assumption. I am going to actually start this demo I have logged into a Drupal 7 site as a user called Librarian Okay, now the librarian one might expect is it responsible for the library section of the hypothetical website that George was showing you And in fact when you install workbench it will ask you if you'd like to install its test hierarchy So you can play around with it without having to know how to configure it It'll just do it for you and install the exact hierarchy that George was showing with the fake museum website. So This is a user who's actually pretty low-powered This user can create certain content and can edit content that falls within the library's scope of Influence that library section and the first thing you'll notice is we've got the The toolbar at the top and they have access to a my workbench screen And this is the screen that that Dries showed this morning except there's no fancy picture of George There's the picture of me as a grumpy Viking. You really should have gone with the Viking I like the ground. It's too low res. This is what happens by the way when you force me to pose for a picture Right and so the idea here is that we want to give people very quick access to the things that they care about There all of this is actually powered by views and we just add tabs to things You can actually extend this very very quickly as a site builder by adding another views tab we did a project that George talked about this morning the Minnesota the Minnesota Public Radio Archive that has another tab that lets them View their content imports to make sure there were no errors during the import process But the idea here is that everything is right here at your fingertips and and I really like this Hey, here are the three most current things that I've edited right the idea being you Have a workflow and we want to get you straight to it right, so you log in you come in here and you can look at a Page that will show you everything you've ever edited on the site Which is kind of useful You can look at all the recent content and this is kind of interesting This is all the recent content that this editor can see and in a minute I'll show you the at the admin super user and I have a lot more authority than that And you can see that some of this stuff is tagged as it's in the library section Some as tagged as it's in the library staff, which is a subsection All right, and this one of these things that people always have wanted in Drupal You can search and sort and filter The content that you have access to very very easily you can't even and I love this feature actually You can say hey, let's check up on the people responsible for the staff section of the library part of the website Let's see what they've been doing Right really useful um The create content tab is here. There's nothing very exciting going on here Obviously what we actually did I didn't enable it. I'll turn it on in a minute or this user doesn't have permissions This screen in in Drupal core is not extensible means you can't add new things to it in in workbench You can so we add a media link here that says hey, yeah I want to add media and I have a patch in to add the block link to say I want to create a new block We're still debating about whether or not that goes in You also have access here to a list of all files. This is all workbench files actually does right now But it's better than what you have otherwise, which is sort of nothing Just a searchable file list where you can preview everything that's going on This this tab is actually a little controversial This just lets the editor see what parts of the website they're responsible for and if you have better permissions fuller permissions You can actually change these settings, but this user can't And then there are two things that are here provided here by the workbench Moderation tool one is my drafts and my drafts are things that are not live on the website There's the stuff. I'm currently working on Right and a lot of people in their workflow. This is where they would come to first Right because you want to come in and say, oh, yeah, I do need to finish that article, don't I? You can also see there in the left rail One of these is a draft and the others are needs review. The basic workflow is that if it's a draft It's just for you to work on but once you think it's ready You can pop it into the needs review queue and the needs review queue Is over here and what's really really useful? I mean just imagine this scenario, right? How many of you by the way work in a large organization and How many of you also have underlings a couple darn you should get some underlings. They're fun I love underlings. So so we'll say for example that you are the chairman of the Department of Mathematics at Cambridge right that's prestigious You don't have time to spend writing the content for the Department of Mathematics website But it's partitioned into five different groups and you've got five different editors who are responsible for making sure that the University's mathematics website is up-to-date and proper. Well, you can come right here To the needs review tab and check up on your staff Right and for those of you who've ever built university websites. That's what they want Right. That's exactly what they want that the chair of the department doesn't want Anything to do with the actual content production, but they want to come like a laser beam and right to one point where they can see that Things are getting done And there's some other stuff that we can build in later. That's really interesting We'll look very quickly at Content creation, which is fun In part because you can see right You can't see real well right there. We have the sections box Which allows the user to assign This particular article that we're about to create to one or more editorial sections And of course notice that in our mock-up we have the entire museum, but this user only has access to three things right because it's a library editor Right. So when you're creating something, it's front and center and you can say okay. That's that's where this content belongs Right. Let me go back. Let's look at trap. Oh, it went there This is another interesting and potentially controversial element that we've we've put in There's some folks in this room. Hi, Bruno Who helped us on this and we're going to talk a little bit more about the user experience to this thing So this is a draft article that I have and and we did a couple of things because we wanted to make it really really Clear to the editor. What was going on? So the first two things I want to point out is We changed the names of the tabs Dynamically based on the actual workflow state of the article you're looking at Right. If this were a live article, this would say view published Right, but we have view draft edit draft, which is very different right and I'll show you a published article in a second There's a moderate tab and that moderate tab shows you the entire editorial history of something And then we have this little info box Which is actually a Drupal block and you can put it anywhere you want to on the site We actually stole this UX pattern from the documentation section of Drupal.org Thanks, Bruno and it's designed to give you just an Pinpoint view of the current state of this thing because imagine that you're an editor and you're the editor of The exhibit section right and you think you should be able to edit this thing, but you can't Well, if you come in and you have the proper permissions, it'll say very clearly workbench access Library and you'll go. Oh, yeah, I'm in the exhibits section. I better call the librarian and ask for access to this thing Right kind of useful. Yeah, the revision state also good to know. Is it current? Right because when you do revisions, they can get kind of complicated. You can actually have a Live draft that is not the current version because that would mean there are other New revisions waiting to be looked at so we tell you that right here And there's actually a shortcut for super users that will let you moderate something straight from this page This user doesn't actually have permission to do any of that and we will have plenty of time for questions by the way This is a pretty straightforward article. There is no great moderation history on it But we even color code things. This is sort of a nice Reddish pink to let you know that it's not actually one. Let me find another article. Yeah new exhibits for May We have a tab change view published But that's all I have authority to do as this user because this is not in one of my sections right so One of the things that that my colleague Colleen Carol likes to say is one of the things we've done here is As an editor, we've moved Drupal out of your way All right How many of you train your clients on how to use the sites you built? Yeah, how long does it take you to explain how to create a new page or how to Find content to edit, you know, you have to go here and click this and find this Workbench for me personally has turned three hours of training into 20 minutes Because I just go oh hey log in click that and They're like oh, how does this oh? It's much more intuitive for them and it's really a lot of fun actually to do that training now. So We will hold the questions for later. I'm gonna Change browsers and show you some stuff under the hood as an admin user. Hey Firefox. No Are we in version? 27 that was version six. They want me to install your way behind. Yeah So here's This is an interesting case So this is an article that I wrote when I was at Drupal camp Stockholm showing off this very same thing But we're not at Stockholm anymore So we're gonna want to change that and you'll notice the tabs across the top, you know view published New draft very clearly telling me oh by the way if you try to edit this it's gonna go back into revision Right And then the moderate and well D Vell's just there because I forgot to turn it off So if we go in and well, let's look at the moderation history of this thing now There's nothing exciting there. Just thought I'd check we want to change this. We want to change the same pub crawl No, I can't type Pib The pub crawl not actually going yeah. Yeah. Yeah, I'm tired jet lagged and stuff Now what's interesting is a super user For people familiar with Drupal normally in the publishing options. You have a yes. No checkbox basically says this is published or this is not published For most of your normal users they won't have access to this moderation state And with workbench moderation I'll show you you can actually control just like I can control which section someone has access to you can control which states They can move things to and from this user can actually override all that because it's user one and Move everything straight into production if I can't choose to but by default if I create a new page Hey, I'm on the view draft tab now Right very clearly telling me. Oh, that's the Drupal con London pub crawl and let's make sure that work correctly Oh, that's the version that your site visitors are going to see. This is the version that's still in cash Right if you're using something like varnish or Akamai or a front edge front side cash That's the still live cashed version Which is really really helpful and if I go in here to the moderate tab now. Oh look Clearly tell me what's going on So let's look at moderation just a little For the developers in the room I will Pseudo apologize for this workbench moderation is actually a fork of the content moderation module from Drupal 6 It was forked because that developer wasn't ready to work on Drupal 7 and we had a deadline to hit there's also a revisioning module for Drupal 7 that that Has many of the same features and I think can be used as a drop-in replacement But we haven't fully tested it and it's just one of those cases of people on different deadlines not quite communicating as well as they might This actually allows you to create and manage different workflow states They are linear workflow states the idea being you know, you want to move it through a process And it is a like say a linear process and it's kind of nice because you can name Well, you can't name them yet, but you can give them different descriptions You can add new states if you choose to you can remove states Which is kind of interesting and you can also define The transitions that can be performed Right because again, this is a linear process It doesn't make much sense to move something from published back to draft You could do that if you want and these transitions are important because when it comes to configuring and I'll show you What comes to configuring the permissions for things workbench moderation gives you very very Specific access controls to what people can do. So on a per-role basis You can say yes, they can perform this workflow transformation this state transformation or not Which is really really useful Exciting you can also set different default Moderation states for different content types. So you could set it up such that blogs blog posts always auto publish and Don't have to go through moderation But you know articles do have to go through a moderation process and that's really really useful and then Workbench moderation can be a little complicated. So Beck white who's one of our engineers built this little permissions checker That's designed to help you understand if you've got it configured properly I don't exactly know how it works, but I'll double check but essentially it says hey Does the editor role do what I think they should be able to do? Can they edit moderated content of the article type the editor role should be a qualified editor So yes, this one passed the check There's some UX work to be done here But this is actually a really helpful feature when you're setting up the site because Moderation can get really complicated and hard to debug so The second part that I will show you is the access control part so workbench access is an interesting beast it tries to Replace some things that we did in Drupal 6 and sort of expand on some things that other folks have tried The first thing to know is that it's a pluggable system It's designed to be an API kind of system and it can use any hierarchical system that you might think of By default right now. It supports the menu system and the taxonomy system that Drupal uses But there's I'm actually working on a patch that supports the role system just because it's kind of fun And those systems don't even have to be hierarchical they can just be they could be flat lists if you want them to be But theoretically you could do like group-based organic group-based access control through workbench access if you chose to It would be a little strange, but you could do it and here on the configuration screen. We have a couple of options You can choose to use one or more of your your vocabularies you you have to select at least one This is what George was talking about earlier. It's divorced Potentially your access controls can be divorced from your site architecture Typically they are but they might not always be so this allows for that There's a nice new feature that we added here That allows you to say you know what I don't want this to be enforced on these content types Which is also very very useful Because by default Drupal users you'll have permissions like I can edit all articles Right well workbench access is turned on if that article is not in your section. You can't do that Right, so we might just choose to say you know what blog posts. We don't care about blog posts We're not going to put them under access control and that's pretty slick There are two other things down here. Well three We talked about section a little bit. I like to call them sections other people don't so we just made it configurable You can call it whatever you want Yeah, I know it's kind of silly these last two are not quite so silly these are fun Automated section assignment enable all sections automatically for the active access scheme. What that means is Hey Make this entire taxonomy Part of the hierarchy All right, and in most cases in 95% of all cases. That's what you want, right? But take this take the following case So back at the University of Cambridge, right? Is it the University of Cambridge or is it Oxford University at Cambridge? Or are those two separate things? They're two separate things. Okay, so Let's say that the physics department really wants this kind of hierarchical control, right? And they've got subunits for astrophysics and whatever other kind of physics there is And the math department just doesn't care in that case You might not want this because that your taxonomy might let the math department tag things as you know statistics versus Number theory Whereas your physics department has you know physics and theoretical physics and astrophysics and applied physics You could turn this off and say you know what we're gonna select Which ones matter and I'll show you the interface for that in a second and then there's allow multiple section assignments having multiple section assignments can actually Complicate things for some folks. In fact when we were building Barnard they explicitly asked not to have that feature Because it makes it easier for people to step on each other right because if the library can edit it and the exhibits Can edit it that who really owns it? So it's now just configurable. So If you turn this off instead of getting a multi select box, you'll get a single select box, which is a useful little feature I'm actually gonna Hey, look, I get an alert. Are you missing a meeting right now? Yeah, I'm missing a meeting I'm gonna turn the automated section assignment piece off I'll also note that if you if you have automated section assignment turned on and you add a new taxonomy taxonomy turn It'll automatically get added in If it's turned on these these things are not configurable anymore It still shows but this is showing me the hierarchy that I have and it just lets me turn these things on and off Which is again, I think really really useful The other thing that's really useful. Let's look at the editors first Is that there are two fundamental ways that you might assign people editorial rights? And they're Anyway, I'm not gonna jump ahead on that This is the overview that talks about Editors that is individual user accounts who have access to certain sections And so we get this little overview that lets me know that what there's one editor for the museum section There's one editor for the library section and I should have made more more users, but I didn't bother And if you go in here and we look at what's under the library It says we might expect the librarian you can remove the librarian. That's kind of useful or I can add a new person and I Think there's an editor in here, and it's just a little Autocomplete text field so now I have two User-based editors right and so when when an individual users access rules are being checked We we look in it in the data and we find this now Imagine that you have 1200 people on your staff You probably don't want to have to administer this for the 80 sections of your website And if that's what you don't want we also have Role-based assignments, which is usually what people end up using right because then you can just make a role That says this is an intern interns belong to these sections Right, and I did set up. Oh look a role to be the museum editor Same basic concept right the thing that you should note though is that Let's say George is an editor and a user If I say all editors are members of the museum section he has access But if I can also say that George has access to the museum section right if I take away the editor's permissions George still has permission because he's assigned as an individual user The reason that you have both of these things most people say well role-based is enough. That's that's fine It's really for the exceptions in the organization because you have that one secretary for some reason who's responsible for the physics department and the English department. Yeah, and the whatever spun off from the English department when they split it into you know Classics versus yeah, anyway, we're not going to foment academic descent in mind. I'll stop So There's the basics and if I go in here to my workbench as this editor I can show you hey look I can look at my sections and I can assign them I can also as an editor I can go look at other people's accounts my contributor here and Look, there's a little tab and we can see oh what sections is this person assigned to oh, they're not assigned to anything That's why this is collapsed. Oh look I can go in and say oh this person should be part of this group Kind of a nice little feature. I will point out by the way That workbench access and workbench moderation do not require each other and in fact don't even require workbench The main module you can actually run them as standalone independent things I don't really recommend it Because it goes to what we've been trying to accomplish Every single client that we launch on Drupal 7 and we've done eight or nine so far At least launched launched Six or seven. Yeah a lot. There's we're working on a lot. We're working on a lot Every single one of our clients gets this every single time. There's not even a debate And what's nice about it for us is It's like a one-hour budget item in the overall project Because instead of having to go find 28 different modules and configure them There's four and we just go get them and we configure them So that's pretty exciting to me As a developer and as a as a site builder So It's really about Changing the way we interact with Drupal That's I think the big thing here The other point that I would try to make I think I just forgot because I'm being spontaneous Darn it That happens sometimes So Let's go back here New exhibits for me My test article. Yeah, this is a more detailed Yeah, I tested this a lot And you can go back and and look at any of these and say, you know, this is the one that I liked I want to make this the line and that's good. So let me go back to to slides for a second Make sure I hit all the points. I wanted to hit so Dries was really nice and and actually every time we go when we show this off people get kind of excited Um, I get excited when I show it off. I'm kind of proud of it I should say that there were been at least eight people involved so far It was really been a big team effort At san francisco, we had a big pizza dinner with all the engineers and we hacked out our list of features and The previous times we've been giving these presentations It's been a little bit as a as a sales pitch to get people excited and get them to use it and to say This is a good idea and hey, look at the cool features. We have that we're still working on From an engineering standpoint, I would say It's feature complete. There's some stuff we'd like to work on. There's some extra stuff we could do But it's ready right it's it's ready for use It's I know it's a beta nine, but we're expecting the 1.0 release Within the next two weeks or so. There's like a half dozen sticky little bugs. We have to fix But they're all edge cases, but we still have to fix them Then there'll be a stable release But in terms of functionality, I think we're fine But what everyone says is especially with the the overall views and things they go, you know It's still a little Ugly little little rough around the edges. It's a little rough and that's true And part of that is because I can I say this we started the project with the ux lead Who then decided not to move to chicago and move to vancouver and steady quit So so we lost our ux guy, but we just hired a new one And this is what he did his first week on the job Patrick grady is our new new ux Uh designer and he said, you know what he doesn't know anything about droopal either Nothing his first exposure to droopal was somebody installed droopal seven for him put workbench on it and said Make this easier to use these are sketches from his first week Right um the other thing that's really really exciting to me and I'll show you he wants to Redule the to redo the toolbar. He thinks the toolbar is too complicated He wants to put like personalized contextual links in the in the toolbar Right so that people can just add their own stuff and as engineers we went Oh, yeah flag module will do that for you. Sure. We can give you that in like a week. Just tell us what it should look like So we're really excited about the work that patrick's doing At the same time in the last three weeks We had two different companies who don't even work with us Um, one of them say a company here in the uk whose name I forget and they said hey We're using this stuff and we think it's pretty awesome, but we have some ideas for how it might be more awesome And we have 10 Work days we can devote to development What would you like us to focus on? Yes, snickering. No, whatever volunteer help. Yay And then and then a friend of mine who's actually doing work at Al Jazeera right now He called me up and he said um We're about to undertake this very large project and mark bolton. You guys know who mark bolton is He did the seven theme and the drupal.org redesign Big ux designer and big designer. He's a big famous name Well mark's going to be designing the Al Jazeera project apparently And the guy who wanted to know if mark found problems in the workbench ux Would we be receptive to hearing about it? Yeah, I think so. Yeah So um rather than be sort of developer focus from now and say hey, what new features and things do we want? My actual plea at Drupal con London is to say all right. We think It's ready. We think it's good. Um We think some of it should go into Drupal 8 But we know we need some some spit polish on it. We need um a little bit of Not eye candy. That's not even the right word, but we need to know where the problems Right. I mean fundamentally the system is designed so that you know very basic content contributors and users can Easily do their jobs on the site. So the system really does need to be easy to use Yeah, and so You can post issues in the queue if you want. There are actually some issues in the queue I'll say there are some technical issues in the queue and then I'll talk about a few of them That are literally waiting for someone to design a user interface for them because we know how to solve the technical problem But we don't know how to solve the interface problem Because that's not what some of us do but that's what we got Patrick. We're working on it. I know we're working on I will give you a little bit of feature roadmap One of the things that workbench access does not do and I blame the the field api for this Is that it doesn't actually interact with native form elements, which means it actually creates its own form element And so you should know going in that if you use it With the menu system, for example, it doesn't actually add pages to your menu It doesn't do that. It just reads the hierarchy that you're using Um, so it's it sits in parallel to it and for those of you who care on wednesday I'll be having a core conversation Um, and I can't remember when um, and we'll talk about why that's the case And why it makes me very angry One of the things that needs ux work are these next to access rules per content type and moderation rules by content type Really nice features that people would love to see Right the idea that hey this intern can only edit blog posts in the mathematics section The problem is the user interface pattern for how you manage that is a freaking nightmare Right. Um, I could give you an ocean of permissions check boxes Right, but if you have 10 content types and 40 sections, it's gonna get I'm not giving you 400 check boxes without some usability work um This idea of editing the default states Renaming them adding new ones Removing them. That's good scheduled state transitions. This one's closed. This is a fascinating one Uh the idea that you can say hey on If someone creates a new new draft on monday If it hasn't been touched in three days Move it into a hey Jerk queue or what would you call it the speak now or forever hold your peace queue? Yeah the All right. Nobody reviewed it. I'm gonna make it go live queue. Right right I like that because then then someone could log in and of course if we if we have um You know notifications sort of emails that go out, you know, we could send a notice Hey editor of the mathematics department. There's a piece of content on your section that's been sitting for three days You need to look at it That'd be kind of nice. Um, and I have we do have clients who really want that feature We have a client who wants an automated message to go out every 180 days To say hey dummy. Look at this page Make sure it's still accurate Every 180 days So scheduled state transitions would allow for that and this other one We have another great guy on our on our team, uh, steve parsh. Who's an engineer and his first day on the job We we showed him work bench and he got excited and we're like, so what do you think we ought to do? And he goes to this one non-linear approval workflows. Well, what the heck is that right now? We sort of walk things through draft needs review published. He goes. No. No. No, that's too much What you really need is little little approval check boxes We know the thing is ready to go live But we're a big, you know, we're we're Cambridge, right? We're important and if we get something wrong, that's a real problem So our lawyer has to review it And our pr person has to review it and our technical reviewer has to has to approve it and our style editor has to approve it Right and in no particular order in no particular order and without actually saying there's been a change to the content structure So what he wants to do is these non-linear approvals that just say, oh, hey, you're looking at this as the legal reviewer Do you approve it? So, um, I think that's really exciting actually So exciting. I really want to write it, but I'm going to let steve do it Um, a couple of others assigned reviewers This is actually a pretty big one. I have a client right now who desperately wants this They want to be able to say, yeah, hey, I just wrote a new draft. It needs review and I need This person to look at All right, so that's a good one. Um, scheduled content publication. Uh, this is actually an ongoing problem The scheduler module is awesome The scheduler module doesn't understand revisions It never has it probably never will so we're fixing that one right now actually Um, notifications is actually pretty easy to do this sort of workflow notifications There's actions and triggers and things we can do for that and then better file and asset management You'll notice I didn't actually show you any of the media integration because It's not quite done. Um, I will urge you to check the issue q one one of the interesting things here is we made a strategic decision Um, as a business and as developers Unlike some similar kind of products. I mean, it's not something that we sell It's not a distribution. We've talked about making one But it's really about making everyone's lives easier and we really want to contribute back As I said, we think some of this stuff will get into Drupal 8 core, and I think that's I think that's going to happen actually But it's not a distribution. It's not something that you go when you get And at the same time, it's not one giant chunk of modules It's five different modules that you have to go download and each have their own issue queues So if you really care about content moderation, there's an issue queue for that on Drupal.org And I encourage you to go check those out Because it's community stuff. I mean, we want people to participate. We want to hear from you in the issue queues, especially if you're a designer We love designers. They make our jobs easier I'll take a sketch on a napkin seriously anything So for more info and questions that we're going to have if we have some time for qa We do that's the the project homepage Um These three folks robin berry is one of our engineers. She is sort of the tech lead She stitches it all together and sort of says yes and no on new feature development Colleen carol is sort of our customer advocate And uh is leading the design process I'm one of the engineers and and i'm pretty visible. So it's easy to find And then there's george and george asks you not to ping him in our irc. I won't see that. Sorry George doesn't hang out in irc, but i'm in droop will contribute all day long. So We have by my watch nine minutes left All right, so yeah, if anyone has any questions, I think we have a mic we can pass around we do So we have a volunteer to Hopefully the second mic is turned on it should be okay. Excellent So, uh, there's somebody okay. Yeah, just take it. I'll let you decide if if folks raise their hands just just Just give it to them Let's torture the volunteer I just wanted to know I saw uh You have the page where you show the source of the hierarchy tree. Uh-huh And it was like a radio button meaning that you could only pick one Yes, how hard would it be to have multiple sources for the hierarchy because Assumption that you would only Uh Place your access control or on the menu tree or a taxonomy tree might not be There's an issue for that in the queue My initial response to is yeah, that's awfully complicated and I urge you not to try that The there's there's actually an architecture problem because it never occurred to me to let you do that So you can't do it right now and it would take it'd take Not a ton of effort, but it would take some effort to allow for that um For me conceptually it doesn't make sense actually to to because It's not one hierarchy anymore. The nice thing about menus and taxonomies is they they have a terminus point, right? There's a top level Um, one of the nice things by the way workbench access unlike other things Will actually let you select the top level menu item or menu Or the top level vocabulary as a section Right. Um, it's not limited to just the children All right, but if you had that you'd have to create a sort of false top level And then you'd have like well, here's your menu stuff and here's your tax on it. It would be weird so Next question Hi nice module. Um, do you have international internationalization or multinational support? There's no sort of special international support. Um, there's just sort of default Drupal seven support. I'm not sure what Else there would be Exactly, I mean like the internationalization module the third party module Well, I mean you can use internationalization with it. Um I don't think there's anything special we need to do if if there are features like Internet, you know panels for people who are doing translation that makes a lot of sense But I'm not at the moment. I don't really understand the question Oh The way, oh if you only want to moderate the english content The easy way to do that is to just edit the views that come with the module and just add it in Bit of explanation If you have an english french and german version of content and somebody modifies the original english one It would be very nice to flag the french and german one to be reviewed as well And yeah, and there's a mechanism for that in Drupal core, but It's not reliable. Is that it or do you have to do it manually? Because you control the states on the nodes you could as well modify the states on the translated nodes Right. I see what you're saying. Yep. Yep and automatically create well you But you don't have a new revision of the translated nodes You you'd sort of want to have another state You'd want to have another state that says hey translation updated Exactly. Yeah that I can see how some of that sort of stuff might work one one It's funny because one of the things we ask for frequently if you went if you went to post that in the issue queue We might have a conversation very much like that in the issue queue where it's like What do you mean? It supports multi-language, but teasing out what that feature actually means Yeah, that makes perfect sense I can see a module that all it does is add a new moderation state called You know translation check or something like that and what does it do? It watches the translations of nodes and If you modified the german version it marks the other two says hey We're going to make a new draft that needs a translation check pointing back to That wouldn't be that hard You mentioned that the module was operating on nodes and files But is there a way to use it for just about any custom entity that a site could use Not at the moment The question was if you didn't hear it We we have support for files and we have support for nodes Do we have support for any type of entity and the answer is no Largely because most people don't interact with those sorts of things So by default we don't support that Again, one of the nice things that the views modules enables is that you could add another tab for that very very easily So if you need to say hey, I want someone to be able to Have an overview of users who are assigned to their section that would be pretty easy to add But we don't do that by default I think simply because most people don't want to look at that stuff In fact for most of our editors we want to we want to keep them away from that that kind of thing And there's there's someone a couple rows up So I have a question. Let's assume we have the Sports section of a website. This is a problem. We're facing and we have a very big editorial team One team that is editing the web version of the site and Drupal is also Serving a mobile version of the site and the sports section Appears in in both versions of the site and For several reasons, we don't want to make a sports mobile section and a sports web section web section We want to have that same Could you split up the permissions? So the sports mobile team Can have their own permissions Versions versus to the web web sports team You you can that's it's that's a complicated question and it depends on how you're splitting the mobile site out Um in the barnard case barnard actually uses domain access Which is another module that I maintain to split content across his departments And they they literally have domain access and workbench access separating stuff for them Which is really kind of interesting. So you could do it something like that In your case, you might need Separate piece you might need another additional thing It's it's a little complicated in that case. It would depend on again How you're splitting out mobile versus non-mobile So I have a client at the moment that wants to review Multiple pages is there is there anything in content workbench that Helps solve that problem. There is nothing in workbench that will solve that problem That's actually a pretty nasty problem to solve But I could tell you how to do it using views bulk operations, you know You could do it It's that's one of those that's one of those Problems that I would put squarely in the category of I want a UX designer to even to look at that before I even try to write a line of code because if you if you approach that in the wrong way, it's going to be absolutely unusable You can you can do it. I mean views bulk operation supports that kind of thing I have a piece that we wrote for the minnesota public radio archive They they imported a bunch of data from a legacy system And they can literally go in with views bulk operations and pick like 20 stories And look at the title and the body text at the same time and rewrite the headlines for like 20 stories at a time And save them all at once And doing it for individual fields like that is actually really easy and there is a UX pattern for that But if they want to view the entire thing, that's a little harder So I've got two quick questions or maybe not quick question but two questions. Um, the first is Does workbench allow for syndication of content across different sections And then the second question is I know that media isn't very far along But what's the state of workbench and media now and the kind of roadmap for that? If you want to take the first I'll take the second Exactly Yes, you can syndicate something across several sections you By default you can assign a story to more than one section Just like you could assign something to more than one taxonomy term So yes, you can syndicate something to multiple places And the the warning I put on that is that it might confuse some of your editors Um, so some of our clients don't want that so that's actually configurable Whether or not you can send it to multiple places All right, and uh, so with regard to media, um, you know, as Ken mentioned earlier We've been really really involved in in working on media and in the media issue queue And uh, it's I think not quite official yet or officially announced yet, but I would expect to hear About an upcoming sprint You know where we're working to get Media to a stable release for Drupal 7 You know precisely so that it can among other things Integrate much more closely with workbench so Ken's put up the feedback slide. Um, so This is something I was one of the chairs at Drupal con chicago and Both as a presenter and as a Drupal con chair Having great session feedback For past Drupal cons is really really helpful and important My understanding is that the the actual links on the sessions For submitting feedback They might not be live yet, but I know that they're working on that today and that those links will be live soon So once they are please Go to the Drupal con website. Find our session. Please submit your You know evaluation and feedback for us. It's a really great and valuable tool And thank you very much