Quick fixes

apivideo · Sep 12, 2023 · 48e4498 · 48e4498
1 parent 4c08de7
commit 48e4498
Show file tree

Hide file tree

Showing 42 changed files with 19 additions and 22 deletions.
diff --git a/README.md b/README.md
@@ -54,8 +54,6 @@ api.video lets you customize a large part of the delivery, whether it's the play
 
 <hr/>
 
-### Section header
-
 ## Quick links
 
 </div>
@@ -94,13 +92,10 @@ api.video lets you customize a large part of the delivery, whether it's the play
 
 <hr/>
 
-### Section header
-
 ## Need help?
 
 </div>
 
-
 <div class="support-cards">
 {% include "_partials/support-card.md" label: "Browse Help Center", icon: "/_assets/icons/js.svg", link: "https://help.api.video/en/" %}
 {% include "_partials/support-card.md" label: "Ask the Community", icon: "/_assets/icons/js.svg", link: "https://community.api.video/" %}

diff --git a/_assets/delivery-analytics/custom-domains/custom-domains-dark.png b/_assets/delivery-analytics/custom-domains/custom-domains-dark.png
diff --git a/_assets/delivery-analytics/custom-domains/custom-domains-light.png b/_assets/delivery-analytics/custom-domains/custom-domains-light.png
diff --git a/_assets/delivery-analytics/private-videos/private-video-reusability-dark.png b/_assets/delivery-analytics/private-videos/private-video-reusability-dark.png
diff --git a/_assets/delivery-analytics/private-videos/private-video-reusability-light.png b/_assets/delivery-analytics/private-videos/private-video-reusability-light.png
diff --git a/_assets/delivery-analytics/private-videos/private-videos-dark.png b/_assets/delivery-analytics/private-videos/private-videos-dark.png
diff --git a/_assets/delivery-analytics/private-videos/private-videos-light.png b/_assets/delivery-analytics/private-videos/private-videos-light.png
diff --git a/_assets/delivery-analytics/private-videos/session-token-dark.png b/_assets/delivery-analytics/private-videos/session-token-dark.png
diff --git a/_assets/delivery-analytics/private-videos/session-token-light.png b/_assets/delivery-analytics/private-videos/session-token-light.png
diff --git a/_assets/delivery-analytics/private-videos/single-session-token-dark.png b/_assets/delivery-analytics/private-videos/single-session-token-dark.png
diff --git a/_assets/delivery-analytics/private-videos/single-session-token-light.png b/_assets/delivery-analytics/private-videos/single-session-token-light.png
diff --git a/_assets/get-started/authentication/disposable-bearer-token-dark.png b/_assets/get-started/authentication/disposable-bearer-token-dark.png
diff --git a/_assets/get-started/authentication/disposable-bearer-token-light.png b/_assets/get-started/authentication/disposable-bearer-token-light.png
diff --git a/_assets/get-started/start-building/what-is-api-video-dark.png b/_assets/get-started/start-building/what-is-api-video-dark.png
diff --git a/_assets/get-started/start-building/what-is-api-video-light.png b/_assets/get-started/start-building/what-is-api-video-light.png
diff --git a/_assets/live-streaming/restreams/restreams-dark.png b/_assets/live-streaming/restreams/restreams-dark.png
diff --git a/_assets/live-streaming/restreams/restreams-light.png b/_assets/live-streaming/restreams/restreams-light.png
diff --git a/_assets/reference/disposable-bearer-auth/disposable-bearer-token-dark.png b/_assets/reference/disposable-bearer-auth/disposable-bearer-token-dark.png
diff --git a/_assets/reference/disposable-bearer-auth/disposable-bearer-token-light.png b/_assets/reference/disposable-bearer-auth/disposable-bearer-token-light.png
diff --git a/_assets/reference/video-best-practices/create-a-video-dark.png b/_assets/reference/video-best-practices/create-a-video-dark.png
diff --git a/_assets/reference/video-best-practices/create-a-video-light.png b/_assets/reference/video-best-practices/create-a-video-light.png
diff --git a/_assets/reference/webhooks/webhooks-dark.png b/_assets/reference/webhooks/webhooks-dark.png
diff --git a/_assets/reference/webhooks/webhooks-light.png b/_assets/reference/webhooks/webhooks-light.png
diff --git a/_assets/vod/add-watermarks/watermark-dark.png b/_assets/vod/add-watermarks/watermark-dark.png
diff --git a/_assets/vod/add-watermarks/watermark-light.png b/_assets/vod/add-watermarks/watermark-light.png
diff --git a/_assets/vod/upload-tokens/upload-token-dark.png b/_assets/vod/upload-tokens/upload-token-dark.png
diff --git a/_assets/vod/upload-tokens/upload-token-light.png b/_assets/vod/upload-tokens/upload-token-light.png
diff --git a/_assets/vod/video-object/create-a-video-dark.png b/_assets/vod/video-object/create-a-video-dark.png
diff --git a/_assets/vod/video-object/create-a-video-light.png b/_assets/vod/video-object/create-a-video-light.png
diff --git a/delivery-analytics/private-video-get-started.md b/delivery-analytics/private-video-get-started.md
@@ -38,7 +38,7 @@ After you learn how private video works and what it’s good for, we can now tal
 
 To reiterate the private video concept, here’s a visual representation of how the whole thing works:
 
