Is this thing going to be able to cater to my current and future requirements? Would it ever lead me into a dead end?
While there’s no simple answer to this, I often request teams to identify their absolutely non-negotiable requirements from the perspective of all the involved stakeholders (content team, marketing team, devs, etc). And then, evaluate the CMS capabilities against those requirements.
In my experience, I have found Strapi:
During all of my Strapi implementation projects, I come across a couple of requirements from teams that are not doable with Strapi (unless we modify the core Strapi code). For teams that are ready to work with work-arounds for such requirements, Strapi works out really well from the dev effort vs gains perspective.
I have also interacted with some teams where all their requirements are absolutely non-negotiable (eg: how they would like to navigate around the Admin UI, how the media upload form UI should look like, etc). I recommend such teams to build an in-house CMS.
A list of posts based on my experiences with Strapi.