►
From YouTube: Monthly UI to Code meeting - Oct 26 2022
Description
Monthly meeting with the Digital Experience engineers and designers where we discuss UI-related items.
B
Yeah
I
wanted
to
give
everyone
a
little
update
on
how
the
our
Major
League
hacking
fellows
are
doing
with
all
of
our
slippers
updates
a
lot
of
new
stuff
in
production.
I
think
we
have
to
update
a
version
or
something
to
get
this
into
actual
the
actual
buyer
Experience
Project,
but
the
stuff
is,
is
living
there.
Now
we
have
a
new
custom
drop
down
and
I
can
show
that
actually.
B
B
These
are
pretty
difficult
to
make
like
custom
wise
and
make
sure
all
that
stuff
is
kind
of
built
in
but
way
did.
This
did
an
excellent
job
for
the
first
iteration
there's
a
lot
of
Aria
labels
deep
in
this,
but
it's
just
a
normal
ad
values
and
and
select
and
then
from
A
View
standpoint.
B
It
emits
whatever
value,
is
selected
further
iterations
on
this
we're
going
to
update
some
of
the
default
text
here,
to
make
it
more
like
how
we'd
use
it
on
our
site,
we're
going
to
add
a
variant
that
will
allow
links,
kind
of
like
a
external
table
of
contents,
allow
these
options
to
use
like
icons
and
whatnot,
and
there's
also
like
a
test
here
to
kind
of
see
that
it's
working
next
I
think
they
were
loading
Spinners
or
loading
options
here.
So
we
have
a
progress
bar
and
a
spinner
yeah.
B
B
This
was
a
request,
I
think
in
our
last
UI
to
code
meeting
to
add
the
the
variables
here
under
the
table
and
likewise
with
the
colors.
So
those
are
some
recent
improvements
in
progress,
we're
working
on
an
intro,
page
kind
of
like
the
pajamas
version.
B
We
don't
really
have
a
design
for
that,
so
we're
just
kind
of
going
off
a
pajamas
version
and
hopefully
kind
of
just
doing
a
lot
of
iterations
to
make
it
look
great
with
the
little
content
we
have,
but
that's
getting
pretty
close
I
have
to
review
that
Mr
and
make
a
lot
of
con
comments,
but,
like
it's,
it's
gonna
be
good.
I'm
really
excited
for
that.
Next,
there's
a
components
overview
page
much
like
pajamas.
B
Also
a
page
I'm
really
excited
about,
because
this
page
kind
of
has
it's
like
our
table
of
contents.
You
don't
have
to
click
through
every
component
in
slippers
to
see
what
it
does
or
what
it's
used
for.
B
Every
component,
then,
should
receive
a
description
when
it
like
if
a
new
component
is
created,
so
that
someone
can
go
to
this
overview
page-
and
it
says
breadcrumbs,
our
bread
crumbs
component
is
used
to
like
show
navigational
hierarchy
or
something
so
that
way
someone
doesn't
have
to
like
click
through
and
see
like
okay,
how
what's
the
best
use
case,
and
maybe
they
might
find.
We
don't
have
a
component
for
that
best
use
case.
Yet
the
accordion
component,
the
first
iteration
of
this,
is
really
close.
B
One
thing
I'm
having
a
hard
time
finding
or
I
just
haven't,
had
enough
time
to
really
dig
into
this
is
our
accordion
component
should
really
be
taking
in
markdown
because,
as
we
use
it
on
our
site,
like
in
the
frequently
asked
questions
instances
a
lot
we'll
take
in
links
or
bold
text
or
lists
so
needs
to
take
in
that
markdown
I'm,
not
sure
how
to
implement
that
in
storybook.
B
Yet,
but
for
this
first
iteration
those
accordion
drop
down,
values
will
just
take
in
a
string
and
then
finally,
the
figma
storybook
plugin
Lauren
kind
of
mentioned
before
we
started
the
recording,
we're
getting
it
up
and
running.
It's
it's
difficult
for
someone
without,
like
our
git
lab
permissions
and
security
to
take
on.
But
this
developer
a
Mecca
did
a
really
great
job,
figuring
it
out
kind
of
locally.
B
So
we've
asked
him
to
kind
of
document
the
process
to
set
it
up
and
then
we'll
Lauren
or
I,
or
someone
will
take
those
steps
and
hopefully
get
this
plugin
up
and
running
posted
some.
Our
link
to
a
collection
of
issues
that
we
have
our
fellows
can't
assign
themselves
to
the
issues
because
they
don't
have
like
they're,
not
in
our
project
as
like
maintainers
or
something.
So
we
have
to
keep
track
of
our
our
projects
with
a
handbook
page.
So
that
link
is
there
if
anyone's
interested.
B
Moving
on
to
the
next
step
here,
I
want
to
note
that
it's
hard
to
get
like
designer
feedback
on
these
things,
because
since
our
developers,
our
fellows
are
like
gitlab
employees,
they
have
to
use
a
forked
version
of
our
slippers
repository
and
so
when
they
create
merge,
requests,
there's
no
review
app,
so
I
kind
of
have
to
like
pull
everything
down
locally
and
review
it
there.
B
So
I
had
a
point
here
like
designers.
How
can
we
make
this
easier
for
you
guys,
making
things
more
efficient
as
you
juggle
that,
with
all
your
other
crazy
work,
you're
working
on
would
screenshots
help?
Is
it
fine
if
we
just
do
our
best
and
like
I,
Lauren
or
I,
like
really
vetting
the
the
visuals,
putting
it
into
prod
and
having
an
issue
where
you
look
it
over
I
kind
of
did
something
like
that
with
Jess
anyway,
but
Jess
I
saw
you
have
a
point
next.
If
you
wanted
to
share
that.
C
C
I
am
curious
to
see
if
that,
like
storybook
figma
plug-in,
might
be
like
a
workaround
I'm,
not
100
sure
how
that
plugin
Works
yet
but
I
am
curious,
also
just
to
see
how
that
plug-in
works
for
like
our
QA
process.
So
if
that's
something
we
can
maybe
like
prioritize,
if
you
think
it'll
help,
maybe
we
could
prioritize
it
and
like
see
if
we
can
get
it
up
and
running,
maybe
a
little
bit
faster
just
to
see
if
it
works
for
us
and
then,
like
my
third
option,
is
like
live
coding.
C
B
Yeah
all
great
ideas
that
once
we
do
get
this
plugin
up
and
running
I,
will
make
that
a
priority
just
test
out
like
if
it
works
for
the
pages,
because
the
way
you
implement
pages
in
The
Storybook
are
different
than
components,
but
I
don't
see
why
it
wouldn't
work
yeah,
we'll
we'll
get
that
set
up,
but
we'll
start
with
screenshots
and
like
if
it's
just
like
a
really
big
thing,
where
it's
like
I
can't
show
you
like
this
long
page
with
screenshots
like
I,
think
the
live
coding
thing
is
is
a
great
solution
before
I
pass
it
off
to
Javi
anyone.
C
D
E
Yeah
I
was
just
saying:
we're
gonna
need
more
work
for
our
fellows.
They
are
flying
through
it
crushing
it.
You
know
they
do
work
about
30
hours
a
week,
there's
three
of
them,
so
it's
90
hours
got
them
until
mid-December.
C
Okay,
we
can
make
that
update
in
our
slippers,
dri
design
files.
We'll
just
should
we
tag
you
Lauren
or
Megan
or
yeah.
F
Sorry
I'll
just
say
this
because
I'm
not
typing
fast
enough,
I
I
just
had
this
idea
after
I
had
my
donut
with
Rey
yesterday
and
I
was
wondering
with
our
current
slack
integration.
F
When
there
is
like
an
update
to
an
MR,
you
still
have
to
Ping
somebody
on
slack.
I
was
just
wondering
I,
don't
even
know
if
we
can
do
this
or
if
the
fellas
could
do
this.
But
what
if
we
had
like
an
integration
where
I
could
ping
somebody
on
an
MR
inside
the
Mr,
it
also
gives
them
the
select
notifications.
E
G
G
F
But
I
was
thinking
because
I
see
like
how
Carrie
Ping's
like
stakeholders
for
page
reviews
and
she
has
to
go
and
do
a
separate
like
Ping
inside
of
slack.
So
maybe
if
there
was
a
way
just
to
do
it
all
and
where
them
are
so
there's
just
not
that
extra
step
and
yeah
to
your
point.
I
also
wouldn't
want
to
get
paid
for
both.
So
maybe
an
option
to
do
notification
for
one
or
the
other.
E
In
our
process
change
issue,
there's
a
threat
about
creating
a
deex,
stand-up
Channel,
so
we're
gonna,
maybe
depreciate
our
three
team
channels
just
have
a
stand-up
channel
that
our
gitlab
bot
posts,
all
the
things
to,
and
this
type
of
automated
notification
would
go
into
that
channel
as
a
possibility.