 All right, one more time. If anyone outside or anyone right outside this hall can hear me, please enter. We're about to begin our first presentation after lunch. And now let me get right into it. Our first speaker after lunch has been wearing many, many hats. He's a member of RoadTrack. He's a mathematics tutor. And he's also been a college ambassador when he's free. He says he likes to roam around mountains, so sort of a mountaineer also. By profession, he's a software developer. And today, he will be speaking on the topic harnessing the power of GraphQL in WordPress. Ladies and gentlemen, let's welcome with huge round up of applause, Mr. Sandeep Bhasthit. Thank you. Thank you for your wonderful introduction. Hello, everyone. Good afternoon. I'm Sandeep Bhasthit. So as of today, I'm using GraphQL in WordPress. It's already used in WordPress. There's no alternative to how to optimize it. I'm going to present it to you. So let me know a few things. Here, we have a lot of people working in the REST API. We're consuming the WP REST API. OK. And then, how many of you have worked in the REST API? We've developed it in the API. OK, a few, a few numbers. And we've worked in GraphQL. Who knows? We've consumed GraphQL. And then we've developed GraphQL API. OK. So we're going to go into a new one. Now, I can't go to the graphQL. I have to think about it. OK. Let's start. We've talked about GraphQL. Now, we've talked about it a lot. So we've taken out the GraphQL from Facebook. We have repackaged the social media on the graph rate. GraphQL is an architect. There is a little bit of architecture. Just what is going on. So, we have a graph related data, networking, multiple notes, multiple content, we have designed and managed it in 22-well. Then, we have opened it in 2015. We have opened it in 2015. We have a rest and graph. First, we have a soap. Rest in peace soap. Now everything is rest. We have a graph tool, a feature, a root development, which is used to do the rest API development. We have a shift in the graph tool. And then we have a graph tool and a rest. We have a graph tool and a defined factor. We have a scheme. We have a front end and back end contract. We have a KK type. So, we have a detailed area in the exchange. Then, we have a query language. Now, we have a scale query. We have a back end server. We have a server setup in the back end. Then, we have a database contact. Then, we have a database value. We have a data store. Then, we have a query. If there is a front-end word, we can pass it. We have a demo area. Then, we have a single input. We have a rest input and a rest in post case. Then, we have categories, author, user details. Then, we have tags. We have to do all these things. We have to do the individual API. We have to work on the rest and consume it. Then, we have an entire purpose. We have an entire API. We have an entire input. But, the beauty of this is that we have an entire input throughout the server. So, we are going to do the rest. Then, we are going to use Kaka today. I have only taken a few samples. In this, we have used Courserar in ad tech. Then, we have used PayPal in print tech. Then, we have used Streaming Giant in Netflix. Then, we have used Github's comprehensive, best graphical implementation. We can see Github as well. Now, we have introduced GraphQL. Why GraphQL? Why not rest? The first reason is overfacing. We have a lot of data in China. For example, we have to do the details of our old-fashioned post. All the data are rendered. We have to show the ideas. We have to show them. We have a lot of information. We have to show the ideas. We have to show the tasks. We have to show the pilots. Then, we have to do another thing. We have to do underfacing. How to do underfacing? We don't have the Chinese information. For example, we have a list of old-fashioned post. We have to show the post list. We have to call the new one after the data is not input. We have to do underfacing. We have to do underfacing. Then, we have to do maintainability and scalability. What about the other new feature? We have to do new input, not input. We have to do error or other things. We have to do it even though there are several changes. We have to do error or other things. We have to do input or other things. We have to do an error or other things. We have to do crud. Then, in case of maintainability and scalability, the graph is very elegant. Then, we have to do other things. In this case, we will make a declarative, whatever we want, we will make a contract with Amazon, and in that case, they will face only China. They will not face only China. In this case, we will make a graph with a QA which is called back-in-front for front-in. What does it mean? What does the front-in mean? The back-in is used to make things dangerous. For example, it is used to make circles or make bubbles. It is a must or a pass. The front-in does not need any information. What does it mean? In this case, we will make a graph of front-in specific, front-in-focus, client-focus. The next reason is pagination. Here, we call it cursor-pagination. I have highlighted it. How to use it? How to use it? It is interesting to see how to use it. How to use it? I have given a link in detail. How to use the cursor-pagination? It is used to make slacks. It is used to make slacks very fast. It is very fast when you message it. It is used to make loads. In this case, we will make multiple posts on the site. It is used to make pagination 1, 2, 3, 4, etc. How to use it? It is called Irritating. It is called Irritating. It is called UX. In that case, it is used to make slacks and messages. It is used to make posts on the site. It is called Graphical Core Principle. It is called Cursor Pointer. It is used to make cursor pointers. It is used to make checks and balances. It is used to make check-in balances. It is used to make check-in balances. You will get fun with documentation. If you want to prepare the documentation. As I made the rest in point, You can prepareimi like the specification. that's why I have offered free. Dawmin it by think. In fact, there is an inner reason. What is it called? It is called declarity because Graph shortcut map is used. It goes into a rest-services course. It appears even before the existing lags. There is no Vertical tool in the top graph. That's why you need to… Is it okay? Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay.