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

HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...Should I switch to DNN or keep my current website?Should I switch to DNN or keep my current website?
Previous
 
Next
New Post
3/28/2013 2:49 PM
 
Hi,

I am about to decide if i switch from my asp.net webform website to DNN CE.
It would be cool to get some input from experienced DNN admins/developers/users.

The URL of my website is www*finanzen-portal*net. Its a german website about finance stuff.

What I have developed so far:
- Q&A system as you can see on the front page (I need to write my own Q&A module for DNN since the existing one here http://dnnqanda.codeplex.com/ doesn't fit my needs)
- I can publish articles (how can I let users publish articles with DNN? do i need an extra module?)
- each content (q&a or articles) can be tagged. users can search for specific tags (i think this works out of the box with DNN)
- I can inject usercontrols directly into my content. If i write "[usercontrol1]" in my Question, Answer or Article it will be replaced by the actual user control. (I think I have to write my own DNN module for that)

Why do I want to change to DNN?
- Better overall content management
- I want to publish articles with a nice WYSIWYG editor.
- A alot of my content is indexed by google but not showing in the first pages of google search results. I hope that DNN offers better search engine optimizations out of the box than my approaches.
- Support for mobile devices like smartphones and tablets.
- I like the idea of having a CMS for the basic features and extend it by your own modules. but to be honest I haven't even started a single module so far. don't know how hard it is.

What prevents me switching to DNN?
- It was a lot of work to build my website and I have to rewrite the most of the code to DNN modules. At this point I don't know if it is worth all the effort.

Thank you
Christoph
 
New Post
3/29/2013 6:42 AM
 

Hi Christoph,

For article, question/ answer and related feature dnn community blog, form & list module can be utilised which are free. Also there are plenty of third party modules are available in dnn store. For mobile device support, in dnn store you can find responsive and multi-colour skins which will be utilized both for browser and mobile devices.

As your website already in asp.net/ webform it should include less effort in order to convert this to dnn cms. And as per me if you are in ASP.Net and want to switch to content management system then should go for DotNetNuke.

Thanks
Sibabrata
Mindfire Solutions

 
New Post
3/29/2013 6:54 AM
 

Depending on how you have coded your current site elements - it is likely that it would not be a major job to portal those elements to dnn modules.

DNN modules are really just a  usercontrol on steroids with a dnn wrapper to exposed elements of the dnn core to the usercontrol and its children.

All dnn modules themselves are also consumers of usercontrols - including the asp:net core ones, dnn:wrappers which extend many of the asp:net core controls - and the most powerful ones being pretty much a full set of wrappers for the telerik asp.net ajax control collection.   This means your modules can include a telerik radgrid or ajax wrapper at no extra cost - with the only exception that you need to do the coding manually.

Westa

 
New Post
3/29/2013 7:55 AM
 
Like Wes stated, if you have the code, converting it to modules may not be as much of an effort as you think.

I've done something similar to my company intranet. While it still took some time to make the modules, I used almost the exact same code to do so.

Mark
 
New Post
4/1/2013 10:46 AM
 

A good thing to remember as well, with switching to DotNetNuke you will be going to a platform that is getting constantly updated ans ungraded. So you will not have to worry about do that with your own code. Plus, the module community is very quick to get in line with the latest updates to the core, so you can really save some time and effort. 


Johnny Gregory Senior Technology Consultant o: 1.877.743.8366 x701115 skype: johnny.managed Managed.com ​ Advanced CMS Hosting and Support for Business Websites DNN - ElcomCMS - WordPress - nopCommerce - Drupal Need a Developer? DeveloperMatch.com
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...Should I switch to DNN or keep my current website?Should I switch to DNN or keep my current website?


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