►
From YouTube: Create UX - 13.2 - Static Site Editor
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
Today,
I'm
gonna
go
through
some
of
the
items
that
I'll
be
looking
at
for
13.2
for
the
static
site.
Editor
group,
my
name
is
Michael
Lee
and
I'm,
the
senior
pastor
designer
and
the
team
soin
13.1.
We
added
this
maintained
by
section
in
the
handbook
and
in
this
next
milestone
we're
gonna
iterate
on
adding
more
functionality
to
the
handbook
page
by
reconsidering,
where
we
put
these
edit
and
open
IDE
page
links
on
the
page.
A
So
there's
an
issue
here
to
suggest
moving
it
to
the
top
of
the
handbook
pages,
and
this
issue
has
been
on
the
docket
for
almost
a
year
now
and
there'll
be
a
little
bit
of
exploration
on
the
design
and
then
the
implementation
of
that
so
we're
looking
at
making
it
easier
for
people
to
contribute
by
making
the
links
to
suggesting
a
change
easier
and
more
visible
in
the
world
of
the
static
site.
Editor
we're
iterating
on
what
this
screen
looks
like,
so
we're
experimenting
with
making
simplifying
the
information.
A
That's
on
the
screen,
so
that
it's
more
helpful.
So
it
gives
you
a
description
of
things
that
you
can
do
and
just
clicking
on.
This
link
will
take
you
to
viewing
the
merge
request,
we're
removing
some
of
the
information-
that's
that
was
there
originally,
such
as
the
branch
name
and
the
commit
ID
that
we
don't
really
need
at
this
moment.
But
you
really
want
that
information.
A
You
can
jump
into
the
merge
request
and
view
that
one
of
the
big
things
in
13.1
that
the
engineering
team
worked
on
was
actually
researching
on
how
we
were
gonna
parse,
the
markdown
file
to
separate
into
nodes
between
content
that
is
venerable
as
markdown
content,
such
as
headings
and
paragraphs
and
links
and
lists
things
that
you're
commonly
used
to
versus
other
content,
such
as
mermaid
diagrams
embeds
codes.
So
the
team's
done
a
lot
of
work
in
the
background
to
understand
the
problem
in
this
milestone,
we're
gonna
take
a
look
at
displaying
some
of
this
content.
A
So
during
this
milestone,
we're
gonna
start
taking
a
look
at
doing
research
around
validating
the
publishing
flow
for
static
site
editing
so
where
the
idea
of
the
static
site
editor
is
that
it's
a
publishing
workflow
on
top
of
a
get
framework,
and
we
are
going
to
experiment
and
test
to
see
what
flow
makes
the
most
sense
for
the
mental
models
of
a
content
editor.
On
top
of
like
a
kit
and
paste
in
a
repository,
the
next
one
we're
gonna
look
at
is
the
editing
experience
itself.
A
So
we
don't
want
to
box
ourselves
too
much
in
a
hole
so,
as
a
stretch,
stretch
goal
for
this
milestone,
you're
starting
to
export
Explorer
thinking
around
what
other
areas
such
as
editing
issue
descriptions.
Could
that
be
something
where
the
static
site
editor
makes
sense,
or
should
we
focus
on
the
gaps
in
the
market
of
static
site,
editing
and
publishing?