Things I have learned.

I developed a simple site on my localhost, created a template (with content) move both files to my host site, then created a child portal. (www.peacemerchant.info/lpevents). The site contained several pages, mostly hidden, each one contained a purchased gallery module.  The "style" of the module had been set on the localhost site, but no pictures were loaded.  The home page consitted of the standard HTML module and the standard links module.

1. The links in the links module lost their bearings and would actually bring you to the home page of the parents site, not of the child site (really dont like this). I have seen this with other errors, DNN hiccups on a child site and it will default to the home page of the parent site. The fix was easy, I edited every link , by changing the page it linked to drop down box to the correct page
2. The HTML module was almost perfect except it lost the picture.  The reason was easy to understand, the ref was the localhost, what was a little disapointing is the the picture was not picked up in the resource file, I had to load it through the file manager.
3.  While the purchased module did appear on the correct pages (I preloaded the module through the host function) the admin settings were lost.

I also did another test , creating a template with a site that contain a great deal of content (Phot Gallery),   I had errors and loads that, if they did finish, created errors at the applcation level.  I determined that it was the amount of data that was causing the problem.

Hope this helps someone with their development and deployment processes.