19 docs tagged with "Content-type Builder"

Instructions to add assets to the Media Library

All elements of Strapi's back end, like routes, policies, middlewares, controllers, services, models, requests, responses, and webhooks, can be customized.

The Content-type Builder is only accessible to create and update content-types when your Strapi application is in a development environment, else it will be in a read-only mode in other environments.

The Content-type Builder is only accessible to create and update content-types when your Strapi application is in a development environment, else it will be in a read-only mode in other environments.

Learn how you can use custom fields to extend Strapi's content-types capabilities.

Strapi includes 2 main components:

Strapi is built around different types of plugins. Every default Strapi application comes with the following pre-installed plugins:

Introduction to the Content Manager which allows to write content for collection types and single types.

The Content-type Builder is a core plugin of Strapi. It is a feature that is always activated by default and cannot be deactivated. The Content-type Builder is however only accessible when the application is in a development environment.

Introduction to the Media Library which allows to display and manage all assets uploaded in the application.

Learn how to manager your content-types in Strapi 5

Instructions on how to manage assets uploaded to the Media Library, including editing, moving, and deleting assets, and cropping images.

Instructions to manage relation-type fields, called "relational fields", which establish a relation between two content-types.

Strapi models (i.e. content-types, components, and dynamic zones) define a representation of the data structure.

Instructions on how to use folders in the Media Library, including adding, editing, and deleting folders, and browsing their content.

Get ready to get Strapi, your favorite open-source headless cms up and running in less than 3 minutes.

Instructions to manage content throughout its whole lifecycle, from the draft version to the deletion of the obsolete content.

Instructions to translate content in various locales with i18n plugin.

Instructions to write content by filling up fields that are meant to contain specific content (e.g. text, numbers, media etc.).