nest landing page content as child element, for responsive templates

[Anonymous]

I would like to suggest that when building a landing page, that there should be an option to make the dynamic content that is being added a child element of the container in the template. This would allow for fully responsive designs, as it would remove the absolute positioning of all the mkEditable elements. 

Basically what I am proposing is to create a "window" in the template where the dynamic content would be placed. This would allow other memebers of our team who arent necissarily developers to make use of the dynamic content features that you guys provide. While at the same time would provide us with flexability in designing landing page templates, as all we would have to do is leave the area where content would go "empty" and the other members of our team would be able to enter content, and not have to worry about positioning. 

[Anonymous]

You could probably do that now by adding a token into your "window," and telling your content editor to update/add their content to a corresponding rich text token in inside the page's program.

[Anonymous]

I would LOVE to have the ability to turn off the default absolute positioning of page elements and nest these elements within containers. It would cut the time it takes us to build a landing page in half. Currently, we have to use elaborate workarounds with iframed forms and/or significant script-based DOM manipulation to build even a simple responsive landing page. Honestly, it seems silly to me that this (page level absolute positioning) is not a basic feature I could toggle on or off.

I can appreciate the need for users without HTML/CSS knowledge to be able to drag, drop and resize elements on the page in a reliable way, there has to be a significant need for other Marketo users like us that would prefer not to be locked into that system.