Add callout to gather feedback for all backend custom. pages (#1661)

Author: pwizla

docusaurus/docs/dev-docs/backend-customization.md

@@ -4,13 +4,13 @@ description: All elements of Strapi's back end, like routes, policies, middlewar
 
 ---
 
+import FeedbackCallout from '/docs/snippets/backend-customization-feedback-cta.md'
+
 # Back-end customization
 
-Strapi runs an HTTP server based on [Koa](https://koajs.com/), a back end JavaScript framework.
+<FeedbackCallout components={props.components}/>
 
-:::strapi What is Koa?
-If you are not familiar with the Koa back end framework, we highly recommend you to read the [Koa's documentation introduction](http://koajs.com/#introduction).
-:::
+Strapi runs an HTTP server based on [Koa](https://koajs.com/), a back end JavaScript framework. If you are not familiar with the Koa back end framework, we highly recommend you to read the [Koa's documentation introduction](http://koajs.com/#introduction).
 
 Each part of Strapi's back end can be customized:
 

docusaurus/docs/dev-docs/backend-customization/controllers.md

@@ -1,5 +1,9 @@
+import FeedbackCallout from '/docs/snippets/backend-customization-feedback-cta.md'
+
 # Controllers
 
+<FeedbackCallout components={props.components}/>
+
 Controllers are JavaScript files that contain a set of methods, called actions, reached by the client according to the requested [route](/dev-docs/backend-customization/routes). Whenever a client requests the route, the action performs the business logic code and sends back the [response](/dev-docs/backend-customization/requests-responses). Controllers represent the C in the model-view-controller (MVC) pattern.
 
 In most cases, the controllers will contain the bulk of a project's business logic. But as a controller's logic becomes more and more complicated, it's a good practice to use [services](/dev-docs/backend-customization/services) to organize the code into re-usable parts.

docusaurus/docs/dev-docs/backend-customization/middlewares.md

@@ -2,8 +2,12 @@
 title: Middlewares
 ---
 
+import FeedbackCallout from '/docs/snippets/backend-customization-feedback-cta.md'
+
 # Middlewares customization
 
+<FeedbackCallout components={props.components}/>
+
 :::strapi Different types of middlewares
 
 In Strapi, 2 middleware concepts coexist:

docusaurus/docs/dev-docs/backend-customization/models.md

@@ -25,8 +25,12 @@ sidebarDepth: 3
 
 ---
 
+import FeedbackCallout from '/docs/snippets/backend-customization-feedback-cta.md'
+
 # Models
 
+<FeedbackCallout components={props.components}/>
+
 As Strapi is a headless Content Management System (CMS), creating a data structure for the content is one of the most important aspects of using the software. Models define a representation of the data structure.
 
 There are 2 different types of models in Strapi:

docusaurus/docs/dev-docs/backend-customization/policies.md

@@ -5,8 +5,12 @@ displayed_sidebar: devDocsSidebar
 
 ---
 
+import FeedbackCallout from '/docs/snippets/backend-customization-feedback-cta.md'
+
 # Policies
 
+<FeedbackCallout components={props.components}/>
+
 Policies are functions that execute specific logic on each request before it reaches the [controller](/dev-docs/backend-customization/controllers). They are mostly used for securing business logic.
 
 Each [route](/dev-docs/backend-customization/routes) of a Strapi project can be associated to an array of policies. For example, a policy named `is-admin` could check that the request is sent by an admin user, and restrict access to critical routes.

docusaurus/docs/dev-docs/backend-customization/requests-responses.md

@@ -4,8 +4,12 @@ description: Learn more about requests and responses for Strapi, the most popula
 
 ---
 
+import FeedbackCallout from '/docs/snippets/backend-customization-feedback-cta.md'
+
 # Requests & Responses
 
+<FeedbackCallout components={props.components}/>
+
 ## Requests
 
 The context object (`ctx`) contains all the requests related information. They are accessible through `ctx.request`, from [controllers](/dev-docs/backend-customization/controllers.md) and [policies](/dev-docs/backend-customization/policies.md).

docusaurus/docs/dev-docs/backend-customization/routes.md

@@ -4,8 +4,12 @@ description: Strapi routes handle requests to your content and are auto-generate
 displayed_sidebar: devDocsSidebar
 ---
 
+import FeedbackCallout from '/docs/snippets/backend-customization-feedback-cta.md'
+
 # Routes
 
+<FeedbackCallout components={props.components}/>
+
 Requests sent to Strapi on any URL are handled by routes. By default, Strapi generates routes for all the content-types (see [REST API documentation](/dev-docs/api/rest)). Routes can be [added](#implementation) and configured:
 
 - with [policies](#policies), which are a way to block access to a route,

docusaurus/docs/dev-docs/backend-customization/services.md

@@ -5,8 +5,12 @@ displayed_sidebar: devDocsSidebar
 
 ---
 
+import FeedbackCallout from '/docs/snippets/backend-customization-feedback-cta.md'
+
 # Services
 
+<FeedbackCallout components={props.components}/>
+
 Services are a set of reusable functions. They are particularly useful to respect the "don’t repeat yourself" (DRY) programming concept and to simplify [controllers](/dev-docs/backend-customization/controllers.md) logic.
 
 ## Implementation

docusaurus/docs/dev-docs/backend-customization/webhooks.md

@@ -5,8 +5,12 @@ description: Strapi webhooks are user-defined HTTP callbacks used by an applicat
 
 ---
 
+import FeedbackCallout from '/docs/snippets/backend-customization-feedback-cta.md'
+
 # Webhooks
 
+<FeedbackCallout components={props.components}/>
+
 Webhook is a construct used by an application to notify other applications that an event occurred. More precisely, webhook is a user-defined HTTP callback. Using a webhook is a good way to tell third party providers to start some processing (CI, build, deployment ...).
 
 The way a webhook works is by delivering information to a receiving application through HTTP requests (typically POST requests).

docusaurus/docs/snippets/backend-customization-feedback-cta.md

@@ -0,0 +1,3 @@
+:::callout 💬 Strapi team needs you to improve this documentation!
+We are currently reworking the Backend Customization section of the Strapi documentation. If you would like to help, please feel free to fill in [this form](https://forms.gle/YS8zGUrG6FQ72dmh8) to share with us your opinions, needs and requests.
+:::