📝 clarify docs

Author: vanyle

docs/user-manual.md

@@ -839,6 +839,19 @@ It can also mean that you forgot to put `runtime.js` and `runtime.wasm` in the s
 
 You put these files in a zip and upload it to [itch.io](https://itch.io) if you want.
 
+# 🧩 Extending Vectarine with Plugins
+
+Plugins are a way to add features to the vectarine editor and to your game. Plugins can add new interfaces in the editor, new luau functions, and do basically anything.
+Because of this, running requires that you trust the author.
+
+Plugins exist in the form of files with the `.vectaplugin` extension. Vectarine stores a list of trusted plugin that you can use in your games to a `plugin` folder that
+you can open using the "Open plugin folder" in the "Plugin manager". When you download a plugin, you should add it to this folder.
+
+Games have their own list of plugins in their `plugins` folder which should be next to the `game.vecta` file. For security reasons, 
+**the vectarine editor will only load plugins from a game if they are also in the `plugins` folder of the editor** and are thus trusted plugins!
+
+If you want to make your own plugins, check the [README](https://github.com/vanyle/vectarine/tree/main/vectarine-plugin-template) of the vectarine plugin template on Github.
+
 # 👥 Collaborating on a project
 
 Working on a game with other people is more fun!

vectarine-plugin-template/README.md

@@ -11,24 +11,25 @@ Run it using `uv run bundle.py`.
 
 You'll need to have [uv](https://github.com/astral-sh/uv) installed.
 
-## Using your plugin
+This will produce a `plugin.vectaplugin` file that you can copy to the `plugins` folder of the editor to use it.
 
-Vectarine comes bundled with a runtime that is precompiled for all the major platforms.
-For your plugins, you will need to manually compile them for the platforms you want to support.
+## Distributing your plugin
 
-If you don't have a Mac, you won't be able to support MacOS users for example.
+To share your plugin, simply share the `your_plugin_name.vectaplugin` file.
 
-## Distributing your plugin
+## Platform support
+
+Vectarine comes bundled with a runtime that is precompiled for all the major platforms.
+However, as plugins contain native code, you will need to manually compile them for the platforms you want to support.
+
+If you don't compile a Mac version of your plugin, games using it won't be able to run on Mac.
 
-Vectarine can load plugins in 2 ways:
+## Lua API
 
-- From a local file
-- From the plugin registry
+If your plugin extends the Lua, you should provide inside `plugin.luau` a list of the function you define, with documentation comments and proper types.
 
-Plugins can have 2 formats:
+## Plugin capabilities
 
-- Unpackage plugins are the main format for plugin developpers, it is just the path to the shared library with the plugin
-- Package plugins are the format for end users, a zip file with the shared libraries with the different platforms an documentation.
+As vectarine plugins are written in Rust, they can do pretty much anything, as long as the platform they are compiled for supports it.
 
-If your plugin extends the Lua, you should provide a `luau-api` folder to document the APIs you provide as well as a `README.md` file
-for a description of your plugin, an **examples** on how to use it.
+Moreover, plugins use the SDK as a dependency to be able to access and create Luau functions for users.

vectarine-plugin-template/plugin.luau

@@ -1,5 +1,8 @@
 local module = {}
 
+--- Returns the square of a number
+--- @param n number
+--- @return number
 function module.square(n: number): number
 	return n * n
 end