►
From YouTube: DEx UI to code - Nov 30, 2022
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
A
30Th
Megan,
you
have
the
first
couple
points.
B
Yeah,
it
looks
like
a
lot,
but
I
won't
say
much.
The
major
league
hacking
fellowship
program
ends
next
week.
What
a
time
it
went
so
fast,
but
we
got
a
lot
accomplished.
B
The
fellow's
last
day,
I
think
it's
Thursday,
because
they
have
like
a
graduation
thing
on
Friday,
but
we
gave
him
some
swag
store
codes
as
like
a
thank
you
and
so
far.
15
like
larger
issues
have
been
closed
and
it'll
most
likely
be
like
20
or
more
than
that
by
the
end
of
next
week,
shout
out
to
Barker
for
all
your
help.
I
know
you're
not
on
this
call,
so
I
hope
you're
watching
this.
B
But
thanks
for
all
your
support
and
making
sure
we
were
hitting
every
milestone
and
thank
you
to
everyone
that
kind
of
helped
with
like
refining
issues,
I
tagged
people
as
we
were
finding
things
and
answer,
questions
that
our
fellows
may
have
pinged
you
on,
and
especially
the
designer
views
that
was
very
helpful.
Getting
that
feedback
and
making
new
issues
for
that
there's
still
a
ton
of
slippers
issues
left
in
the
backlog
that
they
didn't
get
to
or
that
we
didn't
add
to
their
immediate
backlog.
B
So
you
know,
if
you're
looking
for
something
to
work
on
or
contribute
in
a
way
to
slippers,
there's
plenty
of
stuff
to
grab
so
go
grab
them
I.
Also
added
like
a
long
list
of
what's
been
accomplished
so
far,
I'm
not
gonna,
read
that
on
here,
but
at
the
end
of
next
week,
when
we
have
like
the
the
final
list,
I'll
post
it
in
our
Dex
slack
Channel
but
yeah.
Thank
you.
A
All
right,
I'm
going
to
interject
Megan,
thank
you
like
you,
have
been
watching
all
of
them
the
whole
time
and
creating
issues
and
I,
don't
know
if,
if
you
volunteer
for
that
or
if
that
just
fell
on
you,
but
either
way,
it's
like
super
appreciated
because
it's
been
apparently
a
whole
quarter
has
flown
by
and
you've
just
like
taken
this
on.
A
So
like
from
my
side,
we
see
all
the
work
that
you've
been
doing
with
them
and
managing
that
that
team
as
well.
Thank
you.
So
much
do
we
know
if
we're
taking
on
another
cohort.
Has
that
been
decided?
I
know
there
was
talk
of
it.
B
I,
don't
think
so,
I
think
the
like
the
cost
per
like
all.
That
kind
of
stuff
didn't
quite
work
out,
but
it
would
be
nice
if
we
could
have
it
like
once
a
year.
I,
don't
know
it's
all
up
like
whether
like
git
lab
sponsors,
the
program
or
not
and
I'm
not
sure
if
they
are.
But
if
there's
a
way,
we
could
have
like
a
fellowship
like
once
a
year
get
a
backlog
accumulated
and
stuff
like
that
would
be
that'd,
be
great,
but
we'll
see.
A
Cool
cool
Nathan
has
the
next
Point
he's
async,
so
there's
I,
guess
an
issue
with
duplicate,
like
versions
of
slippers
or
css,
being
imported
for
slippers
components
he's
looking
into
it.
I'm,
also
seeing
I've
just
general
questions
about
how
slippers
is
imported
into
our
buyer
experience
repo.
If
you
look
in
the
head
of
our
website
right
now,
every
single
component
in
slippers
is
in
the
head,
which
seems
like
a
weird
way
to
load
slippers.
A
Let
me
share
my
screen
because
I
have
it
up
right
now,
but
I
will
connect
with
Nathan
on
this
as
well.
If
he's
like,
investigating
it,
but
I
mean
I'm
local
here,
but
I
can
go
to
any
of
our
websites
Maybe,
let's
go
with
so
many
tabs.
A
So
if
I
go
and
look
at
like
the
head
of
our
website,
there's
like
all
these
meta
tags
and
all
this
like
necessary,
stuff
right
and
then
as
soon
as
you
hit
like
the
end
of
our
links,
you
get
all
of
these
style
tags
and
you'll.
See
that,
like
this
is
our
accordion
component.
You
know
what
I
mean
this
is
song
component,
I,
guess
Chevron,
maybe
you're
an
icon.
Oh
drop
down,
that's
what
it
is
and
like
every
single
thing-
and
this
just
goes
like
for
evsies.
A
You
know
what
I
mean
like
that's
a
lot
scripts
I
think
it
ends
somewhere
around
here
and
it's
maybe
not
where
the
CSS
belongs
and
I'm
not
I'm,
just
like
starting
to
dig
into
next
config
right
now
and
see
how
the
CSS
gets
loaded
into
our
site,
because,
if
it's
being
loaded
there
and
also
being
imported
elsewhere,
maybe
that's
where
our
duplication
is
coming
from,
but
yeah.
B
It
is
just
like
causing
problems
in
the
sense
that,
like
I,
made
a
change
to
like
H1
and
H2
font,
sizes
and
stuff,
but
the
duplicate
slippers
thing
is
like
overriding
that
so
we're
getting
the
old
stuff
I'm
sure
it's
all
connected,
but
we
removed
it
from
the
nav
right
or
not
yet.
A
It's
removed
in
that
Mr
like
it's
not
merged
in
yet,
but
there's
an
MR
open
where
slippers
is
still
a
pure
dependency.
A
So
it
should
pull
slippers
from
buyer
experience,
but
it's
also
being
pulled
in
as
a
Dev
dependency,
so
for
local
development
in
the
nav
repo,
you
would
see
the
slipper
Styles
we
can
like
I,
have
an
MR
open
that
we
can
like
rip
slippers
out
completely
right
around
CSS
for
the
nav
it's
about
200
lines.
But
of
course,
then
it
doesn't
stay
up
to
date
as
we
change
slippers
stuff,
but
that
is
also
an
option
that
we
could
try
and
see
if
that,
like,
like
fully
scorching
slippers
out
of
nav
entirely.
A
C
Hi
I
I
have
I've
seen
some
stuff
in
the
code
in
the
navigation.
This
is
happening
in
the
navigation
right.
C
Every
CSS
file,
Imports
everything
from
slippers,
so
I
think
that
every
component
that
we
are
using
on
the
navigation
are
important
in
the
same
CSS
one.
At
the
same
time,
so
I
believe
we
can
try
to
globally
import
once
that
CSS
that,
like
we're
doing
buyers
experience
and
maybe
that
can
fix
the
issue.
A
Yeah,
that's
very
true.
We
can
try,
maybe
doing
that
for
today
to
try
and
make
an
MR
to
be
released
today.
Yeah
that
might
be
worth
trying.
I'm
gonna
make
a
note.