Sign up to access "Build an E-Commerce Platform" right now.

of tweaking here because on the home page that's where we want categories but at the moment we've got that default welcome screen. Now the only issue with Laravel Breezes is if we open up app.blade.php and come to the top we've got this navigation here which we can open up but inside of here we can't use this on a guest page. Let's take a look at what I mean. So I want to copy

dashboard.blade.php at least the entire structure over to that welcome.blade.php page. So we're going to paste this in and pretty much have this as our home page. So let's just write home and this is going to be our list of categories. So if we just come over to the home page now and there we go. That works but if we're signed out we can see we've got an attempt

to read property name on null and the reason for that is inside of that navigation component this always assumes that the user is logged in. So this section here with the settings drop down and if we head up a little bit further we should have, well head down a little bit, we should have another version of this as well just here for the mobile menu. We want to kind

of wrap this and only show this if we're signed in. So the first place to do this would be in here so let's go ahead and just collapse this part and let's have a look yes log out as well. So we want to wrap this in auth which is a Laravel directive which will only display the content inside of here if the user is authenticated and we'll do that just up here as well for all of

this stuff here. So let's just go ahead and grab this drop down and that should be it I think. So let's just add this auth check inside of here as well. So we're basically just not showing this unless the user is authenticated. Let's go over and give that a refresh and there we go. So we've still got our navigation structure which we want for a user who is not signed in but we can at

least use this now even if we're not signed in. Now we also want some buttons to log in. We'll get to them a little bit later when we start to add in our cart and everything up here. For now we just want to focus on our categories. So a good place to start would be a model. So let's just close everything off and let's go ahead and say phpArtisan make model category. We'll generate a

migration alongside of this as well and you can generate a factory if you want to randomly generate some categories. We're going to manually do these. Okay let's open up the create categories table and let's fill this in. Okay so we just need some basic information in here. The first thing is going to be a title and then we're going to go ahead and include a slug as well. So we can use

that in our urls but really importantly we're going to add a unique constraint to this in the database. Now because categories are going to be nested we want to reference a parent id so we'll create a kind of top level category and then underneath that we'll have something that references a parent id. Don't worry if this doesn't make too much sense at the moment we'll go ahead and

cover this when we look at our adjacency package. So we're going to add this as an unsigned big integer because an id is an unsigned big integer. You probably won't have that many categories but we'll add that in anyway and we're also going to make this nullable because some categories won't have a parent id e.g if they're the top level categories. So that's pretty much all we need

for categories. Of course feel free to add more like descriptions or anything else you need. So we're going to go ahead and run phpArtisan migrate on this and we'll start to fill in some categories. So let's just do two top level categories to start with. So I'm going to go and call this brands, slug is going to be brands, the parent id is going to be null and then let's go ahead and just

add another one in here. Let's just call this styles, we don't really care what it is for now. Okay let's save that out. Okay so let's at least create a controller to display this information. At the moment over in routes and web we've just got this route closure here that returns this welcome view. So let's go ahead and create out a home controller. So let's say make controller

home controller and let's go ahead and hook this up to that. So let's grab all of this home controller and we'll pop that in there. So if we open up our home controller let's create an invoke magic method because we're not going to use method names here and let's return that welcome view. We can even rename that actually to home. I think that would make a little bit

more sense. So let's go down to welcome and just rename this to home.blade.php. Great. Okay so we want to grab our categories out here. Let's just do this really really quickly just the way that we would normally do this and then we'll look at our adjacency list. So we're going to go ahead and pass the categories down to here and why don't we just go over to home.blade.php and just dump

these out on the page. So let's just say categories and let's come over. There we go. So we've got them two categories at the moment just represented as JSON being dumped out. So the goal here is to get a kind of tree-like structure of all of our categories and then recursively iterate through each of them. Now at the moment what we can't really do is exactly that because we would have

to create a complex relationship, perform way too many queries. We've got a snippet on CodeCourse about using adjacency lists if you want to go ahead and check that out for a little bit more information. But let's pull this package in and see how we can build that tree up as we add to our database. So let's come down and go ahead and use the composer require command just to pull this

in and then let's go over and see what else we need to do. So we want to use the has recursive relationships trait on any model that uses recursive relationships. So that is going to be our category model. Let's open that up and we'll go ahead and use this trait in here. Might just need to re-index our workspace and there we go. So let's just pull that in. So we want to pull that

in and that is it. Now this relies on having a parent ID which we already have. So let's just start to add some subcategories here. So I'm going to go ahead and add Nike in and I'll just put the slug as Nike and the parent ID is now going to be one. Let's go ahead and fill in the time stamp for this as well and let's under styles or we could call this seasons actually and let's go

and add in just a couple under here. So let's say summer and let's set that to two and then let's just duplicate this down and we'll just say winter and this could go on and on. So these two categories are under seasons and Nike is under brands. We'll leave it at that for now because we can add more and we're going

to be recursively iterating through these so you can build up as big a tree as you like. But I think that will be enough for now. Now if we head over to our app we can see that this will just dump all of them as a kind of parent category. So if we were to start to iterate through these as a kind of parent category. So if we were to start to iterate through these now

we would just see every category underneath each other and it wouldn't really make that much sense. Now we've got this recursive relationships trait in here what we can do is in a single query effectively build up a category tree and then display that and keep this stuff in mind because we're going to be using this later like I said for our product variations.

So with this package what we can actually do is use a tree method we can say get and then we can say to tree. Now let's just take a look at the difference in the output here. So this is executed one query using a common table expression to grab all of this data and at the moment we can't really see what's going on because we've got this sort of top level one here then the

children of that which is Nike and then we've got a seasons which is top level and then under that if we just have a look really carefully we've got all of them children. So effectively as we add to these categories they're going to keep adding as children properties underneath each other and really importantly that's going to be done in a single query so we're not iterating through

and creating a query for every single depth of categories we're creating. So now that we've got that set up good time to go over to the next part and look at how we can actually recursively iterate over these to display them as we saw from the introduction. So let's head over to the next episode and do that now.