Upd deps

Author: TheParaziT

blog/authors.yml

@@ -146,6 +146,12 @@ mortany:
   socials:
     github: mortany
 
+aziatka_victor:
+  name: AziatkaVictor
+  image_url: https://github.com/AziatkaVictor.png
+  socials:
+    github: AziatkaVictor
+
 vaierok:
   name: VaIeroK
   image_url: https://github.com/VaIeroK.png

docs/for-contributors/book-style-sheet.md

@@ -49,17 +49,19 @@ Objective: To create a glossary of specific terms unique to the S.T.A.L.K.E.R. u
 
 5. Admonitions
 
-    - Docusaurus provides convenient and stylish blocks for highlighting information.
+    - Docusaurus provides convenient and stylish blocks for highlighting information ([Read Docs](https://docusaurus.io/docs/markdown-features/admonitions)).
 
 6. Blank line
 
     - All files must end with a single blank line character. This is standard for Unix systems and the requirements of many linters.
 
 ## Tools
 
-To maintain a consistent style, use the Markdownlint extension.
+To maintain a consistent style, use the [Markdownlint](https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint) extension.
 
 - Disabled rules:
   - MD033 (no-inline-html)
   - MD013 (line-length)
   - MD010 (no-hard-tabs)
+
+For convenient metadata editing, you can use [Front Matter CMS](https://marketplace.visualstudio.com/items?itemName=eliostruyf.vscode-front-matter).

docs/for-contributors/creating-tag.md

@@ -1,6 +1,6 @@
 ---
 title: Creating Tag
-description: Instructions for creating and managing tags in the documentation system
+description: Instructions for creating and managing tags in the documentation
 ---
 
 # Creating Tag

docs/modding-tools/animations/omf-editor-by-valerok.md

@@ -36,6 +36,10 @@ ___
       <td>Source Code</td>
       <td>[GitHub](https://github.com/VaIeroK/Omf-Editor)</td>
     </tr>
+    <tr>
+      <td>Documentation</td>
+      <td>[DeepWiki](https://deepwiki.com/VaIeroK/Omf-Editor)</td>
+    </tr>
   </tbody>
 </table>
 

docs/modding-tools/audio-video/ffmpeg2theora.md

@@ -14,6 +14,7 @@ ___
 ## Info
 
 <table>
+<tbody>
     <tr>
         <td>Program Developer</td>
         <td>V2V</td>
@@ -22,10 +23,9 @@ ___
         <td>Described Version</td>
         <td>0.30</td>
     </tr>
+    </tbody>
 </table>
 
-___
-
 ## About
 
 This package provides a command-line tool to encode/recode various video formats (basically everything that ffmpeg can read) into [Theora](https://en.wikipedia.org/wiki/Theora), the free video codec.

docs/modding-tools/models/xray-export-tool.md

@@ -38,6 +38,10 @@ ___
       <td>Source Code</td>
       <td>[GitHub](https://github.com/VaIeroK/XrayExportTool)</td>
     </tr>
+    <tr>
+      <td>Documentation</td>
+      <td>[DeepWiki](https://deepwiki.com/VaIeroK/XrayExportTool)</td>
+    </tr>
   </tbody>
 </table>
 

docs/references/animations/skeletons-list.md

@@ -1,5 +1,6 @@
 ---
 title: Skeletons List
+draft: true
 ---
 
 # Skeletons List

docs/references/audio/sound-environment-list.md

@@ -1,5 +1,6 @@
 ---
 title: Sound Environment List
+draft: true
 ---
 
 # Sound Environment List

docs/references/configs/algorithm-of-logic.md

@@ -9,6 +9,13 @@ preview: /docs/references/configs/assets/images/algorithm-of-logic-preview.png
 
 ___
 
+<Authors
+  authors={["aziatka_victor"]}
+  size="medium"
+  showTitle={true}
+  showDescription={true}
+/>
+
 ## About
 
 "Executable" files, game logic files, unlike config files, have an algorithm that, if I'm not mistaken, is based on scripts. The peculiarity of such files is that they have a "Current Section", which defines reactions to interactions with it. Let's look at an example:

docs/references/configs/structure-of-files.md

@@ -10,6 +10,13 @@ preview: /docs/references/configs/assets/images/structure-of-files-preview.png
 
 ___
 
+<Authors
+  authors={["aziatka_victor"]}
+  size="medium"
+  showTitle={true}
+  showDescription={true}
+/>
+
 ## About
 
 The files may differ from each other, depending on their purpose, but they all have properties in common.