Strapi
An open-source headless content management system written in TypeScript and Node.js. It covers content types, draft and publish, a media library, admin users and API tokens, roles and permissions, and webhooks. Maintained by Strapi.
Business rules, traced to source lines.
These 12 rules are a sample of the 40,044 CoreStory V3 extracted from Strapi. Each one links to the exact lines on GitHub at commit 468197a. The statement is CoreStory V3’s wording; the code excerpt is the source it cites.
Regenerating an admin token is only permitted when the requesting user is the token owner; super-admin does not bypass this, and if the request is made with an admin token, only that same token may be regenerated. Otherwise the response is forbidden.
Getting an admin token when the requesting user is not owner and not super-admin results in a not-found response with message 'API Token not found' (indistinguishable from absence).
- API Token not found — message used to obscure unauthorized tokens
Also cited: L34–L48
When userInfo.email is defined (not undefined), the email must not already belong to a different user (queried with id not equal to the current user id); if it exists, the request is rejected with badRequest 'ValidationError' and field error email 'Email already taken'. Emails equal to the current user's own email are permitted.
- ValidationError — error type returned when email is taken
- email — field name for the validation error
- Email already taken — error message when email belongs to another user
Also cited: L43
When deleting a role, the controller fetches the role where type is 'public' from 'plugin::users-permissions.role' and takes its id as publicRoleID; if roleID as string equals publicRoleID as string, it throws ApplicationError 'Cannot delete public role'; otherwise it calls the role service deleteRole(roleID, publicRoleID) and responds with { ok: true }.
- public — role type identifying the public role that cannot be deleted
- plugin::users-permissions.role — model queried to find the public role
- Cannot delete public role — error message thrown when attempting to delete the public role
When the callback provider (defaulting to 'local') is not enabled in the grant settings, authentication throws ApplicationError 'This provider is disabled'. The grant provider key is 'email' when provider is 'local', otherwise the provider name.
- local — default provider
- email — grant key used when provider is local
- This provider is disabled — error message
Also cited: L139–L145
When a password change is requested (isChangingPassword true), and a session manager is available with origin 'admin', the admin session manager must invalidate the refresh token for the current user (String(ctx.state.user.id)). This must happen only after validation checks (current password and email uniqueness) have passed and before persistence, so rejected requests do not log the user out.
- admin — required session manager origin
When a `sizeLimit` is provided and the file size converted from kilobytes to bytes exceeds it, a `PayloadTooLargeError` is thrown stating the original filename and the human-readable size limit. If `sizeLimit` is falsy, no check is performed.
- 1 kilobyte — conversion factor from input file size in kilobytes to bytes used by kbytesToBytes
A filename is valid only if it is non-empty, at most 255 characters, does not contain any of the reserved filename characters <, >, :, ", /, \, |, ?, *, or control characters U+0000 through U+001F, does not match a Windows reserved name (con, prn, aux, nul, com<digit>, or lpt<digit>, case-insensitive), and is not exactly '.' or '..'. Invalid filenames cause formatFileInfo to throw an ApplicationError('File name contains invalid characters').
- 255 characters — maximum permitted filename length
A webhook `url` must be a string matching the URL regular expression `urlRegex` (including a scheme such as `http://` or `https://`, a host, optional port, and optional path/query/fragment), otherwise validation fails with the message `url must be a valid URL`.
- url must be a valid URL — validation error message when url does not match urlRegex
Also cited: L21–L22
A webhook is considered active for an event only when webhook.isEnabled is exactly true, the webhook is triggered by the event, and it is not the case that deduplicateReleaseWebhooks is exactly true while releaseId is defined, the event is either 'entry.publish' or 'entry.unpublish', and webhook.events includes 'releases.publish'.
- true — required strict enabled flag and deduplication flag
- entry.publish — release-related event excluded from deduplicated release webhooks
- entry.unpublish — release-related event excluded from deduplicated release webhooks
- releases.publish — webhook event marking release publish subscription
Operations publish, publishMany, unpublish, unpublishMany, and discardDraft require the content type to have draft and publish enabled; if contentTypes.hasDraftAndPublish returns false, an errors.ValidationError with message 'Draft and publish is not enabled for this content type' is thrown.
- false — return value of hasDraftAndPublish that triggers the error
- Draft and publish is not enabled for this content type — error message
During authentication, if the token has a non-null expiresAt and that expiration date is earlier than the current date, authentication returns { authenticated: false, error: UnauthorizedError('Token expired') }. Tokens with null expiresAt are not expired by this check.
- Token expired — error message returned when a token is expired during authentication
Also cited: L45
What the application does
23 capabilities identified, grouping 686 of the 755 distinct features extracted. These are descriptions, not the cited rules above.
Site Configuration & Public Content
Site-level settings, SEO/metadata, navigation, and rendering of public pages and marketing content.
- About Page: Presents site or organization information through the about content container.
- Article Content Display: Renders an article page with its title, cover media, author, category, and structured content blocks (rich text, quotes, sliders, media).
- Article Display: Renders a published article with its heading, body, author, and publication date for readers.
- Author Management: Create, list, retrieve, update, and delete author records through the authors API.
- Blog Metadata: Provides structured metadata for blog content including titles, authors, slugs, and SEO information.
- Category Creation: Allows a user to create a new category.
- Category Management: Users create and edit categories used to group components and content types.
- Checkout: Checks out the repository source so subsequent build and deploy steps can operate on it.
- Component Metadata Display: Presents descriptive metadata about a code or data structure, including its name, title, purpose, size, and repository.
- Content Info Display: Surfaces informational metadata and content details to users.
- Content Info Panel: Showing descriptive information and attributes about a content item alongside its media.
- Content Rendering: Renders a callable unit's output into a user-visible representation.
- Content Sections Display: Renders a structured set of content sections to present the document's body content.
- Country Availability: Associates a product with the countries in which it is available for user-facing regional selection.
- Data Model Definition: Define structured data entities with display names, plural/singular forms, and attribute collections.
- Entity Metadata Display: Exposes human-facing descriptive metadata for a content entity, including display name, description, kind, and logo.
- Feature Showcase: Presents the product's key capabilities to the user on the homepage.
- Footer Content Display: Renders a footer section with a title, supporting links, and configurable attributes for display to the user.
- Footer and Social Links: Renders footer attribution text and configured social links in the user interface.
- Hero Section Display: Renders a hero banner for a page or screen, combining a title, description, label, picture, and action link.
- Homepage Content Querying: Supports querying homepage content with filtering, sorting, field selection, population, and pagination parameters.
- Homepage Management: Allows users to retrieve, update, and delete homepage content through the /homepage endpoints.
- Job Publishing: Allows a user to publish a job so that it becomes available for consumption.
- Location Display: Renders a location to the user via the LocationDisplay component.
- Logo Display: Displays one or more logos as part of the interface.
- Menu Navigation: Provides a menu for navigating pages and accessing actions.
- Metadata Display: Presents document metadata to the user for inspection.
- Metadata Presentation: Surfaces metadata associated with pages or content for consumers.
- Nested Value Preview: Renders a preview of nested or structured data values for users to inspect.
- Organization Profile Display: Presents an organization's identity and contact details (name, address, info and cover photo) as a user-facing profile.
- Plans Display: Presents product or subscription plans to users, optionally in a column-based layout.
- Product Catalog: Users can view the list of products and add new products to the catalog.
- Product Catalog Display: Present product information including name, display name, description, price, and SKU to users in a storefront catalog.
- Product Creation: Create a new product with its localized content via the product creation flow.
- Product Detail Display: Presents a product's identifying, descriptive, imagery, availability, and SEO metadata for users to view.
- Product Listing Query: List and search products with pagination, filtering, sorting, and field selection.
- Product Lookup: Exposes product information by identifier along with its data fields so a client can retrieve and observe product details.
- Product Model Access: Exposes product data model access for the application.
- Product Query: Build and execute queries for products so callers can search or list them.
- Product Retrieval: Fetch a single product by identifier.
- Product Variation Selection: Exposes a product's available variations and variation blocks so users can browse and choose options.
- Purchase Release: Users can purchase a release, with a subtitle and not-available indicator shown during the purchase flow.
- Related Content Linking: Surfaces related articles and relational content alongside the main content for further reading.
- Release Purchase: Presents a purchase page for a release showing subtitle and unavailability states.
- Rendering: Produces rendered output for display or consumption.
- Rich Text Block Rendering: Displays reusable structured content blocks with formatting and attributes.
- SEO Metadata: Provides page SEO fields such as meta title, meta description, share image, and site-level name and description used by crawlers and social sharing.
- SEO Metadata Authoring: Lets an author define and store SEO metadata — meta title, meta description, and a share image — for content entities.
- Shop Management: Create, read, update, and delete shop entities through the shop API.
- Shop Model Access: Exposes shop data model access for the application.
- Shop Query Filtering and Pagination: Query shops with filtering, sorting, field selection, population, and paginated results including counts.
- Site Configuration: Configurable site identity and contact metadata such as name, logo, contact details, default language, social links, and feature toggles that drive the user-facing experience.
- Site Navigation: Renders site navigation and footer elements such as navbar, footer, and links for users to navigate.
- Social Sharing Metadata: Exposes page metadata for social media previews and sharing, including share images and Twitter card information.
- Stats Display: Shows summary statistics alongside a hero header, title, eyebrow, and subtitle.
- Structured Data Modeling: Defines a typed schema of named attributes and metadata for representing entities with varied field types.
- Structured Data Presentation: Exposes named, documented structured data with attributes and options for consumption by users or other systems.
- Team Management: Create, read, update, and delete teams through the /teams endpoints.
- Testimonials Display: Displays user or customer testimonials.
- Upcoming Match Listing: Provides an upcoming-match resource supporting retrieval, creation, update, and deletion of match entries.
- Video Display: Presenting a large video with its poster, title, and icon for the end user to view.
Admin Panel & Management UI
The admin interface: navigation, settings, dashboards, widgets, tours, forms, tables, and notifications.
- Admin API: Exposes administrative HTTP endpoints for privileged management operations.
- Admin Homepage: The admin homepage welcomes users, provides creation shortcuts, blog/community links, and onboarding guidance.
- Admin Navigation: Users navigate the admin panel through the left menu containing collections, single types, plugins, configuration, and settings sections.
- Admin Panel UI: The React-based admin interface with icons, color picker, routing, styling, and internationalization provides the user-facing management experience.
- Assigned Items Widget: Presents an assignee-focused widget showing items assigned to the user, with its own title and empty state.
- Button Rendering: Supports rendering individual or grouped interactive buttons, including a submit button, for user interaction.
- Collection Listing: Presents named collections of items with metadata such as attributes and informational fields.
- Color Picker: A plugin feature that lets users pick a color via an input with configurable label, format, and advanced validation options.
- Coming Soon Feature Indicator: Displays a coming-soon state or placeholder for functionality not yet available.
- Confirmation Dialog: A popup warning dialog requiring user confirmation before performing an action.
- Content Builder Navigation Menu: Users navigate between the models, single types, and components sections of the content-type builder.
- Content Manager Home: Users see a landing page introducing the content manager with collection types and single types navigation.
- Content Manager Tour: A guided walkthrough of the content manager covering entry creation, fields, publishing, and a final step.
- Copy Value to Clipboard: Users can copy a value (such as a token) to the clipboard with confirmation feedback.
- Copy to Clipboard: Users can copy content with a visual confirmation that the value was copied.
- Data Collection Display: Presents structured collections of records with configurable columns, layout footers, branding, and informational text.
- Data Entry Form: Renders and structures a user-facing form with named, typed fields supporting required, repeatable, and multiple-value inputs.
- Data Entry Form Rendering: Renders form fields from data element definitions, including their display metadata, input types, and field constraints.
- Empty State Guidance: Users are guided to create their first content type or field when a table or component has no entries yet.
- Entity Deletion Confirmation: Users confirm destructive deletions of content types, components, and categories through warning dialogs.
- Feature List Display: Displays a list of product or service features for users.
- Feature Row Listing: Displays configurable feature rows with associated attributes, options, and informational content.
- Feature Rows Group Display: A grouped presentation of feature rows rendered as part of a component's slices, providing a user-facing grouped view of features.
- Filter Management: Users can add, apply, and hide filters for list views, including user-based filters.
- Form Modals: Presents forms to users through modal and popup form containers.
- Form Submission: Allows users to submit forms and select/act via buttons, including accessible skip-to-content navigation.
- Guided Product Tour: Users are guided through the admin panel via a multi-step onboarding tour with skip, next, and completion controls.
- Homepage Dashboard Widgets: Administrators can view, add, arrange, and remove dashboard widgets on the admin home page, including a deploy-now call to action.
- Icon Picker: Provides a picker component for selecting an icon as a data element configuration.
- Key Statistics Widget: Displays administrative counts of content types, entries, assets, components, locales, webhooks, API tokens, and admins.
- Last Activity Widget: Shows recent activity with a link to related content and an empty state when there is no activity.
- List View Configuration: Users can configure list view settings including displayed fields, default sort, page entries, and search/filter options.
- Menu Navigation: Provides a menu for navigating pages and accessing actions.
- Navigation and Discard Warnings: Users are warned before discarding unsaved modifications or deleting content types, components, attributes, or categories.
- Notification Banner Display: Shows a notification banner to communicate messages to users.
- Notification and Error Feedback: Surfaces notifications and error messages to inform users of outcomes.
- Notification and Status Feedback: Users receive informational notifications about model state, such as unsaved creations or autoreload being disabled.
- Operation Feedback Notifications: Users receive success notifications and warnings after plugin operations such as updates, generation, and deletion.
- Profile Tour: A guided tour of the user profile area that can be reset, with a confirmation notification on successful reset.
- Profile Widget: A dashboard widget that presents the authenticated user's profile information.
- Search: Provides a search input with placeholder guidance so users can look up items in the application.
- Search and Filtering: Users can search and filter lists such as users and roles by various criteria.
- Settings Page Purchase Upsell: Offers an upgrade/purchase experience within settings, describing purchase benefits and confirming plan deletion.
- Settings Panel: Users can navigate and configure content type settings, general settings, and layout through a settings view.
- Status Check: Adds a status check capability for entities in the application.
- Structured Data Entry: Captures user input through structured data fields such as names and attribute values.
- Submission Notification Feedback: Users receive a success notification when a form is submitted.
- Table Display: Renders structured data in a table view within the application.
- Toggleable Container: Provides a user-toggleable container that can be shown or hidden.
- Unsaved Changes Prompt: Warns and prompts the user when navigating away from a form with unsaved changes.
- Unsaved Changes Protection: Users are prompted when navigating away from forms with unsaved changes.
- User Notifications: Displays toast/banner messages informing the user of success, error, or warning outcomes of their actions.
- View Configuration: Users can configure list and edit views for a content type, including header layout settings.
- Web UI: Rendering an interactive single-page application front end built with React.
- Workflow Save Notifications: Surfaces success and error feedback to users when workflow stages and assignees are saved.
Content Modeling & Schema Builder
Defining and editing content types, components, attributes, relations, dynamic zones, and content type settings.
- Attribute Collection Definition: Defines a named collection of attributes with display metadata, categories, and configurable options that users can configure and observe.
- Attribute Configuration: Users configure attribute settings such as required, unique, private, length and number constraints, enum rules, and relation targets.
- Attribute Creation and Editing: Users add and configure individual fields/attributes of a model, choosing their type and per-type settings.
- Attribute Relation Targeting: Allows an attribute to declare a typed relation to a target entity, enabling relationships between attributes and other data.
- Attribute Type Selection: Users pick from the supported attribute data types (text, number, date, media, relation, component, dynamic zone, and more) when defining a field.
- Attribute Validation Settings: Users can set per-attribute constraints such as required, unique, private, default value, min/max, length limits and regex on text and numeric fields.
- Component Creation: Creates and persists a new component that can then be composed, published, and updated.
- Component Field Management: Supports single and repeatable component field definitions.
- Component Management: Users can create, select, and configure reusable components and add them to content types, including repeatable and dynamic zone usage.
- Component Publish: Publishes a component so it becomes available for use, with a corresponding unpublish capability to withdraw it.
- Component Selection: Users select existing components when defining a component or dynamic-zone attribute, with component counts and an empty-state message.
- Component Update: Modifies an existing component's definition.
- Component and Dynamic Zone Management: Users create reusable components and assemble dynamic zones by adding components to them.
- Content Model Definition: Defines the full content-type shape via attributes, info, options, and plugin options.
- Content Modeling: Defining structured content types and their fields (types, components, enums, names, localization, repeatability) that users create and edit.
- Content Relations: Users relate content types to one another via one-to-one, one-to-many, many-to-one, and many-to-many associations.
- Content Type Attributes: Lets users define the fields/attributes that make up a content type's structure.
- Content Type Builder: Enables users to define and manage custom data structures by assembling named fields and section layouts.
- Content Type Configuration: Users can view and edit the configuration of content types and components.
- Content Type Deletion: Users can delete a content type via a confirmation modal warning about the impact.
- Content Type Field Definition: Define custom content type fields with display names, plural/singular labels, and typed attributes for a content modeling system.
- Content Type Management: Create, modify, delete, and inspect content type definitions via a code-generation API.
- Content Type Metadata: Expose descriptive metadata such as display names, singular/plural labels, and informational details for content types.
- Content Type Schema Definition: Define and edit content type schemas with singular/plural naming, draft-and-publish behaviour, and attribute definitions.
- Content Type Schema Management: Allows users to configure the identity, display naming, and draft-and-publish behavior of a content type.
- Content-Type Display Naming: Provides human-readable singular, plural, and display names for content types and their fields.
- Content-Type Relations: Declares one-to-one, one-to-many, many-to-one, and many-to-many relationships between content types.
- Content-Type Settings: Users configure content-type identifiers such as display name, singular/plural API IDs, and collection name, with validation warnings for reserved or duplicate names.
- Custom Field Configuration: Defines custom fields with configurable options and defaults.
- Draft & Publish: Enabling draft-and-publish workflows for content entries.
- Draft and Publish: Users author content in draft state and publish it, with schema-level draft/publish options.
- Dynamic Zone Field Management: Provides dynamic zone and block fields for flexible content composition.
- Dynamic Zone Layouts: Build reusable component sections that can be composed dynamically within content types.
- Dynamic Zone Management: Users add components to a dynamic zone attribute and manage the list of allowed components.
- Entity Relationships: Define and manage relationships between content entities, including one-to-one, one-to-many, many-to-one, and many-to-many associations.
- Enumeration Configuration: Users can define enumeration attribute values, display them as a graphql-style list, and specify enumeration rules and placeholder.
- Field Constraint Configuration: Exposes per-field options such as required, unique, and enumerated options for content modeling.
- Field Type Definition: Author content types by composing a rich catalog of scalar, relational, and structural field/component types.
- Media Field Configuration: Users configure media attributes, choosing allowed file/image/video types and single versus multiple selection.
- Media Field Management: Supports single and multiple media field definitions.
- Model Cleanup: Reset or clean up generated model artifacts.
- Model Creation: Creates a new model artifact that users can then work with.
- Model Retrieval: Fetch a model instance from the underlying store so downstream code can operate on it.
- Morph Relation Field Management: Supports polymorphic morph-to-one, morph-to-many, and morph-one relation fields.
- Number Field Configuration: Users configure number attributes with integer/biginteger/float/decimal types and minimum/maximum bounds.
- Publishing Workflow: Controls whether entities support draft and publish states.
- Relation Configuration: Configure relationships between content types, including one-to-one, one-to-many, many-to-one, many-to-many, polymorphic, and self-referencing relations.
- Relation Field Management: Provides one-to-one, one-to-many, many-to-one, many-to-many, and one-way relation fields.
- Schema Update: Update the page schema definition.
- Schema Validation: The system validates user-entered content type and attribute definitions, surfacing errors for reserved names, duplicate enums, and conflicting relations.
- Self-Referencing Relations: Define relationships from an entity back to entities of the same type.
- Self-Referential Relations: Users define relations where a content type references itself.
- Tagging: Allows content types to be taggable via a tagging configuration.
- Text Field Configuration: Users configure text attributes with short/long text options, regex validation, and length limits.
- UID Field Management: Users can generate, apply, and validate unique identifier (UID) fields, checking availability.
Authentication & Account Management
User identity lifecycle: registration, login/logout, passwords, email confirmation, and third-party OAuth sign-in.
- Account Verification: Confirm a user account via a confirmation token and confirmed status.
- Auth Route Exposure: Exposes authentication endpoints on a running server instance so clients can reach the login flow.
- Authentication Provider Configuration: Administrators can enable and configure external authentication providers with key, secret, subdomain and redirect URL.
- Cookie-Based Session Handling: Sets, transmits, and verifies HTTP cookies (including HttpOnly) that carry session state for authenticated requests.
- Device Identification: Extracts a device identifier to associate sessions with a user's device.
- Email Address Validation: Input of an email address in the settings form is validated and rejected when the format is invalid.
- Email Confirmation: Confirms a user's email address through a confirmation link or token.
- External Provider Authentication: Supports authentication through an external provider identified by a provider parameter.
- Google Sign-In: Allowing users to authenticate using their Google account via OAuth2.
- JWKS JWT Verification: Verify a JSON Web Token's signature by resolving the signing key from a JWKS via a JWK-to-key conversion.
- JWT Signing: Create a signed JWT for use as an authentication/authorization credential.
- OAuth 1.0a Authenticated API Requests: Builds OAuth 1.0a signed requests and performs authenticated API calls, including obtaining request tokens for the OAuth flow.
- OAuth Authorization Flow: Initiates an OAuth authorization by building the provider authorize URL with state and scope parameters, then exchanges the returned authorization code for tokens.
- OAuth Callback Handling: The system handles provider callbacks to complete OAuth authorization and return the resulting session or payload to the user.
- OAuth Provider Connection: Users can start an OAuth authorization flow with a provider by building provider config and redirecting to the provider for consent.
- OAuth Provider Enablement: Enables an OAuth provider so users can authenticate through it.
- OAuth Token Query Payload: Converts obtained OAuth tokens into a query payload suitable for downstream consumption.
- OAuth2 Token Issuance: Issue an OAuth2 access token response, producing a signed JWT credential for the client.
- Password Change: Allows an authenticated user to change their password.
- Password Management: Enables users to change, request a reset for, and reset their password.
- Password Recovery: Lets a user request a reset link and set a new password using a reset token.
- Password Reset: Allow users to reset their password using a dedicated reset token.
- Refresh Token Response: Sends refreshed authentication tokens back to the client.
- Registration Terms Acceptance: Users must accept the privacy policy and terms of service when registering an account.
- Role-Based Access: Assign roles to users and support blocking accounts.
- Session Cookie Size Estimation: Estimate the byte size of a signed session cookie so callers can keep within cookie limits.
- Session Management: Provides access to the session manager, enabling users or callers to obtain and work with a session.
- Session Metadata Capture: Builds session metadata from request context for tracking authenticated sessions.
- Session Refresh Cookie Management: Constructs the cookie options used when issuing a refreshed session/token cookie to the client.
- Session Reissue After Password Change: Issues fresh auth tokens to a user following a password change.
- Third-Party OAuth Login: Authenticates users through external providers by connecting and handling provider callbacks.
- Token Confirmation: Confirming actions via issued confirmation tokens that can be consumed once.
- Token Request: A user or system can request a token through a dedicated operation.
- User Account Management: Managing end-user accounts including registration, passwords, profiles, roles and activation state.
- User Account Profile: Represent user identity and profile details such as username, email, and picture.
- User Authentication: Users can sign in, register, recover forgotten passwords, and log out of the admin panel.
- User Authentication Providers: Third-party authentication and user-permission capabilities are integrated to let users log in via external providers and manage access.
- User Login: Authenticates a user via local credentials, returning a JWT and user profile.
- User Logout: Revokes active sessions when a user logs out.
- User Lookup by Email: Retrieves a user record given their email address.
- User Management: Administrators can list, filter, sort, create, and edit users, including assigning roles.
- User Profile Display: Represents a person's profile information including name, bio, photo, role, and organization for display to users.
- User Profile Management: Exposes retrieval and management of user accounts and the current user's own profile.
- User Registration: Allows a new user to create an account with credentials, receiving confirmation and an authenticated user record.
- Username Availability Check: Allows checking whether a desired username is valid and still available, so a user or system can confirm a username before registering it.
- Users Permissions: Provides access to user permission data through a reusable permissions hook and provider.
- Users and Permissions: Provides end-user authentication and role-based access control for the Strapi application.
Localization & Internationalization
Managing locales and translating content, fields, UI strings, and resources across languages.
- AI Translation: Generate and track AI-powered translations for localized content, with completion status and a link to AI settings.
- Article Localization Management: Allows users to add localizations to an article.
- Author Localization: Attach localized content to an existing author via a dedicated endpoint.
- Bulk Locale Publish/Unpublish: Lets users publish or unpublish content across multiple locales from the edit view with confirmation.
- Content Locale Management: Enables users to create, edit, delete, and set default locales for content types in a settings interface.
- Content Localization: Store and serve localized content and attribute labels for internationalization.
- Content Translation: Translates arbitrary content and attributes, including block node detection during translation.
- Content Type Internationalization: Configure localized labels and internationalization settings for content types and their fields.
- Content-Type Localization Configuration: Lets users enable and configure localization for content types and fields in the schema settings.
- Content-Type and Field Localization: Content types and individual fields can be marked as localized so their values vary per locale.
- Copy Content Between Locales: Allows users to copy localized content from one locale to another via a dialog, with success and failure feedback.
- Copy Locale Content: Copy content from one locale into another via a confirmation dialog with success and failure feedback.
- Display Locales in List View: Show and expand the locales associated with entries in the list view.
- Duplicate Value Mapping: Detects and maps duplicate translation values so they can be consolidated during merging.
- Entry Locale Selection and Copy: Editors select a locale when editing entries and can copy localized field values from another locale.
- Fake AI Translations Provider: Provides a mock AI translation provider, letting users substitute fake translations for the real AI-backed service.
- Global Resource Localization: Provides localized content and resources at a global scope, keyed by locale and identifier, so consumers can retrieve locale-specific data.
- Homepage Localization: Enables creating localized versions of homepage content via the /homepage/localizations endpoint.
- Internationalization: Translating the system's own interface strings for different locales.
- Internationalization & Locale Management: Providing locale configuration so content and users can operate in multiple languages.
- Internationalization Support: Enables localized content and options for multilingual audiences.
- Locale Assignment: Allows a locale to be attached to a document.
- Locale List Filtering: Provides a locale picker and list popover letting users display and filter content by locale.
- Locale List Sorting: Users can sort the locale list by default, display name, or id.
- Locale Management: Create, read, update, and delete locale definitions including iso-locale codes and locale identifiers.
- Locale Management Settings: Administrators can list, create, edit, delete, and set a default locale from the plugin's settings screen.
- Locale Picker: Select locales for a content entry, including creating new locales and accessing AI translations.
- Locale Settings Actions: Manage the locale list with add, edit, delete, publish, and unpublish actions and sorting options.
- Locales Column Display: The content list shows which locales an entry is available in via a popover of display locales.
- Localization: Supporting localized, multi-language content driven by a default language and per-element localization settings.
- Localized Field Indication: Indicate to editors whether a given field is localized or not.
- Localized Field Indicators: Marks form fields as localized or not localized so users understand translation state.
- Match Localization: Delivers localized content for upcoming matches via a dedicated localizations resource.
- Missing Translation Key Filling: Detects and adds missing translation keys across files, with support for writing the results to JSON.
- Non-Localized Field Retrieval: Retrieve the list of fields that are not localized for a given content-manager context.
- Package Scope Application: Applies package-level scoping to translation keys so merges respect package boundaries.
- Plugin Translation Prefixing: Enables a prefixed namespace for plugin-provided translations so plugins can expose translated strings without colliding with core or other plugins.
- Pluralization and Localization: Provides singular/plural naming and per-locale content variants for entities.
- Product Localization Management: Manage locale-specific product content via the localizations endpoint.
- Shop Localization Management: Create and manage shop localization settings such as locale.
- Team Localization: Attach localized content to a team via the team localizations endpoint.
- Translation Extraction: Extracts translatable strings from documentation content.
- Translation File Merge: Merges translation keys and values into updated translation files, handling duplicate values and reporting merge results.
- Translation File Read/Write: Reading and writing of translation files, individually or in bulk, keyed by package path.
- Translation Management: A container for translation resources that lets users organize and look up translated content.
- Translation Verification: Provides a check that validates translations across the project so missing or broken localization strings are detected.
Content Authoring & Entry Management
Creating, editing, browsing, publishing, and deleting content entries including rich text and media within entries.
- Article Creation: Create a new article, including an option to publish it immediately upon creation.
- Article Deletion: Allows users to delete an existing article.
- Article Listing: Allows users to retrieve the collection of articles.
- Article Search: Enables users to find articles matching some criteria.
- Article Update: Allows users to modify an existing article.
- Article Viewing: Allows users to retrieve a single article by its identifier.
- Bulk Publish/Unpublish: Users can bulk publish or unpublish multiple selected entries at once, with confirmation warnings and progress notifications.
- Collection Type Entry Management: Users can view and operate on entries of a collection type, including bulk deletion of entries.
- Content Authoring: Users create and edit content entries, including rich text and media blocks.
- Content Block Management: Updates content blocks, such as pages or sections, within entries.
- Content Entry Listing: List the entries of a content type for viewing or selection.
- Content Entry Management: Creating, updating and organizing content entries with authorship and lifecycle metadata.
- Content Lookup: Find content entries by query, the read capability users rely on to locate what they need.
- Content Management: Create and manage content entities composed of sections, text blocks, and media blocks.
- Content Manager: Users can author, edit, publish, and unpublish content entries via the content management interface.
- Content Structure Authoring: Defines the attributes and block layout that make up a content structure.
- Content Structuring: Users organize content into sections and repeatable blocks.
- Content Update: Allows content to be updated through the updateContent operation.
- Document Management: Provides creation, retrieval, and update of documents as a user-facing capability.
- Draft & Publish Management: Users can publish and unpublish content with draft/published state indicators and related confirmation warnings.
- Draft Entry Management: Provides retrieval of draft entries and media drafts so authors can resume editing unpublished content.
- Draft Relations Counting: Users can count the draft relations associated with an entry before acting on it.
- Entry Creation: Allows a user or system to create a new entry.
- Entry Deletion: Users can delete one or more selected entries with confirmation, warning about draft relations, and success feedback.
- Entry Editing: Users can create, edit, and submit content entries with an edit view that tracks information, draft/published versions, and navigation.
- Entry Editing and Creation: Users can create and edit entries by supplying entity input data.
- Entry List View: Users can browse, search, and filter the list of entries for a collection or single type, with displayed fields and pagination.
- Entry Listing with Pagination: Users can browse paginated lists of entries.
- Entry Management: Users can create, retrieve, and update entries in the system.
- Entry Publishing: Enables authors to publish entries, making them available to end users.
- Entry Publishing and Unpublishing: Users can publish and unpublish collection-type and single-type entries.
- Entry Updating: Allows authors to modify existing entries.
- Page Content Management: Manages the content and sections of the application's pages.
- Page Creation: Allows a user to create a new page entity in the system.
- Page Editing: Allows a user to edit page content through an edit page interface.
- Product Catalog Management: Create, read, update, and delete products through the products API.
- Product Creation: Create a new product with its localized content via the product creation flow.
- Publish/Unpublish Actions: Entries can be published or unpublished with additional information shown in confirmation dialogs.
- Rich Content Authoring: Compose rich text, media, and structured block layouts within content types.
- Rich Text Editing: Users can compose rich text content with headings, fullscreen, character counts, and file uploads.
- Single Type Entry Management: Users can view and manage the single entry of a single type.
- Structured Content Authoring: Enables authoring and representing structured content with titles, information, options, content, and imagery.
Deployment & DevOps Pipelines
Building, deploying, and operating the application across cloud, git, CDN, and containerized infrastructure.
- Application Bootstrap: Initializes and starts up the application so it becomes ready for use.
- Application Settings: Administrators can view application title, description, versions, edition, and upgrade/pricing links.
- Application Start: Launches the built application as a running service.
- Build & Release Pipeline: Automates compiling JavaScript and TypeScript outputs and cleaning artifacts for distribution.
- Build Execution: Runs the build and checks its outputs as a pipeline step.
- Build and Package: Builds the project and its compatibility variant.
- Build and Run Toolchain: A set of npm scripts lets developers build and start the Strapi application in both standard and Community Edition modes.
- CDN Delivery: Deployed content is served through a CDN.
- CLI Deployment Guidance: Presents users with CLI deployment instructions and a copyable command on the homepage.
- CLI Install Instructions: Displays the command-line deployment instructions with copy-to-clipboard support and setup guidance.
- Checkout: Checks out the repository source so subsequent build and deploy steps can operate on it.
- Checkout Base Branch: Checks out the base branch of a pull request as part of run setup.
- Checkout Repository: Fetch and check out a repository so its contents are available for subsequent operations.
- Cloud Deployment: Enables users to deploy their Strapi application to Strapi Cloud via the cloud plugin and deploy command.
- Configure Git: Set up git identity and settings for automated version control operations.
- Custom Domain Support: Users can attach a custom domain to their deployed site.
- Database Lifecycle Management: Scripts to start, stop, snapshot, restore, check, and wipe databases across sqlite, mysql, mariadb, and postgres engines.
- Database Service Provisioning: Declares MySQL, MariaDB, and PostgreSQL database services with their container images, credentials, ports, and persistent storage volumes for deployment via Docker Compose.
- Deployment CLI Command Copy: Users can copy a CLI command to deploy, with confirmation feedback and a link to documentation.
- Deployment Guidance: Provides users with instructions and entry points for deploying their site via CLI or Git.
- Deployment Options Display: Surfaces the available deployment methods and documentation to the user on the homepage.
- Deployment to GitHub Pages: Deploys the built site to GitHub Pages, including contributor documentation, as a sequence of pipeline steps.
- Development Server Launch: Starts the application in development mode, with engine-specific variants for sqlite, mysql, mariadb, and postgres.
- Environment-Based Configuration: Reads counts and byte values from environment variables to parameterize behavior at runtime.
- Git Connection Guide: Guides users through connecting a Git repository for deployment via a documented action and status badge.
- Git Deployment: Offers users a Git-based deployment path with a button and badge on the homepage.
- Git-Based Deployment: Users can deploy via a Git workflow, starting from a button with badge and instructions.
- Homepage Feature Highlights: Advertises platform capabilities such as CDN, custom domains, and push-to-deploy to visitors.
- MySQL Database Provisioning: Provision a configured MySQL database service with credentials, root host access, and persistent volume storage for application use.
- MySQL Database Service: Provides a containerized MySQL database service with configurable credentials, port exposure, persistent volumes, and health checking.
- Package Build: The package can be compiled and bundled from source into distributable output.
- PostgreSQL Database Provisioning: Provision a configured PostgreSQL database service with credentials and persistent volume storage for application use.
- PostgreSQL Database Service: Provides a containerized PostgreSQL database service with configurable credentials and persistent storage.
- Production Build: Compiles and bundles the application for production deployment.
- Push-to-Deploy: Pushing changes triggers an automatic deployment.
- Remote Strapi Process Start: Starts a Strapi process on a remote host, allowing a user or system to launch a remote Strapi instance.
- Repository Checkout: Fetches and checks out a target repository branch so subsequent operations work against the correct code revision.
- Secret Redaction: Redacts sensitive values from output so that secrets are not exposed.
- Service Health Checking: Monitors service readiness via periodic healthchecks with configurable interval, timeout, and retry limits.
- Website Build: Builds the project website so it can be published or served.
Media & File Management
Uploading, storing, organizing, retrieving, and serving files and media assets with metadata and folders.
- Distinct Text Fixture Generation: Produces unique text payloads used as upload fixtures.
- Figma Design Import: Users import designs from Figma by selecting images from a multi-step upload flow.
- File Creation: Create a new file in the user's workspace.
- File Deletion: Users can delete an uploaded file by its id.
- File Detail Retrieval: Users can fetch a single uploaded file's details by its id.
- File Listing: Users can retrieve the collection of previously uploaded files with their details.
- File Metadata Description: Uploaded files expose descriptive metadata including name, caption, alternative text, dimensions, provider, and timestamps.
- File Metadata Retrieval: Retrieves file data and size information for uploaded files.
- File Upload: Uploading files with pre-upload existence checking and size/block data handling.
- File Upload & Media Management: Uploading, organizing and serving media assets with metadata, folders and alternate formats.
- File Upload Storage: Uploading and storing user files via pluggable providers like AWS S3 or Cloudinary.
- File Upload and Storage: Upload providers store media assets on AWS S3 or Cloudinary for use within the application.
- Folder Creation: Create a new folder in the user's workspace.
- Folder Management: Users can create and delete folders and enumerate the subtree of a folder.
- Gallery Browsing: Users can browse a gallery by counting its rows and joined rows to enumerate available entries.
- Image Block Rendering: Renders an image block with its media source, caption text, and alt text for display to the user.
- Image Thumbnail Generation: Provision of derived image sizes (thumbnail, small, medium, large) so media can be displayed at appropriate resolutions.
- Image Upload: Allows a user or system to upload an image asset into the application.
- Media Accessibility Metadata: Capture and exposure of alternative text and captions for media assets to support accessible content.
- Media Asset Display: Provides media asset records with URLs, dimensions, and generated responsive image variants for rendering files, images, and thumbnails to users.
- Media Asset Retrieval: Access to stored media assets via URLs, document identifiers, and stable ids so users and other systems can reference and fetch them.
- Media Asset Storage: Upload and persistence of media files with associated metadata such as name, hash, size, mime, dimensions, and provider details.
- Media Block Authoring: Add and manage media blocks within content type definitions.
- Media Block Display: Renders a media block containing a title, description, media type, and media URL for presentation to users.
- Media File Upload & Storage: Stores and manages uploaded media files with metadata such as mime type, size, hash, extension, and provider information.
- Media Image Display & Responsive Formats: Serves media with image dimensions, alt text, captions, and derived responsive format variants for display.
- Media Kind Detection: Classifies media values as audio, image, or video so callers can render or handle each kind differently.
- Media Library: Users can upload, browse, preview, and remove media files with details such as name and size.
- Media Localization: Association of media assets with a locale so localized content can reference the appropriate asset variant.
- Media Localization & Publishing: Supports localized media entries with publish lifecycle metadata for content delivery.
- Media Publishing: Supports publishing and versioning of media assets with timestamps and locale awareness.
- Media Publishing and Scheduling: Tracking of creation, update, and publication timestamps so media lifecycle and publish state can be observed.
- Media Upload: Allows users to upload media content through a configurable upload container with type restrictions and display options.
- Media and Link Display: Presents linked resources and media alongside structured content.
- Multiple Media Upload: Allows users to attach multiple media files via a media configuration data element.
- Plain Text Multipart Upload: Submits a text body to the service via a multipart/form-data POST request.
- Upload Concurrency Instrumentation: Attaches instrumentation to observe concurrency behavior during uploads.
- Upload File Transfers: Uploads files to the system through file counting and seed upload signature generation backed by the uploads database.
Developer Tooling & Package Management
CLI entry points, dependency declaration/installation, build tooling configuration, and monorepo package metadata.
- Command-Line Interface Invocation: Entry-point capability that lets a user invoke the tool from the command line.
- Command-Line Invocation: Provides the executable entry point that drives the tool's package version auditing behavior.
- Dependency Declaration: Declares runtime and development dependencies and supported engine versions for installation and environment checks.
- Dependency Installation: Installs a monorepo's JavaScript dependencies using yarn, optionally enabling Corepack first.
- Dependency Management: The package declares its runtime and development dependencies plus supported Node engine versions.
- Dependency Manifest Inspection: Surfaces declared dependency, devDependency, and peerDependency sets together with build/test scripts and environment constraints for the package.
- Dependency Name Resolution: Resolves and reports the dependency names declared by a package.
- Domain Configuration Loading: Capability to load domain configuration definitions for use by the tool.
- File Deletion: Users can delete an uploaded file by its id.
- Forwarded Runner Arguments: Capability to build argument sets that are forwarded to the underlying runner.
- Helper Generation: Generate helper utilities for the generated codebase.
- Internal Peer Dependency Rewriting: Rewrites internal peer dependency references, using glob directory resolution to locate the relevant packages.
- Issue Tracking Configuration: Advertising where bugs and support requests should be reported for the package.
- JSON Output: Produces serialized JSON output as a code container.
- Maintainer Custodianship: Recording the set of maintainers responsible for the package.
- Mock Provider: Provides a mock data source that consumers can use in place of a real provider.
- Module Entry Point Resolution: Declares the package's entry points (main, module, types) so bundlers and consumers can resolve its code.
- Package Distribution Configuration: Declares how the package is distributed and consumed, including its exports, published files, and supported runtime engines.
- Package Entry Point Resolution: Exposes the main, module, and source entry fields so consumers and tooling can resolve the package's public entry points.
- Package Manifest Authoring: Reading and writing package.json metadata such as name, version, description, license, author, repository, and keywords.
- Package Metadata & Dependency Declaration: Provides the package's identity, description, license, author/maintainers, repository/homepage/bugs URLs, and declared runtime and development dependencies/engines.
- Package Metadata Display: Exposes the package's identity and provenance metadata such as name, version, description, author, maintainers, license, and homepage for consumers to read.
- Package Metadata Distribution: Exposes npm package metadata (name, version, author, license, homepage, repository, bugs, maintainers, keywords) for consumers and registries.
- Package Module Exports: The package defines its public entry points and type declarations so consumers can import the module and its types.
- Package Script Configuration: Exposing executable scripts and package entry points so consumers and tooling can build, run, and import the package.
- Package Scripts and Distribution Files: Defines runnable npm scripts and the set of files included when publishing the package.
- Project Directory Creation: Creates the project directory needed to hold uploaded artifacts.
- Project Metadata: The package exposes descriptive and repository metadata for discovery and support.
- REST Resource Transformation: Transforms internal representations into REST resources for API responses.
- Runnable Domain Selection: Allows a user or system to select, or obtain the set of, runnable domains to operate on.
- Shard Planning: Plans shard distribution and processing by parsing shard specifications and computing shard arguments such as median-based partitioning.
- Shipped Artifact Detection: Determine whether a component is shipped or hand-written, individually or across the whole set.
- Task Script Execution: Provides named scripts that can be invoked to run the package's build, test, and other lifecycle tasks.
- TypeScript Compilation Configuration: Defines how TypeScript source is compiled and which files are included or excluded from the build.
Testing & Quality Assurance
Unit, integration, end-to-end, and UI testing plus linting, static analysis, and quality gates.
- API Test App Loader: Provides a helper to create and load the API test application.
- API Testing: Executes API test suites across database backends and editions (community/enterprise, mysql/pg/sqlite).
- Benchmarking Suite: Runs comparative benchmarks with seeding, suite execution, and comparison scripts.
- CLI Output Snapshot Normalization: Normalize CLI output (line endings, volatile IDs) so snapshots are stable and comparable.
- CLI Testing: Runs CLI test suites and exposes the command-line interface entry point.
- Code Linting: Provides linting and formatting tasks for the codebase, including oxlint and pretty formatting.
- Code and Content Linting: Runs a suite of language-specific linters and content checks over repository files.
- Collector Fixture Retrieval: Look up collector fixtures by name for use in tests or data collection.
- Console Output Assertion: Let a test assert that captured console output equals or includes expected lines.
- Duplicate Detection: Identifies duplicated entries or translations in a codebase and surfaces them to the user.
- End-to-End Testing: Runs end-to-end test suites covering community, enterprise, enterprise plugins, and media library scenarios.
- Execution Timing: Measure and report the duration of an operation for performance observation.
- Fixture Generation: Generate and tear down test fixtures or seed data programmatically.
- Fixture Management: Create and delete test fixtures, allowing users to set up and tear down seeded data for testing.
- Frontend Unit Testing: Runs the frontend test suite to exercise UI behaviour.
- Generated Client Verification: Verifies that a generated database client matches the expected client, including format and identity assertions.
- Linting: Provides a lint script for static code quality checks.
- Page Verification: Assert expected page state in tests.
- Runtime Database Verification: Asserts and verifies runtime database dialect and assurance by inspecting the live database.
- Security Lockfile Analysis: Analyzes lockfiles to surface security findings about project dependencies.
- Stamp Fixture Retrieval: Look up stamp fixtures by name for use in tests or data collection.
- Static Analysis: Runs static analysis quality gate for the codebase.
- Test App Environment Loading: Load the application environment for use in tests.
- Test App Generation: Generates a temporary test application, links its package dependencies, and runs it to exercise the project under test.
- Test App Listing: Provides a listing of test applications that a user or another system can retrieve.
- Test App Requirement Calculation: Capability to determine how many test applications are required for a given context.
- Test App Setup: Retrieves and prepares test applications against which a package can be exercised.
- Test Execution: Run frontend and unit test suites to validate the codebase.
- Test Fixture Management: Provides the ability to create and delete test fixtures for setting up and tearing down test data.
- Test Fixture Seeding: Seed pages with cards and delete fixtures to set up test scenarios.
- Test Suite Execution: Runs unit and TypeScript test suites (including watch and Vitest variants) to validate the package.
- UI Testing: Runs next-generation UI test suites and TypeScript checks.
- Unit Testing: Runs frontend and backend unit test suites, including vitest-based backend tests.
Documentation & Static Content Publishing
Generating, building, deploying, and serving documentation and content sites including search and metadata.
- API Documentation: A documentation plugin publishes the API surface for external consumers.
- Client-Side Redirects: Handles client-side URL redirects for the documentation site.
- Code Syntax Highlighting: Renders syntax-highlighted code blocks in documentation pages.
- Delete Documentation: Users can delete generated documentation for a document, including confirmation and handling of missing versions.
- Display Generated Files: Users can toggle and view the generated documentation files through the plugin UI.
- Document Deletion: Users can delete generated documentation documents with success notification, guarded against missing versions.
- Document Display: Renders a document with its title, body, and attributes so a user can view its content.
- Document Regeneration: Users can trigger regeneration of a plugin's generated documentation, with handling for missing versions.
- Documentation Access: Links users to deployment documentation from the homepage.
- Documentation Build: Builds the project documentation.
- Documentation Generation: Users can generate documentation artifacts for content types from the plugin's home page.
- Documentation Logging: Provides logging output for the documentation tooling.
- Documentation Notification: Triggers documentation-related notifications through the notify-docs capability.
- Documentation Page Viewing: End users can open and read the generated documentation through the public plugin page.
- Documentation Regeneration: Users can regenerate their generated documentation output, with feedback on success and version-missing errors.
- Documentation Site Build: Produces a production build of the documentation site for deployment.
- Documentation Site Deployment: Deploys the built documentation site and serves it locally.
- Documentation Site Development Server: Starts a live local development server for the documentation site.
- Documentation Site Scaffolding: Scaffolds and manages a Docusaurus-based documentation site including packages under scaffold:packages with declared browser targets.
- Documentation Status Badges: Displays visual status indicators on code containers to show documentation health such as documented, draft, missing, stub, needs-review, and badge markers.
- Documentation and Help: Users can access embedded documentation, help, and cheatsheet resources from the admin panel.
- Generated Documentation Display: Users can view generated plugin documentation and its version in a table on the plugin page.
- Generated Files Display: Users can view and toggle the display of generated files and their versions in a table.
- Heading ID Generation: Generates stable anchor IDs for documentation headings.
- JWT Token Configuration: Administrators can configure and copy a JWT token to authenticate documentation access.
- LLM Content Exposure: Exposes documentation content in a machine-readable form for LLM consumption.
- Local Site Search: Provides offline full-text search over the documentation site content.
- MDX Content Authoring: Enables authoring documentation content with MDX and React components.
- Mermaid Diagram Display: Renders Mermaid diagrams within documentation pages via a dedicated theme.
- Regenerate Documentation: Users can regenerate generated documentation for the current document, with feedback and error handling for missing versions.
- Theme and Component Customization: Allows customizing Docusaurus themes and components via swizzling and shared TypeScript config.
- i18n API Definition: The OpenAPI specification defining i18n endpoints with their paths, schemas, parameters, and security schemes.
CI/CD & Release Automation
Automated pipelines for building, testing, caching, versioning, and publishing packages and releases.
- Browserslist Database Update: Update the Browserslist database and open a pull request when changes apply.
- Build Cache Restore: Restores cached build and Nx artifacts so subsequent runs can reuse prior build outputs.
- Build Cache Save: Saves Nx cache artifacts for reuse by later runs.
- CI Node Version Matrix: Runs CI steps across a configured matrix of Node.js versions on specified runners.
- Canonical Version Resolution: Resolves a package or dependency to its canonical version identifier for comparison or reporting.
- Change Freeze Check: Determines whether a change freeze is currently active so that pull request automation can be enabled or disabled accordingly.
- Dependency Cache Restoration: Restores previously saved caches for node_modules, yarn, and npm to speed up installs.
- Dependency Ignore Rules: Allows specified dependencies to be excluded from update processing.
- Dependency Package Grouping: Groups related dependencies (e.g. babel, eslint, jest, react, typescript) so their updates are managed together.
- Dry-Run Preview: Allows the PR lifecycle automation to run without applying changes so users can preview its effects.
- GitHub Action Script Execution: A GitHub Action step that invokes a shell script from within the action directory, driven by configurable step and run inputs.
- GitHub Actions CI Workflow: A CI pipeline that runs on triggers, checks out the base branch, sets up Node, resolves an issue template, validates checkboxes, and installs scripts.
- Issue Label Triggered Automation: A GitHub Actions workflow that runs automatically when an issue is labeled, executing a label-handling script within a defined job and permissions context.
- Manual Workflow Trigger: Allows a workflow to be dispatched manually with configurable inputs.
- NPM Dependency Updates Configuration: Defines Dependabot update configuration for npm ecosystem packages including update intervals, versioning strategy, and pull request limits.
- Package Manifest Discovery: Locates package.json files across the filesystem so they can be processed by tooling.
- Package Publishing: Publishes a distributable package to a registry using a configured name, version, and distribution tag.
- Package Publishing Configuration: Provides the file allowlist, entry exports, maintainers, and bug tracker configuration used when publishing and distributing the package.
- Package Version Check: Checks package versions within a package manifest to report outdated or mismatched dependencies.
- Re-run Failed Jobs: Allows a user to re-run the jobs that failed, and to list the jobs that then passed on the re-run, within a job run.
- Release Drafting: Draft a release, producing a pull request with its URL and number.
- Release Management: Create and version releases with semantic version bumping and changelogs.
- Security-Dependency Updates: Provides grouped configuration for security-related dependency updates across the tooling ecosystem.
- Semver-Aware Cooldown Scheduling: Applies per-update-type cooldown windows (major, minor, patch, default days) to schedule when updates are taken.
- Version Bump: Bump a package version and record the change in a journal.
- Version Enforcement: Determines whether version constraints must be enforced and applies that enforcement to packages.
- Workspace Cleanup: Removes transient workspace artifacts and cached PR state to leave a clean environment after a run.
- Workspace Package Discovery: Discovers and lists the packages defined within a project workspace, resolving workspace glob patterns and package names from configuration.
- Yalc Package Publishing: Publishes local packages to a yalc store so consuming apps can install the current build.
- Yarn Config Exposure: Exposes yarn configuration values as GitHub Actions outputs for downstream steps.
Release Management
Creating, scheduling, editing, publishing, and grouping content releases with settings and entry association.
- Add Content to Release: Allows users to select an existing release and add one or more content entries to it from the content manager edit and list views.
- Add Entry to Release: Lets a user select an existing release and add a content entry to it with success/cancel/redirect handling.
- Browse and Filter Releases: Lists releases with grouping options, counts, empty states, and status indicators so users can find and inspect releases.
- Content Manager Release List: Users can view releases associated with a content entry in the content manager, with a title and entry error notification.
- Create Release: A user creates a new release by specifying a date, time and timezone.
- Delete Release: A user deletes an existing release via a confirmation dialog.
- Edit Release: A user modifies an existing release's details, with a success notification on update.
- Group Release Entries: Lets a user regroup the entries in a release by actions, content type or locale.
- Open Content Manager from Release: Allows navigating from a release entry to the content manager to view the related content.
- Publish Release: A user triggers publishing of a release and receives a success notification.
- Release Action Menu: Provides an actions menu for a release exposing release operations such as edit and delete.
- Release Actions Menu: A per-release action menu exposes operations such as edit and remove on an individual release.
- Release Creation: Users can create a new release by specifying a date, time, and timezone via a modal form, receiving a success notification upon creation.
- Release Default Timezone Setting: Users configure a default timezone for releases in settings, with a success notification.
- Release Details Viewing: Users can view detailed information about a release including its grouped entries with columns for content type, locale, name, status, and actions.
- Release Limit Reached Feedback: Informs users when the maximum number of releases is reached and offers a next action.
- Release Limits and Error Feedback: Enforces and surfaces a maximum release limit as well as scheduling errors and not-scheduled states to the user.
- Release List Viewing: Users can browse the list of releases, view release details, and see a tabbed view of release information.
- Release Listing: Displays the list of releases including counts, scheduling state and empty states.
- Release Management Actions: Users can edit, delete, publish, refresh, and open release actions for a release through the header actions menu.
- Release Scheduling: Users can schedule a release for a future date/time and see scheduled date information.
- Release Settings: Users can configure the default timezone for releases in settings, receiving a success notification.
- Release Settings Configuration: Provides a settings panel to configure release defaults such as timezone, with confirmation feedback.
- Remove Content from Release: Allows users to remove content entries from a release via the content manager edit view's release action menu.
- Remove Entry from Release: Allows a user to remove a content entry from a release and notifies them of success.
- Upcoming Releases Widget: A dashboard widget surfaces upcoming releases with a link and an empty state.
- View Release Details: Shows the details of a release with a table of its entries and grouping controls.
Repository & Pull Request Automation
Automated triage, review, walkthroughs, staleness handling, and PR lifecycle management.
- Automated Pull Request Review: Automatically reviews pull requests according to configured profile, instructions, and path filters, producing review status and labels.
- Automated Stale Issue Closing: Automatically closes issues that have remained inactive for a configured period, optionally posting a closing message.
- Benchmarking Suite: Runs comparative benchmarks with seeding, suite execution, and comparison scripts.
- CI Status Check: Retrieves the CI status for a given pull request.
- Commit Message Configuration: Configures commit message prefixes and labels for automated dependency update pull requests.
- Community PR Sync to Linear: Synchronizes all community pull requests into Linear.
- Community PR Triage: Determines whether a contributor is an organization member and applies labels to triage community pull requests.
- Conventional Commit Classification: Categorize commits into types such as feat, fix, chore, docs, and security.
- Duplicate Issue Detection: Detects and deduplicates issues that share the same issue id.
- External Author Filtering: Fetches and identifies internal authors versus bots to filter community contributions.
- Feature Branch Merge: Performs a merge operation targeting a branch, taking a target branch input for the merge destination.
- Issue Triage Automation: Automated closing of irreproducible issues and reconciliation of invalid template issues via scheduled tasks.
- Merged PR Fetching: Fetches merged pull requests for a given repository and owner, producing the list of PRs for the specified or default base branch.
- Merged Pull Request Fetching: Fetches merged pull requests between two branches, scoped by base and target branch inputs.
- Pull Request Auto Reply: Automatically replies to pull request conversations on behalf of the tool.
- Pull Request Listing: Fetches and displays pull requests for a repository by comparing branches via the compare API, showing progress while retrieving and de-duplicating results.
- Pull Request Status Check: Retrieves and reports the status of pull/merge requests for a project.
- Pull Request Sync to Linear: Fetches community pull requests and creates or updates corresponding Linear tickets, including labels and metadata.
- Pull Request Walkthrough: Generates a structured walkthrough of a pull request including high-level summary, changed files, sequence diagrams, and optional poem.
- Remove QA Done Label: Automatically removes the 'qa-done' label from pull requests via a CI job step, gated by permissions and a run condition.
- Stale Issue Cleanup: Automatically closes issues that have become inactive or stale.
- Stale Issue Detection and Marking: Marks issues as stale after a configurable period of inactivity, with exemption rules for labels, assignees, and milestones.
- Stale PR Detection: Evaluates pull requests against age thresholds to determine which are stale or waiting on the author.
- Stale Pull Request Handling: Applies stale and close timing rules to pull requests via dedicated day thresholds.
- Stale Workflow Run Configuration: Configures workflow execution limits, authentication, and ordering for running the stale-management process.
- Waiting-on-Author Notification: Identifies pull requests waiting on their author and triggers reminders to prompt action.
API Surface & External Integrations
REST/GraphQL APIs, authenticated outbound requests, and third-party service integrations.
- API Request Creation: Builds authenticated and content-specific API requests for outbound calls to remote services.
- Authenticated JSON Fetch: Fetches remote JSON resources using a bearer token for authentication, with the token attached to outgoing requests and the response parsed as JSON.
- Base64URL Encoding: Encode binary or string data into URL-safe base64 form for use in tokens and cookies.
- Error Monitoring: A Sentry plugin reports application errors to an external monitoring service.
- GitHub Integration: Initializes and performs authenticated GitHub API requests including GraphQL queries and paginated REST calls.
- Issue Management: Handles issue comments and threads as part of the tool's repository interactions.
- Issue Reporting: Provides structured templates for users to file bug reports and feature requests across Strapi products.
- Linear Integration: Initializes Linear API access and issues GraphQL operations, including project updates.
- Linear Label Management: Loads, resolves, and ensures team labels exist on Linear for tagging tickets.
- Linear Ticket Sync: Syncs pull requests to Linear by creating Linear tickets for community PRs with appropriate labels.
- Linear Weekly Report Posting: Posts a weekly report to Linear summarizing relevant activity.
- Notion Integration: Initializes Notion API access and writes pages and rich text blocks to Notion.
- Output Sanitization: Sanitizes output content to neutralize unsafe or unwanted material before it is returned to the user.
- RSA Key Generation: Generates an RSA public/private key pair that a user can rely on for cryptographic use.
- Rate Limiting: Applies request throttling by building a rate-limit runner from a configured rate-limit path and enqueuing context operations under that limit.
- Repository Integration: Integrates with repository branches and pull requests as the primary surface of the tool's operations.
- Repository Reference Validation: Validates user-supplied repository, branch, and ref names before they are used in API requests.
- Request Authorization: Attaches authorization credentials to outgoing requests.
- Request Header Application: Applies HTTP headers to an outgoing request.
- Slack PR Notification: Sends a Slack notification when a pull request event occurs, using the pull request's title, number, and URL.
- Twitter API Access: Provides a capability to perform authenticated GET requests against the Twitter API.
- URL Encoding: Encodes owner, repository, and branch identifiers for safe inclusion in API request paths.
- URL and Host Allowlisting: Restricting which URLs and hosts are permitted based on configured allow lists.
- User Data Sanitization: Sanitizes user objects before they are returned to clients.
- Webhook Management: Administrators can create, list, and configure webhooks with URLs, headers, and events, including triggering test webhooks.
Content Transfer & Migration
Moving, importing, seeding, and migrating content and schema data between environments and versions.
- Collection Browsing: Exposes named data collections containing data elements for selection and display.
- Content API: Exposes HTTP endpoints for accessing and managing content.
- Content Import: Importing structured content entities such as articles, authors, categories, and general about/global data into the system.
- Content Import and Seeding: Imports seed content such as articles, authors, categories, and about data into the application, including example app data on first run.
- Content Transfer Operations: The core data-transfer capability that moves Strapi content between environments via streams and archives.
- Data Migration: Performs schema/data migration to version 5.
- Database Migration and Seeding: Applies data migrations and seeds the database with versioned data sets.
- Directory Scanning: Enumerates and reads files from a directory, with format-aware readers for JSON and JSON Lines directories.
- Example App Seeding: Provisioning an example application and seed data on first run to bootstrap a fresh installation.
- File Content Reading: Reads the contents of individual files, including JSON and JSON Lines formats.
- File Content Search: Search across files loaded into memory for matching filenames and string content.
- GraphQL API: Exposes the Strapi content API over GraphQL through the GraphQL plugin.
- GraphQL API Endpoint Provisioning: A GraphQL plugin that exposes GraphQL endpoints alongside the default API methods.
- GraphQL Content API: A GraphQL plugin exposes the application's content through a GraphQL API.
- Indexed Populate Query: Builds a populate query that fetches referenced entities by index identifiers for use in read operations.
- Payload Construction: Assemble a structured payload object from scalar inputs for transmission or use.
- Query Builder Setup: Initializes and configures a query builder instance, including setting query array limits, before queries are run.
- Query Sanitization: Sanitizes incoming queries to strip unsafe content before they are processed.
- Query Validation: Validates incoming queries to determine whether they are acceptable for processing.
- Record Collection: Collects parsed input into output forms: raw, string, JSON, and JSON Lines collectors.
- Rename Migration Tracking: Discover and track pending rename migration files so attribute renames are applied to stored data.
- Test Transfer Token Creation: Enables creation of a token that allows a test transfer to be authorized and performed.
- Transfer Test Data Generation: Creates deterministic transfer test files and seeds transfer test media, providing reproducible test fixtures.
- Upload Policy and CSA Generation: Generates an upload policy and produces a CSA document for uploading project content.
Plugin & Extension Ecosystem
Discovering, installing, configuring, and extending the system through plugins and integrations.
- Internationalization: Translating the system's own interface strings for different locales.
- Internationalization Support: Enables localized content and options for multilingual audiences.
- Plugin Configuration: Per-plugin options and configuration that extend the system's capabilities.
- Plugin Description and Metadata: Exposes descriptive metadata about a plugin - its name, description, kind, version, and visibility - so users and hosts can identify and present it.
- Plugin Discovery: Users see the content-type-builder plugin presented with its name and descriptive text.
- Plugin Extension: Lets users extend the application's capabilities through plugins.
- Plugin Extension Options: Expose configuration options on data structures so plugins can extend their behaviour.
- Plugin Header Display: Displays plugin name and short/long descriptions in a header for the user.
- Plugin Home Page: A home page interface where users view plugin branding and manage generated documentation via update and regenerate actions.
- Plugin Identity Display: Exposes a plugin's name as user-facing identity information.
- Plugin Management: Administrators can browse, install, download, and delete plugins from the marketplace and manage installed plugins.
- Plugin Options Display: Surfaces plugin configuration options associated with the data structure to the user.
- Plugin Overview and Metadata: Users see plugin name, descriptions, and a plugin header on the home page.
- Plugin Registration: Plugins can be registered under a named identity.
- Plugin Settings Configuration: Users can view and edit plugin settings, including toggling options and saving changes, with validation of input such as JWT token, password, and restricted access.
- Plugin Settings Form: A configuration form where users set JWT token, password, restricted access, and generated file display options.
- Plugin Settings Management: Users can view and save plugin settings via the settings page, including toggles.
- Strapi Application Scaffolding: Provides the core Strapi application framework and CLI so users can build, develop, and start a Strapi-based app.
- Strapi Integration: Enables the package to be recognized and consumed as a Strapi plugin/extension through its dedicated Strapi configuration block.
- Strapi Plugin Configuration: Supplies the Strapi-specific configuration block that activates and configures the plugin within a Strapi application.
- Strapi Plugin Integration: Declaring the Strapi-specific extension metadata that enables the package to act as a Strapi plugin.
Permissions & Access Control
Roles, permissions, policies, and authorization gating across routes, entities, and settings.
- API Token Management: Creating and governing API access tokens with permissions, lifespan and usage tracking.
- Administrator Management: Managing administrative users, their roles and permissions in the admin panel.
- Entity Access Control: Locate an entity and determine whether the requesting user is permitted to access it.
- Grant Initialization: Enables users to initialize grant-related functionality.
- Locale Permissions Settings: Surface loading and read-denied states for locale-related permissions.
- Ownership Check: Verifies whether a user is an owner of the relevant resource and reports the outcome via a response.
- Permission Management: Exposes the set of permissions available to users and roles.
- Permissions Configuration: Administrators can assign fine-grained read/create/update/delete/publish permissions and conditions to roles.
- Permissions Management: Lets administrators view and manage the permissions tree applied to roles.
- Policy Management: Administrators can view and manage policies with header guidance.
- Protected Advanced Settings Access: Users must be authorized to access a protected advanced settings page.
- Protected Role Page Creation: Provides page creation restricted to protected roles, enforcing role-gated access to the create-page capability.
- Protected Roles Editing: Allows editing of protected roles through a dedicated edit page.
- Protected Roles Listing: Displays a list of protected roles to the user.
- Restricted Access Settings: Administrators can enable restricted access controls on generated documentation.
- Role & Permission Management: Defining roles and their associated permissions for users and API tokens.
- Role Management: Administrators can create, list, edit, and delete roles with their descriptions and user associations.
- Roles Listing: Displays a list of roles to the user.
- Route Authorization: Determines whether a given route is enabled for the current user or configuration before it is accessed.
- Settings Permission Gating: Access to the locale settings screen is gated by read permissions with loading and denial states.
Email & Outbound Messaging
Configuring, templating, and sending transactional email through pluggable providers.
- Advanced Settings Configuration: Users can manage advanced settings including email-related toggles for sign-up, confirmation, password reset and role selection.
- Advanced Settings Retrieval: Retrieves advanced configuration/settings for the user.
- Advanced Settings Viewing: Users can view an advanced settings page interface.
- Email Configuration: Allows users to set up and initialize email settings.
- Email Delivery: An email provider lets the system send transactional email through Mailgun.
- Email Plugin Configuration: Configure email delivery settings such as default sender, reply-to address, and provider.
- Email Plugin Settings Configuration: Users can view and configure the email plugin's provider and sender/reply-to addresses through a settings panel.
- Email Recipient Management: Address an email to primary, carbon-copy, and blind-carbon-copy recipients with an optional reply-to address.
- Email Sending: Send an email message with recipients, sender, subject, and text or HTML body content.
- Email Service: The system sends transactional emails such as password-reset messages.
- Email Settings Management: Administrators can configure email templates and sender options such as from address, response email, subject and message.
- Email Settings Validation: Validate email addresses entered in the settings UI and surface validation errors.
- Email Templates Viewing: A protected page that lets users view the available email templates.
- Email Test Sending: Send a test email to a nominated address and observe success or failure.
- Message Publishing: Publishes messages through a transport layer, exposing a single publish capability that callers invoke to emit data.
- Test Email Delivery: Users can send a test email to a specified address and observe success or failure feedback to verify their email configuration.
Database Persistence
Persisting application content to supported SQL databases with driver and lifecycle support.
- Database Lifecycle Management: Scripts to start, stop, snapshot, restore, check, and wipe databases across sqlite, mysql, mariadb, and postgres engines.
- Database Persistence: Database drivers support persisting application content to SQLite, PostgreSQL, or MySQL.
- Diagram Restart: Allows the user to restart the process or diagram state from its current point.
- MySQL Database Service: Provides a containerized MySQL database service with configurable credentials, port exposure, persistent volumes, and health checking.
- PostgreSQL Database Service: Provides a containerized PostgreSQL database service with configurable credentials and persistent storage.
- Restart: Triggers a restart of the service or system.
- Runtime Database Verification: Asserts and verifies runtime database dialect and assurance by inspecting the live database.
- Service Restart: Restart a running service.
- Simulation Restart: Allows a user to restart the running simulation from the current state.
- System Restart: The capability to restart the system or service, exposed as a directly triggerable operation.
AI Assistance
AI-powered chat, content/schema generation, code upload, and feedback within the admin experience.
- AI Chat Assistant: Users can open, create, and interact with an AI chat that accepts prompts, uploads code, shows thinking state, and supports stopping generation.
- AI Content Generation Chat: Users interact with an AI chat assistant to generate Strapi schemas, CTB prompts, or code, including sending messages and stopping generation.
- Chat Attachments: Users attach or upload images and code/folder files to a chat conversation.
- Chat Feedback Submission: Users submit feedback on AI responses by selecting a reason and adding a comment.
- Chat Interface: Enables users to exchange messages through a chat interface.
- Code Upload to Chat: Users can upload code into the chat via a drag-and-drop zone with a browse option.
- Eval Dataset Processing: Loads and processes a collection of eval records, each carrying an identifier, prompt, and file references, as an evaluation dataset.
- Interactive Chat: Provides a conversational chat interface that can invoke configured tools.
- Knowledge Base and Learnings: Captures and reuses persistent knowledge and learnings to inform future interactions.
Analytics & Reporting
Dashboards, statistics, triage reports, and result reporting for administrators and maintainers.
- Analytics: Administrators can view analytics data within the admin panel.
- QA Checklist Generation: Generates a QA checklist for users or downstream systems to consume.
- Related Tasks: Retrieves and presents tasks related to the current task, allowing users to navigate associated work items.
- Report Generation: Produces reports through a report run that gathers a mode and assembles the report output.
- Results Reporting: Prints the analysis results to the user for review.
- Stats Display: Shows summary statistics alongside a hero header, title, eyebrow, and subtitle.
- Task Listing: Displays a list of tasks to the user, providing the primary read/view capability over task data.
- Task Modal: A modal dialog capability for presenting and managing a task to the user.
- Weekly Triage Report: Builds and publishes a weekly Notion report of PR triage categories including new, quick-win, pickup, and stale PRs.
Token & Cryptographic Utilities
Signing, verifying, encoding, and cloning utilities underpinning tokens and secure data handling.
- Base64URL Encoding: Encode binary or string data into URL-safe base64 form for use in tokens and cookies.
- JSON Deep Clone: Produce an independent copy of a data structure via JSON serialization for safe mutation.
- JWKS JWT Verification: Verify a JSON Web Token's signature by resolving the signing key from a JWKS via a JWK-to-key conversion.
- JWT Signing: Create a signed JWT for use as an authentication/authorization credential.
- RSA Key Generation: Generates an RSA public/private key pair that a user can rely on for cryptographic use.
- Session Cookie Size Estimation: Estimate the byte size of a signed session cookie so callers can keep within cookie limits.
- Token Confirmation: Confirming actions via issued confirmation tokens that can be consumed once.
- Token Request: A user or system can request a token through a dedicated operation.
What was analyzed
- TypeScript · 4,902 files · 594,209 lines
- JavaScript · 770 files · 130,262 lines
- JSON · 661 files · 68,045 lines
- Markdown · 253 files · 19,200 lines
- YAML · 56 files · 5,464 lines
- JSX · 38 files · 3,610 lines
- CSS · 8 files · 1,038 lines
- Handlebars · 29 files · 361 lines
- Bourne Shell · 8 files · 305 lines
- HTML · 3 files · 226 lines
- SVG · 15 files · 80 lines
- Other (3 languages) · 6 files · 49 lines
Whole repository: 7,510 files. cloc 2.06 counts 822,849 lines of code in 6,749 of them (1,010,752 lines with comments and blanks).
Where this came from
Extracted by CoreStory V3 (build 4470 with two small engine fixes) using DeepSeek-V4.1-Flash from the public repository at commit 468197a on 2026-11-15. Capability descriptions are from the same run.
- Repository strapi/strapi
- Commit 468197a26158120e13c9d0797c313e9cbeb5531e
- Line counts cloc 2.06
- Rule citations Each rule shown was checked: its quote was compared with the repository source at the cited lines at this commit.
Code excerpts are from the upstream repository and remain under its license (MIT core, with proprietary enterprise directories). CoreStory is not affiliated with or endorsed by Strapi Solutions.
Want this for your own codebase?
Talk to us about mapping the business rules in your repositories.