How well does DNN support test/prelive areas for page content updates? What I want is a development or staging environment where I can try things out or build out pages and content and then move them out into a production environment. I want to build pages and do page reorganization but not include them in the live navigation until I'm ready. Making changes directly in the production environment make me feel a little exposed, if you know what I mean!?!

I know that a DNN contains a combination of data (e.g. user subscription details, survey questions/answers) and metadata (e.g. page content), but how easy is it to separate one from the other when migrating from a development/staging environment for content to the live environment? Are there any published scripts or guidelines for doing "metadata only" DNN data migrations to support what I'm looking for?

Yes creating new content is less of an issue. It's when changes need to be made to existing pages and menu structures, or when the site is significantly overhauled, that I would need to use a staging area - I wouldn't want to disrupt the existing live site while work is in progress on major structural or content changes which affect existing live pages or menus.

It's more for content than modules as well.

Glad to hear that it's on  the roadmap.

In the meantime is it feasible to script migration of new/modified content from a staging area to the live environment (both files and database table content)? Is anyone out there doing this?