feat: update for new plugify

Author: qubka

content/1.introduction/4.architecture.md

@@ -4,6 +4,12 @@ description: How it works under the hood (high-level explanation).
 icon: lucide:layers
 ---
 
+# Version 2.#.#
+
+## TODO
+
+# Version 1.#.#
+
 The core architecture of Plugify is designed to facilitate seamless interaction between language modules, each implemented as a separate C++ library. As a result, the core does not communicate directly with plugins; instead, all interactions occur through these language modules. Likewise, plugins do not directly interact with the core but rely on language modules for communication. This modular design even extends to the C++ language itself, requiring a dedicated language module for handling C++-based plugins. The primary objective of the Plugify project is to establish a universal environment that enables fast and efficient inter-language interaction.
 
 ## Core Components of Plugify

content/1.introduction/5.faq.md

@@ -92,7 +92,7 @@ To create a new language module:
 
 1. Implement the `ILanguageModule` interface provided by Plugify.
 2. Compile the module with the same C++ version and compiler as the Plugify core.
-3. Place the compiled module in the `res/modules` folder.
+3. Place the compiled module in the `res/extensions` folder.
 4. Update the `plugify.pconfig` file to include the new module.
 
 Refer to the [Language Module Development Guide](/developer-guide) for detailed instructions.
@@ -125,10 +125,10 @@ Manifest files are JSON configuration files used by Plugify to define metadata a
      ```json
      {
          "$schema": "https://raw.githubusercontent.com/untrustedmodders/plugify/refs/heads/main/schemas/plugin.schema.json",
-         "friendlyName": "my-plugin",
+         "name": "my_plugin",
          "version": "1.0.0",
          "dependencies": [],
-         "entryPoint": "bin/plugin_name"
+         "entry": "bin/plugin_name"
      }
      ```
 
@@ -139,7 +139,7 @@ Manifest files are JSON configuration files used by Plugify to define metadata a
      ```json
      {
          "$schema": "https://raw.githubusercontent.com/untrustedmodders/plugify/refs/heads/main/schemas/module.schema.json",
-         "friendlyName": "cpp-module",
+         "name": "cpp_module",
          "version": "1.0.0",
          "language": "cpp"
      }

content/1.introduction/6.requirements.md

@@ -43,8 +43,8 @@ Plugify requires a C++20-compatible compiler. The following compilers are suppor
 Plugify has the following dependencies:
 
 1. **Core Dependencies**:
-    - [CURL](https://curl.se/): For remote package management (optional, can be disabled).
-    - [miniz](https://github.com/richgel999/miniz): For handling ZIP archives.
+    - [asmjit](https://github.com/asmjit/asmjit): For runtime code generation.
+    - [libsolv](https://github.com/openSUSE/libsolv): For effective dependency resolution.
     - [glaze](https://github.com/stephenberry/glaze): For JSON parsing and validation.
 
 2. **Language Module Dependencies**:

content/2.essentials/1.installation.md

@@ -66,10 +66,9 @@ The `plug` app allows you to test plugins and language modules locally. Follow t
    ```
 2. Inside the `res` folder, create two subfolders:
    ```
-   mkdir ../res/plugins
-   mkdir ../res/modules
+   mkdir ../res/extensions
    ```
-3. Place your plugins in the `plugins` folder and language modules in the `modules` folder.
+3. Place your plugins in the `extensions` folder and language modules in the `extensions` folder.
 
 ### Configure `plugify.pconfig`
 The `plug` app requires a configuration file named `plugify.pconfig` in the working directory. This file specifies the path to the `res` folder and other settings.

content/2.essentials/3.building.md

@@ -336,12 +336,11 @@ mkdir ../res
 ```
 2. Inside the `res` folder, create two subfolders:
 ```
