Dave…I have seen most people pick up the design and usage of Skuid pages pretty quickly.  I think that you can introduce the new design in a webinar and get some feedback before you roll out.  I think you’ll find a very positive response.  As another option, you could use Skuid to replicate the layout of the standard Salesforce page and then begin adding tabs and moving related lists to their own ‘area’.

Your Noob approach was not so far off (But I’m sorry this is 2 months later…)

Make sure that the SF header is turned off in your VF page code (or in your skuid page definition) and the header nesting will be avoided.  Then I believe your strategy will work. 

Ty, I actually had figured it out a while back, but good for other people in case needed

At this point my account page is fully skuidified! 

Hi there.  Even though I’d love to just skuidify everything, everywhere, my hands are tied a bit…We’re trying to replace an old VF page embedded in a standard page that is essentially a related list with inline creation and editing.  I can get the Skuid page to work - no cascade problem - but I can’t figure out how to pass the id of the Account to the models, so I just get blank tables.  What am I missing here??

I think i also had the same problem. In which case you have to set the condition value to “Content = Page/URL parameter” and “Parameter = Id”.

Hope this helps.

Cheers,