ЁЯМР US-Proxy
class="wp-singular page-template-default page page-id-8 page-parent wp-embed-responsive wp-theme-wporg-parent-2021 wp-child-theme-pubwporg-plugins-2024 no-js">

Developer information

You’ve got a cool new plugin and are hoping to give it some exposure. You’re in the right place. Just ask us to host it for you. You’ll be able to:

  • рдХрд┐рддрдиреЗ рд▓реЛрдЧреЛрдВ рдиреЗ рдбрд╛рдЙрдирд▓реЛрдб рдХрд┐рдпрд╛ рд╣реИ рдЗрд╕рдХрд╛ рдЖрд▓реЗрдЦ рд░рдЦреЗрдВред
  • рд▓реЛрдЧ рдЕрдкрдиреЗ рдкреНрд▓рдЧрдЗрди рдХреЗ рдмрд╛рд░реЗ рдореЗрдВ рдЯрд┐рдкреНрдкрдгреА рдЫреЛрдбрд╝ рджреЗрдВред
  • Get your plugin rated against all the other cool WordPress plugins.
  • Give your plugin lots of exposure in this centralized repository.

рд╡рд╣рд╛рдБ рдХреБрдЫ рдкреНрд░рддрд┐рдмрдВрдз рд╣реИрдВ

  • Your plugin must be compatible with the GNU General Public License v2, or any later version. The plugin should either include its human-readable source code or provide a clear, accessible link to it. We strongly recommend using the same license as WordPress тАФ “GPLv2 or later.”
  • The plugin must not impose artificial restrictions on its built-in functionality. This includes license gates, paywalls, time-limited trials, usage quotas, or any other mechanism that limits features included in the plugin code and/or that the plugin code can do.
  • The plugin must not do anything illegal or be morally offensive (that’s subjective, we know).
  • You have to actually use the Subversion repository we give you in order for your plugin to show up on this site. The WordPress Plugin Directory is a hosting site, not a listing site.
  • The plugin must not embed external links on the public site (like a “powered by” link) without explicitly asking the user’s permission.
  • Your plugin must abide by our list of┬аdetailed guidelines, which include not being a spammer and not abusing the systems.

рд╕рдмрдорд┐рдЯ (рджрд░реНрдЬ) рдХрд░рдирд╛ рдЖрд╕рд╛рди рд╣реИ

  1. рд╕рд╛рдЗрди рдЕрдк рдХрд░реЗрдВWordPress.org рдкрд░ рдЕрдкрдиреЗ рдЕрдХрд╛рдЙрдВрдЯ рдХреЗ рд▓рд┐рдПред
  2. рд╕рдореАрдХреНрд╖рд╛ рдХреЗ рд▓рд┐рдП рдЕрдкрдирд╛ рдкреНрд▓рдЧрдЗрди рдЬрдорд╛ рдХрд░реЗрдВред
  3. After your plugin is manually reviewed, it will either be approved or you will be emailed and asked to provide more information and/or make corrections.
  4. Once approved, you’ll be given┬аaccess to a Subversion Repository where you’ll store your plugin.
  5. Shortly after┬аyou upload┬аyour plugin (and a readme file!) to┬аthat repository, it will be automatically displayed┬аin the plugins┬аbrowser.
  6. рдЕрдзрд┐рдХ рдЬрд╛рдирдХрд╛рд░реА рдХреЗ рд▓рд┐рдПрд╕рд╛рдорд╛рдиреНрдп рдкреНрд░рд╢реНрди рджреЗрдЦреЗрдВред

рд░реАрдбрдореА рдлрд╛рдЗрд▓реНрд╕

To make your entry in the plugin browser most useful, each plugin should have a readme file named readme.txt that adheres to the WordPress plugin readme file standard. You can put your readme file through the readme validator to check it.