The Complete Strapi™ Course with Plugins and Deployment - Premium Posts: Introduction

The video tutorial discusses implementing a premium posts feature in Strappy. It covers creating a boolean field to mark posts as premium, ensuring only authenticated users can access them. The tutorial emphasizes using existing Strappy features to minimize new code and maintain modular architecture. It also highlights the importance of handling logic on the server side to keep client requests simple. Finally, it demonstrates creating and configuring the premium field in the admin panel.

What is the purpose of adding a premium boolean field to posts?

• To track the number of views on a post

• To differentiate between public and premium content

• To enable comments on posts

• To categorize posts based on their length

Why is it important to respect the architectural principles of Strappy?

• To reduce the number of developers needed

• To maintain code simplicity and leverage existing features

• To increase the number of features in the application

• To ensure the application runs faster

What is the advantage of keeping the premium posts logic on the backend?

• It simplifies the client-side code

• It allows for more complex client-side logic

• It increases the number of API calls

• It reduces server load

How can you determine if a request is authenticated in Strappy?

• By creating a new endpoint

• By checking the request headers

• By using a custom policy

• By examining the CTX.state.user object

Why is it unnecessary to create a new route for premium posts?

• Because it would complicate the database schema

• Because new routes are not supported

• Because the existing route can be leveraged

• Because it would require too much server space

What is the default value for the premium field when a new post is created?

• True

• False

• Undefined

• Null

What should be done to existing posts when a new premium field is added?

• They should be deleted

• They should be archived

• They should be left unchanged

• They should be updated to include the premium field