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...Tranfering an existing site to DNN - Management perspectiveTranfering an existing site to DNN - Management perspective
Previous
 
Next
New Post
2/5/2006 8:42 PM
 

Hi.

I am new to DNN. Is there a proper workflow from designing to the development phase? Currently our designers just creates the sites without much thought about whether DNN will be used in the future. And each designer, creates sites differently.

Is there a process of transfering an existing custom site to DNN? Basicly, with an existing site, what needs to be done before we can DNNabled it? Following all the online tutorial dont seems to give me much feel of how it could be done as they are mainly basic and follow the demo structure. The designers does not know about the concepts of things like containers, and the whole DNN stuff. Is it their responsibility or the developer's?

Thanks

 
New Post
2/8/2006 11:49 PM
 

This isn't really a DNN specific question, but it is something that DNN folks face.  In general, one of the biggest hurdles for designers is the idea of following ( what may appear to them as ) a rigid formatting strucutre... by which I mean "panes".  The whole notion of having particular "zones" of content requires a little learning curve.

As for transferring an existing site... it depends entirely upon what that site does and how closely the behavior must be duplicated.  In most cases, it is possible to achieve near 100% visual duplication, although realistically... you'll want to change a few small things... like adding Site Search if you did not have it before.  Menuing systems can be a little harder to duplicate, I just finished a conversion for a friend of a friend ( I don't make a habit of this ) which required the use of a Panelbar menu which required a custom wrapper to fully duplicate their exisiting functionality.  In that particular case, it had to look the same to preserve investment in existing marketing literature.

Start by converting a skin... and itemizing the "functions" that the website needs to support.  Does it have forms?  Media?  Other interactive components?  Make sure you can duplicate what you need to in an acceptable manner, before you start.


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Tranfering an existing site to DNN - Management perspectiveTranfering an existing site to DNN - Management perspective


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