> The ideal, methinks, would be import/export/hook support for CCK the same way > Views has. Then many modules simply become a pre-packaged node (user > editable), some pre-packaged views (user-editable), maybe a pre-packaged > field type if needed, and a little glue code. your ideal was committed a few days ago to core cck. see content_copy.module.