►
A
B
Thanks
so
my
main
focus
for
this
iteration.
Can
you
see
my
screen?
Do
you
see
gitlab
security
and
government
governance?
Yeah
was
the
security
and
compliance
landing
page
now
called
security
and
governance
I've
also
been
working
on
some.
You
know
iterative
ux
improvements
for
all
of
those
Solutions
child
pages,
so
I
decided
to
apply
some
of
those
changes
to
this
page
too.
B
So
I
I'd
ask
Dennis
to
get
some
Data
Insights
so
that
we
can
see
how
those
pages
are
performing,
also
asked
Carrie
to
take
a
quick
look
at
from
a
design
lens,
a
ux
lens.
So
some
of
the
changes
include
a
little
wording.
Change
here
for
part
of
me
I'm
a
little
bit
sick
for
the
what
used
to
say
the
start.
Your
free
trial,
we're
gonna,
try,
try
ultimate
for
free
for
clarity
for
the
free
trial
ctas.
Here
we've
also
separated
out
the
this
component.
B
B
What
else
changed
here?
I
think
the
other
changes,
so
the
case
studies
that
we
used
to
have
on
these
pages.
So
a
lot
of
these
Pages
have
three
case
studies:
stacked
one
on
top
of
another
are
one
of
the
lowest
performing
sections
on
these
Pages.
Nobody
clicks
on
them,
so
I
want
to
try
swapping
it
with
like
a
social
proof
section
with
a
testimonial.
I
think
it'll
be
a
lot
more
valuable
and
they
still
link
to
case
studies.
So
we'll
see
how
that
goes.
B
B
Is
this.
This
little
feature
section
here,
which
used
to
say,
take
good
lab
for
a
spin,
is
the
lowest
clicked
item
on
the
page,
and
we
understand
that
it
is
at
the
bottom,
but
the
actually
the
footer
gets
more
clicks
than
this
section,
so
people
are
just
passing
by
it.
So
I
just
wanted
to
try
a
little
wording
change
here.
Instead
of
try
get
lab
for
a
spin,
which
seems
kind
of
a
bit
vague,
we're
gonna
try
again
try
ultimate
for
free.
B
B
Another
thing
that
I
got
pulled
into
was
this
a
form
update
for
the
trial,
but
I
don't
think
we're
going
ahead
with
it,
but
this
was
released
by
me
as
a
design
and
I.
Think
that's
it
for
me,
aside
from
the
devops.
No,
what
was
it?
The
team
Ops
reviewing
the
team,
Ops
page
and
some
other
stuff,
kubecon
I,
don't
know
who's
next
and
stop
talking.
C
Yeah
I
can
go
next.
This
iteration,
you
talked
about
cute
cut
at
the
very
end.
We
released
that
page
I'll
share
my
screen
for
it,
since
it's
something
that
we
had
released.
Let
me
hit
I
have
like
so
many
monitors
now.
So
it's
like
a
challenge,
but
this
is
what
it
looks
like.
Can
you
see
it's
the
right
screen,
I
hope.
So
so
this
page
got
released.
C
Collaboration
between
us
and
some
of
the
events
folks
worked
with
also
updating
a
lot
of
their
things
because
they
were
kind
of
in
a
pickle
where
a
lot
of
their
events
team
had,
coincidentally
left
the
organization,
as
some
of
the
biggest
events
for
them
were
happening
this
year.
So
that
was
a
lot
of
fun
to
help
them.
Try
to
put
out
that
I
worked.
C
The
situation
I
still
worked
with
a
small
update
of
updating
the
CTA
for
the
Ducks
header,
so
that
was
just
a
simple
just
Bureau
of
change
knocked
that
out
and
then
the
rest
of
my
iteration
I've
been
working
on
the
data
layer.
Events
for
the
SAS
trial
flow.
That's
been
something
that's
been
open
for
a
while.
So
then
I
had
to
go
back
and
like
unscale
that
work
reopen
an
MR
and
just
like
see
where
I'm
at
I'm,
again
pretty
close
to
finishing
it.
C
E
The
featured
content
block
I
wanted
to
show
that
one,
but
to
merge
it
I
just
took
it
out
of
the
of
the
home
page,
so
it
doesn't
show
up
while
the
other
component
is
ready
and
I
also
created
a
new
issue
to
implement
the
actual
test
once
the
other
component
is
in
I
also
worked
on
solution.
Child
template
fixes
I
can
show
that
one.
E
So
it's
small
changes
to
this
solution.
Pages
issues
with
the
distance
for
the
site
nav.
It
was
too
far
away
on
large
monitors,
colors
of
the
icons
and
then
the
intersection
of
servers
of
this
component,
not
working
correctly
and
then
I
am
also
working
on
the
devops
tool,
comparison
page,
creating
this
table
for
for
the
comparison
with
the
competition
and
yeah.
That's
what
I
have
been
doing
and
I
will
pass
it
over
who
hasn't
said
anything
yet
Nathan
thanks
Mateo.
F
Is
it
just
copies
over
the
artifacts
from
the
build
and
install
stages
so
that
it's
not
doing
anything
fancy
it's
just
taking
the
artifacts
and
then
gonna
run
testing
on
that,
and
so
the
404
Checker
checks
against
the
dist,
the
disk
directory
before
it
gets
built
or
before
it
gets
published
and
inside
it
just
checks
and
it
Compares
it
to
the
local
directory
and
also
to
about
docketlab.com,
because
there's
Pages
like
handbook
and
stuff
like
that
which
they're
not
there.
They
don't
exist
in,
like
the
review
app
or
in
the
build.
F
So
there's
a
bunch
of
stuff
that
I
found
like
the
just
running
it
for
the
first
time,
there's
50
broken
links
on
just
by
experience
side.
So
some
of
them
are
just
typos
like
this
one
I
guess:
that's
not
a
page
that
exists
anymore
solution.
It
should
be
Solutions
and
so
I
went
through
and
I
fixed
them
all
and
I
closed
a
bunch
of
404
related
issues,
but
I
think
that's
the
most
of
it.
Another
small
thing
was
just
adding
proper
page
titles
to
all
the
about.getlab.com
pages,
because
I
think
for
SEO.