►
From YouTube: Why to avoid linking from UI to docs
Description
Here is a great example of how links from the UI to the docs can result in a bad user experience. It's better to have no link than to have a bad link.
Pajamas guidance here: https://design.gitlab.com/usability/contextual-help
A
Hi
so
I
just
noticed
a
UI
link.
That
is
one
of
the
reasons
why
we
try
not
to
link
from
the
UI
to
the
docs
and
I
just
wanted
to
share,
because
it's
it's
a
bad
user
experience
that
I
think
we
can
all
learn
from
so
I
go
to
settings,
General,
Advanced
and
then
I
want
to
remove
the
forking
relationship
and
I'm
expecting.
Oh,
this
will
teach
me
more
about
forking
relationships.
A
Hopefully,
but
I
click,
the
link
and
oh,
it
tells
me
basically
the
same
things
that
are
in
the
UI
and
how
to
get
to
where
I
already
was.
It
says:
go
to
settings
General
advanced,
so
it
probably
wasn't
created
this
way
from
scratch.
But
the
docs
are
constantly
changing
and
we're
getting
contributions
from
around
the
world
all
the
time
and
we're
always
updating
things
trying
to
improve
them,
and
things
like
this
get
lost
in
the
shuffle.
And
then
you
end
up
with
a
bad
user
experience.
A
So
when
you're
designing
UI,
you
really
should
try
to
put
the
content
into
the
UI
and
don't
worry
so
much
about
help
links
because
we're
getting
an
approved
search
and
we
want
people
to
search
the
documentation,
but
it's
better
to
have
no
link
than
to
have
this
link
that
sends
them
in
a
circle.
Thanks.