►
Description
Weekly sync call of the Static Site Editor group focused on product and design efforts.
A
Welcome
everyone:
this
is
the
static
site,
editor
weekly
product
and
design
focus
call
it
is
july
20th
and
let's
get
it
kicked
off.
I
don't
have
any
high
level
fyis
or
anything
to
start.
Let's
flip
the
order
this
time,
because
I
feel
like
I
always
talk
a
bunch
first
and
only
give
you
five
minutes.
So,
michael
you
want
to
start
with
anything
design.
I
put
something
on
the
agenda,
but
do
you
have
anything
you
wanted
to
to
cover.
B
No,
nothing
really
to
cover
last
week
was
still
just
like
getting
some
feedback
from
the
team
on
the
prototype,
so
that
was
useful,
so
making
some
changes
there
and
then
today
I
will
be
adjusting
the
discussion
guide,
but
I
think
that
segues
nicely
into
interview
sourcing
internally
and
yeah.
Maybe
we
can
jump
to
your
point
there,
eric
on
a
slack
recommendation.
A
Yeah,
so
I
thought
about
it
from
our
conversation
last
time
separately,
I
put
together
a
spreadsheet
that
had
some
internal
stakeholders
and
a
document,
because
we
have
a
lot
of
people
interested
in
the
static
site
editor
internally,
it's
a
very
well,
we
just
say
the
the
founding
of
our
team
was
out
of
a
need
internally
to
make
the
handbook
editing
process
more
accessible.
So
we
have
a
lot
of
interested
parties
and
internal
stakeholders.
A
Not
all
of
them
would
make
great
ux
research
candidates,
though
so
I
was
thinking
more
about
it
and
I
think
the
slack
channels,
I've
posted
in
the
agenda
for
sales,
customer
success,
marketing
and
just
the
website
and
handbook
channels,
I
think,
are
an
approach,
maybe
not
the
best
approach,
but
an
approach
might
be
to
craft
a
message
with
a
link
to
a
calendly
link
or
a
google
form,
or
something
that
we
can
capture
interest
or
even
like
an
emoji
vote
and
just
put
out
a
blanket
call,
because
I
think
if
we
stick
to
the
people
that
we
know
already
use
it
or
are
interested
we're
gonna
get
a
little
bit
too
much
like
familiarity
with
how
we're
approaching
it.
A
Hopefully
we
can
get
a
few
fresh
eyes
in
a
slack
call
for
feedback,
so
I
think
these
would
be
good
channels
to
start
probably
just
posting
one
and
cross
post
it
to
some
others
and
hope
that
people
don't
get
too
annoyed
with
the
noise
if
they're
members
of
all
of
them
like
I
am
but
yeah,
that's
my
opinion.
A
I
don't
know
if
anybody
else
has
a
different
opinion.
I'm
open
to
feedback
on
it,
though.
B
A
Guides
was
that
to
me
or
catherine.
C
Oh
I'm
sorry,
I
I
think
this
is
a
good
approach.
This
I've
seen
a
lot
of
people.
Do
it
this
way.
I've
done
it
this
way
before
too
definitely
makes
sense
to
set
up
the
calendly
unless
you
would
rather
search
on
their
calendar
for
when
they're
available.
You
could
do
that
too,
but
yeah.
I
think
this
is
a
good
approach,
usually.
B
Okay,
because
with
the
calendar
lee,
I
think
the
one
issue
is
like
I'm
in
like
a
weird
time
zone.
So
then
it
will
never
line
up
perfectly
to
anyone
and
everyone
would
be
like.
I
don't
want
to
really
book
any
times
out
of
this
stuff.
So
can
we
do
like
a
combination
calendar
early
like
if
that
combines
like
eric's
in
my
time
together,
or
is
it
usually
just
one
in
one.
A
I,
the
probably
the
easiest
thing
to
do,
would
be
to
post
two
links
and
just
say
if
you're
in
you
know
this
time
zone.
If
this
is
time
zone
friendly.
For
you
choose
me
if
it's
if
you're
you
know,
apac
choose
this
one.
If
you
can't
find
a
time
that
works
for
you,
you
know
if
you
want
to
post
yours
first
and
then
use
mine
as
a
backup.
That's
fine,
too!
I'm
happy
to
facilitate
as
many
of
them
as
you
need
to,
though,.
B
Okay,
cool
yeah:
let
me
draft
something
up
and
I'll
just
send
it
sometime
today.
A
That's
great,
I
can
I'll
give
my
calendly
link
in
the
agenda
so
that
you
can
include
it
all
right.
Thank
you.
A
A
A
Cool,
I
didn't
have
much
as
far
as
like
major
topics
or
anything
but
coming
out
of
the
last
couple
meetings
where
we've
been
talking
about
longer
term
direction,
and
you
know
I
had
that
little
diagram
of
different
paths
we
might
take.
I
got
some
feedback
from
some
of
the
internal
stakeholders
and
other
people
that
are
that
happen
to
watch
that
when
I
post
it
to
the
ceo
channel,
I
think
it
has
my
gear,
spinning
and
also
it's.
I
think
it's
about
time.
A
We
do
a
proper
revisiting
of
the
of
our
user
journey
and
jobs
to
be
done.
Update
our
direction
page
a
little
more
holistically
and
I
think
user
story
mapping
can
be
really
helpful
for
that.
I've
never
done
it
distributed
across
so
many
time
zones
and
in
a
company
that
values
short
and
concise
meetings
like
I've
done
it
in
like
two
and
a
half
hour
time
blocks,
I've
done
it
in
multiple
sessions,
I'm
just
curious.
A
If
we
wanted
to
talk
about
maybe
the
best,
the
best
format
that
could
take
here
in
the
call
this
morning.
My
time
sean
suggested
I
just
take
over
one
of
the
social
calls
on
thursday
at
9
00
a.m,
eastern
and
that
would
at
least
it's
on
everybody's
calendar.
A
I
believe
that's
just
an
hour,
though
sometimes
these
things
can
go
long,
so
one
idea
I
had
was
trying
to
get
everybody
together
for
that
hour,
and
at
least
kick
it
off
kick
off
the
discussion
of
the
high
level
jobs
to
be
done,
user,
motivations
and
start
the
process
for
the
actual
story.
Mapping,
but
then
maybe
turn
it
over
afterwards
to
an
async.
A
Exercise
that
people
can
somehow
contribute
to
that
might
be
difficult,
because
not
everybody
has
figma
we'd
have
maybe
mural
would
be
better.
We
can
make
sure
everybody
has
an
account
on
mural
and
we
can
just
kind
of
whiteboard
on
there.
A
Maybe
we
could
assign
dris
for
different
I'm
just
this
is
all
off
the
top
of
my
head.
We
can
sign
dris
for
like
different
user
flows
like
you
know,
chad
go
kind
of
explore
what
you
know.
User
tasks
would
be
necessary
for
the
schedule
of
publish
schedule,
a
post
being
published
or
something
like
that,
and
then
we
would
regroup
for
feedback,
maybe
the
next
week,
or
something
like
that.
A
C
Sometimes,
if
I'm
going
to
lead
a
session
I'll
kind
of
prep
prep
the
thing
you
know,
I
think
I've
used
mural
often
and
they
have
a
couple
templates
for
it.
I'm
not
sure
if
you've
seen
it,
but
if
you
haven't,
then
I
can
look
for
it
and
put
it
in
the
agenda.
It'll.
D
C
Okay,
yeah,
so
then,
like
kind
of
setting
it
up
knowing
what
we
need
to
talk
about,
so
that
there's
not
as
much
you
know
like
the
the
five
to
ten
minutes
kind
of
getting
oriented
around
what
should
happen
and
then
doing
a
chunk
of
it
synchronously
and
finishing
asynchronously.
But
I
I
agree
with
you
as
much
synchronous
as
possible.
Here,
I
think,
usually
goes
better
because
sometimes
people
just
take
a
little
bit
longer
to
get
back
to
their
part
of
things.
C
A
That's
yeah
that's
helpful.
I
have
been
in
sessions
like
that
where
it
takes
a
while
to
get
started,
and
then
we
hit
the
ground
like
an
hour
and
20
minutes
in
and
we're
just
like,
okay.
Well
now,
let's
now
we
really
get
it.
A
Do
you
know
of
any
like
good,
primers
or
examples
that
we
can
I'm
sure
if
I
search
the
handbook,
there
might
be
an
example
of
how
gitlab
does
it,
but
like
a
this,
is
story,
mapping
and
the
goals
and
like
just
to
that
I
could
share
with
people
a
youtube,
video
or
something
a
resource,
that's
very
concise,
because
I
I
feel,
like
it's
hard
for
me
to
be
concise.
When
I
explain
at
the
upfront
of
the
story.
A
I
don't
think
it
needs
to
just
a
good
resource
to
outline
the
exercise
for
anybody
that
might
need
a
refresher.
A
Cool
I'll
I'll
do
some
searching
too
tomorrow
I
know
I've.
A
I
know
I
probably
have
in
my
history
in
my
browser
history
years
back
as
long
as
I
haven't
cleared
the
links
that
I
would
share,
but
they
were
more
like
blog
posts
and
they
were
not
necessarily
visual.
They
were
just
like
talking
about
story
mapping
in
general,
so
I
think
bite
size
that
we
can
do
just
as
a
little
bit
of
prep
work
before
the
meeting
would
be.
A
A
And
then
we'll
work
on
picking
which
social
call
to
do
it.
I
guess
it
would
probably
be
next
week
I'll
expand
the
agenda
for
that
one.
I
mean
not
the
agenda
the
invite
list.
So
catherine,
if
you
want
to
join-
or
you
know,
we
might
have
some
folks
from
the
doc
site
or
from
the
marketing
team.
I
know
eric
brinkman
wants
to
join.
A
A
So
user
story
mapping
should
be
fun.
The
only
other
thing
I
wanted
to
mention
is
just
to
bring
back
up
the
maturity
scorecard
exercise
now
that
we're
in
13.3
and
we're
close
to
making
this
available
to
to
the
product
in
the
product
pages,
we
will
probably
want
to
start
thinking
about
that
maturity
scorecard
process.
A
If
we
intend
to
get
the
right
amount
of
feedback
to
reach
our
quarterly
goal
of
getting
into
viable
maturity,
it's
probably
too
much
to
combine
the
research
that
we're
doing
with
an
interview,
but
we
might
be
able
to
use
similar
subjects
so
as
we're
recruiting
we
could.
We
could
keep
an
eye
out
for
the
people
that
are
most
excited
about
it
and,
possibly,
you
know,
hold
a
second
session.
That's
that's
the
the
it's
it's
a
brief
interview.
A
As
far
as
I
understand
for
for
to
go
from
minimal
to
viable,
there's
really
just
a
few
questions
that
we
need
to
answer
and
grade
ourselves
on,
so
it
should
be
like
a
15
minute
call
for
people
that
are
familiar
with
the
product
and
yeah.
I
think
the
the
point
I
was
trying
to
make
is:
maybe
we
can
use
the
same
interview,
sourcing
and
try
and
try
and
get
a
few
candidates
there
by
the
end
of
the.
B
Quarter,
yeah,
I'm
helping
out
the
source
group
team
with
some
category
maturity,
interviews
and
so
they're
kind
of
doing
so.
I'm
doing
that
just
to
understand
how
to
do
these
scorecard
things,
but
yeah
you're
right.
It's
just
like
one
or
two
questions,
and
it's
very
like
it's
something
that
we
could
even
distribute
to
other
team
members
to
help
out
where
it's
like
you
only
it's
it's
not
about
helping
or
even
like
a
normal
like
using
it.
You
feel
or
usability
study.
It's
very
like!
Please
do
this.
A
Time
was
it
easy
on
a
scale
of
zero
to
ten?
How
easy
was
it
that
kind
of
stuff
yeah?
I
think
we
collectively
need
to
get
clear
on
like
what
we're
grading
ourselves
on.
What
that
one
job
to
be
done
is
it's
making
it's
likely,
gonna,
be
just
making
it
edit
like
a
copy
change
to
a
a
pretty
basic
formatted
handbook
page,
but
then
having
them
go
all
the
way
through
the
process
to
create
the
mr
and
then
ask
them
a
few.
A
B
A
A
Thursday,
anyway,
with
jackie
the
pm
over
there-
and
we
talked
a
lot
about
the
potential
convergence
or
mind
share
of
git
lab
pages
and
how
that
might
overlap
with
our
static
site
editor.
If
we
choose
for
that
to
be
the
home
within
gitlab,
so
it
was
really
helpful.
There
was
a
recording-
I
don't
know
if
I
put
it
in
our
in
our
slack
channel,
but
I
will,
I
think
it's
on
our
playlist.
A
Let
me
pull
it
up.
That
was
that
was
really
helpful
to
hear
kind
of
her
thoughts
on
on
gitlab
pages
and
how
it
how
it
measures
up
in
the
market
with.
A
And
yeah,
I'm
I'm
enjoying
the
static
site,
editor
playlist,
although
if
there
was
a
day,
I
guess
it
was
thursday,
where
I
was
posting
so
much
on
there.
I
felt
a
little
bit
self-conscious
about
how
much
content
had
me
in
it,
but
that's
just
something
I
need
to
get
over.
D
A
C
Okay,
this
is
this
is
getting.
This
is
getting
interesting
now.