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...questions from client about DotNetNuke use as a CMS for their sitequestions from client about DotNetNuke use as a CMS for their site
Previous
 
Next
New Post
12/8/2009 11:11 AM
 

A potential client has these concerns about using DotNetNuke as a framework to rebuild their current web site. I know DNN is one of the best CMS tools available and is super flexible as far as functionality is concerned but how do you tell them that to relieve their concerns?

This is the biggest concern I'm aware of; however, other concerns mentioned include:  DNN not being the easiest to use (admin-wise) or that it might not be the leading open source CMS, or that it's 'behind the times', or that we're restricted by DNN's limited functionality/technology, or that we won't be able to expand as the site grows, our needs change, or as technology changes.  Many of these comments are perception-based, but they exist nonetheless.

Thanks for any comments!

 
New Post
12/8/2009 12:55 PM
 

DNN is an open framework, which can be developed and extended by third party developers or the client themselves.  Due to that nature, none of these concerns apply.  Just remember, the latest and greatest is only that way until something later and greater comes along.  Usually in a week or less.

Jeff

 
New Post
12/8/2009 3:27 PM
 

As far as functionality - As mentioned, DNN is a framework, which allows for, pretty much, any type of functionality your client needs. All it takes is a module [or set of modules] that performs that functionality. Custom development can take care of any functionality that existing modules don't provide.

DNN for me, is the easiest CMS's I've used to admin. First time I used it, I understood how to do things in it. I haven't had the same level of ease that I did with DNN. 

Custom modules can be bought/created to simplify any administration functionality that needs to be made simpler. More cost, but it can simplify any tasks.

DNN's functionality is only limited by the imagination of module creators. :)

 

There is the Professional version of DNN which might make the client feel better about using it knowing there is support backing behind it. 

 

These are just my opinions and thoughts - but I hope they help.

 
New Post
12/10/2009 11:30 AM
 

Thank you for your responses. They do indeed help! :-)

Shelly

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...questions from client about DotNetNuke use as a CMS for their sitequestions from client about DotNetNuke use as a CMS for their site


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