I'll briefly explain how it all works together ...
"Styles" comprise (presently) of three "Style Elements"; template, theme and imageset. The template set obviously comprises all the markup describing what the forum layout looks like. The theme contains CSS and associated images thus specifying the actual look of the board. The imageset contains non-theme specific images; buttons, icons, etc. These can be combined in any way.
The styles are stored in the styles/ folder off the phpBB root folder. Each style or style element must be stored under a unique name ... this shouldn't be a problem since experience with 2.0.x indicates designers tend to be quite "imaginative" in their style naming
Each Style Element set contains a .cfg file; template.cfg, theme.cfg and imageset.cfg. These contain basic information on each of the element sets. In the case of templates for example it details the name, the copyright, the version of phpBB 2.2 under which it was exported and a bbcode bitfield identifier. The imageset config contains information on which image maps to which button/icon in the database. These .cfg files are generated automatically when a Style Element is exported.
If you manually extract a Style Element archive into a newly created (uniquely named) Style Folder in styles/ ... and then visit the relevant Styles module this new style element will automatically be detected and listed as an "Uninstalled theme/imageset/template" ... you can then click "Install" and voila, a new style element is available.
In 2.2 we've introduced a far greater capability to alter the style online. In 2.0 you were limited to a few predefined colour, typeface settings. In 2.2 you can edit a whole raft of predefined theme classes (or add your own custom classes), you can alter the imagesets, etc. You can also modify the templates online.
To allow users who may be wary of setting their style elements to world writeable (required for PHP to modify the files online) 2.2 will transparently and automatically copy to the database templates and theme information if it detects it cannot write to them on the filesystem. You may also do this manually if you choose. All editing of such data will then be stored in the database. This does mean duplication of data but it was the best solution I could come up with ... and the impact is likely negligible considering the typical space allocations of hosting packages these days
Admins may also decide they want to upload or import (from their store/ folder) styles ... this will require the styles/ folder be given appropriate write permissions. While we can store stylesheet and templates in the DB we can't store every single image we use
A warning here ... safe mode is nasty
I note that while getting there styles admin in CVS is not yet complete ... some things don't work, some things work "oddly". If something does behave oddly please let me know ... if something blatantly doesn't work chances are I've not finished it
Anyway this is a basic overview of how things work ... I could probably add more here but it's probably better if people "ask questions" to which I can respond.