►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
I'll
just
do
a
quick
welcome
to
the
november
2nd
static
site,
editor
engineering,
weekly
call
and
I'll
turn
it
over
to
darva.
B
All
right
just
congratulations
on
making
progress
on
the
new
architecture
proposal
and
I
will
start
off
with
an
intro.
I've
met
most
of
you.
I
don't
think
I've
met
you,
susan
nice,
to
meet
you.
I
will
be
the
acting
em
for
just
a
few
weeks,
so
I
will
we
will
all
be
transitioning
to
a
new
em
in
the
next
few
weeks.
I
the
next
item
I
just
wanted
everyone
to
to
write
their
out
of
office.
B
The
reason
why
I
wanted
this
in
particular
was
obviously
first
planning
for
planning
reasons,
but
this
month
is
the
performance
review
month
and
discussions
will
be
happening
and
ems
will
be
speaking
with
you
all
and
have
to
have
all
that
done
by
the
end
of
by
november
24th.
So
this
lets
me
know
when
to
schedule
those
conversations
all
right.
If
there's
no
other
general
items,
I
will
move
on
to
nav
and
settings
I
just
was.
I
had
a
few
questions
about
the
re-architecture
proposal.
B
A
It's
a
so.
The
link
in
the
document
is
the
epic
which
I
added
the
the
full
description
at
the
end
of
last
week,
and
so
I
think
we
would
circulate
this
for
feedback
from
the
technical
side
and
then
I'll
circulate
it
around
the
product
team
as
well
just
to
keep
everybody
in
the
loop.
I
actually
don't
think
we've
ever
done
anything
of
this
kind
of
scope
and
as
thorough
a
proposal
when
we
first
decided
on
the
architecture
for
our
nbc.
A
It
was
made
not
more
hastily
but
with
less
like
impact
to
the
rest
of
the
architecture
and
the
company,
so
we
could
move
a
little
bit
faster
in
general,
so
I
actually
don't
know
how
we
what
kind
of
timeline
we
should
be
looking
at
for
approvals
or
what
the
next
steps
would
be.
A
As
far
as
scheduling
out
the
work,
though,
I
think
we
would
work
the
engineers
at
this
point
would
probably
be
working
on
breaking
these
out
into
tasks
there's
in
the
epic,
a
high-level
sense
of
what
iteration
steps
we
might
take
over
the
next
milestones
when
we
start
implementing
this,
but
I'd
be
looking
at
the
engineering
team
pretty
heavily
for
for
next
steps.
There.
B
A
That's
a
good
question
too.
I
I
would
imagine,
at
least
from
the
product
side
that
I'd
want
to
get
sign
off
from
from
the
director
from
my
director
at
least
eric
brinkman,
but
he's
been
aware
of
this
as
it
goes
along.
I
don't
imagine
that's
going
to
take
long
for
him
to
sign
off.
We
probably
would
want
to
get
tim's
approval
before
we
move
forward
too
fast
on
the
architecture
from
the
engineering
side.
A
I
I
definitely
want
to
leave
time
for
feedback
from
groups
like
the
editor
and
maybe
knowledge
as
well
as
maybe
source
code
for
for
how
it
might
affect
the
merge
request,
views
and
if
we
were
to
load
this
into
the
description
fields
for
merge
requests,
for
example,.
B
C
We
have
a
technical
issue
that
describe
the
architecture
proposal
more
from
an
engineering
point
of
view,
so
the
idea
is
that,
besides
adding
to
what
eric
said,
we
are
going
to
wrap
up
that
issue,
so
we
are
going
to
wrap
up
the
work
that
I'm
doing
and
creating
a
proof
of
concept.
We
want
to
share
that
with
the
engineers
in
the
create
a13,
also
other
engines
that
work
with
with
ui
components
and
have
expert
expertise
in
that
area.
C
After
that,
we
can
get
there
some
level
of
approvals
that,
except
from
from
a
direct
level,
and
then
we
can
start
creating
the
planning
issues
and
after
that,
we're
gonna
start
executing.
D
So
the
this
issue
is
a
summary,
but
there's
been
a
lot
of
very
in-depth
technical
exploration
on
other
issues
that
enrique
and
the
rest
of
the
team
have
done
over
the
past
several
weeks,
and
I
would
think
that
the
answers
to
any
technical
questions
that
remain,
which
are
mainly
around
you,
know,
acceptance
of
this.
D
These
choices
and
directions
are
are
found
in
there,
or
at
least
you
know,
that's
should
answer
most
of
them,
so
there's
been
a
ton
of
technical
exploration
and
we've
been
thinking
about
all
of
the
questions
that
the
wider
team
might
potentially
ask
about
the
plans
for
this
incorporating
the
product.
A
A
D
A
Yeah,
I
think
that
is,
I
mean,
I
think
what
we're
doing
is
proposing
a
way
that
those
who
are
interested
in
using
it
would
have
access
to
it.
But
it's
not
a
as
it
says
in
the
proposal.
It's
not
a
drop
in
like
we're
solving
this
for
everybody
else,
so
there
will
be
investment
in
other
groups
time
to
adopt
it.
A
So
I'd
like
to
take
their
feedback
into
consideration
so
that
we
can
make
that
easier
for
them
in
the
future,
but
I
don't
think
we're
necessarily
looking
for,
like
the
knowledge
group's
approval
on
this
we're
just
you
know,
we
want
to
hear
their
take
on
whether
or
not
it'd
be
useful
for
them.
B
Okay,
eric,
I
do
have
a
question
about
on
the
product
side.
So
what
at
what
point
are
you
going
to
eric
brinkman?
After
maybe
the
engineers
have
their
conversations?
Is
that
what
you're
going
to
do.
A
A
B
All
right
and
those
were
the
two
items
that
I
a
few
items
I
had
and
then
I
in
the
dock.
I
just
put
any
updates
because
I
didn't
know
the
format
you
all
usually
have
so
I
guess
facility
a
sync
update
on
disabling
items
in
the
left.
Now
I
don't
know
if
he
wrote
that
or
if
someone
was
asking
him
that
question.
A
Sorry
I
didn't
open
pre-penned,
my
name.
I
wrote
that
just
to
see
if
we
could
he's
out
today
and
for
the
next
few
days,
so
the
settings
and
nav
related
work
he
was
doing
was
on
disabling
items
in
the
left.
Nav.
A
If
you
don't
use
that
feature-
and
I
just
was
curious-
if
he
had
an
update,
I
know
he
was
working
on
one
who's
had
some,
mrs
open,
so
I'll
dig
into
the
issues
and
see
if
I
can
answer
my
own
question,
but
if
he
can
post
in
the
agenda
or
in
slack
some
updates
when
he's
when
he's
able,
but
we
can
move
on
to
the
next
one,
which
is
chad,
you're
working
on
and
providing
a
lot
of
information
on
the
frequently
used
projects
and
groups
in
the
menu
and
using
cloud
you
know
cloud
storage
instead
of
local
storage.
A
A
I
just
found
it,
but
if
you
don't
have
it
off
on
hand
but
anyway
to
to
summarize
michael's
proposal,
we
would
actually
just
like
to
hold
on
this
on
implementing
this
exact
change,
but
we
have
two
or
three
other
smaller
things
we
think
could
could
be
achievable
and
valuable
in
in
relation
to
this.
The
first
being
just
make
sure
this
is
instrumented,
so
we
know
how
much
people
rely
on
these
links
in
the
nav
in
general
and
then
building
a
dashboard
to
to
take
away.
A
Oh,
it
looks
like
he
did
get
around
to
creating
a
few
issues,
so
there,
on
the
very
last
comment,
I'll
put
a
link
to
the
exact.
C
A
So
his
latest
comment
there
at
the
bottom
of
the
issue.
We
have
a
small
iteration
to
improve
the
empty
state
and
promote
more
searching.
A
This
is,
if
you
don't
have
any
data
in
your
local
storage.
The
menu
feels
a
little
like
empty,
and
that
is
feedback
that
was
found
during
research,
so
improving
that
as
well
as
making
sure
we're
instrumenting
so
that
we
can
understand
how
people
use
the
frequently
visited
links
and
then
there's
a
secondary.
A
I
thought
he
had
an
experiment,
he'd
like
to
run
around
bringing
recently
viewed
into
the
home
page
and
that
wouldn't
actually
be
something
we
would
try
and
get
done.
This
milestone
probably
take
that
and
get
some
feedback
from
other
groups
as
well,
because
we,
technically
it's
not
part
of
the
nav,
although
it's
related
to
what
we're
trying
to
solve
so
yeah
those
three
issues
that
were
created.
A
A
A
A
And
I
guess,
while
I'm
talking
I'll
jump
into
the
static
site,
editor
and
voiceover,
jacques
update
for
the
static
site,
editor
feature
he's
working
on
uploading
images
and
it
looks
like
he's
got
on
his
plate
this
week.
The
displaying
images
with
relative
paths
sort
of
a
related
issue.
We
thought
might
be
solved
entirely
by
it,
but
it
looks
like
he's
going
to
use
some
of
the
config
work
that
you
did
chad
to
to
build
out
the
base
path
and
and
show
relative
paths
there.
That's.
A
E
Yeah,
as
mentioned
previously,
my
webcam's
kind
of
worked
right
now,
but
I'm
here
last
week
helped
monica
automate
a
bunch
of
handbook
links
and
then
also
had
the
mr
template
in
the
static
site
editor
set
and
that
should
land
today
and
then
for
this
week.
I'm
just
going
to
do
the
second
one
which
actually
ties
everything
together.
We
didn't
actually
have
the
end
point
we
needed
so
there.
E
D
D
E
D
E
So
yeah
we
can
take
this
offline,
but,
based
on
my
understanding
was
they
were
all
anchor
links,
and
that
was
the
reason
there
weren't
redirects
set
up
to
begin
with
so
but.
D
B
All
right,
I
guess
I'll
go
ahead
and
verbalize
and
recase.
Last
week
we
documented
the
wizzywig
architecture
proposal
in
this
issue.
This
week
he
plans
to
expand
the
documentation
to
cover
instrumentation
concerns
and
he'll
update
the
proof
of
concept
to
make
some
of
the
more
abstract
concepts
in
the
architecture
docs
easier
to
understand.
C
Gosh
you're
here,
I'm
sorry
so
well
by
the
way.
Thank
you,
but
yeah,
basically
that
last
week
when,
when
I
met
with
eric,
we
discussed
how
instrumentation
is
a
is
a
very
important
concern
for
him.
C
C
I'm
ready
to
make
clear
how
we
are
gonna
include
that
within
the
architecture
and
also
we
are
going
to
have,
I
want
to
to
cover
more
about
testing,
because
we
are
going
to
have
some
coupling
points
with
prospero
and
tiptop,
and
this
will
be
the
the
best
tool
that
we
are
going
to
have
to
control
those
complete
coupling
points
and
control.
C
How
we
are
dealing
with
those
dependencies
that,
if
we
get
a
dependency
upgrade,
we
are
not
gonna
be
we
are
gonna
have
we
are
not
gonna
have
a
broken
head
or
without
us
knowing
and
about
the
the
proof
of
concept.
So
we
created
a
proof
of
concept
when
we
were
evaluating
data
that
we
were
later
platform
that
we
were
going
to
choose
to
implement,
that
we
see
with
editor.
So.
E
C
Taking
that
same
proof
of
concept
and
making
some
updates
because
it
was
implemented
with
a
different,
remarkable
posture,
I
want
to
to
use
the
magnum
parts
that
we
are
proposing
in
the
issue.
So
I'm
going
to
work
on
that
and
after
that,
I'm
going
to
start
sharing
with
the
source
code
team
and
the
knowledge
team
and
the
and
the
interteams.
A
I'm
I'm
really
excited
to
get
brace
feedback.
I
hope
everybody
else
gets
as
excited
as
I
am,
and
we
are
about
this
architecture.
I
think
it's
it
could
be
really
really
valuable
to
a
lot
of
different
people
yeah.
I
spent
a
lot
of
time
thinking
through
it,
as
I
was
writing
up
that
epic
description
last
week
and
just
the
more
I
the
more
I
look
at
it,
the
more
I
write
it
down
the
the
more
exciting
it
is
so
should
be
an
interesting
week.
A
We
don't
have
much
going
on
in
the
handbook,
but
I
did
just
drop
this
in
chad.
I
think
you'd
mention
that
you
might
spike
on
on
getting
frontman
started.
I'm
not
sure
if
you
had
a
chance
to
it's,
not
it's!
Okay,
if
you
didn't,
we
don't
have
any
like
prioritized
work
on
that
right
now.
I
don't
think,
but
I
just
wondering
if
you
had
any
updates
on
that.
D
So
what
I
did
is
just
refresh
and
review
on
what
it
would
entail
and
the
summary
is:
there's
nothing
really
difficult
about
it,
but
there's
a
lot
of
little
things.
The
biggest
one
is.
We
should
just
get
every
all
of
the
assets,
image,
stylesheet
and
javascript
processing
not
handled
by
middleman
anymore
and
switched
over
to
webpack.
So
the
the
growth
growth
marketing
team
and
lauren
already
have
an
epic
that
covers
all
of
that
and
they've
done
the
first
little
part
of
that
which
is
the
the
style
sheet
handling.
D
So
really
it's
it's
just
kind
of
parked
and
once
we're
all
on
webpack.
Maybe
we
can
revisit
that
and
related
to
that.
D
The
the
handbook
part
of
the
monterey
pro
site
build
was
the
longest
running
build
of
of
all
of
the
things
and
it
was
sort
of
the
bottleneck,
and
so
I
went
ahead
and
split
that
into
two
parallel
partial
builds,
which
should
have
cut
about
four
and
a
half
minutes
off
of
the
overall
pipeline
time.
I'm
still
waiting
for
all
of
the
metrics
to
to
update,
but
that's
what
I'm
expecting
it
to
be.
D
A
That's
great
but
yeah
thanks
for
for
continuing
to
focus
on
on
the
build
times
the
pipeline
times,
if,
if
they
are
dropping
by
four
or
five
minutes,
that's
going
to
be
huge,
and
once
we
see
that
in
the
data
we
should
definitely
celebrate
it.
A
Well,
I
think
that's
that's
great
honestly.
We
won't
have
much
time
to
spend
focusing
on
it
with
the
nav
inciting
stuff
anyway,
so
this
is
a
great
way
to
wrap
up
the
work.
I
think
this
would,
if,
if
the
four
or
five
minute
drop
gets
in
there
we'll
be
under
10
minutes
for
our
build
times,
I'm
pretty
sure
so.
A
I
know
we're
a
couple
minutes
over.
I
actually
for
docs.
I
I
vasily
was
working
on
the
aircraft
improvements,
the
offline
docs
stuff.
So
I
don't
have
an
update
from
him
today,
but
we
can
follow
up
with
that
async.
That's
definitely
his
priority
for
13.6.
A
And
the
only
other
product
thing
on
the
agenda
darva,
I
see
you
linked
to
that
video
that
sid
recorded
about
his
feedback
on
the
settings
and
and
whether
we
should
split
them
up
from
a
global
settings
to
put
them
inside
each
individual
feature.
I
think
that
is
a
strategy
we've
considered
I'll
leave
the
more
in-depth
conversation
for
when
michael's
online
this
evening,
my
time
for
the
design
and
ux
research
weekly
call.
A
But
the
summary
is
we're
not
actively
planning
that
particular
tactic
for
anytime
soon,
but
we
are
using
that
a
similar
approach
in
some
solution,
validation.
So
he's
he's
working
on
some
ideas
that
are
in
a
similar
vein
and
we'll
be
getting
those
validated
before
planning
on
any
particular
milestone.
A
But
that
settings
work
in
particular
the
problem
of
discoverability
and
access
is,
is
like
the
number
one
priority
I
believe
on
the
settings,
epic.
So
it's.
D
A
Likely
to
be
the
most
immediate
iterative
change,
we
have
a
little
work
to
do,
but
it
is
probably
going
to
be
the
the
more
meaningful
work
that
we
do
in
two
three
milestones
from
now.
If
I
had
to
guess,
okay
sounds
good.
A
And
I
did
post
that
video
to
slack
as
well
in
the
nav
and
settings
room,
which
I
realized,
I'm
pretty
sure
I
added
you
all
to,
but
we'll
make
sure
that
you're
all
in
there,
just
when,
when
I
saw
it
recorded
yeah
sid
had
a
great
point,
which
is
there's
it's
hard
to
access
those
settings
and
the
mapping
in
a
lot
of
cases
is
one
to
one.
A
And
I
think
that
wraps
it
up
on
the
agenda
at
least
I'll,
be
logging
on
later
today
for
the
design,
product
and
ux
research
call.
But
unless
there's
anything
else,
I
can
stop
the
recording.