►
Description
Weekly sync call of the Static Site Editor group focused on product and design efforts
A
A
A
I
know
we
had
thought
about
like
coming
out
of
it
with
like
a
little
bit
of
a
design
exercise,
maybe
a
day
or
two
to
spend
thinking
through
further
the
job
to
be
done,
that
we
highlight
or
the
you
know,
potential
solution
that
came
from
the
discussion
and
I'm
not
sure
we
got
all
the
way
there
during
that
hour,
but
just
wanted
to
hear
your
take
on
it.
B
Yeah,
I
thought
it
was
good.
It
was
a
good
discussion
around
that
particular
job
to
be
done
of
linking
to
partials
or
other
content
that
may
exist
elsewhere
in
the
code
base,
so
kind
of
like
lookups,
and
things
like
that.
B
I
think
there
is
enough
there
to
kind
of
have
like
a
high
level
kind
of
like
big
blocks
like
today.
We
will
link
you
to
the
file
tomorrow.
You
can
just
do
everything
right
in
the
editor.
So
that's
why
I
was
actually
looking
to
see
if
there
was
an
issue
for
this
yesterday,
but
I
didn't
see
it
so
after
today,
I'll
create
like
a
an
issue
just
to
capture
that
conversation
and
like
pull
out
points
that
we've
discussed
and
then
decisions
and
then
probably
from
there.
C
B
On
the
high
level
things
it's
just
like
here's,
a
rough
diagram
of
like
what
that
might
look
like
moving
forward.
I
think
there's
there's
like
big
big
stepping
stones
that
we
talked
about
yeah,
nothing
super
concrete,
but
I
think
it
does
give
you
a
good
sense
of
like
the
potential
problem
spaces
that
we'll
have
and
and
like
what
we
might
do
as
rough
iterations
towards
solving
that
problem.
A
Yeah,
I
agree,
I
think
it
was
a.
It
was
a
helpful
and-
and
it
was
a
really
good
conversation.
I
liked
all
the
different
threads
of
thought.
I
was
just
looking
through
our
category
of
maturity,
ethics
and
I
could
have
sworn
that
I
made
at
least
a
placeholder
issue
for
using
reusable
content,
but
maybe
I
didn't
get
around
to
it
so
yeah,
please
feel
free
to
just
create
one
as
a
placeholder
and
start
putting
some
thoughts
in
there.
We
can.
A
B
A
There
we
go
yeah,
so
we'll
have
one
one
of
those
next
month
and
I
think
we'll
get
more
focused
and
more
disciplined
with
it
as
we
go
on.
I
think
the
format
was
fine
and,
and
everybody's
points
were
were
really
insightful,
so
I'm
I'm
happy
with
it.
I'm
glad
we
finally
got
to
do
it.
So
thanks
for
pushing
me
towards
it,.
A
I'm
gonna
highlight
my
two
product
points
on
the
agenda
now,
because
one
of
the
ux
research
ones
is
going
to
relate
to
it.
So
just
fyi
enrique
has
a
proof
of
concept.
A
If
you
didn't
see
it
in
slack
or
in
the
issue
for
using
ck
editor
5
as
a
wysiwyg
editor,
I
think
it's
down
to
this
one
and
tip
tap
as
as
potential
frameworks
to
go
with
I've
scheduled
a
call
with
the
ck
editor
team
who
are
based,
I
believe
they
said
in
poland
and
they
are
going
to
talk
us
through
some
of
their
licensing
and
they
have
a
in
my
opinion,
because
I'm
not
an
expert
on
licensing.
It's
a
slightly
complicated,
open
source,
slash
commercial
license
agreement.
A
I
want
to
see
how
we
fit
into
that
that
will
factor
into
our
decision.
So
it's
important
that
we
get
this
figured
out
now
and
I'm
great
I'm
grateful
that
they
were
quick
to
respond
to
my
inquiry
on
their
website,
because
13.6
would
be
a
great
milestone
to
circulate
our
for
our
final
proposal
for
feedback
and
potentially
start
at
least
making
a
plan,
if
not
starting
to
execute
on
the
plan.
A
For
the
first
steps
towards
implementing-
and
so
in
your
case
right
on
track
there
on
thursday
morning,
my
time
we'll
have
that
call-
I
have
enrique
and
john
joining.
I
didn't
want
to
overwhelm
the
team
with
too
many
get
lab
people,
but
I'll
make
sure
to
report
out
and
ask
if
I
can
record
it
in
case.
Anybody
else
is
interested
and
yeah.
So
the
that's
the
bulk
of
13.6
as
far
as
the
static
site
editor
is
concerned
and
the
rest
of
it
will
be
split
up
between
some
back-end
tasks:
offline
docs.
A
A
But
the
next
topic
is
settings
in
nav,
so
I've
been
spending
a
lot
of
time
working
through
all
the
issues,
existing
research
watching
some
recordings.
Although
there's
a
lot
more
for
me
to
to
process,
I've
been
trying
to
meet
with
people
that
have
been
involved
and
identifying
some
low-hanging
fruit
that
we
might
be
able
to
start
working
on
13-6.
I
think
getting
some
momentum
getting
people
familiar
with
that
area
of
the
code
base.
A
That
would
be
fantastic.
I
proposed
a
few
to
john
this.
This
morning
we
reviewed
those
one-on-one.
I
I
think
the
ones
I
picked
were
a
little
more
back
end
heavy
than
anticipated.
So
I
see
catherine,
you
have
a
comment.
B
A
With
a
list
which
is
fantastic,
so
I'll
review
that
that
could
help
a
lot.
C
B
C
Lot
of
what's
in
there,
depending
on
how
far
down
you're
going
because
I
know
originally
eric
brinkman-
was
saying
that
I
guess
a
static
site.
Editor
would
pick
up
priorities
one
to
three.
C
However,
as
I'm
kind
of
combing
through
the
issues,
what
I'm
seeing
is
that
the
left
side
navigation
is
actually
not
the
place
to
start
in
my
in
my
opinion,
because
a
lot
of
that
needs
to
be
researched
in
terms
of
establishing
the
baseline
for
changes,
the
one
area
that
I
would
say
is
like,
and
and
if
it's
not
needing
research,
it's
needing
design.
C
So
the
one
area
that
I
would
say
is
the
exception
to
that
with
the
left
side,
nav
would
be
the
issues
related
to
see
the
settings
like
enabling
and
disabling
features
in
the
left
side.
Now
those
would
are
what
I
would
say
are
the
exception,
because
I'm
not
sure
if
you
know
what
I'm
talking
about.
But
let
me
actually
okay,
you
know
what
I'm
talking
about.
A
Actually,
those
were
ones
that
I
I
had
called
out
as
potentially
good
options.
They
are,
I
think,
more
back
end
heavy,
so
I
think
in
my
mind
and
in
in
our
initial
discussions
we
had
been
allocating
a
lot
more
front
end
time
for
the
settings.
B
A
B
C
Yeah,
so
I
would
definitely
say
that
on
the
side
of
navigation,
unless
you
go
down
into
the,
I
guess
the
priority
number
four
on
that
epic
with
the
ui
cleanup.
So
basically,
I
wouldn't
really
think
of
the
priorities
as
a
linear
way
to
work
on
this
because
yeah
they
actually
have
more
the
way.
C
It's
not
nuanced,
but
I'm
going
to
use
more
new
ones
too
then,
and
a
lot
of
them
actually
need
to
be
reorganized
according
to
what
needs
to
be
researched
and
then
designed
and
then
developed,
but
like
michael
mentioned
below
settings
is
another
area
that
might
have
like
a
lot
more
ready
to
work
on
than
than
navigation,
like
just
in
general,.
B
C
Different
issues
and
bugs
that
were
serviced
around
settings.
There
are
a
lot
of
them
in
that
epic,
and
that
is
not
currently
underneath
the
prioritization
and
scope
epic
for
the
settings,
part
of
things.
So
it's
a
little
bit
disconnected.
C
B
A
That's
very
helpful.
I'm
definitely
on
board
with
the
left
side
nav.
A
A
Maybe
just
get
you
know
four
or
five
of
them
done,
or
should
we
hold
focus
on
static
site
editor
that
that'll
be
a
conversation
I
can
have
with
with
other
folks
this
week
and
then
the
ones
I
had
picked
out
at
a
high
level.
There
was
a
there
was
a
bug
that
felt
like
a
good
place
to
work
on,
but
actually
john
wasn't
able
to
reproduce
it.
So
it
pos
it's
possibly
fixed
already,
which
is
the
best
kind
of
bug,
but
it
doesn't
help
us
for
planning
13
6..
A
Then
there
was
the
there
was
one
related
to
that's
an
another
bug.
I
think
it's
on
priority
three
in
the
navigation,
which
is
just
like
something's,
not
working
right
like
frequently.
Oh,
that's
what
it
was
to
stop
using
local
storage
for
frequently
used
groups
and
make
it
persistent
across
your
user.
Account
seems
like
a
clear
win.
It
actually
doesn't
change
the
like
ui
as
much
as
it
does
just
like
consistent
experience,
so
it,
but
it
didn't,
seem
dramatic
enough
that
it
would
like
skew
measure.
A
And
then
yeah,
the
hiding
unused
sections
from
the
left.
Nav
was
a
candidate,
and
that
was
really
it
so
far
that
didn't
have
design.
There
was
another
one
that
I
wanted
to
talk
about,
that
the
the
global
search
team
or
advanced
search
team
is
working
on
being
able
to
search
settings
in
13
5.
C
All
right
yeah-
and
I
think
this
is
one
thing-
that's
tricky-
is
understanding
with
settings
and
with
nav
as
two
separate
efforts
which
one
like
are
they
being
considered
at
the
same
time?
Or
is
there
an
order
to
have
you'll
work
on
them,
but
they
both
like
have
their
own
long
list
of
considerations
and
research
needs
and
whatnot,
but
settings,
I
would
say
there
are
a
lot
more
bugs
and
things
that
can
be
immediately
fixed.
A
Cool,
so
we
can
yeah
it'll,
be
an
ongoing
discussion
this
week,
I'm
hoping
to
come
out.
Well,
we
have
kickoff
on
friday
for
13.5,
so
or
13.
6,
whatever
milestone
around
and
so
we've
got.
You
know,
have
something
queued
up
for
that
and
there's
plenty
of
work
to
be
done
on
the
stock
site
editor
and
the
handbook
and
the
docs
site.
A
So
whatever
is
ready
for
the
settings
in
nav
will
will
surface
this
week
and
and
then
just
make
room
for
it.
C
B
What
at
one
point
in
their
history
has
tried
to
attack
settings
because
it
was
a
blocker
to
either
discovery
or
usage
or
making
it
easy
for
people
to
use,
but
it's
always
been
kind
of
disgust,
because
it's
like
moving
something
really
big
there.
I
was
just
gonna,
watch
these
videos
and
take
some
notes,
but
I
decided
that
I'm
actually
going
to
just
watch
them
through
dovetail
highlight
all
the
key
points
and
then
synthesize
them
that
way.
B
And
then
this
way,
there's
insights
that
I'll
have
at
the
end
kind
of
like
kind
of
the
overall
findings.
And
then
it's
in
the
shareable
format
for
other
people
who
want
to
get
in
on
this.
But
don't
have
time
to
watch
like
20
or.
C
B
10
30
minute
calls
and
scan
through
everything,
so
I'm
planning
to
leverage
dovetail
to
transcribe
and
take
notes
and,
and
then
once
this
is
all
done
I'll
I'll
share
it
back
through
through
a
video
or
something
like
that
in
the
future.
A
A
I'm
getting
that
sense
too,
that
everybody
has
tackled
settings
and
now,
at
least
at
some
point
in
some
way-
and
I
think
that's
been
that's
still
the
biggest
unknown,
and
even
it
came
up
today,
like
somebody
had
a
proposal
for
a
change
now
that
we're
the
dri
it's
going
to
be
important
to
track
down
all
those
loose
threads
people
have
plans
those
ideas
that
they
think
they
can
you
they
can
implement,
that
that
are
blocking
their
work
or
that
would
make
their
feature
better
or
make
the
feature
more
visible
and
just
get
their
input
and
and
try
and
consolidate
everything
and
make
sure
it's
all
consistent.
C
Yeah
that
that
right
there,
I
think
part
of
that
might
need
to
be
addressed
and
I'm
not
sure
I'm
not
sure
where
I'm
not
sure
if
it's
in
the
product
handbook
or
in
the
design
system.
But
that
has
been
a
ongoing
problem
that
grows
in
woods.
So
I
think
we
actually
need
some
guidelines
and
some
type
of
checkpoint
for
when
something
is
added
to
these
things,
but
that
will
come
through
basically
research
and
design
as
well.
C
So
there's
actually
a
lot
to
unpack
with
both
of
these
areas,
but
it
will
be
unwrapped
but
yeah.
C
B
Point
I'll
go
ahead.
Rihanna
started
mr
to
create
an
area
in
the
pajamas
handbook
to
start
documenting
how
we
use
settings
and
things
like
that
as
a
baseline,
so
that
I
think
this
is
where
we'll
start
adding
more
stuff
to
back
it
up
with
research.
Like
you
know,
this
is
what
we
found
and
link
that
up
to
any
relevant
research,
but
yeah.
B
A
Yeah-
and
I
think
that's
that's
super
important-
I'm
glad
that's
already
in
progress
when
I
was
first
introduced
to
the
idea
of
taking
on
this
effort
and
was
reviewing
the
epics
at
least
for
the
settings.
That's
that
was
my
first
instinct
too,
which
which
was
well.
This
needs
to
be
approached
like
a
design
system
problem
like
this
or
the
solution
needs
to
be
based
around
a
design
system.
A
There
needs
to
be
a
predictable
pattern
for
others
to
implement
settings
so
that
there's
no,
you
know
we
don't
have
one
group
that
entirely
owns
everything
every
time
you
need
a
setting.
You
need
to
go
to
that
group.
That's
not
how
gitlab
works.
That's
not
an
efficient
way
to
work
on
something
of
this
scale,
but
we
do
need
guidelines
and
recommendations
and
design
patterns,
and
you
know,
engineering
patterns
code
patterns
that
we
can
follow.
C
Yeah
another
thing
to
consider
about
settings
not
to
make
the
scope
grow.
More
and
more
is
there
are
multiple
types
of
settings
and
the
same
will
go
for
navigation,
so
everything
does
the
one
like
the
project
level
left
sidebar.
You
need
to
be
kind
of
considered
for
the
group
level
and
what
settings
they're,
basically
for
there's,
project
group,
admin
and
personal,
so
they're,
just
I'm
not
sure,
what's
all
within
scope,
but
those
are
also
things
to
consider.
C
But
in
my
point
that
I
have
here
just
to
quickly
put
that
there
we
kind
of
touched
on
it
earlier,
but
that's
what
I
was
doing
with
that
sheet
is
basically
trying
to
go
through
what
we
actually
need
to
go.
Take
through
kind
of
ux
research,
because
we
do
have
a
a
new
handbook
page,
that's
around
the
metrics
that
we
want
to
track
for
improvements
to
navigation
and
settings.
C
So
that's
what
I've
linked
below
here
and
I've
created
ux
research
epics
for
the
left,
sidebar
and
settings
and
that's
where
I'll
be
adding
kind
of
the
relevant
research
issues
but
yeah,
that's
all
in
progress
figuring
out
how
to
basically
plan
it
all
out.
But
what's
hard
about
is
not
knowing
the
full
scope?
Yeah,
that's
that's
improv!.
A
Yeah,
we
can
definitely
dive
deeper
into
that
tomorrow.
During
our
meeting
we
can
record
it
for
the
rest
of
the
team
too.
If
they're
interested
and
yeah
I
mean
defining
that
scope
coming
to
an
understanding
of
what
is
the
most
important
thing
to
work
on
right
now
and.
A
A
C
A
It's
not
my
goal
as
much
as
that's
my
instinct.
Sometimes
it's
not
the
way
to
do
it.
There
may
be
a
day
for
I
should
say,
since
it's
being
recorded
for
posterity.
A
There
may
come
a
day
when
the
whole
ui
needs
to
be
refreshed,
and
we
need
to
just
you
know,
rip
it
off
like
a
band-aid
and
make
a
big
change.
That's
not
going
to
be
my
proposal
at
first,
at
least
not
yet
based
on
what
I.
A
B
So,
just
just
raising
that
we
have
like
one
more
session
tomorrow
and
I'll,
probably
synthesize,
every
the
four
sessions
there
then
I'll
ask
both
of
you
to
review
it
to
see.
If
we
need
more
other
areas
to
research,
I
think
they'll
probably
be,
and
I
think
that's
always
the
thing
of
research
like
in
the
brands
right
so
but
overall,
I
think.
C
C
B
Some
stuff,
we
can
probably
go
ahead
with
some
stuff
that
actually
most
stuff,
I
think,
seems
okay
right
now,
it's
not
as
drastic
as
last
time
when
people
had
no
clue
where
to
start,
and
so
I
think,
that's
an
improvement
but
yeah
so
look
forward
to
getting
a
ping
on
that
towards
the
end
of
the
week.
A
Yeah
excited
I
had
to
to
move
that
for
the
holiday,
but
I'm
looking
forward
to
having
that
session
tomorrow.
A
A
Something
that
we
we
should
work
on
next,
as
far
as
like
validation
and
getting
feedback
from
design
work.
As
we
finalize
our
editor
architecture,
it
might
be
a
good
chance
for
us
to
take
a
step
back
and
do
like
a
a
more
complete
vision
that
shows
all
the
feedback
and
input
that
you
have.
I
mean
you've
been
doing
this
a
little
bit
iteratively
with
the
new
editor,
and
it's
like
you
know,
takes
the
full
width,
and
but
you
know
when
we
have
a
an
editor,
that's
more
of
a
block
editor.
A
What
does
that
look
like?
How
does
that
bottom
bar?
If
that's
the
design
pattern
we
move
forward
with?
A
How
does
that
bottom
bar
fit
into
you
know
the
page
as
a
new
editor,
and
then
it
might
be
good
to
throw
in
some
forward-looking
things
in
there
about
front
matter,
editing
and
creating
new
pages
from
templates
and
things
like
that,
just
to
kind
of
solidify
our
thoughts
around
like
more
of
a
12-month
vision
than
take
that
and
make
sure
that
that
cohesively
makes
sense,
then
maybe
we
can
spin
off
from
there
and
do
more
iterative
validation
and
research
around
individual
parts
of
that
vision.
A
I'd
like
I,
don't
think
we're
going
to
do
a
think
big
on
settings
in
that,
or
at
least
I
don't
want
to
take
that
time
for
it.
If
we
do
it,
I
think
I'll.
Do
it
separate.
A
So
yeah
that
would
be
a
good,
would
be
a
good
discussion
to.
C
B
Oh
really
good
question,
catherine
thanks
for
that.
So
this
week,
and
probably
most
of
next
week
is
still
catching
up
on
things.
One
would
be
helpful
towards
the
later
half
of
next
week
would
probably
be
like
things
that
need
design
or
even
earlier,
so
that
I
can
start
addressing
some
of
those
so
that
we
can
start
solution,
validation
on
some
of
them
and.
C
B
That
kind
of
gets
that
ball
rolling
and
then
let
me
know
if
there's
anything
you
need
help
with
on
the
research
side.
Catherine,
I'm
happy
to
help
if
you
need
help,
but.
C
A
C
A
I'll
I'll
chat
I
I
spoke
with-
I
spoke
with
tim
today
and
so
I'll
reach
back
out
to
him.
I
should
have
asked
him.
B
A
But
yes,
I
will
create
one.
I
think
that
would
be
great
if
we
just
had
a
column
that
was
like
these
things
are
ready
for
design.
These
things
are,
you
know,
pending
research,
these
things
are
ready
for
dev.
Then
the
conversation
is
a
lot
easier
than
waiting
through
links
from
epic
descriptions
and
things
like
that.
C
A
Yeah
I'll
try
and
work
on
that.
We
can
talk
about
maybe
I'll,
try
and
have
a
draft
before
a
meeting
tomorrow
and
then
that'll
be
a
forcing
function
to
to
sift
through
all
the
issues
as
well.
A
Cool
well
thanks,
as
always
and
we'll
chat
soon
so
long
yeah.
You
have
a
good
night
to
all
of
our
viewers.