►
From YouTube: DEx Retro - Sept 7, 2023
A
B
Thanks
Laura
yeah
first
one's
actually
about
you,
thanks
for
the
component
audit
that
figma
file
I,
have
it
open
on
a
tab
all
day
every
day,
and
so
when
I'm
building
out
console
types
I
can
be
like.
Oh
this
one
has
a
hero.
This
one
doesn't
and
so
I
just
want
to
say
you're
saving
me
hours
every
day.
So
thank
you.
B
C
D
Yeah
I
just
wanted
to
say
we
launched
the
platform
page,
which
is
super
exciting,
so
this
was
work
that
was
just
rolled
over
a
little
bit
from
Q2,
but
it
was
a
lot
of
work
and
I
know
a
ton
of
energy
went
into
it.
I
was
writing
at
the
thank
you
and
the
thanks,
Channel,
and
just
seeing
how
many
people
we
collaborated
with.
It
was
amazing,
but
it
also
kind
of
understood
why
it
took
so
much
time
when
it
requires
so
many
different
groups
working
together.
D
C
And
I
got
a
big
shout
out
from
Miracle
she's.
Just
really
helped
us
in,
like
leadership,
get
aligned
on
what
the
cookie
marketing
cookie
does
and
how
we
want
to
iterate
from
it
to
make
it
better
and
then
also
shipped
a
fix
to
our
bug,
which
is
awesome
and
I
saw
that
that
got
merged,
which
is
super
cool,
so
good
job.
There
I'm
right
back
to
filza.
D
D
When
we
first
started
this
work,
I
know
we
got
a
lot
of
hesitation
from
our
team
around
the
timeline
so
being
able
to
meet
the
deadline
of
September
7th.
For
this
video
is
incredible
and
we
have
exactly
watched
3x
speed.
We
talk,
slow
I,
talk
fast,
so
it'll
be
fine,
but
yeah.
It's
really
exciting.
So
we're
gonna
share
that
out
with
the
rest
of
the
org
and
there's
a
lot
of
great
insights
that
are
going
to
inform
our
next
year's
thinking,
which
is
super
exciting,
so
great
work
for
the
design
team.
C
E
Think
it's
basically,
the
fields
that
come
in
the
object
in
contact
full
are
very
nested.
He
pasted
an
example
there,
the
parent
type,
Fields
reference
fields
and
other
reference
Fields,
that's
how
it
comes
in
contentful,
so
I
think
he
suggesting
making
a
solution
beforehand,
because
we
are
going
to
have
contentful
and
yaml
files,
so
yaml
files
will
have
to
have
this
this
same
structure
as
well.
If
the
same
component
is
going
to
consume
content
from
both
sources,
I
think
that's
what
it
is.
B
A
F
B
B
As
like,
larger
content
types
just
for
now,
because
I
think
maybe
we're
going
a
little
too
abstract
and
a
little
too
modular,
and
that
we
might
shoot
ourselves
in
the
foot
later
down
the
road
because
we're
gonna
have
so
many
these
little
building
blocks
and
we're
not
gonna
be
able
to
get.
You
know
the
200
300
Pages
out
quickly
because
we're
trying
to
make
every
single
little
block
and
then
we're
trying
to
reference
them
all
together.
B
So
I'm
wondering
if
we
should
just
start
thinking
of
things
bigger
like,
for
example,
the
pricing
page,
the
next
steps
component
for
sure
we
can
reuse
that,
but
maybe
like
that
Grid,
it's
I,
don't
know
if
it's
going
to
be
reused
somewhere
else,
I,
don't
know
if
it's
worth
trying
to
like
make
it
fit
into
another
example
of
a
grid
on
another
page.
Why
don't
we
just
hard
code
it
for
the
pricing
page
for
now
and
then
later
down
the
road?
B
If
we
find
it
reusable,
let's
make
it
reusable
so
I
almost
want
to
like
change
the
way,
we're
thinking
and
or
propose.
We
change
the
way,
we're
thinking
to
maybe
like
static
first
and
then,
if
it's
reusable
go
reusable
later.
If
that
makes
sense,
because
I'm
nervous
that
we're
going
to
spend
way
too
long
trying
to
create
this
massive
structure
of
relationships
and
it's
going
to
be
a
mess.
E
G
It
was
brilliant
now,
just
just
to
reiterate,
like
we
have
a
lot
to
do
in
a
bit
of
a
short
amount
of
time
like
work
small
for
now,
like
we're
learning
as
we
go
and
we're
finding
better
ways
to
do
things.
But
maybe
now
is
not
the
right
time
to
do
that.
Just
build
it
a
simple
way
and
when
you
hit
the
wall,
then
you
break
through
the
wall.
But
no
there's
no
need
to
get
a
sledgehammer
ready
now,
I'm
really
bad
at
metaphors.
But
hopefully
that
made
sense.
B
No,
that's
a
good
point,
though,
like,
for
example,
the
events
page
like
that
hero
I,
don't
think,
is
reused
on
other
pages.
So,
instead
of
trying
to
adjust
the
existing
hero
to
work,
why
don't
we
just
hard
code
it
in?
For
that
events
page
and
let's
be
real,
like
a
lot
of
these
Pages
aren't
going
to
get
updated
by
the
content
teams.
B
The
things
are
going
to
update
they're
gonna,
update
events,
they're
gonna
update
customer
case
studies,
you're
gonna
update
the
blog,
so
maybe
those
template
Pages
sure
we
start
thinking
about
reusability
there,
but
the
pricing
page
homepage
I,
don't
think
we
want.
You
know
everyone
being
able
to
shift
stuff
around
and
make
massive
changes
to
the
these
pages.
A
Yeah
I've
definitely
been
in
that
cycle
like
because
I
have
the
events,
hero
and
I
agree.
It's
it
I
know
it's
only
used
on
that
one
page,
because
it's
in
my
audit,
but
the
like
try
to
make
a
hero
that
I
know
I
can
use
in
the
future
like
make
this
into
a
version.
I
can
use
later
and
like
merge.
The
two
together,
it's
like
kind
of
put
me
at
a
dead,
stop
like
Megan
was
saying
like
I
just
need
to
like
no
no
just
build
it.
We
delete
this
later
and
hard
code.