►
From YouTube: DEx: UI to Code, Sept 6 2023
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
Okay,
we'll
get
started,
I
think
we're
a
couple
minutes
and
now
I
just
wanted
to
bring
up
the
component
audit
I'm
hoping
to
close
that
out
this
iteration.
A
So
just
one
last
PSA,
if
you
want
to
check
it
out,
I've
linked
the
issue
in
point
a
it
just
talks
about
like
what
I
think
each
component
should
have
like
whether
it
should
be
multiple
versions
of
a
content,
type
or
One
content
type
with
multiple
variants
and
all
of
that,
but
I
think
ultimately,
it'll
be
up
to
the
person
building
the
thing
so
I
went
into
the
issues
that
I
could
find
for
Content
types
that
we're
building
in
the
CMS
and
added
a
link
to
that
issue.
A
If
anyone
wants
to
reference
it
while
they're
building
out
those
pieces,
I
think
most
of
a
lot
of
that
pre-work
is
kind
of
done
was
done
this
iteration
anyway,
but
it's
there.
A
If
you
want
to
look
at
it
or
if
you
have
thoughts
and
opinions,
the
I
guess
Barker
was
asking
me
kind
of
like
what
happens
to
this
and
I
think
it
was
just
a
nice
visual
way
to
kind
of
see
what
all
we
have
on
our
website,
but
I
think
going
into
the
future
when
it
gets
to
the
point
where
content
editors
start
making
stuff
in
the
CMS.
A
They
might
not
know
which
content
types
to
use
and
I
know
that
we're
planning
on
like
building
out
a
page
and
only
allowing
certain
content
Types
on
that
page,
like
Solutions
Pages,
only
have
these
types
of
content
available
to
them,
but
I'm
not
sure
how
that
works
with
creating
like
for
I'm
doing
the
heroes,
for
example,
and
if
I
make
one
hero
that
just
has
a
bunch
of
like
different
variants
like
there's,
either
a
primary
button
and
a
secondary
button
or
there's
a
background
image
or
there's
like
a
foreground
image
and
a
background.
A
B
A
Yeah
there's
a
waiting
room
here
and
I
have
to
like
admit
people.
This
is
not
my
meeting
I.
Don't
know
why
I
was
giving
these
to
numbers
yeah,
so
yeah,
that's
pretty
much
it.
A
quick,
tldr
I
know
that
a
couple
people
are
joining
now
but
like
yeah,
just
take
a
look
at
the
component.
A
Audit
I,
don't
know
what
it
looks
like
in
the
future,
but
maybe
there's
a
visual
library
that
we
can
give
to
people,
content
creators
or
content
editors
later,
but
for
now,
I'm
gonna
close
that
guy
out
and
yeah.
B
A
Do
it
all
yeah,
like
I
I,
know
looking
at
like
the
cards,
for
example,
we
have
so
many
different
cards
and
like
do
we
just
have
one
super
mega
card
that,
like
does
everything
like
you
know
it's.
It's
gonna
be
up
to
the
person
who
ends
up
building
each
of
these
things
as
we
go,
but
since
in
contentful
we
can
only
have
a
hundred
types
of
content,
we're
kind
of
limited
with
just
like.
B
B
Just
the
trade-off
is
yeah
governance,
in
terms
of,
if
someone
is
trying
to
use
something
in
a
certain
way
that
they
they
may
be
using
it
a
different
way
or
they
should
use
it
a
different
way.
I
think
that's
just
kind
of
the
trade-off
that
we're
getting
here,
but
it
seems
like
that
could
be
solved
through
something
else,
not
through
course
kind
of
like
blocking
the
component.
B
It
could
be
through
education
and
things
like
that,
so
yeah
I
mean
like
I,
think
just
sort
of
like
generally,
it
seems
like
your
recommendation
is
probably
the
like.
That's
the
way
I
would
I
would
recommend
going
opposed
to
having
sort
of
like
unique.
You
know
we
have
20
different
Heroes
I,
think
that'd
be
really
challenging
to
to
manage
and
then
multiply
that
through
all
the
components
on
our
experience,
it
could
be
really
challenging
and
probably
gets
away
from
the
purpose
of
this.
B
If
we
were
to
do
something
like
that,
so
yeah
I
think
this.
This
recommendation
makes
makes
a
lot
of
sense.
Yeah.
C
I
was
just
gonna
say
when
it
comes
to
the
code.
Do
we
keep
the
100
hero
files
and
then
pick
one
through
the
contentful
Json,
or
do
we
just
make
that
into
one
huge
hero
file?
How
are
we
gonna
do
that
in
the
code
I.
A
C
Think
that
can
get
very
hard
to
maintain
the
future,
maybe
having
the
separate
files
for
the
variants
of
the
hero,
but
picking
one
similar
to
what
we
do
with
the
component
is
where
we
have
like
the
empty
template
and
fill
in
with
whatever
component
is
needed,
because
I
don't
want
something
like
the
copy
media
component
that
we
had
to
happen
where
it
was
like
300
400
file
lines
of
code
to
render
a
copy
so
yeah.
That's.
B
Yeah
and
just
so
I'm
understanding
that
that's
the
difference
between
like
we
have
one
component
and
you
can
kind
of
just
pick
and
choose
what
you
want
in
something
opposed
to,
starting
with,
like
like
I,
just
to
make
sure
I
understand
what
what
that
means
or
if
there's
any
sort
of
like
impact
from
a
design
perspective
is
that
is
that
just
kind
of
sort
of
the
approach
from
an
engineering
perspective?
Or
would
there
be
any
impact
from
the
experience.
B
A
Cleaner
yeah
and
then
I
guess
the
other
piece
is
like
I.
You
know
we
have
pages
that
are
like
beautiful
and
like
not
cookie
cutter
Pages,
like
the
like
the
AI
pages
and
the
well
I
get
lab
page,
like
you
know,
pages
that
like
have
animations
and
like
fun
stuff
that
are
like
the
one-off
pages
and
do
not
belong
those
components.
Don't
belong
in
contentful
like
the
the
one-offs.
A
So
our
plan
is
to
just
keep
those
separate
in
buyer
experience
for
now
or
are
we
ever
gonna
like
keep
the
styling
I?
Guess
for
those
in
buyer
experience?
How
are
we
managing
those.
C
C
C
D
I
mean
you
can
have
a
static,
I,
I,
don't
know
a
page
example
like
the
platform
page.
We
could
just
have
like
a
static
content
type
for
the
platform
page.
You
can't
move
anything
around.
It's
purely
just
like
fields
to
enter
and
I
I
think
we
could
address
the
roles
like
if
we
don't
want
anyone
touching
that
we
can
just
set
the
role
to
us
as
Developers,
so
I
I'd
still
put
it
in
contentful.
A
A
B
And
so
this
is
like
those
unique
pages:
each
unique
page
will
take
up
a
content
type.
Is
that
right,
like
the
kitlab
Duo
page.
B
C
B
Oh
interesting
Megan
and
just
to
make
sure
I'm
understanding
this
correctly
like.
Are
you
saying
that,
for
instance,
so
take
a
look
at
the
gitlab
duo
page,
for
example,
are
you
saying
there's
going
to
be
multiple
content
types
within
that.
D
I
mean
that's,
that's
up
to
us
as
a
team
to
figure
out.
You
know
what
should
be
a
content
type
and
like
looking
at
the
gitlab
duo
page
like
I
I,
don't
know
what
that
section
is
where,
but
it's
like
the
cool
little
like
the
little
image
that
goes
down
and
then
select,
AI
powered,
workflows,
privacy,
first
blah
blah
like
if
we
don't
want
anyone
to
really
update
that
like
we
could
make
the
whole
page
a
content
type,
and
it's
like.
D
Okay,
like
you
can't
like
the
hero,
is
always
going
to
have
a
title
subtitle
and
a
button
that
cool
image
thing
is
always
going
to
be
like
the
image
on
the
left
and
like
four
chunks
of
content
like
there's
something
you
can
do
about
that.
You
could
edit
the
headers
if
you
want
like
it
as
developers,
already
we're
breaking
out
your
designs
in
two
components.
D
Right
so
like
we
have
a
button
component
thanks
to
slippers
in
our
design
system
like
we
have
little
atoms
as
components
already,
and
sometimes
those
atoms
build
up
like
an
entire
hero
component
or
Carousel
component.
So
it's
just
kind
of
like
how
do
we
build
these
out
in
our
in
our
mental
model,
because,
like
I
know,
we
have
a
button
content
type
already,
because
that's
used
everywhere.
D
We
should
just
might
as
well
make
one
and
we
could
have
a
hero,
content
type
or
like
we
could
have
a
huge
chunk
of
the
page,
be
part
of
the
page
content
type
and
like
yeah
I,
don't
know,
there's
so
many
ways.
We
could
do
it.
It's
just.
We
all
have
to
be
on
the
same
page
on
how
we
break
these
things
down.