►
From YouTube: Search, Nav, Support Iteration Release
Description
Nov 7, 2022 - Nov 20, 2022
https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/boards/4305230?label_name[]=dex-group%3A%3Asearch-nav-support&iteration_id=76462
A
A
B
A
Mascot
or
mascots
there
are,
they
are
at
party
okay,
so
I'm
going
to
start
with,
with
myself
in
this
direction.
I
I
worked
on
changing
navigation
from
using
floating
view,
that
is
a
library
to
show
pop
hours
and
drop
downs
and
make
it
from
scratch.
So
I
did
it
from
scratch,
and
now
we
have
all
the
links
in
the
Dom.
So
this
is
an
an
improvement
for
the
SEO
team.
A
A
A
Okay,
sorry
for
this
okay,
so
I'm
I
have
right
now
this
documentation,
because
I
do
not
have
a
practical
example
right
now,
but
we
are
using
semantic
release
with
70
release.
We
can
update
the
version
of
the
project,
the
npm
version.
Also
we
can
create
a
releases
or
or
tags
in
this
case
and
when
we
create
a
new
release
or
when
we
create
a
new
version.
A
This
tag
will
be
created
in
our
project
and
whenever
we
need
to
do
a
roll
back
to
a
certain
version,
we
we
will
be
able
to
to
to
do
that
and
also
we
can
create
a
change
log
file.
So
right
now
we
have
this
configuration
for
for
the
symmetric
release,
so
we
have
a
commit
analyzer
release,
null
generation
generator
and
some
modules
for
npm
and
git.
A
The
most
important
thing
is
is
that
we
need
to
use
conventional
commits.
You
can
see
it
here
in
this
documentation.
The
combination
commits
will
allow
us
to
create
automatically
the
change
look.
So
it
depends
on
us
for
the
chain
loop
to
be
really
well
done,
I'm
going
to
talk
about
this
further,
but
this
is
right
now
what
we
have
and
it's
pretty
cool,
because
it
is
needed
in
any
project.
C
C
So
we've
had
an
error
in
production
for
our
font,
not
loading
properly
in
404.
So
I
got
to
fix
our
content,
secure
policy
in
next
config
to
allow
for
our
font
to
come
from
the
Google
fonts
website.
So
that's
finally,
fixed
I
got
to
add
a
type
on
the
button
component
in
slippers,
which
was
failing
some
hydration
errors,
which
leads
me
to
I,
got
to
add
the
hydration
Checker
into
our
repository,
so
that
hasn't
been
merged
yet,
but
when
it.
A
C
I'll
make
sure
to
let
the
team
know
as
you're
running
your
development
server
you're
going
to
see
a
lot
of
Errors.
It
doesn't
error
out.
It
doesn't
stop
your
server,
but
it's
just
like
every
page
has
a
ton
of
like
warnings
so
I'm
trying
to
make
those
less
verbose.
But
it's
already
been
really
helpful,
showing
that
I
have
you
know
a
button
that
has
as
a
div
inside
of
it
we're
not
supposed
to
do
that
and
that
could
cause
hydration
bailout.
C
So
that's
really
cool
I'm
waiting
for
Nathan
to
review
that
when
he's
back
as
well
and
then
another
big
piece
that
I
was
working
on
was
removing
the
slippers
code
from
our
navigation,
because
it's
such
a
huge
package,
so
I
have
two
solutions
to
that.
One
of
those
two
different
Mrs
again
we'll
kind
of
see
which
one
fits
our
team
better.
But
one
is
just
adding
the
navigation,
the
slippers
package
to
navigation
as
a
peer
dependency.
C
So
it
looks
for
the
slippers
package
over
and
buyer
experience
as
a
peer
dependency
instead
of
as
a
dependency.
But
then
we
also
have
to
add
it
as
a
Dev
dependency.
And
then
we
kind
of
worry
about
slippers
package
versions
getting
out
of
control
out
of
sync.
The
other
option
is
to
remove
slippers
entirely
and
just
write
our
own
CSS.
That
looks
like
slippers,
so
I
have
an
MR
open
for
that
as
well.
C
It
was
like
150
lines
of
CSS,
like
it's
pretty
lightweight
to
just
have
our
own
CSS,
but
again
that
could
stay
out
of
sync
with
slippers
changes
that
are
made,
that
we
want
in
the
navigation.
So
there's
pros
and
cons
to
both
so
we'll
discuss
with
the
team
how
that'll
work
and
then
I
had
a
small
request
to
change
some.
Some
stats
on
the
company
page
so
I
believe
that's
in
review
by
our
stakeholders
and
I.
Think
that's
just
about
it.
For
me,
next
up
is
Miguel.
D
Thank
you,
Laura
yeah,
so
this
iteration,
maybe
I,
was
really
concerned
about
a
lot
of
changes
to
the
about
the
partners.
Page.
Sorry
so
I'm
going
to
show
you
here
we
did
some
some
style
changes
copy
changes.
We
added
a
button
to
find
a
partner
here.
We
also
made
these
cards
clickable,
so
they
can
go
to
the
other
pages
of
Partners,
and
we
also
created
this
new
partner,
Solutions
component,
that
also
links
to
like
nested
and
bonus
pages
and
yeah.
D
D
D
E
E
It
basically
uses
most
of
what
all
of
our
other
Solutions
page
that
uses
the
template
that
all
of
our
other
Solutions
Pages
have,
but
like
it's
just
a
little
bit
different
with
that
content
other
than
that
I
reviewed,
the
trust,
Center
review,
the
partners
pages
and
the
analyst
pages.
So
that's
it
I'm
going
to
hand
off
to
miracle.
B
Hi
everybody
this
iteration
I
worked
on
in
vc2
of
the
analyst
page.
It's
in
the
final
stages
of
review.
I
just
got
some
feedback
from
Carrie
this
morning
that
I'll
be
working
on
after
this
meeting,
and
the
other
thing
I
worked
on
was
the
bug
that
we're
having
between
one
trust
and
GTM.
It
looks
like
one
trust
is
blocking
GTM
on
some
of
our
pages
and
I
had
to
push
that
to
next
iteration.
Just
because
that
bug
is
bigger
than
I
expected,
and
it's
being
mean
to
me
and
that
was
it
for
migration.
F
And
take
it
away,
we
finished
the
first
part
of
our
talent
assessments.
Those
are
due,
so
that's
all
done
now,
it's
in
calibration
mode
and
then
starting
to
plan
the
globalization
work
for
the
quarter
since
we'll
be
launching
fully
localized
versions
of
our
marketing
site
in
French,
German
and
Japanese
by
the
end
of
January.
So
we're
gonna
get
moving
on
that
and
lots
of
good
Q
for
planning.