►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
B
This
is
the
static
site
editor
weekly
group
chat.
This
is
the
engineering
edition
and
let's
get
going
so
on
the
general.
I
just
want
to
remind
everybody.
We
don't
have
any
more
issue
refinement
sessions.
This
month,
they've
been
replaced
by
okr
hackathon
sessions.
Thank
you
again,
chad
and
lucille
for
joining
today's
session,
and
in
recap,
you'll
see,
there's
a
few,
mrs
for
you
to
review
that
we
got
through
so
hopefully
a
few
more
tooltips
will
be
converted
shortly
right.
B
Let's
get
into
the
static
site,
editor
section,
so
derek's
not
he's
on
pto,
so
I'll
quickly,
just
highlight
his
section.
He,
the
the
merge,
request,
title
description.
Uri
is
actually
on
production
at
the
moment,
so
you
can
play
with
it
and
eric.
I
was
thinking
it's
probably
worth
doing
a
shout
out
in
what's
happening
channel
because
I
know
a
bunch
of
people
were
asking
for
this.
So
that's
nice
to
see.
A
B
C
I
share
the
links
of
the
merch
request,
where
I
included
that
report
answering
some
of
the
evaluation
criteria,
the
that
we
defined
in
in
our
last
issue
requirement
session,
and
there
is
also
a
link
to
the
review
app
where
you
can
play
with
the
demos
I'm
gonna,
be
I'm
gonna
create
a
calendar
event
with
a
zoom
room
tomorrow
at
9
00
am
atlantic
time.
This
is
the
same
hour
of
our
issue
refinement
session.
C
If
you
want
to
join
and
ask
any
question,
please,
I
I'm
gonna
be
very
happy
to
discuss
this.
B
Cool,
so
for
anybody,
that's
that
needs
that's
yeah.
It's
a
normal
1,
1
pm,
utc
time
slot.
I
think
that's
somewhere
early
morning,
for
you,
chad,
probably
about
five
or
six
so
probably
to
anybody
anyway.
Yeah
thanks
for
that.
Enrique
I'll
have
a
look
at
that
and
make
sure
that
I'm
prepared
for
tomorrow's
session
as
well
all
right
chad.
Can
you
give
us
an
update
on
the
configuration
file
stuff.
D
So
all
of
the
functionality
to
support
the
config
file
entries
is
merged
and
as
discussed,
I
made
a
documentation.
Mr
it's
a
document
of
it
and
marcie
ramos
commented
said
we
should
not
document
that
stuff
until
it's
actually
ready,
because
I
had
notes
in
it
saying
this.
Config
file
option
is
here,
but
it
doesn't
do
anything
yet.
D
So
we
should
probably
discuss
and
keep
that
in
mind
for
future
reference
to.
Unless
something
is
actually
functional,
then
we
don't
document
it.
B
Cool,
so
I
assume
we
can
officially
now
say
that
the
image
upload
work
is
now
unblocked
and
that
we
can
move
ahead
with
that
right.
B
E
Yeah
for
handbook,
I
was,
I
improved
our
handbook
later,
a
bit
so
ex
extended
amount
of
cases
it
it
can
detect.
Now
and
today
morning.
My
time
I
merged
these
changes,
so
it
hopefully
will
decrease
an
amount
of
broken
links
that
we
have
in
handbook
because
it
will
start
notifying
people
about
these
cases.
E
Yeah
forgitlab
docs
all
documentation,
url
related
things
were
merged,
so
I
was
planning
to
go
forward
and
actually
enable
this
functionality
today.
E
But
like
just
half
an
hour
ago,
I
learned
that
I
need
to
create
a
special
issue
to
request
this
kind
of
official
change
to
the
settings
of
the
gitlab
main
instance,
and
I'm
planning
to
do
it
tomorrow
and
hopefully
I
don't
know
how
long
this
process
takes.
But
I
don't
think
it's
something
really
that
takes
lots
of
time
so
yeah,
probably
tomorrow
it
will
get
go
live
and
we
will
start
redirecting
users
to
docs
hit
laptop.
B
Cool,
that's
exciting,
to
see
that
moving
forward
a
quick
question
on
the
the
offline
documentation
which
this
functionality
is
a
precursor
to.
Is
there
any
further
input
we
need
on
that
before
you
can
start
planning
and
getting
your
stuff
ready
for.
E
E
I
think
I
will
probably
think
about
it
a
bit
more
and
if
I
haven't
find
a
better
solution
that
works,
then
we
will
proceed
with
that.
So
and
in
terms
of
the
moving
forward
with
the
first
solution,
it
seems
to
be
clear,
so
I
know
who
to
contact
like
from
the
delivery
team.
Who
can
assist
me
with
that?
If
I
have
any
questions,
I
just
need
to
read
about
services:
read
about
how
to
add
a
new
service
to
our
stack
and
how
to
ship
it
as
a
part
of
the
package.
B
F
Yeah
this
week
we
want
to
launch
webpack
to
build
just
our
style
sheets.
Instead
of
middleman,
we
decided
to
take
an
iterative
approach
to
adding
webpack,
so
first
doing
the
style
sheets,
and
then
we
can
solve
for
edge
cases
and
monitor
that
once
it
goes,
live
and
then
adding
javascripts
and
then
finally
migrating
our
roll-up,
bundling
of
view
components
over
to
webpack
like
to
get
that
out
the
door
today.
So
we
can
monitor,
monitor
it.
B
D
A
review
on
that
do
you
want
me
to
I
could
get
to
that
this
morning.
D
F
F
It
was
yeah
yeah
because
splitting
it
up
like
that,
it
adds
some
extra
ci
jobs,
so.
B
Nice
looking
forward
to
that
all
right
and
then
over
to
eric
with
product
update.
A
Yeah
thanks
so
last
week
I
was
focused
on
trying
to
plan
for
13.6,
which
is
a
lot
more
complicated.
Now
that
we
have
settings
and
nav,
so
I
was
trying
to
dig
into
that
the
settings
in
nav
work,
though
I
I
think
I
was
able
to
identify
a
few
issues
that
are
well-known
enough,
understandable
enough
and
we're
confident
enough
that
it
needs
to
be
done,
that
we
don't
need
to
take
this
into
ux
research.
A
I'll
talk
more
about
that
with
michael
and
and
hopefully
catherine
will
join
on
our
our
design
product
call
later
today,
but
the
gist
of
it
is
the
the
ones
that
I
picked
are
either
known
bugs
or
inconsistencies
with
the
navigation
and
settings
experience.
I
think
it'd
be
good
to
dive
in
so
I'd
like
to
go
ahead
and
carve
out
some
time
in
13.6,
we'll
review
the
issues
and
and
share
those
specific
links
with
you,
so
you
can
see
which
ones
I'm
talking
about,
but
yeah.
A
This
will
be
the
first
milestone
where
we're
we're
picking
up
that
work.
I
don't
expect
huge.
You
know,
mrs,
to
drastically
improve
the
experience,
but
I
think
dipping
our
toes
in
and
getting
familiar
with
the
code
base
would
be
helpful.
A
The
other
things,
though,
that
we'll
focus
on
the
editor
architecture
is
clearly
our
top
priority
from
the
static
site,
editor
product
side.
I
think
moving
forward
on
that
full
steam
ahead
as
much
as
we
can
is
the
priority
for
13.6
there.
The
offline
docs
work
that
we
already
talked
about,
we'll
we'll
carry
that
forward
in
13-6,
hopefully
wrap
it
up
in
13-6,
and
then
I
lost
my
agenda
place,
yeah
carryover
of
image
upload.
A
So
now
that's
unblocked
the
I
did
I
almost
I
wanted
to
jump
in,
but
didn't
want
to
interrupt,
but
really
great
work
on
the
settings
stuff,
chad.
This.
It's
really
important
that
we
have
this
configuration,
and
I
know
it
was
very
complex,
but
it's
going
to
hopefully
unlock
a
whole
future
for
the
static
site
editor.
A
So
it's
a
pivotal
feature
that,
even
though
it's
mostly
behind
the
scenes
having
that
wrap
up
now
and
unblock
image,
uploads
is
great
and
it
will
inevitably
be
extended
in
the
future
for
for
any
number
of
customization
options,
so
really
really
excited
to
see
that
hit
and
image
uploads
we'll
wrap
that
up
in
13.6.
A
I
don't
want
to
overload
it
because
I
don't
know
how
much
the
settings
and
nav
stuff
is
going
to
take.
There
might
be
some,
you
know
roadblocks
and
minefields
that
we
have
to
navigate
there.
So
that's
that's
kind
of
what
I'm
thinking.
D
So
we
given.
D
Changing
the
setting
stuff
or
the
paper
file
going
forward
as
expected,
is
pretty
easy
to
add
and
change
things.
It's
declarative
in
the
config
file
api,
but
there's
still
some
more
thought
that
needs
to
go
into
that,
like
especially
like.
We
talked
about
the
mount
stuff
and
you
know
how
we
actually
want
to
implement
that
and
with
using
that
as
a
way
to
leverage
how
files
and
how
paths
map
to
actual
files
in
the
repo
and
duplicating
that
with
route
maps
and
stuff.
D
A
Yeah,
I
think
I
remember
seeing
a
follow-up
issue
that
you
made
about
the
routes.
Maybe
I
can
try
and
I
can
put
that
at
least
on
our
13
sticks
planning
spreadsheet.
If
we
have
time
to
look
at
it,
but
I'll
just
make
sure
that
it's
it's
clearly
defined.
That's
a
good
point.
We.
A
D
A
We
don't
want
to
overload
it
and
we
don't
want
to
make
the
the
wrong
decisions
in
the
settings
and
then
have
to
deprecate
things
a
bunch
in
the
future.
So
now
that
we
have,
the
power
doesn't
mean
we
need
to
abuse
it,
but
yeah.
That's
a
good
point
I'll
see.
If
I
can
I'll
see
if
those
issues
are
clear
enough
or
I'll
ping
you
on
slack.
If
not,
and
we
can,
we
can
round
that
out
with
the
mounts
and
any
of
anything
else
related
to
the
configuration
of
that
yeah.
A
So,
on
the
topic
of
the
re-architecture,
I
was
really
excited
to
see
the
proof
of
concept
enrique.
I
think
I
will
try
and
click
through
that
after
lunch
today
for
me,
and
we
have
a
meeting
with
the
ck
editor
team
to
talk
about
licensing
and
usage
on
thursday,
I
wanted
to
keep
it
small,
so
we
didn't
overwhelm
their
team
with
like
a
panel
discussion.
A
So
it'll
just
be
me
sean
and
enrique
if
they
can
all
join
but
I'll,
see
if
they're,
okay
with
us,
recording
it
so
that
we
can
share
it
around
internally,
at
least
the
the
main
goal
there
is
to
understand
their
licensing
and
whether
or
not
we'd
be
able
to
build
paid
features
on
top
of
ck
editor
or
use.
Ck
editor
in
our
paid
features
like
epics
or
you
know,
if
any
potential
feature
that
that
is
paid
in
the
future.
That
could
benefit
from
a
wysiwyg
editor.
A
If
there's
gonna
be
restrictions
there,
it
could
be
a
deal
breaker.
I
I
don't
know
what
the
kind
of
license
agreement
they're
going
to
want.
So
that's
what
the
discussion
will
be
about,
hopefully,
it'll
be
fruitful
and
they'll
be
enthusiastic
and
it'll
all
work
out,
but
we'll
report
back
and
oh,
the
other
thing
I
wanted
to
mention
is-
I
think
I
was
digging
through
and
I'm
pretty
sure
I
know
the
answer
to
this,
but
ck
editor
4,
I
believe,
has
a
more
liberal
license,
but
I
don't
think
it's
as
feature
rich.
A
A
Enrique,
did
you
happen
to
see
any
of
that?
No.
C
I
I
don't
know
how
house
gate
report
is
architecture,
but
I
think
that
they
put
a
significant
report
into
making
cke
ck,
8
or
5
to
separate
they
separated
the
data
into
two
parts.
They
have
a
preview
version
of
the
editor
that
are
feature
reached,
and
you
just
you
can
just
embed
it
in
in
your
application
and
then
they
create
that
framework.
That
is
what
we
are
going
to
actually
use
and
it's
what
allows
us
to
implement
plugins,
to
extend
the
functionality
and
support
new
content.
A
A
If
that
framework
is
feature
rich
enough
for
us,
then
that
might
be
an
option,
but
I
have
a
feeling
it's
not,
and
I
wouldn't
want
to
necessarily
go
down
in
a
major
version
if
we
have
a
perfectly
viable
other
opportunity
with
tiptop
or
pros
mirror,
or
something
like
that,
so
yeah,
hopefully,
it'll
be
a
good
conversation
and
we'll
report
back
on
thursday
afternoon.
B
The
last
thing
I'll
add
there
is
just
that
ck
editor
for
only
has
support
until
2023.
So
that's
something
to
keep
in
mind
as
well
with
that
type
of
decision,
so
yeah.
D
B
It's
you
know:
they've
put
a
it's
clear
that
they've
put
a
lot
of
development
time
and
effort
into
ck
editor
five,
so
one
can
only
just
expect
that
they
will
continue
to
push
that
forward,
and
you
know
considering
that
ck24
was
has
been
up
and
about
since
2012.
It
was
probably
time
for
it
to
be.
Someone
said.
A
Yeah
yeah,
the
probably
not
the
best
choice
to
choose
for
just
for
the
license,
but
yeah
we'll
we'll,
hopefully
come
out
the
other
side
of
this
meeting.
With
with
a
clear
understanding
of
their
license
expectations.
I
don't
think
that
we're
entertaining
a
paid
license
at
this
point
for
it,
but
we'll
have
a
lot
more
information
to
have
that
conversation.
A
So
the
last
item
that
I
had
on
the
agenda
was
related
to
prod
ops,
product
operations.
So
vasily
we
had
discussed
putting
that
automated
content
assembly
for
the
release
post
back
on
the
pipeline
for
the
18th
to
run.
I
think
we're
all
good
with
that.
Tao
is
the
release
post
manager
for
13.5.
A
She
was
shadowing
me
in
1304
and
she's
comfortable
with
letting
it
run
and
seeing
what
happens
but
then
being
prepared
with
a
you
know,
manual
running
the
script
manually
if
it
doesn't
work
so
whatever
we
need
to
do
to
get
it
back
on
the
pipeline
I'll
confirm
with
her
and
we'll
be
able
to
try
that
out
over
the
weekend.
A
Awesome
done
all
right
didn't
even
need
to
make
a
to-do,
so
I'll
confirm
with
her
that
she's.
So
she
knows
what's
gonna
happen
and
then
maybe
we
can
just
a
quick
write-up
of
like
what
she
would
have
to
do
if
it
would,
if
it
failed,
which
branch
to
delete
or
which
you
know
which
commits
to
revert
something
like
that
yeah.
That's
it
for
me.