Directus doesn't make sense

Help
1

Please point me to the right direction. I’m comparing multiple headless cms to simplify my tech stacks. And directus caught my attention with its features. But after reading it’s official docs. It start doesn’t make any sense. Most of its guide is for full stack framework (frontend and backend) like nuxtjs and nextjs. Very few for frontend only framework like react (client side).

Directus is a backend. Why all your guide is pointing to use another backend stack like nextjs? Why we need another backend as it’s complicate things. Directus marketed as “headless” Cms. People who look at headless solution usually want to separate front and backend to simplify things not to complicate things.

2

I guess it’s basically because those meta frameworks grew in popularity over the last years and many people got used to them or need server side rendering for performance reasons.

But they usually also provide more features beside server side rendering or server routes. Like improved image, fonts, meta handling or dedicated dev tools for example.

But you can perfectly call into Directus directly from the client!