►
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
Hello,
my
name
is
michael
lee
and
I'm
in
the
static
site,
editor
team
and
today
I'm
going
to
do
a
walkthrough
of
the
publishing
flow
and
prototype.
So
let's
get
into
it.
So
we're
going
to
start
off
on
the
handbook
page
here
at
the
static
site,
editor
page-
and
I
want
to
make
some
edits
to
this
page
and
then
click
on
this
we're
going
to
see
what
the
feedback
is
around
this.
The
new
kind
of
interaction
of
showing
edit
this
page
right
by
the
and
the
static
site
editor
under
the
name
of
new
editor.
A
So
I'm
going
to
click
on
that.
Now,
I'm
going
to
get
taken
directly
into
the
static
site
editor
in
edit
mode.
So
while
in
edit
mode,
I'm
just
gonna
get
the
user
to
click
on
the
contents
to
simulate
edit
and
then
we're
gonna
see
what
they
notice
here.
There's
some
unsaved
changes.
So
what
you
want
to
do
about
it?
A
So
here
it
says,
create
merge,
request
for
saving
changes.
Okay,
your
work
will
be
saved
and
to
merge
a
new
merge
request
and
it's
using
this
branch.
You
can
edit
the
title
description
later.
Okay,
it
sounds
good.
I'm
going
to
create
this
merge
request
cool
so
that
merge
request
has
been
created
and
I
see
it's
a
work
in
progress,
merge
request
with
an
update
to
this
title
page
and
so
the
title
of
the
page
itself
and
then
and
there's
two
or
four
tasks
completed
okay,
cool.
A
I
made
my
change,
so
I'm
happy.
So
let's
go
ahead
and
publish
this,
so
I
had
the
title
and
then,
as
I
do
the
description
I
had
a
description
in
here.
There's
a
little
progress
bar
here.
I
don't
know
if
people
will
notice,
but
let's
see,
what's
going,
let's
see
how
that
goes,
and
the
assignee
this
individual
will
be
reviewing
and
merging
the
change
I'll
do
that
later.
A
So
I'm
just
going
to
go
ahead
and
publish
this,
so
that's
been
published
yeah
and
the
screen
should
be
bigger
for
this,
but
and
there's
a
pop-up.
So
I
can
view
or
close,
I'm
just
gonna
close
that
with
this
now
this
is
in
the
view.
A
I
just
published
some
stuff
in
the
front
so
from
here.
I
can
click
on
this
to
jump
into
the
merge
request
page.
So
I
can
see
that
oh
okay
cool,
that's
there,
so
let
me
go
back
and
then
that's
essentially
the
straight
edit
flow.
A
A
It's
prompting
me
to
create
another
merge
request
for
saving
changes,
but
I
want
to
use
an
existing
merge
request.
So
I'm
going
to
click
on
that.
This
is
just
dummy
data
right
now.
It's
all
the
same
thing,
I'm
just
going
to
select
that
merge,
request
and
say
use
that
one
and
then
I'm
in
this
merge
request,
update
ux
maturity
and
like
before.
A
There's
this
one
here,
three
or
four
completed
that's
cool
and
then
I
can
go
ahead
and
make
some
edits,
save
that
and
then
the
screen
size
should
be
bigger,
but
there's
a
little
toast
that
pops
up
there
so
in
a
whole
nutshell,
that's
the
publishing
flow
for
the
static
site.
Editor
there's
a
lot
of
things
to
unpack
and
test
here
and
out
of
under
the
solution,
validation.
We
can
refine
some
of
these
aspects
of
the
prototype.
A
So
I'm
just
going
to
jump
into
one
area
here.
So
one
of
the
discussions
that
was
talking
about
was
whether
we
force
the
merge
requests
at
the
start
of
entering
the
static
site
editor
after
much
discussion
from
the
engineering
manager,
john
and
the
product
manager,
eric
they're
saying.
No,
I
don't
think
that's
a
good
idea.
A
It's
not
good
because
you're
taking
away
control
from
the
users
by
creating
things
that
they
didn't
really
want.
So,
instead
of
that,
what
we're
going
to
do
is
when
there's
unsaved
changes
or
the
first
time
you
interact
with
either
save
or
publish
changes.
A
One
question
here
is:
how
might
we
handle
the
scenario
of
committing
directly
to
master,
and
perhaps
we
can
postpone
this
to
a
future
consideration,
but
this
kind
of
paradigm
makes
sense,
and
also
in
the
scenario,
if
I
don't
have
permission
to
merge
directly
to
the
repository.
So
the
scenario
here
is
like
I'm
outside
the
organization
or
something
like
that
and
in
those
scenarios
I
need
to
fork
the
repository
before
making
changes
so
using
the
same
kind
of
interaction.
We
can
stick
in
different
models.
A
So
in
this
scenario,
if
I
click
save
a
motor
will
pop
up
saying
you're
not
authorized
to
make
any
changes
directly
to
the
repositories.
Please
create
a
fork
of
the
repository
to
save
changes
and
then
you
can
create
a
fork
from
here
and
it's
just
an
additional
a
check
that
we'll
have
in
the
flow.
But
it
keeps
the
user
interface
kind
of
consistent.