feat: add plugins

[raideno]

• Define what plugins will be able to extend.
  • Maybe add themes into the theme selector.
  • Add in new sections.
  • Add in new fields, with new controllers.
  • Etc.

Plugins can be stored in any GitHub repository inside of a plugins folder, inside of the plugin folder must be defined an index.ts or index.js with some specific structure to be used by the website.

Inside of the website, you can install plugins by specifying the repository you want to install from, you can add and save repository links so that you don't have to re-enter them each time, there will be a default one. Once the repository is loaded you can choose plugins to install from there, plugins are just tsx or jsx files, self contained files that have a very specific structure, there will be multiple types of them.

From the awesome website when you install a plugin, the plugin's file will be downloaded into the browser and committed into the GitHub repository inside a plugins folder and it'll be automatically loaded into the website's bundle at build time.

Plugins will have versions and can be updated, uninstalled, etc. Plugins won't be able to extend the schema, but they'll have a special file to store their attributes and options.

[raideno]

Beside a GitHub registry of plugins, we should also be able to install a plugin by specifying the link towards the plugin's file directly. The website will first look for a plugin file.

[raideno]

We won't be able to make plugins secure and hide the token for them, this is why it is important to only install trusted plugins. Plugins export a PluginDefinition which contains an id, name, description, author and an array of extensions, each extension is an object and have a type, there will be several type of extensions:

• card action. will be displayed on the card's context menu.
• action sidebar. will be displayed on the actions sidebar.
• card content. will be displayed inside the card's full screen.
• group action. will be displayed inside the groups's context menu.
• card sidebar. will be displayed inside the card's editing sidebar.
  Each extension will define some render element function that'll be called by the website, the function will receive the element, group or concerned entity as well as the context which contains the entire list, whether the editing is enabled or not and the file api which allows the plugin to write and read from its assigned file. This file is automatically loaded when the website is loaded and committed when changes are pushed.

[raideno]

The website will come with some default plugins to remove some unnecessary things from the website core. Other official plugins we could provide could be some excalidraw plugin, AI plugins, etc.

[raideno]

Some plugins are a bit heavy, we'll be providing a directory for each plugin rather than a single file to store things, this will be more ideal and more practical.

[raideno]

We're also going to try and make the plugins able to completely modify the website's layout and stuff. For example a plugin can inject a header into the website and replace the default one, inject a different search-bar, a different grid, etc.

Only one plugin that changes the ui and stuff will be injected, if multiples are available only one will be selected and only one will be loaded into the website's bundle.

This way even the website's default features will be built as plugins.