-mkdir ../res/plugins
-mkdir ../res/modules
+mkdir ../res/extensions
 ```
 3. Copy the built plugins and language modules to the `res` folder:
-- Place `cross_call_worker` and `cross_call_master` in `res/plugins/`.
-- Place the language modules (e.g., `cpp-module`, `python-module`) in `res/modules/`.
+- Place `cross_call_worker` and `cross_call_master` in `res/extensions/`.
+- Place the language modules (e.g., `cpp-module`, `python-module`) in `res/extensions/`.
 
 #### Run the Tests
 1. Navigate to the `build` directory and run the `plug` app:

content/2.essentials/5.configuration.md

@@ -35,41 +35,33 @@ The `.pplugin` file defines the configuration for a specific plugin. Below is an
 ::code-group
 ```json [*.pplugin]
 {
-  "fileVersion": 1,
   "version": "1.0.0",
-  "friendlyName": "Sample Plugin",
+  "name": "sample_plugin",
   "description": "This is a sample plugin.",
-  "createdBy": "untrustedmodders",
-  "createdByURL": "https://github.com/untrustedmodders/",
-  "docsURL": "https://github.com/untrustedmodders/sample_plugin",
-  "downloadURL": "https://github.com/untrustedmodders/sample_plugin/releases/download/v1.0/sample_plugin.zip",
-  "updateURL": "https://raw.githubusercontent.com/untrustedmodders/sample_plugin/main/sample_plugin.json",
-  "entryPoint": "bin/sample_plugin",
-  "supportedPlatforms": [],
-  "languageModule": {
-    "name": "cpp"
-  },
+  "author": "untrustedmodders",
+  "website": "https://github.com/untrustedmodders/",
+  "license": "MIT",
+  "entry": "bin/sample_plugin",
+  "platforms": [],
+  "language": "cpp",
   "dependencies": [],
-  "exportedMethods": []
+  "methods": []
 }
 ```
 ::
 
 #### Configuration Options:
-- **`fileVersion`**: The version number of the configuration file format.
 - **`version`**: The semantic version of the plugin.
-- **`friendlyName`**: A user-friendly name for the plugin.
+- **`name`**: An alias name for the plugin.
 - **`description`**: A brief description or overview of the plugin.
-- **`createdBy`**: The creator or author of the plugin.
-- **`createdByURL`**: The URL linking to the creator's profile or information.
-- **`docsURL`**: The URL linking to the documentation for the plugin.
-- **`downloadURL`**: The URL for downloading the plugin, typically a release package or ZIP file.
-- **`updateURL`**: The URL for checking and fetching updates for the plugin.
-- **`entryPoint`**: The entry point or main executable for the plugin, specified as `bin/sample_plugin`. (Depends on the language module.)
-- **`supportedPlatforms`**: An array listing the platforms supported by the plugin. (Currently empty in this example.)
-- **`languageModule`**: Information about the programming language module used. In this case, it's specified as `"cpp"` (C++).
+- **`author`**: The creator or author of the plugin.
+- **`website`**: The URL linking to the creator's profile or information.
+- **`license`**: The license for the plugin.
+- **`entry`**: The entry point or main executable for the plugin, specified as `bin/sample_plugin`. (Depends on the language module.)
+- **`platforms`**: An array listing the platforms supported by the plugin. (Currently empty in this example.)
+- **`language`**: Information about the programming language module used. In this case, it's specified as `"cpp"` (C++).
 - **`dependencies`**: A list of plugin references specifying the dependencies required for the plugin. This field is crucial for topological sorting to load plugins in the correct order of initialization.
-- **`exportedMethods`**: An array describing functions/methods exposed by the plugin.
+- **`methods`**: An array describing functions/methods exposed by the plugin.
 
 ### Module Manifest
 
@@ -78,35 +70,27 @@ The `.pmodule` file defines the configuration for a language module. Below is an
 ::code-group
 ```json [*.pmodule]
 {
-    "fileVersion": 1,
     "version": "1.0.0",
-    "friendlyName": "C++ language module",
+    "name": "cpp_module",
     "language": "cpp",
     "description": "Adds support for C++ plugins",
-    "createdBy": "untrustedmodders",
-    "createdByURL": "https://github.com/untrustedmodders/",
-    "docsURL": "https://github.com/untrustedmodders/cpp-lang-module/README.md",
-    "downloadURL": "https://github.com/untrustedmodders/cpp-lang-module/releases/download/v1.0/cpp-lang-module.zip",
-    "updateURL": "https://raw.githubusercontent.com/untrustedmodders/cpp-lang-module/main/cpp-lang-module.json",
-    "supportedPlatforms": [],
-    "forceLoad": false
+    "author": "untrustedmodders",
+    "website": "https://github.com/untrustedmodders/",
+    "license": "MIT",
+    "platforms": []
 }
 ```
 ::
 
 #### Configuration Options:
-- **`fileVersion`**: The version number of the configuration file format.
 - **`version`**: The semantic version of the language module.
-- **`friendlyName`**: A user-friendly name for the language module.
+- **`name`**: An alias name for the language module.
 - **`language`**: The programming language supported by this module (e.g., `"cpp"` for C++).
 - **`description`**: A brief description or overview of the language module.
-- **`createdBy`**: The creator or author of the language module.
-- **`createdByURL`**: The URL linking to the creator's profile or information.
-- **`docsURL`**: The URL linking to the documentation for the language module.
-- **`downloadURL`**: The URL for downloading the language module, typically a release package or ZIP file.
-- **`updateURL`**: The URL for checking and fetching updates for the language module.
-- **`supportedPlatforms`**: An array listing the platforms supported by the language module.
-- **`forceLoad`**: A boolean indicating whether the language module should be forcibly loaded by the core.
+- **`author`**: The creator or author of the language module.
+- **`website`**: The URL linking to the creator's profile or information.
+- **`license`**: The license for the language module.
+- **`platforms`**: An array listing the platforms supported by the language module.
 
 ### Notes:
 - Ensure all configuration files are valid JSON and adhere to the schema provided by Plugify.

content/2.essentials/6.commands.md

@@ -178,7 +178,7 @@ plg show _package_name_
 Add a new remote repository for package installation.
 
 ```bash
