Last post Feb 06, 2006 08:36 AM by xddg
Feb 05, 2006 10:42 PM|msy|LINK
I am new to DNN.
Can anyone please share some light about migrating existing non dnn website to DNN efficiently.
Online tutorials, dont really tell me much, cause all the example uses the same structure as the demo. But in a real world situation, I would like to know who is incharge of the migration.? the Designer or the developer and what needs to be done.
Feb 06, 2006 02:42 AM|xddg|LINK
I can't honestly say that a designer should be in charge of migration - I would think it would lean closely to the developer who might be able to write scripts or code to perhaps assist in importing of data.
I'm currently in the throws of upgrading my own site and I can tell you regardless of how much you try to automate, its' really an initial hands on job of copy and pasting of information to a certain extent.
How many pages are we talking? My site is only about 150 pages.
I think there is no specific tutorial since many instances are so individual and different, but I can tell you I wouldn't be asking a designer to move data unless they knew about DotNetNuke. A developer might think it's not their field, which is why I
have an intern who is experienced at this sort of thing.
The key areas to look for is when copying and pasting data, to maeke sure it's nicely pasted without taking the other formatting into the page because that's a horrible job to go back and revisit.
Feb 06, 2006 07:54 AM|msy|LINK
Thanks. Suprisingly I was actually browsing through the XD site on the same day.
Well, I guess the site that I have been ask to migrate is not big compared to yours. Say 16 pages. It wont be so much of an issue, if the designer did not try to sell the idea to the clients of a more then one template website. But I guess being designers they
like the freedom of expression. My difficulty lies with trying to maintain as much as possible the original look and feel of the existing site when migrating. Having done Mambo, it was a huge challenge. But fortunately, client was understanding. But like you
said...the are many different instances.
If only they the designers can create a readily uploadable dnn template, instead of me trying to DNN'able it.
Feb 06, 2006 08:36 AM|xddg|LINK
AAh that's two different things - migrating in my interpretation, and incorrectly I apologise - was the content.
What I think you mean is replicating your site to maintain the existing look and feel.
I do a fair bit of that - the master of replication is a bit of a tricky art but now you have shed more light on it, my approach is that you should get your content into the site first - get your pages and menu on there so the designer can see where there
might have to be some compromises.
So yes your designer can do the storyboard/layout but perhaps a little bit of knowledge about dnn might help. I can't tell you how often I've been contacted by people who have had headaches with time constraints because their designer was given this project
- Turn our site into a DNN one! And I feel for these people who may have no concept of the DN architecture, concepts of skinning, or experience in CSS or html at all. So make sure you give your designer some time to learn DNN.
The other alternative is that you run with the default skin while yours gets dressed up while you wait, that's also feasible and many people do this. But it could depend on your circumstances and time constraints.
So, my suggestion is that you get a dev environment setup for you to copy the content and add the pages, it seems you're well able to do that, while your designer learns a bit about DNN and then you discuss what if any compromises you need to do to get the
site live, but as close as possible to what you are trying to achieve.
Thanks for visitng my site - I'm busy getting the final touches on the new one and am excited about it with more free skins that I've found and some other cool and better laid out information for people to learn from.