All right.
And the way we set up nested pages in Reactor Outer six is falling.
So we go with our parent route, which in our case is going to be for its lush, but I'll showcase that
it is regardless.
Whatever the URL is over here and then whatever routes are going to be placed inside, we will get both.
We'll get that shared layout, which we don't have in this particular example yet.
So set up later.
And also very actually are relative to the parent.
So in this sense, this is a home run.
It's going to be Ford's stats, all jobs, our job and of course, the profile, and we'll set up our
components.
But if I were to type here different URL, then it's going to be forward slash, for example, dashboard
than Ford slash that.
And the same for all the jobs.
So hopefully you get the gist and also eventually will set up the index.
So start step by step where first I want to showcase how the URL is going to work and then the shared
layout, where eventually we'll have those nav bars and sidebars and also eventually will add the index
over here.
And if indexed at the moment, doesn't make any sense.
Don't worry, we'll get there in a second.
So our first step is falling.
We're closed all the times just because I'm annoying that way and I'm going to look for my app.
Jess and I have my route, so that still stays the same.
We're not touching the roads.
Here's what I want to do, though.
I want to remove this element, and I want to actually remove the closing one.
Now I want to set up my route.
So that's going to be my home run and then inside of it.
Let's place the rest of them all.
Jobs profile, not sure.
Allowed stats and add.
And now I just need to come up with the URL.
So in my case, I'm going to go with all jobs van.
I'm going to set up ad job and stats and profile and stats eventually will be an index dropped, but
not for now.
So let's go here with around and then I'll go with path.
So that's my URL.
And then let's say stats, then what element do I want to render?
Well, I have the stats one, correct?
So let's go here with stats, then let's close this route and then let's copy and paste.
Now we just want to change the URLs, and we also want to change the components.
So my.
I'm going to go with all the jobs and we want to set up our job and job and then lastly, we have over
here a profile profile.
Now we want a change here component.
So let's say here all jobs than where you want to at the AGM, add job.
And then lastly, we have over here a profile, and once we have all of this in place, let's save it
and let's navigate to the big screen because first, I want to showcase how the URLs are going to work.
And as I Senate, there's a tiny bug over here.
Actually, we don't need to set them up these boards.
My apologies.
This one actually will be relative by default.
So we save over here and then let's navigate to our local host 3000.
Now, at the moment, nothing riskier.
That's fine.
Let's take a look at the forward slash and stats.
What do you think you're going to see or hear?
Perhaps that's correct.
So if I'm going to go to all jobs, what I'm going to get here, all jobs.
So this works.
I know that I can hop from page to page.
And since they're nested, eventually there's also going to be a nested layout.
Now let me showcase that this path is always going to be relative to the parent.
So if I add here, a dashboard supports slash and dashboard, which you'll notice that now the parts
are going to be dashboard stats and hopefully you get the gist.
So let's navigate back.
At the moment, we have four or four.
Why?
Well, because there is no page, all jobs.
What page exists there?
There's a forward slash and dashboard, and then we have all jobs, correct?
And once we navigate here, woah, we have all jobs page.
So hopefully this is clear that in order to set up a nested structure, we just need to come up with
a parent throughout.
We need to come up with the URL, which in our case is the home page.
And then whatever route we nest inside of, it will always be relative to this.
And we're still set up the path.
We come up with the URL and we pass in the element.