-![](/_assets/private-videos.png)
+{% include "_partials/dark-light-image.md" dark: "/_assets/delivery-analytics/private-videos/private-videos-dark.png", light: "/_assets/delivery-analytics/private-videos/private-videos-light.png" %}
 
 Knowing that now we can finally start building stuff! 
 
@@ -145,9 +145,7 @@ There are two types of tokens for private videos:
 
 At a very high level, to request different assets for the same private video, more than having the private token is required; you also need to retain the session. For that, we have the session token. In the flowchart below, you can see that for each private video, we are using a session token + the private token:
 
-![](/_assets/vod/demo-private-video/52f1d35-Private_videos_post_-_15FEB23.png "Private videos post - 15FEB23.png")
-
-
+{% include "_partials/dark-light-image.md" dark: "/_assets/delivery-analytics/private-videos/single-session-token-dark.png", light: "/_assets/delivery-analytics/private-videos/single-session-token-light.png" %}
 
 So let’s get a bit technical here. To start the session, you will need to request the `/session` endpoint, get the session token, add it to the first asset you request, and then add it to every following asset you request. In the example above, we will request the `/session` endpoint, then add the session token to the query string of the private video thumbnail → request an embedded video asset with the session token in the query string → request a private video asset in mp4 format with the session token, and so on, you got the idea 😄
 

diff --git a/delivery-analytics/private-video-session-tokens.md b/delivery-analytics/private-video-session-tokens.md
@@ -13,8 +13,9 @@ In order to preserve the session and give the ability to make requests to multip
 
 The session starts with the /session endpoint where we get the session token from which then cached in the browser cache and used to make the requests to multiple assets later.
 
-Once the session token is acquired, it is reused in all other requests to the different assets. 
-![Imported image](/_assets/Session%20Token.jpg)
+Once the session token is acquired, it is reused in all other requests to the different assets.
+
+{% include "_partials/dark-light-image.md" dark: "/_assets/delivery-analytics/private-videos/session-token-dark.png", light: "/_assets/delivery-analytics/private-videos/session-token-light.png" %}
 
 {% capture content %}
 **Time to Live**

diff --git a/delivery-analytics/using-custom-domains.md b/delivery-analytics/using-custom-domains.md
@@ -12,7 +12,7 @@ Using Custom Domains
 
 api.video enables you to deliver video content and provide live streams using your own custom domains. You can decide what custom URL or subdomain you use in your implementation, for example `live.mycustomdomain.com`.
 
