building a Complete Jamstack Application with Next.js and Strapi CMS”.png

jamstack.tar.gz

github_name

github_email

github_access_token

Next_base

next_user_build

github

next_build

strapi_prebuild_base

fullstack

Jamstack proposes an architecture for creating flexible, secure, and performance-efficient web applications. This course follows a tutorial-based approach, through which you will learn how to build a complete Jamstack application with Next.js and Strapi.

This course will introduce you to Jamstack and how it differs from standard web applications. you will then learn about Next.js and how to create static websites. Along the way, you will create a Recipes application with a list of recipes available through TheMealDB API. You will also integrate Strapi as a headless CMS, enabling you to authenticate users and allow them to save their favorite recipes. You will conclude the course by working on a project where you will be using Strapi and Next.js to authenticate users and allow them to create, retrieve, update, and delete notes for themselves.

By the end of this course, you will have a thorough command of Strapi and Next.js to create flexible, secure, and performance-efficient web applications.

Building a Jamstack Application with Next.js and Strapi CMS

Because they don’t have any front-end technology related to it.

Because they provide a complete web development package.

Why are some CMS called “headless” CMS?

**(Select all that apply.)** Which option is a content-type in Strapi?

(Select all that apply.) Which option is a content-type in Strapi?

We can define any relationship between any two content-types. 

We can only define one-way relationships between single types, that is, content-type A has one content-type B.

We can only define one-to-one relationships between single types, that is, content-type A has and belongs to one content-type B.

Which statement about relational fields in Strapi is correct? 

Which statement about relational fields in Strapi is correct?

It can be anywhere in the project directory. The exact path doesn't matter because the endpoints are also automatically generated.

This folder is created in the `/api` subfolder, under the content-types folder.

We learned that, whenever we create a collection type in our Content-type Builder, Strapi automatically generates a folder with the name of that collection. What is that's folder's path? 

We learned that, whenever we create a collection type in our Content-type Builder, Strapi automatically generates a folder with the name of that collection. What is that’s folder’s path?

The name of the file is always `schema.json`.

It contains all the information Strapi requires about the content that is saved in this content-type.

If needed, we can directly edit the file without having to use the Strapi admin panel.

We learned that Strapi automatically generates a folder with the name of the user-created collection type. It also creates some subfolders, including the `content-types` folder with a file named `schema.json`.  Based on this, which statement is true? 

We learned that Strapi automatically generates a folder with the name of the user-created collection type. It also creates some subfolders, including the <code>content-types</code> folder with a file named <code>schema.json</code>. Based on this, which statement is true?

The `create` route: This is a `POST` route with the path `/api/:pluralApiId`. It creates a new entry in the collection.


The `update` route: This is a `PUT` route with the path `/api/:pluralApiId/:id`. It updates the entry that has the ID mentioned in the route.


The `findOne` route: This is a `GET` route, with the path  `/api/:pluralApiId/:id`. It gets the entry that has the ID mention in the route.


The `delete` route: This is a `DELETE` route with the path `/api/:pluralApiId/:id`. It deletes the entry that has the ID mentioned in the route.

We learned that Strapi automatically generates a folder with the name of user-created collection type. It also creates some subfolders, including the `routes` folder.  Which option below is one of the default routes? 


We learned that Strapi automatically generates a folder with the name of user-created collection type. It also creates some subfolders, including the <code>routes</code> folder. Which option below is one of the default routes?

Each route is assigned to a controller function, which are called actions.

Strapi automatically generates the controller functions for the automatically generated routes.

We can't override the already existing functions to change the controller functions of the default routes.

We learned that Strapi automatically generates a folder with the name of user-created collection type. It also creates some subfolders, including the `controllers` folder.  Which statement is true for Strapi controllers?

We learned that Strapi automatically generates a folder with the name of user-created collection type. It also creates some subfolders, including the <code>controllers</code> folder. Which statement is true for Strapi controllers?

Introduction

Getting Started with Jamstack

Basics of Next.js

Static Site Generation with Next.js

Using Strapi as a Headless CMS

Building the Complete Application

Project: Notes Application

Conclusion

Quiz: Using Strapi as a Headless CMS