Merge branch 'master' into markupupdate

Author: sanjam-deriv

.eslintignore

@@ -3,4 +3,5 @@ docusaurus.config.js
 jest.config.js
 commitlint.config.js
 babel.config.js
-examples
+examples
+src/theme

config/v3/app_register/send.json

@@ -14,9 +14,9 @@
       "enum": [1]
     },
     "app_markup_percentage": {
-      "description": "[Optional] Markup to be added to contract prices (as a percentage of contract payout).",
+      "description": "[Optional] Markup to be added to contract prices (as a percentage of contract payout). Max markup: 3%.",
       "type": "number",
-      "maximum": 5,
+      "maximum": 3,
       "minimum": 0
     },
     "appstore": {

config/v3/app_update/send.json

@@ -13,9 +13,9 @@
       "type": "integer"
     },
     "app_markup_percentage": {
-      "description": "[Optional] Markup to be added to contract prices (as a percentage of contract payout).",
+      "description": "[Optional] Markup to be added to contract prices (as a percentage of contract payout). Max markup: 3%.",
       "type": "number",
-      "maximum": 5,
+      "maximum": 3,
       "minimum": 0
     },
     "appstore": {

docs/code-examples/javascript/keep-alive/index.mdx

@@ -16,9 +16,12 @@ keywords:
 description: Keep Alive code example
 ---
 
+import RenderOfficialContents from '@site/src/components/RenderOfficialContents';
 import SandboxIframe from '@site/src/components/SandboxIframe';
 import { sandboxes } from '@site/src/components/SandboxIframe/utility/sandboxes';
 
-In this example you'll see how to keep a connection alive when getting contract proposals via the Deriv API. This example keeps the connection alive by sending a ping every 30 seconds.
+<RenderOfficialContents>
+  <p>In this example you'll see how to keep a connection alive when getting contract proposals via the Deriv API. This example keeps the connection alive by sending a ping every 30 seconds.</p>
+</RenderOfficialContents>
 
 <SandboxIframe sandbox={sandboxes.keep_alive} />

docs/code-examples/javascript/ticks-history/index.mdx

@@ -16,13 +16,16 @@ keywords:
 description: Ticks History code example
 ---
 
+import RenderOfficialContents from '@site/src/components/RenderOfficialContents';
 import SandboxIframe from '@site/src/components/SandboxIframe';
 import { sandboxes } from '@site/src/components/SandboxIframe/utility/sandboxes';
 
 With ticks history you are able to get a collection of past tick times and prices.
 
 <SandboxIframe sandbox={sandboxes.ticks_history} />
 
-We subscribe to the ticks functionality from the Deriv API websocket to keep track of current and past ticks.
+<RenderOfficialContents>
+  <p>We subscribe to the ticks functionality from the Deriv API websocket to keep track of current and past ticks.</p>
+</RenderOfficialContents>
 
 As an example you could create an interactive tick graph.

docs/code-examples/javascript/ticks/index.mdx

@@ -14,13 +14,20 @@ keywords:
 description: Ticks code example
 ---
 
+import RenderOfficialContents from '@site/src/components/RenderOfficialContents';
 import SandboxIframe from '@site/src/components/SandboxIframe';
 import { sandboxes } from '@site/src/components/SandboxIframe/utility/sandboxes';
 
-The easiest way to understand how Deriv API works is to try our Tick call:
+<RenderOfficialContents>
+  <p>The easiest way to understand how Deriv API works is to try our Tick call:</p>
+</RenderOfficialContents>
 
 <SandboxIframe sandbox={sandboxes.ticks} />
 
-We'll start with the ticks example because it's a pretty simple block of code to implement. You don't have to log into the Deriv account and get your app authenticated to try it.
+<RenderOfficialContents>
+  <p>We'll start with the ticks example because it's a pretty simple block of code to implement. You don't have to log into the Deriv account and get your app authenticated to try it.</p>
+</RenderOfficialContents>
 
-A tick is a measure of minimum upward or downward movement in the price of a trading commodity. We subscribe to the ticks functionality from the Deriv API websocket, which will return new tick data every second. As an example you could create an interactive tick graph with this data.
+<RenderOfficialContents>
+  <p>A tick is a measure of minimum upward or downward movement in the price of a trading commodity. We subscribe to the ticks functionality from the Deriv API websocket, which will return new tick data every second. As an example you could create an interactive tick graph with this data.</p>
+</RenderOfficialContents>

docs/core-concepts/_category_.json

@@ -1,4 +1,5 @@
 {
+  "className": "hide-sidebar-item",
   "label": "Core concepts",
   "position": 2,
   "link": {

docs/core-concepts/api-calls-anatomy/index.md

@@ -24,9 +24,9 @@ All API calls have a send functionality for making a request and receiving a res
 
 Several API calls provide the `subscribe` functionality. When you subscribe to an API call, you will receive a continuous stream from data of this particular API call.
 
-Some of these API calls automatically subscribe (e.g. [ticks](https://api.deriv.com/api-explorer#ticks)) and some have an optional `subscribe` field. If you pass `1` to the `subscribe` field, the subscription will start and the server will continue to send the requested data until you unsubscribe by calling the `Forget` or `Forget all` API calls.
+Some of these API calls automatically subscribe (e.g. [ticks](/api-explorer#ticks)) and some have an optional `subscribe` field. If you pass `1` to the `subscribe` field, the subscription will start and the server will continue to send the requested data until you unsubscribe by calling the `Forget` or `Forget all` API calls.
 
-For example, you can call [Tick History](https://api.deriv.com/api-explorer#ticks_history) to receive tick history data. But when you add the `subscribe` option to this call, you will receive the tick history data you requested in the first response, and you will continue to receive a new response every time there is a new tick published by the server for the given symbol.
+For example, you can call [Tick History](/api-explorer#ticks_history) to receive tick history data. But when you add the `subscribe` option to this call, you will receive the tick history data you requested in the first response, and you will continue to receive a new response every time there is a new tick published by the server for the given symbol.
 
 In the message stream from `subscribe`, there is a field called `subscription`. This is the `Stream ID`. With this ID, you can identify the message stream in your logic and stop the stream with `Forget` and `Forget All` API calls.
 
@@ -41,7 +41,7 @@ If you call the API with the `send` functionality, then the server will only sen
 If you want to stop the message stream created by `subscribe`, you will have to call the `Forget` API call with the correct `Stream ID`. Otherwise, you can use the `Forget All` API call to stop streams by their `Method name`.
 
 :::caution
-For more information on the `Forget` API call, have a look at [Forget](https://api.deriv.com/api-explorer#forget) and [Forget All](https://api.deriv.com/api-explorer#forget_all) in the API explorer.
+For more information on the `Forget` API call, have a look at [Forget](/api-explorer#forget) and [Forget All](/api-explorer#forget_all) in the API explorer.
 :::
 
 ## Request data
@@ -64,15 +64,15 @@ A `Residence List` call returns a list of countries and 2-letter country codes,
 
 The request data for this call is as below:
 
-```ts
+```ts showLineNumbers
 {
   residence_list: 1; // Api Call Method Name
   passthrough?: object; // Optional
   req_id?: number; // Optional
 }
 ```
 
-The `residence_list` field is the `method name` for the call and is required. There may be other required fields related to this type of the request you want to send. To know more about `Residence List` and other API calls, please check them out in [API Explorer](https://api.deriv.com/api-explorer#residence_list).
+The `residence_list` field is the `method name` for the call and is required. There may be other required fields related to this type of the request you want to send. To know more about `Residence List` and other API calls, please check them out in [API Explorer](/api-explorer#residence_list).
 
 ### Optional fields
 
@@ -87,7 +87,7 @@ Whatever you pass to this field will be returned back to you inside a `response`
 You may need to `tag` your requests and pass them through our `WebSocket` calls. You can do so by passing a `number` to this field. It can be helpful when you need to map `requests` to `responses`.
 
 :::caution
-To learn about additional optional fields specific to each API call, please refer to our [API Explorer](https://api.deriv.com/api-explorer).
+To learn about additional optional fields specific to each API call, please refer to our [API Explorer](/api-explorer).
 :::
 
 ## Response data
@@ -96,7 +96,7 @@ When you get the response for the call, there will be a `Field` with the same na
 
 The response for the `Residence List` call:
 
-```js
+```js showLineNumbers
 {
   echo_req: {
     req_id: 1,
@@ -163,7 +163,7 @@ The response for the `Residence List` call:
 };
 ```
 
-Here the `residence_list` is the `method name`, and it contains the actual data you requested. To keep it short, we haven't included the rest of the array. You can check the actual response [here](https://api.deriv.com/api-explorer#residence_list).
+Here the `residence_list` is the `method name`, and it contains the actual data you requested. To keep it short, we haven't included the rest of the array. You can check the actual response [here](/api-explorer#residence_list).
 
 #### The `echo_req` field
 
@@ -173,7 +173,7 @@ This `Field` contains the exact `Request Data` you sent to the server.
 
 This `Field` helps you determine which `message` data you're getting on the message event of the WebSocket connection. For example, your `onmessage` event handler for your WebSocket connection in `JavaScript` would be:
 
-```js
+```js showLineNumbers
 socket.onmessage = (event) => {
   const receivedMessage = JSON.parse(event.data);
 

docs/core-concepts/authorization-authentication/index.md

@@ -33,7 +33,7 @@ Please refer to [Setting up a Deriv application](docs/setting-up-a-deriv-applica
 
 An API token is a unique identifier of a client that requests access from a server. It's the simplest way of authorisation.
 
-The access level for each API token has to match the required access level of each API call, which can be found in the [API Explorer](https://api.deriv.com/api-explorer) as well.
+The access level for each API token has to match the required access level of each API call, which can be found in the [API Explorer](/api-explorer) as well.
 
 For example, on the screenshot below, you can see that to be able to use the Account Status, a token with read access level must be used.
 
@@ -71,7 +71,7 @@ Once a user signs up/logs in, they will be redirected to the URL that you entere
 
 The query parameters in the redirect URL are the user's accounts and their related session tokens. You can map the query parameters to an array using the following approach:
 
-```js
+```js showLineNumbers
 const user_accounts = [
   {
     account: 'cr799393',
@@ -86,17 +86,17 @@ const user_accounts = [
 ];
 ```
 
-To authorise the user based on the user's **selected** account, call the [authorize](https://api.deriv.com/api-explorer#authorize) API call with the user's **selected** account **session token**:
+To authorise the user based on the user's **selected** account, call the [authorize](/api-explorer#authorize) API call with the user's **selected** account **session token**:
 
-```js
+```js showLineNumbers
 {
   "authorize": "a1-f7pnteezo4jzhpxclctizt27hyeot"
 }
 ```
 
 The response for the `authorize` call would be an object as below:
 
-```js
+```js showLineNumbers
 {
     "account_list": [
       {

docs/core-concepts/websocket/index.md

@@ -47,7 +47,7 @@ Sending a message can be done via socket.send(data).
 
 Here’s an example in `JavaScript`:
 
-```js
+```js showLineNumbers
 const app_id = 1089; // Replace with your app_id or leave as 1089 for testing.
 const socket = new WebSocket(`wss://ws.binaryws.com/websockets/v3?app_id=${app_id}`);