►
Description
Weekly sync call of the Static Site Editor group focused on product and design efforts
A
Hello,
everyone-
this
is
the
static
site,
editor
product
and
design
focus
weekly
meeting
shifted
by
a
day
because
I
was
off
yesterday.
This
is
october
6th
and
we'll
jump
right
into
what
we
were
just
chatting
about,
which
is
some
takeaways
from
the
jams.conf,
the
virtualjams.com
today
or
at
least
day
one.
There
are
workshops
tomorrow
and
chad.
You
were
talking
about
the
performance
talk,
I
don't
know
if
you
want
to
repeat
any
of
that,
but
it
did
sound
very
interesting.
I
didn't
get
to
attend
that.
One
though.
B
No,
I
just,
I
think,
it's
a
good
little
reference
in
general
for
everything
just
virtual
nowadays,
so
this
one
is
a
fun
the
the
visual
perform
where
the
visual
testing
talk
was
really
interesting.
The
things
that
applify,
I
think
was
in
the
company.
The
things
they
can
do
are
pretty
amazing
and
she's.
A
really
engaging
speaker
too.
B
A
Always
helps
yeah.
Let's
see
I
I
did
get
to
sit
through
one.
That
was
interesting
about
the
way
I
think
it
was
teespring
had.
A
Had
architected
themselves
around
a
bunch
of
microservices
and
medium-sized
services,
they
were
talking
about
sort
of
the
scale
at
which
they
were
building
that,
and
so
I
do
recommend
that
it
was
only
slightly
over
my
head
as
far
as
the
actual
architecture
they
built,
but
it
was.
It
was
interesting
to
hear
them
present
that
and
and
talk
about
how
they
came
to
that.
Like
conclusion,.
A
I
know
they
were
all
recorded
too.
I
hope
to
go
back
and
catch
up.
I
did
get
sidetracked
in
the
afternoon
and
wasn't
able
to
watch
as
many
as
I
wanted
to,
but
I'm
looking
forward
to
catching
up,
and
maybe
we
can
have
a
slack
channel
or
something
where
we
or
I
guess,
just
in
our
social
channel
or
really
any
of
our
statics
editor
channels
would
be
appropriate
to
post
these
takeaways
as
we
catch
up.
B
On
they
had
a
thread
going
in
the
quality
channel,
I
think
cool,
cool
or.
A
Yeah
overall,
I
thought
it
was
yeah.
It
was
well
organized
and
put
on
smoothly.
I
think
they
addressed
at
the
beginning.
They
took
a
little
bit
of
the
feedback
from
their
other
one
earlier
in
the
year
and
made
things
a
little
more
focused
and
shorter.
A
That
and
that
helped
a
lot
yeah
I
mean,
I
think
it's
it's
always
interesting
and
as
we
catch
up,
I'm
sure
we
can
talk
more
about
any
other
key
takeaways.
B
There
was
between,
I
think,
that
the
guy
who
owns
or
runs
wordpress
and
one
of
the,
I
think,
the
main
people
from
netlify
and
it
wasn't
fluff
like
they've
kind
of
got
into
it.
So
there
was
a,
I
think
they
didn't
let
them
bash
php,
which
was
really
interesting.
So
they
definitely
everything
else
was
on
the
table
and
they
got
into
it
and
the
moderator
was
really
good
yeah.
It's.
A
A
Let's
see
here,
let's
start
with
ux
research
today
I
think
I
don't
know
if
catherine
or
michael
put
this
one
in,
but
we
can
talk
about
the
solution,
validation
for
that's
that's
ongoing.
C
Yeah
so
I'll
I
put
that
one
down
so
that's
started
last
week
ran
three
sessions
so
far
and
so
far
it's
good.
I
just
realized
that
the
one
participant
I
was
waiting
upon
for
feedback
no
longer
works
at
get
lab.
So
that's
I
probably
need
to
find
another
person
to
fill
in
their
shoes.
C
If
you
know
of
anyone,
let
me
know
otherwise
I'll
just
ask
product
marketing
or
sales,
probably
sales
or
yeah,
or
if
you
know,
if
any
other
groups,
I
should
ask
because
we've
been
pretty
product
marketing
heavy
so
far,
so
yeah,
that's
that's
ongoing.
I
think
there's
one
more
session
scheduled
next
week
and
you're
you're
handling
that
one
eric
for
me
and
for
us
I
mean
and
so
yeah.
A
B
B
B
A
But
yeah
looking
forward
to
running
that,
and
I
can't
think
of
any
individual
in
particular.
But
if
I
you
know
come
up
with
something
before
tomorrow
morning,
I'll
ping,
you
in
slack
on
on
somebody
to
reach
out
to
otherwise.
I
think.
A
Reaching
out
to
sales
would
probably
be
good
because,
like
you
said,
product
marketing
is
has
been
participating,
maybe
disproportionately
it's
great.
We
want
their
feedback,
but
might
be
good
for
variety.
A
A
A
I
did
not
get
you
an
agenda
until
a
few
hours
ago,
and
that
was
two
lines
in
a
dock.
So,
let's
we
can
just
talk
about
how
we
think
that
should
go,
and
my
only
idea
was
just
putting
out
like
one
major
opportunity
or
job
to
be
done,
or
some
kind
of
you
know
prompt
and
then
letting
us
discuss
in
depth
just
without
too
many
constraints
around
it.
A
A
I
think
what
was
holding
me
back
from
scheduling
these
before
is
getting
too
hung
up
on,
like
formal
formalized
processes
and
terms
and
stuff
and
journey
mapping
and
story,
boarding
and
stuff
like
that.
So
if
we,
if
we
abstract
it
a
little
bit,
I
don't
know
that
we
really
even
need
to
talk
about
jobs
to
be
done
in
the
sense
that,
like
this
is
the
format,
and
this
is
what
a
job
should
be
done
is,
if
we
just
say,
like
users
need
to
be
able
to
do
this.
A
How?
How
does
that
look
in
gitlab?
Not
necessarily
you
know,
how
do
we
solve
for
x,
y
and
z
in
the
static
site
editor,
because
we
know
it's
on
our
backlog,
but
if
we
just
say,
users
need
to
be
able
to
create
and
use
content
in
multiple
places
create
reusable
content
that
can
be
inserted
in
their
pages
and
that's
the
job
to
be
done.
Then
we
can
just
have
a
discussion
around
that
and
brainstorm.
C
Yeah,
so
I
think,
for
the
sake
of
time
and
like
a
lead
up
for
this
session,
I
think
that's
a
good
idea
to
like
have
one
pre-selected
in
the
future.
We'll
probably
should
do
some
kind
of
voting
across
the
group
just
to
see
just
to
gauge
everyone's
understanding
of
where
they
think
the
problem
space
is
and
then
have
a
discussion
around
that
then
to
focus
on
certain
areas
but
yeah.
I
think
where
we're
at
right
now.
C
I
think,
for
the
sake
of
discussion
and
getting
the
ball
moving,
focusing
on
one
area
and.
C
Partials,
it
includes
is
one
one
area
like
it's
almost.
D
C
The
job
to
be
done
is
like
get
me
to
what
I
need
to
edit
and
it's
like
the
bigger
job
to
be
done,
and
that
opens
up
another
can
of
worms.
As
in
like
oh
accessing
the
stack
site
editor
from
the
handbook,
is
it
clear
enough?
Do
we
need
to
add
another
icon
in
there
to
the
pop-up
that
chad
added
a
few
months
ago
like
do
we
need
to
do
that?
Do
we
need
to
add
stuff
in
the
bottom?
Do
we
need
to
kill
the
links
at
the
bottom?
C
B
C
Kind
of
give
us
some
more
structures
and
words
so
that
we
have
something
to
run
off
for
the.
A
C
In
tonight's
session
or
today's
whatever
tomorrow
session
and
yeah,
we
should
just
get
started
and
then
we'll
learn
what
works
and
what
doesn't
and
then
we'll
carry
on
from
there.
I
haven't
done,
I
think,
big
section,
so
maybe
cat
maybe
do
you
have
any
like
insights
or
guidance
on
what
we
should
do
in
this
scenario,
because
you
probably
attended
more
think
bigs
than
I
have.
D
I
haven't,
I
haven't
attempted
any,
but
I
think
what
I'm
hearing
makes
sense.
D
I
think
there's
as
long
as
you
have
a
goal
to
orient
a
room
that
should
do
it
like,
for
example,
if
the
goal
is
to
come
up
with
things
for
a
road
map
or
if
the
goal
is
to
identify
areas
for
improvement
like
if
there's
just
some
kind
of
overarching
goal
that
you
can
land
on
at
the
end
and
say:
okay,
these
are
the
action
items
we'll
take
toward
this
goal.
I
think
that
would
help,
but
otherwise
I'm
not
really
sure
how
people
run
them
so
far.
D
C
D
A
Yeah,
I
agree,
and
for
the
record
I
just
added
you,
it
might
be
a
little
early
for
you,
catherine,
but
I
just
added
you
as
optional
for
tomorrow.
Sorry,
I
didn't
put
you
I
should
just
by
default.
Include
you
we're
gonna,
try
and
do
these
monthly,
though
so,
if
you
can't
make
it
tomorrow,
please
join
the
next
one.
A
You're
always
welcome.
I
I
think
the
outcomes
for
me
is
probably
closer
to
the,
like.
You
know,
backlog
issue,
creation,
populating
a
backlog
of
these
ideas,
so
that
we
can
start
to
formulate
them
into
more
clear
issues
and
then
you
know,
take
them
and
get
them
through
the
design
process
and
validation
and
everything.
A
So
I
think
with
that
goal
in
mind,
even
if
it's
just
our
first
stab
at
it
and
only
a
couple
concrete
issues
come
from
it.
I
think
that
would
still
be
a
success
and,
to
your
point
earlier,
michael
about
getting
a
shared
understanding
of
like
the
problem
space.
A
I
think
that's
definitely
one
that
we
should
plan
for,
and
one
that
I
had
hoped
would
you
know
be
our
first
one
and
and
would
what
was
the
stumbling
block
for
me-
was
trying
to
wrap
my
head
around
how
we
were
going
to
do
that
in
a
timely
manner,
but
having
a
way
to
do
a
sort
of
a
macro
level
problem.
Space
brainstorm
would
be
a
great
candidate
for
for
one
later
on,
when
we
have
a
little
more
time
to
plan.
A
D
Oh
apparently,
there's
a
handbook
page
on
think
of
aids,
think
big
sessions
and
from
what
I
see
they
suggest
doing
like
research
review,
epic
review.
So
basically,
you
know
there's
the
goal
of
getting
on
the
same
page
about
the
the
goals
and
kind
of
your
purpose.
Your
stage
stage
group
vision,
but
then
there
are
also
things
you've,
probably
already
learned
from
research,
especially
a
lot
of
the
solution
validation.
D
So
I
think
those
would
be
things
to
discuss
as
well
so
like
from
the
research
you
already
conducted,
what
were
some
recurring
things
that
have
come
up
or
what's
what
are
some
things
that
are
unfinished
in
terms
of
the
flow
things
we
can
iterate
on?
I
think
those
also
have
places
to
be
big
but
I'll
link
this
random
page
that
I
found
about
it.
Maybe
you've
seen
it
already.
I
can't
say.
A
I
just
yeah,
I
just
put
it.
I
found
that
today
by
accident
and
I
was
working
on
a
different
area
of
the
handbook
and
I
saw
it
and
yeah
it's
slightly
different
approach
than
than
I
think
we
were
planning
voted.
I
think
we're
pretty
close.
A
For
the,
for
the
sake
of
time,
we
should
address
that
the
static
site
editor
is
going
to
be
assuming
the
responsibilities
for
for
taking
work
on
the
settings,
the
gitlab
settings
and
global
navigation
secondary
navigation
and
breadcrumbs,
and
just
generally
improving
the
user
experience
are
in
there.
We
will
be
balancing
the
work
against
our
existing
roadmap
for
the
static
site
editor,
so
we'll
continue
to
be
working
on
that
as
well.
I
can
yeah
michael.
A
Specific
question
around
that
work
in
in
the
design
section,
or
did
you
just
want
to
address
it.
C
Yeah-
and
it's
just
more
like
this-
is
what's
on
track,
it's
just
absorbing
and
like
meeting
with
people,
and
you
know
just
just
absorbing
until
we
need
to
like
start
making
moves.
At
least
I
know.
B
C
I'm
coming
in
from
and
cat
helped
up
with
understanding
the
past
research,
so
I
hope
I'm
going
to
upload
that
to
youtube
later
and
share
it
with
the
group.
A
Excellent
that
would
be
helpful.
Thank
you.
Yeah,
I'm
digging
into
poorly
timed
vacation,
so
I'll
feel
a
little
behind
already,
but
I'm
digging
in
and
I
think
the
the
the
best
approach
would
probably
be
to
schedule
a
separate,
maybe
weekly
or
bi-weekly
sync,
so
that
we're
not
trying
to
accomplish
too
many
things
with
one
weekly
stand-up
but
I'll.
Think
through
the
format
on
that,
and
we
can
talk
about
it
in
slack
and
whatnot.
A
But
chad,
you
had
a
follow-up
in
the
ux
research
about
this.
So
did
you
wanna.
B
Sure
yeah
the
I
showed
up
at
the
research
hours
last
week
and
jeff
and
catherine
were
there,
and
it
was
a
really
good
talk.
We
started
on
the
settings
and
nav
stuff,
but
we
got
into
lots
of
other
things.
Catherine
schroeder
fascinating
the
history
of
the
evolution
of
the
get
lab
navigations.
D
Yeah-
and
I
don't
know
eric
how
much
context
do
you
have
around
everything,
but
one
thing
that
I
think
all
of
us
are
kind
of
wondering
is:
what's
the
the
continuum
like
there's
the
epic
that
contains
like
the
priorities,
but
it's
like
where
what's
the
box,
not
the
time
box,
you
know
what
I
mean
it.
It
kind
of
seems
like
it
could
be
a
huge
project
that
goes
on
forever
or
it
could
be
a
very
short-term
goal.
I
think
that
has
been
one
of
the
biggest
questions
that
I
yeah
see
in
the.
A
We
did
we
did
and-
and
it's
one
I'm
hoping
to
get
answers
for
soon.
I
think
we're
partially
or
I
am
partially
dri
for
making
that
decision
and
determining
that.
I
will
obviously
be
asking
for
input
and
absorbing
all
this
existing
research.
So
I
can
form
that
opinion.
I
think
the
like
the
political,
like
turn
it
back
around
on
you
non-answer
would
be.
It
is
something
that
we're
always
going
to
be
working
on.
We
being
gitlab
should
never
just
like
we're.
A
C
A
We
as
a
team,
the
static
site
editor
group,
will
help
to
find
some
clear
iterative
releases
that
we
can
achieve
based
on
research.
That
we
think
will
like
will
result
in
measurable
outcomes.
But
I
I
don't
think
right
now,
there's
a
a
tendency
to
revamp.
A
And
do
a
broad
sweeping
change
to
the
navigation,
although
that's
my
like
instinct
as
a
former
designer
and
and
I
I
would
just
want
to
start
over
and
and
rethink
everything.
I
don't
think.
That's
the
best
approach
right
now
and
I
need
to
dig
through
the
existing
issues
a
little
more
and
the
research
and
get
a
get
a
better
sense,
but
you'll
be
able
to
help
me
there
and,
as
I
dig
in
I'll,
certainly
let
you
know
in
slack
or
in
the
issues.
If
I
have
any
questions.
A
A
Do
they
get
in
the
way
of
this
baseline
measurement
at
all,
and
and
how
quickly
can
we
get
that
baseline
measurement
in
place
and
then
how
quickly
can
we
get
additional
research
where
necessary
to
to
fill
out
fill
in
the
gaps
on
the
issues
that
might
be
a
little
more
less
lined.
D
Yeah,
yes,
I'm
happy
to
talk
with
you
about
it
whenever
you're
kind
of
in
in
the
froze
of
it,
because
there
is
a
lot
there,
it
takes
a
lot.
It
has
haunted
me
for
years.
A
D
A
There
are,
there
are
no.
I
have
about
eight
people
that
I
need
to
to
schedule.
Coffee,
chats
and
you're
on
the
list
to
to
kind
of
catch
up
and
and
figure
out
like
what's
been,
what's
already
been
accomplished,
where
do
they?
Where
do
these
people
think
we
should
be
focusing
on
our
efforts
and
then
I'll,
try
and
just
synthesize
that
so
expect
an
invite.
A
And
just
for
the
record,
we
have
a
an
mr
out
now
for
updating
the
direction
page
so
that
we
are
formally
the
dri.
The
group
is
formerly
the
dri,
so.
C
A
And
nothing
else
on
the
agenda
anything
anybody
else
wants
to
add
before
I
stop
the
recording.