Update docs to: Add more pages to docs

Author: github-actions[bot]

docs/build.md

@@ -8,9 +8,7 @@
 
 ## Get Engine
 
-Text Forge built on Godot (v4.4.1.stable.official [49a5bc7b6]), you can get this version from this page:
-
-https://godotengine.org/download/archive/4.4.1-stable
+Text Forge built on Godot (v4.4.1.stable.official [49a5bc7b6]), you can get this version from [this page](https://godotengine.org/download/archive/4.4.1-stable).
 
 ## Get Source
 
@@ -26,4 +24,4 @@ Now you can use Godot to import project and edit it, or press `F5` to run projec
 
 !!! Important
 
-    If your clone is for conribution, Alway create a new branch for new PRs.
+    If your clone is for conribution, Always create a new branch for new PRs.

docs/data_driven_ui.md

@@ -0,0 +1,30 @@
+# Explanation about Text Forge "Data Driven UI"
+
+Text Forge uses a data driven system for important parts UI, including menu options and texts. This architecture make
+a dynamic UI and clean translation system.
+
+## Menus
+
+All data related to menus stored in `data/main_ui.ini`, this file have a section for menus and a key for each menu (or 
+submenu). Each item is an array of dictionaries and each dictionary has the following structure:
+
+- `"code"` - a unique integer for connect this option to its action script, its value can be any non-negative int bug must
+  be unique.
+- `"text"` - english text of option, it will be used for add name to action scripts and call them based on names.
+- `"key"` - linked translation key in translation file, menu loader will use it to set item text.
+- `"type"` - an integer related to option type, this key can have these values:
+  - `-1` - Separator
+  - `0` - Regular (this is default value, so items with `0` type haven't `"type"` key)
+  - `1` - Submenu
+  - `2` - Checkbox
+  - `3` - Radio Checkbox
+
+Each key must have `_menu` or `_submenu` suffix, items with `_menu` suffix will load in main menu and items with `_submenu`
+suffix will load as submenus based on texts, for example `Convert Case` submenu in `Edit` menu will load from `convert_case_submenu`
+key (snake case of submenu text with suffix).
+
+## Panels
+
+To handle panels, we have `data/panels/` folder. Here, each panel have a folder with icon, configuration file, and scene.
+In config file, we have place of panel (`R`, `L`, or `B`). Panel manager will load panels from here based on configuration
+file and stored files.

docs/object_oriented_design.md

@@ -0,0 +1,18 @@
+# Object Oriented Design
+
+This page explains meaning and examples of OOP in Text Forge architecture.
+
+## OOP in Text Forge, what and why?
+
+We have a lot of concepts from XP (extreme programming) in Text Forge architecture to have very clean codebase,
+and OOP is a tool for make them real; So we have an object-oriented like core for Text Forge (based on Godot 
+limitations), it means everything in Text Forge are objects.
+
+Also, we have a modular design to make Text Forge easy and sustainable expansion, OOP and its principles allow us to 
+develop modules stable and powerful. (though the Godot structure creates restrictions)
+
+## How we use OOP?
+
+We use the Godot nodes system and object sampling to dynamically load the editor components, this can affect speed but 
+maintain the editor's expansion. All in all, any module added to the editor (and its default modules) is a set of 
+objects that are connected by the Godot scene tree and can communicate with other modules.

mkdocs.yml

@@ -24,9 +24,11 @@ nav:
   - Introduction:
       - Introduction: introduction.md
       - Setup: setup.md
-  - Structure:
-    - Modes: modes.md
-    - Action Scripts: action_scripts.md
+  - Architecture:
+      - Data Driven UI: data_driven_ui.md
+      - Object Oriented Design: object_oriented_design.md
+      - Modes: modes.md
+      - Action Scripts: action_scripts.md
   - Developer Guides:
       - Contributing Guide: contributing.md
       - Contribution Types: contribution_types.md