►
Description
Weekly sync call of the Static Site Editor group focused on product and design efforts
A
Hello:
everyone:
this
is
the
static
site,
editor
product
and
design
weekly
call
for
september
14th
2020..
I
don't
have
much
on
the
agenda
that
wasn't
covered
in
this
morning's
meeting,
so
I'm
just
going
to
turn
it
over
to
design
and
we
can
chat
on
your
first
topic.
Michael.
B
All
right,
so
the
first
topic
is
the
category
of
maturity
scorecard,
so
the
static
site
editor
group
underwent
our
first
maturity
scorecard
testing
round
to
get
us
from
minimum
survival.
B
Today's
session
was
our
10th
participant
out
of
the
groups
of
part
of
marketing
and
sales,
so
those
are
the
personas
we
wanted
to
target
and
we're
still
like
going
through
the
details
of
the
notes
but
like
if,
from
a
high
level
perspective,
the
scores
are
high
enough
to
move
to
update
the
scorecard
rating
so
yeah.
Thank
you
for
all
the
people
involved
in
taking
time
to
talk
to
eric,
and
I
through
that
and
yeah.
I
think
this
is
good
for
our
group
overall.
A
Yeah
and
to
be
clear,
I
only
did
one
today.
It
was
mostly
you
so
thank
you
for
and
for
catherine
for
for
pushing
this
through
and
doing
the
hard
work
here.
I
had
a
script
to
go
off
of
and
everything
I
didn't
hardly
have
any
any
hand
in
this,
but
it
was
a
great
conversation.
It
was
really
valuable.
I'm
glad
I
got
to
do
one
of
them.
B
Yeah
yeah,
so
I
guess
the
next
step
there
is
yeah
updating
that
rating
in
the
handbook
itself.
B
The
other
solution,
validation
thing
that
we
had
on
the
docket
was
editing
front
matter,
so
that
one
was
I
kind
of
wrapped
it
up
with
four
participants,
because
I
felt
like
it
was
enough
to
for
us
to
move
forward
with
some
of
the
designs
that
we
have
and
there's
probably
more
in
depth,
situ
scenarios
that
we
can
go
into
once
we
dive
deeper
into
front
matter,
so
in
the
handbook
front
matter
is
usually
responsible
for
handling
title
and
description
and
page
layouts.
B
It's
in
marketing
that
it's
a
little
bit
more
in
depth
with
social
media,
multiple
authors
and
more
elaborate
use
cases.
So
I
think
we
have
enough
now
to
move
forward
with
the
handbook.
So
I
think
we
can
go
forward
with
that,
and
if
we
need
further
testing
specifically
to
marketing
use
cases,
then
we
can
schedule
further
solution.
Validations
in
in
that
kind
of
space,
yeah
the
unique
part
of
the
editing
front
matter.
B
A
B
To
it
and
upload
the
video
back
to
us,
I
think
in
theory
it's
a
really
good
way
to
get
some
quick
feedback
asynchronously
from
people,
especially
where
a
global,
remote
company,
the
platform
we
used
was
a
little
bit
tricky
to
use.
So
I
think
that's
something
that
I
fed
back
to
the
ux
research
team
and
they're,
going
to
iterate
and
use
that
information
to
make
a
good
choice
in
the
future
for
tools
to
use.
So
overall
yeah,
that's
a
positive
aspect
for
us
from
the
design
side.
B
What
I'm
taking
a
look
at
right
now
is
updating
the
publishing
flow
thinking
about
that
whole
lag
in
the
summit.
Changes
where
there's
a
a
bit
of
a
way
to
create
the
branches
and
the
mrs
and
stuff
like
that
and
looking
at
the
flows
also
from
like
associating
new
changes
to
existing,
mr,
which
is
a
very
common
workflow.
B
So
I'm
taking
a
look
at
all
those
kind
of
holistically
because
they
all
seem
very
interrelated,
but
I'm
also
knowing
that
I
need
to
get
some
designs
ready
for
like
title
and
description,
editing
and
based
on
the
comments
that
I've
seen
so
far
in
this
morning.
I
feel
like
I'm
on
the
right
direction
for
that,
so
that's
good,
so
yeah,
I'm
just
going
to
crack
on
with
that,
probably
create
an
issue
by
the
end
of
the
week
for
solution.
B
Validation
with
publishing
changes
again,
but
I
feel
like
this
time
it
might
be
a
longer
like
one
hour
session
because
it's
it
feels
like
more
in
depth.
So
far,
we've
been
doing
30
minute
sessions
and
we
we
get
by
a
cat
in
terms
of
like
testing
internally
like
when
it
reaches
an
hour.
Do
we
compensate
people
or
do
we
try
to
keep
it
to
30
minutes
or
what's
I'm
not
really
sure
what
the
protocol
there?
C
Yeah,
I
don't
think
we
have
a
specific
protocol.
Usually
we
just
have
our
sessions
uncompensated,
so
I
guess
you
could
pose
the
question
to
the
participants
like.
B
B
B
C
A
C
Yeah,
so
this
one
is
the
just
a
recap
from
I
think
it
was
like
it's
crazy.
I
think
it
was
three
weeks
ago
already,
but
recap
from
then
we
decided
to
start
with
the
internal
one
and
then,
as
we
kind
of
get
a
little
bit
more,
you
know
maybe
some
insight
into
the
direction
we
want
to
go
whether
we
want
to
start
with
an
edit
a
content,
editing,
persona
externally
or
configuring,
the
site
that
sort
of
thing.
Then
we
could
do
the
rounds
of
interviews
for
the
external
persona.
C
You
know
it
gets
harder
and
harder
each
time
this
one
was
actually
pretty
simple,
but
so
we
try
to
keep
them
gender
neutral
and
some
of
them
are
really
tricky,
but
this
one
I'm
like
okay,
we
could
have
connor
constance
connie.
How
about
that?
Let's
just
say
it's
gender
neutral.
I
think
it
is,
but
I've
been
wrong
before
I've
had
people
correct
me
and
be
like
nope.
C
A
Is
we'll
I'll
give
some
feedback
and
I'll
share
with
the
rest
of
the
engineers
as
well,
so
they
can
see
the
work
in
progress.
This
is
great.
C
Awesome
well
yeah,
so
I'll
leave
it
open
for
you
to
give
feedback,
and
then
I
will
submit
it
I'll,
probably
I
don't
know,
I
think
maybe
william
owns
the
the
page,
one
of
them,
but
yeah
just
feel
free
to
add
any
feedback
or
suggest
a
point
to
add.
There.
A
Great
well,
I
don't
really
have
much
I'll
just
recap.
A
couple
points
that
I
made
earlier,
just
not
that
you
can't
watch
the
recording,
but
I
do
want
to
celebrate
our
our
group's
iteration
because
it
was
called
out
internally
and
I
feel,
like
everybody
should
get
the
credit
they
deserve.
For
that
I
had
the
the
shorter
story
is.
I
had
been
working
on
release
post
items
and
I
was
drafting
one
for
our
configuration
file
which
chad
has
been
working
on
architecting.
A
He
has
a
an
iterative
set
of
mr's
and
the
first
few
iterations
are
just
building
out
the
foundation
of
the
configuration
file,
and
you
know
using
values
and
and
his
approach
is
to
use
first,
a
value
that
actually
doesn't
get
surfaced
anywhere.
But
it's
a
very
important
feature
so
and
it's
a
directional
feature,
I
wrote
a
release
post
item
and
then
a
in
a
comment.
I
said:
I'm
not
really
quite
sure
about
this
one.
I
feel
a
little
uncomfortable
talking
about
a
feature
in
a
release
post.
It's
meant
to
be
something
of
a
release.
A
That
means
we're
we're
doing
something
right,
so
I
should
because
afterwards
I
got
called
out
by
a
product
group
manager
and
my
manager
a
product
director
for
for
a
good
example
of
iteration,
and
so
I
I
think,
chad
this
morning,
I
think,
even
made
it
into
the
handbook
as
an
example
of
how
we
should
be
iterating
towards
things,
even
if
they're
so
small,
that
they
can't
be
used
yet
or
you
know,
have
no
visible
change.
A
The
other
is
the
front
matter,
editing
ui,
which
is
I'm
very
excited
about,
and
I'm
focused
on
13-5
planning
the
rest
of
this
week,
I'll
be
recording
the
kickoff
call
actually
tomorrow.
So
not
really
the
rest
of
this
week
for
the
first
half
of
this
week.
C
A
Recommend
you
read
it
it's
interesting,
it's
not
something
we're
trying
to
solve
immediately,
but
it
is
a
pain
point
that
he's
had
with
the
static
site,
editor
and
others
have
come,
ran
run
into
this
too.
A
The
gist
of
it
is
there's
some
pages
that
are
essentially
just
a
ruby
helper
partial
that
gets
that
links
to
a
data
file
and
gets
dynamically
created
when
the
sonic
site
generator
is
building
the
page
in
the
stack
site,
editor
itself
or
sorry.
The
static
site
generator
is
building
the
page.
The
static
site
editor
doesn't
provide
much
value
for
those
types
of
pages.
There's
not
much.
You
can
do
there.
A
It
might
be
that
case
for
a
long
time.
It
might
never
be
valuable,
but
we
should
you
know,
keep
that
thread
in
mind
as
we
think
about
the
path
for
linking
files,
including
data
files,
and
things
like
that,
and
the
last
is,
I
guess,
maybe
an
fyi
that
could
have
done
off
the
off
the
recording
but
I'll,
be
the
release
post
manager
this
week,
and
this
is
a
busy
week
reviewing
the
post
and
getting
everything
assembled.
A
So
if
I
fall
off
the
radar
and
you're
waiting
on
me,
if
I'm
become
a
blocker,
please
let
me
know,
and
I
will
turn
my
focus
to
where
it
should
be.
So
that's
it
for
me.
C
I
do
have
one
question,
so
I
was
in
the
same
vein
of
this
persona.
I
was
thinking
ahead
about
the
screener
for
the
external
one,
and
I
was
wondering
if
beyond
the
tools
that
are
currently
on
the
category
direction,
page
as
like
competitive
landscape
or
something
if
there
are
tools
that
you
would
keep
in
mind
when
screening
for
people
to
talk
to
talk
with,
I
think
there
was
netflix.
A
Netlify,
forestry
contentful,
those
are
big
ones,
I
would
add
wordpress
in
there,
because
it's
a
little
more
ubiquitous.
We
wouldn't,
I
wouldn't
necessarily
say
we
would
compete
directly
with
wordpress,
but
the
people
who
would
be
contributing
would
be
familiar
with
wordpress,
most
likely.
B
Yeah,
I
was
thinking
about
this
the
other
day,
but
in
a
very
like
off
off
angle
side,
but
with
the
competitive
landscape.
I
think
these
are
like
our
static
site,
editor
competitors.
A
B
Companies
and
products
that
solve
the
static
site
editing,
but
in
the
case
of
solving
like
the
handbook,
like,
I
think,
that's
another
like
list
of
category
a
different
list
of
competitors
or
like
other
solutions,
people
would
use
so
like
companies
that
use
notion
or
confluence
as
their
handbook
would
definitely
fall
into
place
and,
like
you
know,
adopting
like
our
group,
started
off
in
the
handbook,
and
it's
like
we're
kind
of
solving
that
problem
as
well,
and
I
think
that's
almost
something
that
we
should
mention
so
like.
B
I,
I
think,
there's
that
kind
of
gray
area
like
one
is
like
a
technical
solution
and
then
the
other
one
is
like
the
problem.
We're
trying
to
solve
with
this
product
or
solution
is
like
making
it
easy
for
everyone
to
contribute
content,
be
it
like
product
company
information
processes
and
I
think,
that's
a
different
list
of
things
that
we
could
put
in
there.
So
if,
if
y'all
want,
I
can.
A
Yeah,
I
think
especially
confluence
would
be
helpful
just
for
the
editing
and
collaborative
right,
you
know
collaborative
editing
experience,
even
if
we're
not
directly
competing
again
like
wordpress.
It's
like
something
these
authors
and
contributors
would
be
familiar
with,
and
I
know
we
have
some
research
most
likely.
I
think
I
know
we
have
some
research
on
confluence
related
to
the
wiki
and
everything
as
well
authoring
experience
there.
So
if
we
don't,
then
it
could
be
valuable
in
both
places.