►
From YouTube: 2021/12/02 Backdrop Design/UX
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,
hello,
everybody
it's
thursday
december
2nd,
and
this
is
the
backdrop
weekly
ux
and
design
meeting
before
we
start
its
meeting.
We
go
around
the
room
and
introduce
yourselves
I'll
start
with
myself.
I'm
greg
I'm
joining
from
greece
generally
interested
in
anything
related
to
backdrop,
in
any
ways
that
I
can
help
really
excited.
This
is
the
last
month
that
we
can
get
most
of
the
things
for
the
next
miner
release,
so
yeah
mostly
going
to
be
working
on
issues
each
chance.
I
get
I'll
pass
it
on
to
robert.
B
C
Tim,
okay,
I'm
not
muted,
am
I
where's
my
I'm
okay.
You've
got
tim
erickson,
st
paul
tim
coming
to
you
from
deerwood,
minnesota
and
yeah.
I
feel
like
the
last
month
or
two.
A
lot
of
activities
been
happening
in
contrib
and
I've
been
doing
a
lot
of
contrib
stuff
and
now
we're
we're
zeroing
in
on
feature
freeze
a
month
from
now.
I
think
this
january.
C
Second,
I
think
I
saw
might
be
the
official
day
so
probably
focusing
more
on
core
issues
for
the
next
month
and
I
don't
feel
like
we're
starting
to
focus
in
so
let's
go
ahead
and
get
started.
We
have
a
small
group.
Today,
robert
you
were
just
listing.
Let's
look
at
the
you're
pulling
a
few
things
in
right
yep.
So
I
real
quickly.
C
Yeah,
some
of
the
things
you're
thinking
I
think
are
for
will
be
for
the
next
meeting.
That's
okay!
How
to
handle
bug
fixes
like
we
should
do
with
nate.
That
meeting.
C
For
this
meeting
I
was
thinking
about
hidden
path.
I
wanted
to
show
a
little
bit
the
progress
and
hidden
path
knows
and
get
more
feedback,
because
I
think
largely
what
this
issue
is
at
right
now
is
largely
a
stage
of
give
and
take
on
content
and
stuff,
and
I
just
need
feedback,
and
I
might
need
to
bring
it
up
briefly
in
a
couple
of
meetings.
If
we're
gonna
get
it
in,
so
we
can
revise
it.
Then
then
robert,
I
think
one
of
the
issues
I
you
had.
C
Where
are
they
well
one
of
them
that
I
think
you
you
might
need
some
some
ux
design
feedback
and
there's
the
contextual
links
one.
What
was
the
other
one,
though,
towards
the
top
of
your
list.
B
Yeah,
so
there
was
adding
the
contextual
menu
yeah
to
layouts
and
got
some
overnight
feedback
from
indiegozella
who
said
essentially
it.
It
doesn't
play
well
with
some
themes
and
suggested
having
it
off
by
default,
and
I've
made
that
change
in
push
to
revise
pr
with
that.
C
C
We
talked
about
it
a
bit.
If,
if
you,
if
it
is,
it
is
some
had
you
planned
on
it
being
that
enable
and
disable
option
yeah.
B
C
B
C
It
I
mean,
I
think,
I'm
on
the
side
of
if
we
we
can't
have
an
individual,
that
we
can
enable
it
by
default.
If
it's
breaking
some
yeah
some
themes,
yeah,
like
you
know,
I
mean
this-
is
just
it's
sort
of
a
little
bit
gray
area,
but
I
lean
that
way
and
I
think
other
people
would
too
so
yeah.
B
I'm
fine
with
that.
The
flip
side
is
it's
it's
a
little
harder
to
discover
now,
but
but
when
things
break
out
from
under
you,
that's
much
more
painful
for
the
developers
soon.
C
Yeah,
have
you
shared
the
issue
number
yet
for
that
in
case
anybody's
yeah?
It's
15
59
15
59.,
so
I
think
jen
had
been
leaning
towards
the
idea
because
it
was
breaking
things
of
having
it
into
crib
until
2.0
and
at
that
like
in
2.0.
That's
when
we
could
enable
this
by
default.
C
But
in
the
meantime
I
think
that
a
good
compromise
would
be
having
it
off
by
default.
So
we'll
see
what
others
think
of
that.
That
seems
to
me
like
and.
B
I'm
sorry,
I
gave
the
wrong
number.
It's
it's
26,
26.,
okay,.
A
Did
you
have
a
question
greg?
Oh
yes,
which
issue
we
were
talking
about,
but
I
phased
out
for
a
moment.
Is
it?
Is
it
the
one
with
contextual
links
being
one.
B
C
C
Of
the
people
that
have
been
involved
in
that
discussion,
it
sounds
like
most
of
them
would
be
okay
with
the
option.
The
the
the
def
off
by
default
option
would
be
good
to
hear
from
general
what
she
thinks
but
yeah.
I
think.
B
A
Yeah,
I
just
didn't
check
the
the
comments
that
happened
in
the
last
12
hours.
I
have
to
admit,
but
yeah
it's
one
of
my
pet
peeves
as
well.
I
find
it
yeah.
I
find
it
an
odd
workflow
for
those
that
have
been
working
with
backdrop.
A
long
time
they
have
gotten
used
to
it
like
the
work
around
is
to
basically
edit
edit
the
block
and
then
close
the
dialogue
and
then
do
it,
but
we've
sort
of
like
gotten
used
to
that
work
around,
but
it
feels
like
an
odd
and
quirky
workflow.
A
So
I'm
not.
I
haven't
read
the
last
comments,
but
I've
heard
you
guys
say
that
there's
concerns
about
breaking
existing
themes
because
of
it.
Well,
yes,.
B
Yeah
well
so
indigozella
said
the
when
she
tried
it
with
the
snazzy
theme
that
the
result
she
just
said
it
made
it
ugly.
But
I
interpret
that
as
breaking
the
theme
so
because
it's
it
does
have
a
checkbox
to
turn
that
capability
on
and
off
and
when
it's
off
there's
no
change
to
the
layout
when
it's
on
there's
new
divs
for
the
contextual
links-
and
you
know
that
that
certainly
could
break
anything
that
used.
You
know
class
greater
than
class
that
wasn't
expecting
that
div
wrapper
to
get
stuck
in
there.
B
A
A
B
That
does
the
same
thing
for
those
who
might
prefer
to
keep
everything
in
the
admin.
C
A
Is
there
any
wrapper,
contextual
link
that
that
is
on
a
top
level
element
by
default,
the
an
existing
one
that
we
have
now
that
we
can
sort
of
like?
I
know
it
might
not
look
perfect,
but
that
we
can
hook
on
like
instead
of
creating
a
new
div
for
a
new
contextual
link
and
we
tuck
those
links
into
a
an
existing
one.
B
C
Well,
if
anybody
has
any
other
ideas
on
how
to
make
this
work
with
it
on
by
default,
that
would
be
good,
but
otherwise,
for
now
I
think
I
mean
my
history
of
this
was
that
we,
you
had
to
fix
basis
right,
it
broke
bases
originally,
and
then
we
made
an
adjustment
to
basis,
and
at
that
time
our
assumption
was
well.
If
it
could
break
basis,
it
could
break
other
themes.
B
Yeah,
although
it
didn't
break
basis
in
that
the
page
looked
exactly
like
it
did
before
it
was
that
it
didn't
work
in
basis
because
it
was
hidden
underneath
the
admin
bar.
So
so,
there's
separate
configuration
settings
to
to
push
it
down
below
the
admin
bar.
If
you
happen
to
be
using
basis
or
another
theme
that
accommodates
the
admin
bar
the
way
basis
does
seven
does
it
differently,
and
so
it
works
out
of
the
with
no
cur
no
extra
changes
needed
for
seven
got.
It.
A
A
It
wraps
the
layout,
the
layout
yeah
yeah.
So
how
about
if
we
had
a
second
admin
bar
like
region
which
is
at
the
top
of
the
page
but
lengthwise
like
it,
didn't
have
any
background.
It
was
transparent
and
then
the
only
thing
that
it
would
accommodate
was
that
cog
wheel
for
that?
Have
you
tried
that?
Do
you
understand
what
I'm
saying?
Maybe
I'm
not
explaining
it?
Probably.
A
B
That's
that
sounds
more
complicated,
more
more
fraught
with
hazard.
The
difference
basis
accommodates
the
admin
bar
by
putting
a
margin
on
the
top.
Seven
accommodates
it.
B
I
think,
with
padding
and
or
maybe
it's
the
other
way
around,
but
but
but
so
with
one
of
them.
I
guess
it's
the
one
with
padding
that
must
be
basis
that
then
I'm
not
sure
which,
but
they
do
it
different
ways.
This
okay,
I'd,
have
to
play
this
again
like
it
basically
works.
B
We
just
need
to
account
for
the
fact
that
there
is
some
theoretical
case
where
it
won't.
I
think
it
would
be
hard
to
come
up
with
an
entirely
different
solution
that
would
that
would
be
likely
to
work
in
that
theoretical
case
that
it
doesn't.
Although
I
guess
we
could
also
try
it
out
with
snazzy
now
that
we
know
that
that's
going
yeah.
C
Okay,
well,
I
think
we've
got
a
progress
forward
there
and
if
anybody
has
more
ideas,
they
can
put
them
into
the
issue.
But
thanks
for
working
on
that
and
the
hidden
do
we
have
the
hidden
nodes
issue
number
in
the
in
the
agenda
right
4903!
That's
what
it
says.
It
makes
people
happy.
C
C
Let's,
if
it's
okay,
I'd
like
to
talk
about
that
one,
a
minute
yeah
sure-
and
I
I'm
gonna-
share
my
screen,
because
I
have
some
work
to
show.
That
is
not
in
the
pr
because
and
we'll
talk
about
this
we're
having
problems
we
haven't,
I
haven't
solved.
I
haven't
really
worked
on
the
the
problem
since
last
week,
robert,
but.
C
So
this
the
hidden
path,
how
quickly
the
summary
of
the
hidden
past
content
type
is
the
idea
is
to
add
a
new
hidden
path,
content
type,
which
is
a
content
type
that
basically
uses
the
old,
what
we
call
rabbit
hole,
but
we
have
a
setting
in
backdrop
that
allows
you
to
hide
the
path
from
regular
users.
C
So,
if
you're
creating
a
type
of
content
that
is
only
intended
to
be
displayed
in
blocks
or
in
views
or
in
a
slideshow,
you
can
hide
that
so
people
can't
access
the
regular
node,
and
this
is
a
type
of
content
that
is,
is
fairly
useful
in
a
lot
of
websites,
but
a
lot
of
users,
don't
sort
of
understand
how
it
works.
So
our
goal
was
to
provide
the
content
type
out
of
the
box,
along
with
some
samples
of
how
it
might
be
used.
C
Now.
I
think
that
this
issue
is
primarily
at
a
stage
where
we
need
to
settle
on
some
images,
and
these
are
pretty
random
images,
I'm
hoping
that
somebody
will
come
up
with
better
ones.
One
of
the
blockers
on
this
issue
right
now
is
that
to
generate
con.
We
wanted
sample
content
like
this.
This
we
had
a
meeting
about
this
about
six
weeks
ago
and
we
spent
an
entire
design
meeting
talking
about
this
issue,
and
I
think
we
came
to
a
consensus
that
this.
C
C
I
had
and
I've
borrowed
some
of
his
ideas,
and
I
have
it
working
in
my
local,
but
the
tugboat
bills
are
not
we're
having
problems
getting
the
images
in
the
right
place
and
named
correctly
and-
and
we
had
a
bunch
of
us
looking
at
this
issue
last
week
and
it
seems
like
it.
I
think
we
were
pretty
sure
that
the
problem
is
specific
to
tugboat
there's
something
about
the
way.
C
Tugboat
builds
the
sites
that
is
causing
this
to
not
work
when
normally
it
would
so
that
one
blocker
is,
we
can't
really
get
a
working
pr
until
we
solve
that
problem,
which
is
probably
solvable,
but.
C
C
Yes,
and
and
back
wilmont
peter
and
robert-
and
I
all
spent
about
an
hour
together-
okay,
very
nice,
trying
to
get
this
fixed.
So
we
had
smart
people
looking
at
it.
Yeah
yes,
well
excluding
mine,
but
yes,
the
other
three
at
least
anyways.
So
that's
where
they're
at
I
I
I
don't
know
that
I
want
to
be
responsible
for
finding
images
here.
So
I
just
took
some
cute
images
that
I
thought
made
sense,
but
I
doubt
that
people
are
going
to
like.
C
I
think
these
are
all
wikipedia
or,
like
you
know,
the
images
that
should
be
available
to
use.
But
if
somebody
one
of
somebody
were
willing
to
do
some
work
on
the
images,
that
would
be
great
if
we
I
mean,
but
we
what
I
need
is
sort
of
feedback
on.
This
is
the
first
time
that
anybody
is
seeing
this
with
all
three
images.
C
C
C
So
some
of
the
the
the
issues
coming
out
of
that
meeting
the
suggestions
were
one
more
issues.
Two
greg.
You
had
made
a
comment
that
like
we're
explaining
what
these
cards
are
and
then
we've
got
this
post
and
we
you
don't
understand
what
the
difference
is.
So
I
I
added
some
content
here
about
that.
Like
what's
different
about
this
than
the
things
above
it,
there
was
also
some
discussion
about
possibly
having
a
link
to
the
magic
diffuser
guide,
yeah
that
helps
yeah.
We
saw
that
on
the
drupal
site.
C
I
also
I
put
a
couple
of
direct
links
into
the
the
user
guide.
You
know
like
this
one
taking
you
directly
to
the
layouts
section
of
the
user
guide,
so
what
we've
avoided
is
doing.
There
was
talk
about
having
links
to
things
like
how
to
do.
You
know
to
the
delete
page
or
for
content,
but
we
don't
want
to
do
any
links
that
take
you
to
admin
pages,
because
if
you're,
not
logged
in
those
links
are
broken.
C
A
Yeah
and
the
other,
the
other
feedback
was
that
if
you
view
these
pages
anonymous,
then-
and
you
click
the
links
because
they're
pageless
nodes,
you're
gonna-
get
four
or
fours.
So
we
need
to
render
those
as
text.
C
Yes-
and
that
is
true-
and
there
is
an
issue-
there
is
an
issue
in
the
issue-
queue
which
would
be
a
blocker
for
this
issue
to
fix
that
jen
has
a
pull
request
that
basically
will
automatically
check,
and
if
a
user,
if
you're
an
anonymous
user,
doesn't
have
access
to
this
and
yeah
well,
we
were
working
on
that
poll
request
already
for
the
last
release.
So
I
believe,
though,
that
somebody
found
a
problem
with
it.
C
A
Yeah
but
but
it
looks
promising,
I
said
it's
pretty
close,
so
basically
yeah
if
we
were
to
sort
of
like
bullet
point,
the
the
remaining
tasks
is
fix.
The
issue
with
the
links
agree
on
the
text
that
we've
added
tweak
it
whatever
when
we
like
it
and
then
find
images,
is
that
it
for
it
and
then
and
then
solve
the
problem
with
attack
board
pr?
Those
are
the.
C
Things,
I
think
so
I
mean
at
one
point
I
had
hoped
to
maybe
do
a
little
bit
more
on
the
front
page,
but
I
think
we
decided
that
that
might
not
be
wise
and
I've
agreed
that
we
should
focus
on
this
part
of
it
so
yeah.
What
I
will
do
is
put
a
screenshot,
so
people,
because
we
can't
people
can't
use
the
tugboat
right
now.
Well,
actually
they
can
use
the
tugboat
for
the
content.
C
They
won't
be
able
to
see
the
images,
although
the
images
probably
are
not
permanent
anyways.
So
if
people
want
to
review
the
content,
they
can
go
to
the
tugboat,
otherwise
I'll
also
put
a
screenshot,
so
you
can
into
the
the
issue
so
that
people
can
see
where
this
is
at
and
give
me
some
feedback.
C
C
Yeah,
okay-
and
I
know
people
are
not
having
time
to
read
all
and
proof
this
text
right
now
on
the
the
meeting.
So
let's
leave
that
for
the
issue
too
yeah.
If
there's,
if
there's
no
other
immediate
feedback,
I
think
that
gregory,
you
summed
it
well
in
terms
of
what's
left
to
do,
and
otherwise,
then
this
is
moving
along.
I
do
need
help
with
that
tugboat
issue.
Actually
joseph,
were
you
there
last
week
for
that
discussion
too?
C
Oh
yeah,
well
good
we'll
talk
about
that
later.
I
hope
that
went
well
or
is
going
well.
We
this
was,
we
were
during
the
last.
We
have
off
we're
doing
office
hours
every
wednesday,
at
least
through
the
end
of
the
year,
and
it
was
last
week
during
office
hours
on
wednesday
afternoon
that
the
brain
press
tried
to
solve
the
problem
and
that's
not.
A
Yeah
so
I
was
advocating
for
10
40,
which
is
basically
inline,
form
errors,
and
I
started
doing
some
preliminary
work
on
my
local
and
then
I
realized
that
there's
not
necessarily
blockers,
there's
both
blockers
and
groundwork.
A
I
guess
issues
that
need
to
be
done
before
that
some
of
them
may
be
considered
bugs
or
they're,
maybe
considered
tasks
other
new
features,
but
they
have
to
do
they
all
revolve
around
form
api.
So
some
of
them
are
api
additions
or
fixes.
A
A
So
so,
basically,
one
of
the
things
that
we
need
to
do
is
to
switch
to
html5
validation.
A
A
C
Okay,
other
than
drawing
our
attention
to
that
is
there
anything
else
we
can
do
right
now
to
help
you.
A
I
know
that
when
we
brought
up
this
issue
during
past
meetings,
I
think
both
jen
and
nate
sort
of,
like
said:
oh,
you
picked
a
hard
one,
but
it
doesn't
seem
to
be
a
hard
one.
Okay,
it
might
be,
it
might
be
a
tricky
tricky
to
navigate
around
on
all
these.
You
know,
satellite
issues
that
I
need
to
sort,
but
I
trust
their
judgment.
So,
if
there's
something
that
I
didn't
see,
that
is
that
sort
of
like
justifies
this
difficulty.
A
C
Okay,
is
that
enough
on
that
issue,
then?
Yes,
okay,
so
I
want
to
do
one
more.
That
could
be
a
quick
one
which,
which
is
actually
another
one
of
the
ones
you
listed
robert.
It's
issue
4868,
that's!
This
is
the
help
text
to
the
layout
page.
C
I'm
going
to
share
my
screen
again,
so
we
can
look
quickly
at
what
you
did
and
then
my
question,
which
I
just
think
will
be
easier
to
answer
here
than
it
would
be
in
the
issue-
is
an
issue.
So
the
issue
is
we
just
wanted
to
add
some
help
text
to
add
to
better
describe
how
the
layout
listing
page
works.
C
B
Yeah,
so
just
a
second,
I
want
to
also
pull
it
up.
Okay,
say
idea:
I
mean
basic
ideas:
layouts
are
probably
the
most
confusing
thing
to
people
coming
from
drupal
7,
because
we've
never.
B
Like
it
and
and
we
wanted
to
make
it
to
give
them
a
lot
of
information-
that's
there
on
the
page
that
where
the
confusion
starts
so
hence
expandable
help
test
and
greg
had
recently
added
the
details,
element
which
is
wonderful,
because
now
we
can
use
that,
and
so
I
did.
C
Yep
and
that's
my
my
question,
the
reason
I
wanted
to
talk
about
this
in
the
meeting
the
functionality
in
the
text
I'm
pretty
happy
with,
and
I
I
think
I
might
have
been
part
of
the
impetus
for
this,
because
at
a
previous
meeting
I
was
asking
about
how
the
the
ordering
affected
the
display
of
layouts
and
that's
maybe
part
of
what
inspired
this
and
I've
added.
C
B
So,
but,
and
something
I've
mentioned
this
in
a
comment:
there's
another
relevant
issue
issue
5077
right,
which
is
a
reorganization
of
reordering
of
the
of
these
layouts,
which
I
I
hugely
am
in
favor
of,
and
it's
just
it's
a
gen
change.
B
C
A
In
that
a
once
one
gets
once
this
gets
in,
we
will
we
may
have
to
rewrite
the
text
or
adjust
adjusted
and
that
this
was
basically
trying
to
eliminate
the
need
of
having
to
explain
things
in
help
text
if
possible.
Some
of
the
things
right.
C
B
Change
right,
I
think
the
help
text
yeah,
let
me
put,
I
think,
the
help
text
works
with
either.
Okay
display.
Okay
and
you
know
once
we
see
them
together,
they
may
be
fine-tuning
or
something
but
but
it
would
be,
it
would
make
sense
out
of
the
box
with
this,
but
I
I
pretty
strongly
think
help
text
will
be
beneficial
even
when
5077
is
in
place.
Sure.
C
Go
ahead,
sorry
go
ahead.
Well,
my
question
is
about
this
deta
pals
element
and-
and
I
erased
this
earlier
in
the
issue
which
is
my
only
concern,
is:
is
this
a
a
a
way
we
want
to
move
forward
with
this
kind
of
help
text
like
if
we're
doing
this
on
other
pages,
will
we
be
doing
it
the
same
way?
A
We
already
have
help
text,
we
have
free
floating,
I
should
say
so,
not
within
any
field
set
or
details
element
in
other
pages,
but
that
text
is
like
one
line
long
right,
so
it
becomes
an
issue
only
on
mobile,
maybe
where
you
would
want
to
sort
of
like
collapse.
It
collapse
it,
but
I
can
only
think,
like
the
other,
the
other
place
that
I
can
think
needs
lengthy
help
text
is
the
roles
order
thing
which
has
not
as
much
optics
but
still
considerable,
and
there
is
an
issue
for
it.
A
I
don't
have
it
with
like
out
of
my
top
of
my
head
now
so
yeah
roles
and
maybe
then
permissions
exactly
right.
Those
roles
and
permissions
to
explain
how
how
things
work
so
yeah
yeah.
We
could
reuse
that
pattern
to
sort
of
like
collapse
text
for
those
that
do
not
need
it
out
there,
and
my
assumption
is
that
we'll
only
use
it
in
really
confusing
pages
that
you
know.
Maybe
we
do
user
studies
or
from
feedback
from
users
that
things
are
confusing.
A
C
A
C
C
Yeah,
I
will
say:
does
anybody
else
feel
like
it
just
looks
a
little
bigger
it?
I
think
it
almost
feels
like
the
the
ad
layout
button
starts
to
disappear,
because
the
help
grabs
my
attention
and
it
almost
feels
like
it-
should
be
the
opposite
that
my
attention
should
be
directed
to
the
ad
layout
and
the
help
should
be
kind
of
a
little
subtler.
If
I
need
it
yeah.
This
is
my.
C
A
My
other
my
other
comment
as
a
feedback
is
that
just
help
doesn't
like
as
a
user
experience
or
journey.
I
see
that
I
expanded.
Oh,
this
explains
how
layouts
work,
but
I
already
know
that
then
I
close
it
collapse
it
again.
So
maybe,
instead
of
just
help,
you
say
actually
sort
of
like
two
or
three
words
to
say
what
does
the
ordering
of
layouts
in
this
page
mean
or
something
like
that,
which
basically
explains
what?
If
people
click
on
that,
then
what
are
they
gonna
see?
A
What
what
help
text
are
they
going
to
see
about?
That's
my
only
feedback
but
yeah
good
point,
though
team.
That's
the
default!
The
default
style
that
we
use
for
field
sets
right.
B
Yeah,
maybe
I
could
make
a
request
for
folks,
I'm
I'm
sympathetic
amenable
to
the
point
greg
just
raised.
That
help
is
not
as
to
the
point
as
how
layouts
work
or
something
like
that,
and
so
could
I
maybe
ask
people
to
post
in
the
issue,
suggestions
for
what
that
wording
should
be.
C
Yeah
and
if
we
end
up
doing
something
like
this
on
three
different
pages,
there
should
be
something
consistent
about
them
like
it
could
be
help
colon
with
a
description
or
yes,
exactly
yeah
or
it
might
be
a
color
or
something.
But
you
know
I
right.
I
would
like
some
consistency
or
something
you
know.
If
we
have
this
on
the
rolls
page
as
well,
there
should
be
something
about
it
that
make
them
similar
more.
What
that
is.
D
C
A
C
So
that
sounds
like
a
different
issue,
because
this
is
affect
other
pages,
and
but
I
agree
that
that
another
way
to
solve
the
problem
I
raised
would
be
to
just
have
ad
layouts
stand
out
a
little
bit
more
and,
to
be
honest,
I
feel
like
that.
Those
links-
sometimes
I
you
know
it
might
not-
the
problem-
might
not
be
with
the
help
text.
The
problem
might
be
with
the
action
link
with
the
action
link.
Just
never
was
that
prominent
and
it
should
have
been
more
prominent
even
without.
A
The
help
yeah
the
other
thing,
if,
if
we
are
hesitant
to
change
those
and
make
them,
if
it's
considered
a
radical
change,
then
maybe
we
can
tone
down
the
help
thing.
So
it
can
be
great
text
in
this
specific
like
it's
not
if
we
make
this
specific
purpose
details
element,
so
it's
it's.
It
has
a
different
class
of
help
and
then
it
has
gray
text
or
something
that
tones
it
down.
That
would
solve
the
issue
of
prominence
and
maybe
smaller
smaller
heading
text
as
well,
but
yeah.
C
Okay,
well,
it
looks
like
other
people
are
showing
up
for
the
next
meeting,
so
should
we
we
should
wrap
this
one
up,
yeah,
let's
wrap
it
up.
Okay,
thanks
everybody,
we're
gonna,
end
the
design,
ux
meeting
and
get
ready
for
the
dev
meeting.
The
meeting
yep
thanks.