►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
And
my
name
is
michael
lee
of
the
static
site,
editor
team,
and
this
is
the
ux
update
for
13.3.
So,
let's
get
into
it.
The
main
goal
of
the
group
is
taking
the
experience
of
the
static
site
editor
and
integrating
it
into
the
gitlab
handbook
so
that
we
can
get
towards
viable
maturity.
A
So
that's
key.
Some
things
that
we're
looking
at
of
adding
to
the
static
site,
editors,
the
ability
to
upload
a
video
and
images
to
the
static
site
editor
and
from
a
design
in
ux
perspective.
What
we're
looking
at
is
doing
some
solution.
Validation
on
some
upcoming
features,
such
as
improving
the
journey
from
the
static
site
editor
to
I
mean
from
the
handbook
to
the
static
site,
editor
and
then
looking
at
how
we
can
take
some
of
the
actions
that
are
traditionally
more
done
in
the
merge
request
pages
directly
in
the
static
site
editor.
A
So
as
part
of
13.3
we'll
be
conducting
a
few
rounds
of
usability
testing
around
the
solution,
so
I'm
just
going
to
walk
you
through
that
right
now
I
have
a
spelling
mistake
here
on
single
applications.
Click
on
this
we
can,
edit
with
the
new
editor,
have
this
kind
of
experience
or
we
can
go.
A
What
we're
trying
to
do
here
is
move
some
of
the
links
up
from
the
bottom
of
the
page,
to
be
more
contextual,
so
here
we're
just
going
to
jump
into
the
static
site.
Editor
make
the
change
in
exploring
the
idea
of
and
the
need
to
save
enemies
to
draft
through
the
use
of
merge
requests
and
then
everything
doing
a
once
over
everything
looks
good.
A
So
then
I'll
just
go
ahead
and
submit
some
of
my
changes,
and
this
is
what
I
was
talking
about
about
bringing
some
of
the
actions
of
assigning
titles
and
descriptions
earlier
in
the
process
directly
in
the
static
site
editor
and
what
we're
trying
to
engage
in
this
area
of
the
prototype
is
for
displaying
the
right
information
and
to
see
if
we're
missing
any
other
bits
of
information
that
would
be
needed
for
the
individual
making
the
change.
So
I
can
update
the
title,
describe
the
change
and
then
assign
my
review.
A
The
assignee
submit
my
changes,
changes
submitted
and
I
can
go
back
to
continuing
the
editing
or
potentially
view
the
merge
requests.
If
I
really
wanted
to
I'll
go
back
to
continue
editing,
actually
I
decided
that
I
don't
need
to
do
anything
else,
so
I
just
go
back
in
a
review
of
this
page
again.
Oh
and
it
looks
like
there's
a
spelling
mistake
here,
so
I'll
just
go
here,
hit
it
with
the
new
page
change
that,
but
I
actually
want
to
associate
this
to
the
existing
merge
request,
and
I
can
just
go
through
here.
A
So
whether
this
makes
sense
or
not
to
users
is
the
whole
reason
we're
going
to
do
some
solution.
Validation.
We
want
to
make
things
as
streamlined
as
possible,
but
we
just
want
to
get
a
gauge
if
we're
heading
in
the
right
direction.
A
So
there
we
are
that's
what
we're
doing
for
solution,
validation
and
the
highlights
of
that
is
to
understand
whether
we're
doing
the
right
things
around
the
journey
from
of
the
handbook
over
to
this
site
editor
and
if
we're
doing
the
right
things
in
surfacing
the
right
information
when
creating
a
merge
request
from
the
static
site
editor,
so
that
people
don't
need
to
go
to
the
merge
request
page
and
they
can
just
keep
their
experience
directly
closer
to
the
content.