-![Imported image](/_assets/custom-domains.png)
+{% include "_partials/dark-light-image.md" dark: "/_assets/delivery-analytics/custom-domains/custom-domains-dark.png", light: "/_assets/delivery-analytics/custom-domains/custom-domains-light.png" %}
 
 You can maintain your company branding by utilizing custom domains in any of these use cases, and more:
 

diff --git a/delivery-analytics/video-privacy-access-management.md b/delivery-analytics/video-privacy-access-management.md
@@ -18,7 +18,7 @@ A **private token** is a string of unique numbers and letters. For example: `009
 {% endcapture %}
 {% include "_partials/callout.html" kind: "info", content: content %}
 
-![](/_assets/private-videos.png)
+{% include "_partials/dark-light-image.md" dark: "/_assets/delivery-analytics/private-videos/private-videos-dark.png", light: "/_assets/delivery-analytics/private-videos/private-videos-light.png" %}
 
 ### How to create private videos?
 
@@ -42,6 +42,6 @@ You can see that for each url the token will be included in different places. Fo
 
 You can [retrieve a video](/reference/api/Videos#retrieve-a-video-object) via the API, which will generate the private token while you retrieve it. Each time you make a new request to retrieve a video it will generate a new private token. Hence, if the same user would like to play the video multiple times, on different pages you'll need to make a request to the `https://ws.api.video/videos/{videoId}` endpoint mentioned above in order to get a new private token.
 
-![](/_assets/private-video-reusability.jpg)
+{% include "_partials/dark-light-image.md" dark: "/_assets/delivery-analytics/private-videos/private-video-reusability-dark.png", light: "/_assets/delivery-analytics/private-videos/private-video-reusability-light.png" %}
 
 Once you've retrieved the video you can either use api.video player or an external player to play it back for the user. Hence the user can play it back for as long as the session lives, which is 24 hours in this case. When the session has ended, you will have to generate a new private token.
diff --git a/get-started/authentication-guide.md b/get-started/authentication-guide.md
@@ -56,7 +56,7 @@ Bearer authentication (also called token authentication) is an HTTP authenticati
 
 api.video provides an enhanced security authentication method, which uses a disposable bearer token that has a short time to live and has to be refreshed every 3600 seconds.
 
-![](/_assets/disposable-bearer-token-authentication.png)
+{% include "_partials/dark-light-image.md" dark: "/_assets/get-started/authentication/disposable-bearer-token-dark.png", light: "/_assets/get-started/authentication/disposable-bearer-token-light.png" %} 
 
 Bearer token authentication is simple to set up and use; however, we encourage you to use one of our client libraries if possible. [api.video client libraries](/sdks/api-clients) handle authentication for you, including renewing your token as needed.
 

diff --git a/get-started/start-building.md b/get-started/start-building.md
@@ -14,7 +14,7 @@ Within this section, you can find essential insights into building with api.vide
 
 ## What is api.video?
 
-{% include "_partials/dark-light-image.md" dark: "/_assets/getting-started-diagram-dark.png", light: "/_assets/getting-started-diagram-light.png" %}
+{% include "_partials/dark-light-image.md" dark: "/_assets/get-started/start-building/what-is-api-video-dark.png", light: "/_assets/get-started/start-building/what-is-api-video-light.png" %}
 
 api.video is a cloud-based video hosting and live streaming platform that provides developers and businesses with an easy-to-use API to handle all video-related tasks. The platform offers a range of features to help developers and businesses manage video content, including video hosting, transcoding, player customization, live streaming, and analytics.
 

diff --git a/live-streaming/restreams.md b/live-streaming/restreams.md
@@ -12,7 +12,7 @@ api.video gives you the ability to broadcast a live stream to multiple platforms
 
 ## How it works
 
-![](/_assets/live-streaming/restreams/edc6e78-restreams-diagram.jpg)
+{% include "_partials/dark-light-image.md" dark: "/_assets/live-streaming/restreams/restreams-dark.png", light: "/_assets/live-streaming/restreams/restreams-light.png" %}
 
 You can add restreams to an existing live stream or you can create a live stream that already includes the restream list.   
 

