From 10540dc153bd036b7fc0ad8ece7dbfdca7d5f5dd Mon Sep 17 00:00:00 2001
From: Lerking <33354709+Lerking@users.noreply.github.com>
Date: Fri, 8 Mar 2024 10:58:22 +0100
Subject: [PATCH] Updated The birth of a python plugin architecture (markdown)

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

diff --git a/The-birth-of-a-python-plugin-architecture.md b/The-birth-of-a-python-plugin-architecture.md
index 325d6c6..5c708ec 100644
--- a/The-birth-of-a-python-plugin-architecture.md
+++ b/The-birth-of-a-python-plugin-architecture.md
@@ -21,11 +21,14 @@ My personal belief is that registration and activation should be kept separate.
    - Activation should not be allowed unless the plugin is registered.
 
 ## Plugin requirements
+* Plugin manager to keep track of plugins and their statuses.
 * Plugin registration (installation)
 * Plugin activation (activate the plugin)
 * Plugin deactivation (deactivate the plugin)
 * Plugin unregister (uninstall)
 
+### Plugin manager
+
 ### Plugin registration
 What should happen when a plugin registers?