I'm a web designer, and fluent in html/css.  I don't have much experience with .net, mySQL, etc. A client wants a website and chose DNN for their cms.  I've been readign the forum and looking at installation threads and it almost seems like DNN will be over my head when it comes to a lot of things.  Here are my worries...

1. Do I use a local install and move it to a web host when complete?  Is this something that can be done easily by someone with minimal knowledge of mySQL, databases, etc.? If I use a web host to build the site, it probably would be a temporary server, what is involved with moving things from one web host to another?  The only experience I've had with stuff like this is installing Wordpress, which look 5 minutes and was working perfectly.

2. I haven't tried to modify a skin or make a new one because the online demo won't allow it.  Knowing html and css, will this be an easy process?  Seems like most of the sites I've seen using DNN are low in imagery, and are kind of "boxy".

3. If I use a basic html module to make a custom content area, won't I lose some of the ease of allowing the client to update that section without them having to get into code to change content?

4. What if a client wants a feature that I can't find a custom module for?

I have other questions and worries, but I'm having trouble putting them into words at the moment, thanks for any help
 

I would add that you preface everything with "I'm a web designer..."

#1 is not for a web designer. If you're trying to do it yourself, then do yourself a favor and simply install DotNetNuke to the future live server, i.e., the design/development work is done directly on the same server that will be the eventual live site. You can register a special URL for design/development so that it is accessable, then when ready to launch, simply add the real domain to the portal settings.

#2 is wide open, but depends on the size/nature of the site. If you have established top level links, you can actually prer-create the top level pages and then hard code those into a skin that might use rollovers and whatever else to navigate the site. Once you understand how DNN works, there is actually a lot of flexability. I have many sites that were designed by very insistant designers, and are very fluid and organic.

#3 sounds like it is going up against your comfort level? There are many ways to insert custom code or other stuff that can be protectedc from the client - for example, add stuff to the header/footer area of a module and they don't need to even go in there.

#4 sounds like a designer talking :). So hire it out?!

It sounds more like you are just hesitant pushing DNN as a good solution since you're not entirely comfortable with it yet. You'll get there. It's a great platform for building out a site. I've migrated 95%+ of my clients over, and have never looked back.

HTH