content

An approach for keeping content that is added as part of development synchronized with test and production environments is to use the Default Content module to export the content. It's built for the content to be exported to an installation profile's 'content' folder, and then the module, if enabled, automatically brings the content in when the site is installed.

For the moment, we're following the crowd and using the Default content module. It is nice and has built-in integration with installation profiles, but the export could be more convenient (multiple items of content at once, please!) and import could be made much more robust (given half a chance, we'll reimplement it on migrate).

after wasting untold hours with Deploy and Services modules, i switched to using views with xml export and Mitchell's xpath parser module on the intake side. Thing is magic, just wish he hadn't disappeared again and had done it in 1/10th the time it took me

Bloody magic, i imagine a lot from feeds, but it does taxonomy terms and images perfectly, and links in the url and title pieces, once it is all exported as plain text in xml (i was more comfortable with creating the dedicated feed than doing the HTML parsing)

On the source site, download the Views Datasource project

A test: I gave one GMail account edit access to another GMail account (yes, you can do this) and started editing an e-mail, saved it as draft, and then went to the other account— the draft was there, but not only was there no autorefresh of the other's changes when i edited simultaneously, but it forked and created two drafts of the same e-mail.

drupal 7 programmatically create node in installation profile
http://www.group42.ca/creating_and_updating_nodes_programmatically_in_drupal_7

I have spent the day discovering that you cannot populate with content the content type created in a Feature module using the .install file of that Feature module.