If you haven't already, be sure to install the Firebug plugin so you can inspect the CSS directly in Firefox or Chrome. That will save a ton of time in determining where your changes need to be made. Also, while you're working on the skin, be sure to disable CSS caching through Administration, Advanced Tools, Design Tools, Cache Tool.

Ideally, you want to make minimal CSS overrides, if possible. You may need to change some of the mojoPortal CSS choices, though, to align the look of those elements with your skin. What we do is add a separate .css file for our own overrides, and add it to the very bottom of style.config. That way, we can put in overrides that supersede just about everything else, and keep them in one central spot for maintenance.

Jamie

If the logo is part of the Artisteer design, its possible that the layout.master file is missing a div that would be used for it. I would examine the exported html page and compare it to the layout.master and look for any missing div with a class on it that may be used for the logo rather than using our <portal:SiteLogo control and trying to position it. Chances are if you add the missing div in the correct location and remove the sitelogo control then the existing Artisteer css will add the logo and position it correctly.

Hope that helps,

Joe