Strapi Recenzje i szczegóły produktu

Strapi enables us to create a backend and CMS at the same time using a web interface while also enabling us to fully customise and add extra features to our backend using code. We're able to create graphql routes for each model or content type we add, and these routes have the full CRUD functionality, this has saved us a lot of time while building.

Some of the documentation isn't as helpful and is sometimes not up to date, this is something that has caused confusion for our developers while building or making certain customisations, so it's the one area that could definitely improve. The plugin marketplace is also very limited for v3.

We're solving to create a CMS that non-technical members of our team can use, and also reduce the learning curve for new developers joining our project, Strapi enables us achieve both with it's interactive admin dashboard.

Super fast to set up Highly customisable Active development roadmap GraphQL component focus

It's still pretty young would love to have a hands off cloud hosting option

As a small climate change charity we have been able to build a JAMstack based on strapi to replace our old WordPress setup. Its super-fast, secure, and just works.

I really love the simplicity of the content API. Normally I would have to write my Routes and Controllers inside Node and Express, which can take ages. With Strapi I only have to set them up in the UI, which is easy and straight forward!

I Would love to have the possibility to directly add/change UI layouts in the BackEnd. It would be great to to have a clickable "List" view of all connected Relations, which is currently not possible and makes it a bit more complicated.

My main Problem/Benefit is time saving. With Strapi I can fully focus on getting the Frontend and Application Logic done, while using Strapi as a "Visual Database" management system.

Strapi is highly customizable and easy to use so we were able to use it for entering content into a game we developed that is unique and custom built - Strapi was the perfect solution for managing the content.

I would've said lack of translation was a big hole but that issue was resolved in April and we're now in the process of translating our game into multiple languages. So no complaints!

We have a digital game that was designed from the ground up, with very specific content formats that don't match any existing content management systems. They combine graphical elements (uploaded as SVGs), text, interconnected collections, etc. The game is content intensive so it required a user-friendly interface that was highly customisable. The introduction of translation functionality has enabled us to now develop a multi-language version of the game.

Just the best CMS. It's headless and help to make a secure and easy database and authentification backend system.

I didn't find the way to secure access to media library.

I had a simply and secure authentification system and database system.

Strapi offers a lot out of the box, and most of it can be had with the free community edition. This is great for those looking for something that you can quickly get up and running. For more advanced functionality, you can fairly easily write custom code / plugins for more complex situations.

CMS publishing workflow is still primitive. Currently only supports a draft and publish status. If a conent item was already published, there is no way to test changes out without unpublishing the content item entirely.

We are creating a somewhat simple CMS backend for a marketing website. After the initial effort to create the components and collection types, it makes content creation and updates a lot easier than having content and pages hard coded on the marketing site itself like we were doing previously.

- Support GraphQL. - Highly customizable. - Good documentation. - Update frequently.

- The free plan supports only three roles. - The interface is ok but not as friendly as other CMS I have used.

I have searched for a CMS support GraphQL to connect to my frontend application. I found Strapi to support GraphQL with ease. Besides, the loading speed is fast.

The user interface for Strapi is incredibly modern and intuitive. As a beginner developer, it has made things a lot easier to grasp as I work my way through tutorials, the Strapi Academy and the documentation. Additionally, the support and help I received from Strapi before even getting started was outstanding.

As I expected with moving from WordPress to Strapi, there are some features that are easily available in WP that aren't in Strapi. The community is active though and so usually there are plugins to help with most general cases.

Having a CMS that is detached from any specific frontend makes updating repeating content very easy.

The hability to self host the product and keep the data at bay. Strapi makes it easy to create and use a customized api that meets the needs of the association in terms of managing its websites and applications.

The product is still relatively new, some things are still not fully working and working with internationalization is still quite challenging.

Strapi helps us moving from a slow and monobloc solution to something more agile. We can focus on content management and creation, and less on website maintenance.

Good balance between pre-developed structure and flexibility for customisation

That the plugin community is a little limited at present

Smaller organisations like ourselves need frameworks like Strapi to rapidly develop solutions to meet the growing digital demand from Wadyumers.

strapi offer a great interface, user management et role access base. all that is combined with a great API providing all the information we need about the content of our website

the lack of information and guidance in the interface. I have spent 20 min trying to set roles for my user for allowing them to have user management without giving them full access but I could not succeed, I guess is because I have to pay to have more users.

A client asks me to build him a showcase/portfolio website but he also wants to manage the content and article. I had to find a CMS but not a WordPress. Strapi resolves my issue by offering me exactly what I wanted.

I really like Strapi, it make products management very easy and it's a very ergonomic software.

The only think I don't really like is that to change the defaults role, you need to have a premium subscription

Strapi is solving management problems by making them easier to manage

The plugin system is generally really simple to get started with and enabled us to quickly extend our installation, such as using Cloudinary as a CDN. Similarly, it's proven quick to build with, and the plug-and-play GraphQL support meant we could integrate with our TypeScript codebase easily.

Sometimes the errors when plugins conflict are really obscure, and I wish that content management was viewable as a top-level navigation item, instead of it being a sub-menu.

We replaced our website and needed CMS that was more customisable than we were previously using. It has so far proven itself in this way. Specifically, our team seems to be able to navigate it with ease.

Super quick to get up and running. Allowed us to build out our CMS quickly, allows us to generate our site dynamically and allow our non-technical staff to view all of our relevant data items and page content without hassle.

It would be great if the top-level navigation could be customized. It would be great to bring out certain object types such as from within the content manager and "pin" them to the top-level navigation.

Providing a centralised API/CMS solution that we can sync our various other tools such as Salesforce too, allowing us to request data easily and in a quickly customisable manner.

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.

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.

It allows an almost unlimited number of content types. The relations content types are most useful and helpful types.

The different architectures between strapi v3 and v4.

Choices of different frontends working with Strapi. I am working with Gridsome but it's rather hard to work with Strapi v4 then v3.

Strapi helps me to focus on front-end development by making backend and API implementation very fast and easy !

Backend interface should be fully responsive. Adding entries from a smartphone is not simple.

Get rid of a fastidious API/backend development

Strapi makes it super easy to set up APIs to retrieve, edit and create new content for a static website. It's super easy to work with out-of-the-box but offers the flexibility to customize to each users need.

I think the biggest downside of Strapi so far is the outdated documentation for plug-ins. Both Strapi and Wadyumers heavily documented V3, but that documentation doesn't necessarily translate to v4 that well. With a little bit of finagling, I was able to get my plug-ins to work, but having updated documentation of out-of-the-box features would be great!

The main benefit is that of the headless CMS in general, but also the execution of that idea. Spinning up a new instance on AWS or similar platforms is really helpful!

Strapi is perfect for quickly setting up microservices and start serving data. It's flexible enough to support many different data structure and with GraphQL API out of the gate it's really easy to integrate with an existing infrastructure.

There are some downsides to it, one of the biggest for us being the lack of ability to create label/value lists. Although I understand that this is a limitation connected to having GraphQL support I still think you should be able to "fake" that functionality in some other way. At the moment you have to create a new collection for every category/section that you need and that can become quite cluttered in the admin UI.

The main benefit is that of the headless CMS in general, but also the execution of that idea. Being able to quickly spin up a new instance on GCP or similar platforms is really helpful