Skip to content

Channels: actionable empty state with concrete transport options#66

Merged
lezama merged 1 commit into
mainfrom
ux/channels-empty-state
May 19, 2026
Merged

Channels: actionable empty state with concrete transport options#66
lezama merged 1 commit into
mainfrom
ux/channels-empty-state

Conversation

@lezama
Copy link
Copy Markdown
Owner

@lezama lezama commented May 18, 2026

Summary

The Channels empty state told users to "Activate a transport plugin" without saying which one. This PR replaces the dead-end message with a short list of supported transports (WhatsApp Cloud API, Telegram, external WhatsApp gateway, custom channels) — each with a link or pointer so the user knows where to go next.

Why

Found during a UX review of the full plugin tour. The previous copy required reading the README to discover that any transports exist at all.

Test plan

  • Visit openclaWP → Channels on an install with no channels registered. The new list appears.
  • The WhatsApp link goes to admin.php?page=openclawp-whatsapp and that page exists / renders.
  • Escaping is correct (no double-escaped entities, no PHPCS escaper complaints).
  • On an install with at least one channel, the empty state does not render (existing list rendering still wins).

🤖 Generated with Claude Code

Replace the dead-end "Activate a transport plugin to add one" message
with a short list of supported transports (WhatsApp Cloud API, Telegram,
external WhatsApp gateway, custom channels) so users can discover what
to install or build next directly from the Channels page.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@lezama lezama merged commit 09d2423 into main May 19, 2026
5 of 6 checks passed
@lezama lezama deleted the ux/channels-empty-state branch May 19, 2026 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant