►
From YouTube: 2021-06-03 Inbound Marketing BiWeekly Recap
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everyone:
this
is
the
inbound
marketing
team,
our
bi-weekly
recap
and
demo,
it's
june
3rd
we're
going
to
kick
it
off
with
brie
for
moments
of
insight.
B
Hi,
so
this
is
moments
of
insight
where
you
can
share
something.
You
were
surprised
to
learn
this
week,
which
might
benefit
others,
and
I
think
jeff
is
first
on
this
list.
D
Overflow,
I
just
snuck
one
in
there
also,
so
the
vaccine
rollout,
where
I
am,
is
like
just
objectively,
not
good.
So
I
had
a
vaccine
appointment
that
I
like
scoured
the
website
for
for
the
end
of
june,
and
then
I
wrote
a
script
that
would
just
constantly
like
refresh
the
calendar
that
was
on
the
page
and
find
if
there
was
an
available
appointment
and
then
like
pseudo,
like
click
into
that
appointment
and
then
check
if
it
was
sooner
or
later
than
my
current
appointment
and
then
book
it
for
me.
D
So
like
hacker
man,
not
really
ethical,
but
like
gotta,
got
an
appointment
for
next
week.
So
it's
okay.
A
Awesome
so
moving
on
into
metrics.
A
Okay,
so
there's
a
few
we
weren't
able
to
get
just
in
the
the
short
notice
here,
but
we're
35.16
percent
through
the
quarter
as
of
yesterday
and
we're
right
here
at
22.9
million
page
views
is
our
target
so
we're
at
8.1.
As
of
yesterday.
That's
35.4
percent
of
attainment,
we're
exactly
sure
how
to
calculate
pace
yet,
but
we're
we're
sorting
this
out
since
we've
just
switched
what
we
were
reporting
on
same
with
inquiries
where
things
are
changing.
So
there's
a
lot
of
changes
in
dashboards
in
scissors.
A
C
First,
if
you're
gonna
share
get
off
mute
second
share
your
screen.
If
you
have
something,
that's
you
like
to
share
with
people
and
we'll
start
with
you
tina.
G
Okay,
I'm
first,
I'm
gonna
share
my
screen
and
go
share.
So
I
just
oh,
I'm
gonna
move
there.
Okay,
you
can
see
my
screen
now.
G
Okay,
so
I
just
wanted
to
show
some
of
the
work
we've
been
doing
for
the
solutions.
Cms
template.
So
much
like
the
topic
page
and
the
events
template
we're,
creating
a
set
of
blocks
that
will
live
in
like
one
long
mother
template
so
that
solutions
team
members
can
self-serve
updates.
You
can
see
a
figma
file
right
great,
so
I'll
just
run
everyone
through
this
real
quick
and
then
you
can
kind
of
review
it
at
your
own
time
if
you
wish
to
so.
G
These
are
the
blocks
that
we've
selected
that
will
live
in
the
mother
templates,
so
the
solutions
pages
have
about
32
pages.
I
believe
so.
We
kind
of
went
through
every
one
of
those
and
selected
blocks
that
could
work
for
all
of
those
content
types
and
then,
like
the
topics
and
events,
page
they'll
live
in
one
long
template,
so
please
don't
use
all
of
them
at
the
same
time,
because
that
would
be
a
ux
nightmare.
G
G
So
we
kind
of
use
this
as
the
first
use
case
for
the
template,
as
you
can
see,
like
you'll
recognize
a
lot
of
these
components,
we're
getting
to
a
point
now
where
we
can
keep
reusing
these
blocks
to
create
new
pages,
and
then
these
two
are
just
two
other
content
types
that
live
in
the
solution
pages.
Some
of
them
have
gated
content,
and
some
of
them
have
partner
pages,
so
just
to
show
how
other
pages
can
can
be
ported
into
the
new
template.
If
that
makes
sense.
G
So
that's
all
the
time
I
want
to
take
on
this
but
feel
free
to
ask
me
questions
via
slack
or
in
the
issue
that
I
have
linked.
C
H
There
we
go
so
reminds
me
pretty
quick.
We
are
building
this
little
banner,
which
is
going
to
direct
people
to
a
free
trial,
and
the
idea
is
that
it's
a
reason.
Excuse
me
a
reusable
component,
so
we
got
one
for
desktop
here
and
then
like
a
slightly
condensed
version
for
mobile
and
the
idea
is
we
have
15
pages
we're
targeting
we're
planning
to
put
it
on
all
15
pages,
so
that
no
matter
where
you
are
and
kind
of
the
journey
on
the
website,
we'll
direct
you
to
a
free
trial.
H
So
it's
kind
of
just
like
a
slipperified
version
of
one
that
already
exists
with
some
slightly
updated
content
copy
rather-
and
I
think
niles
next.
F
Thanks
so
share
my.
E
Screen
so
this
is
just
something
where
well,
it's
something
we've
been
continually
working
on,
but
it's
just
that
to
give
you
an
insight
into
some
of
it
is:
is
the
internal
link
optimization?
E
So
the
reason
for
this
is
to,
I
suppose,
link
related
content
together
and
to
create
cluster
formats,
to
try
and
increase
topical
expertise
and
pass
link
equity
to
boost
specific
pages
and
we're
getting
really
good
impact
off
it,
but
just
to
visualize
some
of
the
audit
data
and
how
it
works
is
we
can
crawl
and
scrape
all
specific
pages,
for
example.
This
is
all
looking
at
the
blog
folder.
E
We
identify
the
specific
terms
for
the
primary
pages
you
want
to
link
to
like
application,
security,
continuous
delivery,
etc,
and
it
pulls
all
the
data
for
the
pages
based
on
the.
If
the
pages
have
that
terminology
in
it
and
how
many
times
it's
mentioned
so
obviously
the
more
times
it's
mentioned,
the
more
relevant
that
copy
is
to
the
page
we're
linking
to,
and
also
we
have
a
url
rank
script.
E
Then
that
tells
us
the
the
link
value,
the
equity
that
page
that's
built
up
so
the
higher
that
is
the
more
value
the
that
page
has
and
we
can
pass
some
of
the
link
up
pretty
toughly
to
the
related
page.
So
once
we
identify
the
pages
and
dimensions
we
can
go
in
then
manually
into
the
pages.
I
So
I
have
a
couple
things
that
I'm
going
to
show,
and
the
first
thing
is
our
authorization
process
for
netlify
has
changed
and
what's
really
cool
about.
This
is
when
we
first
fired
it
up
we're
using
client-side
implicit
grant
and
then
turns
out
that
is
going
to
be
super
depreciated
and
the
only
other
way
was
to
use
authorization
code
flow.
But
since
then-
and
since
we've
been
monitoring,
it
look,
what
else
showed
up
this
new
method?
I
And
it
was
super
easy,
so
it
just
shows
like
the
power
of
open
source
and
how
quickly
this
software
is
iterating.
So
that
was
a
really
big,
surprise
and
easy.
The
second
thing
is:
we
have
implemented
thotbot's,
middleman,
inline,
svg
extension
and
what's
really
cool
about
this
is
instead
of
putting
all
this
svg
code
in
our
template,
which
is
really
going
to
bulk
it
up
and
we're
going
to
have
duplicate,
svg
scattered
throughout
the
website,
not
efficient.
I
Now
we
can
just
put
this
one
little
cool
line
and
point
to
here
use
this
svg
and
then
it
prints
out
all
of
that
code,
and
there
is,
we
can
add,
a
css
class
and
colors
and
stuff
into
here
and
we'll
automatically
apply
it
super
cool
extension.
That's
so.
F
I
And
the
last
thing
tyler
he's
out
on
pto,
but
he
completed
step.
Four
of
our
event
template
build,
and
that
is
this,
mr
and
we
now
have
this
template
include
is
in
this
path
right
here
and
you
can
see
all
the
changes
that
were
made
with
this.
Mr,
and
essentially
it
was
putting
all
the
components
that
we
had
built
previously
in
step,
three
arranging
them,
getting
them
the
right
order,
and
now
this
template
is
available
and
so
now
we're
on
to
step
five
and
we're
attaching
it
to
netlify.
A
I
I
I
think
I
saw
something
in
gitlab,
so
it's
deprecating
in
4.14.4
the
oauth
spec.
It
was
deprecating
as
well,
so
it's
kind
of
been
on
our
right
radar
and
we
really
wanted
to
get
it
started
before
14.0.
A
E
F
E
I
think
we're
out
to
shout
outs,
so
this
is
just
the
element
of
the
chat
where
you
can
give
thanks
either
someone
in
the
team
or
the
wider
gitlab
team
that
has
either
helped
you
in
a
task
or
just
made
your
life
a
little
bit
easier
in
the
past
few
weeks.
So
I'll
possibly
be
posting
the
shout
out
in
the
video,
and
so
I
think
the
first
one
up
there
is
me.
E
So
what
I
want
to
do
is
give
a
shout
out
to
mohammed
kobesie
he's
on
the
it
operations
team
and
he
was
generous
enough
to
jump
on
the
call
with
me
today
and
sort
out
a
lot
of
problems
that
got
us
over
a
couple
of
hurdles.
So
just
a
quick
shout
out
to
him
and
a
big
thanks
and
then
it's
on
to
michael.
A
Thanks
now,
jeff
shout
out
to
you:
it's
been
a
very
tricky
month
since
you
joined
your
attitude
and
your
leadership
has
been
awesome.
I
really
appreciate
having
you
as
a
teammate.
It
could
have
been
a
lot
more
rocky
than
it
has
been,
so
I
just
thanks
for
being
you.
A
I
also
have
a
shout
out
for
nathan
he's
not
here
right
now,
but
he
really
helped
us
out.
At
the
beginning
of
the
week
we
had
a.
We
have
a
bi-weekly
meeting
with
sid
to
review
some
pricing,
page
changes
and
there's
just
a
couple
things
that
sid
wanted
to
see.
A
He
got
them
done
like
that
fast,
which
is
amazing
and
then
also
he's
on
vacation,
but
shout
out
to
brandon
continuing
to
do
such
a
great
job,
coordinating
the
digital
experience,
team,
sprints
and
then
as
well
playing
a
lead
role
with
jess
in
that
pricing
page
work,
it's
it's
a
big
ask.
Things
are
not
expected
quickly,
but
they're
kind
of
implied
to
be
done
quickly,
so
we're
able
to
do
it
and
it's
going
really
well.
So
thank
you
over
to
you,
jeff.
C
Shout
out
to
niall
we
talked
about
this
a
little
bit.
We've
had
this
problem
with
google
analytics
this
week
and
niall
has
been
working
around
the
clock
to
get
things
back
on
track
and,
as
I
said,
as
I'm
moving
from
yellow
to
green,
I'm
cautiously
optimistic,
but
great
job
now
of
cat
hurting
people
and
getting
people
to
help
us.
C
So
that's
really
great
and
then
another
and
a
shout
out
to
brock
erica
has
been
out
the
past
two
weeks
and
brock's
been
carrying
the
load
and
there
is
a
lot
of
load
in
the
video
land
and.
C
And
brock's
working
closely
with
the
legal
team
this
week
and
it
might
be
shocking,
but
the
legal
team
is
very
specific,
with
their
feedback,
specific
and
prolific
and
but
brock's
been
great
work
with
him.
So
thanks
nile
thanks
brock.
F
C
J
Okay,
I
just
wanted
to
say
a
big
thank
you
to
the
entire
content
team
for
continuing
to
step
in
and
help
with
the
blog
not
only
like
now,
while
I'm
here,
but
also
while
I'm
out,
and
I
just
really
appreciate
it.
I
know
that
it's
a
lot
of
work
and
I
just
wanted
to
give
my
sincere
appreciation
to
this
team
for
helping
me.
Thank
you.
I
Let's
give
a
big
shout
out
to
nathan
and
laura
for
jumping
on
a
caching
issue
with
our
slippers
package
on
production.
It
was,
it
was
a
sneaky
one
and
they
figured
it
out
and
got
it.
A
Fixed,
I
also
wanted
to
call
out
the
this
isn't
written.
I
totally
forgot
about
this.
I
saw
it
last
night
I'll
share
something,
so
I'm
a
dork,
so
I
was
reading
about
how
the
knicks
got
out
of
the
playoffs
yesterday,
but
guess
what
I
saw
here
I
saw
tktk
and
I
knew
what
it
was
to
come
to
come
and
I
was
like.
Oh
my
god,
I
learned
something
and
how
did
this
you
know
espn
makes
mistakes
too,
so
we're
allowed
to
make
mistakes.