Repository files navigation

The most advanced open-source headless CMS to build powerful APIs with no effort.

If you are looking for the Strapi code, please see theStrapi Monorepo. The present repository is only for the official Strapi documentation hosted atdocs.strapi.io. Blog articles hosted atstrapi.io/blog andcommunity content are not covered by the present repository either.

Strapi is a free and open-source headless CMS that delivers your content anywhere you need.

• Keep control over your data. With Strapi, you know where your data is stored, and you keep full control at all times.
• Self-hosted. You can host and scale Strapi projects the way you want. You can choose any hosting platform you want: AWS, Netlify, Heroku, a VPS, or a dedicated server. You can scale as you grow, 100% independent.
• Database agnostic. You can choose the database you prefer. Strapi works with SQL databases: PostgreSQL, MySQL, MariaDB, and SQLite.
• Customizable. You can quickly build your logic by fully customizing APIs, routes, or plugins to fit your needs perfectly.

The main official Strapi documentation website is hosted atdocs.strapi.io.

Additional official Strapi documentation websites cover different content:

• Documentation for the older version 4 of Strapi is hosted atdocs-v4.strapi.io and featured in thev4 branch. This branch is not actively maintained by the Strapi Documentation team, but community contributions are most welcome!

• Documentation for the older, unsupported version 3 of Strapi is hosted atdocs-v3.strapi.io.
• Documentation for contributors, which include more in-depth and experimental content for developers who actively maintain and contribute to Strapi, is hosted atcontributor.strapi.io. This experimental documentation is maintained by Strapi engineers and any issue should be reported to thestrapi/strapi repository.
• Documentation for the Strapi Design System is hosted atdesign-system.strapi.io and maintained by Strapi front-end engineers in itsdedicated repository.

The following are required if you are submitting pull requests to the documentation:

• NodeJS >=18.15.0 <=22.x.x
• NPM >= 6.x
• Yarn >= 1.22.x

👉 For more information on how to contribute, please read ourcontribution guide.

Submitting issues help to improve the documentation. If you find incorrect screenshot(s), instructions, or code examples, or if you discover UX/UI bugs on the website, please use ourdocumentation issue template to report them. To submit an issue:

1. Verify the issue is only with one of the Strapi documentation websites. Product-related issues, missing Strapi features, and any issues not directly related to the documentation should be directed at the mainstrapi/strapi repository. Updates to blog posts found atstrapi.io/blog are also outside the scope of the present documentation repository; you can either reach the author of the blog post directly or use thecontact form on Strapi's corporate website if you have questions about blog posts.
2. Follow the issue template and fill out as much information as you can.

Technical questions should be asked using the following resources:

• Open a Q&A thread on ourofficial forum.
• Engage with other community members on ourcommunity Discord server.

Requests for new documentation are highly encouraged. This is not limited to new additions but also changes or more information requested on existing documentation. Please use ourrequest documentation issue template. These requests will be checked by the Strapi Documentation team then transferred to another internal tool outside GitHub for priorization and subsequent actions.

Thanks to a continuous integration/continuous delivery workflow, the Strapi documentation can be updated up to several times a day, depending on the number and frequency of contributions. Weekly snapshotreleases happen on Wednesdays and include a list of changes since the latest release.

For general help using Strapi, please refer tothe official Strapi documentation. For additional help, you can use one of these channels to ask a question:

• Discord (For live discussion with the Community and Strapi team)
• Primary GitHub (Bug reports, Contributions)
• Community Forum (Questions and Discussions)
• Canny (Roadmap, Feature requests)
• Twitter (Get the news fast)
• Facebook
• YouTube Channel (Learn from Video Tutorials)

See theLICENSE file for licensing information.

This project and everyone participating in it are governed by theStrapi Code of Conduct. By participating, you are expected to uphold the code.

Please note that, starting with Strapi 5, strapi/documentation and strapi/strapi package version numbers are not synchronized any more. Strapi Docs are treated as their own product and will follow their own numbering system.