►
From YouTube: Search, Nav, Support Iteration Release
Description
Iteration: Jan 30, 2023 - Feb 12, 2023
A
So
hello,
everyone-
this
is
the
search,
nav
and
support
group
we'll
be
looking
at
the
work
done
in
the
iteration
from
January,
the
the
30th
to
February
February,
the
12th
I'm
gonna
share
I'm
gonna
start
first
and
I'm
gonna
share
my
screen.
This
iteration
I
did
a
small
drop
down
for
filtering
at
the
resources
page
by
language,
so
this
page
will
be
redone
in
the
next
app.
The
next
iteration.
So
we'll
be
doing
this
again
in
the
next
app,
but
right
now
we
could.
A
We
can
do
that
in
production
and
I
also
worked
adding
a
module
built
by
the
knock,
stop
also
for
component
cache
for
the
get
started.
Pages
I
also
did
a
small
fix
in
typography
for
the
analyst
page
and
did
another
round
of
image
Cleanup
in
our
nox,
app
the
buyer,
experience
repo
and
there's
some
discussion
going
for
automating
the
the
check
for
images
that
are
in
in
the
in
the
Knox
in
the
next
report.
A
Sorry
I'm
going
to
share
yeah,
sorry
and
yeah
that
will
be
for
the
image
cleanup,
we'll
be
doing
some
automation
there
and
try
to
keep
the
images
cleaned
up
and
also
maybe
do
a
static
server
for
the
static
images
in
a
bucket
and
yeah.
That
was
for
me
for
this
iteration
and
I'm,
headed
over
to
Laura
I.
Think
yeah.
B
B
B
Repo
private
security
had
done
that,
while
they
do
some
cleanup
so
making
our
repo
public
again
fix
that
problem
and
then
the
next
day,
the
residual
errors,
the
404s
imply
that
that
the
file
doesn't
exist,
and
so
it
wasn't
being
uploaded
where
it
was
supposed
to
be,
and
that
was
because
all
of
our
Runners
that
do
the
jobs,
the
pipeline
jobs
were
uploading.
Our
file
to
still
uploading
still,
they
were
still
private
Runners
and
they
were
still
uploading,
our
artifact
to
a
private
location.
B
So
it
didn't
exist
where
we
were
looking
for
it.
So
we
deleted
all
of
our
shared
runners
so
that
we
now
use
regular
Runners
for
all
of
our
jobs
to
run,
and
that
file
goes
where
it's
supposed
to
go,
so
that
www
can
grab
it
and
doesn't
cause
all
of
the
Mrs
to
fail,
which
is
great
a
little
spooky
that
we
didn't
really
know.
This
was
happening
until
all
of
the
Mrs
started.
B
Failing
so
Nathan
had
set
up
he's
been
out
for
a
couple
days
this
week,
but
prior
to
leaving
he
set
up
a
slot
Channel
that
alerts
for
any
failed
pipelines
in
www
he's
going
to
clean
that
up.
So
it
only
alerts
us
for
our
fire
experience.
Failure
the
job
that
we
care
about.
We
don't
need
to
know
every
single
fit
it's
very
loud
right
now,
so
I
wouldn't
recommend
that
anyone
joins
it,
but
it's
called
deex
alerts.
B
If
anyone
wants
to
join
in
slack
and
and
he'll
keep
tweaking
it
just
to
alert
us
of
things
that
kind
of
are
important
to
our
team.
So
that
came
up
for
a
couple
of
days.
This
iteration
I
created
a
new
blonde
repo
as
well.
I
have
share
it's
pretty
layer
bones
and
about
a
million
things
open
here.
Okay,
you
I,
don't
know
if
that's
sharing,
but
if
you
can
see
it,
it's
like
a
real
slippers,
free
version
of
our
blog,
but
it
is
like
it's
grabbing
actual
posts.
B
These
are
two
random
posts.
I
added
in
and
the
problem
that
we're
running
into
now
is
that
we
are
unable
to
use
Vue
to
plugins
and
modules
in
a
view,
three
knocked
three
project
so
trying
to
figure
out
a
workaround
for
that.
But
for
now
we
have
basic
routing.
We
have
Google
fonts
loading,
which
is
kind
of
cool.
B
I.
Also
did
a
little
note,
Banner
thing
here
for
the
admins,
the
netlify
CMS
admin
page
that
just
kind
of
lets
people
know
what
happens
when
they
log
in
because
people
were
logging
in
and
creating
Mrs
and
weren't
sure
kind
of
what
that
process
looked
like
and
what
was
happening
and
why
they
had
access
to
it
so
that
Banner
exists
now
and
I
think
that's
more
or
less
it.
B
Oh
I
created
a
new
plan
for
some
personalization
ideas,
so
that's
an
issue
that
I'll
link
out
to
our
team
for
feedback
for
how
we
can
figure
out,
if
someone's
coming
from
SMB
or
Enterprise
and
maybe
adjust
the
navigation
appearance
based
on
on
what
audience
we're
we're
serving
but
yeah.
Okay,
that's
it
for
me
next
is
carries
out
so
miracle.
C
I
also
focused
on
our
two
GTM
One
Trust
blockers
and
again
I'm
happy
to
announce
that
it
looks
like
we
have
a
solution.
That's
working,
that's
finally
removed
the
one
trust
blocker,
at
least
in
the
buyer,
experience
repo.
It
I
think
the
only
thing
worth
exciting
now
is
whether
or
not
we
want
to
add.
C
One
trust
gave
us
like
one
trust
stocks
suggests
that
you
add
a
class
to
GTM
to
prevent
blocking
from
happening
again
and
right
now
we
have
blocking
not
happening
at
all
without
those
classes,
so
we're
trying
to
decide
if
we're
going
to
implement
those
classes
just
to
thought
our
eyes
and
cross
our
T's
and
that's
it
for
me.
I
will
pass
it
off
to
John.
D
Thank
you,
hello
team
for
this
iteration
I
worked
first
on
the
changelog
pile
Nathan.
Helped
me
doing
this.
You
can
do
the
pipeline
to
run
the
changelog.
I
will
show
it
to
you
right
now,
Heroes.
This
is
the
result.
We
have
this
file.
That
is
our
change
log
file.
We
need
to
as
a
progress
in
our
progress
to
improve
some
things,
but
this
is
finally
a
change
log
that
is
automated,
that
it
would
be
run
at
the
end
of
every
iteration.
D
This
is
our
first
version
we
had
in
our
package.json
file,
div
version
1.0.0,
so
we
increase
it
to
1.1.0
depending
on
on
what
we
did.
So
it
has
icons.
We
have
refactors.
We
have
some
styling
things.
Some
features,
some
bug
fixes
are
some
content
changes.
Each
each
of
these
items
has
the
commit
that
were
made
in
in
the
main
branch
and
also
which
issue
it
closed.
So
it's
it's
pretty
cool,
also
it
created
attack.
So
we
have
two
tags
right
now.
D
So
an
initial
version
that
I
created
before
the
first
automated
run
and
the
version
1.1.0.
That
is
the
current
version
that
we
have
so
hopefully,
tomorrow
it
is
going
to
run
again
and
it
will
increase
to
version
1.0,
1.1.1
or
1.2.0,
depending
on
on
what
content
we
added
to
to
the
to
the
main
branch
or
to
the
to
the
to
the
budget.
D
It
will
be
changing
the
the
next
iteration
because
we
need
to
add
some
other
starters,
but
right
now
this
is
our
current
page
and
last
but
not
least,
my
favorite
one.
We
have
the
search
as
a
new
page.
So
right
now
we
can
do
some
cool
search
like
this
in
the
with
URLs.
So
we
have,
we
can
use
Query
patterns.
So,
let's
type
continuous.
D
And
it
does
the
search
results
for
continuous
that
it
was
our
search
test
by
default.
We
have
sort
by
that
is
suggested
source
that
is
marketing,
sorry
survive
here
and
Source
here
and
the
page
for
the
pagination
that
is
below
here
and
if
we
change
anything
in
our
filters
so,
for
example,
the
survive
most
popular.
It
will
be
changed
here
in
the
query
params
also
here.
The
source
here
is
the
handbook
and
also
the
page.
D
E
Is
so
cool,
I
kind
of
built
on
that
we
removed
blog
posts
and
anything
that
starts
with
handbook
from
that
Global
about
search?
So
if
you
go
and
search
for
something
those
won't
show
up-
and
it
really
just
like
focuses
it
down
to
our
marketing
site,
so
that's
completed
in
Swift
type
and
I
did
some
investigation
in
implementing
the
next
I
18n
module
for
localizations,
just
kind
of
Spun
up
an
RM
Mr,
just
kind
of
like
figuring
out?