►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
Today
we
are
going
to
be
focusing
specifically
on
just
checking
in
on
the
remaining
issues
for
13.1,
as
well
as
having
a
look
at
our
staging
points
to
plan
B
issues
as
we
as
we've
done
last
time,
we're
going
to
do
the
small
something
again
way.
The
week
before
the
mouseland
starts,
we'll
be
focusing
specifically
on
making
sure
that
our
issues
for
30.2
have
been
fought
through
that
we've,
given
it
the
necessary
attention
from
a
product
feature
point
of
view
of
understanding
what
it
is.
A
We
need
to
do,
having
any
conversations
around
misunderstandings
or
looking
at
scope,
how
we
can
break
things
down
to
be
more
iteratively
as
well
as
validating
any
technical
approaches
that
we
might
want
to
validate.
So
that'll,
be
our
main
focus
for
this
week
as
well
as
well
as
wrapping
up
the
remaining
13.1
issues
before
we
look
at
the
34
in
one
issues,
I
want
to
just
reiterate
again
that,
while
we
speak
in
terms
of
milestones,
7.14
in
brain
2
and
so
on,
that
is
to
to
create
a
an
understanding
from
from
a
group.
A
In
point
of
view,
when
it
comes
to
actual
delivery,
we
discussed
that
last
time
and
and
I
want
to
reiterate
it
that
we
do
not
try
and
rush
things
into
a
specific
milestone.
If
there's
a
reason
that
can't
be
made,
whether
it's
personal,
that
you
just
needed
more
time
to
yourself
or
things
that
needed
to
be
done
or
the
development
took
longer,
that
is,
okay,
we
are
not
in
the
business
of
trying
to
rush
features,
are
to
make
a
mouse
and
deadline
we're
in
a
position
where
our
product
is
primarily
sole
using
get
calm.
A
We
and
we
need
to
rather
focus
and
continuously
we
just
keep
pushing
out
the
features.
That's
that's
my
arts
that
we
don't
I'll,
try
a
space
as
possible
to
keep
that
I
know
it
can
become
freezing
as
we
talk
in
terms
of
milestones,
but
think
of
our
talking
of
milestones
more
just
from
it.
A
planning
and
grouping
in
focusing
point
of
view
rather
than
a
this
is
a
deadline
that
has
to
be
made
by
meet
met
by
wall.
A
Only
thing,
the
purpose
of
recording
it
clearly
to
have
to
work
later
or
longer
hours.
That
is
not
the
intention
of
that.
It's
more
just
to
Craig,
focusing
on
a
batch
of
food,
particularly
planning
around.
That
said,
I
will
admit
that
there
are
some
you
know
like.
If
you
look
at
the
source
code,
for
instance,
you
know
that
one
of
the
core
elements
of
the
get
led
product
with
a
lot
of
people,
that
in
self-hosted
environments
that
use
it.
If
there's
a
bug
and
something
like
that
that
might
be
holding
somebody
up.
A
That's
when
we
get
kind
of
like
specific
about
shipping,
something
you
know
for
a
specific
Mouse
and
whether
that's
a
patronage,
social
security
fix
or
or
or
next
milestones
and
so
on,
but
while
we're
still
early
on
in
our
product
development,
that
should
not
be
our
focus
yet
and
I
will
clearly
communicate
if
there
is
a
specific
issue
that
has
priority
focus
needed
to
be
made
by
a
certain
time.
So
unless
that
is
clearly
stipulated,
you
can
assume
that
you
know
we'll
just
focus
on
a
continuous
delivery
point
of
view.
A
A
A
All
right
so
only
add,
mark
and
formatting
shortcuts
in
the
static
site,
editor,
so
doc.
I
know
you've
done
a
whole
bunch
of
stuff
in
is
gonna
Reich
us
Enrique
and
Barry
I'd
appreciate
it.
If
you
can
just
have
a
look
at
explaining
that
he
did
and
just
see
if
you
have
any
concerns
with
it
and
if
you
can
just
kind
of
like
flag
it.
A
A
Right
in
the
next
one,
I
am
Vasily,
I.
Think
I,
actually
just
saw
notification
come
through
earlier
just
before
the
school.
That
of
your
first
summary
of
this
so
I'm
gonna
ask
the
whole
thing
to
also
go
and
have
a
look
at
this
and
just
go
and
review
the
silliest
initial
writer
and
let's
see
if
we
can
get
some
feedback
thing,
that's
leaked
on
that.
C
A
A
A
All
right
next,
one
we
have
here
was
another
stretch,
a
dreary,
dependencies
fashion
for
the
static
side,
with
a
template
I'm
actually
not
too
worried
about
the
stretch
once
I'm
actually
going
to
pull
to
them
up
like
now.
We
don't
need
to
have
a
look
at
them,
because
if
they
were
importing
that
we
included
in
the
certainty
plan
already
all
right,
remove
the
Emerald
front
medic
from
editable
content,
so
that
is
still
in
progress.
E
A
So
so
that's
fine,
the
ripped,
the
release
post.
I
know
this
features
live
the
release.
Those
we
just
need
to
technical
writer
to
give
the
final
okay
I
know:
that's
been
written,
it's
done
so
I
think
we
can.
We
can
probably
and
I
have
verified
it
as
well.
So
we
can
close
this
one,
because
the
word
close
then
and
and
you've
added
it
to
to
the
change
look.
So
we
call
close,
doesn't.
E
E
C
A
That's
good,
alright,
there's
a
follow
up
here:
resolve
remove
old
friend,
again
yeah.
E
E
E
A
C
E
A
And
it
is
a
review,
so
that's
all
good
all
right
that
scares
us
at
for
this
one
we
go
back.
The
next
thing
we
want
to
do
is
have
a
look
at
our
13.2
appalling
issues,
so
business
all
right,
so
I'm,
I'm,
you're
gonna
cover
the
p1
and
p2
s
today,
big
the
P
freeze,
you
know,
literally,
if
we
have
all
that
work
is
blocked
again.
A
Overarching
theme
for
thirteen
point:
two
is
getting
the
static
site,
editor
integrated
into
the
handbook.
That
means
wrapping
up
the
non
markdown
display
of
content,
as
well
as
the
the
image
uploading
that
job
will
be
focusing
on
and
then
any
other
work
that
needs
to
be
done
to
make
it
work
together.
So
just
I
mean
look
at
this
issue.
A
I
know
you've
identified
all
the
various
kind
of
clinic
flavors
or
things
that
we
should
be
accounting
for
at
this
point,
do
you
feel
that
these
issues
for
for
the
the
implementation
do
they
require
any
further
work
to
get
them
ready
for
development?
If
near
the
initial?
Mr,
that
gives
us
the
infrastructure
and
the
framework
for
how
to
deal
with
the
clients,
yeah.
E
So
the
cramdown
one
is
the
one
I
did
this
milestone
and
that
also
did
kind
of
the
groundwork.
If
you
will
so
that's
the
one
we
just
talked
about
in
terms
of
the
review,
I
need
to
do
and
then
the
other
four
are
already
slated
for
as
implementation
issues
for
13.2.
So
I'm
not
really
sure
how.
If
we
want
to
check
all
these
boxes
off,
except
they'll
handle
the
cram
down
one
once
it's
actually
once
I've,
actually
done
that
or
I'm
not
sure
how
you
want
to
track
that.
But
now.
A
So
I
think
in
terms
of
this
issue,
we
we
can.
You
know
this
is
our
feature
issue,
so
we
can
use
this
as
the
overall
feature
and
leave
it
open
until
all
of
these
are
implemented.
That's
my
question,
then,
in
terms
of
the
the
individual
implementation
issues,
for
these,
do
you
feel,
like
you,
have
a
good
handle
in
terms
of
what
needs
to
be
done,
or
is
there
more
work
to
be
done
to
explore
them
in
terms
of
getting
them
ready
for
development?
No.
E
D
A
E
A
Know
that
point
all
right
right.
So
this
issue
is
it's
basically
the
the
big
overarching
issue
for
for
the
future
of
landing
the
the
hand
the
static
sighted
of
the
integration
of
the
handbook.
So
what
I
want
to
make
clear
is
we're
not
integrating
with
the
full
handbook,
yet
we're
only
going
to
make
the
static
site
editor
link
accessible
for
the
product
section.
That
doesn't
mean
we're
gonna
block.
A
If
somebody
wants
to
add
a
URL
to
a
different
page
in
there
and
get
you
will
allow
that
we're
not
going
to
do
any
validation
to
restrict
it,
but
we
are
only
surface
then
the
Edit
link
in
the
UI
for
for
the
product
section
there's
enough
of
a
variation
of
the
content
in
product
that
allows
us
to
taste
a
lot
of
fringe
cases
and
so
on
and
where
I
expect
Moe
of
our
our
work
will
be.
You
know
once
we've
implemented.
All
the
hanging
of
the
different
content
is
fringe.
A
Cases
like
you
know,
like
things
that
are
written
slightly
differently
or
so
on.
So
I'm
sure
that
things
will
come
up
in
Ruby
case
is
kind
of
like
gonna,
be
our
a
quarterback
for
this
milestone.
He's
gonna
be
the
one
that
keeps
an
overall
view
on
the
integration
of
the
static
site,
editor
with
Vista
handbook,
and
that
means
he
could
jump
in
on
issues
on
the
handbook
to
help
out
anybody
there
or
he
can
jump
in
on
issues
from
product
to
help
out
there.
A
Please
raise
your
hand
and
getting
to
our,
but
we
where
he
can
that's
his
task
for
for
this
milestone
and
I've
already
spoken
to
him
and
he's
he's
keen
to
take
on
that
challenge.
So,
let's
see
how
this
works
for
us,
and
if,
if
this
is
a
kind
of
like
a
model
that
works
for
us,
maybe
we
can
utilize
the
downline
on
some
other
things
as
well.
A
All
right
up
there
mean
image
using
a
static
site
editor,
so
I've
spoken
with
Jacque
earlier
today
about
this
I
think
it's
fairly
clearly
defined,
and
we
have
some
some
initial
folds
around.
You
know
things
that
we
won't
do
I
know.
Mike
Jacques
also
asked
Michael
to
come
back.
Do
a
bit
of
a
mock
up.
There's
also
been
some
initial
planning
done
on
this,
so
I
feel
like
this
is
fairly
well
developed
in
terms
of
getting
it
to
ready
for
development.
A
A
The
next
one
is
the
mana
repair
factor.
I'll
just
stick
for
chat
on
this
one.
So
if
you
go
and
have
a
look
at
this
there's
two
main
streams
of
work
on
the
mono
repo
refactor,
the
the
first
one
that
we
are
very
close
to
being
finished
is
separation,
creating
separate
Speyer
projects
in
the
in
the
repo.
So
the
handbook
we
started
with
the
handbook,
the
block
was
already
there.
A
We
revisited
the
approach
we
took
with
with
the
blog,
and
so
we're
almost
done
with
refactoring
that
and
so
we'll,
probably
even
off
with
with
the
the
separation
stream
of
the
the
refactor
in
the
next
week
or
so,
and
it
mostly
revolves
around
moving
the
remaining
sections
of
their
handbook
into
their
new
site
as
well
as
reworking
the
Simulink
approach
with
the
blonde
and
I
know.
Chad
spent
some
time
in
that
recently
and
he's
got
a
working
solution
going
for
that.
A
That
way,
we
can
proceed
with
as
much
as
possible
of
as
little
as
possible
interference
from
from
the
various
sites
working
on
each
other,
and
we
can
then
also
have
a
more
focused
approach
on
optimizing
the
pipeline
for
the
handbook
going
forward.
So
that's
what
we'll
be
doing
there
then
Doc's
linter.
A
C
The
problem
is
clear:
I
can
read
the
task
and
it's
pretty
clear:
what's
I
need
to
do
I
need
to
take
a
deeper
look
into
the
implementation
like
how
exactly
and
maybe
there
are
some
like
small
details,
but
I
might
have
question
about
them
like
later,
but
so
far,
I
think
it's
like
crazy,
like
on
there
there's
a
big
picture.
It's
pretty.
A
Okay,
it's
also
one
that
we
will
want
to
bring
this
functionality
into
the
handbook
at
a
later
point
right
now,
we're
doing
it
in
the
get
let
the
docs
project,
but
eventually
we
want
a
similar
there's.
A
lot
of
links
in
the
handbook
that
link
to
specific
anchors
in
the
in
there
and
I
know
for
a
fact
is
a
bunch
of
broken
ones,
because
I've
recently
found
them,
and
it
would
be
really
good
to
have
this
functionality
in
the
handbook
as
well.
Some
really
important
work.
They
need
to
do
that.
A
A
And
you
go
to
mop
down
mode
so
that
this
has
more
of
a
look
at.
It
was
a
Rick
Stengel
is
me
today
so
totally
of
the
air.
It
is
the
Ross
also
for
now.
Its
purpose
is
to
ensure
that
any
content
of
the
page
editor
committed
in
some
fashion.
So
currently
the
content
is
styled
with
some
amounts
of
rich
formatting.
So
it
is
a
ball
and
it's
confusing
to
have
the
HTML
styling
applied
to
the
source.
So
essentially,
what
we're?
A
But
what
we
want
to
achieve
here
is
not
to
have
the
mark
down
south
in
markdown,
especially
the
headings
new,
but
rather
to
have
everything
as
as
like
a
code
font
and
single
Heights,
and
so
I'm
hoping
it's
as
simple
as
overriding
styling.
But
that
is
a
very
simplistic
view
of
a
solution
and
it
might
not
be,
but
does
that
give
you
these
confidence
in
terms
of
what
you
need
to
achieve
reference?
A
E
A
A
A
Next
up,
we
have
improving
the
the
information
architecture
and
styling
of
the
success
screenings
that
excited
at
their
so
Enrique.
This
one
is
on
you
and
we
have
some
designs
in
here
that
that
Michael,
ladies
updated
it
based
on
the
feedback
that
we
really
gave,
but
you
can
have
a
look
here,
essentially
we're
they're,
taking
away
this
summary
of
change,
which
isn't
adding
a
lot
of
value,
especially
to
a
non
engineering
member
and
it's
not
really
aligned
with
where
we
want
to
go
with
our
product,
and
it's
it's
talking
about
kind
of
like.
A
Are
we
just
kind
of
like
reach?
Ange,
it
I
think
what
we
this
is.
The
one
way
we
had
met
in
the
discussion,
but
we
might
just
need
to
do,
is
to
confirm
with
Michael
that
the
latest
version
that
incorporates
all
the
feedback
has
been
is
finalized
on
this
one.
So
things
because
I
think
from
a
iteration
point
of
view,
I
also
say
to
me
like
we
can,
just
we
don't
want
to
start
with
I'll
choose
this
tiny
on
this
page.
We
just
want
to
change
the
information
reputation
and
make
make
it
eat
clear.
A
What
next
step
is
so
I
think
this
one
looks
like
it
needs
a
little
analyzation
of
the
of
the
final
layout
and
design
de
we
and
copied
it
in
cedar,
but
I
think
from
unclever
all
what
we
need
to
do.
It
seems
clear
that
it's
ready
for
development
from
a
you
know.
We
need
to
change
we're,
not
we're
not
changing
the
functionality,
we're
changing
the
content
and
the
computer
of
the
page.
Would
you
agree
with
that?
Enrique.
A
Next
up,
we
have
using
the
wizard
editor
on
mobile
causes,
inconsistent
jump
to
top
behavior.
So
this
is
one
that
we'll
try
and
tackle
in
this
release,
because
it
is
quite
a
jarring
experience
from
user
experience.
Point
of
view
in
mobile
and
well
is
a
valid
use
case
for
our
editor.
So
we'll
have
a
look
at
that.
This
one
is
really
for
development,
because
it's
more
a
case
of
just
getting
into
and
fixing.
C
A
Links
from
the
handbook,
so
if
we
go
to
book
page,
the
difficulty
is
that
you
have
to
go
all
the
way
to
the
bottom,
to
find
it
yet
now
in
in
in
a
very
soon
iteration.
As
soon
as
I
think
this
emerges,
their
exam
I
will
have
the
maintain
by
section
Year
at
the
top,
and
the
idea
is
that
we
add
those
links
to
edit
the
page
just
below
that
I.
A
Don't
think,
we've
done
a
design
yet
for
this
I
also,
don't
think
we
really
needed
one
I
think
we
can,
because
it's
a
simple
one
where
you
can
add
the
links
to
that
section,
and
we
can
ask
Michael
to
have
a
look
at
it
in
the
reveal
that,
rather
than
waiting
on
the
divine
for
that,
would
you
agree
with
that
or
you
comfortable
that
it's
ready
for
development.
In
that
sense,
yeah.
A
A
Check
that
code
owners
are
valid
user
internal
groups,
it's
in
the
ceiling,
I
know
we
talked
about
this
one
specifically
around
how
we
want
to
pretend
she
use
the
validation
that
they
all
people
the
in
get
left
of
product
to
validated,
but
for
now
the
first
iteration
will
do
a
kind
of
like
a
light
validation
around
this
is
they
need
further
kind
of
like
the
information
you
need
before
we
can
classify
this
one.
It's
ready
for
development.
C
So
I
think
it
depends
if
this
issue
is
like
to
provide
the
full
validation
that
I
need
to
wait,
because
I
want
to
check
with
Carrie
and
she's
on
vacation
this
week
to
figure
out
like
who
is
working
on
what
and
if
I'm
gonna
take
all
these
validation
stuff
on
the
github
site
or
she's
gonna.
Do
it,
and
so
yes,
if
it's
like
light
meditation,
then
yeah
there
is
no
blockers.
A
Yeah
I
think
we
should
update
this
to
to
be
a
light
validation
rather
than
foolish
I.
Think
we
should.
We
should
definitely
align
with
the
validation
that
they
want
to
have
to
get
that
product
and
do
that
as
an
iteration.
So
I
think
we
definitely.
We
should
go
with
an
initial
version,
and
maybe
we
can
never
look
at
the
the
requirements
and
so
I'll
leave
this
one
in.
A
I'll
work
with
you
so
that
we
just
verify
the
requirements
for
what
we
want
to
achieve
in
the
light
version
of
the
validation
all
right,
then,
we
have
show
last
updated
information
and
link
to
page
history.
So
this
is
one
I
believe
we
we
looked
at
previously
and
we
can
run
into
some
issues.
What
we
want
to
do
is,
in
addition
to
to
kind
of
like
showing
the
maintained
buyers.
A
History,
so
you
think
she
will
give
you
the
commit
history
of
the
file,
so
it
will
be
a
link
through
to
the
git
init
product.
So
that's
one
part
of
it
and
the
other
part
is
just
assured
lost,
updated
date
and
we
discussed
if
we
can't
get
the
full
kind
of
like
history
for
followers
updated
long
ago.
We
might
exclude
it
but
and
we'll
show
the
the
most
updated
date
for
for
the
ones
where
we
are
confident.
A
A
We'll
welcome
missing
that
dissolve
it.
Alright
next
is
improving
the
offline
documentation,
experience
poor.
They
get
instances
little
more
of
a
there's,
not
actually
implement
this
one.
We
was
just
gonna.
Do
some
initial
Rd
the
seen
a
jerk
and
I
made
last
week
to
have
a
synchronous
discussion
about
what
it
is
that
what's
the
challenge
and
what
our
options
are
some
clarifying
questions.
We
got
some
initial
answers
to
that,
so
I
think
right
now.
What
we
need
to
do
is
revisit
our
initial
kind
of
like
assumptions
and
factoring
these
answers.
A
I
personally
feel
it
still
leans
more
to
a
a
more
enhanced
embedded
code.
Slash
health
of
the
docs,
rather
than
including
the
docs
in
it.
So
we'll
have
to
look.
Searches
is
still
an
issue
and
especially
because
the
the
gitlab
elasticsearch
isn't
available
on
all
versions
of
the
product
it
states
I
mean
if
paid
for
once.
So
that's
something
we
need
to
consider.
A
A
Alright,
and
with
that
we've
covered
all
of
our
key
ones
and
Peter's
I'm
not
gonna,
go
into
the
P
field
as
I
mentioned.
These
are
are
ones
that
will
only
look
at
and
and
get
to
if,
if
we
run
into
some
other
work
or
if
we
have
some
available
time
and
we
can
be
efficient,
they're
mad
at
the
later
stage.
A
So
with
that,
we
come
to
the
end
of
this
section
where
we
wanted
to
review
and
just
remind
our
focus,
is
this
week
is
getting
kind
of
like
clarity
and
confirmation
that
we
have
what
we
need
to
be
able
to
start
the
week
next
week
into
running
and
so
that
they
aren't
any
major
blockers.
If
we,
if
we
have
any
dependencies
on
Michael
it
surfaces
early,
so
that
he
can
look
at
that
this
week.
B
So
last
week
we
had
a
call
with
John
and
Chad
about
giving
shey's
no
get
her
on
boarding
sort
of
knowledge
on
better
merger,
Chris
reviews
more
context.
It's
not
just
a
human
lender.
Quality
Richard
Besser
views
so
recordings
available
there.
The
document
for
referencing
all
the
links
and
clicking
through
things,
is
right
below.
That's
it
before
me.
Thank
you,
John,
oh
right,.