Before we continue developing
our first Next.js app,
I want to quickly show you where you can
find the source code for this project.
This will be useful if you have
any problems with your own code
while following along with the videos.
Under the Resources for this lecture,
you'll find a link to the GitHub repository,
that contains all the code for
the Next Reviews example.
Now, what you see on this page
is the "main" branch;
this contains the final code.
It includes everythingÂ that's covered in
the next several sections of the course.
But most of the time you'll want to check
what the code should be at the end
of a specific lecture instead.
You can see the changes made in each video
by clicking this "commits" link.
This page shows all the changes
made at every step,
and I pushed a separate commit
for each video in the course,
with the lecture title as the commit message.
Note that this list is in reverse
chronological order,
so the first change we made
will be the oldest entry.
You can see that it says "Creating
a Next.js Project".
If we go back to the previous page,
the second commit says "Home Page", and so on.
Each commit message is the same
as the title of the video where
I made those changes.
"Creating a Next.js Project" was the
first lecture in this section,
"Home Page" the second, and so on.
Now, to make it really easy for
you to find the right code,
I've added a link under the
Resources for each lecture.
So if you open the "Diff" for the "Home Page",
this will show you the changes
made in the previous video.
The diff shows which files we changed,
and for each file, exactly
which lines we modified.
There's also a "Split" view,
that shows the code before and after,
side by side.
You can choose whichever view you prefer.
The important thing is that you
can use this diff to check
if you made all the right
changes to your own code.
Now, sometimes instead of the differences,
you may want to see the full file contents.
You can do that by clicking
this "Browse files" button,
that shows the repository at
this point in the history.
Note that, instead of the "main" branch
this page now displays a specific commit ID,
and you can also see the last commit message here.
So, if you want to see the full code
for the HomePage for example,
you can simply open "page.jsx",
and here you'll see the full file,
that you may want to copy into your own project.
You can also download all the
files to your machine,
by selecting Download ZIP here,
or using the Git command line tool
if you're familiar with it.
So you have a few ways to check
your code against mine,
in case something is not working
in your own project.
If you cannot solve the problem
by looking at the code,
please check the "Q&A" tab in the course.
Maybe a similar issue was discussed before,
and from time to time I also post updates here,
like if there's a new version of some library
and the code needs to be slightly different.
You can search all questions by typing a keyword,
and you'll see any results here.
If you don't find anything, you
can always ask a new question,
selecting "Course content",
and here you can post a new message.
Please make sure to write a descriptive title,
and provide as many details as possible.
You can add screenshots with this button,
and also format code by clicking this other icon.
Keep in mind that I'm not always
available to answer immediately;
among other things, we may be
in different time zones,
so if it's afternoon for you
when you post something
it may be the middle of the night for me,
which means I'll only see your question
the following morning.
The more details you give me, and
the more likely it is that
I'll be able to give you a solution
in the first reply.
If I have to ask you for more information,
the back and forth will just take longer.
That's also why I provide this Github repository:
so you can easily check all the code for yourself,
without having to wait for me to reply.