update links from http -> https

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # How to Contribute to npm docs
 
-Participation in this open source project is subject to the [npm Code of Conduct](http://www.npmjs.com/policies/conduct).
+Participation in this open source project is subject to the [npm Code of Conduct](https://www.npmjs.com/policies/conduct).
 Please also ensure your contribution conforms to the [Contributing Guidelines](https://github.com/npm/npm/wiki/Contributing-Guidelines).
 
 ## To submit a new issue

README.md

@@ -51,7 +51,7 @@ If you rename a directory inside the `content` directory, you'll need to change
 
 ## Development
 
-Download node at [nodejs.org](http://nodejs.org) and install it, if you haven't already.
+Download node at [nodejs.org](https://nodejs.org) and install it, if you haven't already.
 
 To run the app locally:
 

content/company/about.md

@@ -2,8 +2,8 @@
 
 npm is lots of things.
 
-* npm is the package manager for [Node.js](http://nodejs.org/).  It was created in 2009 as an [open source project](https://github.com/npm/npm) to help JavaScript developers easily share packaged modules of code.
-* The npm Registry is a public collection of packages of open-source code for Node.js, [front-end web apps](http://www.ember-cli.com/), [mobile apps](http://cordova.apache.org/), [robots](https://tessel.io/), [routers](https://linerate.f5.com/), and countless other needs of the JavaScript community.
+* npm is the package manager for [Node.js](https://nodejs.org/).  It was created in 2009 as an [open source project](https://github.com/npm/npm) to help JavaScript developers easily share packaged modules of code.
+* The npm Registry is a public collection of packages of open-source code for Node.js, [front-end web apps](http://www.ember-cli.com/), [mobile apps](https://cordova.apache.org/), [robots](https://tessel.io/), [routers](https://linerate.f5.com/), and countless other needs of the JavaScript community.
 * npm is the command line client that allows developers to install and publish those packages.
 * npm, Inc. is the company that hosts and maintains all of the above.
 

content/enterprise/installation.md

@@ -12,7 +12,7 @@ npm On-Site runs locally, on a server you control, with no external dependencies
 
 Follow the instructions in the [quickstart video](/enterprise/intro), or do the following:
 
-1. [Sign up for a trial license](http://www.npmjs.org/onsite#contact) for npm On-Site.
+1. [Sign up for a trial license](https://www.npmjs.org/onsite#contact) for npm On-Site.
 2. Make sure you have a machine that meets the [installation requirements](/enterprise/requirements).
 3. On the server, run ```sudo npm install npmo -g --unsafe```.
 4. visit _http://myreg.mycompany.com:8800_, to configure your instance.

content/getting-started/installing-node.md

@@ -9,7 +9,7 @@ featured: true
 
 ## Installing Node.js
 
-If you're using OS X or Windows, the best way to install Node.js is to use one of the installers from [nodejs.org](http://nodejs.org). If you're using Linux, you can use the installer, or you can check [NodeSource's binary distributions](https://github.com/nodesource/distributions) to see whether or not there's a more recent version that works with your system.
+If you're using OS X or Windows, the best way to install Node.js is to use one of the installers from [nodejs.org](https://nodejs.org). If you're using Linux, you can use the installer, or you can check [NodeSource's binary distributions](https://github.com/nodesource/distributions) to see whether or not there's a more recent version that works with your system.
 
 Test: Run `node -v`. The version should be higher than v0.10.32.
 

content/getting-started/publishing-npm-packages.md

@@ -13,20 +13,20 @@ You can publish any directory that has a `package.json` file, e.g. a [node modul
 
 To publish, you must have a user on the npm registry. If you don't have one, create it with `npm adduser`. If you created one on the site, use `npm login` to store the credentials on the client.
 
-Test: Use `npm config ls` to ensure that the credentials are stored on your client. Check that it has been added to the registry by going to [http://npmjs.com/~](http://npmjs.com/~)<username>.
+Test: Use `npm config ls` to ensure that the credentials are stored on your client. Check that it has been added to the registry by going to [https://npmjs.com/~](https://npmjs.com/~)<username>.
 
 ## Publishing the package
 
 Use `npm publish` to publish the package.
 
-Test: Go to `http://npmjs.com/package/<package>`. You should see the information for your new package.
+Test: Go to `https://npmjs.com/package/<package>`. You should see the information for your new package.
 
 ## Updating the package
 
 When you make changes, you can update the package using `npm version <update_type>`, where update_type is one of the semantic versioning release types, patch, minor, or major. This command will change the version number in `package.json`. Note that this will also add a tag with this release number to your git repository if you have one.
 
 After updating the version number, you can `npm publish` again.
 
-Test: Go to `http://npmjs.com/package/<package>`. The package number should be updated.
+Test: Go to `https://npmjs.com/package/<package>`. The package number should be updated.
 
 The README displayed on the site will not be updated unless a new version of your package is published, so you would need to run `npm version patch` and `npm publish` to have a documentation fix displayed on the site.

public/styles/_config.styl

@@ -43,5 +43,5 @@ column-break-inside(n)
   -webkit-column-break-inside n
   -moz-column-break-inside n
   // Firefox workaround
-  // http://stackoverflow.com/a/7785711
+  // https://stackoverflow.com/a/7785711
   page-break-inside n