 Hello and welcome to the next presentation and learnings from our launch triple eight core customer projects and My name is Michael or people call me schnitzel and I'm Had technology at the major labs. We are a company in Austin and Zurich and I'm Had technology and was one of the co-founders and I'm usually the guy that yells at you at group pictures that you all should wave at me So I can take a picture of you and which also happened this morning So by the way, you all looked really great and it's on flicker already. So you can see the picture But not about group pictures about Drupal 8 living on the edge So our journey or why we even did that? So the first site we launched was our own which was pretty obviously easiest and it was already a year ago so in April 2014 we launched amazing labs in Drupal 8 Alva at that time and It had two languages. It was a completely redesigned. So we did not only take our old design and did it on Drupal 8 We also redesigned it completely And it was a pretty interesting journey because we did it in like in six weeks and so there was a lot of Working on it figuring out fixing box on the go But what was really good is because it was our own site We could live with the box we could work around with the box And we we also decided that like some features we didn't put in and But it was we learned a lot of that and actually out of that came more business out of that So we were asked to help with Drupal.com which is a site owned by Dries and When it's more like the business side of Drupal org so we have case studies up there and we have a lot of different information of For business as for them to find about Drupal. What is it? Why should I use it and stuff? so because we like to live on the edge it's done in Drupal 8 and We're actively working on it. That was like in September 2014 and At that point you already had a beta which was a bit easier and It only has one language right now, but we definitely want to add there are a lot of language spoken in the world So we want to do that The next one was another client project It's for the Schweizerische Gemeinnützige Gesellschaft and it was done in January 2015 when The longest name ever the Schweizerische Gemein so it's a it's like the Swiss Society of like a mine Whatever, so it's like a Country to tell you what it is in English whatever and Yeah, yes, so And That wasn't done in January 2015 and they came to us and said like we have already a Drupal 6 site They had at that point and we said we want to do it new and when you look at the functionality That the site had and was basically a brochure site So it's like well who we are what do we do and three news entries done? so we said okay, let's try it and It actually has four languages. You only can see two right now what we are installing more and that was really great And and yeah, basically starting from that We just felt so we feel so comfortable if to play it so like every new site That is like super tiny like this one we launched two days ago, which is our group the Macy group site It has two content types and three nodes and because it's a one-pager site, but it's just you can already use it It works perfectly. It's super great. So yeah, so we launched that and it's just right now It's our tool whenever you we need like a brochure site a small site. We already do it in triple eight and and yeah We do more so and We have right now like three sites in development that we do About it and I want to tell you about what we learned of a different environments of different areas and To do it short and so yes, it works and it's actually pretty great It's really surprisingly great what you can do Sometimes you have to be a bit creative and we will see them later because as most of you probably know There is not a lot of contrary right now But the best is nobody wants to go back to Drupal 7 Need a site builders need a front and need a back and neither I want to go back And we still have to because we still we usually build sites That are really big so and there is only way to do that in Drupal 7 right now But yeah, so everybody's excited and I think that's great. That's we're looking ahead to a really interesting feature So let's look at the different Type of users of Drupal how they reacted and the first of all are the editors I mean we build sites we implement them with I build them But at the end it's the editors that have to use it if they don't like it We won't have any success with Drupal 8 and the best is we didn't even tell them and In the beginning we didn't tell them if my slides now update No Doesn't want to update. Okay. Yes, so yes We didn't tell the editors that we actually use Drupal 8 they knew Drupal 6 The SGG website and we just told them like there is a new Drupal and we didn't I didn't tell them it's about beta and stuff we just told them go there and edit and They didn't realize it that there is something new that there's a better because it's already so stable from an editor point of view That you can use it, but they really liked it. They liked for example, they really liked the new layout That like the publish stuff is on the right side and actually they have some other Drupal 7 sites So they asked us like can we also have that like we really like that that we now see the publish on the right side and like all the access Like the new buttons and all that stuff that we did a lot about usability. It's it's super great And so we like at the end had to explain them We are you know like it's that new Drupal 8 thingy and better because they wanted to have all their undersides They're really big also migrated to that new thing and so you explain them at the end that it's not ready yet Whatever and we can do it for the brochure side, but not for all the other sites Of course, there are some themes that allow you in Drupal 7 already used a new layout and we use that at the end and but It's yeah, it's we just gave it to them and we asked them how it is and they don't want to go back to Drupal 7 as well So that's cool Let's talk about Multilingual a really important part for us in Switzerland. We have four official languages where English is none of them so actually it's five and and Any website we do is has at least two languages. So multilingual is a really important part for us and We worked ourselves on it. I did a lot of things, but Everything and I say really every single string that you see is translatable out of core without Installing any additional contrip modules Anybody that has installed or that's done full translated the website. I mean really every single String translated on the Drupal 7 site ends up in installing around 27 modules and Which sometimes with patches and stuff so a lot of fun and So it's really like you install Drupal You have four modules you install them and everything is automatically out of the box Translatable and that was one of the big reasons why we do it right now because it just works like without multilingual capabilities We wouldn't use Drupal 8 right now, and I think that's a really big step forward That will also make a meet easier for all of you to start using Drupal 8 if you have multilingual website because it's no longer a Worry-ness, so I don't know if I can install that or if I can use that it's already there It's supported by core. So that's cool Of course, there are some issues and two of them that I'm really interested right now So the problem is that if you use browser negotiation, so that Drupal gives you back the language based on your browser language if you having that installed your whole cache will not be running Which is a bit bad So especially if it's 27 languages which we have on some sites, so I'm working on that right now to Find a way to redirect to the right path prefix which then can be cash So there's some things and there's a really really old issue that is now Reloaded basically it's that entity like translations and innovations. It was a really Bad issue in the past with Drupal 7 already with content installation with entity translation It actually got a slightly bit worse So there are some people working actively right now to make anti translation Which is the default translation method in Drupal 8 now work together with revisions because right now whenever you have revisions installed and you translate one Single translation of a node it will copy all the translations for all the revisions So you not only end up in having a huge list of revisions if you revert back You cannot revert only by language. So if I revert back to the German version Like the English changes in there that I maybe didn't want to revert or also reverted so We have right now not enabled revisions at all on any of our sites And if you use if you want to use that right now Be careful the fun part is actually it's also broken in entity translation with Drupal 7 and revisions So if you do that already these days you probably know about these issues So it's the same with 8 but they're actively working on it and with a lot of different ways And we really hope we're gonna get that in and because without that it's just We're just at 80% of the whole translation with revisions with states with workflows and all that stuff but overall Multilingual works really great and it's and it's a pleasure to work with it And and to definitely see or to definitely earn the fruits that we put the seeds in in like three years ago when we start Or like even longer when we did the whole multilingual stuff Let's go about site building and site building in Drupal 8 gives you this really comfy cozy feeling that it feels everything right and complete In Drupal 7 we have like content types and we have entities Taxonomies and we have users that have fields and that's great if I need a new field for a user I just added but if I need a field for a menu link like I there is there is an entity But there is not so I have to like install another module, which is called menu attribution so I can in check the picture to a menu or If you want to do other like you want to add a field to a blog How crazy is that like who needs a field on a blog in Drupal 7? That's also possible now in 8 as everything is an entity you just do it You just add a field to the menu link you just add a field to a blog and it just feels that Greatness of like I can now have a system that every single pieces match together Like I use a lot of then actually of you of saying Drupal is a bag of Lego bricks to my clients And in 7 it feels like they don't match together all the time in 8 now They all match together the meaning that you can build crazy houses in Drupal 8 now And you can probably go somewhere that you never can go back But I think that's not the system has to prevent that like the system should be able to do that and it's just It's so much easier to do things and like if if somebody wants understands the field system That has never done site building before you just have to explain the differences between terms and contents and users and done That's it. He can use it and that's really great One thing though that we saw in daily working you have now block instances So in Drupal 7 you place a block and it's placed There's a module that is called block clone that you can place a block a second time a second time in 8 you have block instances Which you can place a block multiple times from people that coming from 7 to 8 That's really confusing especially if you combine it with the custom block library So you create your custom block library, which is like your content type You create a block out of that with your content and then you have to place it So it's like three steps after that and for people that started using that it's really Confusing because there are a lot of steps of like in the past you just added your block and you placed it done Now you cannot do that because you have a really great system behind But it's a bit confusing So if you're gonna start using blocks and really start using them and start using custom block libraries But It's just like placing them is sometimes a bit confusing and stuff So maybe give it a time to figure out and First play around and then on like I don't know simply test me start the site and play around with it and and learn how how it works and Of course, there is a lot of controversy like when I look at the sites in Drupal 7 We have at least 50 60 modules installed by contrip one of the reason is like multilingual So I have he thought 27 modules anyway installed But there's just a lot of other things and and one of problem that we had for like the SGT website They wanted to have the news on the home on the home page or on the front page But I will see not ordered by the created date. I mean why not? I mean I want to have the older news should be on top because it's more important than the newest news I mean, yeah, all the requirements of websites and we have to fix them So sometimes you have to be really creative and in Drupal 7. I would have said hey There is no queue you put no queue in and then you can order it Well, you go to Drupal.org and you see the node queue module and there's no Drupal 8 So you think about okay should I now pay my developers to port it which obviously would be great Actually, there's a better way. You just create a new block You put entity references in and you're done. That's your note queue. You have now a block that only has entity references The editors can go and edit that block and add entity references. They can order them Really easy and you just put place the block on the home page and don't if you need views because you need to do Additional things you can do that because a block is an entity views can work with entities entity references It's a relations and everything so it's the the piece of Using the different blocks putting them together and you don't need a country module and that happens to us a lot So there's a lot of things that we say there's a module for that But not in Drupal 8 so we cannot do it and then you start to dig deeper and think about it and learn and you realize I don't even need a country module anymore Because I can build it with what Drupal ships me already if I use it in the right way or if I use it in a Creative way So that's really cool. Of course that system doesn't fix everything that note queue does No, you can like do even more But there is maybe a single module that just lets you shuffle the sorting or that let's you automatically Inject when you create an entity you can say inject that into that entity reference block or something But there's just tiny modules that can also be used for other things and I think that will be interesting to see how The note queue module as an example if that will change Maybe the note queue module will actually not be any code. It will just be shaped configuration So that even you install it it adds you a code a block that has entity references And so I think that's will be some changes how we probably make country modules because as a community we still want to Have something like note queue on Drupal.org We cannot expect from everybody to an understand the entity system well enough to build something themselves So we want to ship something like that But probably it's not going to be code It's just going to be some configuration that we ship that is installed and then you have your new note queue block that completely uses core one other thing and we are just really having that is SEO and So we have actually a sister company that only does SEO and it's a bit of sad part. So there's nothing in Drupal 8 Right now that supports like any SEO So like our system company they do like on-site reviews when we do a new website and we get the lowest rating from them because there's like there's not a lot in there and Like there are no redirects of like and there's a lot of country modules in seven that provide you that I just think as a CMS These days when we ship something we should have at least a minimum amount of SEO The technical SEO that is shipped automatically. So if somebody just uses Drupal 8. He has at least a Average SEO rating and not a completely bad and that we expect him to download new modules because Yeah, we see SEO is getting more important every day and so we should provide it And I'm I don't have a list of all the things that are broken right now because we do a lot of them In code and custom stuff, but I think that would be maybe interesting to get some people That are interested in SEO to like propose like a standard Drupal 8 SEO thing to work in that But yes overall Drupal it's Drupal 7 site builders pick it up in two hours like I just had last week somebody that has never worked in Drupal 8 before and I gave her the specifications that we need and She went in and she created the content types created the views created the blocks There's maybe some things that you have to learn about the new ways But it's like two hours of like reading and throwing around and playing and destroying and trying That's it like you don't need more because the UI is still the same The ways you do stuff is still the same. It just feels more it feels complete and everybody that I've seen Using it tells me it's so much better and I hear that from inside of us But also from other companies that tried it out. So I think that's really cool that we kept all the systems of seven and didn't change and From a UI from a site building point a few house stuff works Which leads us into the configuration management and Configuration management is basically the thing we have all waited for and it's like the most. It's like the most exciting thing because Especially the bigger the sites get the harder it is to handle features and all these things and features was never intended to do that So it's super exciting and everybody likes to use it The problem is and that's what I feel but I also hear it from others We don't provide any help to use it right now There is no UI. There is a UI, but it doesn't tell you how to use it There is no there is some documentation on Drupal org But it's it's more like how it technically works, but it's not like how should I use that system now? And I think we have built one of the best configuration management systems that everybody else is Super jealous about like I talked to people from Adobe and they said like We throw like endless amount of developer hours and they they're not able to do that and What we have right now, but I think we have to make sure that of all the people we made everybody super excited That when they the first time use it they don't get sad and don't use it so One problem is for example, there is no real workflow for death staging production. It supports it There are sessions here. I just was at one, but there's no real documentation about it Then we have a staging folder That is not the staging environment of your site. It's like the import export So it's super interesting then we have an active folder, which is empty Okay, it comes from a history. I know that but I think we have to fix these things like we have to Remove the stuff that is just like because I saw people that first time use triple 8 and they call me and say like I have an Active configuration folder and it's empty. What did I do wrong and they and they don't know they cannot figure out and I tell Me yeah, you know look that is the history that like there was in the past There was an active conflict folder and there was and it's now not used anymore It's on the database and like if you use conflict devil module it will be used and they say like well Are you crazy like so? Yes and There's also no way because in Everywhere you read we say now we can prevent or we can now have workflows where we don't do any changes on life The problem is core doesn't allow us to prevent changes on life There is a module that can do that, but it's not shipped with core automatically. So I think that's things that we should think about of okay, maybe we should Provide them or at least like create a list of Of CMI things or configuration management There's another problem Like if you need to merge CMI changes and we see that every day happening that you cannot merge CMI changes inside of triple Because CMI is like it's the law all the time. So if you have Like a field that is not in CMI and you synchronize it It will be deleted in your active directory in your active configuration It's not how features used to work that it's not just like the additional stuff. It's actually removed It will show you but it's a bit strange. So like the whole Merching needs to happen in git And or there is thrush config merge that helps you doing that But it's just again it's something we have to teach and I had multiple times where my developers because of just not knowing they Take their configuration Put it on deaf and import it and remove just something that another deaf just did Because they didn't know how to use it specifically. So there's a lot of things missing so overall It's really frustrating to work with system that everybody is super happy about and we don't really provide any information. Yes Yes, so the rush merge and rush config merge you can point it to another site and it will take the configuration down merge it with yours and Export it again and create a git commit if you want that and then it pushes it again. So there are some things Yes, so it's a bit really frustrating and sometimes but I mean we wouldn't be the triple community if you could fix that and So I think we should we should fix it and we should do that. So there is one old a git issue I'm serious. Sorry the two Alex part and Jess just hate me But um, yes, so there is I didn't want to create a new one actually but so there's an old Groupal issue that describes basically what I just said and that we should document the git config workflow Of how should we do things? It doesn't have to be that has to be the way But I think we could find a workflow that works in 95 percent of all use cases And if you just follow that You will be happy because right now we don't do anything and people are not happy The other thing and I just did it and so I think we should rename the staging folder with everybody I talked to they think the staging folder is an environment. So they think if I put it in there It will end up in my staging environment and it's not the case The staging folder is actually the import export folder and we can call it sync We can call it import whatever and I know it's what's it's we are close to RC, but and We'll have to talk about it and then the next thing is that I don't think we should have an active directory Like if we ship with an active directory that is empty don't create one There is ways in Drupal that like if you install config devil that we tell the users Hey, you should create like go into your settings PHP and create a folder that we can actually do our things But shipping with something that we never use I think that's not how Drupal 8 works Okay So much about CMI renting It's great. It's great like we you you develop your side You make a whole config export you go on your dev side and you import in everything is there then you realize? Oh, yes. Oh, yeah, I changed that text format I changed the order which something I would definitely have forgotten about when I used features So it's super great, but in the daily use Things just fail a bit. I mean, but it's better. I mean, yeah, we can tell your clients. It's better software, so Let's go to the back end and and It's all pay all the way So it's everything about the object oriented. I have to say we so much like it. It's so much better And I think it's a lot of people told me that they learned maybe objective oriented in school once But now in Drupal 8 when you look at it, it makes the first-time sense Like that whole examples that you learned about like, yeah A dog is of type to do them and the dog has an ad method parking and stuff And you're like, okay, thank you But now show me code like I want to see in real life go to Drupal 8 and it's there and you Realize why do we need interfaces? We realize why do we need? All the object oriented stuff and and it's it's just really cool and But it doesn't stop there We have an entity API that that you can really use no language on the line none anymore that people don't know what it is About but everybody tells me I have to do it. So I do it, but I don't know why and We have plugins and which are really great. It's just like a Block is now a file and it's all in there like if you need a block You just create a file you declare it whatever you need it and it's done and they're like each single block is a single file and You have services so I can hack call without hacking core if I don't like something I just change it with my country modules and I replace it without touching anything. So it's super great I think it's from a From from a way of like changing and using core It's much more like a framework now than it used to be in triple seven. I think that's super great And of course it's concerning as well and for people that don't really know about about objective oriented programming And what I've seen for my site builders that generally don't have a lot of programming knowledge They pick it up. They look at example code. They look at other code And they maybe don't exactly know what the namespace is in PHP But if if you just use existing code and they will use it and another thing is You really have to use an idea now Without support by your editor that can tell you that the class is already client defined somewhere else Or you forgot the namespace or whatever You just end up in a lot of times go to the Drupal to the actual browser window refresh and it will show you an error That has nothing to do with PHP like Writing code wrong. It's just like how the how you used it and an ID makes it faster makes it easier to find stuff And so I really suggest if you want to use triple eight use an ID and we will use PHP storm No plug for PHP some there are others. They just have really great triple integration They actually have a booth down there. So talk to them, but So it's just important and now also our front end They all use PHP storm for development in the past we used and Selene and no What's this called? Sublime text. Yes, but now we just use PHP storm for everything and the same also if you don't know how to debug It can get really hard in seven. It was sometimes really easy. Okay. It's probably there And I just put a DPM in there now in eight you do that and it's never called And then it's over Then you start your debugger and then you can actually go into it in seven I think there was a lot of time. Yeah, yeah, let's just try put that DPM and we'll see if it works I think that's not really working right now in eight anymore. Um, so Teach your developers how to use a dead debugger Set up their systems spend the time. We really spend the time We have conference pages that explain how debuggers work and stuff and now everybody can debug and it just makes their life So much easier and to use that Another problem and we just actually the talk before was about that Most examples you will find online With blocks or whatever. They're most probably obsolete because core changed already So there's a lot of code that you will find About blocks and people talking about it since two years like a blog post that is written about About Drupal 8 like how to do things two years ago. It will not work anymore So it's just something you have to know that That it maybe will point you into the right direction But if you copy paste a code that is probably there, it's not gonna work and there is a really good example module that explains you most of the things but Because we use optatic oriented programming. We have interfaces now and interfaces define us like a block has to look like It defines us programmatically What do we have to do to use a class and your IDE will tell you if you forgot to declare a method and stuff So if using OOP, it helps you to to use Drupal 8 correct so and that's really great and It's a bit of I think it just takes time to play gets more stable The there will be new blog post that will probably work But we had it a lot of time that I searched something I'd copy paste it and Doesn't work and then you're back at square one again But another interesting thing is that non-Drupal developers they can just start working right away So I have people in in Zurich. We have a Drupal user group and now just symphony people show up and they say I'm a Drupal developer now because they say Drupal is not specifically symphony. It's like a dialect of PHP And and they can use it because they understand all these things that like Drupal 8 now uses and it's much better So we are not anymore worried about like hiring people that never worked with Drupal anymore If they can develop PHP in like an object-oriented way They can be there now Drupal developers and we use so many different Libraries and external stuff that all others already use So it will be for us much better to work with and of course it will take our developers that right now can deploy Develop in the Drupal way to learn the other way the way how PHP does it but I think it's a it's an important change that We are not longer Drupal via PHP and The amount of people that we can take in from that and get help and understand how things work is so much bigger So I think I really look forward to whatever comes out of that. Let's talk about custom modules So in Drupal 7 There's all the question like okay. What should I declare as a hook? Like at which point in my country module should I write hook because maybe Some other module wants to hook into me my country module and do things The problem is now with a we don't only have hooks we have plugins we have services We have a lot of different things So I think it's really important or it's really hard to architecture now country modules for people that don't have a lot Of core knowledge They will not know how to architecture their country module like what do I create as a plug-in? What is a service? What is still a hook because the hooks are still there So it's like just more complex I don't know how that should work, but I like that happened in like triple deaf days we had like people that are just really into core where country people came to them and And asked them okay, how should I architecture? So there was something like a country architecture mentoring hours or whatever it is So I think like as a as a community we have to make sure that all the country developers They use the system correctly and we do not create country modules that are not used as we can use core Because the people will now learn how to use core and they should also know how to use country So I don't know how that exactly will work, but I think it's just like if you have a country developer that starts to Port the module from seven to eight and it's really important that they read into the architecture of plug-in services And all these things to make it right to not maybe do it twice or maybe three times next topic front-end and I think that's light says everything and it's great like twig It's at the beginning. We just said it's a small step. It's a small change But how we develop now front-end does so much change we give so much more power our front-end devs So it's actually a lot of non-code change now the front-end They really feel to be empowered to work in Drupal if they need to change a class They just do it if they need to change it div or whatever They just do it and it's easier. We have better debugging functions You can now finally realize where the hook suggest a theme suggestions are you see them in line So it's just great to use it and we just start to love and that's one of the really big reasons why we don't want to go back to seven and actually Drupal core itself is so great We don't need a country-based theme anymore like we use right now for seven we use omega not for the whole layer thing stuff But just for the resetting resetting it to html5 resetting it to like all the craziness that some core thing does because core is five years old and So it's not how we do things anymore So I think It's really great that we don't need a country-based theme anymore as a company that builds our own grid systems in saas and And other libraries if you still need a layout system I mean you will still be able to there will be still country-based themes by the community but It's just for us. It wasn't necessary anymore one other thing and I think it's a hidden superpower That is not really teached by core But it's extends and blocks and it's on it's something that is supported by twig and and I give you a small example of what you can use it Let's say we have a task to our front-end devs. We should remove the h1 on the front page Normal thing because the h1 is coming from somewhere else or I don't know whatever So you have your page html.twig and we see here There is the h1 in there that is printed in Drupal 7 what we would do we copy the page html.twig into page-front.html.twig and you do everything again all the things here and you remove here Two months later you add another region. You only put it to page html.twig. You forget it in front You go to the front Whatever doesn't work dr. CC all whatever like Hundred times and you realize oh damn there is a page dot front that html.twig that I forgot about Look at that That's my page front html Which says it extends The page html.twig and it declares a block that is empty. So what happened in? Here that is default is not there But in my page that html.twig I define that as a block Around my h1 and in my page dash dash front I say that block is empty But everything else is exactly the same And I can also do that in other way I can define a block in my page html.twig that is empty and extended in my front works in both ways But we have now a system that you can build like extend of course You can like extend of extend of extend extend it doesn't prevent you of doing crazy things But like the default things are just much easier and that's like one of the examples that I see the front end Now finally like it because before we just throw them some PHP code at them and say like now work But now we give them twig and they can use it and we can use all of twigs functionality We can use in core drupal 8 now So let's go to upgrading Because everybody that ever started a drupal 8 site and then realized that two months later There's a new beta version that I just put my beta version on top of it and then there's like Luckily you see some text because most of the time you see just a white page and like nobody tells you what is broken So before beta 9, it's really hard. I gave a talk in Drupal con Austin and how to upgrade and Drupal sites and it's basically you have to figure out it yourself and After beta 9 there's a project slash idea of head-to-head Which basically means that on Drupal the dog slash project slash head-to-head It's a whole module, but it's just as a bag of scripts That allow you to upgrade between head-to-head so all the people that now have Drupal 8 Production sites running they all have the same problem. They have to upgrade it so instead of everybody doing it itself we now do it all together and Like we're contributing to it. There are other contributing to it So whenever there is a new head and you need to upgrade something in the database layer You need to upgrade something in the config layer or whatever. There will be Couple of days later, maybe couple of weeks There will be a script there that allows you to run that and it will do it And the best is the beta to beta is nothing else than running all the scripts between the head-to-head So we somehow have something like a de facto beta beta upgrade path It's not like supported by core So it won't and also won't be out at the same time as it probably will be soon when we fix all the upgrade blockers But it's a way to use it And in the past I said all the time You can use it, but you cannot upgrade it yet. So now I'm saying you can use it and you can continue use it um But of course sometimes you have to understand things. It's not like I don't suggest that to everybody But if you can recode if you can debug code, it's it's it's possible to upgrade your sites without spending 68 hours to upgrade a site between beta versions, which we actually spent multiple times And so I had core developers working on like or like my back end developers working two weeks to upgrade sites I mean, I learned a lot That's at least what they said They said I learned a lot about core like they know now more things But sometimes you just like you don't not like to spend the time. So yeah, so that you said Contrib what triple is like in seven? It's that's what the great part is like if I need I don't know um If I need a shop I install Drupal commerce if I need organic like some forum system with groups I so organic groups like all these modules that make Drupal what it is We're getting there. Um, so Some contrip is already existing some Drupal 8 some modules are already ported Because there are a lot of production or a lot of agencies running production sites. They're also upgraded contrip The problem is there is no real way to know if it works if you just visit the Drupal.org project page So you can maybe see there is a eight branch You maybe know how a lot how old it is But there is no passing test information or whatever. So it's really hard to know will that work. So basically you just try it out So maybe you make a clone of your site make a backup before before you install it And then you run it and maybe it works. Maybe it doesn't fun is Most of the time if it's broken, it's not really hard to fix it Most of the time it's like some small change in the configuration some small change in like, I don't know renaming things or whatever. Um, so it's not super hard If the module is maybe three years old in this eight then it probably will be really hard But if it's like a month old or two months old, which most Da country bar and there is a new beta version and you upgrade it It's not really hard to upgrade it if you do, please write a page for it I think we are a community we like when you do the work. Why should somebody else do the work? So contribute the patch give it to everybody that the module maintainer can commit it in and we are we're all ready to use it But of course, it's really hard to know Which modules are in which state and there are two links that I suggest one of them is by Berger or sasha grossenbacher He is um also swiss guy and he works at empty systems and he created a page that is called the eight status Um, which runs the simple tests As well So it takes out information about the simple test and it shows you per country module if it currently passes It doesn't the passing doesn't tell you it will work But it's at least more information about it. And then there was blue spark dot com Um that also do a top 100 contributed modules and they tell you like if there is at least an A module or an eight branch in which state it is So it's easier to go there and find your modules instead of going to do bot or dork To like search through all the modules and figure out if there is something Um, overall we try to use not any country modules at all But um, of course, there is things like path auto Which is not in core. It's already ported. Um, we have like global redirect Which is something that we use a lot because of SEO reasons. So it's all there Most of them are there. Um that are like essential to run aside these days But of course the really big ones I don't know like commerce. Um the whole like organic groups I mentioned. Um all other things They they're nowhere right now migration It's not done yet Um, we have a migration between six and eight That works out of core And there is a mosa migration path from seven to eight that is not yet committed. So we're really close to finish that Um, so which basically means you cannot use it right now for sites that um If you want to migrate like It will be really hard to upgrade or to use triple eight for already migration sites, but We had our own like we migrated the amazing apps from the from the triple seven side to triple eight side And we had to migrate all the blog posts Because we realized writing copy pasting them all of them is a bit too crazy But we actually wrote 200 lines of custom code. That's it We just installed services on triple seven exposed all the all the blog posts as chasen We loaded the chasen. There's a jason parson in php. Yay And you just make like a for each and the entity api you just Fill your notes with all the information you get from the chasen You call notes safe and done. That's it. It's now Because it's so easy to use the entity api To use the systems. It's not a lot of work to write your custom migration And the code is on there if you go to our amazing apps github page. It's there. You can use it Um, there are other companies that also do that. So if you just need to Like, um, migrate a small subset of your site, it's really easy and So because we we decided we were gonna rebuild the configuration anyway So all the content types and all the stuff we did by hand inside building anyway We didn't want to migrate that we just needed the content and it was super easy Done like it was 200 lines of code Six hours of a back end developer and we had our migration But of course, um, we want to know like what is my mob like when can I upgrade my site? And I talked before like how to find my modules, but sometimes you just want to know, okay What is the state of my site? So there's a service or a website that's called d8upgrade.org You can copy paste all the modules you're using on your current triple seven site And they will inform you what the current status is. So at one point you probably will get an even and say Now it's ready But it depends on like if you still want to use the same country modules and stuff and so so it will take from time But that website will probably help you to know about the status of your if when can I Start to build triple eight sites of my existing triple seven so I think we should all start using it And it's really great It works pretty well There are some things that you have to consider first Use it if you build a new site if you want to operate a site, I would Suggest to wait Till like the two plus seven to eight is actually in there But if you're building a new site It's no problem or if you need to migrate only some content Like if you rebuild the whole site, it's no problem And also if you don't need any heavy country modules If you depend on the country module and it's not ported yet It's probably gonna be hard to do that. I mean you can do it and you can Pay your back-end developers to port it and that's great. Yay Drupal But If you just want to do it and you want to get it fast on it will be really hard So if you are if you plan to build a brochure site one thing that I call it's like Hey, we are that in that company. We maybe have a blog post. We have a team page These are our clients whatever like a default default brochure site You can perfectly do that with Drupal eight. It works. It runs We have four of them running. We're building more. So I think it's really great Um, we should all try and if you find a bug It's gonna happen write an issue on Drupal.org Maybe even better write a patch contributed and we're all gonna make it faster running to get Drupal eight out To for all of us use it because I can tell you If you start using it, you don't want to go back really You don't want to go back and all your developers also don't want to So if you want to know more of your if you want to Need help There's a groups Drupal.org that was started off the Drupal dev days. It's really empty right now But it's basically an a group on Drupal.org about Drupal eight production sites Where we want to like share information and stuff. It just starts right now. So if you already are I'm using Drupal eight in production. Maybe join there and we can have a discussion about it And there's also both yay buffs Here which is at 345 Um at the room I oh at the room media current. Um Yes, so which Will tell you about or we we can talk about it what you're using what we're not using yes Basically it was my session and now the question part starts. Thank you Yes, can you walk to the microphone that we have it on the recording? So just a quick update on the status of the d7 to d8 migrations I'm one of the people that's working on that. We're going to be sprinting a lot on that on friday Um, hopefully some news should be coming out of that pretty soon. Awesome. Uh, so it is definitely in the works I've done a d7 to d8 migration using the migrate plugins Uh, so it's uh, it's coming along Certainly, it's still not as far along as the d6 stuff is. Okay, great. Awesome. Thanks for the work So my name is keys to chant or uh, my username is kd chant And if you have any questions about that stuff, uh, come and find me or come sprint with us on friday So can we send you db dumps of trooper seven and you will do it? Depends on how much you want to pay me I don't know. I have stickers I really enjoy your talk. Um, thank you. I was wondering if you have anything to share about performance insights and maybe even like External caching like varnish or something else. Yes as it relates to d8 So there is a much better integration of external systems actually the whole like performance settings page has changed to actually explain you what the different settings are And page cache is now a module the internal page cache. So if you don't use it, you just disable it Um, and there I think the varnish module actually also works and so It can help you purge stuff and so so we all the slides we're running we have varnish in front You have max h headers and all the things there's one really interesting thing inside of triple eight There are cache tags and cache tags could theoretically also be Used by varnish because varnish can also use cache tags So you could invalidate based on these cache tags There is no module right now that does that But I know we had a bar from monday with the fastly guys because they're using varnish and do a lot of things They're really interested to have a triple eight module That exposes all the tags to their server or to their system That you can basically invalidate by tags which would make so much more sense than just like URLs and So overall it works And there is a module for it. You probably want to install it But there's not a lot of more if you need any more, but I think that's the default. Yes Do you think d8 is much slower faster? If you use it, um If you configure it and it's per default it's configured it's faster Like you decide is faster because we have view mode caching. We have whole page caching. We have invalidation per cache tags So a lot like whenever you change a node all the page cache is deleted like what happens currently in triple seven So yes, it's better Hi, um, I think just on the varnish thing the invalidating by Cache tags might be in the commercial version of varnish. I'm not sure Anyway, that's that's not my question, but you mean the conversion version of varnish. Oh, yeah, that could be I don't know. Okay. That's what I heard So I've just got a question about layouts like, um, you know, a lot of people in triple seven use panels or display suites and those kinds of tools Um, how did you manage to do layouts and yes? So this place we already has a running version actually since more than a year ago So as asphalicious asphalicious, whatever his username is, um, he's constantly using it So you can already use display suite. We don't use display suite. We use a lot of um panels and panelizer We actually ended up in just using templates again Because it's so much easier for now for themers to load fields and even put them into a files that it used to be in php template So we don't really feel the need of using panelizer anymore and it's actually doesn't exist But one of the missing things that um, that is in core you cannot create pages You cannot create a landing page and put blocks there And so you even have nodes or you have use there is a module the page manager So there will be page manager itself not like shipped within panels or c tools. Um That x specifically supports that and there is a version on it Um, tim plunkett works on it and it actually works and we use it on some of our sites So that definitely works, but it's not whole panels As you know it But we have like a context api in core. So they will leverage that we have a layout api We will leverage that so again, it's like core provides us all these things and we just have to like pull them together And um, yes, so that's what we're using page manager. Thank you Can you go back to the slide with the node id for the removal of active directory? Yes. I have a patch Um the active Okay Okay, any more questions Yes, yes Security good point So the security team currently does not Carries the wrong word, but does not review anything in droop late So like Drupal getten Also exists in innate. There was no security announcement. There was nothing that pushed you saying You should now update your droop late site because it was also in there Um, so security could be a concerning thing because if there is a security patch found It's it's posted publicly in the droopal issue queue Anybody can find that can write an a script that uses that issue or that had that that whole And hacks all the droop late sites right now And so it's just something to know what we do Our hosting environment is built that every single site is completely separate for others So if one site gets hacked it cannot hack the other sites And from a database from a file structure from basically everything And so and I think that's just important to know Because the the chance that your droop late site is hacked is getting hacked is probably higher than in seven And so to to keep it in one place and make daily backups and all these things Um But we decided that the risk is not that high because We think that Drupal 7 itself is already super stable. I mean we only had one Really critical issue in the last seven years and I don't expect anything happened right now in eight Of course that is also depending on that we run Drupal 7 since a long time So there's a lot of things happened in the past And I think with if when you know these things That's basically you can live with it and you can work with it and you can Create stuff around but yes, it's not reviewed anything at all. Good point. Thank you Okay, that's it. I'm gonna keep you longer if you're around have more questions just hit me Thanks