Learning Next.js

This is the repository for the LinkedIn Learning course Learning Next.js. The full course is available from LinkedIn Learning.

Next.js is a React framework developed by developers for developers, to create high-quality, responsive web applications. With built-in tools and ready-to-use features, Next.js makes the development process painless and a breeze. In this course, web developer and trainer Sandy Ludosky teaches you how to leverage the Next.js framework to speed up and improve your workflow, whether you are a front- or back-end developer. Find out how to build and deploy a fully functional web application. Explore ways to leverage and improve the developer experience. Plus, go over practical examples and complete a course project to help you practice what you’ve learned. This course can help you get to the next level with Next.js.

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

Sandy Ludosky

Web Developer and Trainer

Check out my other courses on LinkedIn Learning.