Right now I am battling the decision of proprietary vs. open source. There is a definite need for You Design It to go to the next level by implementing a Content Management System. Here is my disclaimer first though - I am not an expert on the subject of “Proprietary vs. Open Source”. I can just write about how it relates to our situation.
There are a few factors that we are considering before implementing a CMS, but here is why we are leaning to the open source option:
- Which option has a better return on investment? The most important factor is the cost because we have to follow the ROI so closely. Typically open source is less expensive because the development has already been done but there is still a fee to implement. 9 times out of 10 this integration fee costs less than custom development. Depending on how well our system was built (less hard coding and more object-oriented) will determine the cost.
- Does it fit our needs? We have decided on the Content Management System out of all of the open source options and it is really powerful. We have spec’ed it out to find that it more than covers our needs. Plus, since it is open source, we would get to benefit from the always increasing features and improvements as they are available. The flip side would be to go proprietary and just create what we need to accomplish our strategy. Any features thereafter would incur more costs as they are needed.
- Can it work with our existing hardware? This is already going to be an obstacle that we will face because our current servers run Windows and the content managment system works best on Linux. I have had a continual problem with our servers anyway, so this will provide us with a good opportunity to migrate to a server farm with 24/7 support.
- Does it scale for the future of our business? I eluded to the answer to this one in #2. Given the nature of open source, we should see some good extensions and improvements to the system that will allow us to grow. Most of these features are very competitive with what is hot in the market at the time they are created.
- Which implementation is quicker? Undoubtedly plug-and-play is almost always faster. They are built for integration and most of the discovery process is already taken care of. Going custom in this case is kind of like re-inventing the wheel.
These are our most immediate general concerns. I am sure there are going to be a few more roadblocks regardless of the route we take. I will keep posting about our efforts on this subject……..