This plugin modifies a popular content management system to load its plugins from a symbolic link (symlink) rather than the standard directory. It is designed for developers and administrators who manage their plugin code in a separate repository or location, such as a shared development environment or a deployment using version control. By decoupling the plugin files from the core installation, it facilitates workflows where plugins are developed independently or need to be consistent across multiple site instances.

• Symlinked Plugin Directory: The core function allows the system's plugin loader to recognize and use a symlinked folder as the primary source for plugins, overriding the default behavior.
• Simple Installation: It is installed by cloning it into a subdirectory within the standard plugins folder, with a specific naming convention to ensure it loads first.
• Alphabetical Loading Control: The plugin's functionality depends on it being loaded before other plugins; this is managed by naming its folder so it appears first alphabetically in the plugin list.
• Version Control Integration: By keeping the actual plugin code in a separate, symlinked location, it integrates cleanly with Git or other version control systems, keeping deployment and development histories separate from the core site files.
• Manual Update Process: Updates are performed by pulling the latest changes from the Git repository directly within the plugin's installation directory, maintaining a straightforward update path for the tool itself.