What do you like best about Directus?
We’re currently evaluating Directus and it stands out well above the other CMS' we've tested so far. We genuinely love it, because it really is flexible, open (which is great for a technology team who want to expand and improve for our teams), and doesn’t force any specific way of working.
We are self-hosting, which is simple and well-supported. You're not tied into any platform or service. We had it running in our own infrastructure quickly, with no surprises. It's relatively easy to configure, and we stay in control of our data and stack.
Forking and extending the platform works exactly how you'd want. We’ve already thought about a few internal tools we're likely to build. The structure looks like it's easy to understand and modify without having to rewrite anything major, which again is key for us, we don't want to reinvent the wheel.
The flexibility is on another level. You can build the data model to suit your actual project, not try to jam it into someone else's idea of how content should work, again, the fine-grained control of the data is so good.
It's API first, so it's great if you want something that's headless by nature, not transformed into a headless solution.
The admin interface is clean and configurable. You can change how things are displayed, create roles and permissions easily, and set it up for technical and non-technical users alike. Our marketing team like the look and feel and find it easy to produce content. Review collected by and hosted on G2.com.
What do you dislike about Directus?
I wouldn't say we dislike anything, but things we'd love to see changes on, would be:
The APIs are simple to work with. they’re powerful, but not always intuitive. Some operations feel more complex than they need to be, especially when dealing with nested data or filters, once we got the hang of it, it was fine, but took some time.
Query strings can get excessively long. Particularly with more complex filters or relational data. It’s not unreadable, but not the cleanest either, it can be easy to make mistakes if you're not careful.
Image handling could be better. Files are always delivered as separate requests, we get the ID back only, but it's not the end of the world,
we’d just prefer if images / urls could be returned directly in the initial API payload. Review collected by and hosted on G2.com.