Created by: supergibbs
Since it seems like there is some desire for NuGet support, I went ahead and set it up with my fork as a demo. I got both a css and less version working. Since Sass is a different repo, I can do that one next.
@mdo and team, with a simple pull request, deploy key and webhook the NuGet packaging and publishing can be fully automated. I tried to match the general settings as close as possible to the npm, bower, etc packages.
When you "release" a milestone it'll use the webhook to POST to MyGet.org to kick off the process. MyGet will pull the latest commit (not the actual release tag, didn't see that as an option) from the master branch. It runs a build script that parses the current_version out of the _config.yml Jekyll file and creates the packages. It'll then publish them to the myget feed and to the official nuget.org feed.
If anyone would like to test (and have v3.3.5!!!), you can add https://www.myget.org/F/getbootstrap/api/v2 to your NuGet sources. This is temporary, eventually it'll be on the official nuget.org feed. I set it up so, if you use the outercurve package, it'll detect it as an update. If we can't get outercurve to transfer the package id then it'll have to change to getbootstrap or something. There is also a new package called bootstrap.less that is the same structure as Twitter.Bootstrap.Less but won't be a direct upgrade since the Twitter name isn't supposed to be used. Please let me know if there are any issues or suggestions. Would anyone want a version with the individual js components instead of the full bootstrap.js?