From 0dcd12a34f94e7e0407d8302ccae28645a143128 Mon Sep 17 00:00:00 2001
From: Styloy <100509373+Styloy@users.noreply.github.com>
Date: Tue, 5 Dec 2023 08:44:20 -0500
Subject: [PATCH] add *.info.json examples and info (#25)

---
 mkdocs/docs/settings/actions.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/mkdocs/docs/settings/actions.md b/mkdocs/docs/settings/actions.md
index 665e22c..bb6b288 100644
--- a/mkdocs/docs/settings/actions.md
+++ b/mkdocs/docs/settings/actions.md
@@ -24,6 +24,33 @@ Add a matching *.info.json* file with the media file. Both files need to have th
 
 The import process then looks for the 'id' key within the JSON file to identify the video.
 
+
+Sometimes you may need to create this file manually, The following are the absolute minimum required tags for manual importing.
+
+`thumbnail` can be left blank or null, however it is required to be present. If blank the thumbnail will be extracted from the video file on import.
+```
+{
+  "id": "",
+  "channel_id": "",
+  "title": "",
+  "upload_date": "",
+  "thumbnail": null
+}
+```
+However, you may fill out additional tags if they are known for a more complete result.
+```
+{
+  "id": "",
+  "channel_id": "",
+  "title": "",
+  "upload_date": "",
+  "description": null,
+  "categories": null,
+  "thumbnail": null,
+  "tags": null,
+  "view_count": null
+}
+```
 ### Method 2:
 Detect the YouTube ID from filename, this accepts the default yt-dlp naming convention for file names like: