►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
Hello,
everybody,
the
weekly
static
site,
editor
group,
call
this:
is
the
engineering
focused
one
and
I'm
gonna
get
straight
into
it.
Just
in
terms
of
we
normally
have
a
our
internal
deadline.
So
when
we
want
our
in
order
to
be
with
maintaining
and
merged
to
make
sure
that
you
meet
a
Muslim,
we
know
we
think
about
that
at
all
this
time.
A
There's
nothing!
Anyone
in
the
world
first
thing
to
worry
about
after
worry,
we're
going
to
make
it
on
what
also
a
product
is
I'm,
making
an
assumption.
I
need
to
check
the
data,
but
that
our
product
is
mostly
being
used
in
get
up
calm
if
it
is
being
used,
and
so
what's
the
fact
that
we're
deploying
daily
to
get
out
calm,
we
should
just
you
know
getting
to
continuous
delivery
mindset.
Just
keep
pushing
your
issues
through
and
not
worry
too
much
about
the
milestone
insult.
A
An
infra
milestone
is
important
both
from
external
communication
and
sitting
expectations
and
so
on,
but
I
don't
want
it
to
cause
renewed
pressure.
So
we're
not
talking
about
that
and
when
we
get
to
the
point
below
we're
going
to
talk
about
what
about
thirteen
point
two
and
what
we
might
want
to
carry
over
from
thirteen
point,
one
there's
no
shame
in
something
carrying
over
it.
Just
is
fact,
and
that's
it
right.
So
that's
it.
A
The
initiative
going
on
at
the
moment,
which
is
a
okay,
are
for
the
dev
section
due
to
which
I
would
want
to
give
you
all
an
opportunity
to
identify
any
issues
that
you
might
want
to
work
on
around
that,
and
so
once
I
get
all
of
that
info.
I'll,
add
it
twelve
thirteen
point
two
planning
sheet
and
Eric
inaudible.
They
circle
on
what
our
final
list
is
of
what
we're
going
to
aim
to
achieve.
A
In
thirteen
point
two:
we
want
to
keep
it
fluid
as
far
as
possible
and
not
be
a
little
committing
from
Oh
from
it.
The
liberal
point
of
view,
because
our
main
focus
for
thirteen
point,
two
we'll
be
integrating
with
the
handbook
we're
gonna
do
a
partial
integration
in
the
sense
of
we're
only
going
to
promote
it
on
a
subset
of
the
handbook,
which
is
the
product
section
in
engineering
well
in
engineering
products
and
so
slash
handbook,
slash
product.
A
But
so
what
we're
doing
is
we're
not
going
to
restrict
anybody
from
if
they
put
in
the
URL
from
for
another
handbook
page,
we
can
do
any
checking
for
that,
but
we're
certainly
not
gonna,
be
advertising
the
link
on
the
page
outside
of
the
product
section.
So
why
products
entry,
because
we
don't
want
a
thousand
people,
giving
us
feedback
at
the
same
time,
while
they're
showing
up
there'd,
be
iterations,
also
they're,
a
good
person.
That's
you
know.
Most
product
managers
that
give
that
are
awfully
technical
I
have
a
good
understanding
yet
on
necessary
code
writers.
A
So
they're
gonna
over
analyze,
an
issue,
yet
they
might
likely
give
us
enough
feedback
where
we
don't
have
to
spend
a
lot
of
time,
trying
to
figure
out
what
the
person
was
trying
to
do
just
to
understand
their
feedback.
So
we
feel
it's
a
good
target
market
to
pitch
that
excited
that
they're
to
first
up
and
then
but,
like
I,
said
we're
we're
not
going
to
restrict
access,
we're
just
limiting
how
wide
we
broadcast
it
and
make
it
easy
by
just
clicking
the
link.
A
Let
me
just
move
along
okay
and
then
you
doing
want
to
quickly
just
switch
to
this,
so
I'm,
mostly
quickly
going
to
talk
purpose
and
what
you
know
like
what
your
main
theme
is
for
so
far
that
you
think
you
know
and
remember,
as
I
said
it's
it's
totally
up
for
the
sooner.
This
is
still
what
we
haven't
finalized
anything
yet,
and
we
want
to
take
your
input
into
consideration
as
well,
but
Enrique
is
going
to
take
charge
in
terms
of
the
overall
integration
effort
with
off
the
handbook
in
the
static
site
editor.
A
So
you
know
I'm
tasking
you
to
say
you
know,
you
know
from
the
handbook
side
it
might
be
as
simple
as
adding
a
link
but
I'm
sure
we're
gonna
run
into
a
lot
of
edge
cases
and
and
scenarios
that
we
haven't
thought
about
that
we
need
to
handle
in
the
editor
on
our
side.
Now
that
doesn't
mean
he
has
to
go
and
physically
implement
all
those
edge
cases.
He
might
have
to
work
with
sure
to
finish
fix
it
or
with
Derek
or
whoever.
A
A
Also,
some
more
UX
enhancements
like
custom
troubles
for
window.
We
can
mob
gun
mode
and
then
also
having
a
look
at
a
bug
that
happens
on
mobile
run,
jumping
behavior
in
the
editor
that
is
from
now.
Primarily
your
focus.
So
you
know
the
image
uploading
is
is
a
big
part
of
of
hampered
usage.
That
will
be
your
largest
focus
there.
A
A
So
we've
we
see
this
actually
just
merged
the
email
that
introduces
the
the
maintaining
by
section
in
the
handbook
and
we'll
keep
iterating
on
that
by
surfacing
more
information
as
well
as
making
it
more
useful,
then
Vasily,
you
primarily
going
to
be
focused
on
further
handbook,
metadata
surfacing
as
well
as
linting
of
content
in
both
the
handbook
and
the
docs
project,
which
is
where
your
primary
focus
will
be
and
Chad
as
usual.
You'll
be
stuck
with
the
mono
repo
refactor
and
acting
that
East
forsook.
A
I
also
would
like
you
to
be
the
you
now
have
a
very
intimate
understanding
of
the
handbook
and
the
middleman
and
stuff.
So,
if
there's
anything
that
might
need
to
be
customized
or
configured
or
done
to
help
of
the
integration,
the
static
site
editor
that
you
be
the
primary
back
in
support
on
that
aspect,
so
that
that
kind
of
like
gives
everybody.
A
You
know
their
primary
focus
area
for
for
13.2
and
basically
what
we
all
do
now
is
we'll
look
at
what
you
have
identified
in
terms
of
carry
over
from
thirteen
point
one
as
well
as
things
that
you
might
want
to
additionally
focus
on
in
13.2
and
we'll
add
it
all
in
here.
We'll
review
it,
and
hopefully,
by
Wednesday
latest
we'll
have
a
probably
a
first
pass
at
what
the
final
list
will
look
like
any
questions
on
that
before
we
get
into
the
actual
issues
that
we
want
to
tackle.
In
addition
to
the
essentialist.
A
B
Now
that
we
we
have
a
lot
a
graphic
ul
API,
so
we
need
to
implement
some
reading
changes
in
this
area
site
editor
thanks
for
sailing
anyway.
That's
that's
awesome.
Work,
I,
think
that
we
should
replace
it
replace
a
REST
API
calls
in
the
client,
so
I
think
that
that
could
be
something
that
we
could
work
on.
C
A
Yeah
so
essentially
for
13.1.
What
we're
trying
to
do
is
get
the
the
framework
and
the
way
of
how
we
deal
with
non
modern
country
button-down,
and
then
you
notice
various
different
types
of
content
that
will
meet
you
in
cater
for
some
sack
of
I
know:
there's
no
one-size-fits-all
solution,
but
thumbsucker
t-shirt,
siding
for
a
single
content
type
dealing
with
that.
C
It
obviously
depends
on
which
one
you're
doing
but
I
think
they're
small
to
medium
basically,
HTML
might
be
large.
I
just
don't
know
what
the
scope-
and
that
is
as
I
kind
of
mentioned
in
our
one-on-one
and
I.
Basically,
because
we're
using
a
toast,
editor
and
toast
mark
has
the
ast
kind
of
built
in
it's.
Actually,
the
custom
renderer
approach
actually
is
fairly
straightforward,
which
is
pretty
handy
so
across
my
fingers
that
that
remains
true,
but
so
far
it's
pretty
straightforward.
C
A
Just
to
remind
on
everybody:
well,
we
don't
use
weights
or
capacity
planning
old
tracking,
but
we
but
I
am
using
t-shirt
sizing
guesstimates,
just
change
that
I
don't
overload
any
specific
individual
with
too
many
large
items
or
so
on.
So
there's
no
scientific
measurement
behind
us.
It's
all
got
based,
and
it's
just
to
make
sure
that
we're
it's
thing
sensible
in
what
we're
doing,
but
Seeley
you've
got
the
next
one.
D
Okay,
so
from
my
side,
while
I
was
working
on
this
GRI
phone
and
book
pages,
I
discovered
that
that
might
be
some
potential
improvements
to
the
state
that
we
have
right
now.
Example,
there
are
many
pages
that
missing
code
owners
and
one
of
my
ideas
was
to
identify
this
code
owners,
like
maybe
automatically
identify
them,
based
on
how
many
changes
a
specific
person
made
and
also
some
tags.
D
These
club
handles
are
incorrect
and
we
do
not
validate
them,
so
it
will
prevent
us
from
display
in
the
correct
avatar
of
the
user,
and
there
is
also
like
an
idea
to
introduce
this
validation
and
notify
users
if
something
went
wrong
in
terms
of
t-shirt,
size
effort
right
now.
It's
like
three
potential
improvements.
All
of
them
are
small,
so
in
general,
I
think
it
will
be
like
medium
task.
A
D
A
E
A
A
If
you
haven't
put
something
down
yet
this
is
not
lost
opportunity
to
do
so.
If
you
don't
have
something
yet
I
know,
some
of
you
have
just
come.
Online
chat
hasn't
have
enough
coffee
yet
to
be
properly
functioning
this
in
the
morning,
so
I'm
giving
everyone
giving
everybody
opportunities
till
tomorrow.
A
But
let's
talk
in
update
tomorrow
to
to
identify
any
specific
issues
you
want
us
to
to
focus
on
four
women
plan.
They
next
up
is
the
making
it
up
significantly
first
initiative.
So
a
whole
bunch
of
issues
and
epics
have
been
identified
of
how
are
things
we
can
do
to
improve
the
performance
of
cute.
Laugh,
calm
and
I
really
want
to
encourage
you
all
to
do
something
up
and
participate
in
there.
A
It
doesn't
mean
that
it
has
to
be
finished
in
thirteen
point
two
you
know
taking
up
an
issue
and
running
with
it
is
sufficient
enough.
It
could
be
a
nice
gap
filler
for
you
in
terms
of
when
you're
waiting
between
reviews
for
mrs
or
whatever,
and
it
might
be
something
that
you're
really
passionate
about
as
well.
A
B
B
We
need
like
actually
like
to
make
some
analysis
and
find
where
all
of
those
UT
libraries
are
used,
so
a
good
way
of
contributing
if
you,
if
we
don't
want
like
to
spend
a
lot
of
time,
making
implementation
is
just
like
doing
that.
Work
like
taking
one
of
those
epics
looking
where
all
of
that
technical
debt
exists
and
creating
issues
for
them.
A
F
C
Yeah
I,
basically
just
echoing
the
same
thing
with
Enrique
that
was
actually
a
target
one
when
I
first
epi
show
the
kind
of
had
a
visualization
block
of
our
various
dependencies
and
that
definitely
stuck
out
to
me
I
added
a
little
note.
There
I
think
there's
some
level
of
potential
automation
there
as
well,
but
it
may
just
be
too
what
Enrique
is
talking
about
in
terms
of
identifying
versus
just
automatically
fixing,
but
secondarily
there
might
be
some
potential
of
automatically
fixing
in
some
cases.
But
who
knows,
I
did
have
a
question
that
where's
the
spreadsheet.
A
Created
for
as
our
dogfooding
site,
static
site,
editor
unfiltered,
which
ties
in
nicely
with
github
on
the
default
on
youtube,
as
well
as
the
unfiltered
blog
section,
and
essentially
this
is
going
to
be
our
site
that
we're
gonna
use
to
dog
food,
our
like
a
litter.
Now
we,
the
intention,
is
to
just
start
using
it.
A
It's
not
about
being
perfect,
it's
not
about
having
the
ideal
structure
or
anything,
and
so
we're
going
lightweight
we're
going
with
for
the
engineering
section,
a
change,
love
page
essentially,
and
one
thing
that
I
was,
you
know
my
proposal
is
that
we
every
time
at
an
implementation
or
feature
issue,
is
closed.
Ie,
it's
validated
on
Quetelet,
calm
that
you
make
an
update
to
the
changelog
page
to
you
know,
and
it
could
be
as
simple
as
two
symptoms
as
to
say
that
you
can
now
insert
an
image
using
the
static
site.
A
Editor,
it's
not
about
the
content.
It's
about
the
fact
that
we
go
through
the
flow
that
our
users
go
through.
That's
what
I
would
like
us
to
do
to
go,
and
so
I
may
I
would
like
to
hear
from
your
whether
you
think
that
this
is
the
feasible
thing
to
do,
noting
that
there's,
no
there's
a
very
low
barrier
for
for
adding
content
to
to
that
change,
lock
page
doesn't
have
to
be
perfect
or
that
you're
taking
it.
Hopefully,
no
more
than
two
minutes
any
feedback
on
that
I.
C
A
Okay,
I'll,
then
create
of
engineering
change
of
page
Eastwood.
I
think
it
is
because
you're
not
part
of
that
group,
maybe
on
get
loud,
so
basically
that
GL's
that
excited
editor
group
on
get.
That
is
what
we
use
to
fall
short
at
mention
handle
for
somebody
to
reach
dolls.
That
excited
group
so
think
it
might
be
that
that
that
pager
site
is
said
to
be
respected
to
members
of
the
product
only
which
would
be
why
you
concede
know.
A
G
Forget
it
we're
working
on
on
a
small
desktop
that
update
to
of
the
banking
in
WJ,
guess,
which
is
the
wrapper
behind
webapp
the
latest,
and
it
also
fixes
the
get
up
sign
in
issue
that
where
we
were
isn't
that
spawned
small
update
and
then
I'm
we're
gonna,
get
to
know.
Gator
Gator
a
call
out
line
and
we'll
have
a
cattle
call
later
in
the
week,
probably
it'll
it'll
be
recorded
for
others
to
watch
doing
a
verbalize,
John
yeah.
A
You
know
all
of
a
sudden
helping
out
with
code
reviews
on
there,
which
might
be
quite
distracting,
is
we're
going,
especially
concerning
all
the
effort
we're
having
in
13.2
with
Chad
and
I
are
going
to
work
with
Eric,
so
Eric's
going
to
give
us
an
outline
of
we're.
Gonna
have
one
or
two
sessions
where
you
gives
us
an
outline
of
the
product,
the
infrastructure
and
the
probe
base,
and
to
get
us
more
familiar
with
it.
A
A
What
we
don't
want
is
to
use
your
time
to
be
a
human
lender
for
the
Curt,
which
is
why
you
need
more
deeper
insight
into
what's
going
on,
to
be
able
to
to
to
really
add
value
and
to
make
use
of
make
make
sure
that
your
time
is
spent
well
and
that
Eric
is
fairly
from
that.
So
we're
going
to
record
the
session
around.
A
All
right,
inning
before
I
hand
over
to
Eric
the
I
wanted
to
mention
one
thing
will
probably
add
a
Doc's
section
and
a
handbook
hitting
to
our
sheet
going
forward.
So
one
thing
I
wanted
to
mention
was
Jacque
is
basically
taking
over
in
a
non
official
capacity
as
the
Acting
iam
for
the
docs
project,
so
older,
the
lien
responsibilities
I
would
have
had
with
with
the
dogs
project
around
setting
up
process
how
we
interact
with
the
technical
writing
team.
The
only
issues
surfacing
them
for
surfacing
issues
for
consideration
for
planning.
G
F
But
just
to
echo
what
we're
talking
about
with
the
13.2
planning
and
give
some
context
around
sort
of
the
theme
I
was
going
for
I
think
the
getting
13.2
getting
the
handbook
in
some
way
integrated
links.
Getting
that
started
is
gonna,
be
the
most
important
thing
for
us
to
reach
our
maturity
goal,
but
also
to
start
getting
more
feedback
and
more
usage,
and
everything
I
tried
to
prioritize
was
just
around
cleaning
it
up.
In
order
to
do
that,
so
I
think
we've
in
13.1
already
been
tackling
a
lot
of
the
most
important.
F
You
know,
features
that
would
support
working
in
the
handbook,
specifically
not
displaying
front
or
not
editing
the
non-market
own
content,
and
so
I
tried
to
prioritize
a
bunch
of
UX
tweaks.
If
you
know
we're
gonna,
so
we
can
put
our
our
best
foot
forward
as
we
go
out
to
product
managers,
there's
40
some-odd
of
us
and
then
anybody
else
that
is
editing
those
product
pages.
F
So
maybe
we
get
a
hundred
and
some-odd
people
with
you
know,
access
to
the
static
site,
editor
and
then
those
people
in
the
those
team
members
who
stumble
upon
it
and
just
want
to
try
it
out
by
passing
in
the
URL.
So
a
lot
of
it
is
tweaking
the
UX.
The
image
uploading
is
a
is
an
is
a
feature
that
would
be
fantastic
for
for
people
to
enable
that's
one
that
you
know
if
it
had
to
be
pushed
I'd
honestly,
not
be
I,
wouldn't
hold
back
from
being
in
the
handbook.
F
If
we
couldn't
upload
images,
but
I
think
it's
going
to
be
something
that
they
asked
for
immediately
and
I.
Think
the
the
flip
side
of
that
is
you'll
see
more
handbook
related
issues
on
the
on
the
spreadsheet,
then
I
would
normally
prioritize
because
I
think
we're
looking
for
a
home
for
the
static
site
editor
on
the
handbook,
so
we're
trying
to
clean
up
the
handbook
UX
the
code
owners
work
is
the
beginning
of
that.
But
I
think
that
we're
starting
to
see
some
concepts
from
Michael.
F
I
I
think
we'll
need
to
iterate
on
that
a
little
bit,
because
now
we'll
have
three
different
ways
to
edit
a
page,
the
raw
edit
web
IDE
and
for
the
pages
that
support
it.
The
static
site
editor
so
yeah,
we'll
kind
of
find
a
place
for
it
and
13.2
and
then
and
then
maybe
execute
on
that
in
13.3.
But
I
just
wanted
to
to
share
that
context
in
case
you
were
curious
about
why
some
of
the
smaller
UX
improvements
were.
F
You
know,
prioritize
over
other
features
but
appreciate
all
the
feedback
on
on
those
issues
that
you
listed
I.
Think
all
of
them
sound
like
great
candidates
too,
and
if
you
have
any
questions,
I
know
a
couple
of
those
issues
that
are
linked
on
the
spreadsheet
need
a
little
more
detail
and
I'll
be
working
on
those
over
the
next
couple
days
and
last
I
know
we're
over,
but
I
could
use
a
volunteer
that
than
those
of
you
to
help
on
an
issue
this
was
sent
to
me
via
CID.
F
He
was
trying
to
do
some
work
on
a
calculator
that
we
have
already
in
place
in
production
on
the
handbook.
He
added
a
few
rows
to
it
that
are
calculating
some
additional
data
using
the
same
input.
I
don't
know
view
and
certainly
not
well
enough
to
to
extract
the
right
data.
I
was
working
with
another
engineer
on
this
he's
very
busy
and
so
I
just
figured.
F
If
somebody
had
an
hour
to
to
work
with
me
on
this,
that
would
be
immensely
helpful,
looks
like
there
it's
fallen
tearing
but
I
know
he's
got
a
lot
of
it's
late
and
Chad.
What's
up
I
can't
hear
you
this
is
never
mind.
We
can
talk
about
it.
Offline
I
know
we
don't
need
to,
but
the
calculator
itself
I've
blessed.
Some
left
some
notes
in
the
HTML
about
what
we're
trying
to
calculate
I
just
don't
know
how
to
get
the
right
variables
in
place.
So
that's
it.