 Summed up, and now I know there's a lot more to it, but in terms of user experience for creating content, there's finding, editing, and placing. So of course, finding, again, Drupal has kind of the basic administration screen, which, you know, while it's helpful, doesn't really answer a lot of the needs of, you know, really wanting to get the content that somebody created, finding it easily. Editing, the traditional node forms can be tricky at best. They can be 18 screens long, and I think for normal people, it's daunting. There's lots of forms, there's lots of fields, there's lots of little help things. There's the wonderful little sort of whizzy-wig HTML drop-down below the editor interface that just looks ugly. And lastly, placing content can also be quite tricky with most Drupal sites. So how do we make Drupal better? Well, I'll talk about a little bit of a tech, but I'll try to keep it to a minimum. Basically, I want to show sort of patterns and practices of things that we can do to, again, improve the usability of a Drupal site for the editing of content. And there will be a little bit of tech talk, but I'll try to keep it to a minimum. So I'll show up hands. Is there are any developers slanted to people in the room? Okay, so a decent amount. And more of content, sites, builders, it's a good mix. Yeah, I really wanted to aim the talk. Really, I sort of best practice content workflow. And the reason I sort of can say best practices, I've worked with a lot of very large scale projects and I've worked with a lot of really good teams doing really good stuff. So it's not just necessarily my viewpoint, but it's sort of working across the last six or seven years on quite large scale projects, 10 users, 100 users, five users using the system and millions of people viewing the site. And I'd also like to make it interactive as well. So stop me at any time, ask me questions, say I'm wrong, say my ideas are full of crap, I'm happy to hear that. Just let me know. So stop me at any time, please. There will be time at the end for questions, but, and lastly, the main thing is demand more from the developers in the room or the developers that are working in your site. Cuz there are some things that can be done that aren't that difficult but do make a tremendous difference. And you don't have to hack core, you don't do anything crazy. And basically everything I'm going to show you is a contributed module. Some of them are in different states, some of them aren't fully released yet. So first off, I'd like to focus on finding, the findability of content. So essentially we've got, I've got two main items here. So there's workflow and then searching and browsing. So workflow is when a content editor rocks up and starts to want to do something, how do they do that? How do we effectively make it easy for them to first off find what they need to do and do it? Again, Drupal sort of has many different paths and generally you can go to the content admin screen or there's no really central point of reference for a user to focus in on that. So generally, they might begin on the regular administration screen, which isn't very useful and I'll be switching back and forth between lots of tabs, so sorry for that. But there's this really nice module called Workbench. That module, essentially what it does, it kind of creates a user landing page for that editor. Here's the administrator, administrator of the site. And you can see they're basically the recently edited content over here. It shows you the type, if it's published or not, and when it was last updated. And then down here you can see just the overall content of the site. And these are all views, so they're all fully customizable. You can create essentially any sort of tabs and it also integrates really well with the workflow, Workbench workflow. So you can say, I want to see my content that is waiting to be published. I want to see my content that is in review, and so on and so forth. And there's just additional tabs at the top for that. So again, it gives a nice landing page. You just essentially go to my Workbench. You can actually make a user's landing page as soon as they log in. And it does gives a nice really concise point of reference for that user. And then there's also a nice little tab over here for creating content, so anything they're allowed to create, they can quickly then create new content to keynote. So that's, now it's good to searching and browsing. And that's the other kind of source, but I think, and that's the one area where you can make immediate benefits for our end users and the traditional Drupal content finding screen is pretty blah. I mean, it allows you to, I've got the good ones. I want to show you, everyone's seen a bad one, I sure. I'll just skip to the good one. Here's one that's called Enterprise Base. What this does is it allows essentially a customizable entry point to content. And you can essentially add any fields that you want that's pertinent to the content creators. So we've got the normal published, promoted, and sticky. But the other nice thing is author. So there's a nice auto-complete for author in there. And probably everything is mean, so it's anonymous. You can also do contains, and then there's a nice little drop down for tag, so a user can say, I'm looking for all my content that is tagged as cartoon. Click on filter, and immediately you can see, and you can also see you can actually customize the actual results. So you get a nice image there, which again helps visually to see what the content is. So it's quite a vast improvement over the, it's subtle in some ways, but it is quite a vast improvement over the traditional way where you get to click one thing at a time to view the results. And you get, no matter what content type you have, it all looks the same. And it's hard to actually find out what that is. And this module again also has these really nice features so that again, it's available through drop downs and things. But you can say, okay, I'm just interested in articles from myself. I'm just interested in, let's see, do we have any, I don't have a lot of content, sorry, I mean I'm interested in events that I've created. And so immediately you can just drill down to the content that's relevant to me or anybody else and find it quite easily. The question was what's the module name and the answer is enterprise base. Enterprise underscore base, I think it was what it is. And it was created by level 10 and it's still in a beta form. But really what it is, it's a pre-packaged set of views that override the traditional content screens. And the nice thing is as well is you can actually customize the results per content type. So for events it might be more, you'd have the event date and maybe event location or anything that's relevant to that specific content type. Because in general, users tend to, I mean developers think of everything as a node, with fields and everything's the same and it's all, everything's wonderful. But real people think of them as actually different pieces of content. There's an event, there is an article, there's a blog post, and it allows you to more easily find that content. So yeah, this is a great module. It's not, it's not released, there's not a full release yet. But I think it's quite close. Views book operation, it augments it. You actually need to have views book operations in it. What it, you can do all this stuff, if you're a developer or if you've got developers, you can actually do this quite easily. Really it's just a number of, like I said, pre-packaged views that integrates with views book operations and here's views book operations. You can add different ones, but yeah, it's sort of a pre-packaged version. So the question was, how is this different from views book operations? And views book operations for people who aren't familiar are a way of basically adding custom things to this drop-down menu and then being able to perform it over your content. So you might have a custom workflow that says take all these nodes and send them to so-and-so for review and things like that. Yeah, and I was going to ask too, like I would imagine if I asked the question of what do you think of Drupal's built-in view sort of content administration functions? What sort of answers I would get? So if anybody wants to chime up, yeah, yeah, kind of, yeah. You use your site to find your content. I was working on a fairly large project actually last year with quite a large site that there was a point where there was going to be a demo to the company. So for them to actually get introduced to Drupal. And again, this is where the developers weren't sharing love. Basically, half hour before the onsite demo, we sort of whacked up a few quick views and things like that in using view book operations, a few other things. Just to get rid of, because we know that everyone hates the built-in Drupal administration. We've never had a client like it, and it's not intuitive. And basically people kind of just kind of think, well, this is it. So again, I'm very guilty of all these things. And hopefully trying to get better at them. So my name is David. And yeah, here we go. Here's the built-in Drupal screen. So everything is quite painful. You can only do one thing at a time. You can't type any search features in there. You can't sort by tag, author, and things like that. So it's quite limited. Okay, that brings us to the second, the three things, editing. So how can we improve Drupal's editing abilities? Again, the whole node, edit, tab thing, again, it sort of makes sense. But at the same time, I think it leads a lot to the imagination in terms of the disconnect between, and I think with Drupal 7 and the overlay, they tried to sort of improve that a little bit. But I think they kind of didn't hit the target. I think they thought that by having an overlay and having it appear on the screen, that people would feel a little bit disconnected from what they were doing. But I think it didn't work, and we always turn it off, and people don't like it. It slows down the site. So there's a case of an idea that didn't work out well. So what are some other things that we can do? So one thing is to take the node edit screen itself, or the content edit screen, I should say, and make it less cluttered and more intuitive. Yeah, here we go. Here's an example of a traditional, I'm sure everyone here has seen this, where you use title tags, body, and basically even the most simple content type is 18 screens long, and it's just a bit ridiculous. And here's the second part of it. And they did make it a little bit shorter by putting in the tab thing. So that kind of came around in six and seven. But again, it's not very intuitive. It doesn't really kind of cut it. So one thing that's kind of coming out is a panoply, which is a distribution of Drupal. And it's sort of an entire best practice way of building a site from start to finish from the back end. So how to better find content, how to better edit content, and how to better place content. And it's not quite finished. And I think there's actually a talk later on today about Panoply, which I would recommend everyone to go to if they're interested. But it's a really brilliant system. I think phase two is working on that. Sorry, let me go through my browser here. And yeah, so here you can see very traditional edit screen. You know, you've got, it just goes on and on and on and on. And it's just quite mind-numbing and doesn't really make sense. So how can you make that better? Well, here's Panoply. Basically, we've got multi-columns. It looks a lot more like WordPress, which is quite nice. We've got Permalink. We can edit the title there. We don't have to repeat title. I think people know that. And I think people know that this is a body. And they don't have to have that huge block of text below that that explains over and over and over and over and over again what you're doing. So I think there should be a little, I got it already, button here or something like that. So it's just like, yeah, thank you. Thank you for telling me that. Go away now, please. And there's, what's that? Displacement, I'll touch on that later on, actually. Displacement is more on the visual front end of things and how to make your content shape it a little bit better. So this, yeah, yeah, I will cover Displacement a little bit in the upcoming. But I don't really talk about it in terms of that. Coming back to Panoply, and they've also sort of re-architected some of the other ideas, and this is Drupal 7. So they've basically taken a lot of the ideas from Drupal 8 and then backported them. So Drupal 8 is gonna look a lot like this. And so a lot of the really cool stuff is happening in Drupal 8, which sucks because Drupal 8's not gonna be ready until it's realized reset until maybe later this year or when it's ready. And even then when it's released, it's maybe not gonna be stable. People aren't gonna launch it, and probably maybe until mid next year when people really start to use it. So it's not helpful. Whereas they've taken a lot of the features from Drupal 8 and backported them to Drupal 7. So this is essentially a suite of modules in a distribution. So you can actually, if you have a pre-existing site, you can actually bring a lot of the stuff into your existing site and really clean up the experience. So again, we've got things like featured image. Well, rather than here's a traditional screen, here's my featured image, it's way down here. There's really no, again, it's quite disconnected from how you might think of your content. And back in Panopoli, you've got it way at the top. The image is bigger. All text is really prominent. And all the other things are hidden, which is quite nice. And then menu options, that's an important thing. It's very down in the traditional screen, into a tab right here, and there's a little thing, provide menu link. And then look at that. It's just 1,000 options. It's just weight. What does that mean? I really don't know. And I'm a developer. So it's just really dumb. And whereas on Panopoli, they've actually thought about, well, what do real people think? How do real people want to create content? How do real people want to take that piece of content and put it into a menu structure? So you can put the title there. And then you've got the linking it into there. Publishing options that simplified a little bit. Again, it's a bit more like WordPress, which is good. It's nice to learn from somebody else. And now we've got admin, date, and time, and things like that. So it's taken a lot from WordPress. It's also taken a lot from a lot of the UX UI things from Drupal 8. And like I said, really bundled them into one really nice system. And I'm not sure when the release of official release of Panopoli will be. But again, there's a session later on today, which I'm sure you can ask the fellow or when that might be. And then lastly, so yeah, there's the Save button. So yeah, that's a really nice system. And to be honest, I actually just learned about that in January. Like I said, I'm a developer. But there's so much things going on. And everything's kind of like Drupal 8, Drupal 8, Drupal 8. But there are some sensible people out there that are actually thinking, well, that's very far off. We've got lots of clients. We've got lots of customers right now. So let's let the Drupal 8 people do what they want. And let's take what they're doing and apply it to the masses. So they're definitely sharing the love. So if you see the people from Panopoli Distribution, they thank you for some good stuff. You can customize it. So basically, it's using panels. Panels is sort of a drag, drop kind of thing. And what they're doing is they've technically taken panels, which allows you to override anything. And they've overwritten the note edit screen and just made it look pretty and made it look make sense. And so definitely out of the box, if I go back to this edit screen here, if I had, say, 40 fields in here, by default, they would just keep on appearing down here and on. But it would be up to you to maybe push some of those to the sidebar. And I can actually show you to, this is kind of jumping ahead a little bit. You would actually get, these are some things we'll be showing you soon. You would actually get to, say, change this layout. So your note edit screen, you can imagine you could actually choose any one of these layouts for your note edit screen. Whatever would make most sense for that. I mean, you could imagine there would be an image gallery where it would make sense to have the user could actually click in each one of these boxes and add an image, and they visually see what that looks like on the edit screen. Any one of these things can be used as that note layout, note edit layout, as well as for the front end. So it's pretty cool. It really opens up a lot. And again, this stuff was available, has been available for a while with pure panels. But I guess, to be honest, I've always really not liked panels. I've never used it for a lot of reasons. Performance and UI for two. It's really heavy. It does way too much. And the UI is awful. So you're making an awful Drupal UI even worse, but putting panels in place. And so again, the nice thing that they've done with Panopoly and a lot of things they're doing is something called Panelizer is they've sort of said, OK, panels is a powerful engine, but it really sucks to use it. And no one can make sense of it unless you're a developer, there's always overrides, and it's just 800 screens to do any basic thing. So what they've done is they said, well, why don't we just have a button that says, change this layout? And so you can literally click on that button and then change your layout. Anyways, I'm dumping it out of myself. And I need to, I'll get to that when I get to the placing that comes in. You can. Panopoly is a Drupal 7 distribution. It's in a sort of a release candidate stage right now. And it's a suite of, there's a number of Panopoly modules, and it's also bundled together a lot of existing panel modules and a few other best practice things as well. But you can, I hope they'll document it, but it's definitely effective. You can grab those bits that they've done and drag those into sort of piece of meal into your own site. So you can slowly improve over time what you have. I wouldn't recommend basically dropping it all in place. You might want to start with the node at its screen at first and clean that up. And then start adding the layout. Because you're also, well, again, I'm dumping out myself. When I get to the placement part, I'll answer that. Otherwise, I'll be all over the place. So yes, Panopoly, it's a great, it's a great system. The other thing is how do we make content editing actually faster? It would be really great if you could actually just literally go to a page and tap on something and start editing it. That's what Spark does. So Spark is also, was a Drupal 7 thing? And then everyone thought that it's so cool we should make a Drupal 8 and stop the Drupal 7 part of it. Which, again, sucks. Because Drupal 8 is the cool, shiny toy, but it's not going to be available to most sites for at least probably a year and a half, to be honest. I mean, it might be released by the end of the year, but people launching sites on it probably, there are probably some issues. Even with 3 saying that it'll probably be the most stable system, which I agree. But there's still going to be issues. So let me jump to Spark. And again, some really nice people have actually backported Spark to Drupal 7 again. So we should find out who they are and share the load with them because it's a lot of work. So here's, again, another example of a screen. Very, you know, just some demo content, a big image, some body tech, some tags. Normally you would click on the edit thing, which everyone's familiar with. And again, you get that horrible screen. But Spark allows you to do inline editing. There's a little thing that says quick edit. Click on that. And it's really switched into inline editing mode. So I can just click on the title, make some changes. I'm not going to save that. And it's nice, too. It actually warns you that if you jump out of it, if I jump out of it, it says, hey, do you want to discard those changes or not? So it's really quite intuitive. It uses Ajax, so it's fast, done, things like that. So I click out, and I save that node. It's done. There's no sort of disconnect. And it's sort of what I think they were trying to do with overlay, but just didn't have the ability to. So I think this is a really, really great feature. This will be built into Drupal 8. But again, this is being backcorted to Drupal 7 and should be ready in the next, I'd imagine, a few months. I mean, it's ready now. It depends upon how stable you want things to be. But you can add it to your repertoire, your quiver of things. I'll have all the links that I'm talking about. I'll have on the web page as well. I know I'm talking about quite a few things. So I'll put them on the web page, and I'll update the slides as well. The question was, is Spark, is inline anything going to be core for Drupal 8? And it will be, which is great. So yeah, I mean, Drupal 8's going to be amazing in a year and a half. And yeah, this is a Drupal 7 site. So they have sort of backcorted it. And it's feature parity with Drupal 8. So all the nice things that are in Drupal 8, they're bringing to Drupal 7. And they're keeping, as they add new things to Drupal 8, they backport them to Drupal 7. And this is a Drupal 7 site I want to add. So everything I'm showing is Drupal 7. There's no Drupal 8 here. So everything in here is effectively, you can either use it now. Some of it's stable. Some of it's going to be stable. And I wanted to make sure I didn't show anything that was Drupal 8, because it's too far from now and we can't use it. And that's not showing a whole lot of love to everyone. So good question. That's coming in the layout part of it. Sorry. Yeah, so that's the other nice thing about a lot of these tools is now that they're doing all this work in Drupal 8, it's a lot of work to actually backport it, because Drupal 8 is quite a big change from Drupal 7, classes and symphony and object-oriented stuff. And Drupal 7 is nice spaghetti code, in a way. It's nice and Drupal, it's way better than Drupal 6. But it's a lot of work to backport this stuff. So here's that. So also, when you're content editing, you can imagine, Andris touched on that, mobile editing. So when the New York transit system went down, they couldn't use their laptops, things like that, or they couldn't access them in the office. They had their tablets, they had their mobile phones. They weren't using probably things like this, but how can you make your system more usable on devices, whether it's a phone or a tablet or whatever? And again, the normal Drupal menu system doesn't work well with touch. Either you have 800 clicks to get anywhere, or it's really tiny, or as you collapse the system down, the menu just goes all over the place. So Drupal 8 out of the box has, as Dries showed, a nice multi-touch-friendly interface that scales to PCs. That's available for Drupal 7 as well, touch base menu. And that's what you see up here. So it's a big finger-friendly layout, or big finger-friendly sort of thing. And Dries was saying, too, that you don't see these icons in the mobile version, because they're too big. But now in the PC version, you see the icon. And so you can't quite tell right now. I mean, I can definitely touch it with my finger. But that's all multi-touch-friendly. And you get a nice big target there. So you don't have to do 800 clicks to get anywhere. It's, again, you can kind of hop three or four levels deep to get to what you want. And you can add content, you can find content. So that's a really nice feature as well. So you can use that by default, or maybe just for your only for your mobile site. And that one is called, I don't remember. There was too many modules. So like I said, I'll put all the names on this. Because literally, I was in Boston in January. And one thing that Acquia is working on right now is demos. And we're going to give those demos. They're going to be released back to anyone who wants to use them. Because Drupal doesn't generally demo very well. And there are distributions, but a lot of times they tend to be quite one-sided or centric to certain things. And so essentially, what we're trying to do is we're trying to take the best of everything and wrapping them up into one. And so there's actually a guy that was hired in January with Acquia just to build demos and distributions. And this is what I'm using right now, his make file, which is a Drush thing. But effectively, every time he optimizes his build, I can just rebuild it and instantly have sort of the latest and greatest usable system here. So his name is Brant Wynn. So definitely he's a good guy, he's in Chicago. So lastly, getting to the placement of content. Generally, Drupal uses blocks. And again, it's sort of not too intuitive. How do you sort of place content? Do you have to have your designer do things? Do you have to ask the developer to change things? And so there's, again, three sort of areas that I wanted to focus on. One of those is automatic placement of content. So sort of thinking about your site in terms of buckets that you want to fill and sort of thinking about the information architecture of your site. You might, rather than having to manually place content in different slots, you might want to say, well, I want automatically anything tagged as this and sorted by date to appear here and so on and so forth. The other one is drag and drop layouts. And I think that was one of the questions I asked, how do you change things around? I'll show you that. That's again, Panopoli. And then WYSIWYG content blocks. And what that means, again, it's sort of a, I don't know what that means really. It's not a very good description for it. So it's better to show you what I mean. So again, I was touching on that. Sort of a bad pattern that's used to sort of place content is maybe people have seen that where you have a node and then there's like a hundred node reference fields. And so there's kind of throwaway nodes that are used for nothing else, but to just add content to and then use that for a feature that pattern is used a lot, but it really isn't very scalable and it doesn't again make sense because you have a content type that does nothing but list other content by referencing other nodes. And it's a really ugly kind of lookup as you're typing it's quite a clean lookup. So I was gonna show, yeah, basically the thing that you need then is kind of think about flexible themes, classful layouts, and then something called context. So again, this kind of comes to the notion of how do you think of your site in terms of like this bucket that you'd be filled with different pieces of content. You know, it does require the theme to be architected in a way that is compatible. And when I show you the panels layout system, essentially what happens is panels takes over the layout of the entire page and your designer effectively just creates a header or footer and a nice kind of big white space in the middle. And panel takes over that big white space and lets you do all those layout things. So it gives a lot of power and flexibility back to content creators and to site builders. It takes a little bit of the power away maybe from the designers, but it's kind of a good and bad thing. So back to content placing, good blocks. So blocks sort of is kind of, I mean it's been built in the triple since the beginning and it's a way of placing content and adding little reusable components. But again, to use blocks, you have to go to the block administration screen which can be quite bewildering. And you have every single block available and then you have to drag them up and move things around. So it's, again, not very intuitive and it takes a bit of training to understand what that means. So something better is something called beans. So beans I think is an acronym for something that's just really geeky. It's like blocks, entities are not, no, there you go. That doesn't really mean anything to most people and it doesn't really mean anything to me either. Effectively what it means is they've taken the notion of a block and they've made it be yieldable. So you can almost think of a block as a reusable piece of content that you can just attach anything to it and then reuse that anywhere through at your site. So I've got a few demonstrations of that. Here's a site that I worked with Nalsma which is the North Australian Indigenous Land and Sea Management Agency. And this was a very, very early Google 7 site that sort of just kept on being built. And so it went from Drupal beta to Drupal 7.15 before it finally was released. And so I sort of learned Drupal 7 along the way which is great. And you can sort of see, here I'll switch to the homepage here. It's got, you know, a fairly traditional layout. It's got a big image. It's got this thing that goes to the different images. It's got these things, these are blocks for instance. So basically what that means is if I edit this, so I can show you the bad and the good part of it. So here's the bad thing. This is just a block. So you've got the block description in the body. And so, you know, they have to scale that image to the right size. So somebody had to go into Photoshop, scale that image to the right size so that it fits into that layout. They have to make sure that this thing links to the right section. They have to add the right amount of text. So that's blocks. I mean blocks are dumb. They're one-stop shop for anything you wanna use. And I made the homepage before I found a little beans. So this is sort of the story of that. So this is a block. And here's the wonderful region. You know, so you actually have to choose which region it's showing up on. You know, it just, again, it just goes on and on and on and on. And it doesn't, it's not really intuitive. And whenever they need to edit this, I just tell them to, I have them email me and change it. Because it's so easy to, they delete that or they get a huge image and it just looks terrible on the homepage. And so I was really frustrated and I was kind of looking for what's a better way of allowing people to, this is the WYSIWYG editing thing. How can you have a nice layout but make it easy for people to edit that aren't designers, that aren't web developers? So here's the bad way. Here's a block. It's just, it's a, Drupal's used it forever but it's just dumb. So I'm gonna switch to a newer section of the site that we built a few months ago and when I had already learned about beans. There's a very similar blocks, as you can see. But when I click on this, they get a little thing called edit, which is kind of nice. So it's over, I'm already not, and this would be even nicer if it was using the Panopoli layout that I didn't, Panopoli wasn't available at the time so you can see how you can get better and better. But now I can put in a title. I can, this is just, I can upload a 500 megabyte image if I wanted to or whatever and it will scale it to the right size. There's the country text. There's the editor right there. So it's actually a node content or it's actually a piece of content that is edited as you would think of almost any content item and then what you use is display suite to render that into this. So it takes those five or six fields of information and basically creates this. So it's kind of an evolution of a dumb block into something much more intelligent and you can tune that to anything you want and that's where the WYSIWYG part becomes, yep. Exactly, exactly, that's an excellent point. So the point made was blocks are content and so you can't export blocks into features or into code and things like that so it really makes the whole workflow difficult whereas a bean is an entity which can be exported into code and so the placement, the content, everything about it can be, you can export it and so it works much better in many larger organizations' workflows for development cycles. So that's a technical point that is another big reason that beans and a version of beans is actually being integrated into Drupalite so blocks can become much more intelligent in Drupalite. They're not gonna just be the dumb blocks they are now. Yeah, yeah, exactly. So any field that you, like a map, you can even have a map field in there and anything you want to do at the Drupal field you can add to this, it's an entity which in Drupal parlance is effectively just the ability to add any field that you want and actually, I mean, I know that you brought that up, I can actually just show you the block. This is a live site so I won't do this. I was gonna show the fields on it but I'm not paying attention, I might screw it up. Which one? That's actually the bean. The question was, is that a block filter? That's actually the bean interface so you actually, like you create content types, you actually create bean types so you're creating custom blocks that can be then reused so you can imagine, I'll give you one second, you can imagine you could actually create and again this isn't, you could create a slideshow bean that somebody could upload six images and some text or they could link to things and effectively that could just be a reusable component of each functionality and the nice thing about beans is again it's almost like this drag and drop reusable component that you can make once and then just reuse it. I could have used the same thing on the information hub and just drag, drop it and then put in unique content because it's like a node but it's a bean so it actually integrates with the block system but it gets rid of a lot of what the messiness of the blocks. Yeah, definitely. The question was can you use blocks and beans? Definitely. Beans augment blocks and they sort of take over what the block normally would do but then again in Drupal 8, the traditional block will be sort of a relic and it'll just be beans, art bean-like things. I would say it's less than because to be honest a lot of the stuff is being backcorted from Drupal 8 so there's always a difficulty with upgrade paths and somebody asked a question to Therese the other day they almost attacked him with saying how hard it is to upgrade and he said he felt bad but he said talk to me afterwards so yeah I mean that's always gonna be an issue and every module you add to your site does make it maybe that little harder to upgrade so it's something you have to think about. Say with Spark, it's kind of a no-brainer because that's in Drupal 7 or Drupal 8 and other things so kind of the nice thing about what these people are doing is they're backcorting features. It also makes forward port or upgradeability a little bit easier but yes I mean to be honest every single module you add to your site does make it that much harder to potentially upgrade. Well no it won't be but again because these modules are really really really popular and they're being developed by some of the biggest agencies, Drupal agencies in the world, chances are they will create a Drupal 8 version or an upgrade path because they're building this stuff for their clients and they're gonna have to upgrade their client sites in a year and a half to use time so you can always bet a bit of money on a module that has maybe a thousand or more users or a couple thousand module users. You can kind of see that on the module page. A module that's got a few hundred or less probably not gonna go anywhere so yeah I mean everything I'm showing is sort of a free-for-all and it's up to I guess everyone to determine if that fits the use case or not but yeah I mean I think that's a good point. Every module you add does increase complexity and can make it harder to upgrade. They do, they do get a URL but it's not, it's generally not published if you know what I mean. So it's effective and you can also just kind of hide the path. So I can actually go to this, there actually is a URL for this piece of content which is kind of weird. So you can actually go to a page that just lists this content but of course it's kind of all over the place who's not properly aligned but you can just hide that path and then that way you don't get like in a normal system where you are overriding what a content item is and as you said you have to exclude that from the search engines or your search results because otherwise people will always land on these result pages and never actually go to the actual result that they wanted to see. And so like in Solar or in MySQL or whatever your search engine is you have to exclude these dummy content types and things like that. And then it's always tricky whereas beans do, you know, you can create a nice little WYSIWYG interface that says okay, I want to make a slideshow. So let's create a slideshow bean and have a multi-field for all the, you know, one or 10 images and then you just put a little JavaScript around that or there's actually a slideshow module, a bean. There's 15 beans that you can download and there's two slideshow ones. And so out of the box you get a slideshow and then you just drop that block on a page of beans and you add one or more images and it's got the JavaScript and jQuery stuff and it just creates effectively what, again, I didn't, it wasn't available when I started the site. I would have been able to get this exact feature here and then your CSS person can style it out of the box and it's that I had to like find a jQuery thing and this is using views. And so that's the other, this is the bad pattern too. Like when, you know, when, when somebody wants to change this what they actually have to do is they have to go to each separate piece of content and tag it to something. So you're saying, okay, well, and then you have to detag something. And so like, again, that's kind of a thought, that's very thoughtful of me to have done that. So like that person now has to go through their site, find the piece of content that they want to show up here, tag it, but then also remember which one they don't want to be on there anymore, on tag it. And they have to do that. And then the view, it just picks up everything that's been tagged to X. If this was a bean, rather than having to make them do that, they could click on this, go to edit and then just have a nice article-plete thing that they could just type in, I want these things to show up. And I have another example too of a bean, which is a little bit more simple here. So here's again, here's that demo site, this is all Drupal 7. Here's a recent article's block, bean. And it's quite basic, I'm just showing title, image, square image and some tags. And so there's five, three of them there. That's a bean. So I can click on edit. And here what they've done is they've actually created a little interface to this bean. So rather than be the normal fields, I can just say, okay, well, here's the title for it. Here's the view mode that I want. Here's how I want this thing to actually display. So here I've chosen teaser with image and I've used display suite to create a few new view modes which I'll show shortly. And I want to show, I'll just say two items. I click save. And so it's basically views, ultra simple. And see there now I've just edited that recent article's two things and there you go. So it's a really easy system and you can customize that to be as complex or easy as you want with dropdown lists and all sorts of things. So I can click on, again, you can see how easy this is for somebody to say, okay, well I don't really like that layout. You know, let me say, okay, I want to show three things. And I'm gonna use a grid. So this is another view that I've created. I'll click save. And there you see it's a nice big image, the title of the top, so it's a bit more visual. You know, it's like, okay, well, that's a bit big. I don't like that. I'll just give you the last example here. Click forever. Teaser, that's just the Drupal teaser. Everyone, you know, it's just the normal Drupal teaser. Click on that. And there, that's just the teaser just in the side column. So you can quickly see how easy it is for content layout people to have more control and flexibility over what they're doing without forcing them to use views or to sort of jump around to the site and grab pieces of content. You know, you've wrapped up exact functionality that you want that content editor to use or that layout person to use. Giving them a few options, which is really nice. And then create it as a bean. And probably it makes sense that I can actually, you can drag the Drupal out around. So that's bean. It's a really nice module and it does a lot for layout. And again, they're bringing that into the fold of Drupal seven. So that's kind of what I meant about WYSIWYG is that it kind of sums up what you're doing and you can quickly save it and you can easily see what you want to do. So it's dynamic content regions that are what you see as what you get. And in case I didn't have internet connectivity, I had some things here, but I had internet connectivity. So I'll skip over that and I'll go to layout now. So the other really nice, I think I'll try to wrap it up if there's any questions. The other really nice thing about what they're doing with panels, because panels I always felt was just rubbish. Like no one used it except a few people. I don't mean to offend anybody if they use it. I just, I didn't use it. And of all the developers I talked to didn't use it. And it just shocked me when I was in Boston in January that every distribution using panels, it's just like you're learning at Santa isn't real or something like that. Like panels is being used. It's like, oh, that's weird. But there's a reason, because what they've done is they've effectively, they've gotten rid of what was sort of evil about panels and they've made it, they've used what's good about panels. And so we've got these nice big buttons here. Like I won't even show you what panels used to look like. It was really horrible. I'm sure some people have seen it. Like it's this 800 menu screen with 800 tabs and there's no overrides with print signs. And it just wasn't good. It wasn't good. I didn't like it. So what they've done is they said, well, what do people want to do with panels? They want to be able to customize a page and they want to be able to change the layout. So here's my home page. It's really basic, really ugly, but it's just a demo site. So I think if I customize this page you get this inline visual drag and drop interface. So straight away I can scroll. Here's all my content. You can, and the great thing is you still see your content but it's just in the context of the placement. So here's the content, there's the sidebar and you can just, sorry, these are really long, but I can just grab this and drag it up to the top and that just gives you a nice drop slot. I can even crazy take that and put it over there and put this one over here. So, and you can delete stuff. So it gives you total flexibility of the layout of your page and you can add new blocks, beans, nodes, content, views, all sorts of stuff. So the views you still kind of look like this but with more ugly stuff. And so they've tried to simplify it and again I think you can filter this down so that you can say, okay, I only want people to access, maybe like I want them to be able to easily reference another node, for instance. I want them to drop in a bean. So you can add some custom, you can add, and they've done some of these nice things like I want to add a quick image to a page. I want to add a map, I want to add a table and things like that. So I can click on add a map and you can put in an address and so on and so it's kind of like bean but they've augmented into panels so that you get a lot of interaction with your page and this is again part of the Panopoly distribution and it's not 100% stable, you can see it's loading and they can't get out of here. So, switch to another demo. Here again, customize this page, I won't click on map this time, drag and drop. So there's an app already loaded there. So I can drag and drop any of this content. So again, it makes it really easy. You don't have to go to the block screen and I think there's a block screen here. I'm sure everyone's seen a normal block screen as it's not this intuitive for sure. I didn't click on that every before, I thought I'm gonna click on that because it'd be cool but it's not cool, it screwed me up. There we go, good. So yeah, and then again, I can change layout. I'm not, this is a live site so I'm not gonna change layout here. Change list layout and I can just show you, I haven't done this either yet so probably screw up but I'll just go to that and then it says, how do you wanna map, you can actually take your existing content and map it. So it shows where you're going, where you're had and where you're going to and what the preview's gonna be. So it's just, it's really nice. It's really good and you get total flexibility of your layout and you get a little bit power from your designers and you get it back to the content and layout people so you can have really ugly looking sites or really good looking sites. So I guess the power is in your hands and I think I'm nearly at time. So is it 60 minutes or 50? Okay, well then, all right. So yeah, in review, Drupal can do better. Out of the box, Drupal isn't very usable but it's got a lot of power under the hood. These modules, you kind of have to just know what modules are out there. Like I said, I just learned about a lot of the stuff in January and it's cool because I always thought of just Drupal 8 and I'm a developer so I didn't have any excuse. And there's not much code either. A lot of these things are drop-in modules so they're not all stable yet and I'm happy to put in on the module list which ones are stable and which ones are not. And you get really great results. So you can really kind of revolutionize in a way the usability of your site for your content creators which with sort of in between one and 30 modules. So the user experience for content creators, we've got finding, editing and placing and those sort of things altogether I think really do increase the usability of a Drupal site and sort of move it into another level. I mean, I think it becomes way better than WordPress. It becomes way better than many other really commercial systems and almost everything that I showed is available. Well, it's all available today but stable, maybe not. I had to put this slide in. Somebody saw me typing it as I was getting ready. Acquia is hiring here in Australia and get in touch with me or some of the other Acquia people and yeah, it's a good company. Any questions? The question was beans are great but they're not revisionable. Like a node is revisionable and if you've got a site that's got a really complex workflow or just more comprehensive workflow, how do you then not have a revision of something? I haven't faced that but they are working on making beans revisionable. No, they're not yet. Panopoli is, that's just a distribution. You can just go to drupal.org slash project slash panopoli and you can get almost everything I showed right out of the box with that. The other one that Acquia is working on is internal but we'll probably push that out is just a make file and it's just sort of preconfigured site with a few things here and there and I'll ask if we can get that. It's just on our GitHub account but it's locked away but it'd be great if we could just push that to drupal.org project. Yeah, the question was you use context for layout. Can you use beans? Definitely, the site that I'm showing here is entirely built with context. So I didn't actually get to this one but basically everything here is laid out with context and again that's really nice what beans are exportable as well so you can export your context is a way of having your layout all in code and also again it's that idea of having more intelligent layout so that basically says I'm a bucket fill me up with the stuff that you want and so yeah, I mean definitely beans integrate perfectly because beans, it's basically blocks are the wrapper and beans just fit inside of it so it kind of piggybacks up with the block so anywhere where you can get the block you can use beans. The question was I didn't touch on help as for a reason because I didn't have time and I didn't think of it and what would I recommend to put in place for some sort of readily available help for people that aren't familiar with Drupal and again it's something we struggle with with the large scale projects and part of the help that we're trying to do is making the system more usable first off so it looks kind of like WordPress it looks like Facebook or something they're familiar with so that goes a long way because Drupal out of the box doesn't make sense so that's only a little bit of the way there are quite a few videos and things like that that you can access but a lot of them are having to pay but I don't, there is the help module that you can install but then it's just a bunch of text I don't think there really is a clean way of saying like here's a really nice context sensitive help system that will kind of follow you along the way like you said that sounds good I like that. Yeah, Pam was saying that they're working on a tour module that gives somebody a visual tour of each piece and it actually walks them through the editing components of a system and I'm sure you can edit those. Is that a release? Is it on d.o? So it's a tour module. Talk to previous snacks and they're doing some good stuff. The question I'll try to summarize is this gentleman has, he uses files that are attached to nodes and those files are multiple authors and they might be referenced on multiple nodes and so how do they track the, if a file is updated, how do they track that through the different areas and he currently actually has another node as a placeholder that's referenced into the, I would say, do you use Drupal 6 or 7? For Drupal 7, there's something called media module which actually takes a file and makes it fieldable so which, again, almost like I'm talking about beans basically it's taking a file and turns it into a fieldable object that you can treat as an entity and so rather than having to reference a node which references a file, you actually reference a file and you can have any, you can revision that, you can add authors to it, tags to it, it's anything you wanna do with it, it just becomes a reusable object. So if you're using Drupal 7, I'd recommend to look at the media module and the file entity but Drupal 6, I think you're doing the best thing with the node reference pattern. Ah, that's a good question. I'm glad you asked that. There's some really cool stuff this is just locked up and I'm just not... Yeah, that map just did me in here. It's just horrible. Let me try, I think I have enough time to restart Firefox. I've got two minutes, a minute and 10 seconds, nine seconds. This is a fast Mac so it's got a SSD so it should be good for that. But of course I have 150 tabs opening Firefox so. But yeah, I actually wanted to show that. The nice thing about Firefox, it's a new version of Firefox so it only loads the tab that you're on. See, look at that, that's great. And it only loads the tab you're on so that's really cool so that's why you can have 200 tabs and not really screw things up. So let me... How does it affect responsive design? There's this really cool thing up here which actually does that. You can click on this and get a preview of what it looks like in mobile, what it looks like on tablet and what it looks like on your normal screen. So, no, this isn't Phenopoly, this is our thing but I think this is part of Phenopoly as well. So this is Bartik responsive and with theme. So you can see here's the tab-friendly buttons. So yeah, this is really cool. It gets that instant preview. I mean, that's the lazy version of just taking the browser and doing this but it's a lot cooler to click a button, isn't it? So I mean, it's the same thing but it's cooler to this like. That's Bartik behind the scenes and they've just made it responsive. So panels and stuff and it all works with responsive and it's really cool. So you can preview every panel layout, every in Phenopoly is responsive so it's all built into how it's gonna collapse for you. So that's a great thing. You can actually make a change to a page and see exactly what's gonna happen to your wonderful layout. And let me try to jump to, yeah, here's the Phenopoly distribution. Actually Phenopoly doesn't have that built in so I'll find out what that thing is and is it to Spark? Yep. What's that? NavBar, thank you. I had like 800 modules so I just couldn't keep track. I have my notes on the thing but yeah, I think I'm over here. So any last quick question? Like I said, there's a lot of really cool stuff. It's all triple seven, none of this is triple eight and most of it is probably gonna be ready in the next month or two I'd imagine or it's quite stable. I mean, don't add a map to your page because you'll crash your browser. So anyways, thank you for coming.