►
From YouTube: Solution validation Wiki layout #1505
A
So
I'll
be
talking
today
about
recent
solution.
Validation
around
the
wiki
layout
changes,
so
the
first
I
took
people
through
two
actions.
A
The
first
one
was
taking
a
look
at
this
in
the
reading
state,
so
the
read-only
state-
and
some
of
the
ideas
I
wanted
to
explore
here,
was
like
how
useful
the
sidebars
actions
are
clone
repository
edit
sidebar,
and
also
try
to
find
how
if,
if
using
this
triple
dot
menu,
is
a
good
idea
to
tuck
away
actions
that
used
to
be
there,
such
as
page
history
and
looking
at
new
menu
options
such
as
delete
page
to
see
if
this
is
a
good
way
to
go
down.
A
So
around
clone
repository
and
edit
sidebar
clone
repository
people
understood
what
it
meant
like
cloning,
the
project,
but
whether
they
what's
kind
of
unclear
is
like
how
often
they
actually
use
this
like.
How
often
is
clone
repository
used
from
from
the
solution
validation.
It
felt
that
people
understood
this
concept,
but
actually
didn't
use
the
feature
a
lot
as
for
edit
sidebar,
they
associated
the
sidebar
is
this
area
here,
and
they
suggested
that
edit
sidebar
allows
you
to
reorganize
and
change
the
names
and
order
of
these
in
this
list.
A
On
the
right
hand,
side
and
that's
not
exactly
true
and
a
sidebar-
replaces
like
the
content
on
the
right
hand,
side.
So
that's
something
that
we
could
explore
rephrasing
some
of
these
actions
or
taking
a
look
at
how
we
might
make
reorganization
easier
down
to
this
this
layout.
A
Here
I
went
with
this
idea
of
moving
the
edit
button
up
here
and
making
almost
like
a
tertiary
action
to
see
if
people
would
notice
or
would
say
anything
about
it,
and
the
task
here
was
to
say:
hey,
how
would
you
delete
the
page
and
the
current
flow
is
to
go
into
the
edit
mode
and
once
getting
into
the
edit
mode,
then
from
there
there's
a
delete
button
and
you
can
delete
the
page
from
there,
but
we
have
a
issue
out
there
at
the
moment
that
considers
surfacing
it
at
the
root.
A
At
this
view-
and
the
idea
here
is,
if
you
click
on
it,
you
can
delete
page
and
people
found
this
action
eventually,
no
one
couldn't
find
it.
People,
if
they
didn't
see
it
immediately
on
the
screen,
would
just
automatically
gravitate
towards
the
triple
dot
menu.
So
I
think
that's
a
standard
practice.
That's
that
we
can
leverage
to
talk
away
some
of
the
actions
that
we
don't
want
to
focus
too
much
and
highlight
on
actions
that
we
do
care
about.
A
So
we
have
new
page
currently
as
a
primary
action.
Others
cms
wiki
tools
have
new
pages
the
primary
action
on
their
page
as
well.
So
I'm
fine
with
taking
that
forward.
The
area
where
I
was
kind
of
curious
was
this
action
like
what
actions
would
people
want
to
have
in
here
versus
edit,
or
should
edit
be
the
main
action
funny
enough?
I
recruited
two
groups
of
people
for
this.
One
was
just
like
generic
people
who
use
confluence
or
other
wikis,
and
another
group
were
get
lab
users.
A
So
that
was
an
interesting
insight
on
people
coming
in
from
different
platforms
and
what
they
expected
to
see
here
now,
since
we
don't
have
a
current
issue
of
sharing
issues,
I
would
say
that
I
would
want
to
make
the
edit
button
the
key
action
here
and
so
it'll
be
edit
page
new
page
and
some
of
the
questions
that
could
come
out
right
now.
It's
like
in
issues
and
description
and
merge
requests,
etc.
A
Normally
we
associate
the
edit
button
down
here,
but
the
difference
between
edit
buttons
here
and
up
here
is
that
in
the
issue
in
a
merge
request,
the
toolbar
up
here
controls
the
whole
area
down
here,
whereas,
like
the
edit
area
only
controls
this
area
in
the
wiki,
it's
slightly
shifted
where
the
actions
up
here
actually
dictate
the
whole
page,
so
it
actually
makes
sense
to
bring
edit
up
here.
So
that's
the
rationale
behind
that.
So
jumping
into
the
edit
flow.
A
One
thing
that
I
was
experimenting
here
in
larger
screens
is
having
the
action,
the
toolbar,
having
a
primary
secondary
and
with
all
other
actions,
tucked
away
here,
along
with
the
toolbar.
This
to
me
feels
like
a
way
that
we
can
maximize
the
space
on
the
screen,
while
maintaining
consistency
between
the
reading
state
and
the
editing
state,
and
one
of
the
things
that
I
was
experimenting
here
for
people
entering
the
editing
stages
like
if
I
had
to
edit
the
title.
How
would
I
know
that
I
would
edit
the
title?
A
Most
people
just
saw
this
and
said:
hey,
okay,
I'll
just
hover
over
this
and
click
on
it
and
edit
the
title.
So
this
is
experimental
and
kind
of
like
explorations
at
the
moment.
We
still
have
to
consider
other
things
like
accessibility.
How
do
we
do
this
without
labels,
or
do
we
want
to
have
a
label
at
the
top
here
and
how
does
this
fit
in
within
the
whole
pajamas
design
system?
A
Doing
so?
One
of
the
things
I'm
taking
that
is
not
visible
from
here
is
the
idea
of
the
sidebar
for
understanding
the
hierarchy
of
the
page
and
there's
no
messaging
here
to
say
that
you
can
change
the
path
of
the
page
by
adding
a
slap
slap
forward
slashes
to
the
input
box
to
change
the
directory.
So
I
kind
of
left
that
out
to
see
how
people
would
suggest
making
changes
so
based
on
the
ui
people
saw
this
and
said
hey.
A
A
Yeah
so
yeah,
that's
in
a
whole
nutshell
of
where
and
the
solution
validation
is
for
the
wiki
layout
moving
forward.
We
will
start
thinking
about
moving
the
layout
and
putting
actions
into
this
this
menu
up
in
here,
and
that
should
free
up
some
space
on
the
ui
so
that
we
can
rearrange
certain
things.
A
So
thinking
about
how
this
extends
at
the
moment,
I'm
thinking
that
everything
is
just
tucked
away
in
this
plus
sign,
but
we
will
also
leverage
more
of
the
slash
commands
on
the
wiki
page
for
ease
of
access
for
both
for
keyboard
users
and
everyone's
going
to
be
a
keyboard
user
in
this
state,
because
it's
editing
text
yeah.
If
you
have
any
questions,
please
leave
comments
in
the
issue.
Thanks,
bye.