Update docs to: docs: Add more about action scripts (#85)

Author: github-actions[bot]

docs/action_scripts.md

@@ -0,0 +1,56 @@
+# Action Scripts in Text Forge
+
+Action Scripts are a way to separate and manage possible actions in the Text Forge, helping them keep dozens of 
+different capabilities separately and safely and add new capabilities in the shortest time.
+
+## Design goals
+
+- Modularity: Each action script is an independent unit with a specified output and input, almost all Action Scripts are
+  detachable from the editor without making an error in its performance
+- Development: Developers can design new capabilities through simple Action Script APIs 
+- Accessibility: Action Scripts are easily accessible through code, command palette, and shortcuts
+
+## Structure
+
+An action script must extend `ActionScript` or `MultiActionScript` class or another class that extends one of these 
+classes. Each action script should be stored in `action_scripts/` directory and have snake_case file name of an option 
+english name in menus. For example if we have a `Save As...` option in `File` menu, editor will load `action_scripts/save_as.gd`
+as its action script (will remove dots) and otherwise this action script will not be loaded.
+
+Also, action scripts can have a shortcut in `shortcuts/` directory with same name. This file should be a `Shortcut` 
+resource (`.tres` file) with a `InputEventKey` as shortcut. Loading shortcut will be done by `ActionScript` class.
+
+All loaded action script will be children nodes of `Scripts` node in core, you can use `Global.get_scripts_node()` to 
+access to it.
+
+Each action script should override base class `Virtual` functions, you can see them in docstrings. There is a list of 
+virtual functions of regular `ActionScript`:
+- `_initialize()`: For action script initializing
+- `_run_action()`: Main part of action script
+
+## Features
+
+### Access to menu option
+
+Each action script have an item in menus, this item is accessible with `menu` and `index` property of action script.
+For checkbox and radio-checkbox options, editor will handle checking state itself.
+
+### Automated shortcut loading
+
+`ActionScript` and `MultiActionScript` class will load shortcuts from `shortcuts/` directory and call required functions
+in shortcut pressing.
+
+### Define commands
+
+An action script will define itself as a command for command palette, so command palettes can list action scripts for
+user and run them based on selections. If an action script has shortcut, it will add that shortcut in commands database 
+so users can see shortcuts in command palette.
+
+### Automated enabling / disabling
+
+`requires_file` and `requires_saved_file` properties can be used to make smarter action scripts, must action scripts
+just available when there is an opened file, so `requires_file == true` can disable them other times.
+
+## Create new action scripts
+
+To add new action scripts (or edit existing one) see [here](create_action_scripts.md).

docs/create_action_scripts.md

@@ -0,0 +1,67 @@
+# Create action scripts
+
+!!! Note
+    Reading [Action Scripts Guide](action_scripts.md) is recommended before creating actions scripts.
+
+## Regular action scripts
+
+There is some different types of action scripts based on their base classes, `ActionScript` class designed for regular
+action scripts and can handle a lot of tasks.
+
+To add new action script you should make sure there is an item in menus for that action script, you can use `data/main_ui.ini`
+to add new options (or menus), to understand about structure of this file you can see [here](https://text-forge.github.io/docs/data_driven_ui/#menus).
+After select your option create a script in `action_scripts/` directory with same name (but in snake_case), it this case
+we will create **Copy Path** action script that will copy file path of opened file in clipboard, so we will create
+`action_scripts/copy_path.gd` and use this script as start point:
+
+```gdscript
+extends ActionScript
+```
+
+Just that! Run project and see option is enabled. But there is no action for now, so we have 3 steps to complete our 
+action script:
+
+### Add initializing
+
+We needn't any special initializing for this action script, all we need is disabling it when there is no opened file, 
+there is ready-made feature for this:
+
+```gdscript
+extends ActionScript
+
+func _initialize() -> void:
+    requires_file = true
+    requires_saved_file = true
+```
+
+With this function `ActionScript` class will disable option when there isn't saved file, it means when you create a new
+file this option will keep disabled until that file saved, because before that there is no file path. Otherwise, (for 
+example when user uses Open) option will be enabled.
+
+### Add main action
+
+We have initialized action script, but there is no action, so let's add it. To do this we use `_run_action()` function,
+this function will be called when user clicks in option in menus, presses shortcut (we will add shortcut later) or uses
+command palette. So we can complete our action script with this function:
+
+```gdscript
+extends ActionScript
+
+func _initialize() -> void:
+	requires_file = true
+	requires_saved_file = true
+
+func _run_action() -> void:
+	DisplayServer.clipboard_set(Global.get_file_path())
+```
+
+Almost done! We have completed action script, and you can try it now in witch way you want.
+
+### Add shortcut
+
+There is an easy way for adding shortcuts to action scripts, so let's see how we can do it. To have shortcut we need a
+`Shortcut` resource stored in `shortcuts/` directory, so go to Godot's FileSystem dock and use RMB on `res://shortcuts/`,
+then click on Create New > Resource... and create a `Shortcut` resource and save it as `copy_path.tres`. Shortcut will
+be opened in Inspector, click on `Events` and add new element, then create a new `InputEventKey` in that element. Use 
+`Configure` button and set your shortcut, then run project and try it. You can open command palette (Ctrl+P) and type `copy path`
+to see shortcut.

mkdocs.yml

@@ -33,6 +33,7 @@ nav:
       - Contributing Guide: contributing.md
       - Contribution Types: contribution_types.md
       - Open In Godot (Build): build.md
+      - Create Action Scripts: create_action_scripts.md
 
 theme:
   name: readthedocs