►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
Hello,
everybody,
this
is
the
weekly
static
site.
Editor
sync
meeting
today
is
monday,
the
5th
of
october
and
as
usual,
this
is
the
engineering
flavored
edition.
I
will
I'll
start
off
by
reading
a
few
highlights
from
from
the
the
past
week
and
the
first
one
is
actually
one
that
was
missed
from
the
week
before
and
the
initial
work
to
to
make
the
submit
changes,
speed,
ux
improvement
landed
from
derrick,
and
so
now
the
users
forwarded.
A
The
success
screen
instantly
was
waiting
for
for
something
to
happen
on
the
screen
with
just
a
loading
spinner.
So
that's
great
progress
there
and
then
the
initial
merge
request
to
introduce
the
the
title
description
values
that
the
user
can
edit
as
part
of
their
workflow
is,
is
in
play
as
well
and
the
next
one
there
is
derek.
I
saw
you
added
the
svg.
A
I
might
I
I
remember
seeing
the
mr,
where
you
introduced
the
the
the
success
screen
improvement,
and
then
I
saw
on
the
on
the
video
it
popping
in
and
out,
and
I
immediately
I
picked
it
up
and
then
I,
like
later
in
my
email
notifications
and
saw
hey
derek,
is
fixing
this.
A
So
I
wanted
to
do
a
special
shout
out
thanks
for
caring
about
the
quality
of
our
product
and
the
user
experience
to
not
just
leave
that,
because
you
know
based
on
our
principle
of
iteration
stuff,
you
could
have
easily
just
left
it,
but
you
you
cared
enough
to
do
it.
So
thanks
for
that,
I
appreciate
that
all
right,
some
general
announcements,
so,
as
I
mentioned
eric
and
michael,
are
still
ooo.
A
So
it's
not
just
this
week.
It's
today
they're
back
tomorrow,
a
reminder.
B
A
Social
call
on
on
thursday,
it's
a
continuation
of
the
theme
of
and
you're
sharing,
more
about,
your
location,
your
culture
and
your
food
and
and
then
a
reminder.
A
We
have
our
ama
to
continue
our
discussion
around
our
product
group
refocus
and
then
lastly,
also
we've
got
our
first
thing
big
session
coming
up
in
on
wednesday,
so
for
derrick
and
for
vasily
and
and
chad
you'll
remember
when
we
had
those
big
sessions
right
in
the
beginning,
when
we
still
had
no
static
site
editor
or
an
idea
of
what
we
were
going
to
do.
But
these
sessions
are
are
really
important
to
to
help.
A
You
know
just
let
your
mind
go
in
terms
of
where
we
can
take
the
product
going
forward
and
out
of
those
you
know,
we
we
get
some
great
direction
and
feedback
that
we
can
look
to
apply
all
right.
Let's
get
into
the
updates
and
first
up
static
site,
editor.
Chad.
Can
you
give
us
an
update
on
how
the
config
file
works
going.
C
Sure
good
morning,
so
for
point
a
as
it
says,
all
the
functionality
is
merged
just
waiting
to
verify
the
production
before
the
issues
are
closed.
So
all
of
the
the
values
that
we
wanted
to
support
are
there,
and
the
next
step
is
to
update
the
static
side
of
the
project
template
with
those
changes
to
reflect
it
and
I'm
going
to
start
by.
C
From
product
management
or
if
we
can
work
together
on
it,
is
this
issue
there's
the
old
config
file
we
had,
which
has
one
value
in
it,
and
we
need
to
come
up
with
a
plan
for
moving
that
over
and
deprecating
it
I'd
suggested
just
putting
it
as
part
of
this
epic,
but
eric
had
said
he
wanted
to
make
a
a
new
epic
for
that
effort,
since
it
involves
some
deprecation,
so
kind
of
need
to
sort
that
planning
out,
and
we
can
discuss
this,
but
I'm
proposing
that
we
just
defer
all
of
the
documentation
until
after
all
of
that
is
done,
because
I
think
it'll
just
be
easier,
less
time
for
the
the
technical
writers
and
everybody
else.
C
A
All
right,
I'm
I'm
okay,
with
the
documentation
deferring
it
to
to
after
the
change
as
long
as
it.
I
guess
it's
part
of
this,
this
milestone
and
it
will
make
the
release.
Because
this
feature
will
you
know
I
mean
it's?
A
A
So
as
long
as
as
long
as
and
also
we
must
try
and
remember
that
sorry,
try
and
remember
that
the
technical
writers
are
really
swamped
at
the
end
of
or
just
before,
the
the
the
release
cut
off
of
the
17
trying
to
get
all
the
stuff
reviewed
and
stuff.
So
the
quicker
we
can
get
marsha
to
start
reviewing
this
the
better.
So
maybe
a
an
initial
draft,
just
to
kind
of
like
get
things
going,
might
be
a
good
idea.
C
Maybe
you
know
one
and
one
after
this,
since
eric
is
out
today,
we
could
just
get
the
issues
lined
up
or
whatever,
and
I
can
hopefully
just
try
to
maybe
wrap
up
the
work
today
and
get
the
actual
work
for
the
changes,
ready
interview
and
then
plans
to
start
the
docs.
A
B
B
A
All
right,
chad,
you
and
I
can
can
sort
this
out.
You
know
one-on-one
in
terms
of
next
steps.
There,
jacques
update
on
the
video
embeds.
D
Yeah
so
this
week,
I'm
still
just
continuing
work
on
embedding
youtube
videos.
Last
week
we
merged
the
first
part
of
it.
So
this
week
I'm
just
working
on
the
final
iteration,
which
is
adding
the
modal
to
the
front
end.
E
So
last
week
we
finished
the
evaluation
criteria
for
the
rich
contaminators.
We
were
evaluating,
I
linked
the
spreadsheet.
In
there
we
had
a
a
great
discussion
around
all
of
the
data
that
we
that
we
collected
about
those
later
we
decided
to
go
to
move
forward
with
tiptop
and
and
ck835
for
a
proof
of
concept
phase.
E
C
F
Yeah,
just
basically
the
feature's
done
just
gotta
finish.
Writing
the
specs
and
enrique
is
gonna.
Help
me
with
an
issue
I'm
having
with
that
right
after
this
for
the
title,
description,
ui
and
then
after
that,
it's
just
a
bunch
of
various
follow-ups,
I'm
not
sure
exactly
what
order.
I'm
gonna
attack
them,
but
it's
the
last
big
piece
for
me.
A
Cool,
I
think,
it'd
be
a
really
nice
improvement.
I
know
I
will
definitely
be
making
use
of
being
able
to
edit
the
title
description
as
part
of
the
flow
okay,
we're
gonna
move
over
to
the
handbook
updates
chad,
you're.
First
up
there.
C
C
It
gets
stuck
often,
and
sometimes
the
workaround
doesn't
work,
or
at
least
it
doesn't
appear
to
work,
given
how
they've
documented
it
and
also
I'd
commented
on
this
issue
because
it
got
put
in
the
backlog
and
was
concerned,
because
that
takes
a
lot
of
time
for
us,
and
you
know
marketing
as
well
to
to
babysit
this
thing
and
nothing
gets
done
when
it's
stuck
and
we're
also
to
the
point
where
last
time
we
turned
it
off,
we
realized
we
really
can't
live
without
it,
there's
so
much
activity
and
chance
of
broken
master
when
we
turn
it
off,
but
it
looks
like
she
said
that
being
in
the
backlog
doesn't
necessarily
mean
it's
not
going
to
get
in
and
they're
going
to
discuss
being
more
proactive
about
us
fixing
this
or
detecting
it.
C
A
Yeah,
I
think
the
the
thing
to
do
there
is
to
keep
sharing
the
the
challenges
we
have
so
that
it
can
keep
staying
on
their
radar.
In
terms
of
the
importance,
I
think
you
know
like
the
team
member
applied
pressure,
shouldn't
necessarily
impact
the
the
p
or
the
s
level
of
of
an
incident
or
bug,
but
it
surely
does
contribute
to
to
their.
I
hope
it
will.
A
C
A
A
The
gitlab
way,
but
I
think
the
I
agree
with
your
point
last
time-
we
turned
off
no
strings,
of
course,
havoc
with
broken
masters
and
stuff,
and
we
should
not.
That
should
be
a
last
resort.
We
do
that.
So
I
remember
also
with
the
the
block
business
that
needed
to
go
out
for
the
get
her
announcement.
The
train
was
stuck
and
I
had
to.
A
G
So
as
a
preparation
step
for
the
front
migration,
we
are
gonna
move
it
from
the
middleman.
At
some
point
of
time
I
was
migrating
some
hour
extensions
to
the
helpers,
because
extensions
are
not
supported
by
the
front
one
and
I
finished
the
work
of
migrating
two
of
them
last
week,
and
my
next
point
is:
I
was
also
working
on
some
improvements
for
the
inter
that
can
detect
broken
links
and
anchors.
G
Currently,
a
current
version
can
detect
some
of
them,
but
it
does
not
checks
everything.
So
I
added
some
extra
checks
and
I
was
fixing
the
problems
that
a
new
version
of
the
reader
detected
plus.
I
will
request
some
code
owners
of
the
pages,
but
it
was
not
clear
for
me
how
to
properly
fix
the
anchors
I'll
ask
them
to
help
me
with
that.
C
A
Yeah,
I
was
thinking
that
I
spoke
to
andre,
who
you'll
remember
added
that
the
feature
to
for
the
common
misused
terms
and
and
and
we
see
we
went
in
and
instead
of
just
like
giving
feedback
in
terms
of
he
just
went
and
wrote
all
a
bunch
of
specs
and
everything
which
was
great,
and
I
know
andre,
really
appreciate
it.
So
yeah
thanks
for
your
going
the
extra
mile
with
you.
It's
appreciated
all
right.
The
last
point
I
have
there
on
the
handbook.
A
All
right,
lauren
over
to
you
for
an
update.
What's
going
on
in
growth,
marketing.
H
We
are
getting
our
okrs
together
for
the
next
quarter,
the
top
four,
it's
the
nutlife
cms,
implementing
a
design
system,
selecting
a
new
static
site
generator
and
then
getting
a
webpack
build
process
and
which
hopefully
I'll
get
that
launched
actually
this
week.
So
there's
links
to
all
those.
That's
what
we're
up
to.
A
Well
sounds
like
some
nice
work
coming
up
there
all
right
since
eric's,
not
here,
there's
no
product
update
to
to
make.
I
will
just
remind
you
all
again
about
our
product
ama
tomorrow
we
will
continue
discussing
product
focus
for
the
for
the
remain
for
the
next
few
milestones,
and
with
that
we
actually
finished
early
today.
So
I'll
give
you
all
back
your
your
eight
minutes
so
to
half
an
hour
so
have
a
good
day
further.