Changed the website domain name

Author: JamesMessinger

CHANGELOG.md

@@ -5,7 +5,7 @@ JSON Schema $Ref Parser adheres to [Semantic Versioning](http://semver.org/).
 
 ## [v7.1.0](https://github.com/APIDevTools/json-schema-ref-parser/tree/v7.1.0) (2019-06-21)
 
-- Merged [PR #124](https://github.com/APIDevTools/json-schema-ref-parser/pull/124/), which provides more context to [custom resolvers](https://apidevtools.org/json-schema-ref-parser/docs/plugins/resolvers.html).
+- Merged [PR #124](https://github.com/APIDevTools/json-schema-ref-parser/pull/124/), which provides more context to [custom resolvers](https://apitools.dev/json-schema-ref-parser/docs/plugins/resolvers.html).
 
 [Full Changelog](https://github.com/APIDevTools/json-schema-ref-parser/compare/v7.0.1...v7.1.0)
 
@@ -104,7 +104,7 @@ Lots of little bug fixes.  The only major bug fix is to [support root-level `$re
 
 This version includes a **complete rewrite** of the [`bundle` method](https://github.com/APIDevTools/json-schema-ref-parser/blob/master/docs/ref-parser.md#bundleschema-options-callback) method, mostly to fix [this bug](https://github.com/APIDevTools/swagger-parser/issues/16), but also to address a few [edge-cases](https://github.com/APIDevTools/json-schema-ref-parser/commit/ca9b322879519e4bcb2dcf6e63f08ac254b90868) that weren't handled before.  As a side-effect of this rewrite, there was also some pretty significant refactoring and code-cleanup done throughout the codebase.
 
-Despite the significant code changes, there were no changes to any public-facing APIs, and [all tests are passing](https://apidevtools.org/json-schema-ref-parser/test/) as expected.
+Despite the significant code changes, there were no changes to any public-facing APIs, and [all tests are passing](https://apitools.dev/json-schema-ref-parser/test/) as expected.
 
 [Full Changelog](https://github.com/APIDevTools/json-schema-ref-parser/compare/v2.1.0...v2.2.0)
 

README.md

@@ -10,7 +10,7 @@ JSON Schema $Ref Parser
 [![License](https://img.shields.io/npm/l/json-schema-ref-parser.svg)](LICENSE)
 
 
-[![OS and Browser Compatibility](https://apidevtools.org/img/badges/ci-badges-with-ie.svg)](https://travis-ci.com/APIDevTools/json-schema-ref-parser)
+[![OS and Browser Compatibility](https://apitools.dev/img/badges/ci-badges-with-ie.svg)](https://travis-ci.com/APIDevTools/json-schema-ref-parser)
 
 
 The Problem:
@@ -46,10 +46,10 @@ The Solution:
 JSON Schema $Ref Parser is a full [JSON Reference](https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03) and [JSON Pointer](https://tools.ietf.org/html/rfc6901) implementation that crawls even the most complex [JSON Schemas](http://json-schema.org/latest/json-schema-core.html) and gives you simple, straightforward JavaScript objects.
 
 - Use **JSON** or **YAML** schemas — or even a mix of both!
-- Supports `$ref` pointers to external files and URLs, as well as [custom sources](https://apidevtools.org/json-schema-ref-parser/docs/plugins/resolvers.html) such as databases
-- Can [bundle](https://apidevtools.org/json-schema-ref-parser/docs/ref-parser.html#bundlepath-options-callback) multiple files into a single schema that only has _internal_ `$ref` pointers
-- Can [dereference](https://apidevtools.org/json-schema-ref-parser/docs/ref-parser.html#dereferencepath-options-callback) your schema, producing a plain-old JavaScript object that's easy to work with
-- Supports [circular references](https://apidevtools.org/json-schema-ref-parser/docs/#circular-refs), nested references, back-references, and cross-references between files
+- Supports `$ref` pointers to external files and URLs, as well as [custom sources](https://apitools.dev/json-schema-ref-parser/docs/plugins/resolvers.html) such as databases
+- Can [bundle](https://apitools.dev/json-schema-ref-parser/docs/ref-parser.html#bundlepath-options-callback) multiple files into a single schema that only has _internal_ `$ref` pointers
+- Can [dereference](https://apitools.dev/json-schema-ref-parser/docs/ref-parser.html#dereferencepath-options-callback) your schema, producing a plain-old JavaScript object that's easy to work with
+- Supports [circular references](https://apitools.dev/json-schema-ref-parser/docs/#circular-refs), nested references, back-references, and cross-references between files
 - Maintains object reference equality — `$ref` pointers to the same value always resolve to the same object instance
 - [Tested](https://travis-ci.com/APIDevTools/json-schema-ref-parser) in Node and all major web browsers on Windows, Mac, and Linux
 
@@ -82,7 +82,7 @@ catch(err) {
 }
 ```
 
-For more detailed examples, please see the [API Documentation](https://apidevtools.org/json-schema-ref-parser/docs/)
+For more detailed examples, please see the [API Documentation](https://apitools.dev/json-schema-ref-parser/docs/)
 
 
 
@@ -122,7 +122,7 @@ To use Json-Schema-Ref-Parser in a browser, you'll need to use a bundling tool s
 
 API Documentation
 --------------------------
-Full API documentation is available [right here](https://apidevtools.org/json-schema-ref-parser/docs/)
+Full API documentation is available [right here](https://apitools.dev/json-schema-ref-parser/docs/)
 
 
 Contributing

_config.yml

@@ -1,7 +1,7 @@
 remote_theme: APIDevTools/gh-pages-theme
 
 title: JSON Schema $Ref Parser
-logo: https://apidevtools.org/img/logos/logo.png
+logo: https://apitools.dev/img/logos/logo.png
 
 author:
   twitter: APIDevTools
@@ -16,7 +16,7 @@ defaults:
   - scope:
       path: ""
     values:
-      image: https://apidevtools.org/img/logos/card.png
+      image: https://apitools.dev/img/logos/card.png
   - scope:
       path: "test/specs/**/*"
     values:

package.json

@@ -22,7 +22,7 @@
       "email": "[email protected]"
     }
   ],
-  "homepage": "https://apidevtools.org/json-schema-ref-parser/",
+  "homepage": "https://apitools.dev/json-schema-ref-parser/",
   "repository": {
     "type": "git",
     "url": "https://github.com/APIDevTools/json-schema-ref-parser.git"