How Should a WordPress Plugin Developer Show WordPress.org, GitHub, and Private Client Work?

A WordPress plugin developer should create one portfolio entry per distinct plugin or tool, link public work to its strongest maintained source, and describe private client builds only at the level the client permits.

A WordPress.org profile shows directory releases, GitHub exposes selected code, and a commercial site handles sales. Private integrations may have no public surface at all. The portfolio should explain ownership, role, maintenance, and availability across that mix.

Which WordPress plugins belong in the portfolio?

Include plugins and developer tools that demonstrate relevant work, have a clear contribution from you, and can be described accurately today.

Create separate cards for genuinely different products, not for the directory page, repository, docs, and checkout of one plugin. State whether you built the whole plugin, maintained it, contributed a feature, or delivered it for a client.

Theme customisations, migration scripts, blocks, and internal integrations can appear when they form meaningful projects rather than isolated snippets.

What is the fast way to build the WordPress developer portfolio with IndieShow?

The fast way is to claim an IndieShow handle and group directory plugins, commercial tools, active builds, and retired client work by status.

Add the plugin logo, a precise WordPress or WooCommerce tag, a one-sentence purpose, and one public destination when available. Put maintained installable work first and clearly archive unsupported plugins.

For confidential work, use a generic approved name and description or omit it. IndieShow does not require you to upload the client's code or system.

Build your IndieShow pageClaim a handle, organise the projects in the editor, and review the $15 one-year and $30 lifetime publishing options in the dashboard.

Should a plugin card link to WordPress.org, GitHub, docs, or a product site?

Link to WordPress.org for a maintained directory install, GitHub for public engineering evidence, documentation for integration review, or the product site for a commercial canonical page.

Test the link logged out and confirm the version is still supported. A closed checkout or abandoned directory listing should not remain presented as an available product.

Since each project card uses one destination, choose the page that best serves the visitor and explain other relevant surfaces in the description.

How can private client plugins be shown without exposing confidential work?

Describe the problem category, your responsibility, and an approved outcome while omitting client identity, code, credentials, data, and reconstructable implementation details.

Do not publish screenshots from a private admin, copied tickets, production URLs, or unapproved performance figures. If no safe description exists, leave the engagement out and rely on public proof.

The related IndieShow guides cover NDA-safe automation work and presenting projects spread across different platforms.

How does IndieShow keep a WordPress portfolio useful between releases?

IndieShow keeps one public developer URL while you reorder plugins, update links and descriptions, and move unsupported work into Archived.

WordPress.org, GitHub, documentation, and product sites stay authoritative for installation and detail. IndieShow supplies the maintained overview that connects them to one developer identity.

Close with the plugins a visitor can evaluate now, your exact role in each, and no claims that exceed the public evidence or client permission.