 We'll come back to the channel. We're going to be looking at Graphico, which is an IDE. It's just a development environment for us to check out what our GraphQL queries look like and then we can be able to just pick those and duplicate them maybe in our React app or React Native or whichever kind of technology can consume GraphQL content. So one of the things that I've found very hopeful is actually the little bit of documentation that GraphQL has. I know the big myth is that GraphQL is self-documenting because let's say when you hit a particular, when you want to query maybe let's say for pages, you're able to see that and it can quickly give you information that you can, you see as I hit some of these little pieces, we can actually get back the information that probably at the end of the day we shall use, but without us even knowing what's going on, we're able to hit the endpoint and we have this query and this data is actually returned for us if this is what we needed and let's say if we didn't need anything, we're able to take out just one small piece and get back the information that we do need. Now of course this is helpful, but what I've found more helpful is what is debt, what is debt GMT, what is GUID. When you hover over this, the WP GraphQL plugin allows us to see the little bits of information that we can find maybe even in the particular codex, in the codex of what press that we use. So we know that this is the UI, the link that takes us to the post and we can get it from the WP post object if we queried a particular database. If we look at the ID hovering we know that is the page ID and if we look at the status we will know whether it's published or it's draft. So coming from the WordPress background gives you a little bit of this naming conversion that's available. However, you can quickly also open up the docs here that give you a little bit of information. WP GraphQL has done a very good job about trying to give more background information about what's going on. So for example if you were to hit the categories or the comments you're able to see what it's talking about. So you have the comments, you can know what you use in your query. These are the arguments that you can have. So for example I'm going to have a query here and I'll go for comments and I can actually just add a query and say I want to get the first ten comments per se. And in those first ten comments I should be able to get, I'll use the control space bar to find out more so I can get the edges and then I can get the node and inside the node I am able to get whether it's approved. I can get the content so let me check for that quickly and you'll see that we don't have any particular comments per se. It's an empty string but we can find the first ten comments only and apply them later to a particular page if we are going to run it. So also in the root query we are able to see more of the other pieces of information that we can get and that is all available. So these are some of the new, I've written a little bit of code to try to expose the particular custom post types that we have, events, players, clubs and stuff. I've also tried to expose some of the different taxonomies that are available and you'll see that these are not well documented, there is no information about them. So as I put them I need to do a better job at adding documentation for my club or my events or my players so that people can actually follow those up. So what I'm going to do is I'm just going to go back to the custom post type documentation. I'm going to look at the documentation here and then I'm going to try to find out how I can add all of that and I realize maybe I should just try to add the description type. Let me go to the codex and see how we add custom post type. So we know we use the register post type function of our WordPress to add new custom post types, skip through. I'll go for register post type. Now it usually takes in an argument of description. Let's see what is going to help us to add our documentation. So in our player what I'm going to do is I'm going to duplicate this and in the arguments I'm going to pass a description and let me say and let's see whether this will work out well for us. So I'll save this. I'm going to come back into our IDE. I'm going to reload this, go back to the schema that's here, player and that is not the way you add it. So when we go to the player schema we'll see that it also has its own query and as we click on the individual players some information by default comes through. For example things like author, content, content type, dates, the GMT that are generic to every custom to every post type have already been filled in but there is a lot more that needs to be desired in order to make this a better little piece of content for people to follow through as they look through the schemas just like how we've done the different post types. So I think this is a part that is still missing in the documentation and how to extend. That's a part maybe that I'll have to look into. Maybe I'm just skipping and I don't know where this is coming from but it should be available. If you enjoyed the video please give it a like or subscribe to the channel and leave a comment how are you finding this out? Have you been able to actually document your WP Graph QLR new custom post types or taxonomies? Let me know in the comments below. Thank you. Alright welcome back to the channel. We're going to be looking at graphical which is an IDE. It's just a development environment for us to check out what our GraphQL queries look like and then we can be able to just pick those and duplicate them maybe in our React app or React Native or whichever kind of technology can consume GraphQL content. So one of the things that I've found very hopeful is actually the little bit of documentation that our GraphQL has. I know the big myth is that GraphQL is self-documenting because let's say when you hit a particular when you want to query maybe let's say for pages you're able to see that and it can quickly give you and it can quickly give you information that you can see as I hit some of these little pieces we can actually get back the information that probably at the end of the day we shall use but without us even knowing what's going on we're able to hit the endpoint and we have this query and this data is actually returned for us if this is what we needed and let's say if we didn't need anything we're able to take out just one small piece and get back the information that we do need. Now of course this is helpful but what I've found more helpful is what is dead what is dead GMT, what is GUID when you hover over this the WP GraphQL plugin allows us to see the little bits of information that we can find maybe even in the particular codex in the codex of the WordPress that we use so we know that this is the UI the link that takes us to the post we can get it from the WP post object if we queried a particular database if we look at the ID hovering we know that is the page ID and if we look at the status we will know whether it's published or it's draft coming from the WordPress background gives you a little bit of this naming conversion that's available however you can quickly also open up the docs here that give you a little bit of information WP GraphQL has done a very good job about trying to give more background information about what's going on so for example if you were to hit the categories or the comments you're able to see what it's talking about so you have the comments you can know what you use in your query these are the arguments that you can have so for example I'm going to have a query here and I will go for comments and I can actually just add a query and say I want to get the first 10 comments and in those first 10 comments I should be able to get I'll use the control space bar to find out more so I can get the edges and then I can get the node and inside the node I am able to get whether it's approved I can get the content so let me check for that quickly and you'll see that we don't have any particular comments per say it's an empty string but we can find the first 10 we can get the first 10 comments only and apply the blades to a particular page if we are going to run it so also in the root query we are able to see more of the other pieces of information that we can get so we can see the arguments that we can apply we can see the descriptions of the content we are having and that is all available so these are some of the new I have written a little bit of code to try to expose the particular custom post types that we have, events, players, clubs and stuff and I have also tried to expose some of the different taxonomies that are available and you will see that these are not well documented there is no information about them so as I put them I am supposed to have a proper I need to do a better job at adding documentation for my club or my events or my players so what I am going to do is I am just going to go back to the custom post type documentation, we look at the documentation here and then I am going to try to find out how I can add all of that and I realize it is not it is not it is not here, there is no where I can put this here maybe I should just try to add the description type let me go to the codex and see how we add custom add custom post type so we know we use the register post type function of our WordPress to add new custom post types but skip through I will go for register post type now it usually takes in an argument of description let's see what is going to help us to add our documentation so in our player what I am going to do is I am going to duplicate this and in the arguments I am going to pass a description and let me say sports press exposed player custom post type and let's see whether this will work out well for us so I will save this I am going to come back into our IDE I am going to reload this go back to the schema that is here and let me look for player that is not the way you add it so when we go to the player schema we will see that it also has its own query and as we click on the individual players some information by default comes through for example things like author, content, content type dates, the GMT that are generic to every post type but there is a lot more that needs to be desired in order to make this a better little piece of content for people to follow through as they look through the schemas just like how we have done the different post types so I think this is a part that is still missing in the documentation and how to extend so maybe yeah so that is a part maybe that I will have to look into maybe I am just skipping and I don't know where this is coming from but it should be available so as I look through I should be able to get it just a few types so alright alright thank you for watching the video if you enjoyed this please give it a thumbs up or subscribe to the channel if you enjoyed the video please give it a like or subscribe to the channel and leave a comment how are you finding this out? have you been able to actually document your WP GraphQ new custom post types or taxonomies? let me know in the comments below thank you