►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
Hello,
everybody.
This
is
monday,
the
31st
of
august,
it's
either
the
last
day
of
winter
or
the
last
day
of
summer,
depending
on
where
you
are
so,
I
hope,
you're
happy
with
either
way.
I'm
definitely
happy
that
it's
the
last
day
of
winter.
So
this
is
the
static
side.
Editorial
group
conversation,
it's
the
engineering
focus
edition
and,
as
usual,
I'll
start
off
with
a
few
highlights
from
last
week.
A
So
first
up
chad
finalized
the
marketing
site,
monarch
very
factor-
that's
been
coming
along
for
a
long
time
and
really
glad
to
see
that
in
place
now
also
chad,
with
the
initial
work
done
by
james
ramsey,
managed
to
delete
5000
stock
review
apps.com
repo,
which
it's
always
great,
to
delete
stuff.
I
get
a
big
kick
out
of
that
and
then
we
see
merged
functionality.
That
now
means
take
stack
page
in
the
handbook
is
dynamically
generated
from
a
yaml
data
source,
and
he
also,
I
didn't
find
him
fixed.
A
An
issue
with
passing
merge
request
description
of
the
push
options.
If
if
there
was
a
project
default
setting
really
where
it
wouldn't
take
the
value
passed
through
the
red
line
at
last
as
well,
and
then
shall
we
introduce
and
fix
an
issue
causing
community
thought
in
our
apartments
to
fail
and
enrique
came
in
featured
to
bring
the
markdown
attribute
definitions
as
tooltips,
which
also
got
merged
last
week,
and
he
also
pre-formatted
the
first
three
sections
of
the
handbook
that
we
were
working
on
pre-formatting.
So
all
around
a
bit
productive
week.
A
I'll
take
it
all
right
on
the
general
side,
so
just
mentioning
again,
we
see
he
is
on
pto
this
week
monday
through
wednesday,
this
week's
refining
session-
so
I
forgot
actually
to
finish
talking
so
tuesdays
tomorrow
session-
will
be
about
the
defining
the
user
experience
and
technical
requirements
for,
for
our
editor
I'll,
add
a
link
to
that
soon,
but
essentially
there's
a
lot
of
discussion.
A
You
know
we'll
we
need
to
make
the
best
decision
based
on
the
information
we
have
at
this
moment,
similar
to
how
we
did
the
first
time
around,
and
you
know
when
things
change
we
will
adjust,
but
so
tomorrow
session
we'll
focus
on
that
and
in
thursday's
session
it's
early
morning,
my
time,
so
it's
apec
training
session
will
be
about
producing
we'll,
be
focused
on
the
issue
that
deals
with
reducing
the
laptop
comedy
process.
A
So
there's
a
lot
of
previous
issues
and
stuff
that
we
opened
that
I
I
just
need
to
go
and
clean
up
that
epic
to
make
sure
that
still
still
relevant
and
have
a
look
at
all
the
related
issues
there
and
then
the
final
fyi
is
just
to
remember
to
keep
updating
our
setup
cited
unfolded
site.
A
It's
been
a
while,
since
it's
been
updated,
and
I
just
want
to
make
sure
that
everybody's
staying
on
top
of
updating
that
all
right
moving
over
to
the
gitlab
product
so
for
static
site
editor.
Enrique.
Can
you
give
us
an
update
on
things?
You've
been
working
on
and
focusing
this
week.
C
Yes,
before
before,
jumping
into
that,
I
want
to
highlight
that
for
tomorrow's
issue
requirement
session.
One
of
the
questions
that
I
would
like
to
discuss
synchronously
is
what
it
means
to
support
a
new
satisfied
engine.
I
think
that's
something
that
affects
in
a
very
important
way
that,
with
the
way
that
we
structure
that
we
see
with
ether
because
between
side
side
engines,
there
are
big
differences
to
achieve
in
the
techniques
to
achieve
the
same
goal.
So
I
really
would
appreciate
the
discussion
about
that.
C
Okay,
so
study
citator
and
the
formatting
issues
yesterday.
Last
week
we
delivered
a
fix
for
a
book
that
was
breaking
the
table
of
content
syntax
in
the
handbook
pages.
I
think
that's
the
only
the
only
bot
that
was
like
actually
breaking
the
handbook
pages
when
evaluating
with
the
side
side,
eight
or
so
it's
a
very
important
one.
Hopefully
this
will
land
a
very
soon
this
week
on
production.
C
C
The
purpose
is
like
automatic
automating
that
partially,
because
we
still
have
to
to
be
very
sure
that
this
formatter
is
actually
making
changes
that
make
sense
that
it's
not
breaking
the
pages,
but
so
far
in
my
experience,
I've
been
using
it
to
format
some
handbook
sections
and
it's
been
very
helpful
because
making
all
of
the
list
with
a
consistent
in
the
bullet
that
it
uses
or
changing
all
of
the
order
lists.
Those
are
changes
that
changes
are
very
repetitive
if
it
takes
a
lot
of
time.
So
it's
very
helpful
helpful.
C
This
week
we
are
going
to
keep
formatting
more
handbook
pages.
I
grew
up
something
here
about
why
we
are
doing
this.
Basically,
it's
that
that
we
see
with
eight
or
those
does
not
understand
markdown
syntax.
That
is
not
conforming
with
common
mark
and
we
we're
trying
to
make
all
of
the
handbook
pages
conforming
with
that
specification.
C
And
also
in
my
experience
last
week,
I
found
hundred
pages
with
a
broken
markdown.
Syntax
like
this
table,
was
not
defined
and
defined
well
and
then
with
this
out
with
these
two,
we
are
fixing
all
of
those
issues
and
it
will
definitely
improve
the
things.
C
Yeah
there
is
more
information
in
the
issue
that
I
shared
there.
That's
it
on
my
part.
A
So
two
quick
follow-ups
on
that.
Will
this
tool
that
you're
using
to
pre-format
the
pages?
Can
we
use
that
going
forward
in
terms
of
a-detecting
potentially
issues
and
and
providing
that
as
a
linting
or
even
auto-fixing,
things.
C
A
Okay,
slightly
unrelated,
but
a
conversation
eric,
and
I
just
had
around
that
the
table
of
contents
breaking
eric
had
a
thought.
Can
we
can
we
move
away
from
specifying
those
random
custom
attributes
to
using
a
field
in
the
in
the
front
matter
to
indicate
kind
of
like
that,
the
page
into
you
know
what
needs
to
happen
there
you
know.
Is
it?
Is
it
feasible
or
is
this
something
that
really
requires
those
customer
interviews,
though,.
A
All
right,
that's
something
we
can
investigate
after
the
fight,
because
if
we
can
remove
that
the
unnecessary
conflict,
syntax
that
will
be
direct
in
either
way,
but
it's
good
that
you
that
we
fixated
to
handle
the
meeting
thanks
for
that
enrique
all
right,
derrick
is
not
joining
us
today,
but
I
do
know
that
he
has
been
steaming
it
now
on
the
editor
front
matter.
A
The
difference
supporting
different
formatting
so,
whether
it's
json
or
whatever,
and
so
I
my
expectation,
is
and
from
what
I'm
saying
I'll
just
carry
on
with
that.
Then
chad
you're
on
introducing
a
configuration
file
in
a
static
site.
B
So
I
haven't
started
anything
on
it.
Yet,
as
we
discussed
in
our
prioritization,
I'm
wrapping
up
some
of
the
higher
priority
handbook
stuff.
The
first
was
fixing
the
the
bug
about
community
forts
and
then
I'm
going
to
go
ahead
and
finish
the
work
of
removing
the
change
log
from
being
committed
to
the
repo
every
day,
because
that's
about
two
to
three
meg
of
raw
diffs
every
day,
even
though
they
get
compressed
down.
B
That's
one
area
that
the
repo
size
is
just
slowly
creeping
up,
so
we
decided
to
go
ahead
and
get
that
one
thing
out
of
the
way
sooner
than
later,
and
then
after
that,
I'll
can
give
all
my
focus
to
the
config
file
work.
And
since
I
haven't
done
any
real
product
work
since
the
work
on
the
the
web
ide.
When
I
first
joined
back
last
year,
I
just
need
to
get
familiar
with
our
processes
and
how
we
do
everything
to
start
with.
A
Yeah-
and
one
thing
I
can
just
mention
is
that
we're
not
planning
on
in
introducing
the
need
for
configuration
for
editable
front
matter
in
the
short
term,
we're
going
to
go
with
the
first
iteration
of
just
using
plain
text
fields.
B
A
All
right
on
to
the
handbook
so
now
that
the
initial
mono
refactor
work
is
behind
us,
the
main
focus
on
the
on
the
handbook
side
for
for
us,
as
a
team,
we'll
be
on
my
breaking
to
frontman
away
from
the
doorman
as
part
of
this
work.
This
is
the
prerequisite
task
that
we
need
to
start,
namely
you
know.
We
need
to
fully
decouple
the
handbook
from
the
marketing
site
assets
and
we
started
discussing
that
and
it's
a
lot
more
complicated
than
it
sounds.
A
But
I
plan
on
on
having
it
putting
some
time
together
and
having
a
look
at
that
again,
then
there's
also,
we
need
to
convert
some
of
the
test,
extensions
that
we
wrote
for
for
middleman,
related
to
code
owners,
as
well
as
the
break
runs
we'd,
convert
that
to
a
helper,
and
so
those
are
all
conflict
tasks
that
we
need
to
start
shipping
away
at
before.
We
can
actually
get
to
the
actual
conversion
of
the
of
the
site
from
middlemen
to
frontman.
A
So
none
of
these
are
high
priority
at
the
moment,
it's
kind
of
like
a
secondary
priority
for
us
at
this
stage,
so
the
other
work
related
to
just
that
exciting,
inter
different
expressions.
Moving
on
to
gitlab
docs,
so
I'll
just
kind
of
fly.
I
noted
the
update
basically
provided
the
issue
last
week,
so
on
the
issue
relating
to
updating
the
the
header
anchor
links
with
the
product
here.
So
all
the
work
is
it's
done
and
the
merge
requests,
stages
of
review
and
approval.
A
So
those
just
contact
me
to
take
you
through
the
system
and
then
once
they
are
at
a
good
place,
coordinated
for
technical
right
to
get
them
all
at
the
same
time
because
they
all
depend
on
each
other
and
after
that,
from
a
doc's
point
of
view,
feature
that
we
will
be
focusing
is
allowing
well
providing
first
of
all
setting
in
the
admin
section
so
that
you
can
choose
whether
to
use
the
slash
hull
for
the
gitlab
ui
helped
over
the
links
or
having
have
it
point
to
the
gitlab
docs
website.
A
So
that's
all
par
that
that
in
itself
is
a
prerequisite
before
we
can
get
to
offline
doc,
supporting
in
an
air
gap
environment,
so
we'll
keep
iterating
in
that
direction
all
right.
Moving
on
the
guitar
everything
you
know,
give
us
an
update.
D
So,
on
the
getter
side
we
have
room,
did
export
complete
and
I
plan
to
merge
that
and
ship
it
this
week,
which
we'll
finish
off
our
export
sort
of
epic
there,
which
will
be
nice
and
move
on
to
other
things.
I
a
new
thing
that
I
started
last
week
was
get
lab
pages
and
working
on
redirects
there,
which
is
totally
new
to
me
and
working
with
golang
instead
of
javascript,
which
I'm
used
to.
D
But
it's
been
a
good
experience,
trying
to
learn
all
the
strategies
and
patterns
that
you
use
to
build
stuff
and
go,
and
I
have
the
redirects
working
from
the
config.
But
of
course
it's
more
work
in
progress
than
final
security-wise
and
tests.
So
I
need
to
finish
up
some
of
those
to-do's
and
address
the
review
that
just
happened
this
morning,
but
I'm
getting
some
great
help
from
camille
and
jaime.
So
it's
always
going
good
there.
It's
pretty
exciting.
D
B
So
those
are
just
in
the
form
of
meta
refresh
pages
they're,
not
anything
at
the
router
level.
D
Currently,
they're
meta
refresh
tags,
that's
the
solution
for
gitlab
pages,
but
this
new
feature
is
a
redirects
netlify
config.
So
it
reads
from
that:
config
file
single
point
of
redirect
config
and
then
it
redirects
to.
However,
you
configured
that
and
so
that
the
plan
is
to
remove
all
those
meta
refresh
pages
in
our
repos
now
and
specifically
trying
to
dog
food.
This
in
the
gitlab
docs
project.
E
Yeah
I
was
going
to
call
this
is
specifically
helpful
for
k,
lab
docs
and
we
really
appreciate
you
jumping
in
because
this
is
something
that
was
on
their
backlog.
They
hadn't
been
able
to
prioritize
and
it
was
blocking
the
ability
for
us
to
dog
food
get
lab
pages
with
the
docs
project.
So
it's
opening
up
a
huge
opportunity
and
helping
out
another
team,
so
very
much
appreciated.
F
A
F
Yeah,
we'll
probably
yeah
we're
going
to
review
them
in
the
issues
and
that's
where
we'll
document
the
feedback
and
then
I
might
create
videos.
So
people
can
understand
the
process
for
editing
with
each
of
those
systems.
B
So
there
were
no
no
people
excessively
confused
about
the
marketing
repo
move
or.
E
Eric
yeah,
I
don't
have
a
ton,
but
I
do
want
to
highlight
something
of
a
milestone.
I
was
looking
at
our
dashboard
and
we
have
exceeded
50
monthly,
active
users
for
a
new
feature.
I
think
that's
actually
pretty
impressive.
I
know
it
doesn't
sound
like
a
lot
when
we
have
millions
of
customers
and
users
on
gitlab,
but
that's
big.
E
I
think
that
it's
worth
celebrating,
I
mean
that's,
that's
a
lot
of
people
that
are
trying
out
this
list
a
little
feature,
and
obviously
it's
mostly
members
of
the
gitlab
team,
but
we
do
have
some
external
users
and
and
they're
integrating
it
on
their
site
and
and
using
it
at
least
once
a
month
to
qualify
for
our
metrics,
and
that's
that's
really
something
because
we
started
out
the
first
time
we
instrumented.
We
were,
you
know
under
20.,
so
we're
growing
fast.
E
I
think
I'm
paying
pretty
close
attention
to
this
number
I
mean
just
so.
You
can
see
where
my
head's
at
because
our
new
stated
goal
for
product
is
to
just
drive
monthly
active
users
on
the
platform,
rather
than
our
previous
strategy
of
going
wide
and
and
just
having
breadth
over
depth.
We're
really
trying
to
refine
the
experience
and
drive
more
users
in
each
particular
stage.
So,
as
we
look
at
sort
of
the
next
topic
and
beyond
when
we're
prioritizing
features,
I'm
I'm
ultimately
going
to
be
asking
myself.
E
How
is
it
going
to
draw
new
users
into
the
platform
and
and
make
it
possible
for
either
a
new,
a
new
group
to
start
using
the
feature
or
make
it
more
delightful
so
that
more
people
that
can
use
the
feature
are
using
it
more
often
things
like
that,
so
it
doesn't
change
anything
immediately.
This
is
how
I
already
was
thinking
about
our
product.
Obviously,
when
we
start
with
sub
20
users,
we
want
to
grow
that,
no
matter
what
it's
not
a
huge
shift
in,
how
I'm
prioritizing
the
backlog.
E
But
it
is
it's
nice
to
see
it
grow
so
fast
and
and
we'll
start
thinking
about
some
actual
goals
that
we
can
set
and
how
we
can
drive
that
further.
But
I
think
we
should
all
be
pretty
happy
with
how
fast
it's
growing
and
as
far
as
the
other
agenda
item,
I'm
just
starting
to
think
about
thirteen
five
and
sean-
and
I
were
talking
about
some
major
themes-
it'll
be
a
continuation
of
some
of
the
work
that
we've
already
been
discussing.
E
The
the
front
man,
migration
for
the
handbook,
the
editable
front
matter
and
and
the
configuration
file
which
I
forgot
to
listed
here.
But
I'm
assuming
those
will
have
some
work
carrying
over
in
a
13-5.
E
I
want
to
make
sure
that
we're
not
pushing
either
of
those
too
far,
as
john
mentioned,
we
want
to
get
to
usable
and
and
viable
as
far
as
like
the
feature
is
is
useful,
but
we
don't
need
to
push
it
too
far
before
we
start
thinking
about
some
of
our
other
goals
and
in
particular
the
potential
refactor
of
our
editor,
which
could
be
a
much
larger
task,
and
if
we
can
start
picking
up
work
on
that,
even
another
research
issue
or
potentially
initial
implementation
in
13.5.
E
I
think
we'd
want
to
do
that
sooner
than
later,
so
that
doesn't
just
so
we're
not
building
on
top
of
something
that
we're
going
to
replace
anyway
and
then
the
only
other
thing
that
I
think
I'd
like
to
try
and
squeeze
in
I'll,
probably
talk
more
about
this
with
michael
in
our
product
and
design
call
later
today
is
try
and
get
a
really
small
nvc
for
adding
an
mr
title
and
description
into
the
publishing
workflow.
This
submission
of
that
content.
That's
one
of
the
major
pieces
of
feedback,
we're
hearing,
obviously
gitlab.
E
We
have
very
strong
opinions
about
how
an
mr
should
be
formatted
our
static
site.
Editor
does
not
allow
you
to
add
that
context
when
you're
creating
the
mr
and
you
have
to
then
go
to
the
mr
page
and
edit.
It
seems
like
a
great
opportunity
for
us
to
iterate
in
13
5
on
that,
and
I
know
that
we've
been
doing
solution,
validation,
you've
all
been
seeing
the
issues.
E
I
think
we
can
whittle
that
down
to
something
achievable
in
one
one
milestone
and
get
just
the
mmr
title
and
description
not
worry
so
much
about
committing
multiple
times
to
the
same,
mr
or
assigning
reviewers,
and
things
like
that
which
are
all
great
parts
of
that
same
workflow
solution.
Validation,
that's
been
going
on.
I
think
we
can.
We.
D
E
Take
just
a
piece
of
that
and
ship
it
in
13.5.
Hopefully
I
also
we'll
set
up
our
planning
spreadsheet,
so
we
can
all
collaborate,
but
if
there
are
any
bugs
or
low-hanging
fruit,
ui,
ux
or
even
some
tech
de
issues
that
you
feel
passionate
about
you
feel
like
would
be
worthy
of
prioritizing.
E
Please
let
me
know
I'll
be
doing
a
sweep
through
the
backlog,
as
well
john
said
he
would
too,
but
if
there's
really
small
little
things
that
are
just
picking
away
at
you,
we
want
to
be
conscious
of
that
and
make
time
in
every
release.
But
at
any
point,
if
you
want
to
advocate
for
a
bug
or
a
paper
cut
or
something
like
that,
that
you
think
is
worth
fixing,
please
feel
free
to
bring
it
up.
B
I,
like
the
shape
of
the
monthly
active
users
graph-
it's
only
four
months,
but
it's
it's
got.
E
E
Yeah
I
mean
at
a
point
will
probably
not
be
exponential
anymore,
but
I
hopefully
you
know,
it'll
keep
going
up
pretty
steep.