B Blengi docs
/

WordPress & WooCommerce

Plugin distribution

Every workspace's /settings/integrations WordPress card shows a Download plugin link that serves your own branded plugin zip straight to the customer. Nothing to host: the server serves the latest build (and builds one on the first request if none exists yet).

Where to set the text

Super-admin only. Sign in as a platform admin and visit /settings/system#integrations (the "Integrations" tab inside System settings — the WordPress plugin block lives there alongside the workspace-facing integration toggles). Two fields:

  • Help text — short blurb shown before the links. Max 2000 chars. Leave blank to fall back to the default.
  • Download URL — a legacy mirror link. It is still saved (validated as a URL, max 500 chars), but the customer's card no longer uses it: the Download plugin link always serves the direct branded download.

What customers see

On /settings/integrations the WordPress card footer reads: 

{help_text} Download plugin · WordPress install & connect

With no help text, the first part is the default "Download the WordPress plugin and follow the setup guide:". Both links are always there. Help text is rendered as plain text — markdown or HTML in it shows as literal characters.

Build a white-labelled plugin zip

Super-admins build the actual .zip at /admin/integrations/wordpress → Build latest, then Download. The build is automatically branded with this install's identity — it reads your brand name from Settings → Branding (the site title) and your brand URL, then stamps them onto the plugin so the customer's WordPress admin shows your brand, not "Blengi":

  • The Plugin Name in the WordPress Plugins list, the Author, the description, and the author/plugin URLs in the plugin header.
  • The Settings menu label, the settings page heading, and every on-screen label, notice, and connection-test message.

Only display text is rebranded. Internal code identifiers (the PHP namespace, the pitchbar text domain, option keys, and script handles) are deliberately left unchanged so the plugin keeps working and upgrades cleanly. The install folder stays wp-content/plugins/pitchbar/. The downloaded file is named after your brand too — e.g. blengi-2.0.5.zip instead of pitchbar-2.0.5.zip.

You can grab the branded zip in three places, all serving the same build: the Download plugin button in Settings → System → WordPress plugin distribution, the Build / Download page at /admin/integrations/wordpress, and — for customers — the Download plugin button on their own /settings/integrations WordPress card. The customer button always serves this direct branded download; the legacy "Download URL" field no longer changes it.

From the CLI you can pass an explicit brand instead of the install default: 

php artisan pitchbar:build-wp-plugin                     # brands from Settings → Branding when built via the UI
php artisan pitchbar:build-wp-plugin --brand="Blengi" \
    --brand-url="https://blengi.com" --author="Blengi"  # explicit white-label

This is independent of the Help text above — that only changes the words next to the customer's download link; the branded build controls what the zip says.

Related