This week we’re super excited to share the v4 documentation, available at docs.strapi.io
- The back-end customization section has been fully rewritten to reflect all the changes to routes, policies, middlewares, controllers, services, and models in v4.
- The plugin APIs reference section includes:
- The brand new plugins extension and plugins development sections will guide you through v4 plugins customization and creation.
- The Query Engine API allows you to interact with the database layer at a lower level.
- The Entity Service API handles components and dynamic zones and uses the Query Engine API under the hood to execute database queries.
- The GraphQL API offers new sorting, filtering, and pagination possibilities.
- API tokens can now be used to authenticate queries.
- Error handling is now natively supported so you can send and receive errors in a standard format.
- The admin panel customization section has been restructured to give a better view of the possible customization options.
- The REST API has a new response format and is now much more powerful. It includes the ability to sort, filter, and paginate results as well as select fields and populate relations.
- The GraphQL plugin now offers new customization features, with getters and setters offering more granular control at the content-types and field levels while resolvers can be customized with policies and middlewares.
- The configurations section has been simplified. Middlewares configuration is now required and the server and admin panel configurations are now handled by 2 different files.
- The project structure has been updated to reflect the structure of v4 projects.
Since we will now be actively maintaining Strapi v4 documentation, v3 documentation will only be updated for critical issues as long as Strapi v3 is officially maintained (i.e. for the next 6 months).
Note also that some parts of the v4 documentation might not be up-to-date yet, such as integration and deployment guides — community contributions to help us would be highly appreciated . In the meantime, we are also actively working on the v3 to v4 migration guide. We will keep you posted!
We hope you will enjoy this brand new documentation and are looking forward to your feedback