Zef Hemel
2ac30edb2f
- Enhanced the `Config.md` documentation to clarify built-in configuration options and the use of the `config.set` API. - Removed outdated `Page Template.md` and `Slash Template.md` files to streamline documentation and avoid confusion. - Updated references in various documentation files to reflect the removal of deprecated templates and ensure consistency across the site.
20 lines
1.3 KiB
Markdown
20 lines
1.3 KiB
Markdown
SilverBullet at its core is bare bones in terms of functionality, most of its power it gains from **plugs** and [[Space Lua]].
|
||
|
||
Plugs are an extension mechanism that runs “plug” code in the browser using [web workers](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers).
|
||
|
||
Plugs can hook into SB in various ways:
|
||
* Extend the Markdown parser and its syntax
|
||
* Define new commands and keybindings
|
||
* Respond to various events triggered either on the server or client-side
|
||
* Run recurring and background tasks.
|
||
* Define their own extension mechanisms through custom events
|
||
|
||
Each plug runs in its own _sandboxed environment_ and communicates with SB via _syscalls_ that expose a vast range of functionality. Plugs can be loaded, unloaded, and updated without having to restart SilverBullet itself.
|
||
|
||
Plugs are distributed as self-contained JavaScript bundles (ending with `.plug.js`). SilverBullet will load all core plugs bundled with SB itself (listed below), as well as any additional plugs stored in the `_plug` folder in your [[Spaces|space]].
|
||
|
||
|
||
# Third-party plugs
|
||
The [SilverBullet ‘Plugs’ category has a list of third-party plugs you can try](https://community.silverbullet.md/c/plugs/14).
|
||
|
||
Want to develop your own plugs? Have a look at [[Plugs/Development]]. |