UniqAI/hexabot
1
0
Fork 0
mirror of https://github.com/hexastack/hexabot synced 2025-03-10 14:25:42 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

GITBOOK-124: fix broken links

Browse Source
This commit is contained in:
Chedli Ben Yaghlane 2024-12-22 23:05:28 +00:00 committed by gitbook-bot
parent 0b19a9445d
commit 51e7ae6182
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/developer-guide/integrations/build-your-first-plugin.md
View File

@ -355,7 +355,7 @@ The following represents what your custom plugin will look like based on the exa
## Publishing your plugin
After completing your plugin, be sure to connect with the Hexabot community on [Discord](https://discord.gg/rNb9t2MFkG) to showcase your plugin and work in the _show-n-tell_ channel. 
After completing your plugin, be sure to connect with the Hexabot community on Discord to showcase your plugin and work in the _show-n-tell_ channel. 
Consider publishing your plugin to a repository (e.g., NPM, GitHub) for others to use and continue to improve it.

4
docs/developer-guide/integrations/hexabot-plugin-development.md
View File

@ -33,5 +33,5 @@ Let’s break down each component:
1. `README.md`: Provides an overview, instructions, and other relevant information about your plugin. The documentation should clearly explain what the plugin does, its features, any prerequisites, installation instructions, configuration details, and usage examples.
2. `index.plugin.ts`: The heart of your plugin. This file contains the core logic that will govern the plugin's behaviour. This includes how the plugin interacts with Hexabot and any external services it may utilize.
3. `package.json`: Acts as the manifest for the plugin. It’s where you define the plugin's name, version, dependencies, and other essential metadata required for Hexabot to properly identify and handle the plugin. (More details in the[ package.json](https://docs.google.com/document/d/1PyNwF9DHOY8omTm1n8snPrxc9MDHd5vlz6KNM7GuSJ0/edit#package.json) section)
4. `settings.ts`: Defines the customizable settings for your plugin block. This will allow you to tweak its behaviour in the Visual editor. You'll be able to define UI elements such as Text Inputs, Checkboxes, etc. (More details in the[ settings.ts](https://docs.google.com/document/d/1PyNwF9DHOY8omTm1n8snPrxc9MDHd5vlz6KNM7GuSJ0/edit#settings.ts) section).
5. `i18n/`: The internationalization folder where you store translations for your plugin, allowing it to be localized for different languages. Each language gets a separate folder (e.g., en for English, fr for French) containing translation files (e.g., title.json for your plugin’s display name). (More details in the[ i18n](https://docs.google.com/document/d/1PyNwF9DHOY8omTm1n8snPrxc9MDHd5vlz6KNM7GuSJ0/edit#i18n) section)
4. `settings.ts`: Defines the customizable settings for your plugin block. This will allow you to tweak its behaviour in the Visual editor. You'll be able to define UI elements such as Text Inputs, Checkboxes, etc.
5. `i18n/`: The internationalization folder where you store translations for your plugin, allowing it to be localized for different languages. Each language gets a separate folder (e.g., `en` for English, `fr` for French) containing translation files (e.g., title.json for your plugin’s display name). (More details in the[ i18n](https://docs.google.com/document/d/1PyNwF9DHOY8omTm1n8snPrxc9MDHd5vlz6KNM7GuSJ0/edit#i18n) section)