diff --git a/reference/create-and-manage-webhooks.md b/reference/create-and-manage-webhooks.md
@@ -25,7 +25,7 @@ api.video provides you the possibility to get a `POST` request to your server th
 
 Here’s how the `video.encoding` webhook’s flow looks like:
 
-![](/_assets/webhooks-schema.png)
+{% include "_partials/dark-light-image.md" dark: "/_assets/reference/webhooks/webhooks-dark.png", light: "/_assets/reference/webhooks/webhooks-light.png" %}
 
 ## Event properties
 

diff --git a/reference/disposable-bearer-token-authentication.md b/reference/disposable-bearer-token-authentication.md
@@ -5,7 +5,7 @@ We provide an enhanced security authentication method, which uses a disposable b
 
 ## How it works?
 
-![](/_assets/disposable-bearer-token-authentication.png)
+{% include "_partials/dark-light-image.md" dark: "/_assets/reference/disposable-bearer-auth/disposable-bearer-token-dark.png", light: "/_assets/reference/disposable-bearer-auth/disposable-bearer-token-light.png" %}
 
 _Fig. 1_
 

diff --git a/reference/video-best-practices.md b/reference/video-best-practices.md
@@ -12,7 +12,7 @@ A tutorial for uploading a video with curl can be found [here](https://api.video
 
 A more visual representation can be found below:
 
-![](/_assets/reference/video-best-practices/fee60cd-Create_a_video_flowchart.png "Create a video flowchart.png")
+{% include "_partials/dark-light-image.md" dark: "/_assets/reference/video-best-practices/create-a-video-dark.png", light: "/_assets/reference/video-best-practices/create-a-video-light.png" %}
 
 {% capture content %}
 **Important things to know**

diff --git a/vod/add-a-permanent-watermark.md b/vod/add-a-permanent-watermark.md
@@ -26,7 +26,8 @@ Watermarks are uploaded separately from videos. You will need to upload the wate
 {% endcapture %}
 {% include "_partials/callout.html" kind: "warning", content: content %}
 
-![](/_assets/watermark-diagram.jpg)
+
+{% include "_partials/dark-light-image.md" dark: "/_assets/vod/add-watermarks/watermark-dark.png", light: "/_assets/vod/add-watermarks/watermark-light.png" %}
 
 ## Supported Image formats
 

diff --git a/vod/delegated-upload-tokens.md b/vod/delegated-upload-tokens.md
@@ -10,6 +10,8 @@ Using delegated upload tokens
 
 You can upload videos using the traditional two-step process where you create a video container then upload your video into your container. You can also upload a video using a **delegated upload token**. This guide explains how to create, list, retrieve, and delete delegated upload tokens, and how to upload videos with them.
 
+{% include "_partials/dark-light-image.md" dark: "/_assets/vod/upload-tokens/upload-token-dark.png", light: "/_assets/vod/upload-tokens/upload-token-light.png" %}
+
 In this type of upload, you retrieve a token from the tokens endpoint. You can then directly upload using the token upload endpoint. It's one step, and you don't provide anything except the file. You can update the metadata for the upload later. A benefit of a delegated token is that you define the TTL (time-to-live) value, so it expires only when you need it to. You can always use the token to upload. You can also create delegated tokens for others to use to do uploads.
 
 * Anyone who has a token can make an upload, so be careful how you set and manage tokens.

diff --git a/vod/video-object.md b/vod/video-object.md
@@ -15,7 +15,7 @@ The [video object](https://docs.api.video/reference/videos-1) in reference to ap
 
 Before you [upload a video](https://docs.api.video/reference/post_videos-videoid-source), you need to[ create the video object](https://docs.api.video/reference/post-video) that will contain the video itself (once uploaded). 
 
-![](/_assets/vod/video-object/06e7947-image.png)
+{% include "_partials/dark-light-image.md" dark: "/_assets/vod/video-object/create-a-video-dark.png", light: "/_assets/vod/video-object/create-a-video-light.png" %}
 
 The video object has properties and metadata that you can create and update, below are the attributes that are available for the video object.