Page MenuHomePhabricator

Usability: Picking a name for your wbcloud wikibase has opaque naming requirements
Closed, ResolvedPublic

Description

Story: As a user, I want to create a new Wiki. I want to give it a name that makes sense to me

Problem: Names have hidden requirements regarding non-alphanumeric characters, so names are rejected

image.png (54×448 px, 8 KB)

Possible solution:
a) It would probably very easy to provide in-context help via an (i) regarding allowed/forbidden characters. There is already such an (i) below:

image.png (43×391 px, 9 KB)

b) Upon giving back the validation result, tell what caused the violation

(This might need refinement into two tickets for implementation)

Hover icon copy: "The subdomain must be at least five-character long, and can consist of small Latin letters, digits and hyphens."

A/C

  • Solution A is implemented and the the new copy for the hover icon is as described above.

Useful links:

Event Timeline

toan renamed this task from Usability: Picking a name for your wbcloud wikibase as opaque naming requirements to Usability: Picking a name for your wbcloud wikibase has opaque naming requirements.May 4 2022, 12:15 PM
toan updated the task description. (Show Details)
dang removed dang as the assignee of this task.May 11 2022, 1:03 PM
dang added a subscriber: dang.

I think the copy might be wrong here, i've tried this out locally and on wikibase.dev and it seems to be a five char requirement

I think the copy might be wrong here, i've tried this out locally and on wikibase.dev and it seems to be a five char requirement

yes https://github.com/wbstack/api/blob/main/app/Helper/DomainValidator.php#L27

updating the copy

All clear, when we did task breakdown we said 4 and the task desc said 4 also. Never bother to check again. Lemme fix that real quick

Thanks for spotting. I must have done maths wrong.

updating the copy

I hereby declare updated copy to be the correct one and the one to use. Thanks.

Hint on the subdomain indeed added, verified. Probably a more clear hint on incorrect input would still be useful at a later stage.

Tarrow claimed this task.