►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
Hello,
everybody.
This
is
the
statics
idea
of
the
group
meeting
on
monday,
the
26th
of
october
as
usual.
We
start
with
highlights
from
last
week,
and
the
big
highlight
is
that
we
have
settled
on
a
new
editor
architecture
plan
for
the
static
site,
editor
again,
a
big
thanks
to
enrique
and
the
rest
of
the
team
for
finalizing
the
decision.
A
It
was
a
long
journey
with
lots
of
things
to
consider,
but
I
think
you
know
in
the
end
we've
got
good
rational
behind
the
decision
and
I'm
certainly
comfortable
with
the
process
that
led
to
it
and
the
final
decision.
So
thanks
again
for
that
all
right
and
in
on
to
general.
So
since
we
made
such
good
progress
last
week
on
our
okrs,
I've
removed
the
sessions
this
week
because
it's
not
needed
anymore,
we're.
A
You
know
like
just
about
to
to
wrap
up
the
hammel
component
migration,
epic,
that
enrique
has
been
leading-
and
I
have
one
final,
mr
to
submit
on
the
page,
specific
css
and
then
we'll
meet
our
target
on
that
as
well.
So
you
know,
that's
all
all
going
to
be
fine
and
then
on
the
dip
training
as
well.
You
know
we've
got
everybody
is
done
with
that,
just
in
retail,
it's
wrapping
up
this
week
as
well.
So
that's
been
a
great
effort
from
the
team
as
well.
A
So
thanks
for
that
and
then
fyi
so
jacques
will
be
taking
some
further
paternity
leave.
You'll
all
remember
that
he's
got
two
little
hungry
mouths
in
his
house
that
was
added
recently
and
so
in
from
the
10th
of
december
to
january
he's
taking
some
further
paternity
leave,
and
I'm
reading
here,
michael,
is
off
on
the
30th
of
october,
as
well
as
6
and
30
november,
and
enrique
is
off
on
the
6th
and
the
9th
all
right
over
to
nav
in
settings.
A
A
B
C
It
jen
highlighted
we
made
a
decision
about
the
annuator
platform
and
I
left
a
link
to
the
reasoning
behind
the
decision
and,
besides
that,
in
that
issue,
there
is
a
lot
of
information
about
all
of
the
research
that
we
made
towards
making
that
decision,
and
this
week
I'm
going
to
be
working
with
eric
on
creating
and
communicating
the
architecture.
The
architecture
part.
A
D
A
Thank
you
very
much
over
to
gitlab
doc,
so
I'll
quickly
give
an
update
from
brazil
again.
I
know
he's
currently
working
on
the
offline
support
for
gitlab
docs.
I
don't
have
much
more
of
an
update
on
that,
but
when
I
did
have
a
catch
up
with
him
this
morning
he
mentioned
he's
not
blocked
in
any
of
his
work
and
he'll
carry
on.
So
I
expect
he'll
be
able
to
share
more
on
that
soon.
Susan,
you
have
a
note
there.
You
like
to
verbalize.
E
A
F
A
F
Susan,
I
had
already
talked
about
that,
so
it's
no
surprise
here.
This
is
going
to
be
really
helpful
in
documenting,
not
only
our
our
patterns
and
and
future
path
towards
keeping
settings
up
to
date
and
consistent
and
improving
the
experience,
but
also
you
know
making
it
easier
to
figure
out
what
you're
actually
changing
when
the
setting
is
exposed.
So
this
is
good.
F
I
don't
have
a
ton
for
today,
as
everybody
has
already
mentioned.
Almost
we
have
chosen
our
new
editor
architecture,
so
I
will
be
working
with
enrique
to
communicate
that
from
a
product
standpoint
in
an
epic
and
build
out
some
iterative
issues
with
him.
We
met
earlier
last
week
briefly
to
discuss
a
plan
for
that.
F
We'll
keep
going
on
that
this
week
and
I
did
just
want
to
say
thank
you
to
everybody
for
this
whole
project
because
it
was,
it
was
really
helpful
not
only
to
identify
such
a
a
strong
foundation
for
the
future
of
the
static
site,
editor,
which
I
think
we've
identified
a
very
good
one,
but
I
personally
through
following
the
research,
have
learned
a
lot
more
about
what
is
going
on
in
the
back
end.
The
considerations
we
need
to
take
in
place
from
a
technical
standpoint,
so
it's
been
really
enlightening
to
me.
F
I've
wrapped
my
head
around
a
lot
of
the
problems
that
felt
very
nebulous
before
so.
It's
been,
it's
been
really
educational
and
then
also
specifically
thanks
to
enrique.
I
know
this
is
not
a
retro,
but
thanks
to
enrique
for
valuing
transparency
in
our
communication,
especially
with
the
ck
editor
team.
When
he
made
the
selection,
he
sent
an
email
to.
F
F
I'm
really
excited
about
the
things
that
he
has
in
mind.
Our
priorities
are
very
much
aligned
and
they're.
It's
going
to
make
for
some
exciting
changes
and
not
not
in
the
sense
that
exciting,
as
in
like
super
difficult
or
massive
changes,
but
very
iterative
improvements
that
we
want
to
make
to
both
the
settings
and
nav
experience
and
we'll.
F
And
solution
validation
opportunities
for
that
in
the
near
future.
I
don't
have
an
exact
timeline,
but
he's
got
some
next
steps,
so
we'll
talk
about
that
more
I'm
sure
in
the
product
and
design
research
meeting
that
we'll
hold
later
today,
but
I'm
I'm
really
excited
to
get
his
take
on
that
and
I
think
he's
got
a
good
sense
of
what
needs
to
be
accomplished.
F
So
it's
going
to
make
a
big
difference.
I'm
very
excited
about
this.
This
work-
and
I
think,
when
you
take
a
step
back
and
look
at
all
of
the
backlog,
it's
not
as
as
daunting
as
it
may
be,
seemed
at
first,
so
the
the
deeper
I
get
into
it.
The
more
patterns
are
starting
to
emerge
and
I'm
able
to
identify
along
with
michael
some,
some
really
nice
changes.
A
Yeah,
I
think
it
would
be
great
to
you
know
these
are
kind
of
like
high
visibility,
high
impact
areas
and
would
be
good
to
to
have
some
positive
improvements
in
those
areas.
So,
looking
forward
to
that
all
right
before
we
sign
off
anything
else,
I'm
just
having
a
look
at
the
design
in
the
ux
research
sections.
It
doesn't
seem
like
there's
anything
we
need
to
highlight
in
this
call
we'll
see
michael's
just
talking
about
reaching
out
for
help
of
scheduling,
participants
for
solution,
validation,.