►
Description
Weekly sync call of the Static Site Editor group focused on engineering efforts.
A
Hello,
everybody.
This
is
the
weekly
group
sync
for
the
static
site
editor,
and
this
is
the
engineering
focus
edition.
We
have
no
fyis
today,
so
we'll
move
on
an
engineering
general
item
is
milestone.
13.3
is
here
officially
just
to
recap.
Our
primary
primary
objective
is
to
get
the
static
site
editor
integrated
with
the
whole
handbook
in
the
small
sun
and
to
if
everything
goes
well
by
the
end
of
the
milestone,
we'll
we'll
open
it
up
to
to
the
whole
company
as
we'll
discuss
later
on.
A
I've
gone
through
through
those
issues
with
most
of
you
now
it's
just
chad.
I
need
to
go
through
the
web
store,
but
I
think
if
we
can
kind
of
like
get
our
heads
down,
we
can
power
through
most
of
the
work
in
the
first
week
or
two
at
least
to
a
point
where
we
we
will
have
a
sense
of
confidence
or
around
our
objective
for
13.3.
A
B
Sure
so
this
week
my
hope
is
that
we
can
start
formatting
the
pages
of
the
handheld
product
section.
Before
that
we
have
to
deliver
too
much
requests.
One
is
to
to
fix
the
the
order
list
that
this
exit
editor
generates.
We
don't
want
those
lists
to
to
be
incrementable
the
marker,
the
marker
of
those
lists.
B
A
All
right
well
that
essentially
answers
my
second
question,
which
is
what
is
blocking
us
from
launching
it
to
the
product
team.
I
know
eric
and
and
I've
gotten
an
issue
as
well
of
creating
an
issue
for
them
to
give
up
feedback,
so
that's
the
kind
of
like
all
in
place,
so
we
essentially
just
need
to
wait
for
these
last
few
things
to
be
delivered
in
on
production
and
so
that
we
can
pre-format
those
pages
just
speaking
on
on
the
the
rolling
it
out
to
the
rest
of
the
handbook.
A
Eric
enrique
and
I
had
a
quick
discussion
about
this
earlier
and
on
the
whole
topic
of
pre-formatting,
so
it
will
obviously
not
be
feasible
to
pre-format
it
via
the
the
ui,
and
so
that's
something
we
just
need
to
consider
for
for
the
global
rollout.
I
guess
if,
once
we've
adopted
the
the
standard
handbook,
formatting
and
we've
made
all
of
these
changes.
If
the
noise
ratio
is
sufficiently
down
to
the
point
where
it's
only
fixing,
let's
say
proper
issues
like
spaces,
training,
spaces
that
aren't
needed
or
lack
of
new
lines.
C
D
Want
to
add
something
real,
quick
to
1a2
the
brs
and
again
this
is
part
of
kind
of
the
conversation.
I
guess
I'm
still
looking
for
feedback
on
is.
We
can
actually
solve
this
on
the
front
end
as
well.
Again,
the
question
is:
is
that
a
good
idea,
or
not?
I
don't
know,
but
in
terms
of
like
the
spacing
and
like
at
the
end
of
the
file,
needs
a
new
line
like
those
types
of
things
we
can
actually
do
on
the
front
end,
it's
a
question
of.
D
A
D
C
C
Put
off
any
like
stylistic
or
linting
or
cleanup
changes
for
for
later,
which
I
do
think
would
be
really
great,
but
would
probably
expose
us
to
even
more
variables
as
we
expand
into
different
different
static
site
generators
or
or
people's
different
preferences
and
as
far
as
I
understand,
with
markdown
like
multiple
line
breaks
after
your
second
really
doesn't
impact
the
the
shouldn't
impact
the
rendering.
And
I
don't
really
think
that
we
need
to
enforce
anything
there
yet.
C
D
I
think
again
just
I
don't
want
to
draw
on
this
too
long,
but
I
think
a
nice
side
effect
of
that
would
be
enforcing.
That
linting
is
like
to
communicate
people
that
are
using
markdown
that,
once
you
have
multiple
spaces,
you're
not
actually
doing
that
in
the
page
itself,
which
I
think
people
are
expecting
and
same
thing
with
the
br
like
once
you
do
a
new
line,
you
don't
actually
need
to
be
our,
and
I
think
people
have
learned
that
that's
what
they
think
occurs
anyway,
we
can
move
on.
E
E
It's
not
possible
to
without
making
major
changes
to
the
content
of
the
site,
to
not
just
move
everything
else
down.
So
that's
the
current
plan
we're
going
to
move
everything
else.
That's
not
the
handbook
into
its
own
site,
but
even
with
that,
there's
some
important
decisions
to
be
made
about
how
much
we
want
to
share
how
much
we
want
to
duplicate
and
some
very
real
trade-offs
when
you
get
into
the
technical
weeds
of
that
and
john's
got
opinions
on
that.
I've
got
opinions
on
that
they're
not
always
the
same,
and
so
that's
why.
E
I
wrote
that
giant.
Note
that
I
copied
everybody
on
to
sort
of
brain
dump
them
out.
So
at
least
other
people
were
aware
of
these
things
that
we
were
discussing
and
as
part
of,
and
that
was
good
that
clarified
it.
That's
still
a
hard
decision
we
need
to
think
about,
and
then
I
realized
you
know,
there's
a
bunch
of
other
stuff,
a
few
things
that
we
really
have
to
clean
up
and
a
lot
of
other
things
that
we
really
could
easily
clean
up.
E
That
would
make
all
of
these
other
hard
decisions,
much
easier
to
reason
about,
essentially
to
get
to
what
is
left
to
a
point
where
it's
a
bunch
of
small
independent
deploys
that
are
very
already
separated
and
isolated
from
each
other,
and
so
that's
this.
Second,
one
that
I
wrote
up
and
I'm
I'm
just
going
to
put
that
phase
one
link
in
there,
which
summarizes
most
of
them
and
so
that
all
of
the
tasks
that
I
came
up
with
these
preliminary
refactorings.
I
dented
an
issue
and
I'm
just
working
through
those
and
we're.
A
All
right
so
just
a
reminder
that
conversation
about
how
we're
gonna
deal
with
the
that's
happening
a
little
later
today
at
the
1900
uk
soon.
So
it's
open
to
all.
I
did
send
the
invite
to
to
me
chad,
lauren
and
michael
and
brandon,
but
it's
essentially
open
to
all
it
is
on
our
shared
calendar,
so
feel
free
to
jump
in
if
you're
available
and
give
some
insight.
A
Okay.
So
since
we
have
susan
here,
I
will
quickly
give
a
doc's
update
so
susan,
you
went
here
last
week,
but
jacques
is
out
on
fraternity
leave
if
you're
not
aware
yet,
and
I
will
be
taking
over
the
responsibilities
from
him
while
while
he
is
out
the
act,
work
that
that
is
currently
in
our
system
is
the
the
offline
docs
research
that
vasily
is
working
on,
so
he
was
out
sick
for
a
week
in
13.2,
so
he's
still
catching
up
on
that.
A
So
it's
carrying
over
to
setting
three
and
then
also
the
tier,
rename
work.
What
we
I
spoke
with
vaseli
earlier
today
about
that,
and
the
thing
we
wanted
to
said
earlier
is
there
was
another
issue
around
using
the
verbals
in
the
docs
and
whatever
approach
we're
talking
to
a
tre
name
might
be
a
starting
point
for
the
variable
work.
A
He
will
document
that
in
those
issues
with
the
proposed
way
forward
and
then,
if
there's
agreement
on
those
proposed
waves
forward,
then
we'll
need
to
look
at
the
actual
development
effort
involved
and
and
schedule
it.
I
think
the
the
offline
docs
one
might
be
a
bit
of
a
bigger
one
that
that
needs
to
be
tackled.
Probably
over
a
couple
of
milestones.
A
F
C
C
It
was
very
timely
that
you
joined.
I
think
I
got
what
what
amounts
to
a
sales
a
cold
call
from
a
cold
email
from
a
sales,
but
it
had
me
thinking
that
I
don't
actually
know
the
answer
of
how
we
approach
internationalization
in
our
docs.
If
we
do
it
all,
and
are
we
interested
in
building
that
out
further
or
yeah?
How
do
we
contract
that
out?
Do
we
even
translate
any
of
them.
F
C
G
Okay,
on
the
getter
side,
we
completed
get
lab
username
space
communities,
so
I
can
finally
create
a
community
under
my
username
little
mods
or
whichever
sort
of
personal
projects
people
are
working
on.
I'm
now
working
on
the
ability
to
export
data
for
a
given
user.
I'm
probably
going
to
add
in
the
future,
like
you,
can
export
data
for
this
community
if
you're
at
room
admin,
community
admin
that
sort
of
thing
and
then
coming
up
soon,
the
fy21
q2
okr
working
on
adding
some
pwa
features,
so
you
can
install
it
to
your
home
page.
E
G
C
Yeah,
I
don't
have
a
ton
that
hasn't
already
been
covered,
as
john
mentioned,
I
just
posted
a
link
to
the
feedback
issue
that
I
created
so
as
we
do
make
this
editor
available
to
the
product
team,
I'm
going
to
ask
them
to
drop
comments
in
there.
I
think
that
would
be
a
great
way
to
centralize
it
and
expose
and
then
I'll
create
issues
for
anything
that
doesn't
have
an
issue
already.
C
I
want
to
be
wary
of
getting
feedback
and
trying
to
be
trying
to
take
action
immediately.
I
don't
want
to
distract
anybody,
so
I
think
this
is
probably
the
best
workflow
for
for
that,
and
I'm
also
I
didn't
get
to
finish.
Writing
the
last
word
on
my
last
comment.
I
was
thinking
of
coordinating
another
think
big
session.
It's
been
a
while,
since
we've
had
a
synchronous
like
big
brainstorming
thinking,
big
on
the
tails
of
that
diagram
and
sketch
that
I
did.
C
A
A
For
those
of
you
that
weren't
here
at
the
beginning
of
the
start
of
this
group,
those
big
sessions
were
really
helpful
and
just
trying
to
understand
what
we're
going
to
do
and
how
we
go
from
a
blank
canvas
to
something.
And
so
I
I
fully
agree
that,
while
we
need
to
be
inclusive
of
of
different
time
zones
it,
it
really
is
a
a
great
opportunity
for
synchronous
discussion
and
to
make
sure
that
we
actually
get
people's
input.