The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
In past few weeks I’ve seen many people expressing their concern about the (quantity of) features in Sitefinity 4.0. Coupled with the new pricing scheme, some people wondered why would they go with Sitefinity when there are cheaper or even free alternatives that offer the same features or even more features than Sitefinity. As a developer, and I’d say someone rather familiar with the CMS industry and products out there, I decided to shed a bit of perspective on the whole “same or more features” for free or less money. Now, I am not going to go into the whole pricing thing, since many people far more competent than me have already answered those questions at numerous places.
However, what I aim to do with this series of blog posts is to demonstrate what we mean when we say terms such as “workflow”, “taxonomies”, “extensibility” etc. and then let you make your own judgment about the alternatives which provide “same” features.
So, in the first post of this series, I am going to touch on the workflow. When we say workflow, we don’t mean a way to change a state of the news item from “Approved” to “Published”. From our perspective, workflow is a way in which business gets done. Sure, changing the state can be part of this logic, but just changing the state cannot be called workflow (well, it can, but it shouldn’t).
It is our firm belief that it is responsibility of the workflow to accommodate the ever changing business requirements. Workflow has to do this intuitively. The best way I can illustrate this point is to show a possible real world example of this approach.
Your company has recently grown a lot and you have found yourself in a situation with many young, fresh out of puberty employees. They keep mentioning/trashing your competitors in their blogs, and since that makes your company look cheap, insecure and a bit creepy, you decide to end this practice.
If you would to solve this issue without a real workflow, it would look something like this.
You would hire a programmer to hook up to the events of CMS and perform some hard coded logic on the publish event.
Problems with this solution:
I have developed a short example that demonstrates how to do this. Note that the actual code that performs the replacements is quite primitive, but will do the job of demonstrating this principle. Generally, you’d implement this with more intelligent regular expressions.
Download the source code from here (setup instructions packed with the code).
If you are just interested seeing this in action, you can take a look at this video.
View all posts from The Progress Team on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
Copyright © 2019 Progress Software Corporation and/or its subsidiaries or affiliates.All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.