Two possible causes:
Web.config transforms are applied based on the name of the environment you are deploying to. For example, if you have an environment called "Development", you need to call your web.config transform web.Development.config.
Files to be included in the published package need to have build action set to Content. This applies for web.config transforms, but also any static content, such as html/css.