The author of this article shares their vision for Strapi, an open-source headless CMS, after introducing several changes to its interface and core architecture. The project was initially focused on providing a framework for developers to build APIs quickly, but the authors soon realized that they needed to redefine their target audience and create a more user-friendly experience for both front-end developers and content editors. The author explains how these design choices were made with high confidence, despite being complex, and how they aim to improve consistency in the interface and provide better support for non-technical users. The article also touches on the challenges of developing a developer tool and the importance of separating technical aspects from visual interfaces.