If you are shipping a WordPress plugin, the plugin directory submission is part code review, part readme quality check, and part public presentation. The plugin may technically work, but the surrounding assets still matter because the directory page is often the first place people decide whether the plugin looks trustworthy enough to install.
Questions people ask before WordPress.org submission
- What assets do I need for the WordPress plugin directory?
- Do WordPress plugins need banners and icons?
- What screenshot and banner sizes does WordPress.org use?
- How should I package the public page for a plugin launch?
Current WordPress.org asset sizes
The current WordPress plugin-assets handbook recommends:
- plugin banner: 772 × 250
- high-density plugin banner: 1544 × 500
- plugin icon: 128 × 128
- high-density plugin icon: 256 × 256
The handbook also notes that if you do not provide banner images, the normal screenshots are still displayed at the top of the plugin page. That means banners are helpful, not the only path forward.
What a strong plugin submission package should include
- plugin name
- clear description of what the plugin does
- icon
- screenshots
- documentation or setup help
- support path
- optional banner assets for a stronger directory presentation
How Vibe411 now helps with plugin launches
Vibe411 already stored the core plugin-launch pieces: product name, icon, screenshots, docs, support link, tags, and category structure. It now also stores dedicated WordPress.org banner assets:
- WordPress.org banner
- WordPress.org retina banner
Those are kept as submission-prep assets and are not forced into the public listing layout.
What the Vibe411 fields help you clarify
Product Name
Your plugin name should already sound like a real plugin title before it ever reaches the directory.
Tagline and Description
These fields help you refine the value proposition and workflow, which usually improves the readme and the public plugin description later too.
Icon
A plugin icon is one of the easiest ways to make the directory listing feel like a real product instead of a raw code drop.
Screenshots
Show the admin screens, settings, before-and-after result, and any front-end change the plugin creates. Good plugin screenshots reduce install hesitation.
Documentation and Support
Plugins often need setup instructions more than typical apps do. Vibe411’s docs support makes this easier because you can point to external docs on eligible plans or host docs through the docs suite when needed.
Plugin Banners
These help the plugin directory page look more polished, but they are not a substitute for good screenshots and documentation.
What Vibe411 does not replace in the WordPress.org flow
Vibe411 does not replace:
- the plugin ZIP or SVN workflow
- the plugin readme.txt format requirements
- WordPress.org code review
- WordPress.org support-forum or hosting rules
It helps with the public-facing prep and launch presentation around the submission, not the repository mechanics themselves.
Where plan levels matter
WordPress plugin launches often benefit from documentation, support pages, and FAQ links. That means:
- Basic is useful if you already have external docs and support URLs.
- Plus and Pro are better if you want more complete hosted docs support through Vibe411 itself.
Practical solo-builder workflow
- Build the Vibe411 listing as the public explanation layer for the plugin.
- Upload the icon and screenshot set.
- Add support and documentation links.
- Upload the banner and retina banner if you want the stronger directory presentation.
- Use the listing fields and this guide as your packaging checklist before you move into the WordPress.org submission flow.
- Then move into the WordPress.org submission and repository flow.
Why this helps your plugin get seen
Plugin discovery is competitive because many plugins sound similar. Creators who make the plugin understandable, documented, and visually credible before the directory review usually move faster and look more trustworthy once the page is live. That is the part Vibe411 can support best.