 Wydwch gyn nhw'n dwynd i'r ysgrifiadach nifer yma, ac yw'r ddigwyd dwytaeth ar gyfer yn gyfaint ylleywyr â'i cyfaintol. Fynnwch chi'n gweld o'n cael gwneud am y canfodol a'u inchbod? Wédwch, rwy'n gwybod. Rwy'n gofio. fe wnaeth gweithio... Fyny'n eu fan gwlu ffordd. Mae'r gweithio yn yr oed. Rwy'n gweithio yna'r llwyffos. Fyny'n gweithio'r llwyffos, rwy'n gweithio'n gwneud ar gyfer. ac mae'r hyn o'r lleidwch am fydd mawr. Felly, mae'r frelanser, a'r ffordd o'r frelanser, mae'r frelanser yn y cwestiynau ychydig, fyddai'n gwneud o'r lleidwch am y trofnodol a ddiddod i ddwy'n gwneud. Felly, mae'r frelanser, mae'r lleidwch, mae'r frelanser yw gallu gwneud o'r lleidwch a fyddwch sy'n gwneud, i'r ffordd o'r lleidwch, pan mae'r lleidwch arall, ac mae'r lleidwch a'r lleidwch yn gweithio. Mae'r gwelod o'r cydrion, ac rwy'n cael ei wneud yn fawr i'w dweud ar y caniwl. Rwy'n cael ei fawr i'w dweud ar y caniwl, ac rwy'n cael ei gwas o gan. O'ch gael y bai'r grey. Yn amlwg, efallai, yn yna ddefnyddio allan, byddwn i nhw'n haes bwysig. Mae'n meddwl i'n mynd i'w dd ding, a'r command ychydig yn i'u ddebyg, pan pwysig, phasun â'r cwmaint, y cwmaint eich dadur o'r ddegyn, Felly mae'r ydych chi i gyd yn blaen i gael'r proses a how-about, y gydigau gwirionedd i'r bwysig, i'r ddiwylliant yw'r gweithio, mae'n ffyrwyr a'r gweithio. Mae'n gofyn nhw'n ddweud o'n ddwy'r hunain yn ymdiddellai'r cyffredinol yw, mae'n gweithio'n amser. Mae'n gofyn nhw'n ddweud o'r cyffredinol, mae'n gofyn nhw'n gweithio. Felly mae'n gweithio? Mae ydych chi'n gweithio'n gweithio'n gweithio, I don't know whether that's going to help. Well, completely straight. One of the problems that we have with Iwami is that first impressions are incredibly important. And we know that people is like an incredibly good piece of software, but it doesn't always come across that way when somebody first installs it, someone gets hold of Drupal and installs standard or minimal. The initial impression that they get is not necessarily as good as the software that underpins it. This is what Drupal looks like after installing standard. Who thinks this is awesome? Without any sense of irony or misplaced loyalty, this is awesome. Isn't that different to how like Drupal 6 was? I'm not sure about Drupal 5, but in fact he filled in a whole lot of posts on going back and trying to install Drupal as far back as he could. This is kind of not that different to like 2 or something. So it's not a very good first impression of Drupal and the capabilities of it. So what is Iwami? How will we try to address this concern? Iwami's had installation profiles. Is everyone happy with installation profiles? No. Okay. So installation profiles are a way of installing Drupal with some prepared configuration and sometimes some code and a set of modules that you've chosen to gear it towards a specific purpose. If you've ever installed Drupal, you will have seen some installation profiles. You get a choice between minimal and standard when you install Drupal. Those are the two installation profiles that come with Core 5.0. So what we're doing here is giving a stirred installation profile with Core that is better placed to showcase the capabilities of this piece of software. Okay? That's why we call it out of the box. It's to demonstrate what you can do with Drupal without any contribution modules, just what you can do with Drupal 8.0. And with Drupal 8 you can do so much more than you could with Drupal 7 without having to resort to that fact of contributing modules. Who is this time to that? Your Mami installation profile is a demo and it describes Drupal for evaluators, people who are looking at Drupal saying, is this the right fit for our organisation? Can this do what we want it to do? What does it look like? Also technical evaluators can take a look at it and see how you do things behind it and see what is an example of an implementer site actually going right. It's also useful for developers and site developers if you want to have a look at the new feature in Drupal and how to develop what configuration you need to make it fly and what changes you can do, you'll find that they're actually adopting lots of new things into this as they get added into the core. And it also lets us evaluate different Drupal features as well. So how did we actually get here? This has been a very long journey that's had on a lot of people. This is not nearly everyone that's been involved in it, but Llorie Asgolett has been a driver of this for a long time. Just to the two of us, there's done a hell of a lot of work with this. KeyJ has done a lot of work on the design. As you can see with KeyJ, we have Sharon J over here. We'll see a lot of recipes. Sharon has made all these recipes. She's invented them so that we don't have to worry about the copyright recipes and so that Key can focus around them to include them in the demo. So a lot of work on in there. We actually went and assisted that Sharon J created through Drupal.org and counted so that she could get a commit credit for all the work she did cooking. I'm not going to read more than that. Mark, I've always been really important driving this forward. Llorie, Llorie, I'll publish these slides so you can have a load. There's a lot of different roles. Obviously, we went here really important in actually giving us a bite, giving us the roots in suit, the powers that would be so that we can actually get this thing in. Roy Sholton, very important from the UX point of view. We're building something that's the 80s or experience, so we need a guide who is very similar to the UX within Drupal circles to guide us and give us inspiration there. Gabor Hotski, Lee Rowlands, Llorala, have been really good at being committed so when we get so ready to go, they guide you around to say, can we put this in yet, and actually get it committed. Terry Fish has been really good at helping us with the light issues and Henry McPherson has been really good with a lot of the accessibility work we've got. So, lots of people. This has been gestulating in some form or another for ten years. If you actually looked at the initial issue that kicks us off, the concept about it is some sample content at the core. It's actually got a five-digit node number, 79582. So, that's the only five-digit issue that I want to ever get to know about, I'm pretty sure. So, it's been going on for a long time, and then a couple of years ago in... Is there a couple of years ago that used to go by? It feels so much longer. A lot of momentum was gathered there. A lot of people got together after a couple of sessions there. And going forward, we've been doing weekly newsings that we have a Slack channel, and we talk about this, and they have a program and the sample content merged together into one initiative to develop something that looks Slack, something that's well-configured and has some nice contents that people can actually play with people at the box. It was originally... There was this farmers market idea around default content. That was going to be the model, but we moved to our kind of food magazine and saved us from the best. A bit better place to showcase the features of people that we wanted to include. Everyone's still keeping up. Everyone's still going. So, what do we want to do with this now? We wanted to improve the understanding of people's core flexibility and capability to evaluators by providing an on-boarding experience. This is something you can put in front of anyone that can start playing great and make changes to it and see what happens in a way that they can't really do in relation to front bars. It's a much better way to demo if you're trying to show off briefly, if you're trying to say this is good, it's a much better way to spin on that and show what you can do about adding any extra code to it whatsoever. It's a scenario that's suitable for growing with people. We've seen if we have this experimental process where we can add contents and if they become stable in core we can add these features to it and we can do that and then showcase them and see what they can actually do. It improves the perception of Drupal's capabilities. People will not just install Drupal and go, oh, it's like WordPress that I'm hard to use. So, it took a lot of time to plan this. I say, really, I still wasn't involved at this point. But actually, I advertised a goal for the designer, and that was Keith Jay for five months. He was leaving the design world and other designers were involved. And then there was a long period of just doing a design process, getting it to look like it was looking. Before developing a more formal style of knife and then actually implementation in anger going on September 2017. And then in February 2018, just last month, we got it into Drupal 8.5. So, when you get Drupal 8.5, you want to release it to the cheese house boom, this month, right? It will have the money in it. If you go and play with the release time of it and download it, you can actually install the money down there and see what we've been doing. So, this is now actually particle. So, people don't believe me. It is. I don't want to prove it. So, the design process. So, we started doing this like a proper project. We used stories looking at different evaluation roles that we've identified. We built a concept model for the MVP. So, we have a couple of concept types. Articles about food recipes and the fields involved with them. Images, difficulties, tagging, that kind of thing, that kind of thing. We framed it against the concept model. You can see that there was a community review under this. No number. We're well out of the five video ones now. And this is what the front page came up with. But this is the output of the design process. So, you can see we've got some very cool Drupal stuff here, like content types and views, blocks and menus and items and so on and so forth. Most of the stuff we've done is demonstrate with Drupal. And it's at this point that we can definitely solidify on this idea of having it being there. So, this is Imami as a brand. The magazine style really helps give us a lot of reading space. It allows us to have a light touch of the thing that we can play with while exploring the customization later and doing more with it and then promoting it. Very, very cluttered. And the concept types are really, really flexible to allow us to do many, many different things and ways of building them and showing them off. So, you can see that we've got like menus and search showcased at the top, blocks and custom blocks. Promotes of content types, fields, views, end styles, responsive images. I'm not sure we've got responsive images in here, but a lot of this stuff is in the design. So, there are a couple of things that like maybe were in the initial design, but we've still not actually got into FOIA. We have static content, we have dynamic content and people can edit and do that. We have many boxes. Recipes themselves are categorised and targeted. So, we can categorise them by difficulty level. So, we're leveraging, tagging to do that. Lead images used for cars, but at least the images. So, we have a lot of photography that we've got, custom blocks and text fields. So, to be able to just contain the list item and then each item that you need to make a recipe or each ingredient is just a list item within the list. We could actually use our own fields for a piece and have multi-value fields if we wanted to do that, if we wanted to have a bit more flexibility with our content model. And again, this is the instructions for making the recipe, and that's another text field. We also have a related content in the design. We don't have that apart from buying the terms yet. It's like an example of a video demo that we have down here. These are very difficult to see. I do appreciate that, but we'll boot them up bigger when we're actually looking at this for wheels. A couple of challenges. The recipe content type is themes currently made around hard-coding things in template art. And we'd like to actually use something like field layout so people can do some work to do to actually use the full power of some three-fold features, especially more recent ones, like field layout. So, when we have a full layout tools, they will update farming as we go along to make sure it works and uses the factors. Also, the layout builder that's gone in is experimental. I don't know if everyone's playing with that. So, if we don't have that, I need to fight people at the moment. Once that's stable, we will then be rich. So, all this content is created by us so that there's no copyright issues and it's licensed to people. So, the photography, the recipes themselves. That gets around any kind of licensing issues because it's all going into core. We're going to extend core to sort of things like file image fields to the media fields going forward. So, media's just becoming stable in each point of time. It's not that much you can do at the part of a media browser yet. In core, we will have media. So, we're already working on how we can implement that changing our content of spring media. And then, because media's in, we don't just have to update what's there in the images and new videos to do that. It also gives us the ability to tap audio of a video so we can extend this by actually recording video recipes or blog posts or videos of people should it sort of come in the right way. So, it actually allows us to use more things that are in the public domain. We've actually changed the licensing model for Drupal in a day at that for the requirements of the Mami. So, the Mami, something as well as being built on top of Drupal, is also helping to influence some of what's going into Drupal. We can actually say, this will be better if we did this because it would help the Mami. Another example of that outside licensing is someone interested in migraines. Okay, it comes to my talk this time in D200 where we're going to talk about migraines. But, that is the issue to migraines source, CSB, so we can use the migraines module to migrate content into Drupal from a CSB file to migrate to actually build a lot of content out of the install because we have our own process to do that because we don't have enough back-end in core migraines to be able to do that. So, we're using that tonight to pull in another migraines back-end into Drupal stuff. Okay, so, actually building the demo. I can actually bring this up on PHP stone because it's probably a bit easier to do. How does that look? Is that readable? We can kind of see this. So, this is a checkout of just Drupal 8.6.x, the latest development version of Drupal 8.6, checked out with Composer Install Run and nothing else done to it. So, if we have a look in our core folder at our profiles, we can see as well as the minimal and standard that you'll see when you're installing Drupal normally and all these testing ones that are hidden but still used for testing purposes. We have this one called demo umami. And it doesn't really have that much in it to achieve this. We're not trying to show what you can do if you write like a whole metric ton of code. It's what you can do with Drupal mainly by configuring it. So, the bulk of what we have is just config that we're going to import when we actually install our install profile. That's lots of config I don't need to explain all these different config items and stuff. That would be a very little even dullness. We have some optional config as well. We have a bit of CSS, but we're not installing profile here. We're not in our theme. Why have we got CSS in our theme? So, we actually have a warning that we put up because this is a demonstration profile. We want to be really careful that someone doesn't install this and go, oh, that's brilliant. This is nearly like my site. What I'm going to do is I'll install this and make a couple of tweaks and then that will be my site forever. We do not want to have people building their live sites with this. It's for demonstration purposes only. If you ever talk to anyone who's done a lot of work with commerce, you know how many actual production sites are out there that used the commerce kickstart demonstration that was never intended to be production. It's actually out there and churning through money and doing whatever. We really want to avoid that. There's a little bit of CSS because we put a warning in the toolbar. We tell people, if they're on an administrative page, we want to show them the thing saying, this is for demonstration purposes. We have a couple of other places where we try and catch that as well. When we come to, say, people at a point of service, say we've moved everything to the media. Say, well, I've moved it to the media and I've not filed it. If someone wants to use this ground for it, they might try and update it most of the group that they've installed it from. If no one should install something, as they want to say, I'm going to improve it. If we've changed how the marmig works, then we have to write migration pass to everything somebody would possibly do to the two different versions of the marmig that are wired together in different ways. The bad practice in 8.5 won't be the bad practice in 8.6 and 8.7 and 8.8. There's a lot of opportunity costs in white and info that we've done, and the only intention is not that we do that and that we don't incur that. Now, this is an ongoing discussion. Some people say it wouldn't be very good if you'd demonstrate something to somebody and then you could actually demonstrate upgrading to the next version of the same thing. That's a valid point. So we have some issues going back because there was a lot of discussion on that. It wants to make it clear to people that this... Presumably there is a way of, you know, so you can have my restaurant theme or whatever. So you can sort of force, potentially, the current status up there. So what I suggest that you would do with that is you could take the configuration you are interested in from your marmig, which will give you the content types. You can maybe borrow the theme, but the theme may be a little tightly coupled at the moment, and that's something that will keep an eye on going forward. It's like how tightly you're becoming the theme that we use when we go for this or actually what we do. Does it make sense to actually spin a lot of things with themes if you can do it by itself outside of the program? These are all ongoing discussions and valid points. There are some tricky issues around it. It seems to me a bit horrible to end up with an installed profile and then say, well, actually, no, you can't really use this. You too can achieve this if you put in lots and lots of hours and hours of effort, but we're not going to let you use this one, even though it's almost exactly what you want. Maybe I'm being stupid there. That feels almost worse than not having it. I don't think it's about to say it's worse than not having it, but I think it's valid. We need to be careful around the expectations here. We do let people know, so that's not the only warning we have. We'll see a bit that actually if you choose your marmig from the selection you will get a special warning that says this is the demonstration purpose of that. So, yeah, it's a tricky thing. That's some of the reasons. There's probably more than people who've been involved with it. And certainly, if you drop into our Out-of-the-Box channel on Google Slack and ask in there all certainly people who can talk around that to shop. All right, we're very friendly in that because we may have been talking about food most of the time. You've said that a lot. Unless it's late just before lunchtime. I'm just going to check that that clock up there is right. Yes, it is. So, yeah, so we have modules, but we only have this one module and the only purpose of this module is actually to install our dummy content. You can't install content through a bunch of config. And because we don't have that migrate backend we have custom code in here that is actually going to generate our content. And you can see that we actually have the HTML articles that we're going to install. I'm going to get back to it. And we have all the images and stuff. Notice that we've had to put HD access files in here because if we didn't then anyone who site was serving Drupal could actually be serving pictures of chocolate brownies. If people went to the right location there was a real consternation that someone could go to the White House website and serve pictures of brownies rather than serving from their own food blog. So, yeah. So if you actually do put this anywhere public facing and you're using a web server that isn't Apache, like IndianX or whatever the Microsoft thing is then you will have to do your own prevention to stop people accessing like the images that we have here that is built into our people constant. And also the recipe instructions themselves are in HTML files it makes. So we did start with everything in the CSV files and it made reviewing patches of changes to the recipes really, really difficult when your entire recipe is like one field in the CSV file. So I'll split those out. So we have a bunch of tests. We're trying to get stuff into core. You can't do that without actually showing that you've got adequate test coverage. And that's... And we also have a theme that is called Imami that has all the kind of usual themy stuff that you would expect to make your site look nice. So we have some challenges around this as opposed to when you're just developing a site for a customer. Because this is out of the box you couldn't go to Contra this is to show what you can do with just people. And also you can't use anything that's in an experimental thing. Don't you have experimental modules in core? They could go away, they could be removed. Some of them nearly work. I don't think any actually have them removed yet, but one of them was their institution. And the APIs of them might change as well. So we don't want to show people doing six months at the next release with Drupal. We wanted to show what you can do with stuff that is stable with Drupal and or included out of the box. We couldn't rely on any patches that might not get committed. Some stuff actually even wants to get to RTDC still though it gets committed back and forth. And we couldn't drastically affect the file size of Drupal. So it had to do a lot of... Because we can't just like 10 meg of lovely images. But we couldn't, you know, all this stuff was really nice and it keeps pictures of the lovely us. We could totally have like whacked into it if you made that everybody before Drupal or that load of Drupal would actually have to get as well. So it had to be really careful. Things like that. We couldn't... So we couldn't use those and places where that didn't bite us we couldn't migrate from CSV. We can't get what we get. We can't get into Drupal Core and say that we're working on a patch of data right now. We actually wanted quite that to use Playgrave to pull in there. That gives us the added bonus back to how we could really get examples of how to do a migrate in Core, which we don't currently have. We had to multiply and reduce the number of images. To make sure that's consistent we have a very strict process for that. So if you're proposing out a new recipe or a new image send the image to Keith and say you can do what you did with all the other ones. To make sure that we're using the same optimisation. So we have consistency across the aerospace and try to keep the custom code to a minimum. Our custom code is basically around some type of theme which we'll always do with the theme at the time and actually how do we know the concept and actually that people concept. Why don't we just disable that for installing it? Right, in the original plan Mark Connery was going to do an awesome bit talking about how all the themes were put together and then Mark's not here. So we're not going to do this bit. Just again, come in and slacken and ask Mark how the themes were put together or have a look at it. I'd like to do a couple of things around the template files. So I can't really do this but it looks nice. Accessibility, really, really, really important. There's a lot of considerations around here and a lot of our issues where we've done some really cool stuff and then it's kind of bounced back because we haven't fully considered the accessibility implications because we haven't really and jumped on all our stuff and making sure we're doing things like with how high enough contrast between background colours and foreground colours. Simple stuff, by far, is a real difference. We want to showcase the accessibility capabilities of Drupal now that we have standards that we've tried out back here to record. So it's a really good example of good accessible design and implementation as well. So it has to change those colours. We did some redesigning so I started off to make it that nice and accessible and also some style that I changed when it went back in as well as a basis of people that's accessible as possible. The accessibility issues, if they're raised they're considered a blocker and are not getting too stable. So we're actually committed into core but still an experiment of the bit and we've got the staples that would progress and unfortunately all the IE allowances only in time. What time is this supposed to finish? 10 to 1. OK, so we've got like 30 minutes. OK. So the process of getting into core has anybody here got stuff into core before? If they haven't, if you've got a core quicker, go ahead. OK, so lots of people have not been through that journey yet. So to actually get the profile itself into core we had to get approval from community reviews in our ideas and design ourselves and improve community review on Drupal's issues. Let's get product managers and framework managers to any reason that's a good idea in the first place and being that we're hit on missions and also accessibility as we said this is a stable blocker. So to get into core we had to address all these issues before it was considered fixed. And we had like several rounds of reviews to get this in and last year was some online presentations to all the product managers that short notice going through what we've done that really kind of kicked off their happiness to the marginalists to get into 8.5 when coming up to stability cruise for the 8.5 which is back in January. So we did get it committed to first to 8.6 because if it was committed to 8.6 perhaps a lot better to come out with that to see how it wants to get. So we had to address any issues that were going on to be using it. Now it's also in 8.5 we've shaken it out earlier when I said it's included it is there but you can't select it but we can get around that if you're actually on a plane. And the idea is that once people have gone and had a look at it and had a few more eyes on it we'll be able to go on and hide it before we get to 8.2. So maybe at 8.5.1 you will be able to do the gherry select if it's one of your installation options where it comes in. If you do have a plan and you see an initial design you will see that there's some things that we haven't entered yet. So we've done very much an MVP it's very cool in feature but there are some things that we haven't done yet. That's just time we've spent for it. We're going to do this, we're going to extend it as we keep this live as we go forward in core. Let's think about some of the things we're going to do in the future. Tor module Who's used Tor module? Okay so there was an initial plan that we would actually use some kind of custom block solution and Tor modules in core can actually build these features using stuff that's already in core design that we're going to implement there. You'll see that this is actually called something else and it's called an original version of this which is called salvo rather than rumami. Salvo just sounds the opposite of rumami. It's like what's happened to somebody when they're over rumami. So we're not doing that. Media we talked about not just actually converting our images to media but looking at the opportunities that has for including video and audio. Layout builder. We want to use that so we can showcase it. If you haven't played with Layout Builder it's awesome. It's found another way of interacting with your content rapidly. It's really nice. Migrates. As soon as we have that CSV setting straight. Setting straight has gone into core so we already have an issue to start playing now with that. How nice is that play with rumami? Setting straight is where it applies up on the site when you're doing configuration. So we've been playing with that if we've got any CSS. It's actually going to cause conflicts with that made that play nicely. Content moderation. We haven't implemented that yet but content moderation is now in core and what's really cool is that we've got a powerful piece of the group so we can actually come up with another language and have the ability to have the CSS language to play behind it. That's another huge boost to showcase the end of what we might be looking at. So if you want to get involved this is a really good project to get involved with core. We've got a whole bunch of people who've never contributed to core who have come along and helped out with recipes that have reduced the standardizations and I got involved in this because me, along with Phil Mawrthyn, I ran a Maccabe when the user group up in Manchester and to be honest we didn't have anything fine for January and we knew that people had been talking about the box just like a word so we had a look at the user group and we started to see issues with the recipes so people started to come to think of back to that and a whole bunch of people who never managed to get to me in true core thought out something that only like crazy people did. I haven't had a lot of arguments. Now me who's a developer from India has actually got a scholarship to go to Connord National based on his contributions to true core. So there's a load of ways to get involved with this. If you want to get involved look on the issue you've used for the component in the Mawrthyn effect demo or for tags out of the box that's the main two ways. Not everything out of the box has to do with the Mawrthyn demo for instance the issue to put the CSV, migrate back in that's an out of the box tag because it's doing it out of the box but it's not actually to do with the Mawrthyn demo at the moment. So check both of those. We have Out of the box channel on Slack every Monday at 4pm and that's just normally announced very close to the time in that Slack channel so if you hang out in that Slack channel and you want to get involved or see what's going on for you have any questions do that. Because we don't have that one. So we have here let's move this right that's the wrong one, that's migration that's tomorrow's look is that kind of readable let's go bigger so here we've got this is just folder that I've got here I've just checked out the latest 8.5.x and done a composer install and I have trust the database so if we have a look at what that looks like so 8.5.x and so I'm going to choose this in English oh that's standard and minimal can't see it because it's hidden but over here this is 8.6 latest version I've heard and if we have a look at this one standard minimal demo it's really tempting to do the umami in the Vic Reeves Uwabu voice which just derails any meeting or call that you have with it so here we have a demo and if you select this, this warning pops up for demonstration purposes only if you want to tell people about that and then save and continue and it's kind of like installing Dripal normally and it's complaining because I'm just using my local environment and Skol but we don't care okay that's going to go away and install so if you want to play with an 8.5 um back here you can install it if you use Drush so can we read this, can everyone see this at the bottom so let me up yep okay Dripal site can store and our profile is called demo okay we've got that yes Drush 9 nice is everyone using Drush 9? do you like it? yes okay have you had a look inside Drush 9? does it make more sense than Drush 8? cool right so okay that's that's installing Barley command line, let's see where everyone's up to we can do questions while we're doing this if anyone has any questions that we haven't reached so far just shout them out with me and if I don't like them I'll pretend I can't hear them this is all standard install stuff, nothing new here because it's a good question and the very point of this is to show what you can do with Dripal without adding anything to it once you move the capability to do that outside of Dripal you've changed your thing already and it's like what would happen with Dripal if we add some stuff to it there's some really good things that do that already there's a really good distribution called Barbase that has a ton of contrips configured in a really nice way if you haven't played with that go and have a look at it that's a really nice thing for actually just seeing it's got a nicer theme it has a load of stuff you might want to play with it has some exciting views back ends like those graffing stuff and loads of really nice stuff if you want to show what you can do with Dripal Acria have a product as well called Acria Showcase or something Acria demo framework that's it which is also a really good like here's all the bells and whistles here's stuff from Contrib but this is like what would this look like if we totally did it just with corp Barbase, let's bring it up if you go to Dripal.org Project, Barbase I haven't used this actually for any production things I spun it up and taken some really really good ideas from how it's configured found some really nice contributed modules for it it's a really nice version of Dripal that just works out the box you can even take it I think you can no it's not its own thing but this is done by a company that invested a lot of time in doing this and adding tests and stuff like that it's really worth playing with if you haven't done so far ok right what we don't know this is Umami, look at the 8.61 ok that one's finished as well so we have just to prove that this is Umami in 8.5 here we go right there's Umami so it looks like this well obviously we're on quite a wide quite narrow viewport but this is designed to be usable on mobile looks nicer Umami collapsed the nav and carrots articles about carrots who's interested specifically about carrots who's going to look at this and go oh there's carrots or there's brownies I'm brownies right what are we showing oh so we talked about things like that additional warnings so if we go to any page at Dripal considers to be an administration page maybe we're going to look at an article and we're going to edit it here's a list of articles draw your own herbs ok if we want to edit this oh no there's a total warning here so this site is intended for demonstration purposes ok so if you're actually so it doesn't show up because we're trying to give a demo from the front end and show you kind of things and we don't put this in your face all the time but if it looks like you might actually be trying to achieve something change something then we're going to remind you no there's something about this and at the moment this actually points to page on Dripal.org so you can go and get more information which might explain better why it's a bad idea to actually use this to build your site going forward ok so we have what we've got actually in this making it so we have a couple of content types recipe and this probably is exactly the same as the core article images tags recipe has a couple more fields author, cooking time, difficulty look we can use the build views tag so on so forth it probably has some shared configuration but there's no it doesn't actually inherit from the standard profile I think there might be some issues floating around in court about making profiles depend on each other I'm not 100% sure where that's up to again the proper people giving this presentation would be able to give you a much better answer so so we're kind of about out of time so we haven't actually had a look to play around with it but at least you know how you can spin this up have a look at it where you can go if you have any questions that I haven't been able to answer or if you want to get involved the more people we have helping out with this there's loads of things we need helping on in fact let's have a quick look at the issue queue for this ok this is just like the current status of what's going on with different things making things better, improving things adding new recipes we have a recipe for chili sauce that does not get gone on that I'm quite keen to get at but don't eat it unless yes so yeah so that's time so thanks very much and if you're interested in my great from my other talk tomorrow sit at the same time but in a different room thank you oh I thought we did the questions we can do more questions I don't mind oh quit another thing no no there we go complete aside just while I have people's attention as I said earlier me fell in arena run the use group up in Manchester come along we're always looking for people to come and give presentations and also in November we'll be running our third on conference we've done it for the past two years probably the first weekend but we're still finalizing venue and stuff cheap event no formal thing and anyone can actually come and talk it's a great alternative to camp style events because you'll see people you don't normally see get selected being able to give talks and you'll also see people you do normally see get selected trying out new talks before they try them in a more formal environment plus it's really cheap compared to camp events so do keep an eye on the NWDUG Twitter account for any announcements on that we'd love to see you up in Manchester in November or before that thank you I'm really good dude No, Sam's the only thing there for a bit Hey Baris Oden Do you know Liam? No My mind's certainly gone My mind won't work about So I was just wondering what if blinds asked you what if this looks like almost the rest of them won't just different followers So I would take a look at the the thing, just copy and paste it right you could create your own install profile you could import from standard and then import the config from umami you could there's a patch there's a module called config installer no, install profile generator so you can actually take a working site and generate your own install profile from it and that will tie you into the updates going forward so that's an option it would get the core updates not the umami updates so you can have the updates in the install profile so you still get your security fixes and stuff but you wouldn't leak in any changes that have gone in there so that's the kind of things that are the stuff yeah and then after we launched the umami thing came along well this is kind of 80% of what we just built you're the people we need to be careful for so yeah that's the kind of thing I'd explore certainly take it, use it, build it but don't use it as the install profile going forward well certainly there'll be a bunch of us who'll be at front end anyway because I'm coming to front end I'm sure Mark's coming in right he's been one of the main drivers so there'll be Larry might be but the other one the Spanish guy Ruben he's leading the sprints the Preston will be there as well but on your first day we might make it then in the IE 11 if we're at front end as well how's the planning going for that how's the planning going for the day before yesterday we got our main sponsor our main sponsor we have the main sponsor pretty well 925 we're safe with budget now that makes it we can spend more on making the events awesome wicked I'm really looking forward to it I'm really expecting 500 I think we can make that we already sold 250 tickets I'll better check I've got mine I'm not sure I'll catch you around hi thank you