Exploring the Strapi plugin ecosystem
Strapi aims to be easy to use and flexible to extend. As we saw repeatedly in the previous chapters, it's very easy to build an API for the default create, read, update, and delete (CRUD) operations, but we are not locked into the default behavior—it's always possible to extend the default behavior for our API in any way we want. That philosophy goes beyond building and coding APIs and their interactions, to almost every aspect of Strapi and its admin panel.
To achieve such flexibility, Strapi builds heavily on a plugin's architecture to open possibilities for infinite use cases beyond the core functionality.
What is a plugin in Strapi?
In the admin panel, if we navigate to Plugins under General in the main menu, we will see that there are a few plugins already installed. We have already interacted with most of these, and more detail on these is provided here:
- Content Manager: This is where we edit our classroom...
