►
From YouTube: Create:Editor Product/UX Weekly - 2021-02-10
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
A
Today
is
our
sync
up
for
wednesday
february
10th
thursday,
here
in
australia,
that's
always
confusing,
but
I.
B
A
And
we'll
start
off
at
ux
research
because
there's
more
points
around
there,
so
I
can
kick
off
the
first
point
there.
So
last
friday
I
kicked
off
the
unmoderated
user
testing
for
navigating
two
settings.
So
I
wrapped
up
the
insights
yesterday
so
I'll
be
sharing
that
with
the
team
later
today,
but
yeah,
I
think
from
an
unmoderated
sense.
A
lot
of
the
tasks
were
go
from
this
page,
get
to
settings,
make
the
change
and
then
the
idea
was
come
back.
A
Not
a
lot
of
people
came
back,
whereas
I
think
that's
something
to
take
forth
with
unmoderated
tests
that
people
are
used
to
just
like
going
reaching
the
goal
and
like
calling
it
the
day.
You
know
so
yeah,
plus
no
one
noticed
my
little
back
mechanism
so
yeah.
We
will
probably
have
to
do
another
solution,
validation
on
on
how
to
get
back
to
the
page
that
you're
on
so
yeah-
and
that's
me
for
that
point.
So
catherine,
you
want
to
go
on
with
your
other
points.
B
Sure,
yes,
so
I
have
maybe
one
that
might
not
be
able
to
be
answered
here,
because
it's
just
you
and
me,
but
the
first
one
is
about
the
project
level
settings
tree
tests
that
I
did
so
a
benchmarking
study
for
that
and
that
one
actually
turned
out
to
be
very
interesting.
So
the
insights
are
in
progress,
but
they're
mainly
kind
of
wrapped
up.
B
B
And
basically,
what
I
was
seeing
was
kind
of
like
a
mixture
of
behavior,
that
it
really
there
were
cases
where
it
seemed
like
the
the
task
was
more
strongly
associated
with
the
feature
area.
For
example,
customizing
a
pipeline
configuration
was
more
associated
with
ci
cd
pipelines,
but
then
there
were
other
more
general
things
that
were
pretty
strongly
associated
with
settings
like
setting
up
a
repository,
mirror
or
setting
like
things
related
to
the
countdown
timer
in
the
incidence
issue,
or
things
like
that.
That
seems
to
be
more
related
to
settings.
B
So
this
kind
of
concept
of
our
settings
being
in
these
different
subcategories
that
don't
always
make
it
easy
for
users
to
determine
which
one
to
go
into
because
they
think
well.
It
could
logically
belong
in
both
places,
and
then
another
area
was
just
the
case
where
the
task
success
rate
was
actually
very
low,
but
upon
clicking
closer
into
it,
it
was
because
again
of
going
from
one
setting
to
one
setting
area
to
another
category.
So
they
first
clicked
on
settings,
but
they
got
lost
along
the
way
in
trying
to
find
the
right
place.
B
So
that
has
been
an
interesting
study
feel
free
to
check
out
the
insights
that
are
in
progress,
but
also
let
you
know
once
I've
kind
of
wrapped
that
up
as
well.
A
All
right
cool,
that's
interesting!
You
brought
up
the
thing
about
merge
requests
inside
general.
One
thing
that
pedro
kind
of
linked
me
to
was
that,
like
in
the
cms
studies,
the
one
recommendation
was
already
looking
at
putting
merge
requests
into
its
own
page.
That's
something
our
our
group
was
considering
in
the
past.
A
Then,
in
this
latest
solution,
validation
of
mine,
I
actually
experimented
with
the
idea
of
putting
merge
requests
into
a
separate
page
and
seeing
people
can
discover
it
and
yeah
people
went
to
like
general,
but
then
saw
merge,
requests
in
the
left,
nav
and
yeah.
I
think
it
works
and
if
the
left
nav
is
open,
if
the
left
nav
is
closed,
like
yeah.
Good
luck,
so
that's
kind
of
like
a
dangerous.
B
Game
all
right
yeah.
It
definitely
is
an
interesting
one
because
for
the
merge
request
approvals
task,
it
basically
had
a
lot
of
splits
people.
Looking
in
settings
repository
people
looking
in
the
merge
requests
the
top
level
item,
the
merge
requests
in
in
just
the
prod
the
project
area
and
then
settings
general
and
then
also
some
people.
Looking
at
members
that
was
interesting
as
well,
but
probably
kind
of
thinking
of
team
members
and
approvers
the
people
they
might
have
thought
to
go
to
members.
B
B
So
it
definitely
seems
to
be
more
centered
around
this
problem
that
we're
just
talking
about
like
do
we
create
a
merge
request
category
and
does
that
kind
of
increase
the
the
issue
where
you
have
settings
general
merge,
requests
and
repository
which
could
potentially
have
other
settings
that
are
related
and
might
seem
confusing,
but
we'd
be
clarifying.
Merge,
request
approvals
by
adding
a
new
merge
request.
B
A
A
A
This
research
piece,
the
insights,
is
here,
but
you
have
to
link
to
the
actual
issue,
because
I
want
to
leave
a
few
comments
about
exploring
the
idea
of
where
things
have
their
own
place
like
what
you're
doing
right
now,
like
you
know,
where?
Should
these
things
live
in
their
category?
But
then.
B
B
A
A
Members,
oh
okay,
it's
not
in
this
page,
it's
in
another
page,
so
rather
than
making
people
guess
where
to
go,
which
is
what
we're
doing
right
now,
we're
actually
providing
sign
posting
and
saying,
like
oh
cool,
like
if
you're
looking
for
member
organizations
you're
in
the
right
spot.
But
if
you're
wrong
like
follow,
follow
this
link
here
and
it'll.
Take
you
to
where
you
need.
B
A
That
is
like
a
combination
of
ia
and
navigation
that
I
think
is,
could
be
useful.
I
don't
see
a
lot
of
applications
doing
that,
but
it's
yeah
it's
something
to
think
about.
I
think
it's
in
the
execution
of
how
we
do
it.
B
When
you
actually
get
to
the
content
that
currently
lives
under
repository,
it
might
not
really
have
made
sense
to
them
because,
right
now
it's
just
files
commits
branches,
and
things
like
that.
So
as
opposed
to
clicking
on
I
don't
know
the
merge
request
area
then
you're
like
merge,
requests
and
words
request
approvals.
B
B
I
think
what
what
I
plan
to
get
into
next
is
more
around
this
content
audit,
so
seeing
the
content
that
we
have
in
this
left
sidebar
and
where
it
leads
to
and
the
workflows
that
are
kind
of
being
accommodated
by
this
content.
I
think
that
will
start
to
help
with
mapping
out
where
these
different
things
and
touch
points
should
be
because
it's
definitely
it's
a
complex
problem.
A
B
Is
like
ever
more
complex
every
day
but
we'll
get
there.
But
yes,
let
me
find
that
issue.
I
will
there
are
basically
two
of
them
and
I
will
use
the
one
that
is
most
recent,
because
I'm
going
to
leave
an
update
in
the
old
one
so
that
I
can
close
it.
Let
me
find
it
but
yeah
this,
and
this
is
also
something
because
right
now,
I'm
doing
some
ia
work
for
the
dock
side
as
well.
B
So
I'm
just
basically
in
I
land
right
now
and
I'm
seeing
some
similar
patterns
that
are
basically
the
result
of
the
structure
of
our
gitlab.com
left,
sidebar
kind
of
reflecting
in
the
docs
and
in
docs
they
have
some
patterns
where
a
link
will
open
in
two
places.
That's
interesting,
it's
kind
of
confusing
to
me,
but
I
could
also
see
how
it
may
or
may
not
be
helpful.
B
I
I
will
show
you
because
I
was
like
what's
going
on
here.
This
is
a
little
bit
weird
to
me.
It's
like,
because
when
you
do
ia
research,
sometimes
they'll
tell
you,
you
know.
If
people
are
first
clicking
on
two
different
things
like
there's
an
even
distribution
of
people
clicking
on
ci,
cd
and
settings,
they
might
suggest
putting
the
content
in
both
places
because
both
of
those
are
have
like
an
association.
B
A
A
I
lose
so
I
guess
I'll
go
into
contributions.
A
B
Gitlab,
so
any
any
last
thoughts
on
where
you
can
find
some
contribution
analytics.
A
A
Okay,
I
give
up.
B
A
B
A
B
A
You
know
why
is
so
why?
I
think
it
is
is
understandable
in
the
sense
that,
because
they
could
live
in
these
two
places
like
that,
that's
why
I
think
the
y
is
there.
I
think
the
the
execution
like
if
it's
the
is
it
the
same
url.
B
Oh
good
question,
the
one
is
so
yes,
it
is,
it
is
the
same
url.
So
this
is
a
case
where
it's
the
same
url
there's
some
cases
where
they'll
have
an
explanation
of
the
section
and
they'll
link
out
to
it,
but
in
this
case
they
just
share
the
same
page,
and
I
think
it's
the
same
for
it's
the
same
for
another
one
of
these
two
I
found
two
like
that
and
I
was
like
I
did
not.
A
B
And
the
other
one
like
this
is
issue
analytics.
I
think
it's
under
it's
either
under
issues
or
it's.
Where
is
it
there's
another
place
that
lives.
A
B
B
B
A
Very
interesting,
so
so
what
I'm
like
looking
at
this
is
like
what
I
was
suggesting
earlier
about
related
items
and
related
links
to
other
areas.
That's
like
one
solution
to
solve
this
problem.
This
is
another
solution
to
solve
this
problem
of
like
things
that
could
live
in
multiple
places,
but
I
should
only
live
in
one.
A
A
B
B
A
This
is
like
when
you're
looking
at
the
workflow
stuff,
it's
like
there's
going
to
be
some
overlaps
right.
So
if
you're
optimizing
for
a
workflow,
someone
interested
in
looking
at
analytics
stuff,
putting
all
the
analytics
up,
including
issue
analytics
at
the
group
level,
because
that's
where
a
person
looking
at
analytics
would
expect
to
see
it
makes
a
lot
of
sense
from
the
user
perspective,
but
like
also
at
the
same
time,
if
I'm
managing
groups
or
like
controlling
groups,
I
want
to
see
epics
and
like
controlling
my
group,
import
tools.
A
A
Are
the
same
so
the
seo
part
is
cool.
I
think
it's
just
yeah
the
iae
or
the
visual
execution
is
probably
an
area
to
potentially
improve,
but
but
yeah
I
think
at
the
moment
I
get
it
from
a
user
perspective
like
I
think
in
this
scenario,.
A
B
Right,
it's
it's
super
interesting.
Basically,
what
I
found
during
this
whole
thing
is
that
I
think
analytics
and
settings
might
have
some
similar
patterns
and
potential
problems
going
on
in
them,
where
they
both
have
like
the
breakdown
and
in
analytics
it's
even
trickier,
because
sometimes
you
don't
really
know
what
specific
analytics
you're
looking
for
in
general,
because
they're
very
one
one.
Last
one
last
thing
before
we
move
on
to
the
other
points,
it's
just
like
some
things
like
insights.
B
A
B
A
B
B
Maybe
we
can
talk
about
this
next
time
with
yeah
eric
as.
A
Well,
so
your
question
is
about
like
turning
on
feature
which
feature
were
you
thinking
about?
In
that
scenario,.
B
Potentially
doing
a
longitudinal
study
study
so
a
set
of
changes,
whether
we
were
making
kind
of
like
a
set
of
changes
to
the
left,
sidebar
or
set
it
or,
for
example,
the
set
of
changes
you'll
make
to
the
top
nav
bar.
A
B
That
those
could
be
kind
of
tested
with
the
set
of
people
before
their
launch
to
the
wider,
basically
everyone.
So
there
are
basically
two
ways
you
could
just
roll
them
out,
get
some
initial
feedback
and
then
roll
it
out
for
everyone,
or
you
could
do
a
longitudinal
approach
where
you
have
someone
kind
of
use
it
over
time
and
see
the
experience
over
time
like
how
they
feel
about
it.
A
I
think
what
we
can
do
is
just
raise
that
as
a
question
in
slack
and
then
up
helping
I'll,
raise
the
question
and
now
ping
roman
to
see
if
he
can
give
some
input
because
yeah
you're
right,
we
are
able
to
control
it
at
a
group
level
for
sure
whether
multiple
different
uses
across
different
organizations
like
how
that
might
work,
that's
a
probably
a
more
challenging
event
but
yeah.
I
don't
know
too
much
about
the
details
of
how
much
we
can
control.
B
Yeah
as
well,
I
mean
because
because,
if
it's
not
really
possible
to
do
it
in
a
beta
testing
way,
I
guess
that's
another
way
to
think
about
it.
Where
someone
is
using
this
navigation
for
their
own
work
and
day-to-day
life
and
they
give
feedback
on
it,
then
the
other
good
option
would
be
to
have
it
in
a
project
or
a
group
where
someone
can
go
in
and
just
like
test
it
and
play
around
with
and
give
us
feedback
on
it.
That
would
also
be
a
helpful
too.
It
just
wouldn't
have
that
longitudinal
aspect.
B
It
would
be
kind
of
like
a
a
beta
test,
or,
I
guess,
a
pre-release
process
where
you're
testing
it
and
then
after
that
period
you
release
it
to
everybody,
but
I'm
not
sure
what
engineering
would
they
include.
You
know
like
the
effort
to
do
such
a
thing
with
a
potential
to
roll
back.
Certain
changes
like
what
they
would
think
about
that
whole
thing.
A
You
know
what'd
be
interesting
to
kick
off.
This
composition
is
perhaps
create
an
issue
around
around
what
you
would
want
to
study
longitudinally
with,
let's
say,
navigation
changes
and.
A
That
as
the
catalyst
for
for
our
engineering
partners
to
then
look
at
solutions
of
how
we
might
be
able
to
achieve
this,
like
kind
of
scoping
out
the
release,
because
I
I
think
whether
it
can
be
done
or
not,
the
answer
I'm
I'm
like
hunch
like
yes,
so
so,
like
that's
the
same.
A
It's
possible,
but
I
think
it'll,
give
you,
give
us
a
more
power
and
like
kind
of
help,
push
the
idea
along
if
there's
like
a
purpose
to
this,
in
the
sense
that,
like
okay,
this
is
what
we
want
to
learn,
and
this
is
how
we're
going
to
achieve
it.
Like
you
know,
with
the
longitudinal
studies
like,
what's
that
gap
between
doing
a
longitudinal
study,
you
know
diary
studies
or
constant
feedback,
or
something
like
that
like?
What
do
we
want
to
get
out
of
this?
B
A
A
B
Yeah
yeah
and
I
think
that
will
become
a
little
bit
clearer
as
I
am
able
to
come
up
with
a
list
of
just
things
for
us
to
either.
You
know,
work
on
design
or
implement,
like
we
they're
still
like
at
the
end
of
all
this
benchmarking
research
there's
now
the
phase
of
kind
of
distilling
it
down
into
potential
improvements
that
might
still
need
a
design
phase
or
they
might
be
ready
to
the
change
in
because
they're,
just
like
certain
patterns
that
could
be
changed.
B
I
guess
simply
so
I
don't
know
I
basically.
I
need
to
do
a
bit
more
organizing
of
everything
and
then
discussing
that
with
you
and
then
like.
We,
I
think
we
can
dive
into
this,
but
adam
was
curious
about
this
topic,
so
I
want
to
yeah.
I
think.
B
B
A
An
issue
along
with
this
will
help,
and
I
I
know
that
the
engineers
are
keen
to
get
feedback
on
the
things
that
they're
doing,
and
I
think
this
is
a
great
way
to
like
get
that
feedback
and
make
any
necessary
changes
before
we
roll
it
out.
Bigger,
so
yeah
from.
A
B
A
Yeah
so
on
my
side,
a
bit
slow
on
the
fine-tuning
of
the
epic
around
the
consolidation
projects,
groups
and
more
the
thing
that
I've
been
I
didn't
find
enough
time
to
work
on
is
just
what
this
might
look
like
in
in
the
mobile
view.
So
I'm
looking
to
tackle
that
today
and
tomorrow
today
and
so
hopefully
have
something
for
the
team
to
review
over
the
next
few
days.
A
On
that
the
other
thing
I
wanted
to
bring
up
quickly
was
that,
like
this
week
there
was
a
lot
more
discussions
around
editors
for
myself,
so
I've
been
pretty.
A
The
world
of
settings
and
settings
and
navigation,
so
editors,
have
kind
of
like
been
on
the
back
of
my
mind,
but
this
week
yeah
talked
about
them
a
little
bit
more,
and
one
thing
that
I
was
talking
to
my
manager
marcel
was
about.
You
know
this
idea,
where
we're
looking
at
making
all
the
editors
use
like
editor
light
as
a
foundational
piece.
A
How
do
I
make
writing
markdown
a
lot
easier
for
people
and
yeah
with
edited
light,
and
the
possibility
comes
that
we
can
start
putting
some
that
rich
textness
inside
a
comment
box,
and
that
was
like
a
kickoff
discussion
that
was
happened
maybe
like
two
weeks
ago,
so
cool
interesting
and
then
came
across
this
yesterday,
which
is
our
current,
like
code
review
view.
So
if
people
leave
comments
it,
it
could
look
something
like
this.
Where,
like
the
comment.
B
A
Is
within
there
then
marcel
showed
me
another
tool
called
codestream,
and
this
is
how
they
do
their
comments
and
suggestions,
and
then
I
saw
this
and
I
was
like.
Oh
what
happens
if
you
combine
rich
text
editing
along
with
reviewing
process,
and
it's
like
the
rich
text,
equivalent
of
like
code
reviews
or
reviewing
so
imagine,
reviewing
handbook
changes,
but
in
a
rich
text
environment.
A
This
is
a
code
view
it's
marked
down,
but
this
could
potentially
like
there's
a
lot
of
things
in
here
that
I'm
like
glancing
over
like
highlighting
and
line
line
matching
between
code
and
rendered,
but
the
high
level
ideas
that
you
could
render
the
suggested
changes
out
as
well,
so
that
when
you're
reviewing
you're
like
okay,
I
can
see
that,
like
my
suggestion
to
add
this
little
bit,
will
look
something
like
that.
A
But
that's
something
that
I
I
know
I
wasn't
focused
on
earlier
about
what
does
the
whole
static
site?
Editor
experience?
Look
like!
Not
only
editing
but
also
reviewing,
because
at
that
time
we
were
only
looking
at
the
editing
experience
and
the
flows
associated
with
that.
But
now
that
edited
light
is
in
the
picture.
A
It
kind
of
opens
the
possibility
of
stuff,
because
the
web
ide
will
be
powered
by
editor
light
as
well,
and
that
can
render
code
so
yeah.
That's,
and
that
was
my
like
two
cents
on
this-
that
I
think
there's
going
to
be
some
exciting
stuff,
not
only
in
editing
space
but
like
within
the
product
around
commenting,
but
potentially
even
how
you
reveal
text
which
might
be
powerful
for
yeah
markdown,
edits.
A
B
A
B
A
Here
so
I'm
going
to
end
it
in
line
here.
So
this
is
what
a
markdown
page
looks
like
right
now
today.
The
the
idea
is
that
if
it's
marked
down
potentially
how
we
do
it
is
what
I
should
be
looking
at
soon,
but
we
could
have
like
a
markdown
viewer
of
this
so
then,
or
the
rich
text
editor
so
clicking
on.
A
A
Extending
that
experience
throughout
product
editing
experience.
So
this
is
also
the
underlying
idea
of
the
pipeline
editor
team,
doing
their
like
pipeline
editing
or
using
their
editor
tool
that
edits
a
yaml
file,
potentially
somehow
whether
we're
super
opinionated
on
you
know
the
file
type.
It
dictates
the
the
view
or
we
give
users
that
option.
A
So
what
I
was
saying
is
like
at
the
moment
we
have
this
in
the
which
is
a
code
view,
but
if
we
can
render
this
in
rich
text
potentially,
we
could
apply
a
very
similar
pattern
to
this
world
here
where,
as
you
know,
from
doing
like
code
reviews,
research
where
people
are
kind
of
highlighting
some
text
and
then
making
a
suggestion
and
then
applying
that
change
themselves,
because
that's
the
easiest
way
to
make.
B
B
B
A
B
A
So
I
think
it's
just
an
extension
of
a
job
to
be
done
in
there
scenario
where
it's
reviewing,
so
the
persona
of
eddie
encompasses
like
content,
editors,
writers.
Technical
writing.
I
think
it
has
similar
similar
scenarios,
similar
personas
and
roles.
But
yes
in
a
different
context
of
reviewing-
and
I
think
we
were
heavily
heavily
heavily
focused
on
creation-
and
I
think
reveals
is
definitely
a
key
part
of
creation,
especially
in
a
collaborative
environment.
B
B
Yeah,
okay,
I
need
to
I'm.
I
have
the
your
video
with
marcel
on
my
little
youtube
watch
twitter
playlist.
I'm
like
I
need
to
carve
out
the
time,
because
I
am
very
curious
to
see
the
whole
everything
brought
together
from
what
from
what
it
sounded
like.
It
was
kind
of
like
a
history
and
then,
where
you're,
going
kind
of
conversation,
yeah.
A
B
B
A
That's
a
very
good
question:
that's
something
that
I've
been
trying
to
work
out
over
the
last
two
weeks
because
in
personal
life
with
schools
returning
over
here,
it's
just
like
adjusting
for
pickups
and
stuff
has
been
a
little
bit
more.
A
Than
I
expected
so
yeah,
we
have
some
solutions
along
the
way
for
there,
but
from
a
work
perspective.
A
The
focus
time
for
me,
I
think,
is
still
looking
at
this
solution:
validation
for
setting
search,
that's
like
a
big
priority,
starting
to
make
a
move
on
the
top
nav
so
that
we
can
get
some
engineering
work
to
start.
Looking
into
that,
I
think
we're
very
confident
around
moving
verge
requests
out
of
general
and
then
creating
issues
around
that
and
then
seeing
and
feel
free
to
chime
in
if
we
should
be
a
little
bit
more
cautious
around
there.
But
I
think
and
there's
enough
signs
pointing
to
that.
A
So
those
are
the
my
core
focus.
There's
a
lot
of
other
things
around
yeah.
The
editor
experience
consolidating
the
review
on
the
commit
tab.
So
that's
the
web
id
specifically
so
yeah.
A
B
Like
you
just
have
to
like
there's
these
buckets
of
things,
thankfully
I
guess
I
cycle
through
meetings
every
week.
I
think
that's
what
keeps
me
like.
Okay,
we
talked
about
this
last
time.
We
talked
about
this
and
then
we're
doing
this,
but
yeah
right
now,
there's
been
that
stuff,
but
then
also
like
the
documentation
thing
coming
in
and
then
also
well
before.
B
The
mr
overview
page,
because
I
don't
know
the
widget
is
like
potentially
a
widget
of
widgets.
I
don't
fully
understand.
I
was
talking
to
pedro
and
kai
and
kai
was
like,
I
kind
of
see
it
as
like.
There's
a
merge
request,
widget
and
then
there
are
also
other
widgets
from
other
teams
from
other
groups
and
categories,
and
I'm
like.
Oh,
I
thought
these
were
all
just
one:
cohesive.
A
B
A
B
B
Now,
it's
just
organizing
it
and
breaking
it
down
into
steps
like
like
similar
to
what
you
did
with
this
epic.
I
think
I
should
do
some
similar
things
or
to
the
best
of
my
ability
that
you
did
with
this
simplify
the
menu
options.
A
B
A
Yeah,
you
reminded
me
landing
pages
and
left
nav.
Integra
interactions
is
also
another
thing,
that's
big
or
like
it's
on
my
plate
and
so
yeah.
Where
should
these
pages
land
should
they
just
land
on
themselves
or
do
we
continue
with
these
secondary.
B
Pages,
I
think
we
need
to
have
maybe
in
our
next.
I
think
our
next
thing
will
be
next
week,
actually
just
a
session
about
that,
because
I
was
trying,
I
was
setting
up
a
card
sorting
activity.
I
swear.
This
is
my
last
thing.
I
keep
saying
that
I
was
setting
up
a
card
sorting
activity,
and
so
I
had
to
basically
go
through
all
the
all
the
items
on
the
left
sidebar
to
make
them
cards,
and
I
was
going
through
them
and
I
was
like
so
much
of
this.
B
I
don't
personally
know
whether
how
useful
or
how
often
it's
used,
because
there
were
basically
so
many
list
views
almost
every
almost
every
item
has
a
list
view,
but
then
there
are
also
ones
that
were
very
just
specific
things
you
can
do
like
comparing
comparing
branches
and
then
filtering
certain
things
in
that
one
view.
That's
like
this
one
section
and
I
was
like
I
feel
like
some
of
these
things
could
be
connected
together.
B
A
B
Of
whatever
workflow
it's
occurring
versus
separate
pages,
but
then
I'm
like
maybe
usage
data
would
say
otherwise,
and
people
are
interacting
with
all
these
different
pages
all
the
time.
But
it
just
seems
like
maybe
there's
something
around
improving
that
the
landing
page,
but
also
just
how
they
all
connect
together,
like
yeah,
basically
or
more,
to
follow,
but
that
I
think,
is
going
to
be
a
big
part
of
this.
Maybe
even
more
than
changes
to
menus
and
and
such.