►
From YouTube: Digital Experience Navigation Repo Walkthrough
Description
Navigation repo: https://gitlab.com/gitlab-com/marketing/digital-experience/navigation
A
A
So
I'll
share
my
screen
here
this
one
all
right,
so,
first
of
all
I'll
go
and
show
what
this
looks
like
if
I
go
to
about
doggylab.com
the
navigation
repo
contains
all
of
this
navigation
component,
as
well
as
the
footer
at
the
bottom,
and
we
are
currently
in
flux
right
now.
Our
website
is
in
two
different
pieces.
This
is
being
served
by
our
buyer
experience,
repo,
which
is
a
nux
site
using
vue,
and
then
there
are
pages
that
are
still
being
served
by
our
old
www.
A
Repo
events
is
still
one
of
these
old
pages,
so
you'll
see
the
navigation
and
the
footer
look
the
same,
but
they
are
actually
being
served
by
two
different
repos
or
because
the
navigation
is
being
consumed
by
both
of
these
repos.
So
what
we're
going
to
do
is
make
a
change
to
the
navigation,
publish
that
to
npm
and
then
make
the
change
in
both
of
those
repositories,
so
they
both
reflect
that
change.
Okay,
so
let's
get
started.
I
have
a
pretty
simple
issue
here.
A
I
don't
know
what
should
I
have
a
million
tabs,
a
simple
issue
here
that
was
pointed
out
where
one
of
the
links
in
the
solutions
section
of
the
nav
doesn't
go
where
we
want
it
to
go.
So
I'm
going
to
update
that.
So
I
have
the
repo
open
here,
a
quick
breakdown
of
the
repository
structure.
It's
pretty
simple.
We
have
the
footer
here
which
our
json
contains
all
of
the
the
actual
content
of
the
file
and
then
the
footer.view
is
the
actual
component
that
maps
over
each
of
those
links
and
displays
them.
A
A
Let
me
change
that
here:
okay,
cool!
If
you
don't
have
this
navigation
repo
up
and
running
it's
pretty
simple
I'll,
go
to
the
I
have
it
saved
here,
I'm
going
to
the
readme.
The
instructions
are
pretty
pretty
basic.
You
clone
this
repo.
You
might
have
to
run
an
npm
install,
but
to
start
it
up,
you're
just
running
npm
run
serve
so
I'll.
Do
that
now,
so
I
can
see
it
locally.
A
Okay,
so
we're
ready
to
go
here,
there's
just
some
like
lorem
ipsum
kind
of
stuff,
but
what
we
care
about
was
this
one
this
one,
so
I
can
see
down
in
my
bottom
corner
that
this
is
now
going
to
continuous
software
security
assurance.
So
I
mean
this
is
going
to
lead
me
back
to
the
regular
page.
This
repo
is
not
connected
to
anything
right
now,
but
I
can
see
these
changes
here.
Awesome
great.
A
A
A
A
A
I
would
probably
take
a
screenshot
of
my
change
and
post
that
and
then
get
a
design
or
content
to
approve
whatever
my
changes
are,
but
this
is
just
a
mislead
link,
so
we'll
give
this
a
moment
to
kind
of
sort
itself
out
here,
all
right,
so
it
is
ready
to
go
in
this
case.
I
would
get
someone
to
review
this
and
approve
it.
I
know
what
I've
changed.
It's
a
very
simple
like
one-line
change,
so
I'm
gonna
go
ahead
and
merge
this
in
for
the
purposes
of
the
video
okay.
A
A
There
are
instructions
on
updating
the
mpm
package,
so
we've
done
this.
We've
made
changes
to
our
files.
So
now
I'm
on
step
two,
where
I'm
going
to
increment
the
version
in
package.json
and
do
the
actual
release.
So
I'm
going
to
switch
back
to
my
main
branch
over
here,
a
little
change
that
I
just
made
see
that
that
json
has
been
updated
and
then
I'm
going
to
go
to
my
package.json
and
the
version
here.
A
A
And
this
is
doing
the
build
it'll
just
take
a
second
and
then
after
this,
so
this
is
built
now,
which
is
great
after
this.
My
next
step
is
to
publish
npm,
I'm
going
to
run
npm
publish
and
that
should
work.
The
first
time
I
tried
to
do
this.
I
wasn't
logged
into
npm,
so
if
it
returns
a
404,
when
you
try
to
publish
then
just
go
through
the
npm
login
flow
you'll
type,
this
in
it'll
ask
for
your
email
that
you've
signed
up
with
npm
with
and
then
it'll
ask
for
your
password.
A
A
A
We
can
move
over
to
our
two
separate
repositories
that
want
to
consume
this,
so
the
buyer
experience
repo
and
the
www
and
open
up
mrs
in
each
of
these
repos.
So
I'm
going
to
go
to
www,
which
I'm
on
a
different
branch
here,
but
let
me
go
to
master
I'll.
Do
a
quick
dip,
pull
I'm
starting
with
dub
dub
dub.
Only
because
doing
mrs
takes
like
40
minutes
so
might
as
well
get
that
started
and
in
www
I'm
gonna
go
over
to
all
the
way
down.
A
A
A
A
A
A
A
A
So
this
has
these
two
merge
quests
in
it.
If
I
was
feeling
really
fancy,
I
might
link
the
original
issue.
That's
fine!
Okay!
So
both
of
these
are
running.
So
I'm
gonna
pause
the
video
here,
while
I
wait
for
these
pipelines
to
run.
But
the
short
answer
is
that
after
this
I
would
check
the
review
apps
to
make
sure
that
my
changes
have
taken
and
once
that's
the
case,
I
can
merge
in
both
mrs.
A
I
would
start
with
the
www
repo
because
it
does
take
about
40
minutes
for
it
to
become
live
and
then
I'd
move
on
to
the
buyer.
Experience
remote
because
it's
a
little
bit
quicker
but
yeah,
that's
pretty
much
our
process
at
the
moment
for
updating
navigation
or
the
footer.
Thank
you
so
much
and
I
will
stop
it.
There.