Strapi Avis et détails du produit

Just watching an idea become a meaningful experience for our team and customers do not happen simultaneously. Especially, when we had to use two different teams dedicated for ios or android design features or functions. It's the user-friendly interface that's empowering our team to integrate their favorite tools without requiring intense technical knowledge aquisition.

New to Strapi, therefore I don't have any dislikes at the time.

Strapi allows our Non-profit to simplify a fragmented procurement ecosystem for historically underutilized businesses and underfunded social entrepreneur projects that improve their local communities.

The upsides are the customization and flexibility that it gives both the editor and developer

The documentation can be lacking in some areas, but the community is helpful

Building an application for a student chapter that needs to provide tickets to their members for certain events

My organization has been looking for a long time to get out of using WordPress and I've looked into different options, Laravel, a full React-based static site with all the back end handled by a SaaS, but my team loved using the "simple" interface of WordPress and after I found this product and my team loved it, I know this was the keeper.

I'm not too sure if this product has been around for a while or is new, but it could use a lot more plugins that are easy to install just like WordPress and it's easy to use WYSIWYG editors, but other than that this product is pretty cool.

Using a Javascript-based application has just been fun, learning and using getting of a PHP based application I can already see all the speed and usage improvements

The simplicity of having a ready API solution out of the box.

Need more customization options which are for power users.

Cuts down the development time of building and structuring APIs.

I like that we will be able to easily structure and build our course content and have the option to customize to our needs.

I don't like that you can't search between collection types.

It is giving us a customizable CMS that can be integrated with the other software solutions we use.

It's highly customizable, intuitive, and easy to use. There's also plenty of resources out there to help you do what you need to do.

Learning how things work can take some time.

It helps the writing team upload and modify website content.

It has lots of preconfigured customization which can be further customized to make it more useful according to your needs.

It becomes sometimes complex for beginners. It has too much available that become sometimes overwhelming in some scenarios.

Helpful in managing the backend of the jam stack website. It has lots of things premade that can be useful for development. We have a need for CMS that can be self-hosted and Starpi is a good choice for that.

This is by far the easiest solution for a headless CMS solution and even better as an API framework to power whatever your needs are.

Content editor fields are limited in some cases e.g. date input, document selector

Our students need a well-designed and constantly updated platform to support them along the way of their studies.

It helps reduce the time spent for some jobs.

Getting started with Strapi may be somewhat tiring. I hope it would be easier in the future.

Content management is easier with Strapi, it prevents developers from drowning in repetitive tasks.

- Customization - Performance - Plug and play concept

Everything works pretty good. However, some upgrades are necessary to manage better the data and add more functionalities to the UI.

I hosted the entire backend of one of my personal projects. It's easy to setup and you can immediately view and manage the data.

Strapi is super easy to spin up and customizable.

Cannot automatically upgrade from v3 to v4. Merging upstream changes can sometimes take a while if you make customization.

We use strapi as our backend service. Developers can focus on defining their collections rather than writing CRUD endpoints. It also provides a layer to interact with the database.

Easy setup and very simple and intuitive to use.

Our developers love Strapi and haven't found any issues. Have used it in previous projects and will continue to use it.

Helping make managing our database and content on our new site easier.

User-friendliness of system, easy to use for non-tech peopleng

would like to have some features in the basic plan

International management of content for web app

Basic API functionality comes out of the box

There's a bit of a learning curve and custom features will need to be built from scratch in-house.

I am building an internal web tool for housing custom data sets to serve over an API.

Strapi is a flexible solution for the website's backend. It also seems easy to learn for content producers.

We have had some problems with long words in titles (our native language has long compound words).

We are using Strapi for the backend database for our website. It is easy to manage the data of our website with Strapi.

- Devs are happy about easy setup and easy handling - Backend is lean and easy to use - gives enough freedom to develop what you need

- you need experienced Devs to create a good structure for big websites

Strapi is flexible to adapt to your needs. You can go a long way with the free version.

- Easy to use - Good UI - Powerful yet intuitive

- Would like more default plugins - Handling of media files could be better

Building a flexible system that allows multiple types of users to add and edit content. Also, being Headless makes it very easy to consume the data.

In general, the resources are extremely simple and give a perfect speed in developing and deploying applications.

The way to perform the relationship between tables in the many-to-many format is still not user-friendly.

I'm using it to support a simple backend framework to gather human resource information in just one place, much like a blog framework and adding some tooling features.

It's very easy to setup strapi. Difference user interaces help you to create content types, releations and fields without any need to code. It comes with a REST and GraphQL API out of the tools, which provide a very good developer experience.

The GraphQL endpoint becomes slowly once you are using more content types with many relations, but the core team is working on that. Also dynamic zones could be more intuitive to use.

Strapi helps us to organize content that is clearly structured (Events) aswell as generic pages, which are embedding other content types.

the simple and quickly understandable operability

Nothing noticed so far. But im not working for such a long time with strapi, so i will see whats coming next.

I am trying to recreate a website for a university project to better communicate the clarity to the other students and the professor.