►
Description
Weekly sync call of the Static Site Editor group focused on product and design efforts
A
All
right,
hello,
everyone,
this
is
the
static
site,
editor
weekly
product
and
design,
sync
call,
and
it
is
september
28th
on
the
east
coast
of
the
us
september,
29th
in
australia,
where
michael
is,
but
I
think
actually
a
couple
of
our
topics
are
related.
Do
you
want
to
just
talk
about
your
first
question
in
the
product
section
of
the
agenda?
Michael.
B
Yeah
sure
so
one
of
the
things
that's
been
on
my
mind
is
that
now
that
we've
been
tackling
some
of
the
like
the
core,
you
know
flow
and
functionality,
interactions
with
the
static
site
editor
and
now
that
we're
in
the
handbook
it
looks
like
we
have
a
clear
path
there,
but
one
thing:
that's
a
little
bit
uncertain
for
me
is
like
thinking
beyond
that
or
thinking
big.
So
one
of
the
things
that
we
talked
about
a
couple
of
months
ago
was.
A
B
Another
think
big
session,
and
I
was
just
wondering
if
you
wanted
to
collaborate
on
that.
You
know
we
couldn't
like
bounce
ideas
off
each
other
and
something
like
that
and
yeah.
Maybe
you
could
verbalize
your
response
to
that.
A
Yeah-
and
I
think
we
must
have
had
a
very
similar
train
of
thought
right
before
this
meeting,
because
I
added
in
the
design
section
a
topic-
that's
generally
related,
but
so
my
answer
that
I
have
in
the
agenda,
but
also
my
my
take
on
that
is,
I
had
planned
on
creating
a
think,
big
brainstorming
session.
A
I
wanted
to
structure
it
more
like
like
journey
mapping
or
story
mapping,
and
then
I
got
bogged
down
on
trying
to
make
this
maybe
too
much
of
a
formal
process,
which
I
I
think
is
a
very
valuable
format
and
I
tried
to.
I
think
I
just
tried
to
do
too
much
prep,
and
so
there
would
always
be.
There
was
always
something
else
that
came
up
and
I'd
kick
the
can
and
try
and
get
to
it.
The
next
week
I
still
have
the
to-do
list
item
on
my
on
my
list.
A
I
was
wondering
if
you
thought
maybe
one
way
to
alleviate
that
aside
from
yes,
of
course,
I'd
like
to
collaborate
on
it,
but
what
if
we
did
it
monthly?
I
think
that's
probably
as
frequent
as
we
would
need
it,
but
just
like
a
maybe
a
monthly
everyone
that
can
attend
should
have
should
attend
brainstorming.
A
We
can
mix
up
the
structures
and
that's
where
we
could
collaborate
to
find
something,
that's
the
most
effective,
but
I
think
I
was
putting
too
much
like
importance
on
a
single
session
that
needed
to
do
everything
and
set
us
up
for
like
the
next
quarter
or
or
more
and
that
that
was
a
lot
of
it
felt
like
a
lot
of
pressure
to
not
like
you
know.
Anybody
was
imposing
that
on
me,
but,
as
I
looked
at
the
task
I
was
like.
Oh,
I
need
to
get
this
right.
A
B
I
think
that's
a
great
idea
because
I
think
if
we
do
it
monthly,
it
kind
of
aligns
well
with
our
cadence
of
milestones.
So
perhaps
it's
like
looking
at
like
the
next
milestone
and
beyond
or
like.
B
A
B
Will
be
a
good
goal
to
try
to
do
it?
I
know
that
you
have
other
responsibilities
and
other
things
of
planning
and
prepping.
So
that's
already
taking
up
a
lot
of
time.
Hence
I
think
you
know
maybe
collaborating
or
putting
the
pieces
together
together
or
like
collaboratively
as
a
group.
So
you
know
not
just
you
and
I,
but
also
john
and
our
other
engineering
and
team
members
could
like
collaborate
on
that
as
well.
So
I
think
maybe
asynchronously
get
all
the
doc
info
together
and
then
yeah
running
a
session
to
talk
about
it.
B
A
Yeah
generally
yeah,
when
we
do
the
issue
refinement,
if
we
could
push
it
in
by
a
half
an
hour,
I
should
be
home
by
then,
and
that
would
be
a
good
target.
I
would
like
to
you
bring
up
a
good
point
about
just
like
pm
responsibilities
and
monthly
cadence,
just
trying
to
follow
that
train
of
thought.
A
A
It's
relatively
quiet,
where
I'm
early
planning
for
the
next
milestone
the
issues
aren't
yet
like
needing.
Then
it's
not
necessarily
that
they're
fully
refined
but
they're
already
kind
of
themes
emerging
about
what
we
want
to
accomplish,
but
I
don't
necessarily
have
to
do
like
a
kickoff,
video
or
anything
yet.
A
A
A
good
morning
evening
for
you
or
night
for
you
yeah,
so
yeah,
maybe
let's
I'll
just
get
something
on
the
calendar
for
that
day.
And
then
we
can
collaborate
async
on
an
agenda
and
just
yeah,
throw
around
some
ideas
for
a
format
and
just
keep
it
to
like
a
an
hour
or
like
a
tight
50
minutes.
And
we
get
done
what
we
got
done.
But
it's
a
place
for
everybody
to
share.
A
B
Following
are
released
so
like
the
week
following,
like
the
22nd,
would
probably
be
the
best
time
for
the
regular
kind
of
thing
next
week.
I
think
the
6th
and
7th,
I
don't
know
what
the
exact
time
is,
but
the
jam
stack
conference
is
on
those
days.
So
I
don't
know
if.
B
Overlap
so,
like
me,
and
time
zones
are
like
disastrous,
because
I
said
because
I
like
I
live
in
a
weird
zone,
so
you
know
we
probably
just
need
to
double
check
against
that
one,
but
other
than
that.
I
think
it
should
be
fine.
I.
A
A
Okay,
I'll
take
a
look
at
that,
and
jamestack
is
that's
right.
I
only
I
didn't
sign
up
for
any
of
the
paid
sessions,
but
I'm
going
to
be
doing
the
day,
one
which
is
tuesday,
I
believe,
let's
see
yeah
so
tuesday,
so
wednesday.
The
seventh
when
I
had
when
I
was
thinking
it's
possible
that
some
of
our
team
signed
up
for
those
so
I'll
double
check
so
yeah.
A
I
think
that
sounds
good
and
segways
well
into
the
question
that
I
had,
which
is
what
are
your
thoughts
on
as
a
design
exercise
or
just
as
a
maybe
input
or
output
of
these
think
big
sessions,
doing
some
kind
of
vision,
mock-up
or
mapping
out
some
potential
journey
to
highlight
where
we
would
want
to
be
in
in
a
year,
I'm
not
inclined
to
ask
for
like
super
high
fidelity
or
like
clickable
prototypes
or
anything,
because
I
think
that
can
get
in
the
way
of
iterative
releases,
and
we
can
end
up
committing
to
something
that
you
know.
A
After
a
few
iterations,
we
actually
want
to
go
in
a
different
direction.
So
I
understand
the
the
risks
in
like
high
fidelity
vision
work,
but
I
do
think
it
would
be
helpful
to
to
be
able
to
share
visually,
what's
in
our
mind,
rather
than
you
know,
pointing
to
the
direction
page
which
can
be
wordy
or
showing
three
or
four
different
ethics
that
might
have.
You
know
various
levels
of
design
work
done.
B
A
I
think
that's
a
really
good
idea.
That's
yeah!
That's
really
interesting!
Actually
I
I
put
together
that
they
were
related,
but
having
that
as
like
a
like
an
output
of
the
think
big
session,
where
you
could
take
what
were
what
we
just
talked
about,
what
you
have
in
your
head
and
what
we've
talked
about
before
and
time
box
it
a
little
bit
and
make
it
so
it's
not
quite
so
precious
and
not
so
much
a
vision,
artifact
but
like
this
is
how
this
is
like.
A
I'm
illustrating
one
potential
flow
through
things
and
it's
very
forward-looking,
so
you
don't
need
to
like
go
through
and
make
sure
every
like
ui
pattern
matches
what
it
is
today.
It
could
be
like
well,
let's
think
about
something
over
here
or
let's
pretend
we're
using
a
different
type
of
menu
here,
that
that
could
be
a
little
freeing,
but
also
prevent
us
from
getting
too
deep
into
it,
and
spending
like
a
month
on
something.
B
A
Lot:
okay,
cool
well
yeah,
let's
keep
working
on
a
format
and
maybe
open
an
issue
for
the
think
big
session,
and
we
can
just
work
on
the
format
in
that
and
that
can
be
the
outcome
or
sort
of
like
an
exercise
outcome
yeah.
A
I
I
would
say
for
anybody
watching
this
on
the
team
on
the
engineering
side
also
from
there.
If
there
were
like
little
proof
of
concept,
engineering
challenges
that
came
up
where
you're
like.
Oh,
I
wonder
if
we
could
do
that
and
it
didn't
take
like
you
know
a
week
to
do
or
you
did
it.
You
know,
I'm
not
gonna
encourage
anybody
to
work
overtime,
but
you
know
what
I
mean
like
you.
You
did
it
on
your
own,
while
you're
waiting
for
a
merge
train
or
something
like
that.
A
So
you
have
45
minutes,
you
can
mock
something
up
and
build
a
little
quick
proof
of
concept.
Then
that
would
be
a
great
output
as
well.
A
Something
like
you
know,
just
in
a
snippet
or
like
a
you
know,
a
single
bit
of
code
that
you
could
run
and
demo
a
feature
that
would
be
really
awesome
cool.
Well,
I'm
excited
about
that.
Thanks
for
bringing
that
up,
because
I
was
feeling
guilty
that
I
never
scheduled
the
think
big
session
and
I
looking
back
it's
as
we've
talked
about
in
various
meetings
and
retros.
A
B
So
this
week
we're
kicking
off
solution,
validation
for
associating
changes
to
existing.
Mr,
so
we
have,
I
think,
four
of
the
five
sessions
booked
and
confirmed,
so
that's
good
so
happy
to
get
that
going
and
then
the
other
thing
that
I
want
to
talk
about
is
up
on.
The
radar
for
13.6
is
a
problem
validation
around
editing
beyond
the
handbook
and
like
where
do?
Where
else
do
we
take
this
or
what
other
areas?
B
The
reason
I
bring
this
up
is
because
it's
on
catherine's,
like
radar
for
13.6,
that
she's,
probably
gonna,
allocate
some
time
for
it.
Should
we
revisit
this
after
our
session
next
week
and
say
I
think
that
might
make
more
sense.
If
we
are
thinking
of
doing,
I
think
big
session
next
week,
then
perhaps
we
put
off
this
for
13.6
or,
like
we'll
like,
add
the
details
of
what
we
want
to
do
next
week
for
this.
A
B
A
Yeah,
I
agree,
and
I
think
maybe,
if
anything's
changed,
I
would
shift
this
research
more
to
editing
opportunities
based
on
the
input
that
we're
getting
from
the
new
editor
architecture
than
I
would
any
kind
of
like
distinction
between
cms
and
like
how
we
integrate
with
live,
editing
versus
cms,
or
something
like
that,
because
I'm
looking
at
the
issue
now
and
I'm
remembering
sort
of
the
mindset
that
we
were
in
when
when
we
were
planning
this
one,
and
I
would
say
that
one
of
the
more
exciting
aspects
of
the
architecture
that
enrique
has
presented
as
the
potential
to
use
it
elsewhere
in
the
gitlab
ui
elsewhere
in
in
the
product.
A
As
a
wysiwyg,
editor
and
understanding
the
opportunities
there
would
be
really
beneficial
for
communicating
outward
to
the
other
groups
and
as
well
as
just
like,
aligning
ours
on
like
on
the
real
problems
that
people
face
when
they're
editing
markdown
in
like
an
issue
description
or
something
like
that,
and
I
think
that
that
could
then
follow
into
like
okay.
Well
now
we
have
this
editor.
A
How
do
you
get
there
and
what
are
the
other
aspects
of
like
a
cms
versus
live
page
and
we
can
start
evaluating
it
against
the
feedback
that
we're
getting
from
the
netlify
cms
on
the
marketing
team,
but
anyway?
Yes,
I,
I
think
revisiting
this
and
tightening
it
up
for
13.6,
based
on
the
output
of
that
think
big
session
and
the
continued
you
know,
wrapping
up
of
our
architectural
exploration
sounds
good
to
me.
A
A
I
am
planning
some
pto
at
the
end
of
the
month
at
the
end
of
the
well
beginning
of
october,
at
the
end
of
this
week,
so
just
fyi
and
there
shouldn't
be
anything
like.
I
said
this
is
sort
of
our
lull
in
the
product
release
cycle.
So
that's
good
yeah
everything's
going
fairly
well,
I'm
very
excited
about
the
progress
already
on
some
of
the
commitments
we
have
for
our
13.5
deliverables
and
youtube.
A
Videos
are
you
know,
there's
already
an
mr
it's
good
to
have
jacques
back
working
on
that
and
derek's
already
got
some
stuff
in
reviews
and
and
he's
working
already
on
the
title
and
description
workflow.
So
it's
great
it's
only
the
28th.
A
Cool
all
right,
well,
yeah
sounds
great.
I'm
gonna
wrap
the
recording.