►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
Hello,
everybody:
this
is
the
weekly
static
site,
editor
group
sync:
this
is
an
engineering
focused
one
as
usual
I'll
start
off
with
some
fyi's.
So
a
reminder:
this
friday
is
family
and
friends
day.
A
I
can't
think
of
any
valid
reason.
Any
of
you
should
not
be
taking
it,
so
please
do
take
it
and
if
you
do
have
a
valid
reason
not
to
take
it,
please
let
me
know
so
that
we
can
arrange
an
alternative
day
for
you
and
then
just
a
reminder
that
derek
is
out
of
office
this
week
and
he'll
be
back
next
week
all
right
on
to
highlight
from
last
week,
so
chad
got
the
marketing
site
moving
to
the
monorepos
structure
to
pass
on
ci
and
it's
been
has
identified.
A
The
last
conflict,
validation
checks
to
be
done.
So
that's
some
good
news
there
and
derek
makes
some
big
improvements
to
how
the
wizard
editor
handles
non-markdown
code.
So
that's
a
big
step
to
getting
us
to
wroting
this
out
to
to
the
hand
well
rolling
that
out
to
the
full
handbook
and
announcing
it
to
the
company.
A
So
that's
great
news
on
the
general
section
so
we're
in
last
week
of
the
milestone
and
we're
pretty
much
on
track
to
meet
our
key
objective
of
integrating
with
the
handbook
and
also
to
complete
the
first
phase
of
the
monorepair
refactor.
So
I
just
wanted
to
give
a
big
thanks
to
everybody
for
all
the
hard
work
over
the
last
few
months.
There's
a
lot
of
work
that
you're
at
the
surface.
It
might
look
simple,
but
there's
a
lot
of
work.
A
That's
gone
into
both
of
these
initiatives
and
I
just
wanted
to
say
I'm
appreciative
of
all
the
effort
and
and
collaboration
that's
gone
into
making
that
happen,
and
then
a
quick
note
on
our
q3
okrs.
I'm
quickly,
just
gonna
run
through
it
as
a
I'm
not
going
to
go
into
too
much
detail,
but
I
want
to
quickly
just
cover
off
some
thoughts
around
it.
A
So
this
is
still
draft
it's
subject
to
to
the
development
sub
department's
okrs
being
finalized,
but
you
can
see
kind
of
like
how
they
all
ladder
up
to
these
and
so
we'll
I've
got
some
key
results
around
migrating
to
hammel
component
instances,
two
pajamas
and
with
enrique's
help
I've
managed
to
identify
the
two
that
we'll
tackle
since
he's
had
a
head
start
on
that
already
we'll
also
move
two
page
specific
css
files
out
of
the
main
css
bundle
into
page
specific
bundles.
A
This
is
something
that
I've
actually
started
on
working
initially
discussed
with
paul
slaughter
in
the
front
and
pairing
and
then
also
with
lucas
and
sarah
in
another
synchronous
meeting,
and
we've
got
some
free
work
to
do
to
to
get
to
the
point
where
we
can
move
this
out,
but
we'll
be
driving
that
forward-
and
this
all
relates
to
to
our
key
result
of
improving
the
performance
of
of
gitlab.
A
I've
adjusted
this
down
to
from
our
previous
target
of
of
11
to
8.5,
and
that
takes
into
consideration
that
the
jocks
on
paternity
leave
and
also
that
we
will
slow
down
our
work
on
the
dot
com
reaper.
A
We
will,
you
know
the
monoreep
refactor
and
the
work
chad's
been
doing
has
been
kind
of
like
contributing
40
to
50
percent
of
our
of
our
mr
total
over
the
last
three
months,
so
that
will
definitely
slow
down
over
the
next
few
months,
and
so
I've
made
an
adjustment
just
so
you
know
that
the
the
development
department
as
a
new
way
of
looking
at
the
mrs
per
engineer,
I
think
the
target
is
going
to
be
10,
which
is
down
from
from
I
think,
12
or
14
that
it
was
previously.
A
But
that
includes
community
contributions.
This
is
the
the
new
tag.
The
new
mra
that
they've
defined
is
is
separate
from
coming
from
community
contributions.
So
it's
only
from
team
members
and
it's
not,
and
it's
only
from
the
development
department,
so
it's
outside
it
doesn't
include
support.
It
doesn't
include,
you
know
the
other
engineering
departments,
quality
and
so
on
as
well,
so
this
will
be
a
peer
development
one
and-
and
so
it
will
also
have
a
more
direct
correlation
with
our
team's
target.
A
Then
we
will
also
on
expanding
the
the
capabilities
of
our
team,
I'm
proposing
that
we
all
completed
diversity,
inclusion
and
belonging
training.
I
recently
started
initially
it
was.
It
was
rolled
up
to
managers
only
and
I've
started
with
the
training.
I
actually
can
show
you
the
template.
I
found
a
lot
of.
A
I
haven't
actually
finished
all
of
this,
but
I
found
a
lot
of
value
just
in
reviewing
our
existing
pages
in
our
handbook
and
got
refreshed
on
a
lot
of
things
that
I
almost
forgot
from
from
onboarding
and
and
the
pages
have
changed
so
much
since
I
joined
a
year
ago,
so
it
was
really
good
going
through
those
things.
There
was
also
there's
also
this
learning
path,
that
linkedin
is
providing
free
access
to
on
diversity,
including
belonging
and
I've
just
done
an
unconscious
bias
course
so
far,
and
it
was
really
insightful.
A
It
is
quite
a
big
commitment
it
it's
probably
at
a
minimum.
1.5
to
two
days
of
of
time,
and
so
I'm
going
to
work
that
into
our
our
planning
and
and
so
on.
But
it's
really
worth
doing
and
I
think
it
would
be
beneficial
to
everybody
in
the
team
to
to
to
go
through
this.
A
So
those
are
kind
of
like
the
proposed
okrs
that
we
have,
if
you
have
any
feedback
on
that
feel
free
to
leave
a
comment
on
the
issue
or
to
ping
me
directly
and
I'm
happy
to
take
any
feedback
into
consideration
and,
like
I
said
it's
subject
just
to
the
dev,
the
part
sub
department
so
cos
also
being
finalized.
B
So
we
should
have
clarity
on
that
by
the
end
of
this
week,.
A
C
C
So
great
work
on
that
now.
The
only
missing
step
that
we
have
to
overtake
is
supporting
learning
images
from
this
from
there
from
the
editor
and
that's
something
that
we
are
gonna
focus
on
this
week.
A
Thank
you,
and
that
brings
me
to
the
next
point
that
I
have
here,
which
is
a
recommendation
now
that
the
the
erb
handling
code
has
hit
production
to
actually
make
the
static
site
editor
link
available
on
all
the
handbook
pages
as
part
of
a
soft
launch,
essentially
by
thinking
behind.
A
It,
gives
us
an
opportunity
to
get
possible
feedback
before
the
the
group
call
that
we're
having
next
week,
tuesday
and
and
making
the
more
formal
announcement
to
the
company
and-
and
so
my
suggestion
is
that
we
that
we
do
it
now
already
I've
just
I've
pinged,
enrique
and
eric
on
on
the
the
kind
of
like
draft
mr
to
get
their
opinions
on
it,
and
ultimately
it
will
be
eric's
call.
I
think
enrique.
You
mentioned
that
from
a
technical
point
of
view,
it
should
be
okay.
A
C
Yes,
so
we
expressed
some
uncertainty
around
nearly
yeah
erb
support
for
everyone
last
week.
So
a
way
of
of
working
around
that
uncertainty
is
why
plugging
the
erb
support
in
there
in
gitlab.
That
way,
if
we
find
that
we
are
running
that
users
turning
into
too
many
issues,
18
yard
pages
we
just
had
you-
can
we
can
just
disable
the
picture
client.
It
gives
us
a
lot
of
control
because
we
don't
have
to
publish
another
merge
request
to
disable.
It.
A
C
That's
right:
if
the,
if
the
flag
is
disabled,
the
the
controller
in
the
block
can
return
that
the
file
is
invalid.
D
A
No,
I
don't
think
we
have
one
okay,
enrique,
would
you
mind
opening
an
issue
for
that
with
just
with
the
plot
level
requirements
as
you
as
you
kind
of
like
expressed
it?
I'm
I'm
in
support
of
this
approach,
because
it
does
give
us
that
safety
net
of
of
turning
off
the
erb
support.
If
we
do
pick
up
any
major
issues
with
you
know,
without
delaying
you
know,
by
24
to
48
hours
and
having
lots
of
issues
and
potentially
crop
up.
So
I
definitely
be
in
support
of
this.
D
Also
on
the
the
soft
lunch,
I
think
that's
a
great
idea
too,
especially
because
of
the
the
stuff
I
posted
to
try
to
construct
a
url
to
for
this
to
work
can
be
pretty
tricky.
It'd
be
nice
to
just
be
able
to
dog
food
it
easier
on
any
page.
I
want.
A
Well,
chad,
since
you're
in
support,
I
could
really
help
you
use
your
help
with
a
failing
lent
for
specifically
relating
to
to
url
structures
on
that
merge
request
so
I'll.
Take
the
I'll.
Take
your
your
enthusiasm
as
a
indication
of
willingness
to
help
as
well
all
right
and
with
that
over
to
you
again
chad,
for
a
quick
update
on
the
mono
repair
refactor
in
the
handbook.
D
It's
obviously
not
something
that
you
could
just
do
once
and
then
try
to
resolve
with
a
merge
conflict.
So
I
had
to
write
a
script
which
is
fairly
complex,
which
moves
the
stuff
that
down.
D
That
needs
to
be
done,
and
then
I
do
that
over
and
over,
as
I
iterate
on
the
actual
configuration
and
find
things
that
are
wrong,
and
then
I
like
throw
away
that
command
and
move
everything
again,
which
actually
involves
moving
everything
down
and
then
moving
all
of
the
existing
handbook
stuff
back
up,
because
that's
the
only
way
it's
defined
as
everything
else
and
that
went
well,
I
got
the
bills
working
locally.
I
got
it
green
on
ci,
I
went
deep
into
the
debugger.
D
This
may
be
a
little
interesting
to
you
lauren
and
found
out
some
strange
things
related
to
the
monorepo
config,
for
example,
if
a
file
is
used
via
partial,
you
don't
explicitly
have
to
say
hey.
This
is
a.
This
is
a
file
that
is
needs
to
be
listed
and
found.
D
It
will
just
magically
find
it
because
it's
a
completely
different
code
path
in
middleman,
whereas
the
file
that's
used
via
proxy
resource
or
the
blog
plugin.
You
have
to
be
explicit
about
all
of
those
extra
templates
and
make
sure
that
they're
either
are
referred
to
by
a
an
include
or
a
files
watch.
So
things
like
that-
and
I
documented
most
of
it-
is
in
the
doc
monorepo
rv
file.
D
Some
of
it
is
at
the
top
of
the
monorepo
yaml
file,
that's
more
relevant
to
the
the
actual
usage
of
it,
and
so
where
it's
at
now
is
the
only
way
you
can
know.
If
any
of
this
actually
did,
everything
right
is
to
download
the
six,
the
artifacts
from
the
six
jobs
on
the
emr
and
compare
those
against
the
artifacts
of
a
master,
build
that's
against
the
very
close,
commit
and
see
what
the
differences
are
and
account
for
things
like
the
the
emr
url
has
changed.
D
You
know
it's
got
the
review
app
and
that's
where
I
got
to
last
week
and
it
looks
like
some
of
the
proxy
resources
just
aren't
working
as
well
as
some
other
things
and
all
those
those
tasks
are
listed
in
the
merge
request,
so
hopefully
getting
everything
fixed
into
a
degree
of
confidence
by
this
week,
even
with
a
short
week.
B
A
A
I
actually
just
think
the
calendar
invite
to
you
and
chad
for
for
the
three
of
us
to
quickly
sync
up
and
just
discuss
a
kind
of
like
a
rollout
plan,
because
we
need
to
give
people
a
decent
amount
of
heads
up
that
this
is
coming
and
just
kind
of
like
get
ghetto
ducks
in
a
row
how
we
coordinate
with
this
kind
of
like
big
change,.
A
Yeah
all
right
on
the
gitlab
doc.
I
don't
have
a
a
a
big
update
other
than
what
I
shared
last
week.
Vasily
is
back
from
from
pto
and
he's
got
a
few
things
on
his
priority
list
this
week
to
focus
on
outside
of
docs,
but
we
did
catch
up
season
around
the.
A
Installing
a
gitlab
docs
instance
in
an
air
gap
or
offline
environment
and
vasily's
next
steps
on
there
is
to
based
on
the
discussion
we
had
with
with
the
released
the
team
to
have.
You
know
the
releasing
the
distribution
team
to
to
write
up
just
a
summary
of
the
proposed
way
forward
with
that,
and
then
we
can
take
it
from
there.
So
maybe
by
the
end
of
the
week
or
early
next
week,
he'll
he'll
get
to
that.
And
then
we
can
start
making
progress
on
that.
A
And
then
we
do
have
a
bunch
of
docs
issues
scheduled
in
our
13.4
road
kind
of
flight
planning.
So
we
will
be
making
progress
on
those
things
soon.
Cool
eric
update
on
gator.
E
E
A
It
for
me
all
right:
lauren,
updating,
update
on
the
growth
marketing
themes,
endeavors.
F
Yeah
this
week,
we're
gonna
kick
off
our
marketing
site,
cms
proof
of
concept
project
where
we're
just
gonna
build
proof
of
concept,
integrations
for
contentful,
datto,
cms
and
netlify
cms,
and
this
will
create
sandboxes
that
we
can
allow
the
con
content
contributors
to
log
into
and
test
what
the
interface
looks
like.
F
We
also
growth
marketing
has
put
together
a
marketing
website,
refresh
strategy.
I
think
there's
six
or
seven
phases
to
that.
Some
really
big
epic,
that's
gonna
over,
go
all
the
updates,
we're
gonna
be
making
to
the
website
and
michael
prus
put
together
brandon
digital's
foundational
agenda,
which
goes
over
a
lot
of
the
infrastructure
changes
that
we're
planning
to
make,
and
I
wanted
to
share
that
with
this
group.
A
Cool
yeah
that
definitely
interesting
things
that
I
will
make
sure
to
catch
up
on.
I
I
will
offer
my
input
if
you
need
help
with
contentful.
Yes,
yeah,
absolutely.
F
A
I
have
spent
quite
a
few
hours
of
late
playing
with
that
and
it
it.
It
does
kind
of
like
give
you
this
blank
space
a
sheet
to
start
with,
and
then
you
need
to
start
building
your
data
models
and
stuff,
and
you
know
it
takes
a
little
bit
of
time
to
get
used
it,
but
once
it's
in
there
it
does
become
quite
easy
and
intuitive
to
work
with.
A
B
G
Nice,
sorry,
I
am
really
post
shadowing
this
release,
so
I
had
to
go
on
the
stand
up.
Sorry
buddy,
I
was
skimming
the
agenda
and
I
did
want
to
touch
on
the
really
putting
the
static
site
editor
link
on
all
handbook
pages.
I
think
I'm
all
for
it.
My
soft
launch
sounds
good.
Let's,
let's
talk
more
about
that
inside
or
in
the
issue.
G
A
A
I
guess
volunteered
by
by
being
enthusiastic
about
this
change,
that
he
would
fix
the
pipeline
for
me
and
then
we
can
merge
that
and
enrique
brought
up
the
fact
that
one
way
to
mitigate
our
concern
of
whether
to
allow
erb,
support
or
not
was
just
to
add
a
feature
flag
for
for
the
validation
in
in
the
back
end,
and
so
he's
going
to
open
an
issue
for
that
and
we'll
work
with
silly
to
to
see.
A
If
we
can
get
that
in
because
that
will
you
know,
be
our
safety
net
to
turn
off
that
support.
If
we,
if
we
need
to
so,
and
I
think
yeah
then
we're
the
other
part
of
it,
is
that
enrique
is
going
to
focus
on
finishing
up
the
image
upload
feature,
which
is
the
last
outstanding
bit
of
the
the
scope
that
we
wanted
to
target
for
rolling
out
to
the
company
so
yeah
once
it
seems
like
it's
all
coming
together
nicely
and
so
we're
all
on
track.
G
I
only
had
really
one
point
and
then
I'll
probably
elaborate
more
on
this
in
the
design
product
call,
but
I
think
we
we
received
two
really
validating
bits
of
feedback
over
the
past
couple
days,
and
I
just
wanted
to
take
a
moment
to
celebrate
that
and
to
to
highlight
those.
The
first
came
from
get
lab
product
manager
actually
he's
a
group
manager
on
the
product
team
and
he
posted
on
slack,
but
he
found
it
found
using
the
static
site,
editor
delightful,
which
is
just
exactly
what
we
want
to
hear
right.
G
So
I
think
that's
exactly
what
we're
hoping
for
we're
building
an
editor
that
can
offer
an
alternate
experience
instead
of
a
replacement
experience
and
one
that
is
delightful
to
people
who
have
technical
background
or
not,
and
and
it's
we're
not
trying
to
narrow
our
focus
to
build
something
for
for
an
audience
that
is,
has
any
specific
technical
background
or
understanding
of
git
so
yeah
I
was.
I
was
really
encouraged
to
see
that
and
I
really
appreciated
posting
that
it
was
on
a
friday.
G
So
I
figured
I'd
highlight
it
in
case
people
missed
it
and
then
I
think
more
exciting
is
we
had
an
issue
that
was
opened
as
a
sort
of
feature
request
from
an
external
user,
a
member
of
the
community,
and
I
believe
the
issue
was
a
duplicate,
so
I
ended
up
canceling
it,
but
I
referenced
it
and
I
mentioned
in
the
comment
I
commented
on
the
issue
that
I
was
going
to
close
it
and
I
linked
to
the
other
one
and
said
you
know
my
emails
and
my
profile.
G
If
you
want
to
chat-
and
they
did
they
emailed
me-
and
I
posted
in
the
doc-
I
don't
want
to
share
my
screen.
I
didn't
ask
permission
to
to
publicize
this
person's
feedback,
but
I
will
follow
up
with
them
and
see
if
they
want
to
have
some
more
one-on-one
chats,
because
it
sounds
like
the
exact
use
case
and
testimonial
that
we're
going
for.
This
is
a
in
this
case.
Someone
who's
already
a
git
lab
customer
and
obviously,
maybe
obviously,
because
they
submitted
an
issue.
G
They're
they're,
more
engineering
focused,
but
they
want
to
host
a
static
site
to
move
off
of
a
wordpress
site
that
they,
they
said
specifically,
was
what
were
the
clunky
ugly
and
old
wordpress
site.
That
requires
too
much
maintenance
and
updating.
G
G
They
specifically
called
out
that
a
side
by
side,
markdown
preview
was
not
going
to
cut
it
for
their
collaborators
and
that
they
were
very
excited
about
the
static
site,
editor
and
the
future
of
that.
So
it's
I
I
couldn't
have
solicited
a
better
testimonial
for
for
what
we're
thinking
about
right
now.
I
think
this
is
exactly
why
we're
building
this.
G
G
G
And
I
will
summarize
like
I
have,
for
others
for
other
interviews
I'll
create
a
an
issue,
although
maybe
this
I'll
find
a
way
to
see.
If
dovetail
will
be
a
better
place
to
put
this,
so
we
can
keep
all
our
feedback
in
one
place,
but
yeah
we'll
make
sure
this
gets
captured
in
a
way
that
we
can
refer
back
to
it
with
some
key
quotes.
B
D
Time
but
I'm
going
to
be
on
pto
next
monday,
so
I
wanted
to
mention
something,
especially
for
lauren
the.
D
We're
gonna
run
into
all
of
those
decisions
and
have
to
think
about
them,
but
for
now
I'm
just
trying
to
get
the
move
down
this
as
quickly
as
possible,
and
luckily
it's
turning
out
being
able
to
defer
all
of
those.
Just
by
saying
we're.
We're
sharing
lots
of
stuff.
A
Yeah
and
thanks
for
that
timely
reminder,
chad,
I
totally
forgot
that
you're
out
of
office
next
week,
which
makes
our
sync
up
a
little
later
today,
even
more
important,
so
I'll
see
you
too
in
in
that
call,
anybody
else
have
any
parting
thoughts
before
we
close.
This
call.