►
From YouTube: North Star and MVC overview: Design and Product Review
Description
As we head into our MVC discussion with engineering, Nick takes us through the concepts that could be potential MVCs.
A
There
we
go
okay,
so
with
the
navigation,
North
Star
designs,
they've
come
through
the
most
of
the
final
stages
of
uxr.
We
think
that
we
have
the
winner,
essentially
from
that
which
was
this
one
design.
That's
the
super
sidebar
as
a
team.
The
next
step
is
to
get
this
into
mvcs.
So
last
week,
Nick
and
I
were
going
through
this
one.
A
Just
dropping
some
comments
in
design
management
and
came
up
with
it
looks
like
five
potential
mvcs
that
are
fairly
simple,
that
we
think
we
could
do,
but
we
we
need
to
talk
through
all
of
those
with
with
engineering
this
week
on
Thursday
we're
gonna
have
a
kickoff
for
the
north
star
navigation,
and
so
we'll
talk
through
some
of
these
ideas.
A
B
B
So
I'll
have
a
little
bit
disclaimer
here
that,
although
I
have
these
set
up
in
someone
like
out
of
a
linear
path
of
getting
onto
that
North
Star
one,
this
is
kind
of
like
a
first
pass.
That's
some
a
way
we
could
get
there.
So
a
lot
of
this
ordering
could
be
you
know,
adjusted
based
off
of
what
we
see
as
priority
as
well.
As
you
know,
maybe
development
effort
has
a
lot
of
impact
on
that
as
well,
and
also
like
a
lot
of
these
steps.
B
I
do
think
can
be
done,
probably
in
tandem,
meaning
that
we
don't
have
to
say
like
complete
this
first
step
in
some
instances
before
we
do
like
a
different
step.
So
those
are
a
couple
things
I
just
want
to
point
out
and
I'll
just
go
ahead
and
start
going
through
this.
B
So
the
first
step
that
I
have
in
here
is
starting
the
way
of
a
persistent
sidebar,
because
they're
really
the
main
concept
of
that
super
cyborg
concept,
was
that
we
had
everything
Consolidated
into
a
left,
sidebar
and
so
really
in
order
to
to
get
us
to
that
point.
We
have
to
make
sure
that
we
do
have
a
consistent
sidebar
across
our
product.
Otherwise,
you
know
user
won't
be
able
to
navigate
it'll
get
stuck
in
certain
areas,
so
that's
kind
of
like
a
prerequisite
to
be
to
be
able
to
even
have
this
like
sidebar
proposal.
B
So
this
includes
things
like
in
our
projects
page
today,
our
home
dashboard,
which
is
oftentimes
just
a
projects
list
things
like
your
merge,
requests
and
issues.
Pages,
these
all
don't
have
a
sidebar
today,
and
so
this
is
where
we
would
need
to
look
into
adding
a
sideboard
to
those
pages,
and
when
we
tested
this
super
sidebar
concept,
we
essentially
created
a
separate
section
called
in
that
instance.
B
We
called
it
home
here,
I've
labeled
it
as
your
work,
but
the
naming
on
this
hasn't
necessarily
been
decided,
but
essentially
it'd
be
where
all
of
your
items
would
live,
and
we
would
have
this
as
a
separate
section,
with
its
own
sidebar,
there's,
probably
some
additional
pages
that
we
need
to
consider
as
well
like
one
I've
been
looking
into
is
like
how
do
we
handle
the
search
page,
which
today
doesn't
have
a
sidebar
things
like
a
profile
page?
A
B
B
So,
although
we
don't
have
like
that
issues
and
that
Mrs
links
in
the
top
bar
we're
still
proposing
that
you
would
be
able
to
locate
that
stuff
from
underneath,
like
your
user
menu
in
in
the
post
that
we
have
for
for
where
those
would
potentially
live.
So
you
would
click
on
user
profile.
You
would
see
a
list
of
things
that
are
assigned
to
you
issues,
Mrs
Etc.
You
click
on
that.
It
then
takes
you
to
the
page
that
we
have
today
for
those
the
only
difference
being
you're
now
within.
B
Essentially
this
your
work
or
home
section,
so
you
have
a
different
path
that
you
can
go
there
like.
We
have
a
way
to
switch
into
like
this
home
or
your
work
section
from
this
project
switcher
as
well,
but
yeah
that
duplication
of
ways
to
get
to
this
will
always
exist.
So
here
it'll
be
within
like
the
top
bar
itself.
You'll
click
on
issues
and
it'll.
Take
you
to
issues
and
in
the
future,
it'll
just
be
a
little
bit
different.
A
A
B
Yeah
I
mean
this
so
you're,
essentially
talking
about
this
step
here,
which
I
have
this
notifications
relocated
I
mean
this
as
I
kind
of
mentioned.
In
the
description
here,
this
one
is
definitely
not
finalized.
We
need
to
do
further
research
to
determine
like
what
the
best
path
forward
is
for
this,
but
really
the
goal
is
to
reduce
some
of
the
noise
that
we
have
today
in
that
top
bar
of
always
having
these
notifications.
B
Essentially
in
your
face
and
telling
you
you
have
things
to
do
and
have
them
a
little
bit
more
tucked
away
within
like
a
user
menu
or
potentially
like
some
other
section,
and
then
the
idea
here
that
Austin
proposed
with
this
concept,
was
that
this
little
notifications,
icon
that
we
have
in
the
sideboard
in
this
top
bar,
would
essentially
show
you
anything
new
that
happened
so
like.
B
Okay,
but
yeah
like
I
have
explored.
You
know,
I
even
have
a
concept
here
of
like.
Could
we
even
fit
all
of
those
in
as
like
a
transitional
path
towards
you
know
getting
to
the
sidebar
concept
where
we
initially,
you
know
we
keep
these
in
the
top
bar,
but
we're
still
able
to
move
to
like
the
sidebar
concept.
B
But,
as
you
can
see
here
like
it
gets
very
much
tight
like
we
can't
really
have
all
of
these
items
here
without
making
the
sidebar
larger
and
then
in
that
effect,
makes
your
main
content
area
smaller.
So
there's
some
trade-offs
there
I'm
sure
we
could
figure
out.
You
know
a
different
way
to
handle
this,
but
there's
no
like
really
simple
way
of
like
just
keeping
all
of
those
items
today
and
then
still
moving
to
this
left.
Sidebar
concept.
A
A
It's
not
a
notification
to
me.
It's
a
list
of
of
the
assigned
items
that
I
have
to
do
now.
I,
don't
see
them
like
it's.
A
to-do.
I
have
to
get
back
to
someone,
but
it's
like
it's
kind
of
the
equivalent
of
unreads
in
Gmail
or
something
whether
they're,
unread
or
not.
A
A
Okay,
we'll
add
that
to
the
list
of
further
research,
we've
got
favorites,
sectioning
and
persistency
of
those
and
whether
or
not
I
mean
we're.
If
we
get
rid
of
them,
we'll
hear
feedback,
it's
gonna,
it
will
happen,
so
we
can
like
adapt
based
on
what
people
say
or
in
the
beta
I.
B
B
Yeah
so
once
we
have
a
persistent
sidebar
at
that
point,
we
can
move
in
to
start
utilizing
the
sidebar
for
these.
These
changes
that
we
want
to
make
so
one
of
the
top
ones
being
this
context
switcher.
So
this
test
did
really
well
in
our
in
our
latest
research.
So
for
those
who
maybe
haven't
already
seen
that
research,
we
essentially
have
the
name
of
the
project
or
the
group
as
a
clickable
drop
down
element
that
will
then
show
you
similar
items
that
we
have
in
like
the
main
menu
today.
B
So
like
recent
projects,
recent
groups,
there
isn't
the
ability
to
search
here,
and
we
are
relying
on
global
search
for
that
at
this
point,
but
as
well,
that
there's
also
a
link
that
would
go
to
like
that,
your
work
or
that
your
home
section
so
once
we
have
essentially
the
sidebar
on
every
page,
we
can
move
towards
using
this
to
be
able
to
change
context
instead
of
of
users
use
the
main
menu
today.
So
at
this
point
we
would
essentially
lose
that
main
menu
that
we
have
in
the
top
nap
bar.
B
If
that
does
have
other
links
in
it,
such
as
like
the
dashboard
Pages,
but
that's
those
are
items
that
we
would
plan
to
include
on
that.
You
know
home
or
your
work
section
as
well,
along
with
Milestone
Snippets
activity,
that's
also
in
the
main
menu
today,
so
that
accounts
for
all
of
the
items
in
the
main
menu,
with
the
exception,
like
I,
said
of
search
which
we'll
be
moving
towards
pushing
users
to
use
Global
search
to
do
searching
of
projects
and
groups
in
the
future.
B
It's
possible,
but
at
that
point
it
is
very
much
a
duplication
of
the
same
things
that
we
already
offer
and
so
like
that's
why
I
like
my
first
step,
was
like
we
had
to
have
a
sidebar
to
do
like
the
switcher.
Really
it's
like.
That's.
Why
I
like
this
first
step
and
in
doing
that
we
could
add
these
items
within
that
section
that
we're
creating
for
your
work
or
your
home
or
whatever
we're
calling
it.
A
Yeah
already
built
your
home
we
have
to.
We
have
to
add
that
as
a
step,
because
to
be
able
to
remove
main
nav
and
those
items,
we
do
have
to
have
relocated
them
yeah.
Are
they
all
there
yeah?
That's
the
group's
Milestone
Snippets
activity,
okay,
yeah,
okay,
so
step
one
has
us
duplicated
and
then
we
would
remove
it
step.
Three.
B
A
A
B
Yeah,
the
only
problem
being
at
that
point,
we
wouldn't
have
a
quick
way
to
get
to
this.
Your
work
home,
whatever
we're
calling
it
section
like
that,
is
something
that
we're
adding
in
with
the
context
switcher
as
like
one
of
the
top
items
granted,
we
could
add
that
to
the
main
menu
is
just
I,
don't
see
like.
Is
it
worth
the
time
of
like
adding
another
item
to
the
to
the
main
menu
and
doing
more
work
on
that
versus
just
moving
straight
towards
this
foreign?
B
B
B
B
So
in
the
designs
for
the
North
Star,
we
have
search
as
essentially
just
a
button
that
you
can
access
from
the
left
sidebar
and
the
idea
is
that
would
open
a
modal
where
you
would
essentially
have
the
same
experience
that
you
have
today
in
search
just
within
a
modal,
so
that
would
be
the
update
years.
We
would
transition
search
from
its
location,
the
top
bar
to
be
in
a
button
in
the
sidebar.
B
That
then
presents
our
current
search
experience
in
a
modal.
This
is
kind
of
like
one
of
the
biggest
hurdles
in
terms
of
us
getting
to
the
point
where
we
can
relocate
everything
to
this
left
sidebar.
It's
because
of
how
much
room
search
takes
up
today,
especially
in
this
expanded,
State
I,
don't
know
if
everyone's
aware,
but
when
you
focus
on
the
global
search,
it
does
expand
in
today's
state
to
show
things
like
your
current
context
like
shown
here.
B
B
B
I
will
say
that
there
is
current
work,
that's
been
going
on
in
terms
of
creating
a
command
palette.
It
looks
very
much
similar
to
this
and,
like
I
mentioned
in
the
description
over
here,
like
one
of
our
goals
with
search,
is
to
make
it
into
more
of
a
command
palette
type
experience
where
you
can
both
navigate
as
well
as
search
from
the
same
location
and
I've
kind
of
already
had
discussions
with
Marcel
and
those
that
are
working
on
the
command
palette
to
kind
of
discuss.
B
Some
of
these
items,
but
and
I
think
everyone's
to
have
an
alignment
in
that
regard.
But
my
point
is,
like
there's
already
been
some
work
to
create
an
experience
like
this
using
a
modal
and
there's
actually
like
an
MR
currently
open
around
this.
It's
like
a
proof
of
concept,
but
yeah
like
like
I
was
saying
and
just
like:
it's
not
something.
That's
like
out
in
the
Box
I
think
we
can
do
it's
a
little
bit
more
custom
to
get
this
to
work.
B
All
right-
and
then
this
brings
us
to
the
thing
that
we
were
talking
about
before
of
the
notifications
being
relocated.
So
this
one
definitely
need
to
do
more.
Research
on
need
to
potentially
put
together
some
other
options
in
terms
of
design
to
be
able
to
test
some
different
ways
that
we
could
do
this
with
users,
but
we
really
can't
like
I
mentioned.
B
We
can't
move
all
these
items
that
we
have
today
in
the
top
nav
bar
within
this
limited
space
in
the
left
sidebar,
without
reducing
some
of
this,
whether
we
have
like
some
of
these
just
within
a
drop
down,
or
we
just
figure
out
different
way
to
ladies
out.
It
just
can't
currently
get
us
to
this
point
without
changing
some
of
this
Behavior.
B
So
in
the
the
example
prototype
that
we
used
for
the
previous
testing,
this
is
essentially
what
we
had
where
we
removed
those
items
and
they
were
relocated
underneath
the
user
menu
I
can
go
ahead
and
pull
that
out
too
just
to
show
what
that
looks
like.
B
Granted,
like
I,
said
this,
this
doesn't
like
finalized.
It's
just
one
idea
within
the
user
money
having
a
section
for
to-do's
for
assigned
and
created
issues
as
well
as
merge
requests
that
are
reviewed,
requested
and
assigned,
and
so
like.
This
is
essentially
the
proposal
for
where
you
could
see
those
notifications
and
still
quickly
get
to
those
areas,
but
you're
not
constantly
being
being
reminded
that
you
have
eight
things
there
to
do.
You
know
three
issues
that
you
have
assigned
to
you
and
you
know,
however,
many
merch
requests,
there's,
obviously
pluses
and
minuses
to
that.
B
B
I
mean
we
weren't
necessarily
testing
anything
around
that
with
this
navigation
testing.
Okay,
so
I
wouldn't
be
able
to
say
one
way
or
the
other
that
this
that
the
current
way
we
present,
those
is
problematic
to
users.
A
B
A
Numbers
and
for
me
it's
just
like
in
slack
like
if
seeing
if
I
have
to
respond
to
somebody
or
something
is
important.
So
those
are
the
to-do's
kind
of
like
an
inbox
and
then
my
open
Mrs
I
hit
that
every
day
my
open
issues
and
if
one
has
gone
up
or
down
it's
interesting
to
me
because,
like
I'm,
burning
down,
usually
like
I've
got
like
tons
to
go
through
so
watching
the
number
go
down
or
go
up
means.
There's
things
I
haven't
haven't
taken
care
of.
A
B
Yeah
and
I
came
and
I
mean
I.
Think
that's
why
Austin
was
proposing
that
we
have
this
notification
area
here,
would
which
would
inform
you
of
anything
that
new
happened
so
like
once
you
wait
and
you
like
looked
at
your
assigned
issues.
Essentially
those
notifications
would
go
away,
but
until
you've
essentially
viewed
or
read,
everything
that
is
new
to
you.
You're
gonna
have
some
sort
of
a
notification
saying
that
there
are
items
that
need
your
attention.
A
B
B
There
needs
to
be
some
sort
of
layout
adjustment
in
order
to
be
able
to
move
to
a
fully
left,
sidebar
concept
before
we
can
make
this
change
like
we
can't,
like
I,
said
just
keep
what
we
have
today
as
it
is
and
go
to
this
left
sidebar
so
like
whatever
it
may
be,
whether
it's
you
know
changing
the
layout,
putting
some
stuff
under
any
menu
whatever.
B
That
may
be,
like
that's,
essentially
the
step
here
that
we
need
to
make,
but
there
needs
to
be
research
done
before
we
can
make
that
decision
of
like
what
that
is.
But
at
that
point
that's
when
we
can
essentially
rely
on
just
one
sidebar
versus
having
a
sidebar
along
with
the
top
bar,
as
we
have
today.
A
A
B
I
mean
the
one
that
just
I
think
up
top
of
mine
is
linear.
That's
a
full
sidebar
I
know,
there's
another
one
by
jet
brains,
who
also
uses
utilizes
kind
of
like
a
double
sidebar
like
Austin
had
played
with
some
initial
Concepts,
but
yeah
and
honestly,
that
was
probably
one
of
the
biggest
Praises
of
the
full
left.
B
Sidebar
concept
was
that
they
liked
the
fact
that
the
entire
right
side
was
focused
on
their
content
so
like
they
had
two
distinct
areas
like
one
where
they
do
their
navigation
and
one
is
focused
on
the
content
that
they're
they're
working
on
so
I,
don't
make
sense,
necessarily
see
a
world
where
we
keep
this
top
bar.
Just
because,
like
that
was
one
of
the
major
things
we
were
testing
and
it
tested
very
much
better
with
the
removal
of
the
top
bar.
A
Yeah
and
like
right
now
so
we've
got
the
left,
so
this
is
good
on
the
MVC.
The
left
bar
is
still
Gray
or
sorry.
I
I,
don't
know
what
we
call
that
color,
but
they'll
look
really
light
gray
yeah
technically
it
will
match
the
right
hand
sidebars
if
you're
on
plan
or
Mrs.
When
you
open
up
the
the
side
pane.
A
Will
technically
same,
but
how
will
that
will
it
interact
like
being
like
a
a
line
lower
on
the
right,
or
will
the
right
sidebar
go
all
the
way
to
the
top
of
the
browser?
B
B
As
it
stands
today
like
this,
doesn't
so
like
say
we
just
removed
this
top
bar.
If
you
didn't
see
it
like,
like,
you
know,
could
go
into
the
inspections
displayed
at
none
like
these
are
all
on
the
same
level
like,
even
though
you
know
this
is
within.
You
know,
git
lab.
It's
also
on
the
same
level,
so.
A
B
Yeah,
which
potentially
is
one
of
the
problems
today,
is
that,
like
you,
don't
feel
like
this
is
maybe
specific
to
like
the
location
you're
in,
but
that's
also
potentially,
why
we're
moving
and
changing
that
with
things
such
as
like,
of
course,
I.
Don't
have
any
Mrs
currently
for
review,
but.
B
A
Yeah,
if
we
end
up
following
the
design
of
Mrs,
that
one
did
look
different
more
different
than
the
the
left
nav,
which
is
good
and
when
we
get
to
Colors.
Eventually
right,
you
haven't
got
to
talking
seeming
yet
but
yeah.
When
there's
a
dark
purple
or
a
black
left
sidebar,
then
it's
not
going
to
matter
as
much.
They
won't
compete.
B
Yeah
I
mean
yeah
technically
like
these
are
not
the
exact
like
this
has
a
white
background
on
the
right
side.
We
have
like
our
gray
or
whatever
here
and
so
like.
This
is
essentially
using
exactly
what
we
have
today
for
the
left,
sidebar
but
yeah
in
the
future.
Once
we
get
to
the
amino,
like
things
will
change
where
like
this
will
be
a
different
color
but
I,
don't
know
if
that's
enough
distinction
versus
like
eventually
moving
towards
something
like
this
for
issues
too
and
I.
B
Think
that
probably
is
the
path
that
we're
going
to
be
going
towards,
but
yeah
something
you
want
to
consider.
Here's
how
that's
going
to
be
laid
out
in
the
future.
B
B
B
This
change
just
updates
that
to
free
up
that
area
for
things
that
we
found
better
use
with
some
of
our
current
testing,
which
was
the
settings
link
which
I'll
go
to
in
the
next
step,
but
since
we
want
to
use
this
area
for
for
something
else
in
the
future
and
so
reducing
the
prominence
of
that
collapse
button
because
it
does
take
up
quite
a
bit
of
room
today
and
probably
making
it
so
it
only
shows
on
Hover
is
the
direction
that
we're
looking
at
going
so
it'd,
be
updating
how
that
interaction
Works
today
for
toggling
the
the.
B
With
this
last
round
of
testing,
we
looked
at
having
settings
as
essentially
an
item
that
is
now
in
the
footer
of
each
of
these
menus
for
projects
and
groups,
one
it
it's
something
that
probably
isn't
accessed
quite
as
often
as
some
of
these
other
links
within
our
main
navigation
on
the
left
hand,
side
as
well
as
it
puts
it
in
a
consistent
location
for
both
projects
and
groups,
and
seeing
that
we
want,
we
have
quite
a
bit
of
different
menu
options
bin
settings.
B
A
B
And
that's
what
I
was
about
to
say
is
like
this
is
like
another
one
thing
for
like
this
could
be
done.
You
know
way
earlier
in
the
process,
but
it
does
have
a
dependency
of
like
changing
how
we
do
the
collapse
Behavior
today
so
like
some
of
these
are
ordered
based
off
of
dependency,
but
there's
definitely
a
room
to
move
like
these
around
in
terms
of
when
we
decide
to
do
them
next,
I'm,
on
here
navigation
groupings.
B
So
this
is
another
somewhat
larger
change
and
potentially
could
be
somewhat
controversial,
just
because
it
does
by
default,
hide
some
of
your
items
within
a
grouping.
This
did
test
well,
just
because
users
preferred
a
less
overwhelming
menu
to
begin,
and
then
these
logical
groupings
did
seem
to
make
sense
as
to
where
these
items
would
live.
B
We
definitely
need
to
do
further
research
to
make
sure
that
we
do
place
all
the
items
within
groupings
that
do
make
sense
and
that
these
names
are
what
we'd
want
to
move
forward
with,
but
that
is
essentially
what
this
step
is
is
consolidating
our
current
items,
Within
These
groupings,
some
items
we
do
feel
are
used
enough
where
we
want
them
always
exposed.
B
Examples
could
be
like
project
overview
like
your
issues,
your
merch
requests,
potentially
pipelines.
These
are
the
initial
ones
that
we
tested
out,
but
that
doesn't
mean
that
those
are
necessarily
the
final
ones
that
we
would
want
owners
exposed,
and
this
would
be
the
same
for
all
projects
and
it
would
be
the
same
for
all
groups.
It
wouldn't
be
something
that
you
would
essentially
customize.
B
B
This
just
shows
an
example
of
like
expanding
one
of
those
sections.
What
that
would
look
like.
B
Yeah,
so
you
we
currently
have
you're
talking
about.
Essentially
these
menus
fly
out
menus
so
yeah.
We
wouldn't
keep
those
with
this
new
approach.
We
would
have
these.
You
essentially
would
need
to
select
one
of
these
sections
to
expand
it,
and
then
you
had
to
select
the
item
that
you
want
to
go
to.
We
wouldn't
have
a
flyout
menu.
B
Yeah,
so
with
that
change,
a
hope
would
be
to
somewhat
quickly
behind
that
move
into
this
concept
around
favorite,
so
to
help
some
users
deal
with
this
change
of
having
these
items
located
within
these
sections,
but
still
wanting
to
maintain
things
that
they
care
about
the
most,
as,
like
a
very
you
know,
accessible
item
we're
looking
at
the
possibility
of
being
able
to
favorite
items
within
their
menu.
So
you
know
when
you
expand
something
like
develop.
You
can
see
if
hovering
over
these
items.
B
B
That
keeps
things
still
somewhat.
You
know
Consolidated
and
less
overwhelming
for
the
majority
of
users,
but
then
still
gives
you
the
ability
to
to
kind
of
build
out
a
menu
that
suits
you
best
and
the
workflow
that
you
need
to
go
through.
A
Setting
it
up
like
I
might
want
to
go
to
the
issues
of
the
pajamas
project
so
like,
rather
than
navigate
to
it,
and
then
click
the
phone
right
there
there
may
be
one
I
want
to
promote
all
the
way
to
a
favorite.
For
me
on
my
user
page.
A
B
B
You
were
talking
about
pipeline.
We
don't
currently
show
any
sort
of
indicator
with
pipelines
today.
A
B
B
We
put
together
kind
of
just
a
quick
mock-up
of
some
things
that
we
could
see
value
in
having,
but
these
weren't
necessarily
based
off
of
the
previous
research.
They
were
just
a
quick
way
for
us
to
to
put
together
a
home
page
and
test
like
having
some
different
items
here
and
just
a
location
for
users
to
go
back
to.
Definitely
more
research
needs
to
be
done
on
this,
as
well
as
like
looking
into
any
past
research,
but
this
will
definitely
probably
be
a
larger
effort.
B
I
mean
we
could
definitely
start
small
with
you
know
having
it
very
minimal,
like
just
maybe
recent
work
items
or
something,
but
we
also
have
to
realize
that
we
do
offer
the
ability
to
change
your
current
home
dashboard
today
to
different
things,
and
we
don't
necessarily
want
to
take
that
over
with
an
experience
that
is
very
minimal
sort
of
such
that
we
just
did
recent
work
items
if
that's
not
as
valuable
to
something
else
that
users
have
set
up
today.
B
We
want
them
to
be
able
to
continue
using
that
until
we
have
this,
maybe
more
built
out.
So
there's
definitely
could
be
an
iterative
approach
to
how
we
do
this,
but
we
also
have
to
take
into
account
what
users
are
able
to
do
today
in
terms
of
selecting
different
home,
dashboard,
States
or
versions.
B
Yeah,
so
that's
one
week
we
could
handle
is
like.
If
you
haven't
changed
it,
then
we
just
update
it
with.
Maybe
this
is
what
we
see
his
most
value
or
something
because
we
still
are
making
it
very
easy
to
get
to
the
projects
list
from
here
anyways,
but
for
some
of
those
other
things
that
users
have
chosen
to
have
us
their
home
dashboard.
Maybe
we
would
leave
that
for
them
until
we
had
this
more
built
out
or
further
validation.
A
B
A
B
And
then
that
leads
us
to
I
think
this
is
the
last
step.
I
have
yeah,
so
this
is
the
last
step.
I
have
and
essentially
like
this
to
me,
although,
like
I,
enjoy
themes,
I
feel
like
it's,
the
least
it's
adding
the
least
amount
of
value
towards
our
path
to
the
north
star,
and
it's
like
that's
why
it
is
last.
It's
just
essentially
modifying
some
of
our
current
theming
to
make
that
experience
better,
as
well
as
reduce
some
of
the
amount
of
themes
that
we
currently
have
today.
B
B
So
the
idea
is
that
we
reduce
the
amount
of
themes
and
then
we
would
try
and
focus
probably
on
like
a
dark
version,
a
light
version,
maybe
like
a
brand
version
and
something
like
taking
into
kind
of
accessibility
like
having
maybe
some
accessible
oriented
themes
as
well,
just
based
off
of
of
those
needs.
B
So
this
is
going
to
be
like
our
last
step
towards
getting
to
what
we
have
here
as
like
our
North
Star
and
granted.
This
isn't
like.
A
A
A
A
B
B
So
yeah
I
mean
this
had
mixed
kind
of
feedback
in
the
session.
Some
people
really
liked
it.
Some
people
really
didn't
like
it.
B
What
we
were
looking
at
doing
with
that
feedback
was
being
a
bit
more
subtle
with
the
use
of
the
theme
color,
which
is
why,
like
you
see
here,
actually
these
are
the
light
and
dark
versions.
I
had
a
different
version,
which
is
essentially
like
this
one.
Where
like
say
this
is
the
purple
thing
like
we
would
use
purple
as
like
an
accent
color
and
then
not
as
much
as
like
a
full
background.
Color,
that's
interesting.
B
It's
like
that's
why
we
were
exploring
that
were
options
that
were
a
little
bit
more
subtle
in
the
color
usage
yeah
like
so
these
are
really
just
kind
of
dark
and
light
versions.
This
was
more
like
a
brand
like
this
is
essentially
a
similar
branding
that
we
use
on
our
marketing
site.
If
you
view
that,
like
the
sidebar
that
we
have
there,
so
that's
one
option
or
doing
something
like
I
said
more
like
this,
where
we
just
use
that
as
more
like
an
accent
color.
But
what
I
was
going
to
mention
with.
A
B
Yeah
and
that's
that's
the
feedback
that
we
got
from
those
that
liked
more
of
like
a
darker
theme
of
like
they
liked
you
know,
being
able
to
focus
here
on
the
right
hand,
side
and
this
kind
of,
although
it
was
like
kind
of
bold
it,
it
kind
of
went
to
the
to
the
background.
So
some
users
don't
prefer
more
of
a
lighter
approach
like
that's.
B
A
I,
like
moving
this
to
the
end,
because
it's
like
it's
not
the
value,
add,
but
it's
it's
more,
the
pretty
parts
of
it.
However,
if
we
gate
it
on
theming,
which
we
have
on
our
roadmap
as
one
of
the
things
we
have
to
tackle,
that's
a
large
project,
that's
an
that
would
be
a
year
if
we
have
to
gate
on
themes
working
in
gitlab.
That
would
put
us
behind
maybe
even
a
year
of
work,
but
we
can
verify
that
with
engineering.
A
B
That's
why
I,
like
ideally
I,
think,
would
be
good
to
start
with
maybe
two
versions,
just
like
a
light
and
dark
like
I,
don't
think
the
effort,
for
that
would
be
too
much
but
I'm
sure
yeah
Engineers
will
have
yeah
better
perspective
on
that.
Just
because,
like
we
do
have
kind
of
two
different
perspectives
when
it
comes
to
viewing
This
and
like
we
very
much
saw
that
in
the
testing.
Some
people
really
liked
a
dark
sidebar.
B
Some
people
really
like
a
more
clean,
like
light
version
for
a
sidebar,
and
so
if
we
were
able
to
at
least
offer
those
two
I
think
we
would
at
least
handle
majority
of
cases.
The
color
options
is
where
it
gets
to
be
like
a
very
much
more
opinionated
and
like
just
kind
of
like
fun
for
people,
but
having
a
light
and
dark
version.
I
think
is
a
bit
more
important.
A
A
Indigo
yeah
but
I
agree,
though
I
think
if
we
haven't
opt-in
to
a
beta
with
a
switch
which
we
have
to
talk
about
as
well
and
the
user
can
go
between
normal
and
North
Star
during
the
six
months
that
we're
building
I
think
it
would
be
very
cool
for
it
to
be
real,
clear
that
you're
on
Northstar
so
like.
If
your
knob
is
dark,
you
know
you're
on
it,
you
could
switch
back
to
normal.
A
If
you
want
to
go
back
to
the
light
world
where
we
have
everything
light
for
everybody,
so
there
could
be
less
during
the
time
we're
building.
Maybe
we
get
one
up,
that's
dark
people
can
see
the
contrast
and
then,
as
we
refine
at
the
end,
we
can
give
them
the
switcher
between
light
and
dark
or
something
like
that
and
then
to
themes.
B
A
Masculine,
like
the
black
I,
don't
know
even
with
just
having
one
little
purple
thing
like
it
feels
to
me
like
it's
just
the
void
of
color
or
like,
like
a
I,
don't
know,
I
don't
want
to
gender
anything
but
like
to
me.
I'm
just
like
me
feels
like
a
men's
product
or
something
like
when
it's
all
black.
B
B
Before
I
had
like
this
top
portion
as
purple
as
well,
and
like
people
thought
there
was
too
much
color
so
like
what
I
guess,
I'm
trying
to
say
is
like
none
of
this
is
all
finalized.
This
is
definitely
still
in
the
works,
but
it's
also
not
the
most
important
stuff
right
now
that
we
need
to.
B
A
B
B
B
That's
that,
like
yeah,
none
of
us
finalized
still
working
through
it,
but
I
I
do
like
bringing
in
like
more
of
our
like
braining,
that
we
use
externally
into
our
product.
I
think
it
makes
it
ties
it
a
little
bit
better,
but.
A
B
B
No
so
yeah
like
this
is
just
like
the
the
North
Shore
concept.
I
was
showing
is
like
kind
of
we're
trying
to
go,
but
that,
essentially,
is
all
of
it.
Like
I
said
all
this
is
kind
of
open
to
interpretation.
How
we
want
to
move
forward.
It's
just
my
kind
of
first
stab
first
pass
that
laying
out
a
path
that
forced
to
add
value
along
the
way
while
getting
us
to
a
state
where
we
can
support.
You
know
a
full
left,
sidebar
concept.
A
Yeah,
this
is
good
and
I.
Think
for
Thursday.
So
I'll
share
this
video
with
the
team.
They
can
watch
this
and
kind
of
catch
up
on
just
seeing
each
one
and
then,
when
we
go
through
them
in
the
sync
call
everyone
who
should
be
on
the
same
page,
but
we
can
kind
of
I.
Don't
did
you
call
them
do
they
have
numbers
one
two,
three.
A
Yeah
steps,
okay,
so
conversations
we
can
have
on
each
one
in
the
agenda
can
just
get
them
in
for
each
different
step
and
then
we'll
see
if
they
have
feedback
in
terms
of
order
splitting
into
even
smaller
steps
in
between.
But
this
is
really
cool
to
see
it
all
come
together.
I
like
seeing
all
the
left
nav
content,
just
in
that
new
sidebar
too,
so
that
it's
just
clear
we're
just
kind
of
moving
it
over.
As
is.
B
Be
helpful
is
like
showing
some
of
this
like
iterative
approach
of,
like
you
know
it's
hard
to
see
like
our
currency,
at
industry,
new
and
not
like,
be
able
to
quickly
see
all
the
differences
and
so
by
like
showing
how
we
can
slowly
like
add
things
in
while
keeping
some
of
our
current
state
I
think
is
helpful.
It
helps
to
kind
of
break
things
down
into
like
how
we
can
kind
of
go
on
this
on
this
path,
while
my
while
not
having
to
do
everything
at
once
and
like
flipping
a
switch
but
right.
A
So
do
you
mind
uploading
those
onto
the
design
management
as
well
before
Thursday?
Just
so,
we
have
them
there
as
a
reference.
Yep
I
can
do
that,
and
then
we
can
break
them
down
from
there
as
needed,
but
with
this
list
as
long
as
engineer
validates
that
engineering
can
validate
it
and
help
us
I,
think
we've
got
a
amazing
plan
like
we've
got
almost
10
except
10
to
getting
towards
it.