►
Description
Weekly sync call of the Static Site Editor group focused on product and design efforts.
A
Hello,
everyone-
this
is
Eric
and
this
is
the
static
site,
editor
product
and
design
weekly
call
on
Tuesday
May,
26
Wednesday,
for
you,
Michael
the
27th
and
to
start
off
the
the
only
other
FYI
I
have
is
the
jam
stack.
Virtual
conference
starts
tomorrow,
I,
don't
know
if
you
got
registered
for
the
for
the
other,
didn't
you
say
you
were
gonna,
try
and
attend
one
of
the
workshops,
yeah.
B
A
A
Schedule
you
may
not
join
at
all,
but
if
you
were
to
want
to
hop
in
will
most
likely
be
jumping
in
and
out
and
socializing
as
we
watch
the
sessions.
I
have
a
couple
conflicts
throughout
the
day,
so
I
won't
be
able
to
do
the
whole
session,
but
it
is
kind
of
it's
pretty
much.
My
whole
workday,
so
there's
some
good
overlap.
I
will
try
and
join
where
I
can
and
follow
along
and
there's
gonna.
There
have
a
doc
where
they're,
keeping
notes,
takeaways
and
stuff.
A
A
A
Earlier
today,
I
was
mentioning
to
the
team
that
I
really
only
had
to
a
few
things
top
of
mine
this
week.
The
first
is
that
that
website,
Status
page
whatever
project
that
we
can
use
for
dogfooding
I
posted
a
link
again
in
the
agenda
for
feedback.
My
only
real
concern
is
that,
as
I
was
building
out
the
outline,
it
felt
an
awful
lot
like
a
blog
and
we're
not
really
set
up
yet
to
be
a
blogging
platform,
because
we
can't
create
new
pages
or
new
posts
from
the
static
site.
A
Editor
I,
don't
want
to
try
and
embrace
something.
That's
too
complicated,
I'm
gonna
make
it
like
harder
than
it
should
be
so
I'm
trying
to
rethink
the
structure
a
little
bit
less
around,
like
weekly
updates
and
more
around,
like
you
know,
a
single
page
like
monolith,
source
of
truth
with
maybe
an
opportunity
to
sometimes
I
have
new
pages
or
have
maybe
each
person
have
their
own
page
or
something
like
that.
You
know,
I,
don't
want
it
to
be
a
live
journal
either,
but
it's
gonna.
It's
gonna
need
to
be
a
little
more
simple.
A
B
Leave
it
up
to
you,
the
rest
of
the
designers
to
come
in
and
add
the
next
points
to
the
list
as
a
way
to
like
get
around
that
meaning
to
create
a
new
page.
So
yeah
I
already
created
a
project
for
it,
but
I
haven't
like
created
the
page
for
it.
Yet
so,
and
you
know
probably
get
it
done
sometime
this
week
and
early
next
week,
cool.
A
I'm
posting
away:
this
is
really
cool,
yeah
yeah!
Well,
that's
cool
I!
Think
the
the
more
we
can
all
start
using
it.
The
better
I
don't
want
to
put
too
much
more
time
into
overthinking
our
structure,
so
I'll
probably
get
a
project
stood
up
so
that
we
can
all
start
contributing
to
something.
Hopefully
this
week
and
we'll
just
take
it
from
there.
It'll
evolve
just
like
our
product
of
us
or
our
future.
A
So
that's
kind
of
a
side
note.
My
major
focus
this
week
is
ensuring
that
we
have
everything
buttoned
up
for
13.1,
making
sure
that
all
the
issues
are
up
to
date.
After
all,
though,
like
really
healthy
and
helpful
discussions
in
the
in
the
comments
make
sure
that
everything
is
ready
for
development,
we
had
a
review
with
the
engineers
this
morning.
A
It
seems
like
we're
in
a
pretty
good
place
and
then
I'm
gonna
start
thinking
about
13.2
planning
which,
really,
after
some
conversations
and
and
and
hard
thinking
about,
what's
gonna
be
a
requirement
for
getting
the
static
site
editor
into
the
handbook.
I
think
we're
really
close
I
feel
like
we
chose
the
right
things
to
focus
on
in
13.1
and
if
we
can
ship
them
all,
meaning
images
non
markdown
content
being
handled
in
some
way
and
the
frontmatter
being
excluded
from
the
WYSIWYG
editor.
A
But
I
don't
I
think
if
I
sit
here
and
look
at
the
handbook
pages
and
think
about
it,
I'm
not
seeing
any
other
major
red
flags,
but
I,
positioned
it
to
the
team
and
I
will
open
it
up
in
discussion
in
an
issue
just
to
make
sure
I'm
not
missing
anything
but
I.
Think
those
if
we
can
get
those
three
things
like
maybe
for
section
of
the
handbook,
even
I,
think
we
could
get
it
done
in
13
right.
A
I
yeah,
yeah
I
think
absolutely
I
mean
all
of
that.
Stuff
is
helpful
and
I
think
so.
I
was
having
a
discussion
with
Eric
Brinkman
about
the
difference
between
viable
and
valuable
and
how
that's
difficult
for
me
to
under
to
wrap
my
head
around
here,
because
my
my
instinct
from
you
know
previous
roles
and
previous
products
that
I've
managed
is
to
you
know,
put
our
best
foot
forward
and
polish.
They
use
the
user
journey.
A
A
Even
but
it's
it's
usable
end
to
end
and
people
choose
to
use
it,
maybe
like
we
don't
have
to
force
them
to
use
it
I
think
that
would
be
a
good
bar
for
our
viable,
but
but
I
was
looking
at
it
and
continue
to
struggle
by
looking
at
it
as
more
of
like
a
minimum,
valuable
product,
which
is
it's
doing
all
the
things
that
people
need
to
do
to
see
value
in
it
and
we
can
still
get
there.
I
mean
we.
A
We
want
to
be
valuable
for
everybody,
but
I
think
getting
in
the
hand,
looks
sooner
than
later
is
going
to
be
beneficial
for
us
as
a
team
to
figure
out
those
edge
cases.
It's
going
to
be
beneficial
for
the
gitlab
team
as
a
whole
for
editing
the
handbook
and
the
public
if
they
want
to
edit
the
handbook
so
single-page
know
like
integrations
into
the
em
ours,
but
really
clean.
A
Really,
you
know
usable
path
towards
a
single
page
edit,
using
a
visual
editor,
the
WYSIWYG
editor
and
without
destroying
any
formatting
like
a
mole
or
or
a
ruby
code
that
might
be
sprinkled
and
I.
Think
that's!
That's
really
the
that's!
The
the
bar
I'm
trying
to
set,
and
then
if
we
try
to
do
it
in
13.2,
that
buys
us
a
whole
other
milestone
whole
other
iteration,
to
address
feedback
and
edge
cases
as
they
come
up
and
still
hit
our
quarterly
goal
for
being
valuable.
As
that,
that's
a
feature.
A
So,
as
I
said,
I'll
mention
all
of
this
in
an
issue:
I
actually
there's
already
an
epic
for
integrating
into
the
handbook,
so
I'll
just
reuse
that
and
just
tag
people
in
it
and
start
listing
like
the
pros
and
cons
and
what
exactly
needs
to
be
addressed.
And
then
we
can.
We
can
discuss
if
there's
anything,
I
missed
or
as
things
come
up,
we
can
have
the
discussion
there.
A
Yeah,
but
I'm
excited
I.
Think
once
we
get
in
the
handbook,
we're
gonna
get
a
bunch
of
really
valuable
feedback
and
I
guess
what
we
talked
about
was
like,
maybe
just
putting
it
in
like
the
product
directory,
or
you
know
one
section
of
the
handbook
so
that
it's
not
all
of
a
sudden
everywhere,
but
we
can
just
try
it
out
almost.
B
B
We
just
limited
to
sperm
pages
that
we
handle
I,
think
he
had
opened
up
to.
The
sections
is
probably
a
good
thing,
because
some
of
the
feedback
of
in
there
like
snot
channel
is
that
we've
had
is
like
someone
actually
tried
to
use
it
on
their
mobile
low
phone.
Like
you
know,
right
now,
we're
not
focusing
on
the
mobile
editing
experience
but
like
leaving
it
open
like
that
addresses
like
brings
awareness
to
those
areas
earlier
so
I
think
I,
don't
think
we
need
to
lock
off
section
but
Mia.
A
Making
a
little
note
for
later,
but
I
do
want
to
ask
about
dovetail
I
just
so
we
can
get
back
to
it,
but
this
might
play
into
the
other
thing
about
the
code
owners
file
like
if
this
could
be
a
good
place
to
to
highlight
the
different
editing
options
other
than
putting
them
all
the
way
in
the
footer.
But.
A
A
Yeah,
we'll
get
back
to
that,
so
dovetail
I'm,
sure
you're
aware,
is
being
rolled
out.
Company-Wide
I
think
it's
a
sounds
like
a
really
promising
tool
sounds
like
you
had
a
good
experience
with
it.
I
was
a
little
confused
because
I
finally
got
around
to
accepting
the
invite
and
I
didn't
see
anything
that
you've
been
doing
in
it
yeah,
but
it
might
be
because
I
accepted
the
invite
from
the
UX
research
team
and
not
from
you.
It's.
B
Fine,
so
what
happened
there
is
when
I
created
it.
It
was
like
outside
the
world
who
getting
that
it
was
like
in
the
trial
world.
So
it's
in,
like
my
own
little
workspace,
so
I'm
working
with
Sarah
to
work
with
dovetail
to
that
I
get
that
project
migrated
over.
So
that's
what's
happening
in
that
scenario,
got.
A
It
I
figured.
It
was
something
like
that,
because
I
had
to
email
invites
and
I
just
clicked
the
first
one
in
my
inbox,
which
was
the
most
recent
one
and
then
I
went
and
I
was
like.
Oh
I
gotta
look
for
this
stuff
cuz.
It
sounded
really
interesting
and
I,
just
hadn't
gotten
around
to
digging
into
the
stuff
you
had
done
and
then
I
couldn't
find
it.
But
that
makes
a
lot
of
sense.
I'll
keep
an
eye
out
for
that
and.
B
B
Let's
do
like
that,
so
this
Friday
I'll
be
out
so
I'll
try
to
get
stuff
sorted
out
by
then
on
Wednesday.
Your
time,
there's
gonna
be
a
us
showcase.
I'm
gonna
talk
about
this
static
site,
editor
I'm
kind
of
like
the
problem
space
time,
where
we're
in.
Why
we're
trying
to
tackle
it
and
like
a
brief
demo
of
the
experience,
my
his
made-up
story
or
like
made
up
kind
of
site
so
yeah
that
will
be
on
and
the
UX
showcase
playlist
by
everybody
like
Thursday,
probably
so,
yeah.
A
A
Okay,
so
yeah
not
to
make
this
all
just
me
talking
at
you,
but
to
clarify
the
so
jonad
thing
to
you
on
this
issue
related
to
the
handbook
and
the
request
is
kind
of
a
long-standing
one
and
so
I'll
just
give
you
a
little
more
context
on
the
the
handbook,
UX
and
then
so
yeah
anyway.
The
the
handbook
UX,
is
what
it
is.
A
A
lot
of
people
don't
even
know
that
there's
edit
links
way
down
in
the
footer,
because
our
footer,
our
global
footer,
is
very
tall
and
those
links
are
like
20
pixels
down
on
the
bottom,
but
they're
very
useful
links.
So
some
of
the
suggestions
that
we've
had
that
predate
me
at
gate
lab
and
then
also
I,
try
to
just
kind
of
consolidate
them
and
and
to
still
them
down.
A
It's
just
basically
making
sure,
like
the
metadata
of
a
handbook
page
is
easier
to
find
and
in
that
idea
of
metadata
I'm,
throwing
in
the
like
the
link
to
edit
the
link
to
the
source
file,
a
link
to
donate
a
link
to
potentially
a
link
for
the
code
owners,
which
is
what
this
issues
about
and
then
I
think.
This
might
be
a
good
opportunity
to
just
pull
all
that
out
into
the
design
element.
That's
somewhere
on
the
page.
A
I
think
we
don't
get
direct
access
to
that
data,
but
I
think
this
might
be
a
good
opportunity
for
us
to
just
take
a
look
at
those
edit
links
and
maybe
for
the
pages
that
do
support
the
static
site.
Editor
just
add
a
little
extra
button.
That's
like
you
know.
Now
you
can
view
this.
The
code
source.
You
can
open
the
web
ID
or
new,
like
a
new
badge,
try
out
the
new
static
site,
editor
and
that
could
be
a
way
instead
of
a
floating
button.
A
On
the
like
our
default
styling
on
our
template,
a
floating
button
on
the
bottom
left,
we
don't
need
to
use
that.
So
we
could,
we
could
kind
of
tackle
both
things
at
once,
yeah.
So
that's
the
context,
but
the
real
question
is
I.
Don't
know
if
anybody's
talked
to
you
about
like
design
improvements
to
the
handbook
itself
as
far
as
like
how
it's
been,
how
your
time
should
be
spent
on
it.
If
somebody
else
should
be
thinking
about
this
or
if
you
have
given
us
any
thought.
B
A
A
A
B
The
way
the
way
I
was
framing
it
is
that,
like
there's,
the
goal
of
surfacing
like
who's,
that
responsible
individual
from
the
code
owners
is
helping
with
that
mr
step
of
our
arm
kind
of
flow.
So
if
we
look
at
the
whole
kind
of
value
stream,
it's
like
I
want
to
make
an
edit
where's.
The
edit,
like
I,
want
to
jump
to
that
spot
to
make
the
edit,
hence
like
a
in
place,
editing
or
jump
to
line,
or
whatever
here
do.
B
A
B
Way,
I
saw
this
like
a
smaller
step
towards
suggesting
who
should
be
a
reviewer,
because
you
know
you
make
a
change
you
like
course,
but
a
typo
which
is
like
probably
can
be
a
common
use
case,
but
then
like
for
a
small
typo
like
who
do
I
tag
CID
like
right.
It's
like
the
DRI
on
everyone
on
most
of
these
things,
but
it
could
be
someone
knows
and
so
having
that
other
person
might
be
like
the
better
choice.
B
A
That
I-
and
there
is
another
issue
and
another
discussion
about
code
owners
in
general
and
how
we
apply
it
to
the
handbook,
I'm,
not
sure
if
you've
seen
the
issue,
but
it
it
actually
covers
that
exact
use
case
I
mean
a
typo
that
somebody
somebody
should
be
empowered
to
see
a
type
of
fix
it
and
merge
it
themselves,
but
there
may
be
some
pages
in
our
handbook.
There
are
some
pages
in
our
handbook
that
actually
probably
should
have
review
on
nearly
every
change
legal.
A
You
know
people
ops,
things
like
that.
That
could
could
impact
us
if,
if
somebody
were
to
go
in
and
just
like
make
a
change
willy-nilly,
remove
some
language
that
had
been
approved
by
legal
there.
So
I
think
that
the
idea
of
a
code
owner
or
like
a
file
lock
is
being
tossed
around
her
in
that
handbook.
The
thing
that
I'm
trying
to
wrap
my
head
around
with
how
it
applies
to
the
static
site
editor
would
be.
My
gut
would
be
architecting
this
so
that
it
would
just
be
some
thing
we
write
in
the
yam.
A
Well,
that's
like
the
frontmatter.
That's
that's
like
you
know,
owner
and
it's
got
a
get
lab
handle,
but
our
code
owners
filed
by
nature
is
not
in
the
front
matter.
It's
like
associated
with
the
code
base,
so
I
wonder
if
this
is
the
beginning
of
the
gear,
spinning
on
a
deeper
integration
into
the
the
code
base,
so
that
we
can
have
the
static
site.
A
Editor
actually
pick
up
on
configuration
that
might
be
in
the
code
owners
file
or
the
get
lab
CI
file,
or
some
some
like
config
file
down
the
road
and-
and
that
might
be
that
might
people
were
how
we're
going
to
benefit,
is
just
seeing
this
experience.
Having
this
experience
on
the
hand
book
and
then
applying
it
towards
how
we
architect
that,
like
configuration
stuff,
that's
probably
going
to
come
later
this
year,
yeah.
B
From
from
my
initial
investigations
and
like
wanted
to
do
comments
with
John
is
like
the
direction
feels
like
it's
gonna
be
applied
to
all
pages.
With
all
pages
will
have
this
information,
because
the
way
the
code
on
his
file
is
it
works
is
like.
If,
if
there's
no
one
at
this
level,
then
it
like
jumps
up
to
their
parent
and
then
it
goes
up
all
the
way
to
like
the
route.
So
it
does
feel
like
that's
something
that
it
is
something
that
could
be
generated
and
when
the
site
gets
and
built.
B
So
that
does
make
sense
in
a
static
site,
generator
kind
of
scenario,
from
like
a
visual
standpoint,
thing,
envisioning
kind
of
sort
of
like
how
news
articles
have
like
like
published
by
Eric
and,
like
you
know,
like
a
head
or
something
like
this.
B
Where
we
get
like
by
lines
and
things
like
that
for
the
publishing
world
more
more
geared
towards
what
we
need
to
show,
but
it
does
there's
a
familiar
pattern
that
we
could
probably
leverage
and
probably
surface
in
a
way.
That's
obvious,
but
not
obvious
at
the
same
time,
because
you
don't
want
to
like
it
smacks
with
that
all
the
time,
because
the
value
is
the
content.
So
yeah.
A
I
yeah
that's
a
good
point
because
we
could
end
up
shoving
a
lot
of
stuff
in
there
they've
just
scrolled
to
actually
see
anything
which
was
not
ideal,
so
yeah
I
think
this
is
a
good
thing
to
be
thinking
about
over
the
next
few
weeks
and
then
maybe
what
it
is
is
like.
We
have
a
solution
in
place
so
that,
when
we're
ready
to
ship
in
the
handbook,
we
have
a
place
to
put
the
static
side
in
there
and
it'll
feel
natural
instead
of
just
like.
A
B
No
I
pinned
you
offline
about
a
solution.
Validation
for
some
reason
that,
like
in
my
head,
I
read
things
wrong.
I
was
like
solution,
validation,
I
thought.
What
we
were
doing
was
like
post
code
and
post
like
milestone,
released,
immediate
solution,
validation
reading
deeper
into
it,
confirmed
my
thinking
that,
yes,
solution,
validation,
happens
before
development
and
build,
and
the
first
step
in
kind
of
like
assessing
whether
something
needs
to
be
solution.
Validated
is
whether
we
feel
confident
or
not
in
the
direction.
B
B
B
This
is
where
you
need
to
get
some
solution
value
so
yeah
happy
to
help
in
any
ways
like
whether
that's
like
filling
out
the
solution,
validation
issue
with
more
content
to
help
you
out
with
that
yeah
like
math
test,
my
head's
kind
of
bad
looking
future
wise,
so
I
know
that
he
said
that
you
know
I'm
trying
to
make
some
time
this
week
to
look
at
it.
But
remember.