-plg repo https://website.com/_package_file_.json
+mamba install -n your_env_name -c https://website.com/conda_channel/ package_name
 ```
 
 **Note**: Only add repositories from trusted sources to avoid security risks.

content/4.languages/1.python/1.installation.md

@@ -10,16 +10,16 @@ The **Python Language Module** can be installed in two ways: manually downloadin
 
 ::steps
 ### **Download the Release**
-1. Go to the [Python Language Module repository](https://github.com/untrustedmodders/plugify-module-python3.12).
+1. Go to the [Python Language Module repository](https://github.com/untrustedmodders/plugify-module-python3).
 2. Navigate to the **Releases** section.
-3. Download the latest release package (e.g., `plugify-module-python3.12.zip`).
+3. Download the latest release package (e.g., `plugify-module-python3.zip`).
 
 ### **Extract the Package**
 1. Extract the downloaded package to a temporary directory.
 
 ### **Place the Module in the Modules Folder**
-1. Locate the `modules` folder in your Plugify installation directory.
-2. Copy the extracted module files into the `modules` folder.
+1. Locate the `extensions` folder in your Plugify installation directory.
+2. Copy the extracted module files into the `extensions` folder.
 
 ### **Verify Installation**
 1. Start Plugify.
@@ -29,30 +29,14 @@ The **Python Language Module** can be installed in two ways: manually downloadin
 ## **Method 2: Installation via Package Manager**
 
 ::steps
-### **Add the Repository (if needed)**
-If the Python Language Module is not found in the default package repository, you need to add the repository manually.
-
-#### **Option A: Add Repository via Command**
-1. Run the following command in your terminal:
-   ```bash
-   plg repo https://untrustedmodders.github.io/plugify-module-python3.12/plugify-module-python3.12.json
-   ```
-
-#### **Option B: Add Repository via `plugify.pconfig`**
-1. Open the `plugify.pconfig` file in your Plugify installation directory.
-2. Add the following line under the `repositories` section:
-   ```json
-   {
-     "repositories": [
-       "https://untrustedmodders.github.io/plugify-module-python3.12/plugify-module-python3.12.json"
-     ]
-   }
-   ```
+### **Configure Mamba**
+Before proceeding, make sure you have the [Mamba package manager](https://mamba.readthedocs.io/en/latest/user_guide/mamba.html#mamba-user-guide) installed and understand the basics of creating and managing environments.  
+If you are new to Mamba, please read the **Quickstart Guide** in the official documentation.
 
 ### **Install the Module**
-1. Run the following command in your terminal:
+1. Run the following command in your terminal (replace `your_env_name` with the name of your environment):
    ```bash
