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...Evaluating DotNetNukeEvaluating DotNetNuke
Previous
 
Next
New Post
10/15/2008 7:07 PM
 

I and looking at DotNetNuke as a possible CMS for my organization to handle content management for about 50 websites plus an Inranet.

I am a developer so I'm particularly interested in how web sites are integrated into it.

I gather that most CM systems require sites to be embedded into them somehow (if not developed inside them). Is it possible to easily add and remove sites to/from a DNN installation?

Can only sites developed in .Net be added. What about pre .Net ASP sites?

I realise these are fairly basic questions but I could't find answers on the site.

Regards rb

 

 

 

 

 

 

 

 

 

 
New Post
10/15/2008 8:06 PM
 

I am not really answering any of your questions but I did post a similar question in the forums. I am also evaluating dotnetnuke for managing multiple sites and also being able to migrate existing sites from our old CMS to this.

Perhaps we can share discoveries?

 
New Post
10/16/2008 9:28 AM
 

We'll start with the easy questions --

You can't "add suites" to DNN, you create the site in DNN and migrate the content.  DNN uses portals as individual sites, so one DNN installation can handle multiple portals, or sites.

DNN is not a tru CMS, it's a portal framweork.  There are some CMS functions built in and you can add modules that have complete CMS capabilities including workflow management.

To really find out how DNN works, download the Install version, install it on a system and try it.

Jeff

 
New Post
10/16/2008 10:06 AM
 

It sounds like to me you have a number of existing sites that already have your CMS info in it and you are looking for one location to aggregate out that information.   You could always embed your info into a DNN page using an iFrame but the power of DNN is that you can start to bring together all of that information into the Dotnetnuke framework.

Jeff is right when he says download it and give it a whirl.  You will discover quickly what you can and can't do.   The great news is that what DNN can't do out of the box, there is a good chance that a module exists that can do it.  

We can describe DNN until we are blue in the face but until you use it you will never understand how powerful and expansive it is.

Stuart


Hilbert Solutions, LLC
Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com
A DNN Service Provider
From Module Development to DNN Upgrades, your one stop DNN Shop
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Evaluating DotNetNukeEvaluating DotNetNuke


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