How is this module different than the Features module? I ask because this is one of four similar modules listed at Configuration Management, Automation & Features, and Features appears to be furthest along.

I feel the functionality promised by these modules is a critical Drupal innovation. I appreciate that you are doing this, but want to see if there's any duplicate work and any opportunity for the troops to rally around one effort.

Comments

jazzslider’s picture

jazzslider commented
Status: Active » Closed (fixed)

The Features module is definitely the one to rally around; Exportables only exists as a sidekick module to help make certain core modules conform to Features's expectations.

More specifically: Features allows you to export configurations (content types, views, etc.) as code that can then be easily re-deployed on other sites, but those configurations _must_ each be associated with a machine-readable name, rather than just a numeric ID. This works well for content types, views, and the like, but does not work for, say, taxonomy vocabularies, terms, or nodes (since Drupal core doesn't provide machine-readable names for such things). The Exportables module aims to provide those machine-readable names, along with export functionality, so that those modules' configurations can also be included in exported features.

All that said, I should reiterate: our efforts here at Exportables are intended to _support_ Features, not compete with it.

Thanks!
Adam