-   plg install plugify-module-python3.12
+   mamba install -n your_env_name -c https://untrustedmodders.github.io/plugify-module-python3/ plugify-module-python3
    ```
 
 ### **Verify Installation**
@@ -67,7 +51,7 @@ After installation, the Python Language Module should have the following folder
 ::file-tree
 ---
 tree:
-- res/modules:
+- res/extensions:
     - plugify-module-python:
         - src:
             - plugify-module-python.py
@@ -76,15 +60,14 @@ tree:
 ::
 
 ### **Explanation**
-- **`res/modules/plugify-module-python3.12`**: The root folder for the Python Language Module.
+- **`res/extensions/plugify-module-python3`**: The root folder for the Python Language Module.
 - **`src`**: Contains Python source code files (`.py`).
-- **`plugify-module-python3.12.pplugin`**: The module manifest file that describes the module and its language.
+- **`plugify-module-python3.pplugin`**: The module manifest file that describes the module and its language.
 
 ## **Troubleshooting**
 
 ### **Module Not Found**
 - Ensure the repository URL is correct and accessible.
-- Verify that the repository has been added to `plugify.pconfig` or via the `plg repo <url>` command.
 
 ### **Installation Fails**
 - Check your internet connection.

content/4.languages/1.python/2.first-plugin.md

@@ -36,7 +36,7 @@ To ensure seamless integration with the Plugify framework, your plugin must foll
 ::file-tree
 ---
 tree:
-- res/plugins:
+- res/extensions:
     - python_example_plugin:
         - python_example_plugin.py
         - ^python_example_plugin.pplugin^
@@ -48,7 +48,7 @@ tree:
 
 ### Breakdown of the Structure
 
-* `res/plugins/` – The main directory where all plugins are stored.
+* `res/extensions/` – The main directory where all plugins are stored.
 * `python_example_plugin/` – Each plugin has its own dedicated folder. The folder name must match the `.pplugin` file name.
 * `python_example_plugin.py` – The Python script containing the plugin code.
 * `python_example_plugin.pplugin` – The configuration file that defines metadata about the plugin.
@@ -71,32 +71,27 @@ Each plugin in the **Plugify** framework requires a **manifest file** with the `
 ```json [python_example_plugin.pplugin]
 {
   "$schema": "https://raw.githubusercontent.com/untrustedmodders/plugify/refs/heads/main/schemas/plugin.schema.json",
-  "fileVersion": 1,
   "version": "0.1.0",
-  "friendlyName": "PythonExamplePlugin",
+  "name": "PythonExamplePlugin",
   "description": "An example of a Python plugin. This can be used as a starting point when creating your own plugin.",
-  "createdBy": "untrustedmodders",
-  "createdByURL": "https://github.com/untrustedmodders/",
-  "docsURL": "https://github.com/orgs/untrustedmodders/README.md",
-  "downloadURL": "https://github.com/orgs/untrustedmodders/example-repo.zip",
-  "updateURL": "https://github.com/untrustedmodders/plugify/issues",
-  "entryPoint": "python_example_plugin.ExamplePlugin",
-  "supportedPlatforms": [],
-  "languageModule": {
-    "name": "python3"
-  },
+  "author": "untrustedmodders",
+  "website": "https://github.com/untrustedmodders/",
+  "license": "MIT",
+  "entry": "python_example_plugin.ExamplePlugin",
+  "platforms": [],
+  "language": "python3",
   "dependencies": [],
-  "exportedMethods": []
+  "methods": []
 }
 ```
 ::
 
 ### Key Fields Explained
 
-* `entryPoint`: Specifies the **module path** and **class name** of the plugin. For example, if your plugin is in `python_example_plugin.py` and the class is `ExamplePlugin`, the entry point should be `python_example_plugin.ExamplePlugin`.
-* `languageModule`: Should be set to **python3** for Python plugins.
+* `entry`: Specifies the **module path** and **class name** of the plugin. For example, if your plugin is in `python_example_plugin.py` and the class is `ExamplePlugin`, the entry point should be `python_example_plugin.ExamplePlugin`.
+* `language`: Should be set to **python3** for Python plugins.
 * `dependencies`: Lists other **required plugins**, ensuring correct load order.
-* `exportedMethods`: **Functions** exposed by the plugin for external interaction.
+* `methods`: **Functions** exposed by the plugin for external interaction.
 
 ### Why is the Manifest File Important?
 

content/4.languages/1.python/3.export-functions.md

@@ -81,14 +81,14 @@ def add_numbers_exported(a: int, b: int) -> int:
 ::
 
 ### **Plugin Manifest**
-To export the function, describe it in the plugin manifest under the `exportedMethods` section:
+To export the function, describe it in the plugin manifest under the `methods` section:
 
 ::code-group
 ```json [plugin_name.pplugin]
 {
   "name": "ExamplePythonPlugin",
   "version": "1.0.0",
-  "exportedMethods": [
+  "methods": [
     {
       "name": "add_numbers",
       "funcName": "add_numbers_exported",
@@ -136,7 +136,7 @@ def process_data_exported(data: list[float], prefix: str) -> list[str]:
 {
   "name": "ExamplePythonPlugin",
   "version": "1.0.0",
-  "exportedMethods": [
+  "methods": [
     {
       "name": "process_data",
       "funcName": "process_data_exported",
@@ -185,7 +185,7 @@ def execute_with_callback_exported(value: int, input_str: str, callback: callabl
 {
   "name": "ExamplePythonPlugin",
   "version": "1.0.0",
-  "exportedMethods": [
+  "methods": [
     {
       "name": "execute_with_callback",
       "funcName": "execute_with_callback_exported",
@@ -234,7 +234,7 @@ def execute_with_callback_exported(value: int, input_str: str, callback: callabl
 1. **Define Functions Clearly**: Ensure your functions are well-documented and easy to understand.
 2. **Follow Type Conventions**: Adhere to Plugify's type conventions for parameters and return values.
 3. **Test Thoroughly**: Test your exported functions to ensure they work as expected when called by other plugins.
-4. **Update the Manifest**: Always describe exported functions in the plugin manifest under the `exportedMethods` section.
+4. **Update the Manifest**: Always describe exported functions in the plugin manifest under the `methods` section.
 
 ## **Conclusion**