►
From YouTube: Slippers Commit Event Template Overview
Description
Tina Lise Ng and Tyler Williams of the Digital Experience team go over the Figma files, design approach, and requirements for the Commit template in the Slippers design system.
ENG: Slippers: Implement event components and template
epic: https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/315
A
Hello,
I
guess
we
didn't
talk
about
who
would
kick
it
off,
but
yeah,
so
we've
got
tyler
and
tina
here
from
digital
experience
and
we're
gonna
go
over
the
templates
and
blocks
for
the
events
cms
did.
I
did.
I
cover
what
we're
going
to
talk
about.
B
Yeah,
I
think
so
yeah
and
probably
talking
about
like
high
level
like
goals
and
like
things
to
know
about
as
we
go,
because
we're
gonna
be
building
these
out
in
slippers
over
the
next
two
weeks,
like
I've,
already
kind
of
taken
a
look
at
a
few
things.
I
know
I
have
a
few
questions,
so
it'll
be
nice
to
sort
of
talk
that
out
and
have
other
folks
be
able
to
hear
that
too.
A
All
right
so
I'll
just
do
then
I'm
sharing
my
screen,
I
believe,
and
I'll
just
do
a
quick
overview
of
what
we're
looking
at
in
the
sigma
file.
A
A
So
these
here
is
a
big
list
of
the
approved
blocks
for
this
first
iteration
of
the
events
templates
that
we're
going
to
build
out
in
slippers
and
have
available,
and
then
there's
some
readmes
here
we
need
readme
on
the
side
when
we
felt
that
there
was
some
extra
information
that
needed
to
be
written
down
or
noted.
A
So
here
we
have
a
template,
called
the
mother
template,
so
how
this
is
gonna
work
tyler.
Is
that
because
the
event
stages
vary,
there
are
typically
five
stages
of
an
event.
So
there's
like
hey
we're
having
an
event
we
don't
have.
A
We
maybe
have
the
dates,
but
we
definitely
don't
have
speakers
we're
calling
for
proposals,
but
look
at
the
look
at
these
recaps
and
videos
of
past
events,
and
then
you
know
the
stages
continue
on,
as
there
are
sponsors
announced,
and
speakers
announced
and
dates
figured
out
and
scheduled
figured
out
so
because
we're
not
building
a
modular
template
that
our
content
editors
can
drag
and
drop.
Sections
we've
had
to
build,
propose
a
mother
template
that
kind
of
anticipates
all
of
the
different
stages
upcoming
stages
of
the
event.
B
A
A
We'll
we'll
deal
with
those
scenarios
when
they
show
up,
but
the
events
team
has
have
taken
a
look
at
this
and
seem
confident
that
we've
covered
all
the
bases
for
at
least
for
commit
and
again
we're
using
commit
as
a
use
case,
but
hopefully
we
can
use
this
for
all
events.
A
That's
it
for
that
and
then
these
tyler
you're
familiar
with
my
pressure
tests.
So
these
are
three
pressure
tests
for
the
stage
one.
So
this
is
pre-event
another
pre-event,
but
where
things
are
announced
like
a
schedule
and
speakers
and
then,
while
during
the
events
so
at
this
point
we're
going
to
be
wanting
to
put
videos
and
what's
happening
now
and
then
remove
some
other
information.
A
A
notable
thing
also
is:
if
you
go
to
the
current
here,
I
have
it
open
here.
The
current
commit
event
page
these.
This
is
a
one
pager,
and
these
are
anchor
links.
There's
no
change!
We're
still
going
to
use
the
structure
except
we're
going
to
move
the
navigation
out
of
the
header
area
to
the
side
here.
A
This
frees
up
also
this
nav.
If
we
ever
want
to
put
the
get
lab
nab
there
for
other
scenarios,
we're
not
going
to
do
that
for
this
one
and
then,
as
you
scroll
down
the
the
pages,
will
will
notify
you
that
you've
you're
in
a
new
section-
and
this
will
be
sticky-
I
think
that's
probably
the
biggest
change
to
the
page
yeah.
B
B
A
B
A
Cool
great,
I
want
to
call
out
something
on
this
side
here,
so
I
there's
a
branding
section
here.
This
section
is
obviously
meant
for
the
brand
team.
The
idea
is
that
we're
proposing
some
areas
where
the
different
branding
for
different
events
can
can
stand
out.
So
maybe
background
images,
custom
icons,
because
we
don't
want
every
single
event
to
look
exactly
the
same.
Each
event
has
its
own
logo
has
its
own
color
palette,
but
also
we're
working
inside
a
cms.
A
So
we
we
can't
be
completely
flexible,
but
we
should
have
some
room
for
flexibility.
I
haven't
been
able
yet
to
sync
up
with
the
brand
team
on
this:
I'm
not
sure
if
they've
looked
at
it,
some
of
them
have
like
emily
and
some
of
the
events
coordinators,
but
it's
just
something
to
keep
in
mind
as
you're
building
it
that
there
are
some
areas
that
are
gonna
have
custom,
maybe
icons
here,
and
I
know
that
in
the
resources
cms
for
the
topics
page,
the
icons
come
from
a
library
of
icons.
A
A
B
Yeah
that
should
be
playing
time
because,
like
the
for
this,
like,
if
we
don't
hear
like
in
a
worst
case
scenario,
if
we
got
the
final
decisions
on
that
at
the
end
of
this
iteration,
that's
fine,
because
we
can
use
these
placeholders
as
we
build
it
out
in
slippers
and
like
we
don't
need
to
worry
about
the
like
the
final
icons
until
the
next
iteration
when
we
put
this
all
together
in
a
boundary
lab.
B
A
Cool
also,
I'm
sure
you
you
will-
and
you
have
encourage
you
to
read
these,
because
there
are
some
scenarios
which
I've
noted
where,
if
an
event
has
passed,
the
video
will
be
replaced
with
a
recap,
video
things
like
that.
I'm
also
unsure
about
some
of
the
functionality
of
these
videos,
because
sometimes
there's
two
videos,
sometimes
there's
three
videos,
sometimes
there's
five
videos.
When
does
it
transform
into
a
carousel?
Is
that
a
different
block?
A
B
Do
you,
oh
videos,
good
question
for
you?
Do
you
know
this?
I
don't
know
if
you
know
this
off
the
top
of
your
head.
Are
we
anticipating
that
these
are
all
youtube
embeds,
or
should
we
be
more
flexible
in
what
like
the
video
source.
A
I
would
stick
to
what
we
know.
So,
let's
continue
on
with
git
lab
I've
seen
videos
on
vimeo,
but
they
also
exist
on
youtube.
Okay,.
B
B
A
B
B
I've
got
a
specific
question
on
this
header
because
that's
what
I've
been
sort
of
looking
at
right
now,
so
video
or
image,
I'm
assuming
this
video
block
you
have
here,
that's
like
442
right-
is
that
so
right
now
the
little
play
button
makes
me
think
like.
Oh,
this
is
like
the
video
size.
Do
you
basic?
Is
that
same
size
for
image?
Basically,.
B
A
A
You
can't
see
I'm
like
pointing
at
my
face
here
is
where
we
want
to
leave
breathing
space
for
that
sticky,
navigation
cool.
So
I
want
to
stay
inside
this.
This
column.
A
B
A
Okay,
lauren.
A
Have
seen
this
and
are
aware
of
these
dates,
and
I
I
believe
we
scheduled
accordingly,
but
if
ever
you
need
to
reference
back,
it's
something
like
when
is
this
speaker's
block
going
to
be
needed?
Well,
it's
it's
in
in
this
document
and
what
I
have
here
in
purple
are
links
to
the
each
block.
So
this
is
created
by
the
brand
team.
A
A
And
I
did
note
this
during
our
sprint
planning
meeting
that
some
of
these
exist.
Okay
and
I
wrote
from
slippers,
but
when
I
say
from
slippers
I
mean
from
the
figma
slippers,
so
lauren
did
point
out
that
these
have
to
be
kind
of
rebuilt
in
slippers,
whatever
not
sure
exactly
the
details
of
that.
But
if
you
want
to
go
check
out,
you
know
some
existing
code,
sammy,
probably
already
built
this
brand
brandon
built
this
one
and
I
tried
to
know
when
they
already
exist.
So
you
just
don't
have
to
double
work.
A
B
Well,
awesome,
I
don't
have
any
other
specific
questions.
This
seems
pretty
straightforward.
I've
gone
through
the
readmes
and
they
made
a
lot
of
sense
and
it
sounds
like.
Oh,
maybe
here's
another
good
like
high
level
question.
You
mentioned
you're
working
on
like
the
mobile
views
and
stuff
today,
and
I
guess
my
like
I
I've
sort
of
been
like
preliminarily
working
on
the
header
I
just
wanted
to
like
get
in
here.
So
I
could
see
like
you
know,
what's
ahead
of
me
for
the
rest
of
this
iteration
like?
Is
it
basically
like?
B
Is
it
cool
if
I
just
keep
moving
forward
on
that?
Do
you
want
me
to
like
hold
off
for,
like
anything
or
anyone
else,
who's
working
on
this,
like
anyone,
who's
grabbed
issues
like?
Are
we
good
to
basically
go
on
this,
or
do
you
want
like
an
extra
like
the
rest
of
this
day
or
something.
A
No,
I
here
is
the
design
file.
It
says
whip
some
of
the
elements
or
some
of
the
blocks
that
didn't
exist
before
may
need
a
little
bit
of
approval
from
someone.
But
all
of
this
is
just
slippers.
It's
just
slippers,
ui.
You
can
start
taking
a
look
at
this.
It's
all
our
header,
our
headers,
are
our
body
copy
sizes.
There's
you
know
nothing
really
different
from
slippers,
so
I
feel
confident
that
you
can
actually
start
with
at
least
some
of
these
heathers,
these
basic
blocks.
These
list
blocks.
A
B
Call
it
super
early
and
I
will
get
time
back
and
I'll
post
this
recording
like
in
the
next
like
whenever
it's
ready
I'll
get
this
posted
and
share
it
along
with
folks.
But
I
think.
A
B
Yeah,
I
feel
really
confident
about
delivery
on
this.
It
looks
like
lauren
split
this
out
into
an
epic
for
the
slippers,
build
for
this
iteration
and
then
the
middleman
integration
for
the
next,
and
I
think
that,
like
it's
a,
I
think
the
timelines
make
a
lot
of
sense.
So
I'm
not
worried
about
any
of
this
at
the
moment.