So much powerful functionality, it's almost a shame that all of this is used for a mere CMS. I would be really interested to learn how to build an ERP system with everything that a typical ERP customer would need - custom forms for inventory entry, document workflows, reports, PDF printouts of invoices, scheduled actions for ETL, versioning, audit trail, ADFS auth integration etc. Would Orchard help with this or would it get in my way too much and I would be fighting against the system?
Orchard would help quite a lot, hence why we also use it in all of our web projects. Orchard is more of a foundation to build ASP.NET Core web apps, with all kinds of framework and user-level features, plus CMS features. This video focuses on the CMS features but that doesn't mean you can only use them, or you have to use all of them. Furthermore, "content" can really be anything that's user-editable and presented to other users, don't just think of pages or blog posts. Much of what you describe is built into Orchard in a turn-key way, or Orchard's built-in features can be used to model them easily.
You mention in the user management section that you can setup roles so one role can create a blog post but not publish while a separate role can publish. I'm trying to configure that exact same setup but can't seem to get it to work. If my role who cannot publish "content creator" does not have at least the "Publish or unpublish {securable content type}" permission, then the ability for a user with the content creator role cannot see the menu options to create a new blog post. Maybe there's something I'm missing but it doesn't seem like you can restrict roles in that way out of the box.
That shouldn't really be necessary. The permission that the New menu checks for (but keep in mind it's just a shortcut, not the only way to create content items) is the Edit Own Content one. If your role has that, and the given content type is Creatable then it should show up there.
@@Piedone The content does show up in the Content Items menu for the users in the content creator role however so does all the other creatable content types. The user can attempt to create other content types but is denied. I don't like how that user can still see that other content types are available for creation even though the user does not have permission to do so. My solution to that was going to be creating a new Admin Menu scoped down to the specific content items needed per role. My problem is that the user must have publish permission to even see a content item menu node. Just having edit without publish won't display the custom menu node.
@@jessegreenfield9838 If you think something could be made better in Orchard please open a feature request here: github.com/OrchardCMS/OrchardCore/issues
