Strapi Отзывы и информация о продукте

To-go tool for developing a fast and modern WebSite!

Nothing significant to mention, I find the experience very satisfying

Ready to use and secure back-end for your website

With strapi it is possible to accelerate development without losing flexibility for customizations

changes in product usage (Bracking changes to version4)

Back end easy

Offers a good way for students to understand the development process.

Cloud hosting is not yet available, which could prove to be an issue for some.

Strapi will allow me to understand the development process as a designer.

The documents are very informative. Easy to get started.

Not have cloud support, need to self host everything

Strapi brings the headless CMS. I love the built-in CRUD system.

The extent to which it just works out of the box. The most important configuration can be done in GUI form for live previewing the UX for your nontechnical operators.

Large extents of customisability are baked into the packages, meaning to edit things like the landing page, while not techically important greatly impacts the UX, requires forking the project, adding to the tech debt for updates

We needed a highly customisable CMS for handling accessibility data of different buildings on a college campus. Other prebuilt systems were configured for blogs, or products, and was not as blank slate as Strapi

Most websites (if not all) require dynamic content to be put, edited reviewed, and deleted from their website, so I used to build (reuse) an admin dashboard for each use and manage the database choosing and connection, backend, etc... with Strapi, I can just create a new strapi project, hook it with a database hosted on a PAAS service, and the CMS part is done! it's an amazing time-saving solution and more scalable because a whole company is backing it up with updates and fixes thanks to their team.

Things to improve are the language available in the admin interface, Arabic for example is available as an option but about only 20% is translated. RTL Supports languages like Persian and Arabic. Customization of the title just next to the icon, and also to the colors of the interface (more themes).

Every app needs content (Mobile app, website, desktop app, etc..). Strapi is solving the problem of modeling content and providing it to apps in an ease-wey that saves a lot of time and effort. What used to take some times weeks to prepare, which is preparing the backend, modeling the database with raw languages like MySQL etc..., building routes to access the database, providing roles for authorization, etc.. is now done by strapi, so you only focus on the task at hand, not the abstractions that come with each project (authorization, sign-in-out, admin dashboard, etc.).

We have a lot of very specific content formatting and structural needs. No matter what I've thrown at Strapi so far within the CMS, it seems to adapt well on the fly. Something I like a lot is being able to customize the administrative front-end for our editorial team. This affords them an incredibly user-friendly interface, all while guaranteeing a stunning experience by connecting it all to a custom front-end. The opportunity for us to use this at scale for future content distribution needs is already very promising. It's genuinely quite fun to use once you familiarize yourself with the feature set.

Working with content "collection" types feels a little different from past CMS work, but once you get the hang of it it makes building richer content very fast and reliable. The distinction between "Saved" and "Published" states also takes a little getting used to, semantically. Lastly, we're currently figuring out how to make certain input fields feel more familiar and easier to parse through. But these feel like solvable problems that are far outweighed by the positives.

It's allowing us to better share control over our content distribution pipeline with our colleagues, and introduce more consistency to our workflow as designers and developers. It's ultimately saving us a great deal of time and energy, and guaranteeing our end users will receive a more consistent and timely experience.

The Out of the Box experience is amazing. It comes configured to already provide much of the functionality I need, saving my team a lot of development time. Additionally, the plugins available fill in any gaps. My team is also happy to know that the project is open source so that, if needed, we can extend the code to support any use cases not covered by Strapi or its plugins, although we have not had to do that yet.

There currently is no v4 docker image available and it seems that an official one won't be available for a while. The Strapi team have posted a guide on how to build one yourself, created by a trusted community member; we've used that successfully. But we'd be happier with an official published image.

It provides a configurable API GUI that I would otherwise have to code from scratch. It has saved me tons of time and improved my time to market.

It is the most advanced open-source Content Management Framework to build powerful API with no effort.

The account-creating process took me longer than I expected.

It helps to create a powerful API while it is handling content management.

East to get started, customize and scale.

Migration from v3 to v4 is a bit tedious, hopefully, will be improved over time.

Implementing headless CMS, much faster time to develop...