Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN compared to commercial CMS solutionsDNN compared to commercial CMS solutions
Previous
 
Next
New Post
9/13/2007 6:36 PM
 

I am actually in Toronto right now for a conference until tomorrow afternoon and have been talking to several people with similar needs here regarding this issue. All info I am amassing is being shared with them. Many have needs in these areas.

 

~B

 
New Post
9/13/2007 7:53 PM
 

Barbara,

I noticed your post and your current situation is very much in line with a current client of ours. My company, E-Cubed, had done a lot of work with a variety of CMS solutions over the last few years. Virtually all solutions have been using commercial software including ATOMZ, Marqui, Ektron, Contribute, Publish, etc. We've also played with several oepn source solutions including Joomla, Typo3, PHP-Nuke and DNN Nuke. We also have developed two custom Cold Fusion and ASP based solutions. We've abandoned our self-developed solutions since it is impossible to keep up with standards etc. and stay competitive. We investigated a variety of solutions for a number of clients and standardized on Marqui (SaaS) for our smaller projects and Ektron for our larger and more strategic solutions for clients that require a cornerstone type of application for strategic publishing needs.

Our research and I'd love to see what you've uncovered as well as the responses attatched to this thread are that the Open Source marketplace is dominated as you've already discovered by people with a more technical background or larger IT staffing needs. Vancouver, where we are situated, has a very strong OpenSource community and is home to some leaders in that field. I know from the various associations and events that I've attended where OS is the topic these observations are correct.

Not knocking the community as I think they are doing several things very well and in many cases much better than the 'old school' software establishment. However they are largely technically focused and the solutions tend to gravitate towards that genre.

I don't want to start a war on this topic but from reading your posts I do not see your questions being answered. We are a shop that specializes in usability and end user satisfaction. We do not typically deal with IT teams but the marketing and editors/users of the CMS system. In our history of dealing with many professional organizations of significant size who have needs that seem to parallel yours (aside from page count) they are dissatisfied with their previous CMS situations and are seeking a solid CMS solution that represents less risk as they become more and more dependant on it for bi-directional communication.

Where we have seen some success with OS CMS solutions are where a more community focused approach needs to be taken. This may or may not be what or where you are headed. Our experience in this area again is with smaller organizations that are looking for more cost efficient solutions because they are typically NFPs and others with limited or no budget and or an organization where their solution is not deemed mission critical.

Just My $.02.

Very interested in this thread as well as the other one looking at DNN for educational facilites in this forum

 

Kyle

 
New Post
9/13/2007 10:13 PM
 

Barb,

Personally I've only used a few CMS systems outside of DotNetNuke, the largest project being Microsoft's CMS, and I can without a doubt say I hated every minute of it.

Unfortunately you come to an opensource project looking for questions that most of the community will not be able to answer. You're looking for a consultant who has implemented other systems as well as DNN, finding someone like that who actively participates in this community is going to be hard to find.

The folks who dominate the discussion on these forums are people such as myself and Mitchel, the technical folks who understand how DNN works, have worked with it for years, and provide free support to the community through these forums, our blogs, and other outlets. We enjoy supporting the community, and giving back to a project which gives us so much at the same time.

Chris

 


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
9/14/2007 11:28 AM
 

I can't answer your question directly, but I can say that I am very grateful for DNN.

I have built two websites with it with myself as sole administrator and technical support, even though I have no technical or programming background at all.

I agree with those who say that upgrades and 3rd-party add-ons should be tested carefully before putting them into production, but I just assumed that was good practise in any case.  I have found the upgrades to be reasonably problem-free, so far, and I've gone through three or four minor ones.

The support here is a bit hit and miss.  On the other hand, just the other day I had someone hold my hand late into the night to help me solve a problem (thanks, aarsys), completely free of charge.

I looked at other open source solutions but they were all far beyond my technical limitations.  Commercial solutions were beyond my budget.

Not sure if this helps you or not, but I thought you should hear from someone who is an end-user rather than a developer.

 
New Post
9/14/2007 1:47 PM
 

Bottomline - Pro/Cons

Open-Source Solutions

  1. C - Require more study and dedication from you and/or a willingness to engage 3rd party support
  2. P - Certain OS solutions have more integrity in that they adhere to standards
  3. C - OS communities can die out
  4. P - I see little risk of DNN dying out
  5. P - You have the source if anything does go wrong
  6. P - There are always a few uber-geeks out there willing to help
  7. C - Sometimes there are too few uber-geeks
  8. P - You can always build your own modules using known interfaces
  9. C - Documentation may be shakey
  10. P - I think DNNs documentation is good

Products

  1. P - May be more effective for your needs (I highly recommend a Needs versus Features Analysis)
  2. P - May fit your technical ability and range (in other words, may be better for small teams or for those without the time to dive in technically)
  3. C - You are basically relying on the integrity of the principals who run the company.  You hope that they are not so obsessed with making money that they continuely cut corners.  I have seen this happen too many times
  4. C - The Product may become slaves to the flash and glam of releasing new features and lose sight of the basics
  5. C - Costly
  6. C - Tend to lock you into their system and make it difficult to migrate away (captive audience syndrome)
  7. C - Despite being a Product, documentation can be shakey
  8. C - If you need to make a modification you are generally dealing with a closed system and you don't have source.  Unfortunately Product companies make more money when the systems are closed (but with the illusion of being open) because it requires you to engage their Professional Services.
  9. C - The company is always trying to upsale you.  I have worked with products where I have had a maintenance license that gives me the rights to all major upgrades, only to have the company create a New Fork, rename the product, and require me to pay additional license fees.  Criminal!
  10. C - You are trusting that the company provides enough competent support personnel
  11. C - You are trusting that the company has your best interests in mind

Anyone else want to add to the lists?


-something clever or funny.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN compared to commercial CMS solutionsDNN compared to commercial CMS solutions


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out