►
Description
Weekly sync call of the Static Site Editor group focused on product and design efforts.
A
All
right,
so
this
is
the
static
site,
editor
product
and
design
weekly
meeting.
It
is
June
22nd
here
in
the
same
States
and
yeah,
we
can
jump
right
into
it
with
a
couple.
Fyi
is
just
repeating
from
the
meeting
earlier.
360
reviews
are
due
today
within
a
few
hours.
If
you
haven't
completed
a
self-assessment
I
think
that's
the
most
important
part.
I
did
mine
just
yesterday,
because
I
progressed
me,
but
we
yeah
Justin
to
do
as
many
of
those
as
you
can
and
I.
A
Think
managers
will
start
distributing
or
you
know
communicating
the
feedback
over
the
next
week
or
so,
and
there
was
another
thing
about
while
I
was
out
that
I
was
catching
up
on
about
an
effort
to
reduce
the
number
of
meetings
on
Fridays
to
zero.
Hopefully,
no
meeting
Fridays
is
something
a
lot
of
groups
are
doing,
I
think
we'll
try
it
out
and
in
that
spirit
we've
moved
our
team
retro
to
Thursday,
so
we'll
try
that
out
see
how
it
works.
A
As
I
mentioned
before,
we
started
recording
I'm
just
catching
up
right
now
on
everything
that
happened
while
I
was
out
last
week
on
vacation
and
so
the
highest
priority
is
making
sure
that
any
issues
for
13.2
are.
You
know
well
documented
and
clear
and
have
there's
no
blockers,
at
least
on
my
side
to
starting
work,
because
that's
what
we're
working
on
this
week
so
far
seems
pretty
good,
but
they
can
always
use
a
little
more
tightening
up.
So
you
might
see
a
little
bit
of
activity
this
week
on
those
issues
and
yeah.
A
So
we
introduced
the
code
owner's
data
on
the
handbook
pages
with
the
avatars
that
you
had
designed
and
it's
live
now
on
the
handbook
pages
and
it
says
maintained
by
and
I
know.
We
talked
about
that.
It
feels
like
the
right
terminology
to
use.
I
think
somebody
in
slack
mentions
that
there's
a
very
specific
like
role
for
a
maintainer
in
get
lab
parlance,
and
it
was
just
a
suggestion
that
we
might
consider
changing
the
way.
We
position
that
and
maybe
he's
in
a
different
verb
and.
B
A
A
different
way
to
say,
because
code
owners
don't
necessarily
maintain
it.
They
they
are
reviewers,
but
they,
the
page,
may
be
maintained
by
somebody.
That's
not
a
code.
I
think
that's
a
little
semantics
for
the
purposes
of
the
handbook
is
that
these
are
the
dris,
but
we
don't
want
it
as
an
acronym
or
like
an
industry
term.
So
I
don't
know.
If
that's.
C
A
C
C
C
One
of
the
reasons
I
didn't
present
maintained
by
originally
was
because
of
the
different
roles
that
I
maintainer
has
on
projects
like
it's
a
it's,
a
big
thing:
I
came
out
to
become
a
minty
maintainer
or
something
which
is
different
than
the
dri
in
those
senses.
I
can
see
where
the
conflict
comes
from,
so
yeah
I
don't
want
to
introduce
a
word
like
gatekeeper,
because
that's
just
equally
as
bad,
but
it
feels
like
yeah
I,
don't
think!
That's
a
English
word
for
a
checkpoint
person
mm-hmm.
C
A
Then
we
can,
we
can
socialize
that
issue
and-
and
you
know,
if
other
options
come
up,
that
sound
reasonable
will
propose
the
change
and
I
don't
think
it
was
a
high
impact.
I
think
it's
also
not
super
urgent.
So
yeah
don't
drop
everything
to
just
do
that
issue,
but
it
would
be
interesting
to
be
a
little
more
precise
with
that
wording,
even
though
like,
if
you
don't
take
in
the
meaning
of
maintainer
and
violence,
the
maintaining
like
that
still
feels
right
to
me
just
in
like
conversational
English
like
these
are
people.
A
Up
the
page,
but
yeah
I
don't
want
to
I,
don't
want
to
confuse
anybody
or
imply
that
certain
people
have
different
roles
than
they
do
so
yeah
and
on
the
topic
of
the
handbook.
Even
though
I
should
be
talking
about
the
static
site
editor,
the
handbook
is
top
of
mind
because
we're
integrating
with
it
in
13:2
and
I
had
a
conversation
with
John
this
morning
and
our
one
on
one
where
we
really
want
to
get
to
the
root
of
this.
A
A
Be
some
edge
cases
we
have
to
resolve
and
some
kind
of
tough
conversations
and
tough
decisions
to
be
made,
but
I
think
for
the
purposes
of
our
long
term,
direction
being
able
to
control
the
handbook
front
and
end
back
end
will
let
us
move
more
towards
our
end
goal
of
being
able
to
productized
a
handbook
in
general,
so
somebody
could
stand
up
a
handbook
in
one
click
and
get
something
similar
to
us.
I
think
we'd
have
a
little
more,
you
know,
control
and
then
in
that
destiny.
A
A
B
John
and
I
talked
a
little
bit
about
that
today.
In
terms
of
you
know
all
of
the
shared
styling
and
shared
assets
and
JavaScript.
You
know
enough
to
mention
scripts
and
includes,
and
all
of
that,
and
it's
a
trade-off
between
how
can
we
sort
of
take
ownership
over
that,
but
also
we
don't
want
to
duplicate
a
lot
of
things.
That
really
should
be
the
same
because
they're
the
same
side
end
the
same
styles
and
the
same
design
and
aesthetic
so
we're.
A
And
I
don't
think
it
would
be
a
quick
I.
Don't
think
the
the
results
of
this
decision
would
be
immediately
apparent
right,
so
I
think
we
would
then
have
to
turn
around
and
make
a
plan.
First
of
all,
we'd
have
to
make
sure
that
you
know
like
we're
not
stretching
Michael
too
thin
and
and
giving
him
a
new
group
to
to
like
design
against
just
without
any
input.
But
then
we
would.
A
We
would
treat
it
just
like
another
group
which
it
is
and
we'd
have
a
roadmap,
and
we
would
define
some
incremental
steps
to
change
things.
But
ultimately,
a
vision
of
that
I
would
have
would
probably
be
that
we
kind
of
pave
our
own
path
with
the
the
look
of
the
handbook
and
start
to
diverge
from
that
shared
style,
which
would
which
wouldn't
hopefully
provide
a
little
bit
more
clear
distinction
between
what's
a
handbook
page
and
what's
a
marketing
page
and
and
make
it
more
clear
for
the
user
and
for
the
reader.
What
they're?
B
And
just
to
bring
you
up
to
speed
on
and
watch
out
and
I
decided,
the
my
direction
was
gonna
be
this
morning
the
whole
blog
and
releases
monomi
post-fight
we're
just
we're.
Gonna
put
that
on
hold
for
a
little
bit
mainly
so
he
can
be
really
clear
about
expectation
settings
of
how
things
are
going
to
change
how
they're
gonna
move
around
with
all
of
the
the
folks
under
marketing
in
the
dris.
B
A
That
sounds,
awesome
yeah.
So
again,
this
is
just
this
is
our
intention
and
our
proposal
as
I
was
getting
to
like
if
we
propose
this
and
we
get
a
lot
of
pushback
and
when
we
hear
that
you
know,
there's
a
very
clear
owner
on
the
marketing
side
that
there's
a
desire
for
a
consistent
experience
across
marketing
and
handbook
pages
and
and
instead
we
now
have
at
least
somebody
that
we
can
go
to
as
a
DRI.
A
That's
a
perfectly
valid
and
an
acceptable
outcome
in
my
mind,
I
think
that
we
just
we're
looking
for
for
guidance
and
right
now,
I,
don't
see
a
lot
of
downside
to
us,
owning
it
other
than
we
just
have
more
work
to
do,
and
you
know
down
the
road.
There
will
be
tricky
situations
when
we
talk
about
some
of
the
like
direction,
pages
and
stuff,
like
what
style
should
they
be.
B
A
Yeah,
there's
pros
and
cons
for
that
too.
I
mean
it's
technically
more
accurate
than
maintainer,
but
feels
maybe
if
you're
not
familiar
with
the
maintainer
role,
actually
feels
like
a
higher
level
of
responsibility.
Maybe,
but
maybe
maybe
it's
as
simple
as
that,
maybe
it's
owner,
so
the
the
immediate
next
step
Michael
is
going
to
create
an
issue
where
we
we
talked
about
that
the
things
we
considered
and
kind
of
start
the
conversation
and
they
open.
A
That's
it
on
my
side
for
now.
I
think
I'm
really
excited
about
13.2
as
a
I'm,
also
very,
very
impressed
again
with
the
team
for
shipping,
so
much
great
work
in
13.1
both
on
the
static
site
editor
in
the
handbook.
The
performance
is
getting
better
and
you
know
tell
the
story
about
that.
Pipeline
number
continuing
you
know,
having
dropped
so
significantly.
It's
it's!
A
You
know
like
some
of
the
things
about
creating
new
pages
and
maybe
even
scheduling
a
page
to
be
published
later
or
having
a
preview
draft
workflow
and
those
could
get
tricky,
but
I
think
we
could
work
through
them.
You
know
probably
next
quarter
so
I'm
I'm
really
excited
and
I
guess.
On
that
note,
we
can
talk
about
valid
solution,
validation,
yep,
because
that
leads
right
into
it.
A
C
So
last
week,
I
created
three
issues
around
like
areas
from
you
need
research
on
so
in
order,
I
guess
we'll
just
like
random
order.
C
So
that's
that
one
issue
and
nine
twenty,
where
that
I
was
looking
at
the
whole
general
flow.
So
in
this
issue,
I'm
just
expecting
to
like
test
like
how
you
might
create
a
new
one
having
existing
change
things.
They
say,
mr
and
like
kind
of
like
exploring
some
of
those
mental
models
around
that
there's
another
issue
that
I
created
around
the
editing
experience
itself.
C
And
what
do
we
want
to
be
more
fancy
going
toward
say:
Totino
CMS,
where
it's
a
blend
of
the
two
worlds?
It's
a
bit
of
this
a
bit
of
that
at
the
moment,
we're
not
too
sure
which
way
we're
going
and
also
looking
at
this
is
like
those
things
that
we
raised
in
a
passive.
Oh,
if
we
go
down
the
route
of
block,
you
know
if
you're
editing,
long-form
content,
which
is
more
common
in
our
handbook.
C
And
then
the
other
issue
that
I
raised
was
more
like
an
overarching
product
strategy
kind
of
issue
around
usages
of
the
static
side.
Editor
beyond
the
handbook
itself
is
something
that
the
team
it's
come
up
once
or
twice,
and
you
know
even
talking
today
about
whether
the
marketing
site
with
the
blogs
or
detox
site
with
the
wiki-
and
you
know
hunters
out
over
that.
But
the
static
site
editor
this.
C
A
A
A
More
narrowly
scoped
like
like
those
that
are
solved
within
something
like
Tina's,
CMS
or
or
whether
we
need
to
be
working
towards
more
of
like
a
blog
publishing
workflow.
That
inherently
has
a
lot
more
feature-rich.
You
know
workflows
that
been
involved,
multiple
contributors
and
reviewing
queues
and
stuff
like
that.
So
I
think
that's
really
important
to
understand.
A
Those
are
I,
think
a
fairly
common
and
they're
they're.
Definitely
one
of
the
more
common
template
types
for
for
static
sites.
You
know
when
you,
when
you
go
to
it
like
a
Jekyll
or
a
Hugo
gallery.
Those
are
often
the
starter
projects,
and
that
might
be
an
interesting
way
to
to
pull
out.
Some
of
the
use
cases
is
how
how
many
of
those
like
can
we
get
counts
of
how
many
times
each
one
has
been
forked
or
something
like
that
on
some
of
these
projects.
A
B
C
Yes,
so
those
issues
are
still
kind
of
fresh,
so
yeah
when
you,
when
you're
reading
through
them
over
this
week,
feel
free
to
make
any
edits
or
whatnot.
But
during
the
week,
I'll
probably
find
the
description
a
bit
warm
but
also
start
like
some
of
the
interview
guys.
It's
just
given
a
sense
of
how
this
might
go
down
so
that
then
we
can
start
putting
like
a
screener
together
to
recruit
participants,
because
that's
probably
like
the
most
time-consuming
part
of
all
this
yeah.