►
From YouTube: Tufts Capstone Project w/ GitLab: Week 9 (04/07) meeting
Description
As part of https://gitlab.com/gitlab-org/gitlab-design/-/issues/2178, this is week 9 of the Tufts / GitLab Capstone project. Gina Doyle, and Ben Leduc-Mills meet with the Tufts students: Calisa, Claudia, Emmeline, Melinda, and Alex, to review student questions and deliverables.
A
A
A
So,
just
looking
at
the
agenda,
I
think
we
really
just
wanted
to
jump
right
in
and
start
to
show
you
the
prototypes,
because
I
think
the
questions
that
I
was
asking
before
would
come
up
through
that
and
kind
of
make
more
sense
with
visualizing
it
yeah,
and
before
that
we
just
wanted
to
say
that
we
got
some
of
initial
feedback
from
our
students
in
class,
and
they
were
really
excited
about
this,
even
though
they
had
no
idea
what
we've
been
working
on.
A
They
were
really
excited
for
us
and
had
some
great
feedback
that
I
think,
even
though
they
didn't
know
what
we
were
working
on.
It
was
still
very
helpful,
so
nice
to
start
by
sharing
my
screen
and
I'm
going
to
walk
you
through
the
first
part
of
the
Prototype
and
then
I'm
gonna,
give
it
to
kalissa
to
go
to
the
second
piece.
A
So
here's
the
normal
page
that
you
would
see
for
the
CI
CD
editor
a
few
differences
to
point
out
here
on
the
top
bar
I.
Don't
know
if
you
can
see
my
cursor
or
not
yeah
I
can
okay
great.
So
we
have
this
pipeline
status
bar
that
we
wanted
to
include
here
to
have
a
very
straightforward
understanding
of
what
is
the
current
state
and
then
it's
still
like
the
view
pipeline
button.
That
was
there
from
the
previous
website
and
then
another
change
here
we
just
have
like
code.
A
Editor
is
like
a
main
title
for
what
is
going
on
down
here,
and
this
is
just
like
the
template
file
for
the
yaml
and
then
so
we
have
this
drop
down,
which
I
changed
from
the
accordion
style
to
drop
down
to
make
it
more
button
like-
and
this
was
kind
of
my
question
here
so
when
I
click
on
it.
I
have
this
drop
down
that
I
made
to
the
full
size
instead
of
covering
the
editor,
because
I
still
wanted
the
users
to
be
able
to
see
all
the
content
below
oh
good
yeah.
A
So
then
they
have
like
a
search
functionality.
They
can
look
at
recent
templates,
which
we
have
some
options
that
are
coming
up
and
then
suggested,
and
this
would
like
be
able
to
scroll
down
and
see
some
more
options
here
and
then
just
as
an
example,
if
I
click
on
JavaScript
yaml,
it
would
come
up
here
as
like
what
that
file
is.
A
A
So
any
questions
on
this
piece,
because
we
have
another
part
of
this-
that
we
wanted
to
share
as
well.
But.
A
Great
so
now,
just
to
like
go
back
to
so
I
have
like
an
easy
flow
into
what
Calissa
is
going
to
share
with
you.
So
we
wanted
to
allow
the
user
to
have
options
for
searching
these
templates,
because
obviously
the
form
that
it
has
now
there's
a
lot
of
content
to
see,
and
this
is
really
limited.
So
if
the
user
doesn't
want
to
use
reason
templates,
they
would
able
be
able
to
search
to
click
on
see
all
templates,
and
then
this
would
pop
the
user
onto
this
pop-up
that
Calissa.
B
All
right
is
this
visible?
Yes,
okay,
yeah!
So
because
of
that
long
list
right,
we
thought
it
would
be
helpful
to
have
some
filtering
and
more
like
search
capability,
especially
if
you're
looking
for
something
specific,
so
I'll
just
walk
through
some
of
the
changes
that
we
made.
First
is
adding
a
search
bar.
So
if
you
click
on
the
search,
you
can
of
course
like
type
whatever
you
want
in,
but
also
it'll
have
some
of
your
recent
searches.
B
So
if
I
click
iOS,
that's
a
recent
one
that
I
used
it'll
update
the
list
to
show
these
are
just
dummy,
dummy
files
at
the
moment,
but
different
iOS
files
Maybe,
and
you
can
go
back
to
the
original
list.
B
If
you
wanted
to
sort
what
was
in
here
right
now,
we
have
some
suggested
templates,
but
maybe
maybe
you're
interested
in
looking
at
popular
ones
instead.
So
we
also
have
a
feature
for
sorting
and
then
some
some
feedback
that
we
got
from
the
initial
usability
sessions
was
maybe
filtering
by
different
languages,
so
we
also
have
a
filter
for
that
so
like.
If
you
wanted
to
only
see
python
templates,
for
instance,
you
can
click
on
that
and
then
the
list
will
filter
yeah.
B
Let's
see
oh
right
and
then
when
you
want
to
select
your
template.
Let's
say
you
want
to
use
the
first
one
in
the
list.
Here
you
can
get
a
preview
of
the
information
of
what
the
template
is
and
you
can
scroll
through
it
and
once
you're
ready,
you
can
either
create
new
or
import
and
replace,
which
was
one
of
the
questions
that
we
had
put
in
the
agenda,
maybe
renaming
these
buttons
or
if
we
could
learn
a
little
bit
more
about
what
these.
B
B
D
E
D
Think,
yeah,
okay,
so
that
was
because
that
those
were
like
in
we
call
it
a
I
think
it's
just
called
a
text
editor,
but
it's.
Those
are
actions
that
are
available
for
any
file
that
you're
looking
at.
So
you
can
like
create
new
at
any
time,
create
a
new
file
or
you
can
import
and
replace
the
file
that
you're
looking
at
right
now,
I
would
say
in
this
case
just
replace,
make
the
primary
like
you
like
use
this
template
right.
D
Feel,
like
that's
the
main
thing
that
you're
looking
for
and
maybe
in
the
future
like
if
somebody
were
to
maintain
all
the
templates
that
are
shown
here.
Maybe
then
like
create
new
would
make
sense,
so
you
could
add
one
so
your
team
could
use
it,
but
I
think
like
from
what
you're
doing
right
now
you
can
just
replace
it
with
useless
or
something
yeah.
D
B
All
right,
I
will
stop
my
share
any
any
questions
on
that
flow
or
just
any
comments.
I.
D
Really
like
how
you're
previewing
these
files
before
like
in
this
case,
one
question
I
had,
is:
what
do
the
three
dots
do
next,
to
templates.
B
Yes,
so
we
don't
have
it
prototyped
right
now,
but
there
was
some
additional
information
on
the
current
templates
page
that
we
thought,
rather
than
having
them
all
listed
at
the
top.
They
could
be
in
like
a
drop
down
here
or
something
since
they're,
useless
and
things
like
that.
D
D
This
is
just
something
I've
I've
learned
over
time
when
you're
displaying
in
from
like,
usually,
we
use
modals
to
stop
the
user
from
doing
something,
it's
like
something
they
they
must
perform
in
order
to
get
to
the
next
task.
So
that's
why
like,
if
you
did
some
delete
button,
we
would
give
you
a
confirmation
model
to
kind
of
like
warn
you
before
you
complete
it
in
this
case,
because
you're
kind
of
like
browsing
through
things,
I'm
wondering
if
you
could
use
a
drawer
here
instead
of
a
modal.
D
So
it's
a
little
like
less
invasive
and
you
have
more
room
so
that
the
modal
isn't
like
constantly
changing
height
when
you
click
on
things,
just
a
suggestion
and
you
don't
have
to
take
it,
but
it's
a
thought.
B
D
D
Yeah,
so
it's
it's
still
overlaying
like
it
is
like
a
modal,
but
you
can
do
other
things
on
the
screen
versus
with
a
modal.
You
can
only
interact
with
the
modal
yep.
A
Yeah
I
think
that's
definitely
something
we
should
explore
if
that's
like,
aligning
with
your
current
design
system,
if
modals
are
more
like
a
stop,
then
we
don't
want
to
change
like
the
understanding
of
how
the
user
obviously
is
getting
into
the
website
currently.
So
that's
definitely
something
we
can
look
into
and
do
you
think
that
all
I
guess
this
was
another
question
with
just
like
the
way
we're
designing
if
like
adding
the
search
bar
is
like
actually
possible
within
you
know
a
drawer
and
all
these
functionalities
can
be
like
combined.
A
D
Be
yeah
because
what
what
you're
using
to
display
those
templates
is
you'll,
be
using
like
a
table
type
of
format
and
then
the
container
that
you
put
those
on
the
table
in.
Could
it
doesn't
matter
like
it
doesn't
impact
the
filters
that
you
add
to
it?
It's
still
it's
just
like
the
background
thing
that
you're
placing
it
in
so
it
doesn't.
You
can
mix
it.
It's
that's
fine!
Okay,
great
yeah,
one
other
question
I
had
for
you
was.
D
Why
did
you
just
to
get
an
understanding
of
like
your
your
design
process?
Why
did
you
go
with
the
modal
for
that,
because
I
think
today
it
like
links
out
to
a
separate
page
right.
A
So
we
kind
of
wanted
to
ease
that
process
and
I
think
that
the
pop-up
is
what
we
all
originally
thought
and
then
we
kind
of
didn't
we
kind
of
had
the
accordion
style
like
the
first
thing,
I
showed
you
and
the
pop-up
separate,
and
then
we
thought
to
combine
those
to
kind
of
give
more
possibilities
for
the
user
would
be
a
good
idea.
D
D
A
So
on
this,
like
drop
down,
where
it
says
see,
all
templates
like
the
current
drawer
system
would
be
another
kind
of
button.
Would
I,
then
replace
see
all
templates
with
a
button
for
like
to
activate
the
drawer,
or
can
this
be
a
button
to
activate
the
drawer?
That
can
be
a
button.
D
The
other
thing
I
would
wonder
there,
though,
if
you
do
bring
up
the
templates
in
a
drawer,
because
it's
you're
still
going
to
be
able
to
see
your
code
editor
because
you'll
like
instead
of
the
modal
like
overlaying,
on
top
of
it
now
you'll
just
have
the
drawer
on
the
side,
I'm
wondering
if
you
really
need
the
preview
action.
A
Again,
yeah
thank
you
for
that's,
really
helpful,
okay
and
then
Claudia
also
had
another
piece
of
a
third
part
of
the
Prototype,
where
we
are
planning
to
combine
these
together,
but
we've
been
all
like
working
separately
and
we're
gonna,
like
obviously
combine
them
later
on.
But
we
wanted
to
share
all
of
the
pieces
with
you
so
Claudia.
If
you
want
to
share
what
you
were
working
on
actually.
E
Even
before
we
move
on
to
that,
I've
got
one
more
question
about
the
template
stuff.
Do
you
want
to
share
your
screen
because
I
don't
know
if
I
can
find
it
like
the
when
we're
talking
about
like
the
the
buttons
and
the
important
replace
versus
like
create
new?
Thank
you.
C
E
Much
I
think
one
of
the
also
one
of
the
other
reasons
why
we
assumed
this
was
like
X
clusive
to
like
templates
is
because
we
assumed-
or
we
thought,
that
you
can
create
new
pipelines
or
that
you
can
have
more
than
one
pipeline
per
project
and
they
would
be
doing
different
things.
So,
in
the
case
of
create
new,
you
would
be
like
create
a
new
pipeline
based
on
the
template
and
in
the
case
of
like
important
replaces,
which
is
like
big
change
in
your
current
pipeline.
E
But
we
actually
don't
know
how
many
like
I
mean
I
assume
it
was
like,
usually
like
only
one
pipeline
per
project
because
I
don't
know
I
don't
see
because
the
pipelines
seemed
different
enough
to
me.
But
do
you
think
there's
ever
a
use
case
where
you
would
want
to
like
export
a
template
into
another
file
and
make
that
a
separate
pipeline
versus
changing
the
pipeline
that
you
have
right
now?
I.
D
Think
I
like
the
way
you're
thinking
but
I,
think
the
for
each
project.
You
can
only
have
one
pipeline
yaml
set,
so
you
can
never
have
two
yamls
and
one
project
but
I
do
like
the
idea
of
exporting
the
pipeline
yaml
like
in
this
project
and
sharing
it
to
another
project,
because
that
can
make
work
easier.
But
that
seems
to
be
out
of
scope.
But
if
that's
something
you
want
to
suggest,
that
would
also
be
fine.
E
Yeah
yeah
totally,
we
were
that's.
Thank
you
for
confirming
my
suspicions
that
you
can
only
have
like
one
yaml
file
per
project
so
that
also
like
our
different,
like
ideas
of
how
the
pipelines
worked,
inform
our
decision
of
putting
more
than
one
button
there.
So
that's
good
to
know
and
thank
you
so
much
yeah.
D
E
Now
now
we
can
talk
now
we
can
talk
about
like
the
a
little
bit
of
the
work
that
I
did
for
changing
some
of
the
navigation
flow.
E
Let
me
share
my
screen
if
I
can
find
that
here
we
go,
should
be
this
one,
not
as
functional
or
not
as
like,
I'm
complete
as
the
other
products
you've
seen
before.
But
essentially
the
main
idea
was
just
to
be
able
to
in
the
pipeline
section
where
we
used
to
have
like
only
like
musical,
like
desktop
or
showed.
E
Every
single,
Pipeline
and
I
decided
that
if
I
thought
it
could
be
useful
to
instead
have
like
the
current
Pipeline
and
like
that's
the
first
thing
that
you
see
to
see
the
status
to
see
how
many
jobs
you
have
to
see
like
the
comment
that
it
is
and
to
essentially
select
the
the
so
the
status
of
the
job
student
be
able
to
like
restart
them
and
stuff
like
that,
and
then
to
be
able
to
click
on,
like
all
the
previous
pipelines
that
you
have
before
and
I
think,
because
the
previous
way
that
you
were
able
to
access
this
page
like
there's
almost
like
a
hub
of
a
pipeline,
would
be
like
if
you
click
on
all
and
then
you
click
on
past
and
then
yeah.
E
For
some
reason,
it
would
take
you
to
like
this
page,
which
I
think
not
only
I
put
a
couple
people,
so
that
was
like
a
little
bit
confusing
too.
So
that's
like
the
main
change
that
it
did
to
Showcase
here.
D
Yeah
I
think
that
makes
sense
I'm
wondering
for
the
text
if
current
or
if
or
if
most
recent
or
something
like
that
would
make
more
sense.
E
E
D
I,
like
that,
I
actually
think
that
the
pipeline
editor
team
who's,
the
ones
responsible
for
like
this
section
is
exploring
making
this
like
a
landing
page
with
current
pipeline
status.
So
that's
right
in
line.
That's.
E
So
cool!
Okay!
That's
that's
good,
then,
because
that
was
like
kind
of
my
idea,
like
almost
like
a
landing
page.
A
And
people
really
loved
this,
like
visualized
section
and
wanted
it
to
be
more
centralized
and
I,
know
Claudia.
We
were
also
curious
about
like
making
it
more
functional.
E
Yeah
totally
I
have
two
questions
about
that.
The
first
question
is
I,
didn't
quite
find
like
the
component
in,
like
the
pajamas
Library,
the
UI
kit,
for
this
yeah.
E
D
Would
be
fine
if
you
have
to
do
that?
Let
me
just
look
real
quick,
I,
think
I
think
it
might
have
been
like
a
pipeline
badge.
Maybe
oh.
E
E
D
D
A
Yeah
but
I
think
basically
what
we
were
curious
about
for
that
also,
obviously
we
we
don't
want
to
go
too
far
with
our
scope,
because
we
do
want
to
like
have
everything
that
we
produce
like
fully
tested
and.
A
Yeah
like
to
the
fullest
extent
that
we
can
like
the
short
time
we
have
left
but
I,
think
we
were.
That
was
very
quick
about
like
making
that
functional
of
like
moving.
You
know
pieces
to
different
sections
like
from
test
to
build
and
something
like
that
right,
Claudia,
I,
think
that
was
something
that
came
up
in
like
the
oh.
E
D
A
D
A
Think
there
was
one
person
that
was
in
the
usability
test
that
was
a
little
less
experienced
and
for
them
this
was
super
like
easy
to
understand,
and
we
had
even
further
thoughts
of
like
what,
if
this
popped
out
to
like
a
just
that
section
to
form
out
in
and
edit
just
that
piece
of
the
test
job
but
I
do
think
that
is
like
beyond
our
scope
but
like
a
super
cool
idea,
because
this
is
a
page
that
people
really
loved.
D
Yeah
I
would
I
would
agree,
I
think
it's
outside
your
scope,
I,
don't
think
you're
gonna
have
time
to
be
able
to
fully
flush
that
out,
but
I
think
you
should
share
it
with
us,
because
we
could
definitely
do
that,
and
would
you
see
so
that
seems
like
for
people
who
are
less
experienced
with
building
pipelines.
They
would
want
to
see
this
visualization
when
they're
building
it
in
the
first
part
yeah.
We.
E
That's
the
even
from
the
other
person
who
is
also
like
some
sort
of
experience
with
like
engineer.
He
suggested
that,
instead
of
like
starting
from
like
the
from
the
editor,
the
gamma
file
to
be
able
to
code
it
directly
and
you
can
just
move
the
stuff
around.
But
it's
already
on
the
template
and
then
yeah
yeah
yeah.
A
Okay,
we'll
make
a
note
for
that
for
later.
Did
you
have
any
other
questions
on
this
specifically
because
I
just
want
to
make
sure
we
get
to
everything
else.
D
No,
and
also
Claudia,
if
you
want
to
use
screenshots
here,
that's
fine
I
was
saying
you
could
change
the
background
color
for
those.
If
you
scroll
down
on
the
right
side
in
your
panel,
yeah
see
how
it
has
like
the
selection
colors,
you
can
change
those
and
it
won't.
It
won't
like
make
the
component
different,
but
it's
like
screenshots
are
fine.
You
don't
have
to
do
it.
Yeah.
A
Yep
definitely,
okay,
so
quick
question
is
we
just
wanted
to
make
sure
what
we
were
using
the
right
frame
size
that
you
would
typically
use.
E
Right
now,
I
think
we
were
thinking
about
either
920
times
1080,
but
I
think
what
we're
working
with
was
this
size
1440
times
10
24.
A
Perfect
and
then
we
also
linked
the
usability
testing
script
and
our
plan
on
the
agenda,
which
yeah
thank
you
Claudia
for
pulling
that
up,
and
we
wanted
to
add
the
sus
to
the
method
as
part
of
the
way
we're
measuring
the
user's
feedback
which
you
had
shared
with
us
previously,
because
I
think
that
would
be
a
really
great
way
to
measure
their
feedback
and
really
get
like
numbers
associated
with
it.
A
To
back
up
what
we're
finding
and
we
were
wondering,
is
there
already
like
a
survey
form
that
is
created
that
we
can
use,
or
should
we
just
like
copy
those
questions
into
a
survey.
D
Where
did
you
find
the
questions
at
first?
Is
it
in
the
handbook
page
or
something
yeah.
D
A
D
I
think
one
other
thing
you
could
do
is
in
the
sessions.
You
could
just
ask
these
and
then
ask
them
to
rate
it
from
one
to
five.
Instead
of
setting
it
out
separately,
it's
yeah.
If
you
have
time
yeah.
A
I
guess
I
wasn't
the
the
thoughts
what
we're
having,
because
we
haven't
really
been
able
to
do
a
full
pilot
session
on
the
current
prototype,
because
we
have
so
many
tests
for
next
week
we
were
thinking
the
two
sessions
on
Monday
are
gonna,
be
kind
of
a
pilot,
but
we're
gonna
try
to
do
it
to
the
best
of
our
ability
and
just
see.
A
If
there's
any
changes
to
be
made
before
we
have
a
bunch
more
tests
on
Wednesday,
so
I
guess
we
have
to
like
figure
out
the
timing
during
those
sessions,
and
we
may
not
have
time
to
get
to
these
questions.
So
I
was
thinking
we
might
send
it
out
after,
if
that's
necessary,
just
as
a
survey.
D
Yeah,
when
you
did
your
first
round
of
usability
tests,
did
you
have
them
write
stuff
on
a
scale?
D
D
Fine,
okay,
okay
in
the
future,
you
could
because
there's
so
many
questions
in
this.
You
could
just
have
them
like
in
the
first
round.
Ask
ease
of
use
scale
like
scale
up
from
one
to
five
and
then
compare
that
to
the
second
round,
and
then
you
could
use
those
comparisons,
but
because
you
haven't
done
that
you
could
just
use
this.
That's
fine!
Okay,.
E
A
Perfect,
so
it
is
three
o'clock,
so
I
don't
want
to
keep
anyone
longer
and
luckily
I
think
we
were
able
to
get
through
everything
unless
anyone
has
any
other
questions
quickly.
C
I
think
I
added
one
more
question
to
the
agenda,
which
was
like:
how
do
we
get
access
to
the
icons
and
the
font?
Because,
when
I
try
to
get
the
icons,
it
led
to
a
repository
and
I'm
not
really
sure,
because
I've
been
just
downloading
them,
detaching
the
instance
on
the
design
system
and
replacing
it.
But
it's
that's.
It
hasn't
been
working
so.
A
That
worked
for
me,
I
was
able
to
add
the
icons
as
a
new
library
and
then
make
it
like
go
through
the
same
process.
We
did
for
the
original
component
Library
so
now
it'll
pop
up
under
assets.
For
me.
A
C
A
Yeah,
so
we'll
definitely
share
with
you,
like
the
Prototype
on
slack
once
we
have
everything
like
integrated
just
for
you
to
see
like
probably
on
Sunday
we're
gonna
have
another
meeting,
I,
think
I,
don't
Sunday
or
Monday
before
our
usability
test
will
have
like
the
full
interactive
prototype
and
we'll
keep
you
updated
on
how
those
tests
are
going.