Reseñas de Strapi y detalles del producto

It can be used as a simple and easy-to-use CMS without any complications and comes with built-in graphQL support, API tokens with custom permissions, localization and ready to pair with Next.JS! And all of these features can be used under a community license without any fees.

I have been trying it for 2 days, haven't found any issues yet.

Quick and easy to manage content management system

The interface is easy to grasp and implement. Creating carousels and video feed within our app has optimized thanks to strapi.

Its difficult to manage the team and add more users for non-tech people like me.

Strapi is helping us deploy in app banners and carousels on different screens. We also use it for uploading videos in different categories for our in-app training.

Strapi is a great CMS(Content Management System) which provide a lot of great features like easy integration with the product, fast content change, inbuilt editor with multiple formatting options. The content also includes and option to support media files.

Although Strapi is a great product, but there is one thing that can be improved which is the editor provides a very limited formatting options. The editor is a bit basic.

We are using strapi as content management system for our course content in Learning Management System. We also use strapi for managing the content of our blogs and events.

For us, as a non-profit organization with limited funds, Strapi offers one of the best solutions on the market when it comes to headless CMS: - It’s easy to install and configure - It can be deployed to a PaaS (e.g., Heroku) such that we don’t have to deal with the runtime environment, OS and so on - We keep complete control over UI, extensions, data, and models - Maximum flexibility through extensions, i.e., use the HTML editor of your choice - It is open source - Excellent documentation—most questions have been asked and answered before - GraphQL API (it’s an extension)

Unfortunately, this highest flexibility comes at a cost: We have to install, deploy, and test it ourselves, but Strapi is about to launch the Strapi Cloud bringing this flexibility to a SaaS. So don’t take this dislike too serious.

We are developing new projects on a modern tech stack, e.g. with NextJS. Thus, we heavily rely on a predictable and potent API. With Strapi, we can decide whether to consume REST or GraphQL—both work well. Editors get a fantastic user experience with components in models, the media manager, and the navigation extension for drawing the site’s/menu structure.

Overall content management is so great. And the best part is the API services that we are getting out of the box.

I feel Strapi 3 Dashboard UI/UX was better than Strapi 4.

It is solving our scalability issue.

Speed of production and the ability to create custom functions easily in NodeJS through its framework. As much as its advertised as a CMS, its much more powerful than that - i've used it for developing an internal HR system for governments, School Websites & LMS Integrations.

I have not encountered any problems with this application so far.

1) Speed of Production. 2) User Management. 3) Content Management. 4) Ease of Deployment 5) Admin UI/UX

Strapi promotes an API-first way of doing web. It delivers a means to build quickly and efficiently a valuable API, which is what you should expect from the modern web.

Graphic Design could be a little more colorful.

Ship fast standard web applications.

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

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.

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...

The simplicity and effectiveness in content building

I miss a configurable admin desktop panel

I'm developing a non-profit organization backend website with many content types, users management with specific permissions and roles

Speed! The user interface runs incredibly fast making development a snap. Very low overhead compared to something like a headless WordPress install. The free version seems to provide a generous amount of features and the enterprise options add even more.

Haven't found anything yet, our developers have been loving it and it sounds like we'll be using it for lots of projects in the future. Will certainly benefit from a larger community as more folks find out about it and start using.

We are creating a custom app to allow our reporters to send demographic surveys to their sources. Strapi lets us create interfaces for our editors to create forms and reporters to send as well as the actual surveys that are completed by the sources.

I can structure data however I want basing on my requirements. Exposablea s REST API.

Not much so far. It mainly covers all our needs.

We are serving content to our mobile app and web app as well.

Easy to work on backend for frontend developers. Its like drag and drop feature

I think, they should bring a better documentation on how to host it in a individual servers like from Digitalocean or elsewhere

I am workings on a LMS for which Strapi is help me arround

Provides the quickest solution to setup APIs for your frontend.

As it's still growing it lacks some of the features to be used by masses.

Strapi is helping me skip the backend part and focus on frontend by managing the backend all from one place.