►
From YouTube: Digital Experience Sprint Recap 2021-02-11
Description
Sprint Release Video agenda: https://docs.google.com/document/d/1I9Th3Q-AakOkE_-pmNtEzwwMDSqYKF5Je2etGdPTovk/edit
Digital Experience handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
Inbound Marketing handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/
A
B
Yeah,
I
will,
I
don't,
have
a
ton,
that's
super
great
for
screen
sharing,
so
I
will
run
down
the
list.
First
thing
that
is
up
here
is
just
the
mvc
on
slippers
integration
into
about
doculab.com,
so
we
merged
in
a
feature
there.
Where
now
we
will
be
able
to
thanks
just
for
the
agenda,
so
we've
got
options
built
in
so
that
people
working
on
about.lab.com
can
pull
in
either
the
slippers,
css
or
the
exported
component
library
as
well,
and
render
that
all
in
line.
B
There
you
go
and
then
yeah
cool
excellent.
Thank
you
up
next,
beginning
of
the
sprint
merged
in
a
patch
to
middleman
that
speeds
up
local
template
development.
I've
done
some
like
really
rudimentary
benchmarking
on
this,
and
it's
like
anywhere
between,
like
two
and
four
times
faster
for
specific
templating
changes.
So
that's
exciting
and
should
speed
up
everyone's
workflow
a
little
bit
and
then
launched
the
child
topic
pages.
Lauren
did
a
brief
demo
in
the
marketing
meeting
and
it
was
cool
to
see
now
in
the
categories.
B
B
The
takeaway
from
that
was
that
cloudnary
was
like
a
20-minute
integration
into
netlify
cms
super
low
effort,
but
really
high
value
there,
and
I
know
that
the
broader
conversation
about
that
is
sort
of
on
pause
for
a
little
bit.
But
it's
good
to
have
that
to
refer
back
to
when
it
gets
going
again.
Other
good
things.
B
Some
agency
day
work
the
2021
survey,
an
open
graph
tag
extension,
so
it
sets
default
open
graph
images
on
all
pages.
It
basically
looks
to
see
if
that
image
has
been
specified.
If
it
hasn't,
it
falls
back
to
default
values
for
blogs
and
pages,
and
the
nice
thing
is.
We
can
extend
that
to
other
oge
tags
as
as
required,
made
a
change
in
the
pricing
terms
in
one
of
the
release
post
templates
up
next.
So
this
went
up
today.
B
There
were
some
bugs
and
breaks,
but
we
do
have
at
least
the
documentation
on
some
release
strategy
stuff
for
the
library
releases
of
slippers.
So
that's
exciting.
The
pipeline,
I
thought,
was
good
and
then
it
broke,
so
that
has
not
actually
been
released,
but
we
have
sort
of
a
first
strategy
in
place
and
then
up
next
lauren
started
the
migrating
rollup
to
webpack,
and
I
think
we've
got
it
to
where
it's
ready
to
go.
It's
still
in
draft.
B
So
not
quite
released,
but
what
this
will
do
is
this
will
help
out
a
handbook
team
who's
looking
to
move.
They
may
be
moving
from
middle
man
to
front
man,
and
this
is
supposed
to
unblock
them
on
that
and
it'll
be
good
for
us
just
to
have
all
of
our
javascript
being
bundled
and
compiled
through
one
system
instead
of
two
so
yeah
that
was
nice
print
and
up
next
lauren,
hey
quick.
B
B
A
D
This
is,
you
know,
1.0
and
we're
going
to
be
rapidly
iterating
on
that
process,
and
we
made
a
couple
of
additional
admin
iterations
during
this
sprint.
Also
adjusting
the
order
of
the
content
blocks
that
show
in
the
admin
ui,
and
we
also
added
our
first
custom
component
to
allow
editors
to
add
youtube
videos
within
markdown
blocks
by
just
adding
video
id,
and
then
it
builds
all
the
iframe
code
for
you.
A
A
So
there
was
a
pdf
that
was
created
with
a
whole
like
year-long
study
of
out
of
the
office
and
remote
work,
and
they
needed
a
web
page
built
around
that,
and
that
was
also
built
with
our
new
slippers,
css
styles,
that
we
have
baked
into
the
the
above.getlab.com
repo.
So
that
was
cool,
I'm
also
in
the
middle
of,
I
guess,
troubleshooting
some
issues
with
my
grid
component,
but
I
did
at
one
point,
have
a
grid
component
in
slippers,
the
link
in
the
dock.
A
E
Okay,
am
I
sharing
yeah
yeah?
Okay,
I
don't
have
the
little
green
box,
so
we've
got
a
design
for
the
blog
template.
That's
going
to
be
integrated
into
the
cms,
so
we
have
the
figma
file
associated
to
the
issue,
so
anyone
can
go
check
that
out.
We've
got
some
mobile
designs.
What
else
do
we
have
for
this
sprint?
Oh
now,
I'm
lost
in
this
document.
Well,
I
know
what
I
did.
E
We
also
have
a
wireframe
for
the
a
net
new
page
which
is
going
to
be
a
continuous
integration,
landing
page
which
is
going
to
be
accessible
from
the
solutions
section.
So
all
of
this
is
going
to
be
a
new
design,
new
template
that
hopefully,
will
be
able
to
repurpose
for
future
solutions
pages,
and
we
also
kicked
off
some
work
on
redesigning
our
cards
and
card
anatomy
for
the
design
system
and
for
use
in
the
cms.
E
F
C
Yeah,
I'm
just
letting
you
try
and
figure
out
screen
sharing
here,
so
we
released
an
a
b
test
around
the
pricing
page
and
basically
we
were
trying
to
test
a
couple
things
about
how
we
present
our
plans.
So
you
know
before
they
weren't
grouped.
It
was
just
long
a
long
list
and
they
might
not
have
been
items
that
were
important
to
particular
buyer
groups,
or
you
know
they
also
didn't
showcase,
which
plan
had
which
values
attached
to
it.
So
it
was
hard
to
choose
based
on
the
list
of
features.
C
So
in
the
first
iteration
here
that
we're
testing.
We
have,
you
know
a
list
that
is
grouped
by
category
and
it's
in
a
typical
table
that
a
lot
of
our
competitors
use-
and
you
know
we
made
sure
that
the
list
was
shorter
and
grouped
and
had
you
know
a
couple
of
features
from
each
category.
So
you
know
what
you're
getting
if
you
get
a
free
account
versus
premium
versus
ultimate
and
why
you
would
want
to
upgrade
and
then
in
the
next
iteration
of
it.
C
We
are
testing
a
few
more
benefits.
So
you
know
just
give
people
a
brief
overview
and
the
table
is
not
on
the
page,
but
they
can
click
view
more
if
they
want
to
have
a
more
detailed
list
and
yeah.
That
is
kind
of
the
brief
overview
of
the
pricing
page
test
that
we're
running
up
next,
it
looks
like
is
hobby.
F
F
Okay,
so
this
is
really
nice,
oh
well,
this
is
looking
different
but
whatever,
and
so
oh,
I
think
it
might
have
to
do
with
the
the
next
thing
that
I'm
going
to
talk
about
is
that
I
got
rid
of
the
what
is
it
the
preflight
in
tailwind?
So
that
means
that
a
lot
of
these
are
just
like
unstyled
components,
and
this
has
to
do
with
just
things
that
we're
conflicting
with
about
repo
and
just
making
sure
that
we
have
no
conflicts
in
there.
F
We
might
figure
out
something
on
how
to
fix
that
in
a
future
release,
just
to
make
sure
that
we
have
a
better
sense
of
alignment
in
terms
of
what
normalization
process
looks
like,
but
for
now
it's
just
the
simplest
solution
is
just
to
turn
it
off
and
so
yeah.
That's
what
I
worked
on
this
week,
I'm
going
to
pass
it
over
to
jess.
A
Thanks
abby,
so
let
me
just
share
real
quick
okay,
so
one
thing
I've
been
working
on
is
this
partner's
overview
page
and
it's
just
kind
of
a
little
bit
of
a
reskin
of
our
current
one,
a
little
bit
more
content
in
it
and
that's
probably
gonna
go
today,
there's
just
like
one
copy
question
outstanding,
but
otherwise
the
design
is
pretty
much
there
and
then
the
other
thing
I
worked
on
was
the
a
b
test
design
of
the
pricing
page
that
brandon
already
showed.
So
I
think
I'll
I'll
skip
over
that.