rewrite always use good folder names section#64
Open
rtpHarry wants to merge 2 commits intoWordPress:mainfrom
Open
rewrite always use good folder names section#64rtpHarry wants to merge 2 commits intoWordPress:mainfrom
rtpHarry wants to merge 2 commits intoWordPress:mainfrom
Conversation
I was confused by what it was saying until reading it a few times. I rewrote it to state each thing more clearly and try to set it up so it said why you do something before saying what should be done. I also softened the wording so as to not imply that you do legally binding due diligence.
frantorres
requested changes
Jan 3, 2026
| Not only would we not accept it for using the prohibited term ‘plugin’, the plugin team would validate that the plugin owner **legally** represents FaceRange. | ||
| If the folder name of your plugin cannot exist on WordPress.org, it cannot collide with a plugin hosted in the directory. | ||
|
|
||
| The WordPress.org plugin directory does not allow plugin slugs containing the term `plugin`, so any folder name ending in `-plugin` cannot be registered there. |
Contributor
There was a problem hiding this comment.
There are specific cases in which plugin could be allowed, so I'd rephrase this as
In most cases, the WordPress.org plugin directory does not allow plugin slugs containing the term plugin
|
|
||
| The WordPress.org plugin directory does not allow plugin slugs containing the term `plugin`, so any folder name ending in `-plugin` cannot be registered there. | ||
|
|
||
| As part of the directory submission process, it is validated that the plugin owner has the right to represent the company name used. |
Contributor
There was a problem hiding this comment.
I'd join this phrase with the previous one, the documentation tends to be written down using paragraphs composed of several sentences instead of small phrases.
|
|
||
| If you’re making a plugin for your company, you can use a folder name like `companyname-function-plugin`. For example, if you work for FaceRange and you’re making a status plugin, you could name the folder `facerange-status-plugin`. | ||
|
|
||
| This approach affects only the plugin’s folder name and does not change the plugin name shown in the admin UI. |
Contributor
There was a problem hiding this comment.
I'm not sure if this clarification is needed. At this point a developer shall know that the name is taken from the plugin headers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was confused by what it was saying until reading it a few times. I rewrote it to state each thing more clearly and try to set it up so it said why you do something before saying what should be done.
I also softened the wording so as to not imply that you do legally binding due diligence.