Deploying a Subtext skin used to be one of the biggest annoyances with Subtext prior to version 2.5The main problem was that you couldn’t simply copy a skin folder into the Skins directory and just have it work because the configuration for a given skin is centrally located in the Skins.config file.
In other words, a skin wasn’t self contained in a single folderWith Subtext 2.5, this has changedSkins are fully self contained and there is no longer a need for a central configuration file for skins.
What this means for you is that it is now way easier to share skinsWhen you get a skin folder, you just drop it into the /skins directory and you’re done! In most cases, there’s no need for any configuration file whatsoever.
If your skin contains...(
read more)
.