I'm a relatively new DNN 4.0.3 user who has already benefited from the advice of others through the forums and the Wrox text. So far, though, I can't find the exact details I need on Portal Organization and the best practices for setting up (and naming) folders for longterm expansion and maintenance.

For example, let's say I'm using a national company's shared hosting plan with the primary URL being my upstart movie studio's site, and DNN manually installed one level off the root like this:

    www.mymoviestudio.com/dnn

Here's what I'd like to do correctly, the first time around:

1. Prototype my first movie's web site as a Child portal, before going live with its own aliased simple URL, e.g., www.myfirstflick.com

2. Reserve the chance to set up a new portal for the mymoviestudio.com site, replacing its present static page (once I have a movie / corresponding web site to feature on it!)

3. Down the road, be able to create new movie sites in the vein of myfirstflick.com, all off the same DNN installation.


QUESTIONS:

Am I stuck with "/Portals/0" as the directory for my myfirstflick site that's already being prototyped? If not, what's the best way to migrate it to something more intuitive, like "/Portals/MyFirstFlick"?

Also, if I have commonly used graphics or other inter-portal files, is there any drawback to installing them in "/_default" (or, better yet, off that in a subdirectory with an intuitive name)?


Thanks very much for your thoughts on the smartest way to proceed!

-JPW