►
Description
Weekly sync call of the Static Site Editor group focused on product and design efforts
A
A
A
A
B
B
But
I
will
wait
until
then
until
I
find
that
link
just,
but
it
was
mainly
sort
of
a
question
of
if
there
was
anything
that
michael
needs
to
input
on,
because
I
saw
it.
I
think
it's
about
associating
changes
to
an
existing,
merge,
requester
or
something
like
that,
but
I
hadn't
provided
feedback
yet
so
that
that's
what's
on
my
mind,
any
thoughts,
michael.
C
And
so
any
thoughts
on
that
lots
of
thoughts
on
it.
So
I
think
that
that's
been
like
the
main
kind
of
things
that
I've
been
looking
at
is
just
like
the
overall
flow
of
associating
a
change
to
existing.
Mr
I'm
I'm
putting
together
some
prototypes
today
and
then
I'm
going
to
use
the
issue
refinement
session
the
team
later
to
get
some
engineering
feedback
on
some
of
the
prototypes
and
kind
of
the
flows,
and
that
will
probably
dictate
more
of
like
the
direction.
B
C
Like
actually
more
of
the
approaches
that
we
wanted
to
go
for
because
I'm
kind
of
like
debating
between
this
or
that-
and
I
know
that
in
solution
validation,
we
should
go
for
like
bigger
differences.
So
I
kind
of
have
like
two
kind
of
prototypes
to
go
through
for
solution
validation
in
my
head.
It
feels
like
it
could
be
done
in
30
minutes.
So
I
think
that
was
the
concern
I
had
last
time
where
I
said.
Oh,
you
know.
Do
we
need
an
hour
time?
I
think
I
can
do
it
in
30
minutes.
B
And
also
while
the
attention
is
on
me,
it's
not
a
research
question,
but
I
was
wondering
if
you
could
share
thoughts
on
that
issue.
I
think
it
was
from
marketing
how
they've
chosen
a
cms.
I
I'm
not
too
familiar
with
everything,
but
I
was
curious
if
that
is
relevant
to
this
group
or
like
why
why
they
chose,
I
guess,
a
netlify.
A
Yes,
very
relevant,
there
was
a
meeting
our
engineering
focus
call.
This
morning
I
haven't
uploaded
the
recording
I'll,
send
you
a
link,
michael
the
senior
manager
of
that
team,
joined
and
lauren
frequently
joins
our
call
and
they
both
had
joined
in
order
to
talk
specifically
about
that,
but
so
I'll,
try
and
recap
best.
A
I
can
they
chose
netlify
cms
and
I
think
it's
important
to
make
a
distinction
between
netlify
as
a
company
which
offers
a
like
ci,
cd
hosting
kind
of
package
and
solution
and
netlify
cms,
which
is
an
open
source
product
that
they
they
create.
That
is
a
cms
for
jam,
stack
sites
for
static
sites
and
they
evaluated
several
or
the
marketing
team
evaluated
several
cms
type
experiences.
I
think
contentful
was
on
the
list.
A
Natalify
cms
was
one
of
them.
There
were
a
couple
of
others.
They
had
a
list
of
pretty
stringent
criteria
as
far
as
like
wanting
to
keep
a
git
based,
workflow
and
and
not
move
everything
over
into
a
database,
and
you
know
not
have
too
much
overhead
for
for
managing
a
a
new
front
end
or
something
like
that.
So
netify
cms
met
most
of
the
criteria
or
enough
that
they
they
chose
it
to
move
forward
with.
A
They
have
a
proof
of
concept
that
lauren
would
be
happy
to
invite
you
to
if
you
want
to
see
how
it
works.
The
the
feedback
was
generally
positive
from
what
I
understand
on
the
proof
of
concept,
and
I
shared
a
little
bit
of
just
like
a
hypothetical
there,
but
it
was
kind
of
called
out
that's
relevant
to
this
group
that
you
know
we're
not
considering
ourselves
direct
competitors
with
nullify
cms.
A
I
mean
at
least
not
yet.
We
have
very,
very
different
paths
that
we're
taking
right
now,
and
I
I
kind
of
throughout
there
like
someday.
If,
if
we
have
an
open
source
product
or
at
least
their,
they
have
an
open
source
product,
we
could
potentially
have
a
solution,
even
if
it's
custom
built
for
our
marketing
team.
That's
like
the
netlify
cms
for
managing
the
content,
but
then
our
wysiwyg
editor
is
like
jammed
in
there
right
like
so
you
can.
A
You
can
imagine,
like
one
of
I
think,
one
of
the
one
of
the
bits
of
feedback
that
I've
seen
about
nutify
cms
is
that
it's
it's
very
intuitive
and
it's
easy
to
set
up
and
easy
to
use.
But
then
it's
just
like
you're
editing,
a
form
right,
you're,
you've
got
a
form
field
for
title.
You've
got
a
form
field
for
metadata
and
date,
and
then
you've
got
a
big
text
area
that
takes
markdown,
that
you
can
put
body
content
in
and
you
can
have.
A
You
know
like
multiple
body
content
types
and
images,
and
things
like
that,
which
is
quite
nice,
but
it's
a
it's
a
it's
very,
like
kind
of
blocky
and
text
based
editing
experience
where
we're
going
for
something.
A
little
more
word.
Processor,
like
I
guess,
for
lack
of
lack
of
a
better
word,
a
little
more
rich.
B
A
That
rich
editing
experience
layered
on
top
of
something
like
netlify
cms,
could
be
a
really
compelling
offer
offering
whether
or
not
that's
the
direction
we
head
in.
I
don't
know
we're
going
to
keep
going
down
the
road,
making
our
editor
great
and
and
bringing
in
things
like
editing,
front
matter
and
managing
merge
requests,
and
we
could
back
ourselves
into
competing
directly
with
nullify
cms.
A
We
could
back
ourselves
into
you,
know,
finding
a
way
to
merge
and
I
think
we're
just
keeping
our
options
open
as
far
as
the
marketing
site
goes
clearly,
this
has
not
been
like.
I
haven't
talked
to
netlify
about
any
of
this.
This
isn't
some
kind
of
partnership
announcement
or
anything.
So
this
is
all
just
off
the
top,
my
head
and
and
thinking
about
longer
term
product
direction.
A
I
don't
know
where
they're
headed
with
theirs
either
if
they
have
a
brilliant
editor
that
they've
been
working
on
for
the
past
year
that
they're
about
to
launch
but
yeah.
They
chose
that
and
it
I
I
assume,
we'll
we'll
serve
them
for
at
least
the
next
two
three
years
until
the
static
site.
Editor
is
something
that
they
could
potentially
use
exclusively
or
until
we
have
some
kind
of
convergence
between
the
two
sites.
A
But
there
was
there's
a
lot
of
great
thought
in
those
in
that
epic
and
in
those
issues
and
some
proof
of
concepts
and
I'm
gonna
stay
in
close
touch
with
with
that
team
to
hear
the
feedback
and
how
it
how
it
goes.
As
far
as
implementing
the
integration
and
the
first
use
cases
and
how
long
it's
taking
to
set
up
and
all
that
stuff.
Because
that's
really
really
great
input
for
our
our
group.
As.
A
C
C
C
C
For
inputting
title
and
description,
because
we
haven't
really
done
the
solution-
validation
on
that,
so
this
is
just
like
a
really
lightweight
way
to
go
through
there.
So,
after
you
submit
your
changes-
and
you
end
up
on
this
page
and
get
them
to
go
to
the
view,
the
merge
requests
and
we're
gonna
say:
oh,
you
actually
need
to
make
a
second
change.
So
how
would
you
do
that?
So
the
kind
of
goal
here
is
to
see
if
they
can
discover
this
functionality
here.
C
This
is
currently
you
have
like
an
open
and
web
id
button.
What
a
small
suggestion
I
had
in
mind
for
navigating
back
to
the
stack
site
editor
was
to
have
a
split
button
experience
that
allows
you
to
open
it
up
again
in
static
site,
editor
versus
creating
a
separate
button
like
here
to
say,
go
back
and
then
once
you
click
on
that-
and
you
get
back
into
this-
you
go
into
this
page
here,
and
so
that's
kind
of
like
the
one
flow
to
go
back
into.
C
A
A
A
B
C
C
C
A
C
A
C
So
this
was
good
feedback
from
derek.
This
is
like
the
scenario
where
you're
going
into
the
static
site
editor
for
the
first
time-
and
this
was
my
kind
of
take
on
it
last
week
where,
if
you
just
entered
this
edit
site
editor
from
the
handbook-
and
you
want
to
associate
this
to
a
new
merge
request,
what
would
you
need
to
click
on
to
go
to
that?
C
C
A
C
The
whole
discoverability
of
the
previous
iteration
wasn't
that
good.
So
yesterday
I
was
experimenting
with
some
stuff
and
I
kind
of
landed
on
this
kind
of
thing.
So
if
you
enter
the
static
site
editor
for
the
first
time,
this
is
probably
going
really
overboard,
showing
like
a
new
badge
or
something
to
say
this
is
a
new
branch,
but
you
click
on
that.
Then
this
some
kind
of
model
for
selection,
pops
up
and
then
there's
the
switch
action
as
well
to
call
it
out
a
little
bit
more
another
way
to
do.
B
C
Clicking
on
that
could
open
up
the
pop
model
or
another
way
to
do.
That
is
to
kind
of
have
a
pop-up
thing
here
and
you
have
your
filter
and
if
you
want
to
go
with
the
merge
new
merge
request
instead
of
an
existing
one,
there's
like
some
kind
of
functionality
there
to
be
like
taking
around
to
do
that.
A
C
C
One
thing
that
is
experimenting
is
if
we
have
like
review
changes
and
then
inside
here
would
be
kind
of
like
a
stepper
and
in
here
would
have
your
merge
request.
Information,
but
also
here
would
be
your
area
to
change
change,
the
mr
that
it's
associated
to
plus
potentially
open
up
a
view
to
say
like
view
the
diff,
but
I
think
that's
something
that
we
talked
about,
but
I'm
just
experimenting
to
see
if
it
holds
up
but
yeah.
A
This
is
all
looking
great.
I
can't
make
the
issue
refinement
session
in
the
morning
because
I'll
be
dealing
with
release
stuff,
but
my
initial
take
is
that
I,
like
the
second
direction,
with
the
pop-up
for
discoverability
and
just
keeping
things
in
context
I'll,
be
interested
to
hear
what
the
other,
what
the
rest
of
the
team
thinks,
and
then
you
know,
as
this
goes
into
solution
validation.
A
Obviously
we
want
to
be
really
aware
of
discoverability,
but
I'm
really
liking
this
bottom
bar
paradigm-
and
I
think
this
is
a
this-
is
a
good
approach
for
making
sort
of
giving
the
merge
request
home
there.
It
may
be
a
little
discoverable
at
first,
but
hopefully
it's
a
pattern.
People
can
learn
pretty
quickly.
A
I'm
gonna
go
through
my
agenda
real
quick.
We
already
talked
about
the
cms
choice.
I
just
made
a
note
that
we
did
talk
about
it
and
we
talked
about
this
last
time,
but
this
week
I'll
be
updating
our
category
maturity
because
of
the
outcomes
of
our
first
category
maturity
survey,
it
looked
positive.
Our
scores
were
high
enough.
So
I'll
get
all
the
merge
requests
necessary
to
update
that.
A
Hopefully,
tomorrow,
since
tomorrow's,
the
22nd
would
be
a
good
day
to
do
it
and
the
last
I
just
dropped
a
couple
links.
There's
a
couple
of
new
products
in
like
the
the
dev
and
editor
space
that
I
came
across
last
week,
that
I
thought
were
kind
of
neat
and
try
and
be
a
little
more
aware
of
newer
things,
and
I've
been
waiting
on
this
this
one
for
a
while,
but
panic
is
one
of
the
longest
standing,
independent
apple
software
developers.
A
B
A
I
haven't
checked
it
out
too
closely.
It
has
like
extensions
and
themes
and
all
that
stuff
I'd
like
to
see
a
lot
of
like
gitlab,
specific
themes,
and
I
mean
gitlab,
specific
extensions
added
so
that
I
could
use
this
and
make
myself
more
efficient,
but
it
might
be
worth
looking
into
for
like
how
they
handle
dealing
with
git
operations
within
the
context
of
an
editor.
A
Couldn't
hurt
they're
going
to
be
a
lot
more
dev
focused
or
not.
You
know,
they're,
not
abstracting
the
concepts
away,
but
might
be
able
to
see
how
they
manage
things,
and
the
second
was
just
a
small
project
that
I
saw
on
twitter
called
spanner,
which
looks
like
it's
specifically
designed
to
help
hugo
apps
build
locally,
but
just
a
little
a
little
app.
That
runs,
I
think,
a
local
server,
but
I
like
seeing
stuff
in
the
in
the
static
site
space
making.