1) All layout/theme elements are handled by cmsms anyway. css is in the db, templates are in the db, and probably extra images are in the uploads directory.
2) You can work out what goes where based on the template->css links in the db and the image-urls in the template and/or stylesheet.
3) Let the user pick a name and one or more templates to pack.
4) Show the user a bill of lading, so that he may correct his error of packing embarrasing private pics
5) Write the db info to an easily readable and parsable format and pack it together with the images into a zip file.
6) Allow the user make his creation available to the rest of the world, so he can put links to it on a forum for exchanging styles.
7) The format of the package should be so simple that it can be dissected by non-cmsms using people without too much trouble, but also parsable by cmsms so that the styles and templates all end up in the normal places.
So that is my brainfart for today. I suppose that is what you get if i am told my previous idea was very good. (yup, typical geek not good in handling compliments
