Why the Current Structure is the Correct Method
The current structure Plugin_id/PluginName/assets_here follows standard conventions for plugin and project archives. Here's why you should keep it this way:
Reasons to Keep the Parent Folder
-
Clear Identification: The outer Plugin_id folder immediately identifies which plugin was downloaded, especially when downloading multiple plugins.
-
Prevents Conflicts: Without this parent folder, extracting multiple plugins to the same directory could overwrite files or mix contents from different plugins.
-
Industry Standards: Most archive managers (GitHub, GitLab, npm, etc.) automatically create a root folder with the project name. This is a universally accepted practice across software development.
-
Security: This structure prevents accidental extraction of files directly to the root directory, which could cause security issues or system disorganization.
-
Professional Distribution: All professional software packages follow this pattern - it shows proper packaging practices.
The Standard Workflow
The expected user workflow is:
- Download the ZIP file
- Extract it once
- Navigate into the folder structure
- Access the plugin files
This is how software distribution works across the industry.
If You Still Want to Change It
If you absolutely prefer PluginName/assets_here directly, the proper solution is to adjust your extraction process on your end, not modify the archive structure. You could:
- Extract and manually reorganize
- Use a script to restructure after download
- Extract only the inner contents
However, I strongly recommend keeping the current structure as it follows best practices for software distribution and will be familiar to all users.
