►
From YouTube: Deep Dive on Pages JTBD
Description
A deep dive into UX Redesign for Pages (https://gitlab.com/groups/gitlab-org/-/epics/2179)
B
B
It's
fresh
new,
no
tab,
saying
I
got
to
get
filled
up
with
tabs.
So
to
me
like
this,
one
is
a
like
super
low
priority.
This
is
a
really
nice
to
have
and
to
me
this
one
is
definitely
dependent
on
that
idea
that
we've
talked
about
before
of.
If
we
can
designate
a
project
as
a
page
project,
then
something
like
this
would
make
sense.
B
B
That
takes
two
leaps
of
understanding
to
know
that
well
to
do
pages,
I
have
to
do
see
ICD,
so
I'm
gonna
set
up
my
CID
to
set
up
my
pages
it'd
be
a
lot
clearer
if
they
just
go
there
and
you
know
so
that
link
and
this
link
would
essentially
be
the
same
link
but
again
I.
Don't
think
we
should
do
this
one
unless
it's
we
first
doing
mechanism
to
designate
a
project
as
a
page
project,
because
you
certainly
would
not
want
to
see
this
and
anything
that
is
not
a
page
project.
B
A
B
Yeah,
maybe
we
should
just
update
this
epic
to
not
have
I
know.
I
had
done
this
on
the
issue
and
you
kind
of
copied
and
pasted
this
over.
We
should
probably
just
update
this
epic
description
to
not
have
this
list
in
here
anymore
and
use
the
get
line.
Mechanisms
to
do
this,
so
if
it's
already
in
the
backlog,
I
think
that's
fine
I
think
that's
the
appropriate
place
for
it.
We
have
the
issue
for
it
here
and
we
can.
A
B
A
B
B
B
B
B
So
to
me
this
is
the
most
important
one
right
like
if
we
can
clean
up
that
settings
area.
I
think
it'll
go
a
long
way
and
then
set
us
up
to
be
able
to
add
features
on
top
of
it
less
features,
but
more
like
things
on
top
I
think
the
rest
of
these
discussions
will
probably
be
much
better
served
once
this
is
done.
This
is
what
I
would
do
first
time
from
a
UX
standpoint,
so.
A
B
Yeah
and
thinking
about
a
little
more
I
think
the
exercise
that
we
did
on
the
feature
flags
would
be
well-served
here
of.
Do
the
do
the
everything
redesign
on
it
as
a
step
one
and
then
then
we
look
at
that
and
see
if
we
need
to
break
that
down
further,
we
might
not
need
to,
but
it
might
be
significant
enough
that
we
want
to
break
that
into
pieces.
Okay,.
A
B
A
A
B
We'll
see
if
we
can
just
include
this
as
part
of
that
and
then
maybe
the
design
from
that
will
filter
down
into
this
I.
Think
we'll
do
that
I
think
we
should
just
do
that
first
kind
of
do
the
big
redesign
first
and
then
see
if
we
can
break
that
into
if
it's
too
big
to
do
all
in
once
we
can
segment
it
out
into
existing
issues
like
this
one
would
be
a
great
example.
B
I
really
think
what
we
should
do
is
12.8
I'll
commit
to
having
that
design
done
and
then
towards
the
end
of
12.8.
We
can
have
another
kind
of
planning
meeting
like
this
and
see
if
we
need
to
break
it
down.
I
think
well.
That
will
give
us
a
much
clearer
vision
of
how
we
need
to
break
down
the
issues
moving
forward,
yeah.
A
That
makes
sense,
I
am
what
I'll
do
is
just
make
sure
that
we're
linking
and
putting
the
labels
so
that
pulls
it
on
to
our
new
planning
board.
So,
like
sea
ice
d
planning
hold
on
to
that
new
board
that
we
have
and
then
we'll
get
it
we'll
be
able
to
look
at
it,
then,
and
then
I'm
gonna
link
these
two
related
issues
together.
B
This
issue,
the
provide
page
setup
instructions
on
settings
page
is
essentially
this
bullet
point
here
provide
an
area
for
you
in
UI
documentation,
it's
just
more
fleshed
out
idea
of
it.
I
can
basically
just
saying
if
you
haven't
set
it
up.
Let's
give
you
some
clear
instructions
on
the
kind
of
landing
page.
B
You
know
most
settings
things
kind
of
have
those
default
area
where
there
is
some,
you
know,
action
items
that
you
can
take,
so
this
would
basically
be
that
and
go
would
go
a
long
way
to
that
other
issue
of
making
it
easier,
rather
than
have
to
go
to
the
documentation
and
understand
these
steps.
Let's
just
present
these
steps
so.
B
A
B
Yeah,
so
this
one's
an
interesting
idea,
like
I,
think
we
should
given
the
fact
that
this
thoroughly
confused
me
when
I
first
tried
to
set
up
get
web
pages,
was
I'm
going
to
the
settings
to
set
up
get
web
pages,
and
there
are
things
that
you
do
in
the
settings
forget
web
pages,
but
really
to
set
up
get
web
pages.
You
have
to
be
in
the
CI
mo
file,
so
I
think
we
should
build
a
connection
point
between
those
two.
B
So
on
the
settings
page,
we
should
have
a
link
that
allows
you
to
go
to
the
amo
file
and
make
the
edits
that
you
need
to
make
so
that,
if
you
do
like
I
did
and
I
would
suspect,
most
people
do
you're
gonna
go
into
the
settings
page
and
realize
oh
I
do
need
to
do
this.
It's
really
more
just
what
connection
kind
of
thing
I!
Think
it's
simple!
You
know
we
just
put
a
link
in
there
and,
like
some
description
text
around
like
why
this
link
exists.
You
know.
B
B
A
B
B
B
A
B
B
No,
no,
no
I,
based
it
on
static
site
generator
calm,
but
these
are
the
20
most
popular
I.
Don't
think
we
should
do
all
20
of
these,
because
you
know
it
starts
getting
into
weird
stuff
down
here
that
I've
never
heard
of,
but
for
a
lot
of
these,
the
upshot
is.
We
have
example,
projects
for
all
of
these
right,
we're
only
missing
a
few
in
here.
A
A
B
B
B
A
B
Don't
want
to
add
everything
known
to
man
on
there
and
also
even
in
the
template
thing
as
well.
We
don't
want
to
add
every
single
template
known
to
man
on
there.
It
would
be
nice
if
that
was
like
a
more
robust
UI
that
was
kind
of
nested
things
and
we
could
search
it.
That's
the
topic
for
another
day,
so
what
I
think
we
first
need
to
do
on
this
is
prioritize,
which
ones
we
actually
do
want
to
promote
to
that
level.
B
B
B
A
B
B
Marketing
research
exercise
to
really
determine,
in
my
opinion,
get
book.
Heck,
CEO,
Jekyll
Hugo
are
far
less
important
than
Gatsby
in
and
view
press.
Certainly
Gatsby
Gatsby
is
like
the
most
popular
one.
So
if
it
becomes
to
the
point
where
this
list
is
getting
too
long,
we
might
even
want
to
like
consider
demoting
one
of
these
and
promoting
one
of
the
other
one.
So.
B
B
As
far
as
which
one
are
popular
and
I
think
they
count
github
stars
and
all
that
good
jazz,
because
it's
a
difficult
thing
to
quantify,
really
because
you
know
these
are
just
libraries,
there's
no
API
that
really
determines
whether
or
not
somebody's
using
these.
So
it
really
has
to
come
down
to
things
like
stars.
A
B
B
At
the
end
of
your
description,
if
you
have
a
link
to
it,
it
shows
up
here
in
your
project
description,
so
it
it
is
visible
that
this
is
pages
and
you
get
right
there,
a
direct
link
to
it.
If
you
want
to
see
it-
or
it
also
shows
up-
you
know
like
at
the
top
here
right,
it's
a
fantastic
place.
I'm
working
on
pages,
one
of
the
most
important
thing
about
pages
is
the
actual
website
that
it's
related
to.
But
to
make
this
happen,
you
have
to
edit
the
project
description
manually
right.
B
A
B
A
B
This
one's
a
stretch,
this
one's
probably
a
let's,
far
down
the
road
kind
of
one,
but
basically,
if
if
your
job
is
producing
a
deployment
to
get
webpages
mm-hmm,
it
would
be
nice
when
that
job
runs,
if
somewhere
in
the
output
on
the
right
hand,
side
right
now,
you
get
like
the
job,
artifacts
section
that
right
hand
panel
over
there.
It
would
be
nice
to
see
like
a
link
to
the
what
it
what
is
output.
B
A
B
B
A
B
B
B
B
B
B
B
B
And
why
that's
important
is
when
you,
if
you,
if
you
do
it
the
way
it
suggests
I'm
forking
the
project
or
creating
it
from
a
template?
The
first
thing
you
see
is
that
readme,
so
that
becomes
like
the
default
like
these
read.
Me's
are
written
as
documentation
right,
but
they're
a
little
confusing
some
cases,
so
we
should
probably
just
tackle
them
on
a
case-by-case
basis,
but
yeah.
If
you
create
an
epic
for
this,
then
we
can
yeah.