►
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
product
design,
ux
sync
call
for
november
16th
and,
as
we
discussed
in
the
earlier
engineering
call,
our
group
is
being
merged
with
the
editor
group,
which
means
there's
no
more
static
site.
Editor
group
to
have
a
weekly
call.
So
this
will
be
our
our
final
weekly
sync,
but,
as
we
were
discussing
before,
I
hit
record
we'll
be
setting
up
a
nearly
identical
ux
product
and
design.
A
I
brought
this
up
on
the
earlier
call.
Michael,
I
saw
you
dropped
it
in
the
product
section.
I
was
talking
to
marcel
about
the
same
thing:
the
hackathon
that's
coming
up.
I
think
it's
a
great
opportunity
for
finding
some
either
quick,
wins
or-
or
you
know,
medium-sized
isolated
chunks
of
work
that
people
might
want
to
pick
up
for
the
hackathon
that
wouldn't
necessarily
disrupt
any
of
the
ongoing
research
or
or
ideas
that
you
have.
A
The
only
one
I
had
come
across
so
far
had
been
the
one
related
to
your
keyboard
shortcuts
menu,
which
I
thought
would
be
a
great
improvement,
but
one
that
we're
not
likely
to
pick
up
in
the
next
six
to
nine
months.
Given
the
bigger
areas
of
focus
that
we
have
on
our
plate,
I
haven't
gone
back
through
our
list
of
180
issues
or
whatever.
B
A
A
Yeah,
I
think
that's
that's
a
good
plan
and
I
guess
that's
another
thing
I
need
to
consider
before
I
label
these
ready
for
hackathon
is
how
much
work
we'd
have
to
put
in
refinement
and
and
breaking
up
any
issues
that
I
identify.
We
don't
want
to
overload
ourselves
with
admin
work
while
we're
trying
to
get
all
this
other
work
done,
but
it's
all
necessary.
So
we'll
we'll
get
the
right
number
of
issues
identified
and
refined.
A
B
A
But
otherwise
I
don't
so
I
don't
have
a
lot
on
the
agenda.
My
updates
are.
I
will
be
continuing
to
refine
issues
and
organize
our
settings
and
nav
issues
under
that
category,
epic,
that
I
created
and
referenced
last
week.
I
think
that's
probably
my
top
priority
this
week
outside
of
the
other
admin
type
product
things
I
need
to
do
getting
ready
for
kickoff,
so
recording
the
kickoff
video
tonight
we
did
some
planning
for
the
editor
group
13.7
planning.
A
A
I
clearly
didn't
get
to
my
computer
in
time
to
make
these
notes
in
the
agenda.
So
I'm
going
off
the
top
of
my
head,
the
one
that
we
could
go
over
is
I'd
like
to
carve
out
some
time
in
13.7
for
technical
review
of
the
ability
to
search
in
settings-
and
I
know
you're
you're
currently
doing
some
solution,
validation
and
design
work
and
I'd
like
to
in
parallel
get
them
some
dedicated
time
to
review
what
you're
working
on
work
with
you.
A
B
Thanks
thanks
for
that
on
my
list,
I
guess
there's,
like
the
user
menu
thing
that
that
issue
that
I
found
it's
listed
under
like
the
navigation
work,
but
it
feels
like
there's
some
quick
wins
there
like
whether
we
do
them
or
not.
I
feel
like
there's
an
opportunity
here
kind
of
like
the
keyboard
shortcuts,
where
we
could
list
out
what
needs
to
be
done
and
whether
we
take
it
up.
B
You
know
if
we
have
bandwidth
or
we
offload
it
to
someone
else,
but
this
is
definitely
one
where
we
can't
just
send
it
to
another
group,
because
the
user
menu
is
kind
of
in
that
limbo
of,
like
the
whole
team,
really
owns
it,
which
means
it
falls
on
us
if
we
want
to
action
on
it,
so
whether
we
submit
it
for
hackathon
or
we
do
it
ourselves.
That's
at
least.
C
B
A
Problem,
I
and
I
agree
that
that
user
menu
is
probably
a
nice
little
isolated
corner
of
our
domain,
that
we
can
start
iterating
on
pretty
quick,
so
yeah
feel
free
to
start
thinking
about
how
you
would
realign
those.
I
know
this
issue
you
linked
in
the
profile.
Has
some
suggestions
you
can,
you
know,
build
on
those
and
see
what
you
think
is
is
right.
C
B
The
dark,
the
toggling
of
dark
mode,
was
something
that
kind
of
connected
me
to
this
user
menu
issue.
So
they're
very
they're,
related
very
closely,
as
in
engineer
proposed
a
change
to
add
a
toggle
to
toggle
or
dark
mode
on
and
off.
But
then
it
opened
up.
This
can
of
worms
from
my
side
to
say:
hey
a
lot
of
this
stuff
in
the
user.
Menu
is
kind
of
messed
up,
but
then
I
then.
B
C
C
I
think
it's
my
turn,
so
my
update
is
that
I'm
working
on
testing
scripts
for
the
benchmarking
studies,
so
there
are
going
to
be.
I
think
four.
So
one
is
around
the
top
nav
bar,
which
is
what
I'm
using
is
kind
of
like
a
shorthand.
But
it's
basically
going
to
be
like
a
study
around
wayfinding
and
moving
between
levels
and
kind
of
interacting
with
items
in
the
top
navbar
and
then
there's
one
that's
going
to
be
around
project
and
group
settings.
C
This
one
was
a
little
bit
tricky
because
I
was
like
I
don't
know.
If
I
should
just
do
projects
or
group,
I'm
not
sure
yet,
but
that
is
also
going
to
be
another
usability
testing
study,
which
is
basically
giving
them
different
tasks.
That
would
lead
them
to
finding
certain
settings
and
seeing
how
they
kind
of
navigate
their
expectations
around
where
a
setting
would
be
and
have
some
like
upfront
questions
as
well
to
explore
that
topic.
C
So
if
you
have
any
research
questions
related
to
these
areas,
that
you
think
would
make
sense
to
include
in
the
study
feel
free
to
put
them
in
the
agenda
or
comment
in
the
issue.
If
anything
comes
to
mind,
even
things
you're
just
curious
about,
and
then,
if
there's
any
usage
data
available,
let
me
know
I
don't
necessarily
think
there
will
be.
I
think
the
top
navbar
more
button
was
like
just
implemented
or
something,
but
if
you
know
of
any
that
would
have
helped
with
identifying
tasks
to
include
in
testing
as
well
so
yeah.
B
C
So
I
will
say,
findability
rate
is
probably
the
one
that
will
be
most
relevant
when
we're
comparing
between
the
existing
and
the
proposal.
So
if
it
takes
well
one
if
they're
able
to
find
it
more
in
the
proposal,
that's
great,
but
also
it
could
also
be
that
it
takes
less
time
to
find
it,
which
would
also
be
pretty
cool.
C
First
click
testing,
I
think,
would
help
more
around
the
mental
model,
so
understanding
where
people
are
thinking
to
go
first,
even
if
they
change
their
answer,
and
they
find
it
later
on
like
what
was
that
first
initial
gut
feeling.
So,
but
I
do
think
findability
rate
might
be
the
most
important
one.
A
C
C
If
you
see
the
the
page,
that's
linked
above
those
metrics
that
was
defined,
I
guess
on
the
research
theme
side,
so
things
about
evaluating
navigation
changes
as
a
whole
like
the
overall
sort
of
thing
and
then
for
individual
projects.
So
I
just
worked
based
on
that
for
now,
but
definitely
it
can
vary.
C
C
C
A
I
mean
so
specifically
the
project
and
group
settings
and
be
really
curious
about
those
results
and
how
quickly
we
can
follow
up
with
solution.
Validation
on
any
of
the
work
that
michael's
putting
together
for
making
bringing
a
search
menu
into
there
and
and
whether
it
can
help
find
ability
or
you
know,
help
drive
any
of
those
metrics
immediately,
because
I
think
we'd
want
to
you
know,
have
a
similar
survey
in
the
in
the
solution,
validation
or
similar
script.
To
follow
that
would
measure
yeah.
C
A
A
C
Well,
actually,
this
is
not
dependent
on
the
recording,
but
I
do
have
a
question
around
the
work
I
looked
earlier
in
the
agenda
and
I
think
vasily
mentioned
an
mr
draft
related
to
the
analytics
tab,
and
I
was
just
wondering
if
you
got
kind
of
a
sense
of
the
amount
of
work
or
the
weight
of
it.
This
is
just
personal
curiosity
because
I
know,
for
example,
we
have
like
13
of
those
issues
and
I'm
like
are
those
quick
wins
or
are
those
big
issues
curious.
A
It's
a
good
question.
I
think
that
there
is
probably
a
mixed
bag
and
obviously
I
can't
apply
engineering
weight
off
the
top
of
my
head.
But
from
what
vasily
said,
there
were
some
things
he
had
to
figure
out
and
some
considerations
that
had
to
be
made,
but
the
mr
that
he
has
prepared
it's
not
ready
to
merge.
Quite
yet,
but
it's
near
nearly
there
and
then
once
it's
ready,
it
can
be
used
as
a
template
for
a
lot
of
the
others,
and
so
it
should
speed
up
a
lot
of
the
others.
A
The
something
just
fell
over.
I
don't
know
it's
a
ghost.
I
lost
my
train
of
thought.
Oh,
so
then,
when
we
get
to
the
point
where
we're
working
on
the
other
features,
there's
just
likely
going
to
be
a
few
that
have
some
edge
cases
and
complications
like
if
you
turn
off.
I
think
this
is
the
example
that
highlights
it
best.
But
if
you
turn
off
feature
a
feature,
the
issue
feature
on
a
project
level,
there's
still
issues
on
the
group
level.
So
you
want
to
be
able
to
get
to
that
menu
item.
A
But
if
you
turn
it
off
on
the
group
level,
we
want
to
make
sure
it
also
turns
them
off
on
the
side
now
on
the
project
level,
I
believe
so
there's
there's
some
that
kind
of
cross
over,
especially
when
there's
group
and
project
settings
there's
some
that
influence
others.
I
believe
there's
also
like.
If
you
turn
off
issues,
there's
something
in
the
operations
menu
that
measures.
A
I
don't
know
there
there's
several
of
these
like
interconnected
dependencies
that
we
would
need
to
keep
in
mind.
I
believe
our
best
bet
would
probably
be
to
ship
all
the
ones
that
are
obvious
and
then
work
with
the
other
groups
that
own
these
features
to
make
sure
we're
catching
all
those
edge
cases
and
and
try
and
get
on
the
radar
as
quickly
as
possible.
A
Just
I
mean
we
can
just
have
input,
they
don't
need
to
implement
we're
not
trying
to
push
work
on
anybody
else,
but
yeah
so
short
answer
for
for
many
of
them
it
looks
like
it
should
be:
relatively
small
amount
of
work,
we're
hoping
in
13-7
to
get
analytics
and
potentially
operations
features
those
those
two
have
pretty
well
defined
issues
and
you
can
turn
them
on
and
off
already.
We
just
need
to
work
on
the
hiding
the
menu.