An integration cannot supply the words that explain it on the pages it owns #57
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#57
Reference in New Issue
Block a user
What a person cannot do today
An integration developer cannot attach a plain-language line to the surfaces their integration puts in front of a member or an operator. The member dashboard card, the provider page and the readiness rows carry the integration's name and nothing that says what it is, so the name arrives unexplained to anyone who does not already know the product.
What they should be able to do
Declare, with the card and the provider entry, the short description that appears with them, so the explanation belongs to the integration that needs it rather than to the console's own copy.
Why it matters
The console is not the right place to explain a third-party product: a deployment usually sits behind a site of its own that introduces whatever it offers, and every deployment offers something different. A core string cannot serve them all, and an integration that needs one has nowhere to put it.
Where
The dashboard card type and the provider registry entry, and the parts that already render the card and the page headers.
Done when
An integration can declare a description alongside its card and its provider entry, the existing parts render it where it is set and nothing where it is not, and no product name appears on a member surface with no way for its integration to introduce it.
Migrated from status/issues.md at
b7a0e15