 Let us get to the agenda first, so first of all we are going to what is migration and why we need to migrate to the teams, group of 7 or 6 teams to group of 8. So we will go to what and why and then we will go to group of 8 in there, what we have left behind group of 7 and what we have new things coming in group of 8. After that we will go to the migration process, what are things we need to consider while we are migrating from group of 7 teams to group of 8. Then if time will permit we will go to a small demo as well, we will go to group of 7 or basic team and we will migrate that team to group of 8. Let us start, what is migration, anyone? So consensually migration, migrating an old website to a new website will be a simple it should be as simple as this, turn off your old website, copy your data or configurations and turn on the new website. But as soon as you go into the details and for example you will need a backup when you are stuck, you mess up something. Yes, but it will be a process of your data base migration, not just this is just for content. So in case you mess up with something, so you will need a backup of your old site, so that if you mess up you can go back to your old site. So the simple looking process just turn off your old website, copy your data and turn on the new site will become a little bit more strapped will be added here. Same way whenever we are migrating group of sites. So you will see that whenever you say take a backup of old site, if it is a group it is not just a backup of your old site. It is like you have to backup your document separately, you have to backup your data base and then if your files or PDF files are somewhere else on other server then you have to make a copy of that as well. So that simple looking process of turn off your old website, copy your data and turn on the new website will become a complicated process. So whenever we think about migration, it is not a simple process. Let us not get into this. Let us get back to that question that what is migration? So I wanted to just describe how the process of migration is. Let us just look into why we need to migrate. And even Drupal 6, Drupal 7, Drupal 8, why we need to migrate. Drupal 7 to Drupal. So there are multiple things. Drupal 8, frontend has a list of changes which Drupal 7 didn't have or Drupal 7 was having a new course where we have made large improvements security-wise, performance-wise. So there are ones of list but here is the highlights of what is changing in Drupal 8. So we have lots of things but so the core, right? Now the core of Drupal 8 is outputting HTML5. So we get latest code, latest marker with the HTML5. As you all know we have quick support now, right? We must be using particular types and all. So now the ready key layer will be improved with quick and symphony key frameworks. The break points, there was a break points model, right? Now it is in code so we can use break points by default out of the box. Just we need to add one pipe and you can use the break points all over the modules, themes and across the website. So that's how break points will help. Apart from jQuery, right? jQuery is in the core now. Apart from that you have modernizer, underscore.js and all other front and related libraries as well in Drupal 8 core. So those are things that will help. These are the other few examples or you can say other features apart from those features we have talked about. Yes, there are no more Drupal ads, CSS. You have directly, we have CSS and JS aggregation by default enabled on Drupal 8. So those are the few other things we have. I just wanted to make a point here that all these code and master features you get when you migrate your theme from Drupal 7 or 6 to Drupal 8, right? So let's move to a theme layer and I wanted to give you a brief introduction of what major points have changed in Drupal 7 or Drupal 8. So bye-bye BSD. So D and themeers don't need to know BSD because now we have 2A where you know the, now we have 2A templating so you no more need to know BSD, right? This means PHP template and the whole theme layer very insecure. So we had something like this, right? If you write in your TPL, anything that TPL that PHP you write where you drop your user's table, it was possible for the PHP template and the DPS file, right? So now bye-bye PHP. We don't want any more. Themeers must be flat here. The I8 is also, you know now Drupal 8 supports SPG and all those things, whatever browsers which are not supported which do not support SPG is now nowhere and Drupal community has not made any of the browser's compatible things. So lack of browser support for I8 and below means we will get more HTML5 and CSS3 and modern jQuery libraries will be able to use those things, right? Because there is no more support. Drupal 4 will not support I8 and older browsers. In mobile as well, Android 2.3 and below will also be not supported. You must be aware of this thing, right? I mean the Drupal 7 theme layer, right? It was like, you know, there were lots of theme functionals, lots of theme files and the theme layer was complex system and whoever will be working with Drupal 4, they also got confused and frustrated about the system. This makes Drupal 7 hard to learn and is one of the reasons the learning curve for Drupal 3 was very long or you can say so huge. So now no more Drupal 7 theme layer. This is gone as well. Then we have, as I said, right? We have the theme functions, we have the TPS files. All the theme function and TPS files are now, you know, I have been completely removed and I have replaced with fake templates. There are too many different ways to display content in the TPS files. As you say, you know, you want to, if you are in the no TPS.tsp files, if you want to print the attributes, you have to print the stream, right? If the variable was a stream variable, if you want to render a content, you have to, you know, do it in a different way. So there was too many different ways to display the content and there were too many TPS files as well, right? Template files. Besides the template files, Drupal 7 also had the theme functions and the theme functions were more than what we had TPS files, right number of TPS files. So theme functions were more than that and as you say, right? And the syntax identity was almost impossible in the Drupal 7. So these were the things, older things. Let's look at the new things what we can get in the Drupal team here. Any questions, Vilna? So we have gone through the few things we won't see now in Drupal 8, right? Let's now look at what's new coming in the Drupal 8. Too much to list here again, but I have tried my best to cover, you know, as many things as I can. So first of all, TWAIT, right? Whenever you are working with TPS files, whenever you will work with, if you say you will work with TWAIT, it's so simple, it's secure, and it is easy to understand. If you don't know of PHE, then as well you will be able to, you know, build your template files in TWAIT. So TWAIT, you are, you know, right? It's a PHP-based templating language. It is a part of Symphony 2, which is supported by Drupal 8. Tweet syntax, as I said, will be much more easier than the PHP templates. Tweet markup language will also make teaming easier to understand, and non-programmers will also be able to build the teams easily. So Drupal 8.5 will be called support semantic HTML 5, with output semantic HTML 5. So you get latest markup for all your applications, like mobile, Z, website, right? And Drupal 8.5 will be called support responsive, and it ships with responsive features, such as you have six responsive toolbars, you have responsive images, since it is support SPG, you have responsive tables. Breakpoints are also now included in the in the code itself. So you can set the breakpoints once, and you can use the breakpoints across the website. CSS and JS are also now, you know, added no more in the theme.info file. You don't have to, you know, you don't have to write it there. It uses the libraries now to, you know, import all your CSS and JS. Okay. As I said, right, earlier, besides latest delivery, we also have this wonderful front-end libraries included in Drupal 8.5. Okay. Quick recap. All in all, we have all these new tool features, right, in our Drupal 8. So we will now be able to create some cool front-end applications. Yeah. So we have gone through the what we have left behind in Drupal 7, and we have new coming in in Drupal 8. Let's see the file structure changes first. Since, you know, if you want to migrate Drupal 7 into Drupal 8, we should know, right, what's new and what's changing in Drupal 8.5 structure. Everyone is able to view this. In short, you have to learn it. But, okay. Whatever was in the in the Drupal package earlier, right, whatever core things was in the Drupal package is now moved to the core folder. The core modules and themes are now, you know, part of the core folder in the Drupal 8 package. All our sites on slash star is now in the true folder as you see here in the right-hand side. Modules, profiles, sites, themes, all these things are, you know, whatever your custom things are, all the contributed modules which you are going to use and we go in the modules directly on the themes which you will be creating you will download the content and the themes less contributed. I'm going to see it in the next slide. Okay. So, let's go to the theme folder. Right. So, whoever will be working with the Drupal 7 theme will know this, right. Where you look for your themes, right. Where do you put your theme folder, your custom theme folder. If you are familiar with Drupal 7 theme, the first place you will go is sites or themes. Right. So, Drupal 8 has the Drupal 8 theme folder structure is now changed. It has used to, you know, you change to the whatever your custom and content themes are, you can put it directly in your true theme folder. Okay. So, for example, if you want to create a custom theme, say, example theme. So, you will put it like this in Drupal package. You will have themes folder and inside that theme folder you can create custom folder and inside that you can put it, you know, you can create a folder, like, example. Inside the example folder, right, what one file you will need is info.tml file. Right. So, info.tml file is a, it is passed using symphony of PML component. You can simply create info.tml example. For example, our previous example, right. If you want to create an example theme then what you have to do is you have to create a PML file for example.info.tml. So, now, once you create this file, right, whenever you will you will go to admin's less appearance you will see your theme there. So, yeah, you have created Drupal 18. Once you, you know, create info file. Okay. This is the whole Drupal 8 custom theme file structure. If you see, nothing has been changed, right. If you are working with Drupal 6, Drupal 17 then, you know, everything looks same. I mean, CSS folder is there, images folder is there. There is a template folder where, you know, you will put all the all your PBL files, right. So, the structure folder structure is not changed much. There is one change then the schema, right. Schema is going to be config slash schema. So, yeah. And the other changes you and not anymore, we don't have any more dot template file, right. Template.php file. So, we have instead of template.php file we have example.theme file. So, that's what changed. I mean, not changed much. Okay. So, now we move to actual thing, why we are here, right. The migration part of this. So, next few slides now will give you inside of you know, if you want to convert your Drupal 7 theme to Drupal 8, what are changes you need to do, right. What are things you have to consider to make sure that you you know, successfully can successfully migrate your Drupal 7 theme to Drupal 8. Okay, first thing first, install Drupal 8. So, nothing much here you have to download latest Drupal 8 and install it. That's it. And then yeah, once you install it, you are going to you know, create your new theme instance and you will start putting your Drupal 7 things there, right. So, that's it. The next thing is you need to create a folder factor, right. We said that if you want to create your own theme your custom name folder and then inside that folder you create your so that's how you will create your folder inside your themes, flags, custom flags whatever your theme name, right. Okay, the necessary files, right. So, as I said, there is only one necessary file which is your theme name dot yml yes, no more theme dot info file. So, let's look at the example of how the theme dot info dot and if you are working with Drupal 7 already Drupal 7 theme already you will know the first bunch of things, right. The name, type, description all these things are same as it is and that there is a same text difference but it's same as you know how you create a Drupal 7 theme. The next part, right, the style sheet remove as well as it's not added here but style sheet style sheets remove and style sheet override are two ways to control some of the core CSS core style sheets to override or if you want to remove some of the core files then you can do this like for example here if you don't want the menu dot theme dot CSS file which is coming from code, you can remove that by style sheet remove you can add this style sheet remove there in that you know whatever style sheet you don't want. The library is a new way to do our styles of scripts in a more modular fashion here in order to you know reference the inclusive core and we need to make sure that you know whatever you add here to create your example that library is dot byte byte byte and add those there. Okay region functions is on region thing right there that's also similar to what we are doing in local 7 settings again similar to local 7 so nothing changed here and apart from you know we don't have to put hypern or things like that from the local 7 Okay so breakpoint module is now from local 8 so whatever breakpoints you want to create right needs to be added in the example dot breakpoint this is one example of how to create your breakpoints dot dms byte it has mobile view and you don't now have to create media queries or write media queries in your CSS file you can define it here and all your modules or your custom team will be using this okay so team migration process the next thing is once you know create your breakpoints dot dms byte you then have have to create over your ppl files to into the twig files right so here we need we need to 25 your ppl files basically convert your ppl files into the twig syntax okay and if you have page dot ppl dot psp you have to convert that into ppage dot spml dot yes we have a very cool feature for 25 d0 slash project slash 25 that will convert your modules and themes to all this basic things whatever the info you are writing for the theme i need those files to be converted automatically for basically you are writing everything there which is first idea you have to write everything then is there any tool like that i order of drupal console so that you have you have to write and it will ask you all the details and you put all the details and it will automatically create your thing for dot ml file library is dot ml file and all those files will be created automatically drupal console will create with a new theme new theme drupal 7 things will be converted to the 25 25 will convert it to the info files also you know it will give you bunch of things you have to change them convert it for you and then there is some more worth going on there it is in beta i guess even aware of 25 module for drupal 7 but it is in beta or in alpha i guess and it is in alpha right but you can use this to convert ok the final step is tree process functions luckily we do not have any more changes in you know tree process functions for example if you need to include an image in one of your page dot ml file you can still do that in tree process functions so then over your page dot html dot quick file you will be able to use those image models so tree process function is still not much changed and finally we have sub theme so there is no much change there as well you just have to include the base theme line in your code any questions here yes so base theme needs to be converted into A to work with PR something right so if you just want to convert PR something and you can follow this process you will create your info file and if you do not have the bootstrap folder there as well it will work and you just have to remove the base line from your info file and it will work as it is any questions right for to do what to change the theme loading theme loading the different theme based on code this is there all the books whatever we get all the books are let's get into it and we are now I how much time we have we have 15-20 minutes more I will get into the time I tell the total 17 basic total 17 so this is the total 17 which we are going to migrate into total so let me show you what total 17 is so this is my total 17 it is a something of zen as you see something of zen and it just look like we have sticky header, sticky footer and that's it so what we are going to do is we are going to convert this theme into the looper so I have looper 8 installation on my laptop so what we are going to do is as I said whenever you want to create your own theme you have to we have this looper 8 what I wanted to say is we have looper 8 installed here we have as I said the theme folder is now in looper in the looper package so we have themes there we just have to go and create a new directory for example and say demo for example let's create info 5 just open info 5 this is my info 5 in my looper 7 theme so here I have screenshot I have name, description, code things like that I have typeset here I have script.js and then I have regions then you have settings as we have seen in the earlier version so let's convert this info 5 to looper 8 so whenever you have named write name you could have taught me this was the looper 7 now what you have to do is you just so this is the format you will just name your so these are the few things you have to write fact it's custom then you have to define your code if you are defining your name engine because now we are using twig PST then you have screenshot you can same way like looper 7 you can add screenshot you can define the name of the screenshot settings we had in the looper 7 version we had these settings these things so these things as well you can put fabric on you want a lot, logo things like that so these things as well you can define your highlighted versions of content and in library you can say global style right not visible that's fine okay so this is how you know to create your info 5 once it is created let's see we are able to see the you can go to you will be able to see our new theme there we go so we have a demo theme here so for your website on mobile and you will learn that you know this example mobile is for the mobile view the narrow thing is for the tablet thing for this thing for the wider space so it will automatically know that did you just have to go to your custom view folder and create the example no it will be and there will be different css files for your mobile thing time you will have something called mobile.css or something like that so cool so in your global page you have something called site and it works the same as how you will be able to protect you have site and you take that for example this poster and you take that for the other and that is what okay kids we have something for the second yes yeah well thanks everyone thanks for your time