Thanks so much for taking the time to explain this and for doing the screencast. I really appreciate it. The paradigm of responsive layout is new to me and I think I was confusing myself with some of that and I also didn't quite realise the difference of a container.
So if I'm understanding correctly, it seems I should use a container, which uses a width of 960 for desktop. I think I had tried it before but didn't like the fact it made the box so small. I think that's why I didn't use one and had mistaken the elastic box to be a better responsive design.
You see, we have these huge monitors where I work with this insane resolution, way beyond 1080p (probably at least 2k or more I would guess), and my mock up looked so tiny on that, which is probably how I ended deciding on putting a box inside of the body directly, so it would upscale more nicely. But now I see that had unpleasant side effects.
It got me to thinking and I searched about it and I ran across this post:
Anyway, I've followed the changes you made on the screencast and was very pleased with the result I understand more clearly now, it might be better to stick to that whole 960 container grid for this one. To be honest, I'm not a big fan of the box within a box design but my friend had been working on a boxed concept for something different and I decided to play around with the concept myself, which came off looking very IOS7-like in this case.
I've downloaded a few books on responsive design now which I plan on looking over to better acquaint myself with with the paradigm. I also have a lot more Webflow videos to watch to get better using this tool.
My goal is to actually learn to code responsive design and get proficient with HTML,CSS, and Jquery, etc...
Right now I'm using webflow as a crutch to quickly work out design concepts and then take a look at the code. And plus, i've had a few paid jobs for simple static sites, which I was using Adobe Muse for but I think I much prefer Webflow's concept and how it's model more closely ties in with how things are actually coded and thought of.
Sorry for the long reply, I get carried away sometimes. Thanks so much again for being so generous with your time and welcoming me and explaining this basic so nicely. You're a legend!