Last post Jun 12, 2006 02:19 AM by JohnVndnBrk
Jun 08, 2006 01:03 PM|siliconhorn|LINK
Let me start by listing some of the main features of the portal:
Given the above feature requirements, is DNN a viable option? If so, what is the best way to use DNN?
Is there a way to not build the portal on the DNN Framework, but rather just use the DNN Class libraries/functions for some of the CMS features we need?
I have seen the sites listed in the showcase section but none of them come even close to what I have in mind. Has anyone tried to build a site with similar or custom functionality through DNN?
Any feedback will be greatly appreciated!
Jun 08, 2006 11:13 PM|SamTanner|LINK
My 2 cents...
You are talking about implementing a specialized portal site with specialized functionality. I'm sure you have done the research to find an out-of-the-box solution, and of course there isn't one. So, the choice becomes build from scratch versus customizing
an existing solution with similar capabilities, right?
There is nothing in your statement of requirements that cannot be accomplished with dotNetNuke. That's not to say it won't take some study, some custom code, maybe some money, and some work. The great thing about DNN (to me) is, you get a FREE robust and
scalable framework application, over 50,000 lines written (and tested) using current "best practices", documented source code and examples included. This framework provides you with the backbone of what could be most any web application: the systems and providers
for security, roles and memberships, authorization and authentication, data access, navigation, file handling, etc. etc. etc. ad nauseum. Along with this comes the knowledge that the system is ever advancing as new technology opens up.
There are hundreds and hundreds of custom modules written and available either for free or a modest price, giving DNN all the more functionality just by plugging these modules in.
Have a peek at one of my pages listing all the modules I currently have installed. There are many, many more as well. Each of these modules was written by someone capable of extending the framework - and if you get in a jam, there are lots of people anxious
In summary, I wouldn't hesitate to use DNN as a starting point for your project. Of course you'll want to look at others, but DNN should definitely go on your list.
Hope this helps...
Jun 12, 2006 02:19 AM|JohnVndnBrk|LINK
My recommendation would be to download the DNN portal software and setup a local installation to become familiar with its features. Many of the needs you have noted above are part of the DNN portal framework. I would also recommend the snowcovered.com
for custom modules. Google "Cathal" for a list of free modules for DNN, as he keeps a nice list of what others are doing and offering free of charge.
I do not think that you can easily partition some of the Desktop Modules to be used in a different portal, say, that you or some other organization created, but you could gleen some insight into examples that would help you to build your own modules. I
would imagine if you did so, though, you would find that staying within the DNN framework is a rather good choice.
If you need assistance in setting up your portal post your questions here or on the DotNetNuke.com forums.