Merge pull request #24 from davision/master

Fix broken links

Author: davision

.vuepress/package-lock.json

@@ -15,7 +15,7 @@
     "@vuepress/plugin-pwa": "1.2.0",
     "@vuepress/plugin-register-components": "^1.2.0",
     "markdown-it-container": "2.0.0",
-    "node-sass": "4.13.0",
+    "node-sass": "^4.13.1",
     "sass-loader": "8.0.0"
   }
 }

.vuepress/package.json

@@ -278,10 +278,10 @@ Yes, the 0xcert Conventions are simply JSON objects, and you could create them y
 
 | Issue | Id | Description
 |-|-|-
-| [xcert](https://0xcert.org/conventions/xcert-schema.html) | e1823a17bb5dd039e2aff7d997223efed50dbeebb0fcb60cf7bba2a9b6f90140 | JSON Schema definition describing asset schema capabilities.
-| [86](https://0xcert.org/conventions/86-base-asset-schema.html) | 9a7531dd7ac3ed4e3d2fa61d20a825cfd4be7f3e6bc540c82d9dc94b526c5123 | Basic asset data schema.
-| [87](https://0xcert.org/conventions/87-asset-evidence-schema.html) | 02edbb4f2d07017d0ae9148af683a63d4b86d0d357a5019dd794d377a1523e9e | Asset evidence data schema.
-| [88](https://0xcert.org/conventions/88-crypto-collectible-schema.html) | cd3d7fce94669724f964061572f42ae0391996b0e348c7431251f9ab1bab0f49 | Schema describing digital collectible item.
+| [xcert](https://docs.0xcert.org/framework/v2/schemas/xcert-schema.html) | e1823a17bb5dd039e2aff7d997223efed50dbeebb0fcb60cf7bba2a9b6f90140 | JSON Schema definition describing asset schema capabilities.
+| [86](https://docs.0xcert.org/framework/v2/schemas/86-base-asset-schema.html) | 9a7531dd7ac3ed4e3d2fa61d20a825cfd4be7f3e6bc540c82d9dc94b526c5123 | Basic asset data schema.
+| [87](https://docs.0xcert.org/framework/v2/schemas/87-asset-evidence-schema.html) | 02edbb4f2d07017d0ae9148af683a63d4b86d0d357a5019dd794d377a1523e9e | Asset evidence data schema.
+| [88](https://docs.0xcert.org/framework/v2/schemas/88-crypto-collectible-schema.html) | cd3d7fce94669724f964061572f42ae0391996b0e348c7431251f9ab1bab0f49 | Schema describing digital collectible item.
 
 **Example:**
 

framework/v2/api/certification.md

@@ -4,7 +4,7 @@ As explained previously, the 0xcert Framework tends to be platform-agnostic, thu
 
 Each provider operates on the same principles, but can also have its own distinctive characteristics. The current version of the Framework supports the Ethereum and the Wanchain blockchains. Soon, more platforms will be added.
 
-Even within the same blockchain, you can use multiple providers depending on your needs. If you would like to communicate with the blockchain on the front-end, you could use [MetamaskProvider](/api/ethereum.html#metamask-provider), while for communication on the back-end you could use [HttpProvider](/api/ethereum.html#http-provider). For more information about other providers for Ethereum, such as Bitski, please click [here](/api/ethereum.html#api-ethereum), and to learn more about providers for Wanchain, please click [here](/api/wanchain.html#api-wanchain).
+Even within the same blockchain, you can use multiple providers depending on your needs. If you would like to communicate with the blockchain on the front-end, you could use [MetamaskProvider](/framework/v2/api/ethereum-connectors.html#metamask-provider), while for communication on the back-end you could use [HttpProvider](/framework/v2/api/ethereum-connectors.html#http-provider). For more information about other providers for Ethereum, such as Bitski, please click [here](/framework/v2/api/ethereum-connectors.html#api-ethereum), and to learn more about providers for Wanchain, please click [here](/framework/v2/api/wanchain-connectors.html#api-wanchain).
 
 In this guide, we will be using the MetaMask provider for the Ethereum blockchain. [MetaMask](https://metamask.io/) is a popular plug-in that allows you to create and store the private keys for your Ethereum account inside your browser or mobile device. It works as a bridge between your browser and the Ethereum blockchain through its own infrastructure. MetaMask can also be paired with hardware wallets such as [Ledger](https://www.ledger.com/) or [Trezor](https://trezor.io/).
 
@@ -20,11 +20,11 @@ We recommend you employ the provider module as an NPM package in your applicatio
 $ npm i --save @0xcert/ethereum-metamask-provider
 ```
 
-On our official [GitHub repository](https://github.com/0xcert/framework), we also host a compiled and minimized JavaScript file that can be directly implemented into your website. Please refer to the [API](/api/ethereum.html) section to learn more about other providers.
+On our official [GitHub repository](https://github.com/0xcert/framework), we also host a compiled and minimized JavaScript file that can be directly implemented into your website. Please refer to the [API](/framework/v2/api/ethereum-connectors.html) section to learn more about other providers.
 
 ## Usage overview
 
-To start developing the application, we have to first instantiate the [MetamaskProvider](/api/ethereum.html#metamask-provider) provider class. This is usually only needed once within the application.
+To start developing the application, we have to first instantiate the [MetamaskProvider](/framework/v2/api/ethereum-connectors.html#metamask-provider) provider class. This is usually only needed once within the application.
 
 ```ts
 import { MetamaskProvider } from '@0xcert/ethereum-metamask-provider';