From 9942fe6b3935acb0252c66f44910bcef8fabc61d Mon Sep 17 00:00:00 2001
From: Lerking <33354709+Lerking@users.noreply.github.com>
Date: Wed, 6 Mar 2024 07:53:11 +0100
Subject: [PATCH] Updated The birth of a python plugin architecture (markdown)

---
 The-birth-of-a-python-plugin-architecture.md | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/The-birth-of-a-python-plugin-architecture.md b/The-birth-of-a-python-plugin-architecture.md
index bd380b2..014172a 100644
--- a/The-birth-of-a-python-plugin-architecture.md
+++ b/The-birth-of-a-python-plugin-architecture.md
@@ -10,8 +10,23 @@ A. The plugin architecture design pattern (also known as microkernel) is a philo
 
 Q. What is required of a plugin system?
 
+A. These elements must be in place for a basic plugin system.
+  - A core system which handles registration/unregistering
+    - Some sort of configuration file with info about registered plugins. This could be any type of file for storing basic data i.e. json, xml, yaml etc.
+  - Plugins using the plugin class as its main component. This ensures interface stability.
+
+
 ## Plugin requirements
 * Plugin registration (installation)
 * Plugin activation (activate the plugin)
 * Plugin deactivation (deactivate the plugin)
-* Plugin un-registration (un-installation)
+* Plugin unregister (uninstall)
+
+### Plugin registration
+What should happen when a plugin registers?
+
+### Plugin activation
+
+### Plugin deactivation
+
+### Plugin un-registering
\ No newline at end of file