►
Description
Javi walks through a proof of concept using the created footer component on the home page of about.gitlab.com
Slippers Repo: https://gitlab.com/gitlab-com/marketing/inbound-marketing/slippers-ui
A
Hi
everybody,
my
name
is
javier
and
I
am
working
with
the
digital
experience
team
and
right
now
I'm
going
to
be
walking
you
through
how
to
add
a
slippers
component
onto
dub
dub
dub
about
gitlab.
So
I
work
in
marketing
so
we're
working
on
a
design
system
and
implementing
that.
So
I'm
sharing
my
screen
right
now.
Hopefully
you
can
see
this.
Your
screen
share:
okay,
sick,
okay.
A
So
right
now
I
was
working
on
recreating
our
footer
right
here,
and
this
is
an
issue
that
we've
been
working
on
with
a
while
we've
run
into
some
issues
with
trying
to
integrate
with
some
of
this
stuff,
and
so
someone
on
my
team
asked
me
in
the
mr
review
to
kind
of
like
going
through
the
process
of
me
trying
to
integrate
this,
which
I
thought
would
be
a
good
opportunity
to
express
that.
A
So
here
I
am
so
what
I've
done
beforehand
essentially,
is
I've
built
the
slippers
package
using
npm,
sorry
yarn
build,
and
then
I
bumped
the
version
number
here
to
0.8
alpha
and
that's
all
I've
done
so
far.
So
if
I
hit
get
status
right
now,
you'll
see
that
I've
done
that.
So
right
now
I'm
just
going
to
commit
that.
A
0.8.0
alpha,
so
I'm
gonna
do
that
see
that
that
was
done.
Okay,
so
get
status
what's
happening
and
because
I
am
ended
a
commit,
I
need
to
add
the
force
tag
just
because
I'm
rewriting
over
something.
So
if
I
refresh
the
mr
that
I
have
open
on
my
left
hand
side,
you
should
see
okay.
So
then
I
rebased
and
then
so
then
I
did
that
all
right.
So
we
can
wait
for
the
pipeline
to
work,
but
I'm
just
trusting
that
this
is
not
going
to
break.
A
Sweet
all
right
so
publish
is
working.
So
then
what
I'm
going
to
do
now
is.
Oh,
I
got
the
email
that
npm
has
published
so
then
I'm
going
to
then
go
to
about
gitlab
and
I'm
going
to
look
for
the
slippers
ui
package
and
I'm
going
to
update
this
to
8.0
alpha.
A
A
A
You
should
get
sweet
and
just
to
double
check
that
this
is
working,
I'm
gonna
go
to
localhost
and
yeah.
The
localhost
is
working
and
then
just
to
show
you
that
this
has
been
updated.
I'm
going
to
refresh
really
quickly
published
a
minute
ago,
because
I
did
that
so
the
next
thing
I'm
going
to
do
is
I'm
going
to
try
to
convert
this
view
component
over
to
hamel.
A
We
do
have
an
intention
of
wanting
to
have
it
so
that
we
just
call
this
view
component,
just
like
slp
footer
and
then
like
have
middleman,
be
able
or
have
our
www
about
site,
be
able
to
interpret
that
as
a
view
thing
that
gets
built
out
with
our
build
process.
That
is
not
the
case.
How
we
do
it
right
now,
so
what
I'll
show
you
is
kind
of
the
way
that
I've
done
it
so
far,
people
have
different
opinions.
I
think
tyler.
A
A
I'm
posting
facing
this
into
like
a
html
to
handle
converter.
I'm
gonna
hit,
convert
I'm
literally
just
gonna
copy
paste
this
onto
footer.haml
and
we'll
see
how
this
goes.
Urls
need
to
work,
they're,
not
routing
the
right
way.
Laura
did
a
great
job
of
calling
that
out
for
me,
but
just
right
now
for
demo
demonstration
purposes.
This
is
like
what's
happening
all
right,
so
I
have
an
include
in
the
navigation
under
navigation
folder.
So
I
want
to
demo
this
on
the
home
page
just
to
see
if
this
would
work.
A
I
have
no
idea
if
this
would
work,
but
this
is
what
this
is.
This
is
about
right,
just
living
on
the
edge
and
seeing
if
things
work
out
all
right.
So
if
I
hit
save
here,
what
would
happen?
What
should
happen
is
that
this
new
slippers
situation
should
update
in
accordance
to
the
footer
that
I
created
over
here.
A
A
I'm
actually
not
sure
what's
happening.
Let
me
make
sure
that
this
include
is
actually
being
used
in
the
hoof
in
the
home
page.
So
if
I
go
to.
A
A
Oh
well,
they
it's
here,
it's
not
working,
but
it's
here.
This
is
kind
of
like
the
process
of
working
with
slippers
trying
to
get
it
to
update.
A
A
A
Oh,
you
know
what
it
is,
I'm
so
stupid.
I
need
to
include
slippers
into
the
homepage.
That
would
probably
probably
help.
A
In
the
page,
that's
a
oopsy,
you
know,
but
this
is
a
work
in
progress.
You
know
it's
workflows,
we're
working
on
it
all
right,
so
I
believe
that
should
just
work
now
or
be
much
closer
and
there
might
be
conflicting
styles.
But
let's
see
a
lot
of
this
is
just
like
waiting.
A
What
happened
here,
oh
might
be
slippers
conflicting
with
base
2020.
It
might
be
actually
yeah
so
that
we
do
have
conflicts
with
some
things
on
the
home
page.
But
wait
I
mean
this
is
working.
Okay,
it's
not
working
great,
but
it's
working
all
right
enough,
although
I
do
find
it
weird
that
some
of
this
is
being
canceled
done.
I
have
a
feeling
it
has
to
do
with
some
defaults
that
we
have
you
see
yeah.
A
It
might
just
be
some
classes
that
are
specifically
targeting
home
2020
that
we
have
to
work
on,
but
the
plan
here
I
kind
of
just
wanted
to
show
this
right
now.
We,
the
homepage,
has
a
ton
of
conflicting
styles
like
just
like
this
big
white
area
underneath,
but
the
plan
is
that
if
we
make
a
layout-
and
I
was
gonna-
do
this
for
the
demo-
but
I
just
figured
it
would
be
more
complicated
for
me
to
set
up
is
to
just
like
set
up
a
partial
or
set
up
a
layout.
A
Sorry
that
includes
partials
that
only
use
slippers
and
the
reason
why
that's
like
super
great
is
that
we
won't
have
like
this
conflict
of
styles.
Like
if
we
pull
something
from
this
over
here,
if
the
layout
is
completely
like
clean
of
all
styles,
then
in
theory
like
this
should
just
all
translate
over
this
is
all
I
have
for
us
today.
Laura
asked
me
to
do
something
like
this,
and
I
thought
this
would
be
a
good
use
of
our
time
and
I'll
see
you
all
at
the
next
one.