Next.js: Creating and Hosting a Full-Stack Site

This is the repository for the LinkedIn Learning course Next.js: Creating and Hosting a Full-Stack Site. The full course is available from LinkedIn Learning.

Course Description

Many web developers focus solely on one part of an application: the front end, the back end, the database, or the hosting platform. However, JavaScript has become such a pervasive language that it can be used for all of these parts. This means that a single JavaScript developer can now create an entire web application, a task that used to require an entire team. In this course, full-stack development instructor Shaun Wassell shows developers how to do exactly that by using Next.js to build a full-stack application. Find out how to build basic React interfaces in Next.js, add back-end functionality to Next.js applications, make network requests, and finally host a full-stack Next.js application so that anyone can use it.

See the readme file in the main branch for updated instructions and information.

Instructions

This repository has branches for each of the videos in the course. You can use the branch pop up menu in github to switch to a specific branch and take a look at the course at that stage, or you can add /tree/BRANCH_NAME to the URL to go to the branch you want to access.

Branches

The branches are structured to correspond to the videos in the course. The naming convention is CHAPTER#_MOVIE#. As an example, the branch named 02_03 corresponds to the second chapter and the third video in that chapter. Some branches will have a beginning and an end state. These are marked with the letters b for "beginning" and e for "end". The b branch contains the code as it is at the beginning of the movie. The e branch contains the code as it is at the end of the movie. The main branch holds the final state of the code when in the course.

When switching from one exercise files branch to the next after making changes to the files, you may get a message like this:

error: Your local changes to the following files would be overwritten by checkout:        [files]
Please commit your changes or stash them before you switch branches.
Aborting

To resolve this issue:

Add changes to git using this command: git add .
Commit changes using this command: git commit -m "some message"

Instructor

Shaun Wassell

Senior Software Engineer, Educator at CBT Nuggets

Check out my other courses on LinkedIn Learning.