►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
Welcome
everyone:
this
is
the
september
21st
engineering
focused
weekly,
call
for
the
static
site.
Editor
group.
I
am
subbing
for
jean
who's
on
some
pto
this
week
and
I
wanted
to
start
by
calling
on
a
couple
highlights.
I
think
these
were
recovered
pretty
well
last
week,
but
as
I
was
working
on
release
post
items
last
week,
I
did
just
want
to
once
again
call
out
chad.
A
Thank
you
for
the
hard
work
on
the
static
site,
editor
config
file
having
that
merged
in
and
be
able
to
contribute
that
to
the
release
post
was
was
excellent.
It
was
a
good
example
of
iteration
and
I'm
very
excited
for
building
on
that
in
thirteen
five
and
derek
is
not
on
the
call.
Thank
you,
the
editing
front
matter.
A
Work
got
merged
in,
and
documentation
was
merged
in,
and
we
got
everything
just
under
the
gun
for
the
13
4
release
post,
but
that's
going
to
be
a
really
impressive
feature
too,
so
very
excited
about
both
of
those.
Any
other
highlights
that
I
missed
because,
honestly
I
was
probably
only
half
focused
on
the
group.
While
I
was
working
on
all
the
release
post
stuff.
B
A
C
Yep,
so
the
the
approach
we're
taking
to
this
is
we're
reusing
a
lot
of
the
built-in
I
get
live
apis
and
infrastructure
for
the
service
patterns
and
authorization
authentication,
and
for
that
and
as
well
as
for
the
config
file
itself,
we
have
intended
to
get
this
third
mrn
merged
in.
That
is
actually
laying
the
groundwork
for
that
api
and
then,
after
that,
the
actual
fields
that
we're
going
to
use
and
need
should
be
a
matter
of
just
like
adding
some
simple
classes.
C
With
that
a
couple
of
dsl
declarative
lines,
I
went
a
little
bit
slower
than
I
thought
and
I
technically
missed
the
release,
but
there
was
no
functionality
being
delivered
anyway,
but
I've
I
felt
a
little
bit
better.
When
I
I
talked
to
a
couple
of
people
about
it,
including
a
staff
engineer,
and
he
was
like
yeah-
that's
probably
the
second
most
complex
area
of
the
code
in
the
rails
app.
A
A
So
I
think
it'd
be
great
to
mention
it
in
134,
even
if
there's
limited
user
value,
which
was
always
the
case
anyway,
so
that
third,
mr
wasn't
exactly
going
to
deliver
anything
additional,
we
made
that
call
on
thursday,
so
anything
else.
On
the
on
the
product
side,
I
guess
most
of
the
people
working
on
the
product
are
off
right
now
so
or
not
on
the
call.
So
probably.
A
Not
I
did
add
this.
I
don't
know
chad
if
you
want
to
give
an
update
on
the
middleman
to
frontman
plan,
but
since
we
have
our
special
guest
michael
on
the
call,
we
can
actually
maybe
just
give
a
I'll
just
give
a
high
level
update
on
what
that
even
means,
because
it
could
be
interesting
to
you.
In
case
you
haven't
heard
from
from
lauren
we've
been
evaluating
a
replacement,
static
site
generator.
A
A
They
used
it
internally
and
built
it
for
their
own
needs,
but
have
open
sourced
it
and
we're
evaluating
it
and
it's
it
looks
pretty
promising.
So
we're
going
through
the
process
of
trying
to
make
it
work
for
us
in
in
the
handbook,
and
so
now
that
the
handbook
is
just
a
single
site
to
target.
We
don't
have
to
switch
over
the
whole
marketing
page
as
well.
C
C
But
given
that
the
main
benefit
that
it's
going
to
provide
us
is
is
really
the
speed,
and
even
though
we
could
always
stand
to
be
faster.
All
of
the
improvements
we've
made
where
we're
the
fastest
we've
been
in
three
years
and
still
well
under
10
minutes
for
the
longest
job,
which
is
the
handbook
which
we
still
could
parallelize
and
optimize.
C
D
C
A
A
C
Bad
with
names,
so
that's
where
we
are.
We.
We
have
a
lot
of
work
to
split
that
up
and
john,
and
I
spent
some
time
last
week
really
digging
down
into
the
details
of
that,
because
on
the
surface,
it's
like
yeah,
just
split
it
up
or
duplicate
it,
but
there's
a
lot
of
really
tricky
things
and
also
some
hard
decisions
to
be
made
of
like
okay,
which
side
is
this
going
to
live
in
and
what's
the
other
side
going
to?
Do
they
either
just
don't
display
that
you
know,
for
example,
direction
pages?
C
You
know
automatically
generated
those
are
displayed
in
both
marketing
and
the
handbook
we're
going
to
have
to
just
pick
one
of
those
which
owns
all
of
the
logic
to
generate
and
display
those
and
then
the
other.
You
know
if
it's
the
handbook
that
doesn't
have
it
we'll
just
put
it
in
an
iframe
or
link
to
it.
So
those
are
the
sort
of
decisions
that
are
going
to
have
to
be
made
as
we
split
all
this
stuff
up,
as
well
as
all
the
javascript
and
everything
else.
D
Yeah
that
makes
sense.
I
think,
thanks
for
all
this
insight
too,
because
it's
something
that's
a
little
bit
blurry
to
me,
though,
what
the
details
are
blurry,
but
the
amount
of
work
and
importance
is
very
clear
and
lauren
is
so
great
at
explaining
it
to
me
in
like
normal
human
terms
and
I'm
very
grateful.
I
have
a
front-end
dev
background
too,
so
I
can
kind
of
piece
it
together.
D
I
definitely
like
that
was
one
of
the
first
things
I
saw
coming
in
was
like
oh
wow
middleman,
like
the
name
kind
of
says
it
all
to
me.
It's
like
you
never
want
a
middleman,
and
this
thing
seems
like
so
slow,
so
that's
a
decision
that
I
would
love
to
make
with
on
our
side
in
concert
with
both
of
like
this
group.
Is
you
know
the
marketing
site
being
so
front-end
focused
like
we,
we
kind
of
want
to
razzle
dazzle
and
get
people
to
understand
how
awesome
the
product
is.
D
Of
course,
I'm
going
to
be
a
little
bit
skewed.
Like
I
mentioned,
having
front-end
background
like
it
seems
like
something
that
would
be
javascript
based
would
maybe
you
know
lean
into
the
skill
set
that
we
should
probably
build
out
on
our
marketing
side,
just
all
that
front-end
cool
stuff,
but
it
also
makes
very
little
sense
to
me
to
have
well.
Maybe
it
does
make
sense,
it's
unresolved,
why
we
would
have
front
man
running
and
then
like
next
or
something
a
different
like?
Will
that
create
more
complication
in
these
potentially
shared
resources?
D
D
The
other
one
slipped
my
mind
here,
oh
just
getting
a
clear
understanding
of
when
we
are
splitting
and
in
this
future
state
where
there
there
are
two
different,
you
know
sites
or
packages
or
apps
whatever
they
are.
What
does
that
look
like
difference
from
current
state
like
how
much
support
are
we
losing,
because
I
have
a
feeling
that
it's
an
incredible
amount,
because
this
team
is
awesome
and
I
feel
like
we're
going
to
be
losing
you
in
the
future
and
somehow
we
have
like.
D
I
want
to
be
able
to
go
to
danielle
and
todd
and
say
you
realize
that
we're
losing
like
90
percent
of
our
support,
like
it
went
from
lauren
with
the
support
of
the
static
site
group
to
now
it's
just
like
lauren
and
then
she's
like
expecting
me
to
do
something
and
I'm
useless.
So
I
need
we
need
more
people,
so
those
two
things
would
be
great
to
collaborate
on.
C
C
The
the
big
issue
is,
I
don't
know
how
much
of
it
technically
falls
under
growth
marketing,
but
definitely
for
the
handbook
and
definitely
for
other
areas
that
that
are
currently
under
the
marketing
site.
There's
just
a
lot
of
historical
functionality
and
complex
functionality
like
the
direction
pages
and
a
half
dozen
dozen
more
that
you
could
list
that
are
like
significant
apps,
all
written
in
ruby.
C
A
D
A
Cool
well
yeah,
we're
more
than
happy
to
partner
and
there's
a
lot
of
work
to
be
done.
Some
decisions
to
be
made.
I'm
excited
about
frontman.
I
could
see
in
the
future
us
reconverging
around
the
static
site
editor,
but
for
now
I
think
this
is
we're
going
on
great
paths
that
are
going
to
diverge
and
we
might
converge
again
in
a
few
years,
but
we'll
always
be
open
to
collaborate
and
and
help
out
awesome.
B
So
for
this
milestone,
I
have
a
couple
of
issues
related
to
documentation
project
and
our
goal
is
to
migrate
our
documentation
from
slash
help
page,
which
renders
the
documentation
right
now.
But
the
way
how
it
renders
is
not
the
great
and
we
have
a
docs
project
which
provides
a
much
better
experience.
B
So
we
gonna
migrate
all
of
this
documentation,
so
the
users
will
be
using
the
docs
project
to
like
check
the
documentation
and
right
now
I
picked
the
first
issue
that
introduces
a
new
configuration
option
for
in
admin
area.
It
allows
users
to
change
the
default,
slash
help
pages
to
the
docs
gitlab.com.
B
So
it's
the
first
step.
We
provide
it
as
an
option
and
we'll
probably
switch
it
on
for
the
gitlab
main
project
and
then
we'll
start
moving,
removing
the
old
slash,
help
pages
and
making
the
documentation
a
project
to
be
shipped
together
with
a
gitlab,
so
the
users
will
receive
both
of
the
projects
and
will
be
using
by
default.
The
docs
oh
yeah,.
E
Sure
so
the
first
thing
that
I
was
working
on
last
week
finished
up
with
git
lab
pages
redirects.
So
now
we
can
use
that
in
the
gitlab
docs
project
and
change
all
those
meta
refresh
tag
pages
over
to
a
single
config
and
hopefully,
in
the
coming
weeks
we
can
remove
that
feature
toggle
all
together
and
like
actually
generally
available
to
everyone
in
their
normal
instances.
E
Getter
wise
I've
been
working
on
issues
that
I've
been
piling
up,
that
I've
been
wanting
to
get
to
while
I've
been
working
on
the
redirect
stuff.
So
I
added
some
pagination
to
the
archive
before
it
was
like
day
pagination.
Now
I
added
our
pagination
for
those
rooms
that
have
lots
of
activity
added
multi-line
support
to
the
threaded
conversations,
so
you
can
actually
compose
them
in
that
getter
itself
instead
of
outside
and
copy
paste
inside,
which
was
a
bit
annoying
before
and
then
ux
wise
moving.
E
E
A
Week,
great
yeah
and
thanks
again
for
the
the
redirects,
the
it
did
not
go
unnoticed
by
the
way,
so
in
getting
feedback
for
the
release.
Post
sid
was
very
happy
to
see
that
and
give
you
a
little
shout
out
in
his
in
his
comments.
So
thank
you
from
it.
Everyone,
I
guess,
that's
marketing,
so
lauren
and
michael
now,
now's
your
chance.
It's
the
fourth.
F
F
F
I
I
thought
that
they
wouldn't
like
nutlify
and
they
actually
did
so.
It's
really
exciting.
If
any
of
you
want
access,
just
ping
me
and
I'll.
Add
you
as
a
contributor
to
the
repository,
which
then
gives
you
access
to
the
admin
and
it's
a
great
sandbox.
You
can
go
play
around
with
and
break
stuff.
Do
whatever
you
want,
yeah,
that's
what
I
got
michael
do
you
have
anything
to
add.
D
Just
just
for
like
forward-looking
plan,
now
that
we
have
this
selected
and
again,
lauren
did
such
a
great
job,
organizing
three
people
building
three
proofs
of
concepts.
While
I
was
on
like
a
parental
leave,
so
it's
just
like
I
came
back
after
three
weeks.
I
was
like
what
you
did
all
this
and
we
feel
very
confident
about
the
decision
and
like
having
gone
through
and
have
marketing
ops,
the
content
team
and
then
art
technology
teams
go
through
it.
D
I
too
was
surprised
it
was
netlify,
but
I'm
really
happy
because,
like
I
think,
between
lauren
and
I
and
a
few
other
members
on
our
team,
we
have
this
sort
of
back
of
our
head
vision
of
maybe
in
you
know,
2022
the
cms
that
we're
building
in
integrating
with
the
static
site
editor
and
then
this
being
a
package
product.
That's
actually
built
into
git
lab
that's
offered
to
our
customers,
and
I
feel,
like
netlify,
allows
us
to
take
a
step
towards
what
that
vision
would
be
sooner.
C
Lauren
gave
me
a
quick
run
through
of
it,
and
it
looks
good
and
I
had
a
while
back
sort
of
looked
at
what
I
would
like
to
use
for
my
own
site
and
my
own
side
projects
and
did
a
review,
and
I
like
to
net
lafaye
a
lot
and
I
think
they're
they're
sort
of
the
pioneers
of
the
gemstack
term
and
that
approach.
So
I
think
their
philosophy
and
everything
going
forward
is
probably
going
to
be
one
of
the
most
aligned
with
the
way
the
static
site.
C
D
You
know
one
of
the
things
we
got
mildly
confused
on
is
like
netlify,
no
cms
just
netlify
is
cicd
and
and
inherently
you
know,
we're
we've
been
told
it's
not
necessarily
a
competitor,
though
we
are
offering
similar.
You
know
functionality
or
services
to
the
same
user
base,
but
netlify
cms.
It's,
I
think,
todd
even
like
kind
of
drew
a
circle
around
it
was
like
this
is
not
a
competitor
at
all.
So
it's
because
we're
not
building
that
currently,
so
that
we
kind
of
waited
through
that
a
little
early
and
yeah.
I
agree.
C
And,
like
I
said,
I'm
I'm
really
interested
in
seeing
how
y'all
evolve,
that
and
having
an
l5
cms
but
having
git
lab
run
all
of
the
cicd
backend
infrastructure,
because
that's
exactly
what
I
wanted
to
do
for
my
own
stuff,
so
feel
free
to
keep
me
in
the
loop
and
reach
out
for
questions
on
that.
Lauren.
Because
I
want
to
learn
more
about
the
details
of
how
that
works
and
what
problems
you
run
into.
F
D
A
Okay,
I
was
also
I'm
also
interested
in
this
feedback
about
the
side-by-side,
editing
and
I'll
look
into
their
implementation.
So
the
the
feedback
that
we
got
when
we
were
looking
at
just
general
directions
very
early
was
that
the
side-by-side
editing
of
like
raw
markdown
that
didn't
gets
like
parsed
into
html
on
the
side
was
not
going
to
be
as
helpful.
But
from
what
I
understand,
what
netlify
cms
is
doing
is
more
about
like
providing
content
blocks
in
a
form
and
then,
as
you
edit,
that
it
renders
out
the
page.
A
So
I
think
I'll
be
really
interested
to
see
how
the
team
uses
that,
because
I
think
it
could
inform
how
we
evolve
our
editor,
which
you're
right,
though
we're
not
direct
competitors
right
now
and
and
they're
an
open
source
project.
I
could
actually
see
like
a
very
complimentary
service,
like
you
could
maybe
use
our
wysiwyg
editor
in
their
content
blocks.
One
day
like
that
would
be
a
fantastic
approach.
A
A
D
A
Yeah,
I'm
I'm
definitely
gonna
be
digging
through
the
proof
of
concept.
I
meant
to
do
it
last
week,
but
didn't
get
a
chance,
so
I
will
be
absolutely
doing
it
this
week
and
yeah
I'll.
Send
you
any
any
questions
I
have,
but
any
feedback
that
you
get
as
you
roll
this
out.
Send
it
our
way,
we'd
love
to
maybe
we'll
just
maybe
we
should
just
have
like
an
issue
open.
That's
like
rolling
threads
of
feedback.
So
we
can
capture
the
meaning.
A
Fantastic
well
thanks
for
your
hard
work
on
identifying
the
cms.
I
know
it's
been
an
important
project
for
the
marketing
team
and
yeah.
I'm
I'm
happy
that
you
chose
notify
cms
and
I
do
think
we
need
to.
We
need
to
be
specific
about
choosing
netlify
versus
netflix
ems.
They
are
two
different
products.
It
would
be
interesting
for
us
to
choose
netlify
as
a
like
ci,
cd
and
hosting
one
like
a
conjugate
delivery
partner,
but
yeah
we'll
see
this
is
the
content.
A
A
F
A
A
We
had
a
little
team
viewing
party,
it
was
fun,
yeah
cool.
I
don't
have
much
we're
hitting
close
to
time.
I'm
gonna
be
working
on
the
release
post
again
this
week,
the
releases
tomorrow
and
then
there'll
probably
be
some
feedback
coming
in
that
I
have
to
manage
so
I'm
excited
about
it,
though
it's
a
great
release,
I
I
think
the
static
site
editor
has
two
really
solid
release
post
items
in
there.
It's
making
the
team
look
good,
I'm
very
very
happy
to
see
that
but
yeah.
A
If
I'm
a
little
slow
to
respond,
that's
why
13.5,
the
kickoff
call
is
recorded.
I
posted
it
to
youtube.
I'm
really
really
excited
about
this
release,
but
I
also
want
to
make
sure
that
there's
no
questions
or
concerns
about
how
much
we're
committing
to,
if
you
have
any
of
that,
please
let
me
know
I
I
think
we've
made
it
clear
at
this
point
that
I'm
not
one
to
to
push
for
items
to
be
done.
A
A
And
the
last
thing
I
wanted
to
highlight
was
that
we
talked
about
this
on
our
weekly
design
call
last
week,
but
we
wrapped
up
the
last
of
the
category
maturity
survey,
interviews
and
the
scores
were
potentially
slightly
skewed
towards
the
positive.
I
mean
that
people
were
being
a
little
generous,
but
the
people
all
the
interviewees
were
able
to
complete
the
action
for
the
most
part,
and
the
scores
are
high
enough
that
we
can
formally
update
our
category
maturity
too
viable
I'll,
be
going
through
all
that
and
updating
that
this
week.
So
that's
very
exciting.