►
Description
https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/boards/4305230?label_name[]=dex-group%3A%3Asearch-nav-support&iteration_id=73693
A
A
A
Oh
where's,
my
screen,
there
I
also
swapped
out
the
pricing
page
header
during
the
navigation
release,
so
that
it
has
the
full
header
now,
instead
of
the
minimized
header,
and
we
finally
got
the
company
page
merged,
which
was
good
after
a
bit
of
back
and
forth.
That's
it
for
me,
and
next
is
John.
Wait.
D
B
D
Great,
so
we
changed
our
nap
to
some
hover
drop
downs.
Pretty
cool
cover,
drop
downs
that
you
can
see
right
here,
more
minimalistic
than
before.
We
also
changed
the
nap
from
two
rows
to
only
one
row,
so
we
have
more
space
for
the
page
and
we
also
have
the
login
right
here.
We
have
the
search
as
always,
but
in
in
this
new
row
and
for
the
mobile
size.
Let's
see
we.
D
D
The
automation
of
the
API
from
GitHub
to
create
the
change
look
automatically.
The
next
step
is
to
create
automatically
the
attacks
with
a
semantic
version
and
also
how
to
automatically
bump
the
version
from
bios
experience.
So
after
that,
we
will
have
a
good,
automated
change,
lock
releases,
so
it
would
be
pretty
cool,
that's
it
for
me.
Next
one
is:
let
me
see
Miguel.
E
Thank
you,
John
yeah,
the
navigation
is
great,
looks
very
good
for
this.
Iteration
I
did
a
small
change
to
the
footer.
We
introduced
a
new,
a
new
column
and
we
arrange
all
the
links,
so
it
will
be
aligned
with
the
header
that
was
merged.
Also,
and
it's
also
live
I
did
a
work
with
the
gitlab
manager.
You
know
it's,
it's
a
glm
tag.
We
we
attached
to
the
free
trial
button.
E
I
did
put
it
a
dynamic
way,
so
we
can
know
in
which
page
the
user
was
I.
Also
did
a
small
change
in
copy
in
the
in
the
partners
page
and
we've
also
been
making
sure
that
the
navigation
has
all
the
tracking
for
the
Google
tag.
Manager
that
that
work
was
also
done
was
also
done,
and,
finally,
I
added
a
a
section
in
the
navigation
release.
E
F
B
This
iteration,
thanks
to
Carrie's
like
awesome
designs,
I,
was
able
to
release
the
analyst
page
and
then
the
rest
of
the
iteration
I
spent
in
the
GDK
I
was
working
on
updating
our
visible
scripts
and
right
now
that
final
changes
in
reviews.
So
hopefully
it
doesn't
take
too
long
to
get
through
the
process,
and
that
was
it
for
me.
This
iteration
I'll
pass
it
to
Lauren.
C
Hello
such
a
good
iteration
for
the
team
so
proud,
and
so
what
I
did
was
we
shipped
the
POC
for
our
localization,
our
smart
Lane
localization,
which
you
know
it
was
kind
of
a
whole
quarters
of
work.
So
I'm
gonna
actually
share
a
little
bit
of
this
video
that
I
recorded
I'm
just
gonna
hop
over
here.
This
is
the
issue
we're
using
to
gain
approval
of
it,
and
here
are
the
pages
that
we
did
French
Japanese
German,
it's
the
home
page.
C
Why
get
lab
and
the
pricing
page
we'll
just
go
ahead
and
click
into
here.
This
is
our
home
page
or
French
super
cool
there,
it
is,
could
go
over
here,
Japanese
there.
It
is,
and
then
German
wow,
so
wow
so
cool
so
that
got
launched
in
our
stakeholders
were
able
to
review
it.
We
are
going
through
with
the
gdn,
so
we're
signing
that
contract
next
quarter,
we'll
be
implementing
it
site-wide.
C
So
get
ready
for
that
to
happen
because
it's
happening
and
it
did
cause
some
pretty
big
SEO
errors,
because
there
were
three
versions
of
our
site:
translate
it
by
Google.
So
there's
the
French,
the
German
and
the
Japanese
version.
So
there's
like
four
search
engine
results
for
each
search.
Query,
not
good
gotta
fix
that.
So
there
is
some
some
stuff
we
needed
to
do.
There
I
had
to
purge
our
Swift
type.
Cash
set.
Some
rules
I
have
to
remember
to
take
those
off
and
then
the
process
changes
me
Phil's.
C
A
Sure
yeah,
so
we
released
navigation
and,
during
those
releases,
I
think
most
of
the
team
understands
that
we
have
the
navigation
package
that
then
gets
brought
into
two
repositories,
our
repository
and
our
fire
experience
repository.
Unfortunately,
those
are
two
different
environments,
so
in
both
repos
we
found
some
conflicting
styles
that
were
overriding
our
navigation
Styles,
which
is
kind
of
a
pain,
so
to
make
sure
that
the
navigation
Styles
take
precedent
over
anything.
That's
coming
up
in
buyer
experience,
we
had
to
add
some
important
tags,
which
isn't
great.
A
There
was
an
issue
with
some
hydration
issues
on
our
buyer
experience.
Repo
hydration
issues
are
kind
of
a
complex
view,
ISM,
where,
if
you
have
invalid
HTML
markup
HTML
markup,
that's
redundant.
If
you
have
invalid
HTML
or
if
you
have
anything
like
be,
if
instead
of
V
show
or
some
things,
that
view
doesn't
like
you're
going
to
get
errors,
but
those
errors
only
show
up,
sometimes,
which
is
a
little
bit
annoying.
A
A
So
I
have
a
package
that
I
found
that
kind
of
combs
through
all
of
your
HTML
and
looks
for
those
kind
of
gotchas
that
I'll
probably
add
to
the
navigation
repo
and
probably
the
buyer
experience
just
to
catch
those
before
we
before
we
release,
and
then
the
www
is
just.
There
are
so
many
CSS
CSS
on
CSS
on
CSS
that,
like
it's
really
a
pain
to
make
the
navigation
be
the
most
important
style,
because
everything
has
an
important
tag
in
www
so
coming
through.
A
That
was
a
bit
of
a
problem,
but
we
expect
that
we
expect
some
kind
of
some
headaches
when
using
the
repo,
so
that
was
understandable,
but
yeah
lots
of
improvements
we're
going
to
improve
the
tabbing
through
each
of
the
items
in
the
navigation,
because
the
tabbing
isn't
great
right.
Now
we're
using
an
external
library
that
kind
of
blocks
us
a
little
bit
from
from
tabbing
through
items.
But
we've
got
some
improvements
to
make
and
that'll
come
in.
The
next
version.