How can I version control in Microsoft cloud TFS the html and js files which are stored in document libraries? I have these kind of questions: How could I

* "publish new versions of the solution" (what would be an easy way; should we for example create a PowerShell script which will deploy the files to the correct folder structure, and update one file which contains the version numbers?
* See the current version number (if we, for example, branch new versions every now and then - where to store the currently "deployed" version number of all of our files if we deploy them all at once)
* What would be a nice way to arrange the html, js, css files in document libraries? (and should we replicate the structure in our VS solution for easy updating of them during versioning)?

A simple example might be where the solution spans a couple of subsites inside one single site collection. Subsites could contain CEWPs in web part pages in document libraries. The CEWPs point to html files which reference one js and one css file per CEWP. Files need to be kept in Microsoft cloud visual studio for a global development team, and deployed to on-premises SharePoint every now and then.

For example

* SiteCollection/MySolutionFiles/MyComponent/my-component.aspx
* SiteCollection/MySolutionFiles/MyComponent/my-component.html
* SiteCollection/MySolutionFiles/MyComponent/my-component.js
* SiteCollection/MySolutionFiles/MyComponent/my-component.css
* SiteCollection/Lists/MySolutionVersions/

and the same structure in visual studio (starting from MyComponent) storing other files than the aspx (web part page with CEWP). PowerShell would then copy-paste all the files to the SharePoint site collection, overwriting the existing files and saving a new row to the versions list (which might contain VersionNumber, Description)