Now, speaking of amazing NextJS features,
I wanna come back to that decision we had to make
when we created a new Next project.
There, we had to choose whether we want
to use the App Router or not.
And I mentioned that there are simply two different ways
of building NextJS apps,
and these different approaches exist for historic reasons.
There is the so-called Pages Router
and the So-called App Router.
Now, no matter which approach you choose,
you are building full-stack applications
where the pages are rendered on the server,
and where you use the file system to set up routes.
That's always the case,
but the Pages Router is the older way of doing that.
This approach has been around for many years,
and it's a very stable approach.
And indeed, I cover it in depth in this course
because it's very stable
and because it's used in many projects.
Now, as mentioned with this approach, with the Pages Router,
you build feature-rich, full-stack apps
with React and NextJS.
So, that's the case with this approach as well.
But we then also have that other approach, the App Router,
which is a relatively new way of building NextJS apps.
It was introduced with NextJS 13, so not too long ago,
and it is now an approach that is marked as stable
but still relatively new,
and at least in my experience, also partially still buggy.
Nonetheless, it's the most modern way
of building NextJS apps,
unlocking many amazing modern new features
like React Server components or Server Actions,
which are features I'll explain in greater detail
throughout this course, of course.
Therefore, it's the future of NextJS,
and that's why in this course I of course also cover that.
I simply cover both approaches.
But we'll start with the App Router
after this React.js refresher section
before we then take a close look
at the Pages Router thereafter,
so that by the end of the course
you know about both approaches
and you are ready to work on any NextJS project,
no matter which approach that project is using.