Plugin architecture

[apexdodge]

A good plugin architecture can make building applications a more enjoyable experience, but it can be difficult to create and easy to get wrong. For example, the plugin system for Wordpress has been a source of maintenance issues. Similarly, .NET has its own challenges when it comes to implementing a plugin system.

In order to create a successful plugin system for the .NET application, Raytha, the development experience should be improved compared to simply modifying the existing application. This could be achieved through the implementation of an interface that allows for the integration of plugins into different parts of the Raytha application, whether through a pipeline or event-based approach. It is important to consider the specific requirements and goals for the plugin system in order to effectively design and implement it.

interface IRaythaPlugin 
{
    IPluginResult BeforePageLoad(HttpContext context);
    ...
    ...
   
}

Then our system automatically detects and registers plugins on startup, and before the model is rendered by Liquid, we run through the all registered plugins and call the method(s).

We can add another attribute to Wrapper_RenderModel which could be a Dictionary<string, IPluginResponse> and store all the plugin responses there, and that variable would be available for the liquid templates.

Just spit balling here, but I think that's how something like that might work.

I see the benefit from a Tutorial and Guides perspective, that there is a "standard" way to plugin to raytha.

Any other ideas around this?