Hey @alexandrebodin,
Thanks for your explanation, I understand your point of view but I disagree with the reason.
To me everything the content editor does should be doable via the API. Before being a CMS, Strapi is an API builder, and that’s what makes it awesome.
Following what you say, this means that I couldn’t implement scheduled publishing with the native draft & publish feature ? Also, many clients may ask for (or already use) an agnostic custom admin which just plugs into any headless CMS or content API.
If so, using Strapi for these use cases would mean having to redevelop the same features from scratch and adding “duplicate” fields, wouldn’t it ? This would feel hacky IMO.
This is not my product and you definitely know a lot more about the vision than I do, but I love the flexible aspect of Strapi and to me admin features should go alongside their API implementation.
Please let me know if anything evolves on this matter, it’s an important subject for my team 