Change the Name of plugin from AspireUpdate to Aspirepress #144
Replies: 5 comments 2 replies
-
|
#140 There is this happening, but we should all move from that discussion to a broader one. We have already renamed the plugin once, lets finalize and make sure we don't end up renaming it again after this one as it affects translations at this point. |
Beta Was this translation helpful? Give feedback.
-
|
I've shared this to #branding channel. |
Beta Was this translation helpful? Give feedback.
-
|
Just to let everyone know GlotPress changes slugs to all lowercase. Consequently language files will be in the format |
Beta Was this translation helpful? Give feedback.
-
|
Even the Plugin Check plugin looks to the name of the plugin folder as the slug. Another reason to change the repo to lowercase. |
Beta Was this translation helpful? Give feedback.
-
|
this is a dupe of #140 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The name "aspireupdate" for the plugin could be a bit misleading to the users or devs who will be installing it.
The aim of the plugin is to be a distribution channel to install and manage the wp assets and not just to update the plugins. Aspireupdate may mislead devs to think it is kind of auto update feature.
Also this is the only plugin/endpoint that most of the devs/users will interact. So the plugin name is a big Marketing/branding thing.
Beta Was this translation helpful? Give feedback.
All reactions