| commit | c903cabfb404420e60425d7b28084cbec3e676de | |
| author | intrigeri <intrigeri@boum.org> | |
| Sun, 21 Jan 2018 21:05:33 +0000 (21 21:05 +0000) | ||
| committer | Michael Stapelberg <stapelberg@users.noreply.github.com> | |
| Sun, 21 Jan 2018 21:05:33 +0000 (21 22:05 +0100) | ||
| tree | 1859fcf7918922ecf33f1944986706ab2665887f | treesnapshot (tar.gz zip) |
| parent | b49bd8be9ca922e9bfd13a4896e4c6040b0fb215 | commitdiff |
Phrase the error message when there's no result in a nicer manner. (#88)
"Did you read the FAQ" may be interpreted by some users of the service as
a reproach about not having read it already. This conflicts with the usage path
that's encouraged: the homepage does mention the FAQ but not as a compulsory
first step before using the service; for example, the focus is set by default in
the search box.
So when there's no result, let's instead guide the user towards one of the
possible paths to solving their problem, that is the FAQ. Ideally the word "FAQ"
in this error message would be a link to the FAQ but I lack time to learn how to
test such changes myself right now.
"Did you read the FAQ" may be interpreted by some users of the service as
a reproach about not having read it already. This conflicts with the usage path
that's encouraged: the homepage does mention the FAQ but not as a compulsory
first step before using the service; for example, the focus is set by default in
the search box.
So when there's no result, let's instead guide the user towards one of the
possible paths to solving their problem, that is the FAQ. Ideally the word "FAQ"
in this error message would be a link to the FAQ but I lack time to learn how to
test such changes myself right now.
| static/instant.js | diffblobblamehistory |