Remade understanding-plugin.md

Updated the understanding of plugins section with new content and improved formatting.

Author: Neootic3

docs/getting-started/understanding-plugin.md

@@ -1,17 +1,36 @@
 # Understanding Plugins
 
 :::warning
-**Note:** Work is in progress 🚧
+**Note:** Work in progress 🚧
 :::
 
-We are currently working on this section to provide you with detailed and comprehensive information about how Acode plugins work. Please check back soon for updates!
+## What is a Plugin?
 
-## Contribute to the Documentation
+A Plugin is basically an **Add-on** you add them to the base of a platform to make it much more personalized and Fitted for specific cases.
 
-We welcome contributions from the community! If you would like to help improve this documentation, please visit our [GitHub repository](https://github.com/bajrangCoder/acode-plugin-docs) and follow the contribution guidelines.
+---
 
-:::tip
-You can suggest changes, add new content, or improve existing sections. Every bit of help is appreciated! 🤗
-:::
+## How Do Acode Plugins Work?
+
+Acode Plugins put themselves on top of foundation by adding new features such as: **Ui Elements** , **functions**.
+
+think of Plugins as a supervisor that Make the default editor (worker) follow custom-made rules.
+
+
+---
+
+## Why do Plugins Exist?
+
+Plugins exist as a way to personalize and customize the user experience, a user can make a plugin that fits their workflow and make coding faster, easier and more accessible.
+
+---
+
+## What are the types of Plugins?
+
+There are many types of plugins like:
+
+• **Productivity based:** Plugins that help you do a specific task quicker.
+
+• **Feature based:** Plugins that add niche features to a specific type of development.
 
-For more information, see official [Guide](https://acode.app/plugin-docs).
+• **Malicious Plugins:** that are intended to make your experience awful.