►
Description
Weekly sync call of the Static Site Editor group focused on product and design efforts
A
All
right
welcome
everyone
to
the
static
site,
editor
product
and
design
weekly
call
for
july
27th
2020..
A
I
don't
have
a
ton
on
my
agenda
that
wasn't
covered
in
the
earlier
meeting,
but
a
follow-up
on
one
of
the
items
was
that
I
did
go
ahead
and
record
a
video
and
kick
off
our
internal
testing
of
the
static
site
editor
with
the
product
team.
I
let
everybody
know
that
they
can
edit
the
product
pages
and
I
sent
them
a
link
to
the
feedback
issue.
I
hope
we
get
a
lot
of
new
users
in
the
coming
week
or
two
I'll
also
be
bringing
it
to
the
product
weekly
meeting
on
the
agenda
next.
A
A
Like
it
and
then
just
to
recap,
a
few
things
from
below
for
michael's
sake,
but
maybe
we
can
dig
in
a
little
deeper
on
some
of
these.
I
am
going
to
not
officially
delay
because
I
never
had
it
on
the
books,
but
we
were
talking
about
maybe
doing
story
mapping
on
thursday
instead
of
our
social
call.
I
think
we
should
keep
our
social
call.
I
talked
to
john
about
this.
A
It
might
be
next
week
or
the
week
after,
but
probably
no
later
than
that,
I
don't
want
to
push
it
too
far
out
and
then
we
have
a
correct
maturity
date
and
the
reason
I
bring
this
up
again
is,
I
know,
michael
you've
been
involved
in
some
of
the
category
maturity
scorecards,
which
I
I
was
involved
in
a
issue
through
head
that
specified
that
I
should
stop
calling
a
ux
scorecard
because
there's
two
processes,
the
category
maturity
score
card,
is
the
lighter
weight
like
two
or
three
questions.
A
And
as
an
fyi,
I
signed
us
up
for
the
group
conversation
on
august,
18th
I'll,
be
hosting
there's
no
like
requirement
that
we
all
be
on
the
call,
but
it
could
be
interesting,
as
I
mentioned
earlier
today,
my
I'm
more
nervous
about
nobody
showing
up
than
I
am
presenting
to
the
whole
company.
A
So
I,
if
you
can
spread
the
word
and
encourage
people
interested
in
the
static
site,
editor
to
join
I'll
start
doing
my
own
little
promo
rounds
around
slack
leading
up
before
the
meeting,
but
hopefully
we'll
get
some
good
questions,
get
a
lot
of
interest
and,
and
then
hopefully
it'll
be
very
shortly
before
we're
ready
to
just
roll
out
the
handbook.
I
mean
the
editor
and
the
handbook
altogether.
A
It's
really
good.
On
my
side
we
touched
a
little
bit
on
134
planning.
I
guess
I
should
talk
about
that,
while
you're
here,
michael,
my
intent,
is
to
flesh
out
the
the
issue
which
I'll
probably
turn
into
an
epic
for
editing
front
matter
in
the
static
site
editor
so
that
we
can
start
exploring
it
unless
there's
a
reason
why
it
won't
work
or
we
need
more
time
to
do
research.
A
I
think
that'll
be
a
good
candidate
for
for
our
like
next
meaningful
feature,
while
we're
figuring
out
the
research
and
the
ux
for
the
merge
request
flow,
there's
a
there's,
a
few
other
things
and
obviously
I'll
have
a
planning
issue
in
the
coming
week
or
week
and
a
half
that
we
can
collaborate
on,
but
that'll
be
the
one
big
feature.
The
directional
feature
that
I'm
focusing
on.
C
Yeah
I
was
muted,
but
that
was
okay.
I
was
going
to
jump
on
to
the
next
one,
but
yeah
jumped
on
it.
That's
cool,
yeah
yeah.
I
thought
the
first
session
went
well.
I
think
there
was
a
bit
of
a
hiccup
with
the
prototype,
but
other
than
that,
I
I'm
getting
what
I
need
from
it.
I
think
it's,
I
think,
there's
a
lot
of
stuff
in
there
for
a
30
minute
session.
So
it's
like
a
really
like
I
realized
at
the
end.
C
I
didn't
really
leave
any
time
for
you
to
ask
any
questions
or
or
the
participant
to
ask
any
question
it
was
just
like
boom
boom
boom
boom
boom.
It
was
like
okay,
it's
pretty
jam-packed,
I
think
so,
but
from
from
what
I
see
from
it,
it's
okay!
Well,
I
think
we're
getting
some
information
here.
I
made
some
changes
to
make
the
prototype
not
work
better.
On
smaller
screens,
I
made
like
little
nudging
changes
with
like
the
copy,
and
things
like
that.
C
I
also
updated
the
prototype
to
reflect
the
new
direction
on
what
I'm
proposing
for
what
I'm
saying
the
direction
is
for
moving
the
edit
links
up
on
the
page.
So
I
don't
know
if
you
saw
that
issue.
Let
me
try
to
link
that,
but
I
moved
the
links
to
the
sidebar
for
for
this
iteration
here
I
don't
know
if
you
saw
that.
A
I
saw
the
issue
I
didn't
get
a
chance
to
click
through
yet
today,
but
I
yeah
yeah
take
a
look
at
it
now:
okay,.
C
Because
the
example
that
I've
been
working
with
with
the
prototype
doesn't
have
like,
so
if
you
go
to
like
the
gitlab
the
product
page,
it
has
a
whole
list
of
links
at
the
top
and
chucking
in
our
putting
in
like
contribute
to
this
page
at
that
top
as
well
as
like
be
updated
by
whoever.
At
this
time,
I
thought
by
adding
that
without
really
reconsidering
that
top
area,
I
think
it's
just
going
to
get
messy
over
time.
So.
C
Rather
than
trying
to
solve
that,
I
kind
of
pulled
back
the
scope
of
the
ticket
to
just
look
at
like
moving
the
links
up
to
the
top
of
the
page
somewhere.
So
I
probably
went
with
like
one
of
your
original
considerations
of
having
like
contributes
to
this
page
and
then
a
list
of
the
links
underneath.
But
I
just
laid
it
out
a
little
bit
different.
C
B
A
Thoughts
on
this
question,
I
felt
the
same
way
I
feel
like
we're
getting
good
information.
I
think
there
are
yeah.
I
mean
it's
just
one
data
point,
but
it
was
it
was.
I
took
some.
I
took
some
notes
and
I
meant
to
summarize
them
in
an
issue
which
I'll
do
first
thing
in
the
morning
as
well.
If
you
want
to
summarize
your.
C
Notes,
do
you
want
to
do
it
directly
in
dovetail,
and
then
we
oh.
B
C
Yeah
right
yep
bring
it
back
once
we've
done
this
sessions.
B
C
Yeah,
I
appreciate
you
going
through
that
too
chad.
It
was
really
helpful.
Having
you
know,
people
within
the
team
to
go
through
it
as
like,
also
a
rehearsal
run,
but
also
like
ironing
out
any
kind
of
flows.
So
some
of
the
comments
that
you've
made,
like
I
incorporated
into
this
as
well
so
yeah,
it's
really
valuable
and
yeah.
I
think
I'm
gonna
start
recruiting
internally
just
for
dry
runs
because
it's
good
for
other
people
to
get
exposure
to
it,
not
just
only
like
eric
and
myself
and
john,
but
like
yeah,
get
other
people
involved.
C
B
C
I
ran
it
through
with
derek
as
well
on
our
team
so
and
then,
after
this
call,
I'm
going
to
talk
to
lauren
about
it
so
lauren's
the
front-end
engineer
on
the
brand
marketing
website
so
and
we
haven't,
I
think,
but
we
also
have
some
other
people
lined
up.
So
there
was
a
lot
of
people
who
were
enthusiastic
about
giving
feedback,
so
I
think
editing
front
matter
will
be
one
where
yeah
I
might
pull
in
more
engineering
like
people
in
there,
but
also
have
some
mix
of
other
people.
Who've
interacted
with
what
matter
before.
C
Which
kind
of
segues
to
like
you
know?
I
think
we
should
be
doing
these
solution,
validation,
things
like
at
least
once
a
milestone.
I
think
it
kind
of
slipped
on
my
radar,
or
I
think
I
was
thinking
too
big,
but
I
think
we
have
a
few
things
lined
up
that
we
could
do
some
solution,
validation
on
so
editing
front
matter.
I
think
there
could
be
a
light
one
just
to
see
like
which,
where
the
panel
should
be,
should
it
be
a
side
panel
top
panel.
B
C
Or
whatnot
but
yeah
it
might
be
an
interesting
one
to
just
to
get
some
feedback,
because
I
know
that
in
the
first
round
of
interviews
we
had
like
one
individual
who
knew
what
from
one
or
two
individuals
who
worked
with
what
matter
at
least
once
or
twice
in
their
career
at
get
lab.
So
it's
good
to
get
those
people
back
involved
in
this
because
they
know
what's
up
so
yeah,
I
might
reach
out
to
those
people
again.
A
B
A
You,
know
the
scope
and
make
sure
that's
clear
and
then-
and
you
know,
small
enough
iterative
enough
and
then
work
on
a
prototype
and
start
recruiting
shouldn't
be
too
hard
to
find
a
handful
of
people
that
one
is
going
to
be
tricky,
but
I
was
talking
with
john
about
it
and
I
think
of
all
the
the
things
that
are
kind
of
near
term
on
our
our
backlog.
A
On
one
hand,
it's
the
it's
one
of
the
things
that
would
be
least
likely
to
be
have
to
be
redone.
If
we
decide
to
go
with
a
new
editor
and
it's
more
directionally,
it
telegraphs
our
direction,
a
little
better
with
what
we're
doing
with
the
editor.
What
we
want
to
do
with
the
editor,
then
something
say
like
the
markdown
formatting
shortcuts,
which
I.
A
To
be
in
there,
too,
but
for
things
like
just
editing
the
title
or
even
being
able
to
help
the
the
handbook
be
more
seo
friendly
or
like
introduce
a
new
type
of
front
matter
to
the
handbook
that
can
benefit
it
and
then
make
it
really
easy
for
people
to
configure
the
properties
of
that
front
matter
in
the
editor
would
be
a
huge
win
yeah.
So
I'd
like
to
yeah
I'd
like
to
at
least
get
going
on
some
solution,
validation.
A
And
then
I
added
this
last
bullet
because
I
forgot
to
mention
it
before
I
got
a
message
on
slack
from
kai
the
pm
for
the
web
ide
for
the
editor
team,
our
editor
group-
and
he
shared
this
dovetail
link,
which
is
some
a
survey
they
did
regarding
when
people
use
the
different.
B
A
The
single
file
editor
and
the
web
ide,
and
why
there's
some
interesting
information
in
there
about
editing,
markdown
and
the
different
use
cases
for
the
different
editors?
This
did
not
include
anything
about
static
site
editor,
but
we
can
probably
extrapolate
from
those
use
cases
and
and
learn
a
little
bit.
A
A
Oh,
you
don't
have
a
login,
I
don't
know
let.
C
Yeah,
I
can
give
you
access
to
chat.
I'm
just
gonna
look
up
your
email
now,
so
dovetail
is
like
a
new
tool
to
manage
research
and
findings
like
this,
but
yeah.
It's
just
been
rolled
out
recently,
so
it's
kind
of
like
the
same
thing
that
we
had
with
figma,
where
some
people,
when
we
had
a
bit
of
a
hiccup
with
like
permissions
a
few
times
but
yeah.
C
C
That's
it
from
my
side:
oh
yeah.
I
guess,
like
I
have
a
few
days
off
at
the
end
of
this
week,
starting
next
week
and
maybe
randomly
next
week
but
yeah.
If
you
wanted
to
do
the
you
know,
I
think
big
session
or
something
like
the
same
time
as
the
social
call
works
really
well
with
me
on
most
days,
because,
like
that's
night
time
over
here
and
like
yeah,
I'm
pretty
much
night
owl
so
I'll
be
awake.
But.
C
For
scheduling
for
me
at
those
times,
so
if
you
are
considering
like
using
wednesday
or
thursday
yeah
or
if
I
you
know
thursday
wednesday
next
week,
yeah
just
yeah
just
book
it
and
if
there's
any
issues
or
if
you
want
to
pick
me
first
in
slack,
that's
fine
too.