# Strapi Documentation

- [Account billing details](https://docs.strapi.io/cloud/account/account-billing): Billing details and invoices are managed on the Profile page, where payment methods are updated and invoice history is available.
- [Profile settings](https://docs.strapi.io/cloud/account/account-settings): Settings of the Profile page include account details, connected accounts, and account deletion options.
- [Database](https://docs.strapi.io/cloud/advanced/database): Default PostgreSQL can be swapped for any supported SQL database by aligning configuration and environment variables.
- [Email Provider](https://docs.strapi.io/cloud/advanced/email): Third‑party email services integrate through plugins and environment variables to replace the default sender.
- [Upload Provider Configuration for Strapi Cloud](https://docs.strapi.io/cloud/advanced/upload): External storage like S3 or Cloudinary requires plugin setup, security middleware, and Cloud variables.
- [Command Line Interface (CLI)](https://docs.strapi.io/cloud/cli/cloud-cli): CLI commands handle login, project deploy, linking, listing, and logout without needing a remote repository.
- [Caching & Performance](https://docs.strapi.io/cloud/getting-started/caching): Edge caching via Cache-Control headers reduces latency and server load for heavy static content.
- [Strapi Cloud の基礎](https://docs.strapi.io/cloud/getting-started/cloud-fundamentals): Strapi Cloud のドキュメントを読み進む前に、ここで紹介する主要な概念を押さえておくことをおすすめします。Strapi Cloud の仕組みの理解とスムーズな利用に役立ちます。
- [Strapi Cloud - ダッシュボードからのデプロイ](https://docs.strapi.io/cloud/getting-started/deployment): Strapi Cloud へ Strapi アプリケーションをデプロイする手順です。
- [Strapi Cloud - CLI deployment](https://docs.strapi.io/cloud/getting-started/deployment-cli): Learn how to deploy your Strapi application via the CLI.
- [Project deployment](https://docs.strapi.io/cloud/getting-started/deployment-options): Learn how to deploy your Strapi application on Strapi Cloud, via the Cloud dashboard or the CLI.
- [Strapi Cloud ドキュメントへようこそ](https://docs.strapi.io/cloud/getting-started/intro): Strapi Cloud ドキュメントには、Strapi Cloud アカウントとアプリケーションのセットアップ、デプロイ、更新、カスタマイズに関する技術ドキュメントが含まれます。
- [請求と利用に関する情報](https://docs.strapi.io/cloud/getting-started/usage-billing): Strapi Cloud アカウントとプロジェクトの利用・請求に関する概要です。
- [Collaboration](https://docs.strapi.io/cloud/projects/collaboration): Project owners invite maintainers through the Share button, manage pending invitations, and revoke access.
- [Deployments management](https://docs.strapi.io/cloud/projects/deploys): Deployment triggers can be manual or automatic on git pushes, with the ability to cancel active builds from dashboard or CLI.
- [Deployment history & logs](https://docs.strapi.io/cloud/projects/deploys-history): Deployments tab lists every build with status and allows deep inspection of build and runtime logs.
- [Notifications](https://docs.strapi.io/cloud/projects/notifications): Bell icon opens a feed of recent deployment events, automatically purged after 30 days.
- [プロジェクトの概要](https://docs.strapi.io/cloud/projects/overview): プロジェクト一覧では各アプリの状態とクイック操作が分かります。カードを選ぶとメトリクスと操作付きのダッシュボードが開きます。
- [Runtime logs](https://docs.strapi.io/cloud/projects/runtime-logs): Runtime logs tab streams live server output, though Free plan logs reset when apps scale to zero.
- [Project settings](https://docs.strapi.io/cloud/projects/settings): Settings area spans project-level controls (general, billing, plans, invoices) and per-environment configuration.
- [Admin panel customization](https://docs.strapi.io/cms/admin-panel-customization): The admin panel can be tailored to match your branding, by editing src/admin/app and using an extensions folder to swap logos, favicon, locales, translations, themes, bundlers, or editors.
- [Admin panel bundlers](https://docs.strapi.io/cms/admin-panel-customization/bundlers): Supported JavaScript bundlers influence builds and development flow.
- [Admin panel extension](https://docs.strapi.io/cms/admin-panel-customization/extension): Learn more about extending Strapi's admin panel.
- [Favicon](https://docs.strapi.io/cms/admin-panel-customization/favicon): Replace the favicon displayed in Strapi's admin panel.
- [Homepage customization](https://docs.strapi.io/cms/admin-panel-customization/homepage): The admin panel homepage displays default content and profile widgets and supports custom additions through the app.widgets.register API.
- [Locales & translations](https://docs.strapi.io/cms/admin-panel-customization/locales-translations): Configure the admin panel languages by updating the config.locales array and override default or plugin strings with config.translations or custom translation files.
- [Logos](https://docs.strapi.io/cms/admin-panel-customization/logos): Update login and navigation logos by extending the admin app. Prefer SVG for crisp rendering; provide light/dark variants when possible for contrast.
- [Theme extension](https://docs.strapi.io/cms/admin-panel-customization/theme-extension): Extend Strapi's admin panel theme.
- [Customizing the rich text editor](https://docs.strapi.io/cms/admin-panel-customization/wysiwyg-editor): Learn more about the various strategies available to customize the WYSIWYG editor in Strapi's admin panel.
- [Strapi Client](https://docs.strapi.io/cms/api/client): The Strapi Client library simplifies interactions with your Strapi back end, providing a way to fetch, create, update, and delete content.
- [Content API](https://docs.strapi.io/cms/api/content-api): Strapi 5 の Content API について説明します
- [Documents](https://docs.strapi.io/cms/api/document): Strapi v5 における Document 概念を説明します
- [Document Service API](https://docs.strapi.io/cms/api/document-service): The Document Service API is the recommended way to interact with your content from the back-end server or from plugins.
- [Using fields with the Document Service API](https://docs.strapi.io/cms/api/document-service/fields): Use Strapi's Document Service API to select the fields to return with your queries.
- [Using filters with the Document Service API](https://docs.strapi.io/cms/api/document-service/filters): This document provides information about the filters available in the Document Service API.
- [Using the locale parameter with the Document Service API](https://docs.strapi.io/cms/api/document-service/locale): Use Strapi's Document Service API to work with locale versions with your queries.
- [Extending the Document Service behavior](https://docs.strapi.io/cms/api/document-service/middlewares): This document provides information about the middlewares in the Document Service API.
- [Using Populate with the Document Service API](https://docs.strapi.io/cms/api/document-service/populate): Use Strapi's Document Service API to populate or select some fields.
- [Using Sort & Pagination with the Document Service API](https://docs.strapi.io/cms/api/document-service/sort-pagination): Use Strapi's Document Service API to sort and paginate query results
- [Using Draft & Publish with the Document Service API](https://docs.strapi.io/cms/api/document-service/status): Use Strapi's Document Service API to return either the draft or the published version of a document
- [GraphQL API](https://docs.strapi.io/cms/api/graphql): import DeepFilteringBlogLink from '/docs/snippets/deep-filtering-blog.md'
- [OpenAPI specification](https://docs.strapi.io/cms/api/openapi): Learn how to generate OpenAPI specifications for your Strapi applications using the @strapi/openapi package
- [REST API reference](https://docs.strapi.io/cms/api/rest): Interact with your Content-Types using the REST API endpoints Strapi generates for you.
- [Filters](https://docs.strapi.io/cms/api/rest/filters): Use Strapi's REST API to filter the results of your requests.
- [REST API Guides](https://docs.strapi.io/cms/api/rest/guides/intro): Deep dive into some specific REST API topics using guides that extensively explain some use cases or give step-by-step instructions.
- [Interactive Query Builder](https://docs.strapi.io/cms/api/rest/interactive-query-builder): Use an interactive tool that leverages the querystring library to build your query URL
- [Locale](https://docs.strapi.io/cms/api/rest/locale): Browse the REST API reference for the locale parameter to take advantage of the Internationalization feature through REST.
- [Parameters](https://docs.strapi.io/cms/api/rest/parameters): Use API parameters to refine your Strapi REST API queries.
- [Populate and Select](https://docs.strapi.io/cms/api/rest/populate-select): Use the populate parameter to include relations, media fields, components, and dynamic zones in REST API responses. Use the fields parameter to return only specific fields.
- [Relations](https://docs.strapi.io/cms/api/rest/relations): Use the REST API to manage the order of relations
- [Sort and Pagination](https://docs.strapi.io/cms/api/rest/sort-pagination): Use Strapi's REST API to sort or paginate your data.
- [Status](https://docs.strapi.io/cms/api/rest/status): Use Strapi's REST API to work with draft or published versions of your documents.
- [Upload files](https://docs.strapi.io/cms/api/rest/upload): Learn how to use the /api/upload endpoints to upload files to Strapi with the REST API.
- [Back-end customization](https://docs.strapi.io/cms/backend-customization): Strapi’s back end is a Koa-based server where requests pass through global middlewares, routes, controllers, services, and models before the Document Service returns responses.
- [Controllers](https://docs.strapi.io/cms/backend-customization/controllers): Controllers bundle actions that handle business logic for each route within Strapi’s MVC pattern. This documentation demonstrates generating controllers, extending core ones with createCoreController, and delegating heavy logic to services.
- [Middlewares](https://docs.strapi.io/cms/backend-customization/middlewares): Middlewares alter the request or response flow at application or API levels. This documentation distinguishes global versus route middlewares and illustrates custom implementations with generation patterns.
- [Models](https://docs.strapi.io/cms/backend-customization/models): Models define Strapi’s content structure via content-types and reusable components. This documentation walks through creating these models in the Content-type Builder or CLI and managing schema files with optional lifecycle hooks.
- [Policies](https://docs.strapi.io/cms/backend-customization/policies): Policies execute before controllers to enforce authorization or other checks on routes. Instructions in this documentation cover generating global or scoped policies and wiring them into router configs.
- [Requests and Responses](https://docs.strapi.io/cms/backend-customization/requests-responses): Koa’s context (ctx) carries request info, state, and response data through every Strapi endpoint. This documentation details ctx.request, ctx.state, and ctx.response, plus a helper for accessing context anywhere.
- [Routes](https://docs.strapi.io/cms/backend-customization/routes): Routes map incoming URLs to controllers and ship pre-generated for each content type. This documentation shows how to add or customize core and custom routers and attach policies or middlewares for extra control.
- [Services](https://docs.strapi.io/cms/backend-customization/services): Services store reusable functions to keep controllers concise and follow DRY principles. This documentation explains generating or extending services with createCoreService and organizing them for APIs or plugins.
- [Webhooks](https://docs.strapi.io/cms/backend-customization/webhooks): Webhooks let Strapi notify external systems when content changes, while omitting the Users type for privacy. Configuration in config/server sets default headers and endpoints to trigger third-party processing.
- [Command Line Interface](https://docs.strapi.io/cms/cli): Strapi comes with a full featured Command Line Interface (CLI) which lets you scaffold and manage your project in seconds.
- [Configurations](https://docs.strapi.io/cms/configurations): Learn how you can manage and customize the configuration of your Strapi application.
- [API calls configuration](https://docs.strapi.io/cms/configurations/api): /config/api centralizes response privacy, REST defaults (prefix, pagination limits, max request size), and strict parameter validation for both the REST Content API and the Document Service.
- [CRON jobs](https://docs.strapi.io/cms/configurations/cron): Cron jobs schedule custom functions at specific times via node-schedule, activated through server config and optional task files.
- [Database configuration](https://docs.strapi.io/cms/configurations/database): /config/database defines connections, clients, and pooling for supported databases like SQLite, MySQL, and PostgreSQL.
- [Environment variables configuration](https://docs.strapi.io/cms/configurations/environment): Strapi-specific environment variables and .env usage enable per-environment configs, with env() helpers for casting values.
- [Features configuration](https://docs.strapi.io/cms/configurations/features): Future flags in /config/features toggle experimental Strapi features, allowing early testing at your own risk.
- [Lifecycle functions](https://docs.strapi.io/cms/configurations/functions): src/index hosts global register, bootstrap, and destroy functions to run logic during application lifecycle.
- [Middlewares configuration](https://docs.strapi.io/cms/configurations/middlewares): /config/middlewares orders global middleware, enables custom names or resolves, and exposes built-in configuration options.
- [Plugins configuration](https://docs.strapi.io/cms/configurations/plugins): /config/plugins enables or disables plugins and overrides their settings, with examples for local plugin development.
- [Server configuration](https://docs.strapi.io/cms/configurations/server): /config/server manages host, port, URL, proxy, cron, and more; changes require rebuilding the admin panel.
- [TypeScript configuration](https://docs.strapi.io/cms/configurations/typescript): TypeScript configuration explains the project’s tsconfig files, output directories, and an optional config/typescript.js|ts that auto-generates types on server restart. This documentation explains which folders store compiled code and how to toggle this experimental feature.
- [カスタマイズ](https://docs.strapi.io/cms/customization): Strapi 5 でできるカスタマイズの概要です。
- [Database migrations](https://docs.strapi.io/cms/database-migrations): Database migrations run one‑time scripts before schema sync to preserve data during upgrades. The experimental API uses alphabetical up() files and warns about missing down migrations and potential table deletions.
- [Database transactions](https://docs.strapi.io/cms/database-transactions): Database transactions group several operations so they succeed or roll back as a unit. The experimental strapi.db.transaction helper exposes trx, commit, and rollback utilities for wrapped service calls.
- [デプロイ](https://docs.strapi.io/cms/deployment): デプロイにはハード／ソフト要件、環境変数の設定、公開前の管理パネルのビルドが含まれます。ドキュメントにはプロバイダー別・高度な手順へのリンクがあり、ホスティング戦略の選択に役立ちます。
- [Error handling](https://docs.strapi.io/cms/error-handling): Strapi’s APIs return errors in a consistent structure and let backend code throw custom exceptions for controllers, services, policies, or lifecycles. This documentation lists error classes, context helpers, and examples for crafting meaningful responses.
- [管理パネル](https://docs.strapi.io/cms/features/admin-panel): 管理パネルは Strapi のバックオフィスとして、コンテンツタイプやエントリー、管理者・エンドユーザーのアカウントを扱います。本ページでは概要のあと、インターフェース言語・モード、ログインとプロフィール情報、ブランド用ロゴなどプロフィール周りに焦点を当てます。
- [API トークン（API Tokens）](https://docs.strapi.io/cms/features/api-tokens): API トークンを使うと、ユーザー資格情報を露出せずに REST / GraphQL リクエストをスコープ付きで認証できます。このページでは、トークン種別、作成、期限、管理パネルでの安全な運用を説明します。
- [監査ログ（Audit Logs）](https://docs.strapi.io/cms/features/audit-logs): Audit Logs は、管理操作を検索・絞り込み可能な履歴として記録し、障害調査やコンプライアンス対応を支援します。このページでは、Payload の確認やユーザー／日付での絞り込み方法を説明します。
- [コンテンツ履歴（Content History）](https://docs.strapi.io/cms/features/content-history): Content History はドキュメントの過去バージョンを保存し、編集者がコンテンツマネージャー上で比較・復元できるようにします。このページでは、誤編集時に素早くロールバックするための参照・復元手順を説明します。
- [コンテンツマネージャー](https://docs.strapi.io/cms/features/content-manager): コンテンツマネージャーは Strapi でエントリーを閲覧・編集する画面です。概要に加え、各ビューやフィールド、コンポーネント、ダイナミックゾーン、リレーションフィールドでのコンテンツの書き方を説明します。
- [コンテンツタイプビルダー](https://docs.strapi.io/cms/features/content-type-builder): コンテンツタイプビルダーは、コンテンツタイプとコンポーネントを設計するためのツールです。概要に加え、フィールドの選択肢、リレーション、コンポーネントの使い方、データモデリングのヒントを扱います。
- [カスタムフィールド（Custom Fields）](https://docs.strapi.io/cms/features/custom-fields): カスタムフィールドは、コンテンツタイプビルダーとコンテンツマネージャーでネイティブフィールドと同様に振る舞う新しいフィールド型を Strapi に足します。このページではプラグインでの導入・自作と、プログラムからの登録方法を説明します。
- [データ管理（Data Management）](https://docs.strapi.io/cms/features/data-management): Data Management は、Strapi インスタンス間のコンテンツのインポート、エクスポート、転送を CLI で行う機能です（管理パネル側に一部設定あり）。このページでは、安全に移行するための前提設定と操作を説明します。
- [下書きと公開（Draft & Publish）](https://docs.strapi.io/cms/features/draft-and-publish): Draft & Publish は下書きと公開版を分け、公開前にコンテンツを整えられます。コンテンツタイプごとの有効化と、公開・非公開・一括操作の手順を説明します。
- [メール（Email）](https://docs.strapi.io/cms/features/email): Email 機能は、ローカル SMTP や SendGrid などの外部プロバイダー経由でトランザクションメールを送信します。このページではプロバイダー設定と、コントローラー／フック経由で送信処理を拡張する方法を説明します。
- [多言語（Internationalization）](https://docs.strapi.io/cms/features/internationalization): Internationalization は、管理パネル上で複数ロケールのコンテンツを扱います。ロケールの追加、エントリーの翻訳、ロケール単位の権限の考え方を説明します。
- [メディアライブラリ](https://docs.strapi.io/cms/features/media-library): メディアライブラリはアップロード済みアセットを集約し、検索・フィルター・フォルダー整理ができます。プロバイダー設定、アップロードの流れ、コンテンツへの差し込み方を扱います。
- [プレビュー（Preview）](https://docs.strapi.io/cms/features/preview): プレビューはコンテンツマネージャーとフロントをつなぎ、公開前に更新内容を確認できます。このページではプレビュー URL を組み立てる設定手順を扱います。
- [ロールベースアクセス制御（RBAC）](https://docs.strapi.io/cms/features/rbac): ロールベースアクセス制御（RBAC）は、管理パネルでの管理者ロールと細かい権限を管理します。このページではロールの作成、権限の付与、管理業務の保護について扱います。
- [リリース（Releases）](https://docs.strapi.io/cms/features/releases): Releases はエントリーを公開用のまとまりにし、コンテンツタイプやロケールをまたいで同時に公開／非公開できます。リリースの作成、エントリーの追加、プラン上の制限を説明します。
- [レビューワークフロー（Review Workflows）](https://docs.strapi.io/cms/features/review-workflows): レビューワークフローは、コンテンツレビューのための複数ステージの独自パイプラインを定義し、下書きから公開までの協業を支えます。このページではワークフローの作成とステージ割り当てを説明します。
- [シングルサインオン（SSO）](https://docs.strapi.io/cms/features/sso): シングルサインオン（SSO）を使うと、管理者はローカルパスワードの代わりに Azure AD などの ID プロバイダーで認証できます。このページでは SSO の有効化とロール割り当て設定を説明します。
- [ユーザーと権限（Users & Permissions）](https://docs.strapi.io/cms/features/users-permissions): Users & Permissions はエンドユーザーアカウント、JWT 認証、API へのロールベースのアクセスを扱います。このページではロールの作成、権限の設定、安全なアクセス用の API トークンについて説明します。
- [インストール](https://docs.strapi.io/cms/installation): Strapi をインストールするさまざまな方法と、使い始めの手順です。
- [Additional resources for migrating to Strapi 5](https://docs.strapi.io/cms/migration/v4-to-v5/additional-resources/introduction): The following pages cover some dedicated topics for specific use cases when upgrading to Strapi 5. Please ensure you have read the [introduction to up...
- [Breaking changes](https://docs.strapi.io/cms/migration/v4-to-v5/breaking-changes): View the list of all breaking changes introduced between Strapi v4 and v5.
- [Upgrading to Strapi 5 - Introduction and FAQ](https://docs.strapi.io/cms/migration/v4-to-v5/introduction-and-faq): Learn more about how to upgrade to Strapi 5
- [Step-by-step guide to upgrade to Strapi 5](https://docs.strapi.io/cms/migration/v4-to-v5/step-by-step): Follow this step-by-step guide to upgrade from Strapi v4 to Strapi 5
- [Admin hooks](https://docs.strapi.io/cms/plugins-development/admin-hooks): The Hooks API lets plugins create extension points (createHook in register) and subscribe to them (registerHook in bootstrap). Hooks run in series, waterfall, or parallel. Strapi includes predefined hooks for the Content Manager's List and Edit views.
- [Admin injection zones](https://docs.strapi.io/cms/plugins-development/admin-injection-zones): Injection zones are predefined areas in the admin UI where plugins can inject React components. Use getPlugin('content-manager').injectComponent() to extend built-in views, or define your own zones with injectionZones in registerPlugin.
- [Admin localization](https://docs.strapi.io/cms/plugins-development/admin-localization): Register translation files with registerTrads, prefix keys with your plugin ID to avoid conflicts, and use react-intl's useIntl hook in components. Strapi merges plugin translations with core translations automatically.
- [Admin navigation & settings](https://docs.strapi.io/cms/plugins-development/admin-navigation-settings): Use addMenuLink in register to add sidebar links, createSettingSection in register to create settings groups, and addSettingsLink/addSettingsLinks in bootstrap to extend existing settings sections.
- [Admin Panel API overview](https://docs.strapi.io/cms/plugins-development/admin-panel-api): The Admin Panel API exposes register, bootstrap, and registerTrads hooks to inject React components and translations into Strapi's UI. Menu, settings, injection zone, reducer, and hook APIs let plugins add navigation, configuration panels, or custom actions.
- [Redux store & reducers](https://docs.strapi.io/cms/plugins-development/admin-redux-store): Use addReducers() during register to add custom state to the Redux store. Then read state with useSelector, update it with useDispatch, and subscribe to changes with useStore. The admin_app slice exposes theme, locale, permissions, and authentication data.
- [Content Manager APIs](https://docs.strapi.io/cms/plugins-development/content-manager-apis): Content Manager APIs add panels and actions to list or edit views through addEditViewSidePanel, addDocumentAction, addDocumentHeaderAction, or addBulkAction. Each API accepts component functions with typed contexts, enabling precise control over document-aware UI injections.
- [Plugin creation & setup](https://docs.strapi.io/cms/plugins-development/create-a-plugin): The Plugin SDK generates plugins without a Strapi project and links them to an existing app with watch:link and yalc. In this documentation: build and verify commands to bundle the plugin for npm or marketplace publishing, and information for monorepos and local setups.
- [Developing plugins](https://docs.strapi.io/cms/plugins-development/developing-plugins): Generation introduction about Strapi plugins development
- [How to create admin permissions from plugins](https://docs.strapi.io/cms/plugins-development/guides/admin-permissions-for-plugins): Learn how to create and configure admin permissions for your plugin
- [How to create components for Strapi plugins](https://docs.strapi.io/cms/plugins-development/guides/create-components-for-plugins): Learn how to create and configure components for your Strapi plugins
- [How to pass data from server to admin panel with a Strapi plugin](https://docs.strapi.io/cms/plugins-development/guides/pass-data-from-server-to-admin): Learn how to pass data from server to admin panel with a Strapi plugin
- [How to store and access data from a Strapi plugin](https://docs.strapi.io/cms/plugins-development/guides/store-and-access-data): Learn how to store and access data from a Strapi plugin
- [Plugin SDK reference](https://docs.strapi.io/cms/plugins-development/plugin-sdk): Reference documentation for Strapi's Plugin SDK commands
- [Plugin structure](https://docs.strapi.io/cms/plugins-development/plugin-structure): Learn more about the structure of a Strapi plugin
- [Plugins extension](https://docs.strapi.io/cms/plugins-development/plugins-extension): Existing plugins can be overriden by placing code in /src/extensions or using global register/bootstrap hooks. Instructions in this documentation cover reshaping plugin content-type schemas or server logic — altough upstream updates may break extensions.
- [Server API for plugins](https://docs.strapi.io/cms/plugins-development/server-api): The Server API defines what a plugin registers, exposes, and executes on the Strapi server. It covers lifecycle hooks, routes, controllers, services, policies, middlewares, and configuration. Use the entry file to declare what the plugin contributes, then navigate to the dedicated pages below for each capability.
- [Server configuration](https://docs.strapi.io/cms/plugins-development/server-configuration): The Server API exposes a config object with a default property and a validator function. Strapi deep-merges the defaults with the user's config/plugins file, then runs validation before the plugin loads. Read configuration at runtime with strapi.plugin('my-plugin').config('key').
- [Server content-types](https://docs.strapi.io/cms/plugins-development/server-content-types): The Server API exports a contentTypes object from the server entry file to declare plugin content-types. The recommended naming convention is to use the same value for the export key and info.singularName so the runtime UID remains predictable when querying or sanitizing data.
- [Server controllers & services](https://docs.strapi.io/cms/plugins-development/server-controllers-services): Just like the Strapi core, plugins can have controllers and services. Plugin controllers handle the HTTP layer: they receive ctx, call services, and return responses. Plugin services hold reusable business logic and interact with content-types through the Document Service API. Keep controllers thin and put domain logic in services.
- [Server getters & usage](https://docs.strapi.io/cms/plugins-development/server-getters-usage): Access plugin resources through top-level getters (strapi.plugin('my-plugin').service('name')) or global getters (strapi.service('plugin::my-plugin.name')). Both return the same object. Use top-level getters inside your own plugin, and global getters from application code or other plugins. Routes have no global getter equivalent. Configuration uses dedicated configuration APIs.
- [Server lifecycle](https://docs.strapi.io/cms/plugins-development/server-lifecycle): The Server API has 3 lifecycle functions. Use register() to declare capabilities before the app is fully initialized, bootstrap() to run logic once Strapi is initialized, and destroy() to clean up resources on shutdown. Each function receives { strapi } as its argument.
- [Server policies & middlewares](https://docs.strapi.io/cms/plugins-development/server-policies-middlewares): Just like the Strapi core, plugins can have policies and middlewares. Plugin policies run before a controller action and return true or false to allow or block the request. Plugin middlewares run in sequence around the full request/response cycle and call next() to continue. Declare policies and middlewares as objects of factory functions and reference them by their plugin-namespaced name in routes.
- [Server routes](https://docs.strapi.io/cms/plugins-development/server-routes): The Server API exports a routes value from the server entry file to expose plugin endpoints. Use the array format only for implicit admin routes, the named router format to separate admin and Content API routes, or the factory callback format for dynamic route configuration.
- [Documentation plugin](https://docs.strapi.io/cms/plugins/documentation): The Documentation plugin auto-generates OpenAPI/Swagger docs for your API by scanning content types and routes. This documentation walks you through installation, customizing settings, and restricting access to the docs.
- [GraphQL plugin](https://docs.strapi.io/cms/plugins/graphql): The GraphQL plugin adds a GraphQL endpoint and Apollo-based sandbox for crafting queries and mutations. Options in config/plugins let you tune depth, item limits, and other Apollo Server settings which are explained in this documentation.
- [Installing Plugins via the Marketplace](https://docs.strapi.io/cms/plugins/installing-plugins-via-marketplace): The in-app Marketplace lists plugins and providers with badges, search, and “More” links to detailed Strapi Market pages. This documentation outlines browsing cards and following provider-specific instructions to install new integrations.
- [Sentry plugin](https://docs.strapi.io/cms/plugins/sentry): The Sentry plugin connects Strapi to Sentry to report errors and attach debugging metadata. This documentation details installation, environment-based configuration, and ways to disable or skip sending events outside production.
- [プロジェクト構成](https://docs.strapi.io/cms/project-structure): 既定の Strapi アプリケーションのプロジェクト構成を確認します。
- [クイックスタート - Strapi 開発者向けドキュメント](https://docs.strapi.io/cms/quick-start): お気に入りのオープンソースヘッドレス CMS、Strapi を数分で起動する手順です。
- [Templates](https://docs.strapi.io/cms/templates): Templates are full Strapi apps that bootstrap new projects via CLI flags such as --template, --template-path, and --template-branch. Instructions in this documentation cover referencing templates from GitHub and turning any Strapi project into a reusable template.
- [Testing](https://docs.strapi.io/cms/testing): Testing relies on Jest and Supertest with an in-memory SQLite database, a patched Strapi test harness that also supports TypeScript configuration files, and helpers that automatically register the /hello route and authenticated role during setup.
- [TypeScript](https://docs.strapi.io/cms/typescript): Get started with TypeScript for your Strapi application
- [TypeScript development](https://docs.strapi.io/cms/typescript/development): TypeScript development showcases Strapi typings for autocompletion, schema type generation with ts:generate-types, and programmatic server starts via strapi() or strapi.compile(). This documentation addresses plugin builds and managing generated type definitions.
- [TypeScript Guides](https://docs.strapi.io/cms/typescript/guides): Learn how you can leverage TypeScript while developing your Strapi project.
- [Upgrade tool](https://docs.strapi.io/cms/upgrade-tool): The Strapi upgrade tool is a CLI command that helps automatically upgrading to a new Strapi version.