 All right, it's five o'clock now and I guess that I'm the last thing standing between you guys and your well-deserved drink today, so I better get this started right away. And I have a tendency to go for 60 minutes anyway, but I'll see if I can make it a little bit shorter for once. But let's figure that out. So, welcome to my session here at Duplicon around admin-based themes or the admin experience for normal people, the non-developers, which I've been looking into a little while. So, first of all, let me just use the right clicker. Is that the right one? Let me just see. Yes, so my name is Morten, also known as Morten Birch, or Morten Decay in this community, which is also my Twitter handle. Actually, I'm the one who has the business card that says Badass, so if you do not know that, that's how it is. I do run a shop called Theme Machine. It is theme machine, not the me machine, which I've seen people yesterday completely ripping my theme machine out and now just taking the piss on me. Apparently, it's because I stopped ranting about this, which I'm not going to talk about today. I'm not going to mention anything around Markov, anything else, which I've been doing for the last 10 years, which also means that my material is new today. But, first of all, just to put it very clear, I love Google very much. Actually, I love Google so much that I've named my two biceps after two popular Google distributions, Lightning and Thunder. But today, what I'm going to talk about first is the whole, like, Google history of what I call developer-driven design. So, what is developer-driven design? Well, first of all, the first time I talked about design in the world of Google is almost 10 years ago. I did a bath at GoogleCon in Boston and the first thing that happened there was I came into the room with those two other people sitting there and they thought that, you know, Drupal and design, they've got to be database design. So, me as a designer sitting there talking icons and stuff, they want to talk about how we design the best database. I was like, holy crap, I'm far, far, far from home in this world. But that has changed over the years. But Drupal have always been very good at being a developer-driven design system, as we see here in the very first version of Drupal almost 17 years ago. Those of us who know Drupal 1 can see here some patterns that we all know from later on. Drupal, we have an account, we have the block, block and a box and a calendar and comments and so forth. We also have the very useful Drupal Blue. Blue as a link color is always a good thing. There was actually a theme already at this point and there's actually one thing that you need to see here that is it is modern. So, already at this point, we are using the word modern as a thing that we do. If you go further down here, we see the use of tables, a little bit of spacing as it should be back in the days. It goes up to Drupal 4 as well doing the same thing. And then at some point, we get to Drupal 4.7 and that's when your blue marine comes in. But it still keeps the same like design patterns, you know, use a table because it's data and that's what we're going to do in the same way how we modify and have a lot of lists. It's form fields, it blocks, it's elements, it's always in the table. That goes further down as we come into, a little bit too fast here, into garland as well which came back in Drupal 5 and Drupal 6, which was basically the admin theme. At that point, there was no real difference between having an admin theme or non-admin theme. It was kind of like all swallowed together, which is kind of still is. And then we come up to the era of 7, which is basically from back in 2009 and up until now, which we all know. So what I did here was actually, I took a bunch of screenshots. This is Drupal 7 and this is Drupal 8. As you can see this, though a lot of things happen over these seven years of our admin themes or as the structure here says, you see, loads of change. We really have a new product in Drupal 8. We used, what, seven years of our life to push in Drupal 8. I used four years of my life in the issue trying to get tweaked in and it still looks the same. If you see content types, changed a little bit. We got a drop-down or the drop links and so forth themes as well. It's the same thing. It's pretty much the same theme that we built up. It changed a little bit, but it's kind of like, if you actually go all the way down to it, as I come here, here's my favorite part, by the way, of Drupal permissions, right? Permissions are one of the good things as well that we try to work a lot with. Permissions are actually kind of complicated because there's a lot of data in there. But again, it's a table because everything in Drupal needs to be a table because we're developers, so of course we do a table. The biggest things, biggest change I've seen over these seven years actually came into Drupal 8.3, which is the status page. This is how the status page used to look and now it looks like this. Wait, I mean, I do enjoy a lot. But basically the only things that we changed from Drupal 7 to Drupal 8 is the admin menu. As you can see, they got a little bit of icons changed a little bit. There's more white space. It's a good thing. Taps changed position. It became responsive, at least. So I'm sitting and looking at this and I got a little bit cranky. I saw one treat it out, like now I'm going to bitch and moan about everything that's wrong in Drupal. Actually not. I was just more looking at it from the perspective of how to design trends works because it's kind of design trend when 7 came into Drupal 7, we were all so excited by it and now we're kind of a little bit sad. And there's a reason for that. Anything that's that was new at some point, it's going to go through these phases. So this is kind of like, I was looking at different fashion elements. This is basically me when I was like 19 years old, like Doug Martens, flannel shirt, Metallica, the lightning shirt. I just bought a new one actually two days ago. Yes. That was a good year in 1984. And a chair of jeans. So if you go back to 1992, you have bands looking like that. That was how we were looking at that point. And then I was looking at men's fashion. Did a quick Google search and you have the same thing. So we just have to wait 20 years. And then 7 is going to be like the new hot thing. And I'm not saying that 7 is bad design. That's not what I'm saying. I'm just saying that just as us who is 43 years old, at some point, we're used a lot. We look like we're getting a little bit tired. So at some point, the next decade, it's probably going to be hot again. But I do think it's about time to begin to look into rethinking these things. Because if the difference between 2.8 and 2.7 is basically nothing, why would you then go out and update it? Here we go. Why would you go out and use a ton of money on a thing where it's not really changing anything? Because basically, we're based as a record, as an album. See, I'm that old. I'm talking about records. I've found these two wonderful things. But if you want to go out and sell something, you just need to accept that you get judged by how it looks. And I do think it's a little bit sad that here in our Google world, we've used 6, 7, 8 years of building a new system. And we can talk all the wonders about like configuration management. I can talk days and everybody who knows me knows I can talk days about quick and the wonders of that. But nobody besides us who knows it can see it. Because anybody who's going to come in and use a 2.7 site versus 2.8 site is going to see the same thing. So how are we even going to go to, are you going to go into your boss at your company and be like, hey, so I want to upgrade my site to Drupal 8. Look how awesome it looks. And then you show them the 7th theme, which is the same they had in Google 7. So why would they upgrade when they cannot see that? So it's kind of like 17 years of developer-driven design. Or let me do it like this. So if there's developers in the room, you can actually understand what it does. Because I know when I use colors and do things like this, it goes into panic mode. This is gold. Because in the world of Drupal, code is gold. And designers, it's a pretty thing. But it's an afterthought. It's always an afterthought. It's not like you come into the Drupal one, but like, yeah, I'm a designer and you should listen, hear me roar. It's more like, oh, I'm a designer. And yeah, well, can you walk over in that corner and then paint within the little blocks we have made for you? You can get like red and blue and green and just make it pretty. And it's kind of turning into this mess. So I've been thinking a little bit like, why did we end up in this? How come did we end up in this kind of mess? So if I go back like 11 years, this is my first Drupal con 11 years ago, we're just a bunch of nerds, basically. And we're never thinking about like who the audience were. We just want to build a system, a system where we could publish our websites and be done with it. We never thought about the audience. I mean, and normally when I think about my audience, it's like this dude, you know, who's standing behind me and explaining to me, I can move to the left, I can move to the right, I can move to the little bit, just a niche, just a notch. How big is that notch? I still don't know, but I've moved a lot of websites around that way. And the problem we have with this mess is like, it's undefined, you know, it's jubilant tool. Is it a site? Are we building websites? Are we building a data structure, something, something? Who's the user? Who's actually using the admin interface? Is it you as a developer who's building all these things? Or is it a site editor that puts the data in? And we're trying to put everything in to one big box. And we're trying to force everybody into the same thing, which if you work in any level of design know how hard it is, it's kind of like somebody says, well, I need a new logo that's, that's modern, but timeless. What? I mean, that, that doesn't make sense, right? Like how many, how many designers in here have worked on a modern, but timeless design? There's at least three of you. I am not the only one to share this pain. So I look at Google as this, Google is used to build web things. That's what it does. Actually, a couple of years ago, while I came up with trying to figure out why I did not fit into this Drupal, like, definition of Drupal developer, I came up with this thing that Drupal is built by engineers for developers. That's basically what it is. It's a bunch of fucking nerds hammering around, trying to build something that they think are really, really fucking cool. And then we give it to that end user we don't really know. So what if we made Drupal instead of something that's made by geeks for people? It begins to think that way instead. You don't think of like you as the target audience. You think about that person who's going to use it. Then Drupal turns into become another thing. It's like building this for people, not for ourselves anymore, which I know as a developer makes me fucking scared because they don't, they don't even know how much a notch is. They just want things and I just want to build my stuff over in this corner. But that's not why we built Drupal. We're building Drupal because we wanted to kill the developer, we want to kill the designer, we want to kill all these people so normal people could build websites. That should be the goal. So instead of just moaning about it, how can we fix it? Well, there's different ways of fixing it. There's of course the trash it all. That's been like a good thing. You know, let's go on a complete checklist, murdery, like rip everything out, go as much headless as we can, drop everything we've done and start all over. You know, kind of what, you know, TechSmate did a couple of years ago when they were like 80% done with TechSmate 2 and they skipped all the production because they want to make it perfect. How many here use TechSmate today? Mark Carver is still, yeah, you use it sometimes. It's like, but, you know, five years ago, everybody was using TechSmate even better. You know this logo? Yeah, Netscape, right? Netscape came up with Netscape 6. And I was like, yeah, we're going to rebuild the whole platform. It's going to be this amazing thing. And we're starting this small project over here in the site called Firefox. Fast forward, they were building and building and building and building and building and nobody used it. So my opinion, what we should try to do instead of going like checklist mode, actually look into like how can we fix it? Now fix it in contrib, not try to fix it in core because anybody who's been into any core users, core issues and trying to fix things inside a triple core, knows that that's going to be a never ending discussion where it's going to be really, really hard to get anything done. There's a reason that I'm losing so much here. It's not because I'm getting old. There's a reason that I have gray hair now. It's because of the fucking issue queues and having to discuss everything with everybody. You know, if there's one person in the room with things like, you know what? I don't like that gray. They will then stop the issue for coming in. And then we have to discuss color theory once again. You don't have to have any kind of degree in design or anything else. You can just stop it because you don't feel like it. So if we instead of trying to push all this into triple core, right away, do that in contrib instead, then we can actually get stuff done. That's at least my theory about it. I might be wrong. It happened before that I was wrong once or twice. Anyways, so I was taking a step back and looking at the theme space. What do we do in the themes in Drupal? How does it work? Well, basically your site has three... Oh, thank you. There we go. Basically you have three themes. Say that really fast. I have three themes, three themes. Anyways, we have three themes in every Drupal site. And you're going to be like, nope, I have seven and my front-end theme. That is not true, my friends. You have three different ones. You have the thing you use for your Drupal admin thing. Right now, a bunch of you is probably going to use seven. Then you have your Drupal front-end, which is... God damn it. This clear guy is not working right. Then you have your normal front-end and then you have what I call front-end admin tools. Are you... Jesus Christ, Dave. Epic trolls. We have the heckling roller. If you want to heckle me, you need to sit over down here. So I can actually throw water at you later on. Well, now I'm talking about the front-end tools. Let's call them front-end themes instead. No. So the idea for the front-end admin tools or themes, as you can see, I've not really figured out the names yet. I'm not calling it FAT because that would be fat. And then, you know, somebody might think something, something. That's not the point of it. But the idea is that we have three different themes in your site. So what is front-end admin tools? Well, that is your toolbar. It is there when you are developing your site. It goes over your normal front-end theme. And it's using something from somewhere in Drupal. It's actually using Drupal core elements. That's where it comes from. Right now, that's the same as seven, but that's not the same thing as that. It's the same theme. You can actually overwrite these elements. The same thing with the inline editing. It's the same thing or the contextual links or the outside-end elements. All of these things are different front-end tools. And they are all, like, inhering from different places. This is just how I added in. It's not important. So all of these different front-end admin tools by separating these three different things out, you can then begin to focus on how should my admin experience actually be, how should that look, how should my front-end site look on a normal level, and then how does my tools, when I'm logged in as an editor and have access to these elements, how do they actually interact? Because the whole idea of saying, well, I'm not going to give my end users any reason to use that, that's kind of like saying, well, so you're not going to give your end user inline editing, but all the other systems is giving their users. So I wouldn't use all these elements. We need to rethink that and package it in. So with those different kind of conceptual thinking, I started out by saying, well, I did one admin theme like last year, and I said, okay, how can we change this? So how can we fix this issue? So I came up with this theme called 11, a theme that's not designed for developers, but actually designed for more of the normal user. So it's actually with the idea of trying to make stuff pretty and kill the tables. And that's the funniest story from yesterday, when I demoed this the first time for anybody outside of pretty much my own apartment, because building layouts, building design ideas, building concepts out is really, really hard if you only show snippets out to people, and it can be really hard. Designers get kind of sensible about their designs. So, but when I showed this off the first time, the first comment I got from one of the developers was like, but what if I want the table? I was just like, yes, exactly. But I have a solution for that, so no worries about that. So this is the very first public showing of my admin theme 11. The idea here is that instead of having a table of data, you have a bunch of cards. Instead of, so as you move around your site, it's going to be separate elements, having an icon on them, having colors on them, having this concept of ideas. This used to be tables. It is not anymore. It's completely rewritten. Same thing when you go into your content types. Why is a content type put in a table? If you browse around that, that doesn't look pretty. Should we actually have all the links visible from the get go as well? Same thing when you come in to manage fields. All these fields are now just elements in a table which makes things feel and look very, very technical. If you put them into a card instead, which is basically a card means it's a box that has a specific image and a title and some body text. If we try to think it this way instead, then suddenly you get away from the table look, you get away from the technical interface and try to make it more human. And of course, me and my love for iconography makes it really, really fun to add in these little icons and find them. That takes only forever and ever. The same thing as when you go up and actually say, well, every element that you have in this Drupal system, why is it all text? Why don't we have little icons on them, make them pretty? Why are we always limiting ourselves to these like, well, what can we kind of agree upon? What is the lowest level we can agree upon? Why don't we try to push these things around? And the same thing, so the displays and everything else tries to rethink them. Even how views is listed out. Why is views listed out as a table again? It's an element that we built. And just to show you, actually this is actually working. I'm not doing a live demo because doing live demos means that my machine will crash instantly and I will burn down. So this is views and how the page of views actually looks. And you can see it still works. It's just changing a little bit of the markup, changing a little bit of the CSS, changing quite a lot of JavaScript elements around to figure out where stuff comes from. Views UI is the biggest beast I have ever tried to wrestle with and the amount of times I lost, and I was like, no, fuck it, I'm not going to do this. And I begin to use the argument to say, well, you know, an end user is not going to use views because why would he? And then I begin to think about, I've been trying to use having normal people inside of my apartment, not nerds. So having my girlfriend and her daughter there and my daughter as well trying to talk like web designer with them and you know what? They don't care about Drupal at all. Not one bit. So when I begin to explain all these technical difficulties like how it's good, I'm like, well, it's not pretty. Is it easy to use? Does it look good? Can I use this from my phone? And I'm sitting there with my laptop and trying to explain the epicness of how I made an icon move around on the screen and all these things that normal users don't care about. They don't care about if it's Drupal or not. They care about if it works. They care if it looks good. They care if it feels good. And we are running around in this conflict like high-fiving each other over how epic Drupal is. But as soon as you go out of this room, they don't care at all, not one bit. So, I mean, the idea of if an end user, like let's say somebody who's never worked with Drupal, never worked with anything of these, actually they begin to play around in the admin interface and we're then going to say to them, well, no, you're not allowed to go and play with views because that's too big, too dangerous for you. Like, no, come on, we need to rethink and rebuild these elements all the time. Which also means that even views needs to think in, how can we make views prettier? How can we make these different elements work better? And this is very raw and it kind of works. But the idea is to begin to look at this as how would a non-technical person work with this stuff? How could we make it easier for them to work with it? Instead of us always going and finding an excuse why we would not let them work with it? Or you should not work with views because that's way too advanced for you. We should not let them give them access to the user access because that's way too advanced for them. Well, what if they just download a Drupal and build their website on it and really don't care about what we feel that they should use it for? I mean, is it in my role as anybody to say somebody should not use Drupal in a certain way? I thought Drupal was built for people to build websites, not for us as nerds to be like, no, you should not use this or that. No, I did leave one table in this system still and that's the content table, which is still because I'm so much caught up in the idea of data being a table. Why is the preview of all the content here a list of data? I mean, with the content type on, who cares besides of developers of what content type and element is? Why don't we have this shown in ways that would make sense instead, make it like preview of the data instead? Anyways, same thing with files and maybe there'll be an idea to actually have previews here and so forth, all of these ideas. So you can see, I've only scratched the surface here of how to rethink it. If we begin to rethink how we're building this and thinking this is a non-technical user coming in and wanting to administrate the Drupal site, you can see how many things that we're stopping them using it. They would become scared. I went, of course, a little bit further because when I was done with this, I was like, hey, let's figure out how could the themes look? What if themes actually look in a different way? Why is themes just this long, long list of data? Why are we putting so much stuff out there? Why don't we have like little, again, little nice icons or, you know, a little hard when you set something as default? These like little things, it's things that makes people happy. And yes, I know that maybe Blue Marine sneaked in there. There's another reason for that. Anyways, later on. The same thing, now we come into the place which I know is going to make people freak out, you know. The modules page, the way we install a module today, or no, we don't install it, we enable and disable or whatever it's called, I don't know. Anyways, so here's the modules page. And what I began to play around was like, why don't each module have an icon? Have a visual element that tells me this is action, this is the band module, this is big pipe, this has an identity, there's a graphical identity and each element have that. Wouldn't that be way cooler? Wouldn't that be epic if it did that? Same thing here, like when an element is not, if I'm not able to show, why do we put all this data out? Why don't we try and like put it into little cards, make it human and nice to look at? I mean, it's back to like Apple's design thinking where they went like, well, you know, everything have to be hoggable. Why isn't it like that? Why do we have like, install and we have a link? We can't even click anymore because of the form items. It doesn't make sense. So, as you can see here, my machine, this machine is getting very, very, very old, by the way, and it's getting a little bit tired of doing development and it's not so good, but still, it's coming there, hurry. Anyway, so by beginning to think these things instead of being dragged up in our concept and our idea of like, everything is data tables and we're developers and we're just building for developers, I'm beginning to look at all of these interfaces as things I should play with and I should design and I should put colors on, I should put identity on because when I do that, I make it to a thing that's not a technical element. It's a tool that we use to build websites and that experience should be just as good as the website you're building. It shouldn't be hidden away. Another thing I'm beginning to play around with like, your configurations, again, why is this tables? It should not be tables, like, what if, what if every part of a configuration had its own little icon, own little element had, maybe even had its own color that was always symbolized with so when you're navigating through the site and yes, I know that, well, what if your color line and what if, what if, what if, all these, what ifs, but what if we try to stop ourselves constantly from wanting to rebuild things because we are afraid we're doing something wrong and just be like, hey, why don't we just do this stuff? I mean, as well as the permission page. So when I did this, this is the permission pages. Let me just show you how it actually looks now. I thought about permissions as a pain in the ass today to look at what if we begin to rethink this and I put a screenshot out of this on Twitter about two, three months ago and the first feedback I got was like, no. And I'm like, why, what are you saying no to? Well, I don't like that because I'm a developer and I need all my data to come fast and be this, this and that, but it's not for you. It's for those people who's not doing development, there's those who's not writing the secret choirs for those people who just want to build it. What if we begin to rethink these interfaces in different ways? What if these buttons you can click down here actually show the status of what's going on instead? Which, by the way, I also sent out a tweet with a screen of that which had a little locked icon on the person on and people went apeshit because I like checkboxes. Well, that's all good, but let's just not stop ourselves just because somebody says no. Let's try to like build these things around. And a lot of this is like CSS details so it's like one of the elements I'm trying to build up around here. Oh, you have like tons of little elements that actually would make sense. Oops, let's see what's this demo about. There we go. Yeah, so as you can see up, if you look at the little elements over here, it's like trying to like do a little bit of very small animations, trying to play around with that, trying to figure out how could we, how can I maybe actually elevate what we could do right now just with CSS? What if we like try to do these things? I know that's not gonna not work on somebody's browser or Boohoo. Well, actually, this theme was not working with any icons on Firefox up until last Thursday when they finally got SVG masks in. And I was actually about like, shit, I need to rewrite every goddamn page here to actually support Firefox. And then I was like, you know what? Nope, Firefox, I'm just gonna wait until you're gonna catch up because this is my little project, right? So I can do whatever I want. I can go like browser requirements. My browser requirements, you're gonna use the latest KGS browser you can find. I'm sorry for that. I'm gonna use CSS variables because I don't wanna mess around with SAS. Did he say that? Yes, I don't wanna mess around with SAS. I love CSS variables. And I know there's reasons to use SAS. I know all these things, but this project is just about getting stuff done. Same thing when it begins to like play around with mobile. What I actually would love to do now is see if this actually works. Yes, what I would love to do was actually maybe change the position of where our menu is. Why is it, I mean, when you use your phone, right, you have your phone up in your hand like this. And normally I then have something else in my hand because that's how it is. Why am I then, I'm navigating with my thumb. Why is my menu all the way up there? Why is it up in the top? Well, because that's how we used to do it. What if we placed it in the bottom? I know that again, putting that stuff out on Twitter, well, it doesn't work in this browser or that browser, whatever it is, like, well, you know, it's not like we're saying that this should go into a Google corn. Everybody have to do it, but let's try to rethink these things. Let's use this as a base to try to rebuild these things up. And just to show you actually that my front-end admin tools or themes, I need help with naming these things, right? As you can see, I'm not the best thing at my, I need some people to do work in marketing with me. But to show you that actually works, you know, you have, you know, this is like custom themes built on top of Bartik. Same thing here with like the outside-end editing. And, you know, editing up here as well. There's another design principle I began to work with. It was like, how can we always use blue? What if we used another color, like pink, screaming pink for everything that says an action? What if we tried to think these ways? And say, what if we didn't have an admin theme that was actually blue? I know that's like, I was trying to design something that was not blue and I could not get my mind around it. So I ended up just be like, fuck it, first version, just gonna be blue. At some point it's gonna change. At some point, someday I will also grow out of blue, but there might gonna be people who don't wanna have a blue theme. They might wanna have a green theme because their company colors are green, or what it could be. Like there's a million different ways of thinking these things. And one of the principles I came back with was like, well, basically if you look at it as a data data, it's always gonna be a table, but then if I look at it as a card instead, it gives me other options. I know that designers and developers are looking at things very differently, but this is not built for developers. It's built for designers. It's built for a concept of where we could start. It's built on all these different ideas around how a card could look. What if the way we're managing a field was not even like with big ass buttons, but with small little buttons, just with icons that we would then recognize? And I know that some people will then not be able to use it, but what about all the other people who wanted to use it? We're trying constantly stopping ourselves from thinking around these boxes. Icons and colors. So the way I built around this 11th theme was basically saying, well, let me start by defining also a color plate. Not saying this should do everything, just a simple color plate. So I have my different colors based on asphalt and concrete and gravel, and I have a blue sky because you need blue because we're in Drupal world, right? I have raspberry and I have like grass and strawberries and pumpkin colors and even yellow snow as a color, which again is just my dumb sense of humor, which suddenly came in and now is written in every CSS variable in this whole system. I'm like, God damn it, Morten. You're like, why are you doing this? Why are you calling it yellow snow? But then again, it makes you laugh and made me laugh every time I have to use yellow. I'm like, don't eat that yellow snow. But doing these things and finding a design language that we want to design with, the same thing here around type. So typography, I'm always messing around with typography. If it's an admin theme, let's then use whatever it's built in. Let's make it closer to the element or make it look like maybe an app someday when progressive web apps comes for reals. Then we can just take our stuff imported directly. That's, I mean, at least I didn't want to use six months to figure out what kind of funds. I just want to use the funds that already built into my system. Also, I don't have to download that on the CSS. It's pretty easy for that. And if your developer goes completely into panic mode, here's the good thing. You can still just install Blue Marine, go back to the good old day of 4.7, and nobody in the world is going to mess with you. It's not like the mortening precision of design is going to show up and knock on your door and be like, you need to use the 11 theme. No, you can actually just use Blue Marine because, I mean, I don't really care. The only thing I was sad about when I installed Blue Marine was I didn't get the gray color I used to hate with such a passion back in 4.7. So that was like a really quick presentation of this. I'm trying to run it through fast because I know that you guys like tired from all day. I do, it's the last thing, and then we can do some questions and stuff. I can show you more of some of the files. I do want to thank out FISA Disical and Adnovation who picked me up about three, four months ago and actually have just been like funding my work here. Actually, Dave Hall made sure that that happened doing normal ranting but having at least one company to back me up in this work makes it possible for me hopefully to do this stuff. But I do really want to have some help for it. So if you want to play around with this theme and I do need to warn you all that as yesterday when I presented it the first time and one developer took it down and he installed it, his first comment about the error message looks really pretty. And it is really pretty because I found two different colors of raspberry I'm using for the errors. So I mean, at least the idea of make it pretty, there's going to be a ton of bugs in this. Of course there is because I'm just hammering on stuff trying to figure it out. And it's even worse, it's on GitHub. I have not even put it over on D.o yet because I don't like to do patches. I really like to just work with this stuff. I don't want to go into technical levels. So and then of course there's the usual question I get on this is why did you call it 11? And there's a simple reason for that. Let's see if I can make this work. Why is it? Nose. This is the oldest joke in any metal environment. I'm an old school heavy metal fan. So basically he made this new amp and it goes to 11. And he gets this question about why does it go to 11? Why doesn't it just go to 10? Why don't you just make 10 higher, more loud? But it goes to 11. But why? Or it's one more. And that's the whole concept here. It's one more just trying to figure how we can do that. So here's a few links. 11 theme is the hashtag. I'm going to use for it. If you want to play around with the GitHub theme machine or the me machine slash 11. GitHub theme machine 11 style guide.viggy is where I'm putting down the style guide. I would love to get feedback and having especially designers coming in to help out. The technical implementations can be done a thousand ways. The whole front end admin themes, maybe we should put that into a module. I don't know yet. I'm just trying to see what kind of boundaries I can push. If you have questions like what kind of icon sets I'm going to use, well at this point it's going to be fund awesome. Because fund awesome is it's GPL 3.0. We can release it on D.do. People can use it and so forth. So with that, and I only spoke for 35 minutes. So there's actually room for questions. With that I will actually give you the chance to either come with some questions or you can go out and get a piece of this sunny, sunny lovely weather we have here in Baltimore. I'm so happy for the swimming pool. I made sure that my girlfriend could swim in each day. It's been wonderful to see the rain from our hotel windows. It's good to nerd out. So if there's any questions you can use the mic there. Or I can like show off a little bit more of the other design principles I've built in. If you want to see that. How much I paid for the icons. Well so fund awesome just released a new version or it's about to release a new version and I paid a fuck ton of money for that. Which I put in so it can actually get developed. Besides of that it's free because it's GPL 3.0. So that's good. So if there's no question I would like to show off a little bit of the design concepts if all people want to run out. So there's I have a sketch file here which have all the things in. And if I could like get my screen to me what is place when it's good when it's done. When do you think it's going to be done. Yeah it's going to be done when it's done. Well no I hope to have a stable version now within a couple of months. I know the guys at Pfizer really want to use it fast quick. So I need to like really push up the speed a little bit on this. So I do one of the one of the funnier things that I begin to work around with in this whole 11th thing was the concept of sizing. Funny enough it's called 11 and it's built for Jubilee but I'm actually building everything around the idea of stuff is being an M. One M which is 16 pixels so you can have something that's like half an M which is like eight pixels and so forth. So everything is going to be divided up in that. But the good thing about that is it makes it really really easy when we begin to like wanted to design elements and how should they how should stuff. Let me just see here. This is where we can see that. So by saying that everything has this size of one size is 16 pixels or eight pixels and we stop talking in pixels and talking this one or half or one and a half or two and a half or three or four and five also makes everything actually aligned correctly. Same thing with all the typography as well it's going to be 16 pixels or 24 pixels or 32 pixels but it all goes back to being one M or actually one Rem because I'd like to more use Rem instead of M because then I don't get confused. Anyways I'm not that clever. I'm pretty but I'm not clever. Jesus. Anyways so as you can see everything is always thought and this idea of being like this is like all checkbox is going to be one and a half instead of one because I want to have them big I want to have big checkboxes. The same thing if you go and let's say you know the labels for checkbox is the same concept. Everything here is divided up by 16 in some way. So that just makes it easy for us to figure out where do you want to put stuff? Where do you want to place that? So that's how that works out. Let's see if there's more fancy stuff I can show. Different, same thing with different concepts of how do we actually want to install elements? What if it had these kinds of icons in instead of having links? Been to rethink replay with these things figuring out how to make it more doable how to make it better because there's one thing I've learned over these years like it's only us developers also who's using these laptops so we need to rethink these elements in so many ways and maybe we're actually getting obsolete with our laptops even worse so stuff needs to be bigger because it needs to go into our phones and so forth. Let me see what else I do have here. Start, simple, space structure, admin layers. Yeah so basically these are the key concepts of the system the same thing here if you look at my menu here like if you have anything this is just like conceptual ideas if you have anything that requires an action like this is what we want to focus on well then it's going to use my strong signal color which is my screaming pink here or trying to break away from these standard elements. Same thing like everything needs to basically have some level of an icon on it because if it has an icon if it's not only the words on it by adding it into the icons it takes a ton of time I know but that do make the system way more appealing to look at and that's basically concept of this make Drupal pretty. First concept was like change everything and rebuild everything but at the end of the day it's like how do I make it pretty because I'm not expecting able to from the theme perspective to rebuild everything I'm expecting to at least make it prettier and make this a stepping stone. So if anybody want to come and help out you know I would love to hear about it I have a bunch of cards up here for my little shop you can ping me and talk with me about this. The way this is going to be built because it's out in contrip it's basically going to be like hey I have some ideas some concepts I want to build you have seen some of them if you like it fine if you really really hate them you know you can always go on let's see if I can find that slide you can go up and get up and just clone it and build whatever you want with it and that's the idea like start to build these things but not build them in the idea of like want to change everything in Drupal I just want to build an admin design an admin theme that makes me happy when I use Drupal and that's the plan of it so with those words and if there's no no questions at all yes just go up take the mic yeah I know I'm hey I'm standing up here sweating so and mainly so we can hear it on the recordings afterwards so is there any chance that something like this can be ported over to the front end so if you have a site that the regular users are going to log in and start using the back end elements that they'd also have a front end to match it well hopefully this theme is going to be so amazing that you want to use it on your front end that's actually one of my I know it sounds like arrogant that's hey I have a company called the me machine right but the the idea is yeah I have to embrace it because if I don't embrace it you guys are going to mark me for years no but the idea is to make admin themes that are so visual appealing that I mean we're using the admin theme more than we're using the front end theme and it should I mean I would hope that we could like completely remove that barrier so our site would become that pretty actually that we didn't even have an admin theme which is like beautiful all the way but that's really really hard and complicated so is this a Drupal 8 theme just because you started it now and Drupal 8 is out or are you actually using things about Drupal 8 that are different from Drupal 7 so about almost a year ago when we were done doing got Drupal 8 out and I was sitting and looking at the last Drupal 7 site I did I decided never again to touch Drupal 7 because it doesn't have trick inside of it and that I used a lot of my life on it was simply a personal choice to never again work in Drupal 7 because I got I got frustrated, angry and hateful and instead of being joyful and smiling as I'm usually or kind of is so right now it's only Drupal 7 Drupal 8 I could totally see if somebody take all the design principles and begin to port them back I can totally see that happen which would make a lot of sense which I would love if somebody want to build that come and join the fight or the party I would hate personally ever to do anything in Drupal 7 again I've said no to a whole bunch of projects because I don't want to work in Drupal 7 and I hate Drupal 7 with a passion and it does not make me happy and I really want to move forward the same thing here is like the way I'm building this is very much cutting it browsers because as I figured out with like icons that was not supported by Firefox well Firefox is going to catch up and that might going to be a little bit dangerous but this is not built for Drupal Core it's built out in contrib we can always fix those those are technical issues this project is not about checklist it's about fixing design issues first and then fixing it technically so there might not be a bunch of things that I have no idea how to fix and that's why I need other designers to play with me and I need other developers to hopefully fix all the things I don't know anything about because no I might it's why we have a community for it any more questions should I actually let you all go well then thank you for not heckling me too much and thank you for attending and I hope that you all gonna jump in and give me feedback on this play around with it download it I'm sorry if you're gonna break your side it probably will because it's highly experimental but this is a thing I'm gonna be keep on pushing at least for the next six to eight months thank you to Pfizer for doing that and thank you guys for showing up