Tim Priebe

"Not a problem." - Tim Priebe

"Sounds like Imposter by Phillip K. Dick." - Tim Priebe

"I use a variation on iterative programming. I start with a CSS/HTML/PHP framework (WP theme framework, actually), then do a series of iterations. At the end of each iteration, I have a usable, good-looking theme, but it doesn't actually match the design file until the end of the process. Typically, the iterations look something like this: 1. Basic color scheme, fonts, and logo in place. 2. Design-accurate header and footer, primarily through CSS, without HTML changes to framework. 3. Design-accurate content area for normal inside page. 4. Design-accurate sidebar(s) for normal inside page. 5. Design-accurate blog index and single blog entry template. 6. Alternate templates, one at a time. (Home page, pages with/without sidebars) Within each iteration, it looks very similar to your process, although I don't use SASS. I constantly refer to the design file throughout the process. I typically do all the iterations in Firefox, then cross browser-test at the very end. But that's because our..." - Tim Priebe

"Don't touch anything outside the wp-content folder. Everything outside is a core file, and should never me modified. Once you get more experienced, you can override and hook into certain functions. You still will rarely need to go outside the wp-content folder, though. When you're first starting out, go one of two routes: 1. Grab an existing theme that's close to what you need, and hack the crap out of it. 2. Create your HTML and CSS the normal way, then use a pre-created theme as a way to convert it over to a WordPress theme. I hear about a lot of people doing #1. But it sounds like you're in the same boat I was in when I started, so I always did #2. I gained enough experience that I ended up developing a framework that we use internally, so you may end up wanting to go that route at some point. Hope that helps!" - Tim Priebe

"Different locations. Our actual location is more like this... demo.whatever.com/clientcode/w1 demo.whatever.com/otherclient/w1" - Tim Priebe

"We do the development work on the client preview site. We use a pretty basic versioning system. Each time a client sends a batch of changes, we increment the version, basically copying the installation each time. We also leave them all up until the site's been up for a few months. So... whatever.demo.com/version-01 whatever.demo.com/version-02 whatever.demo.com/version-03 We have our home-grown script that does the copying while still on the demo location. We really only use BackupBuddy when launching the site. But you could just as easily use BackupBuddy each time you incremented the version." - Tim Priebe

"My company does that, and we do a separate installation of WP for each. Then when it's ready to launch, we use BackupBuddy to move it to its new location. It's worked well for us." - Tim Priebe