Backend customization: An examples cookbook using FoodAdvisor
The content of this page might not be fully up-to-date with Strapi 5 yet.
The present section of the documentation is intended for developers who would like to get a deeper understanding of the Strapi back end customization possibilities.
The section is a collection of examples that demonstrate how the core components of the back-end server of Strapi can be used in a real-world project. Front-end code that interacts with the back end may also be part of some examples, but displayed in collapsed blocks by default since front-end code examples are not the main focus of this cookbook.
Examples are meant to extend the features of FoodAdvisor, the official Strapi demo application. FoodAdvisor builds a ready-made restaurants directory powered by a Strapi back end (included in the /api
folder) and renders a Next.js-powered front-end website (included in the /client
folder).
- 👀 You have read the Quick Start Guide and/or understood that Strapi is a headless CMS that helps you create a content structure with the Content-Type Builder and add some content through the Content Manager, then exposes the content through APIs.
- 👀 You have read the back-end customization introduction to get a general understanding of what routes, policies, middlewares, controllers, and services are in Strapi.