Workflow and Versioning for DotNetNuke, a true CMS module

Workflow and Versioning for DotNetNuke, a true CMS module

Earlier today we had a customer post a question in the forums on www.engagemodules.com regarding using Engage: Publish as a replacement for the Text/HTML module within DotNetNuke.

That is definitely one of the use cases we have for Publish, though have not promoted that much. Using Engage: Publish as a replacement for the Text/HTML module gives you actual CMS functionality within DNN. You can now have versioning and approvals on your content for your website, rather than just giving access to content editors who then can make live changes on your website.

For the steps to configure Publish as a Text/HTML replacement check out the Wiki entry I updated today on the topic.

Recent Comments

There are currently no comments. Be the first to make a comment.

Add Comment

Please add your comment by filling out the field(s) below. Your comment may need to be approved before it becomes visible.
Enter your first name for display with the comment
Enter your last name for display with the comment.
Enter your comment here.
If you can't type DNNRocks in, you can't post, plain and simple.
Submit Comment Cancel

Chris Hammond

Chris Hammond is a father, husband, leader, software developer, photographer and car guy. Chris focuses on the latest in technology including artificial intelligence (AI) and has spent decades becoming an expert in ASP.NET and DotNetNuke (DNN) development. You will find a variety of posts relating to those topics here on the website. For more information check out the about Chris Hammond page.

Find me on Twitter, GitHub and LinkedIn.