Orchard Core is an open-source modular and multi-tenant application framework built with ASP.NET Core, and a content management system (CMS) built on top of that framework.
I don't think it is needed. But if you were to go down that route, I would not pollute the ContentManager with that logic. You could introduce ContentService that would wrap that logic.
Currently, it seems that the most complete management of content items is done through the controller.
Can we extract the logic into the
ContentManager
class to simplify the secondary development process?