►
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
sinkhole.
This
is
the
engineering
focused
edition
and,
as
usual,
we'll
start
with
a
few
highlights.
So
first
up
is
derek
who
finished
the
work
on
getting
the
editable
front
mounted
ui
integration
wizard
mode
completed
thanks,
derek
for
including
the
review
app
linkedin.
I
encourage
everybody
to
have
a
play
with
that
business
finished
refactoring
the
gitlab
docs,
so
that
the
tier
name
that
doesn't
impact
the
header
links,
which
was
a
great
collaboration
effort
across
multiple
emrs
with
many
people.
A
Thanks
for
that,
one
vasili
and
chad
finished
off
two
of
the
first
three
iterations
on
the
static
site,
editor
config
file,
support
and
followed
standards
used
in
existing
apis
and
git
lab
for
service
patterns
and
config
files.
A
So
that's
a
good
one
that
we
can
leverage
the
existing
things
thanks
for
that
show
on
to
general,
welcome
back
jark
nice
to
you
to
have
you
back
in
the
fold
for
those
of
you
that
don't
know
jacques
was
on
parental
leave
for
the
last
two
months,
and
it's
getting
back
slowly
into
the
swing
of
things
in
13.5.
A
Expecting
a
coffee
chat
called
from
him.
Sometime
to
catch
up
on
everything,
I'm
not
going
to
read
out
the
out
of
office
notice,
but
there's
a
few
of
us
being
out
of
office
over
the
next
while
so
please
take
take
a
look
at
that
and
then
just
a
heads
up
this
week,
I'll
be
focusing
on
making
trying
to
get
all
of
our
13.5
issues
ready
for
development.
A
So
expect
a
few
things
for
me
to
help
flesh
things
out
and
provide
the
look
at
the
iteration
steps
on
the
various
issues.
All
right,
let's
get
into
our
static
site.
Editor
update,
derek
you're.
First
up.
B
Sure
so,
yeah
kind
of,
as
mentioned
before,
we
have
the
kind
of
last
mr
to
get
the
front
matter.
Ui
feature
set
so
just
a
matter
of
getting
that
through
and
then
there's
going
to
be
an
iteration
for
a
performance
improvement.
We
went
that's
actually
one
of
the
things
that
delayed
this
feature
internally,
like
going
back
and
forth
on
what
we
should
actually
use
and
that
kind
of
there's
you
know
trade-offs
and,
ultimately
we're
actually
gonna.
I'm
sorry
short.
B
A
Cool
and
anderson's
enrique's,
not
on
the
call
I'll
verbalize
for
him,
so
he
delivered
two
fixes
for
bugs
that
were
breaking
handbook
pages.
The
first
one
was
flattened
nested
lists
and
the
other
one
was
reference
definitions.
A
So
with
those
two
out
of
the
way,
I'm
hoping
that
we
won't
see
any
major
bug
reports
if
there
are
any
we'll,
obviously
look
at
them,
but
that
should
hopefully
fix
the
majority
of
the
issues
we've
had.
There
has
been
one,
mr,
I
was
picking
on
about
noise.
I
explained
the
situation
and
I
think
it's
fine.
You
know
people
really
there
except
to
to
have
a
bit
of
noise
in
the
mr
or
use
another
make
another,
mr
with
only
the
necessary
edits
they
want,
and
then
enrique
will
focus
this
week.
A
You
would
have
all
seen
me
posted
a
message
in
our
channel
slack
channel
around
tomorrow's
session,
where
we
will
be
discussing
specifically
prose
mirror,
as
well
as
its
view,
genius
kind
of
like
implementation
as
a
potential
editor
and
talking
about
that
and
there's
some
kind
of
like
pre-reading,
which
would
be
great
if
you
are,
if
you
do
plan
on
joining
the
session,
to
read
through
that
read
through
his
proposal
in
the
issue
as
well,
so
that
you
come
with
kind
of
like
a
prime
demand
for
for
the
discussion.
C
C
The
second
was
to
introduce
the
standard
service
pattern
and
the
third
was
to
implement
the
standard,
config
file,
support
with
and
dummy
value
that
we're
not
currently
using
yet,
which
is
the
the
static
side
editor
generator
of
which
the
only
valid
value
is
middlemen
and
first,
the
first
one
is
done.
C
The
second
one
is
completely
reviewed,
I
think
ready
to
be
merged
and
the
third
one
is
mostly
coded
and
once
those
are
done,
we'll
have
all
of
the
config
file
framework
in
place,
and
it
should
be
straightforward
to
just
implement
additional
classes
for
the
new
config
files
that
make
it
easy
to
add
the
value
and
the
validation
and
they'll
be
easy
to
send
to
the
front
end.
So
that's
the
plan.
C
It's
a
little
bit
slower
to
split
it
up
and
have
the
separate
review
and
maintain
your
cycles,
but
that's
the
way
we're
supposed
to
do
to
get
lab.
So
that's
moving
along
pretty
quickly,
even
considering
that.
A
Cool
all
right
onto
the
handbook.
I
there's
no
update
this
week
for
those
that,
when
doing
the
fall
last
week,
I'll
just
reiterate
that
13.5
focus
will
be
on
completely
decoupling,
the
marketing
and
handbook
sides
and
then
moving
to
front
main
as
our
static
side
generator.
A
D
It's
these
tasks
are
mostly
about
migrations
that
we're
gonna
do
from
slash
help
to
docs,
gitlab.com
and
particular
one
issue
when
we
want
to
replace
all
of
the
links
that
currently
point
to
slash
help
to
be
able
to
provide
an
option
for
users
to
switch
from
this
switch
all
of
the
links
for
their
projects
from
the
slash
help
to
docs,
I
created
a
proposal
and
I'm
I
just
finished
it
a
couple
of
minutes
ago.
D
So
I'm
waiting
for
the
feedback
from
the
technical
writers
team
to
see
if
this
approach
good
enough-
or
there
are
some
kind
of
problems
with
that
and
after
that,
I'll
continue
with
these
issues.
Cool.
A
Perfect
eric
give
us
an
update
on
your
work
on
gitlab
pages
redirects.
E
So
it's
really
close
to
merging
and
the
docs
are
added.
We
have
various
cross-linking
docs
across
like
the
get
lab
project,
the
gdk
docs
and
all
that
stuff
and
then
the
maintainers
approved,
but
I
need
to
just
rebase
to
get
rid
of
this
conflict
that
popped
up
during
that
time.
So
that's
looking
really
good
and
then
getter
wise.
I
just
been
working
on
a
few
fixes
in
between
all
the
redirect
stuff.
A
Cool
yeah,
I'm
really
excited
to
see
you
redirects
learning.
Gitlab
pages
lauren
give
us
a
little
bit
of
an
update
on
the
growth
marketing
world.
F
So
we
are
almost
done
with
our
proof
of
concept
review
of
the
cms's.
Would
you
you
all
like
access
to
poke
around.
F
Okay,
yeah
they're,
just
like
sandboxes,
where
you
can
go
in
there,
try
it
out
mess
it
up
awesome,
and
this
week
last
week
you
kind
of
dragged
my
feed
on
it,
but
I'm
gonna
start
on
adding
webpack
to
the
marketing
site,
adding
that
external
asset
pipeline
just
got
to
do
it,
and
then
we
are
hiring
a
full
stack
developer
on
the
marketing
team.
So
get
your
referrals
in.
If
you
know
anyone
that
would
be
a
great
fit.
A
That's
great
news:
happy
to
see
your
acting
team's
engineering
capabilities
increase.
F
C
And
I
also
anticipate
you
pretty
quickly
running
into
some
need
for
discussion
on
with
us
about
splitting
files
and
and
duplicating
files,
which
is
close
on
our
roadmap
too
right
john.
A
Yeah
13.5
related.
A
You
know
the
big
thing
we
need
to
tackle
is
the
decoupling
of
the
marketing
and
handbook
sites
and
specifically
how
we
deal
with
all
the
static
assets
and
so
on.
So
that's
that's
a
priority
for
me
this
week
too,
I
made
a
recommendation
in
the
issue
last
week
and
I
I
need
to
just
get
every
all
the
kind
of
conversation
together
as
a
final
kind
of
like
proposal.
Then
we
should
probably
have
a
bit
of
a
sinkhole
to
just
catch
up
and
make
sure
we're
all
on
the
same
page
around
that.
F
I'm
hoping
to
get
like
a
mvc
approach
where
you
just
get
it
working
like
real
minimally
and
then
then
we're
really
gonna
have
to
yeah
decide
what's
lit.
G
G
With
this
one
here
to
build
on
chad's
update,
I
want
to
give
chad
and
everybody
involved
in
planning
of
the
config
file,
some
kudos
and
and
high
fives,
because
we
were
called
out
specifically
by
the
product
team
in
at
least
among
create
for
an
excellent
example
of
iteration.
So
we
are
shipping
the
config
file
and
I
wrote
a
release
post
item
and
I
mentioned,
as
you
can
see
in
the
link
here
my
first.
G
My
first
comment
was
basically
I'm
a
little
uncomfortable
positioning
this
because
we're
not
bringing
a
lot
of
value
to
users
like
in
a
release
post
as
a
release,
notes,
type
item.
It
does
it's
hard
to
position
this,
but
it
builds
a
foundation
for
some
really
really
important
work
later
on.
So
I
did
my
best
to
wordsmith
it,
but
I
asked
for
some
input
there
and
the
input
was
basically.
This
is
perfect.
G
This
is
a
perfect
example
of
iteration
and
so
perfect,
in
fact,
that
one
of
the
other
group
pms
raised
an
mr
to
include
it
in
the
handbook
as
an
example
of
iteration
and
how
we
should
be
doing
it.
So,
thank
you
very
much
for
again
making
me
look
good
and
the
key
takeaway
is,
if
I'm
uncomfortable
talking
about
it.
It's
probably
a
good
first
iteration.
C
C
And
I
think
the
link
may
be
wrong.
Okay,
in
the
thing
you
linked
to
just.
G
Fyi,
I
probably
still
had
it
on
my
clipboard.
I
need
a
clipboard
manager
with
all
the
copy
and
paste
into
yes,
okay,
the
there
is
a
there's,
a
link
to
an
mr
that
should
update
the
handbook
and
then
the
mr
that
they're
linking
to
is
the
release
post
item.
So
I
I
will.
I
will
draft
an
mr
for
the
handbook
to
make
sure
that
it
links
to
the
mr
of
the
iteration
and
not
just
my
my
release
post
item,
but
thanks
for
catching
that
yeah
so
great
job.
G
The
next
one
is
a
conversation
I
wanted
to
highlight.
On
slack.
G
We
don't
have
like
immediate
action
that
we
need
to
take
on
this,
but
it
was
an
interesting
use
case
for
the
gitlab
handbook.
Anyway,
we
have
a
custom
helper
for
our
performance
indicator
files,
which
are
a
list
of
yml
files,
data
files
that
it
looks
like
there's
a
ruby
helper
for
that
you
just
feed
it
which
file
and
it's
going
to
embed
the
properly
formatted
performance
indicator
page.
G
This
kind
of
goes
back
to
what
we
were
talking
about,
but
with
maybe
using
snippets
as
reusable
custom
content
blocks,
or
something
like
that.
This
would
be
a
much
more
advanced
use
case
than
I
was
discussing
before,
but
basically
sid
was
looking
for
a
way
to
link
between
the
handbook
page,
where
you're,
using
this
helper
and
saying,
show
the
performance
indicator
for
sales
and
then
find
a
way
to
actually
jump
to
that
yaml
file
to
edit
it,
whether
that's
in
the
static
site
editor
or
in
the
web,
ide
or
whatever.
G
I
don't
think,
was
as
important
as
being
able
to
create
a
link
between
those
files.
We've
talked
about
concepts
for
partials
and
includes
and
components,
and
all
these
different
words
for
reusable
content
within
the
static
site.
Editor,
but
just
keep
this
on
your
radar.
It's
possible
that
we
have
a
use
case
that
isn't
even
relevant
to
the
rest
of
the
community
and
external
users,
and
this
might
be
something
we
just
need
to
build
a
custom
solution
for
how
we
use
our
handbook.
G
But
we
should
think
about
it,
see
if
there's
any
way
to
abstract
this
and
make
make
it
possible
for
things
like
that.
You
know,
like
this
use
case,
to
exist
in
a
way
that
other
people
could
get
value
from
it.
We
don't
need
a
solution
for
it
right
now,
but
if
you
have
any
thoughts,
you
can,
let
me
know
or
I'll
pause
and
if,
if
anybody
has
any
ideas
on
how
we
can
fix
it,
we
can
we
can
talk
a
little
bit
about
it
now.
B
I'll
just
add
I'm
solutioning
here
basically,
but
if
we
know
that
we're
have
a
template
link
somewhere
within
our
markup,
we
could
basically,
you
know,
save
that
url
and
then
somehow
save
it
as
a.
I
think
I
kind
of
mentioned
this
somewhere
recently
too
solving
something
similarly
and
have
like
a
data
attribute.
That's
a
special
data
dash
attribute
and
then
just
on
the
front
end.
G
Yeah
yeah,
I
remember
you
talking
about
that.
So
in
this
case
we
would,
when
forming
the
link,
so
in
the
helper,
we'd,
probably
add
the
attribute
tag
or
where,
where
would
we
determine
the?
G
B
A
B
B
G
What
I'll
do
is
create
an
issue
around
this
specific
use
case
and
we
can
see
if
we
can
have
a
conversation
about
whether
or
not
there's
a
general
solution
or
or
we
can
have
whatever
helper
was
written
to
generate
these
pages
pass
the
data
into
the
statics.
I
editor
in
a
way
that
is
fairly
low.
Friction
for
us
to
solve,
but
for
context.
These
pages
are
fairly
useless
when
you
open
them
up
in
the
static
site
editor
because
it's
the
title
and
then
it's
a
block
of
non
markdown
content.
So.
D
G
Very
useful,
so
that's
yeah
I'll,
create
an
issue.
We
can
chat
about
it,
no
immediate
disruption
to
planning
or
priority.
So
this
isn't
a
fire
drill
or
anything
I'll,
be
wrapping
up
the
13.5
planning
and
recording
a
kickoff
video
later
this
week,
so
I'll
be
trying
to
actually
get
some
issue,
refinement
done,
which
leads
me
to
my
second
or
my
fourth
point,
which
is
this
is
the
busy
week
for
release
post
managers
and
I'm
a
release
post
manager.
G
G
A
Thank
you
eric
right,
everybody.
That
brings
the
end
our
agenda.