james yong wrote "The special-purpose and hot-deploy folders are essentially combined into a plugins folder which is easier understood by new users, in my own opinion."
I disagree strongly with this statement. Historically, special-purpose was just that, components which are not generally used by most users. hot-deploy is (was) used by nearly everyone to put custom components used by their application. Having a single plugin folder that combines both hot-deploy and special-purpose seems to me to be a very bad idea. Why not just rename hot-deploy to plugin and leave special-purpose as it is. Makes directory management much easier to not have the 20 odd components in special-purpose combined with the few in hot-deploy. Skip
