►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
All
right,
hello,
everyone-
this
is
the
november
16th
static
site,
editor
engineering,
weekly,
sync,
first
item
on
the
agenda
is
that
unless
anybody
else
here
disagrees,
I
think
this
is
going
to
be
the
last
static
site.
Editor
weekly
engineering,
sync,
as
we've
mentioned
on
some
of
these
recorded
calls,
but
all
of
you
are
obviously
aware
the
static
site
editor
group
is
being
merged.
With
the
editor
group,
we
have
a
new
consolidated
editor
group
that
is
focused
on
the
web.
A
Ide
snippets
single
file,
editor
static
site
editor
and
under
that
new
team,
we'll
be
having
a
different
meeting
schedule
and
and
we'll
be
recording
all
of
those,
but
this
meeting
makes
it
a
little
redundant,
so
we
probably
wouldn't
have
this
one
moving
forward.
That
said,
lauren
there
are
still
really
great
opportunities
for
for
you
to
come
in
and
offer
input
we
won't.
A
We
need
to
work
out
what
it
means
for
like
how
we
what
responsibilities
we
have
over
the
handbook,
because
that
category
isn't
carrying
over
and
sadly
this
would
mean
probably
our
last
weekly
meeting
with
celie
because
he's
moving
on
to
a
different
group,
and
we
wish
him
all
the
best.
Of
course,
and
he'll
be
just
a
slack
message
away
he's
not
going
far.
C
I
posed
the
same
question
to
our
group
to
danielle
so
they're,
aware
of.
A
That
it's
gonna
take
a
little
while
for
the
dust
to
settle
and
figure
that
out,
but
we're
working
on
it.
A
So
this
being
our
last
meeting,
we
should
still
we
still
have
stuff
to
talk
about
we're
wrapping
up
this
milestone
and
we
want
to
get
some
updates.
I
did
see
someone
posted
a
link
to
the
editor
deep
dive
recording
that
was
definitely
a
highlight
of
last
week.
For
me,
I
was
only
able
to
join
over
the
phone.
I
didn't
get
to
see
everybody's
faces,
but
I
called
into
that
one.
A
It
was
a
very
informative
meeting.
Enrique
did
a
great
job
running
through
not
only
the
architecture
proposal,
but
how
we
got
there.
It's
a
must
watch
if
you
didn't,
if
you
didn't.
D
A
To
join
it's
a
really
really
great
meeting
and
a
great
example
of
collaboration
across
the
two
groups.
Now
one
group,
so
I
think
the
the
takeaways
were
were
really
exciting.
As
far
as
understanding
more
about
the
architecture
of
editor
light
and
how
it
might
complement
the
work
that
you've
been
doing
and
how
it
might
fit
together.
A
And
if
you
want
to
talk
anymore
about
your
takeaways
or
leave
that
for
the
stock
site,
editor
update.
A
Cool
so
the
navin
settings
work.
So
let's
just
do
a
quick
update
on
work
in
progress.
There
were
a
couple
issues
already
closed.
I
think
the
the
two
open
ones
are
related
to
analytics
and
turning
off
items
on
the
left
side.
Now
so
chad,
you
want
to
take
the
analytics.
B
Sure
so
this
one's
dragging
out
a
bit,
I
went
kind
of
deep
trying
to
understand
analytics,
maybe
a
little
bit
too
deep,
but
the
the
long
story
is
if
we
want
to
have
events
for
self-hosted
and
or
granular
events
for,
like
every
click
that
a
given
user
makes,
even
if
it's
the
same
user
as
opposed
to
just
tracking
unique
clicks
over
a
period
of
time.
You
know
aggregate
by
day
per
user.
B
That
is
more
difficult
and
it
involves
like
read
this
hll
and
I
talked
to
several
different
people
and
and
took
notes
a
lot
of
notes
on
it
and
possibly
even
some
things
that
aren't
even
implemented
yet
that
silly
is
still
working
on
he's.
One
of
the
people
I
talked
to
so
after
took
a
while
to
talk
up
to
all
of
us
before
we
come
to
that
conclusion.
B
B
So
I
started
implementing
that
end
of
last
week
and
then
I
got
stuck
because
the
new
events
I
wrote
are
showing
up
in
the
snow
plow
plug-in
lots
of
other
ones
are
showing
up,
but
it
seems
like
nothing
that
I
change
or
touch
shows
up,
try
to
get
a
review
app
working
to
see
if
it
worked
on
a
review
app,
and
that
seems
to
be
failing
because
of
a
flaky
test
that
is
persisting
even
after
a
rebase,
so
the
implementation
seems
really
straightforward.
A
Sorry,
as
muted,
I
said
that
sounds
good
analytics
are
rather
confusing
for
me
around
here
too.
B
A
vast
topic,
as
I
found
out
but
the
given
this
approach-
I
you
can,
let
me
know
what
you
think,
but
I
don't
think
it's
as
critical
like,
even
if
we
miss
the
date
for
this
particular
milestone.
Since
it's
going
in
gitlab.com
we're
not
going
to
have
to
wait
a
whole
month
to
see
it,
it
should
be
out
whenever.
A
It's
pushed
any
data
is
good.
All
data
is
better,
so
we
would
want
to
definitely
keep
pushing
on
getting
the
self-managed
data,
but
I
understand
that
it
that
there
are
complications
there.
I
don't
know
if
you
said
you've
asked
around.
I
have
just
learned
that
our
very
own
editor
team
member
fran,
is
something
of
an
expert
related
to
instrumentation
and
analytics.
So
if
you
haven't
reached
out
to
him,
it
might
be
good
to
run
it
by
him.
A
Cool
well
appreciate
it
and
oh,
we
can
follow
up
on
slacking
in
the
issue
for
for
more
and
vasily
the
left-hand
navigation,
consistency,
stuff.
D
So
for
this
task,
I
have
a
mr
draft
that
I
created
some
time
ago
and
actually
it
works.
So
you
click
on
the
toggle
and
it
removes
the
element
from
the
nav
bar,
but
still
it's
on
the
stage
that
I
need
to
finalize
it-
and
I
hope
I'll
find
some
time
this
week
to
work
on
that
and
get
it
to
the
point
that
it
can
be
reviewed.
D
And
after
that
I
think
it
will
be
possible
to
use
my
mr
as
an
example
for
the
future
changes,
because
I
think
we
can
repeat
the
process
for
other
tabs
that
do
not
have
the
toggle.
Yet.
A
Great,
if
you
could
maybe
find
time
this
week
to
do
a
little
bit
of
knowledge
transfer
with
chad.
Just
I'm
assuming
at
this
point
that
as
we
carry
over
into
the
editor
group
in
the
next
milestone,
this
work
is,
you
know
it's
not
obviously
going
to
be
wrapped
up
for
every
feature.
I'd
like
somebody
else
to
to
get
a
really
good
sense
of.
A
A
E
Yeah,
I
have
some
some
comments
so
last
week
before
jumping
what
I
want
to
do
this
week.
I
want
to
make
some
remarks
about
last
week
and
basically,
we
met
with
with
our
new
teammates
of
the
8th
group.
E
My
main
takeaway
is
that
they
have
so
much
strong
opinions
about
how
we
we
should
start
implementing
and
delivering
this
with
segregator.
From
the
point
of
view
of
of
how
we
can
integrate
with
either
light
on
monaco,
but
also
from
the
point
of
view
of
how
we
we
have
to
implement
that
we
see
with
gator
itself.
So
I.
E
I
think
one
of
the
of
the
lessons
that
I
really
liked
from
last
from
last
week
is
that
I
think
that
we
can't
realize
value
from
the
reciprocator
earlier
if
we
rely
on
the
markdown
preview
endpoint,
because
the
the
the
main
challenge
of
of
integrating
that
with
your
creator
in
places
like
the
initial
description
on
the
other
measures
and
the
immerse
request
description
page-
is
that
there
are
many
elements
that
that
doesn't
have,
like
a
doesn't
add
any
value.
E
This
might
explain
it
like
a
reference
to
a
message,
request
or
an
issue,
and
it
would
be
very
expensive
to
to
work
on
implementing
a
renderer
for
those
elements.
So
I.
D
E
That
we
can
rely
on
the
on
the
work
that
we
have
we've
already
done
in
the
vacuum,
to
to
support
those
pictures
quickly
quicker.
I
want
to
incorporate
those
thoughts
in
our
visibility,
implementation
plan
and
then
start
creating
implementation
issues
for
for
that
this
week.
E
I'm
gonna
also
be
talking
more
with
dennis
about
aether
light
and
monaco,
and
I
want
to
understand
if
the
idea
of
integrating
a
visualizator
as
a
view
of
the
editor
live,
it
still
allows
allows
us
to
create
an
editor
where
we
see
with
atm
experience
is
the
main
actor
like
in
the
user
interface
right,
because
in
the
case
of
the
satisfied
editor,
we
have
a
reciprocator
first
and
then
we
have
the
source
tab
that
is
like
in
in
the
background,
and
I
want
to
understand
if
we
can
actually
do
that
with
with
aether
light.
E
So
yeah,
that's
that's
that's
my
goal
this
week
learn
more
about
monaco
and
then
started
creating
a
concrete
plan
of
how
we
are
gonna
deliver.
This.
A
Yeah,
that's
great.
I
I
learned
a
lot
last
week
about
editor
light,
there's
still
so
much
more
for
me
to
understand
as
well.
I
know
dennis
offered
up
doing
another
like
deep
dive
on
his
side
about
how
it's
architected
and
the
potential
it
has
there.
So
we
can
try
and
get
that
scheduled
as
soon
as
possible
and
sounds
like
a
good
set
of
goals
for
this
week,
and
I
agree
with
the
the
main
point
about
making
it
so
that
the
editor
can
sort
of
default
to
the
wysiwyg
rich
text.
A
Editing
experience,
I
think,
we've
we've
found
in
our
research
pretty
consistently
that
a
real-time
preview,
even
a
real-time
preview
that
can
be
edited,
is
not
the
same
as
a
rich
text.
Editing
experience
to
users,
so
you
know
dropping
them
into
a
code
view.
A
Even
if
there
are
really
nice
wysiwyg
features
available
is
a
is
a
barrier
to
collaboration
or.
A
All
right,
so,
oh
the
other
issue.
I
just
wanted
to
ask
you
about,
because
I
saw
it
on
your.
I
think
it's
on
your
slack
update.
Are
we
good
to
go
with
your
mvc
on
committing
pre-committing
the
formatting
for
handbook
updates
as
a
as
a
way
to
reduce
the
noisiness
of
mrs.
A
Cool,
we
can
chat
more
about
this
on
slack
but
as
I
was
talking
about
that
with
a
couple
people
and
it
still
seems
like
a
good
way
to
go,
but
we
they
were
following
up
on
on
just
like
a
couple,
other
alternatives
that
we've
already
discussed
like
pre-formatting-
and
I
remember
weeks
back,
you
me
or
and
john
on
the
slack
thread
about-
or
maybe
it
was
an
issue
thread
about-
maybe
revisiting
the
reformatting
in
bulk
as
well.
So
we
can.
We
can
talk
about
that
on
offline.
C
Okay
for
real
still
working
on
adding
javascript
to
the
webpack
working
through
some
bugs
it's
adding
a
webpack
bootstrap
in
front
of
every
javascript
file,
which
adds
a
lot
of
weight,
and
it's
not
working.
So
I
gotta
figure
that
out
and
I'll
assign
over
to
you
to
chat
once
I
know
it's
actually
good
for
you
for
your
eyes,
then
I'm
adding
netlify
cms
to
the
code
base
to
the
marketing
site.
It's
really
lightweight.
C
C
C
Yeah
I'll
just
I'll
keep
asking
them
so.
C
E
He's
on
opportunity
leave,
but
I
think
that
a
good
group
to
reach
out
to
reach
out
is
the
front-end
foundation
team.
I'm
gonna,
give
you
a
link
to
the
channel
mike
railing
is
the
one
who
is
working
all
the
time
on
webpack.
C
Okay,
yeah.
That
would
be
great,
I
think,
I'm
still
running
into
issues
from
coming
from,
like
a
javascript
task,
runner
point
of
view
into
webpack,
which
it
is
not
so.
B
A
Cool,
let's
move
on
to
get
lab.
Docs
vasily's
got
some
pretty
amazing
news
here
in
this
update
I'll.
Let
him
share.
D
It
will
increase
the
size,
but
not
that
significantly.
So
I
think
I
will
stop
this
optimization
here
and
this
week
I
plan
to
add
actually
documentation
pages
to
the
omnibus.
I
need
to
update
some
scripts
that
we
execute
to
build
this
package,
so
I'm
gonna
test
it.
I'm
gonna
see
if
the
how
much
actual
size
increase
it
will
be
at
the
end,
but
yeah
I'm
looking
well.
I
think
it's
like
a
positive
thing
and
I
hope
I
will
be
able
to
do
it.
E
D
D
A
So
I
don't
oh
I
should.
I
should
mention
that
gitlab
docs
is
coming
over
to
the
editor
group
as
a
as
a
category
that
we
oversee
vasily
is
not
coming
with
us
to
the
editor
group
in
talking
on
slack.
He
graciously
offered
to
continue
working
on
the
offline
docs
since
he's
been
heads
down
on
this
for
a
long
time,
I'm
going
to
run
that
by
his
new
em.
I
don't
wanna
assume
that's
gonna
happen,
but
we'll
we'll
take
that
as
an
action
item
this
week
to
see.
A
If
we
need
to
you
know,
pass
that
off
and
get
somebody
up
to
speed
or
if
you
can
just
kind
of
work
on
it.
Maybe
you
know
slightly
reduce
capacity
over
the
next
milestone
or
two
or
something
like
that,
and
then
obviously
we
would
continue
picking
up
any
other
doc's
work
on
the
editor
group.
A
So
by
way
of
product
updates,
I
don't
have
much
michael
dropped
this
in
the
product
section,
but
it's
a
real
interesting
opportunity
for
us
on
the
settings
and
nav
work.
We
have
a
hackathon
coming
up
and
I
was
talking
to
marcel
the
design
director,
and
he
mentioned
this
as
well.
A
I
haven't
actually
dug
into
the
hundreds
of
issues
in
our
epics
with
this
lens
on,
but
the
first
one
that
I
noticed
was
related
to
just
making
keyboard
shortcuts
more
visible
and
easier
to
navigate
when
you
do
find
the
little
shortcut
modal
help
menu
things
like
that
little
ux
improvements
would
be
fantastic,
but
that
one,
I
think,
is
entirely
front-end.
I
will
be
coming
through
the
backlog
this
week
and
trying
to
label
them
or
otherwise
identify
them,
maybe
put
them
in
an
epic.
That's
indicates
that
they'd
be
good
hackathon
issues.
A
I
think
the
the
benefit
this
is
for
us
is
that
we
have
these
big
epics
full
of
bugs
and
really
no
intention
to
work
on
them.
In
the
next
three
to
six
months
on
in
a
focused
manner,
so
this
is
a
great
way
to
address
some
of
the
more
important
ones
if
you
come
across
any
and
you
happen
to
stumble
across
an
issue.
Just
let
me
know
just
ping
me
in
slack
or
in
the
issue.
B
A
That
might
be
better
yeah
yeah
if
they
were
the
only
way,
I
would
move
them
into
an
epic
there's
right
now,
just
like
a
generic
settings,
ux
bugs
epic,
I
might
move
some
of
those
out
of
there,
but
yeah
a
label
would
be
easier
and
they
are
not
exclusive
cool.
So
yeah,
let
me
know
if
you
see
any
other
candidates,
but
I
will
be
looking
this
week
on
to
try
and
spread
the
work
around
otherwise
we'll
have,
unless
I
think
michael
was
feeling
a
little
under
the
weather.
A
I
don't
know
if
we'll
have
our
weekly
design
and
product
sync
today
or
if
it'll
be
later
in
the
week,
just
keep
an
eye
on
the
calendar
for
any
changes.
A
We'll
talk
more
about
settings
and
nav
there,
I'm
sure
that's
has
been
his
main
focus
and
other
than
that,
I'm
just
getting
somewhat
up
to
speed
with
all
the
new
responsibilities
and
doing
a
lot
of
housekeeping
related
to
our
group
transition,
getting
direction
pages
and
handbook
pages
updated
and
that
kind
of
stuff.
So
that's
where
you'll
find
me
this
week.
A
A
Yeah
yeah,
and
also
just
to
clarify-
because
I
don't
know
that
I
said
these
exact
words
in
the
beginning.
The
statics
like
editor
group
is
not
getting
or
the
static
site.
Editor
category
is
not
getting
de-prioritized
in
in
any
way.
It's
just
coming
along
into
the
new
editor
group.
So
more
updates
on
that
in
our
in
our
editor
weekly
meetings
and
our
direction
page
will
reflect
our
priorities
and
all
that
stuff
moving
forward.
A
I
will
too,
we
can
we'll
have
to
have
something
you
can
come
to
the
editor
meetings.
Just
come
hang
out,
it
might
be
a
little
more
than
you
want
to
know,
but
just
just
join
okay.
One
of
these
days
will
get
you
just
to
officially
join
the
team.
B
I
think,
regardless
of
what
is
decided
with
the
handbook
you-
and
I
will
probably
still
you
require.
A
Yeah
and
I'm
really
interested
to
see
through
all
this
stuff
with
netify
cms,
so
I'll
be
bugging
you
about
that.
I'm
sure.