►
From YouTube: Backdrop Design/UX - 2021/10/07
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
Hello,
everybody.
This
is
the
weekly
bachelor
of
design
and
ux
meeting
it's
october.
It's
thursday
october,
the
7th.
Before
we
start
the
meeting,
I'm
gonna
do
what
we
usually
do.
I'm
gonna
introduce
myself
and
then
go
around
the
room
allowing
everyone
to
do
so.
So
my
name
is
greg.
I'm
joining
from
greece
and
I'm
interested
in
helping
move
forward.
Many
ux
and
design
meetings
in
the
sorry
issues
in
the
queue
I'm
gonna
pass
on
to
robert.
C
Yeah,
as
usual,
a
bit
frozen
right
now
been
busy
making
some
videos
about
backdrop
and
yeah
just
keeping
busy
so
looking
forward
to
talking
about
priorities
for
the
next
release
in
our
in
our
dev
dev
meeting
later
today,.
D
Joseph
hi,
I'm
joseph
I'm,
a
backend
developer
from
las
vegas
nevada
and
I've
been
working
on
actually
fixing
bugs
in
about
the
reference
module
in
the
display.
Suite
module
hopefully
get
those
closer
to
stable,
so
yeah
and
survivor.
E
C
Okay,
well,
that's
everybody!
We,
I
posted
an
agenda.
I
don't
have
anything
specific
on
it
today.
Let's
look
at
it.
C
Yeah
the
agenda's
very
empty,
so
let's
just
sort
of
open
the
floor.
We
we
right
before
the
meeting
we
were
talking
about
in
the
spirit
of
planning
for
the
next
release
we
could
be.
C
We
could
talk
about
the
idea,
which
is
all
it
is
at
this
stage
of
adding
a
new
themed
background,
a
new
core
theme,
but
I
think
before
we
do
that,
let's
see
if
we
have
some
other
smaller
issues
that
we
could
get
out
of
the
way
and
then
we
could
switch
over
and
maybe
talk
about
that
one
because
I
think
that's
a
big
one.
B
Sure-
and
it's
really
more
of
a
documentation
issue,
it's
issue
number
5232,
which
is
just
question
about
documentation.
The
the
for
the
theme
function,
the
current
documentation.
Basically,
s
discourages
using
the
theme
function
directly
says.
Instead,
we
should
create
a
array
and
use
backdrop
render,
but
there's
about
400
500
calls
to
theme
currently
in
codebase,
and
so
I'm
just
wondering
if
we
should
bow
to
current
practice
and
remove
that
discouragement
from
the
documentation
or,
conversely,
if
it's
something
we
seriously
want
to
try
to
do.
A
Yeah,
so
I'm
I'm
sort
of
like
responsible
for
quite
a
few
of
those
400-plus
whatever,
and
the
reason
is
because,
when
I
started
coding,
I
just
sort
of
like
was
looking
through
code
to
see
how
things
are
done,
and
this
is
what
other
people
have
done
before.
So
I
just
mostly
copied
what
was
done
before
me.
I
was
not
aware
of
this
sort
of
like
advice
against
using
the
theme
function
directly
before
you
mentioned
it
robert,
and
I
would
like
to
understand
the
reasoning
behind
it.
A
C
I
have
no
objection
to
talking
about
this
right
now.
However.
Well
it
okay,
it
is
a
theme
function.
It
seems
like
it
might
be
a
better
topic
for
the
the
dev
yeah
yeah,
but
we
could
talk.
I
mean
if,
if
people
have
thoughts
or
opinions
on
it
now,
it's
not
like
we
have
a
full
agenda,
so
people
should
go
ahead,
otherwise,
robert
you
might
want
to
bring
that
up
again
because
there
might
you
know,
nate
or
somebody
might
be
more
equipped
to
talk
about
this
who's.
Not
here.
A
I'll
do
that
yeah,
it
might
be
a
performance
issue.
If
it's
a
performance
performance
issue,
then
then
it
might
be
really
worth
conforming
to
what
the
the
advice
says:
yeah
what
I've
done
while
we
were
discussing
that
is
I
I
went
to
the
issue
queue
and
filtered
it,
because
we
we
have
a
specific
label
for
design
related
issues
and
there's
like
85
of
them
currently
open
in
in
the
queue
we
can.
We
can
grab
and
discuss
any
of
those
if
we
feel
that
we
don't
have
anything
else
to
discuss.
C
Well,
we
could,
I
mean
we
do
have
the
theme
thing
we
have
so
two
weeks
ago
we
talked
about
this
front
page
issue
and
I
don't
think
we
need
to
talk
about
that
again
so
soon,
because
no
there
hasn't
been
any
progress
since
that
meeting.
Maybe
it's
is
there
anything
else,
though.
That's
that's
sort
of
hung
up.
People
have
been
working
on
recently.
A
There
were
quite
a
few
that
I
worked
on
and
reviewed
recently
and
then
this
is
not
just
a
design
meeting,
it's
a
ux
meeting
as
well.
So
the
the
85
issues
that
I
mentioned
are
just
the
ones
tied
with
design.
We
don't
have
a
label.
We
just
have
a
ux
brackety
thing
for
the
title
for
ux
and
there's.
I
guess
I'm
imagining
hundreds
of
issues
that
we
can
discuss
with
related
to
ux
should
I
may
I
suggest,
because
it
does
seem
that
the
the
theme
sort
of
like
discussion
might
take
a
while.
C
Queue
sure
I'll
just
you
know,
I
encourage
other
people
to
think
about
this.
One
of
the
things
I've
been
trying
to
do
lately
for
these
meetings
is
just
sort
of
look
through
the
issue
and
find
an
issue,
a
design
issue
that
or
a
ux
issue
that
I
care
about
and
be
prepared
to
talk
about
it
at
the
meeting,
and
I
just
didn't
have
a
chance
this
week.
So
I
don't.
C
C
I
found
it
already,
it's
51.75,
so
I
opened
this
issue
back
in
late
august
and
my
motivation,
my
personal
motivation,
although
there
are
others,
other
good
arguments,
was
just
sort
of
ongoing
frustration
that
we
can't
come
up
with
any
kind
of
consensus
on
how
to
fix
css
problems
and
bases,
and
I
feel
like
basis
is
flawed
and
one
one
alternative
would
be
to
to
to
just
propose
a
new
theme
that
we,
where
we
either
you
know,
fix
a
lot
of
these
problems.
C
In
addition,
you
know
to
maybe
giving
it
a
new
style,
but
also
possibly
it
might
be
easier
to
build
something
into
a
new
theme.
I'm
not
quite
sure
what
that
would
be
some
ideas
about
how
to
keep
it
up
to
date.
Anyways.
C
There
are
other
good
reasons
to
enter
a
new
theme
just
because,
first
of
all
it
you
know
the
basis
is
what
five
six
years
old.
Now
it's
been
there
since
the
the
release
of
backdrop
right
and-
and
you
know
part
of
I
mean-
I
think,
any
sort
of
big
visual
change
to
backdrop.
C
Would
be
a
good
sort
of
move
to
just
sort
of
show,
progress
and
and
show
that
backdrop
is
moving
along
so
having
it
look
different
now
than
it
did
five
years
ago,
especially
because
we're
not
going
to
have
a
new
major
release
for
another
four
years
or
three
years
really.
Another
four
years,
I
think,
is
what
our
commitment.
D
C
A
I
would
like
to
first
because
you
said
that
basis
is
flow
that
might
hurt
the
feelings
of
the
creators
of
the
theme.
Of
course
it's
flawed.
I
would
like
to
correct
certain
things
that
you
just
said,
or
or
sort
of
like
clarify.
First
of
all,
when
basis
was
created,
of
course,
there
were
many
things
that
could
have
been
opinionated
about
it,
or
there
would
be
things
that
we
didn't
anticipate
to
be
added
in
core,
so
to
make
bases
account
for
these
right.
So
the
reason
is
not
that
we
cannot
fix
bases.
A
There
is
sorry.
The
problem
is
not
that
we
cannot
fix
bases
it's
that
we
cannot
find
a
suitable
way
to
fix
bases
in
a
way
that
is
backwards
compatible
just
to
clarify
things.
So
that's
the
issue
there
and
and
as
tin
mentioned,
there's
quite
often
mentioned
in
the
zulipchat
that
that
the
base
system
is
outdated.
As
you
mentioned,
and
I
and
I
I
find
it
like
a
good
starter
thing,
but
but
I
agree
that
people
that
that
work
more
with
building
sites
may
find
it
where
they
might
be
bored
of
it.
A
I
guess
they
want
they're.
Looking
for
something
new,
what
I
would
like
to
say
to
that
and
then
I'll
pass
it
to
someone
else
is
that
it
might
be
worth
if
we
decide
to
go
ahead
and
do
that
to
actually
look
at
the
things
that
are
popular
for
d7
right
now
and
see
if
we
can
either
port
something
that
looks
like
it
unless
that's
not
like.
I
know
that
moving
from
d7
to
backdrop
means
that
you
you're
going
to
have
to
adjust
your
theme,
because
you
have
to
account
for
layouts
but
yeah.
A
B
I
just
so
looking
at
the
comments.
One
of
the
points
against
doing
it
was
that,
if
we
add
a
bunch
of
new
themes
over
time,
we'll
stuff
the
theme
directory,
but
it
seems
like
adding
a
new
theme
every
four
or
five
years
that
rate
of
stuffing
is
pretty
low.
I
mean
lots
of
other
things
are
going
to
happen
over
the
time
scale
of
in
10
years
we
might
have
two
or
three
new
themes,
total.
A
Sorry
I'll
just
take
the
opportunity
to
just
mention
one
more
thing
mentioned
it
offline
before,
but
it's
worth
mentioning,
we
have
a
meta
issue
which
is
3193,
which
is
about
promoting
certain
projects,
country
projects
from
the
project
browser.
So
if
the
the
addition
of
the
new
theme
in
core
it's
sort
of
like
pushed
back
because
of
overhead,
we
could
consider
doing
that
like
porting,
a
a
or
helping
make
it
sort
of
like
an
official
semi
official
sort
of
like
initiative,
start
things
in
contrib
and
then
request
that
this
is
promoted.
A
E
I
was
wondering
what
is
the
most
up-to-date
usable
theme
that
would
be
used
in
place
of
basis
now
as
an
option
if
somebody's
basis
is
going
to
be
going
away
before
too
long.
And
what
would
what
would
be
a
good
choice.
C
Yeah,
I
don't
either
we
could
look
up
like
what
the
most
popular
theme
for
usage
is,
but
I'm
not
even
sure
that
that
would
help
us
much.
I
don't
think
the
numbers
are
pretty
low,
are
very
high
on
any
theme.
C
I
don't
know,
we
don't
don't
have
usage
stats
by
type,
so
I
just
have
to
scr
I'm
sort
of
scrolling
through
the
projects.
To
look
for
the
first
theme
that
I
recognize
yeah,
but
I
think
a
lot
of
people
do
custom
themes.
I
I
don't
know
that.
There's
one
theme
in
our
current
setup
I
mean,
I
think
we
would.
We
would
more
likely
port
something
from
backdrop
or
start
fresh.
A
I
have
a
feeling
that
most
of
the
most
popular
themes
in
d7
are
starter
kit
themes
which
are
not
I'm
not
sure.
If
we're
looking
for
something
like
that,
like
zen
or
omega,
which
are
basically,
I
think,
all
the.
A
Let
me
just
put
my
thoughts
together,
so
we
are
looking
like
the
the
same
way
that
we
the
same
reasons
that
we
that
that
led
to
adding
bases
to
core
should
apply
here.
I
think,
and
the
the
most
important
of
these
were
that
we
wanted
once
the
installation
finishes
to
have
to
have
the
users
have
the
feeling
that
they
see
something
of
semi-complete
site
or
something
that
they
can
start
working
with,
and
these
base
starter
things
in
d7,
they're,
the
opposite
of
that
they're
just
blank.
A
So
maybe
we
should
look
at
the
most
popular
theme
in
d7.
That
is
not
a
starter
team
yeah.
That
was
my
point.
E
It
seems
that,
since
the
layout
and
design
is
separated
from
the
the
graphical
aspect
of
the
theme,
that
upgrading
from
one
thing
to
another
is
much
more
straightforward
in
background.
You
know
why
it
doesn't
really
matter.
It's
just
trying
to
give
you
different
colors
and
different
options
for
color.
C
Sure,
well,
I
I
I
mean
I
think
it's
possible
to
do
something
in
between
the
other
thing.
The
other
question
we
would
have
to
answer
is:
if,
if
we
added
a
new
theme,
would
it
would
we
want
to
make
it
the
default
theme
which
so,
if
we
added
a
starter,
we
could
add
a
starter
theme
to
core.
I'm
not
suggesting
that,
but
I'm
saying
we
could,
if
we
left
basis
as
the
default
theme
and
then
had
a
starter
core,
I
don't
know
that
we
need
to
do
a
starter
theme.
C
I
don't,
I
think
anybody
that
needs
a
starter
theme
can
just
as
easily
get
it
from
contrab.
I
think
the
event
you
know
the
audience
we're
playing
to
with
core
themes
are
our
beginner
users
who
aren't
looking
for
starter
things,
so
I
would
be
in
favor
of
doing
something
that
looks
good
and-
and
I
would
be,
I
would
probably
be
in
favor-
of
making
it
the
new
default
theme
just
as
an
opportunity
to
sort
of
change.
The
way
backdrop
looks
out
of
the
box.
A
The
first
one
is
bootstrap,
which
is
basically
not
a
theme
theme,
it's
sort
of
like
something
that
allows
you
to
use
the
bootstrap
for
your
things
and
when
I
say
theme
team,
I
mean
theme
according
to
the
what
I
mentioned
before,
like
something
that
could
look
ready
and
then
the
second
most
popular
is
at
minimal,
which
I
sort
of
like
mentioned
offline.
A
So
that's
that's
a
an
admin
theme
and
what
I
was
mentioning
offline
was
that
maybe
we
should
look
into
revamping
seven
as
well,
but
then
you
have
zen
omega
adaptive
theme
yeah.
They
all
seem
to
be
just,
as
I
said,
starter
things
instead
of
this,
the
the
two
that
I
don't
see
as
starter
themes
are
tau,
I
think,
and
corporate
clean
and
right
after
that,
it's
the
gene
admin
theme,
which
is
gaining
a
lot
of
traction
in
in
drupal,
8
and
beyond
or
triple
9.
I
think
it's
based
on
power.
A
C
So
the
thing
about
getting
a
new
theme
in
decor
is
I
envision.
Is
it
a
pretty
big
project,
whether
it's
porting
well,
porting,
a
theme
from
drupal
might
be
a
little
bit
easier
in
the
sense,
primarily
in
that
we
wouldn't
have
to
engage
a
designer
like
somebody
could
do
it
that
didn't
necessarily
have
design
skills
but
just
had
theming
skills
or
even
coding,
skills
really
the.
C
But
if
we
created
you
know,
if
we
wanted
a
fresh
design,
then
we'd
have
to
also
engage
a
designer,
and
that's
all
pretty
big.
So
you
know
I
mean
one
of
before
we
get
to
too
far
into
the
discussion
of
whether
or
not
it's
a
good
idea.
We
should
be
even
thinking
about
how
big
of
a
project
is
it
and
is
it
possible,
you
know,
do
we
have
the
resources
or
it
seems
like
it
would
need
somebody
to
get
excited
about
it.
C
A
With
it
not
to
help
with
it
but
yeah,
I
seem
to
be
drawn
to
usability
ux
issues
in
core
and
that's
where
I
spend
most
of
my
time.
A
A
It
seems
to
be
very
popular,
so
there
are
some
themes
that
are
non-starter
non-admin
themes
that
we
could
pick
would
seem
to
be
popular
like
and
and
I'll
actually
check
usage
stats
for
those
things.
Just
to
so
we
have
a
a
rough
idea,
so
yeah
when
I
mentioned
dunlop,
that's
seven
and
a
half
thousand
users.
So
it's
not
one
of
the
you
know,
hundreds
of
thousands
of
sites,
it's
a
few
thousand
sites.
C
Yeah,
so
it
looks
like
in
terms
of
backdrop
the
the
most
popular
one
I'm
seeing
looking
at
the
list
is
corporate
kiss,
which
is
you
know.
I
I
think
it
has
the
advantage
of
being
a
somewhat
finished
theme,
that's
kind
of
flexible
and
and
looks
good,
but
you
know
the
the
stats
are
108
sites
using
it.
So
that's
in
bootstrap
lite
is
at
174,
oh
okay,
which
actually
makes
sense.
I
didn't
see
that
but
you're
right
in
bootstrap
lite
is
really
well.
C
B
A
Yeah
can
I
can
I
because,
while
we're
talking,
I'm
just
using
looking
at
usage
stats,
so
you
mentioned
about
100
sites
using
that
most
popular
theme
for
backdrop
out
of
2000
sites
that
we
have
and
then,
if
I'm
not
mistaken,
I
think
the
drupal
7
usage
is
like
half
a
million
or
a
bit.
I
don't
know
600
000
and
then
the
most
popular
non-admin
themes
are
in
the
less
than
ten
thousand
like
nine
and
a
half
thousand
or
seven
and
a
half
thousand.
C
No,
I
would
say
the
opposite
that
it
could
mean
that
a
lot
of
people
are
using
the
default
team
because
they're
not
using
contrib
themes.
Well,
oh
yes,
that
or
some
theming
or.
A
C
It
would,
but
I
think
my
experience
is
that
it
seems
like
most
people
and
from
anecdotal
evidence
only.
It
seems
like
I
hear
a
lot
of
people
just
some
theming
bases,
so
the
basis
doesn't
show
up
as
a
project
in
the
project
stats.
So
we
don't
know,
but
that
that's
something
telemetry
could
help
us
with
yeah.
A
Telemetry
will
help
us
with
that,
but
on
on
drupal
land,
the
the
issue
that
they
have
is
that
disabled
themes
can
be
used
as
base
teams,
so
these
will
not
be
reported
if
you
don't
have
the
checkbox.
That
says
also
check
for
updates
for
disabled
projects.
So
this
is
something
that
dilutes
the
stats.
We
should
keep
that
in
mind.
Is
it
that's
true
for
us
as
well
that
you
can
sub
theme
a
disabled
theme,
because
yeah.
D
So
current,
currently
the
way
themes
don't
have
themes,
can't
create
database
tables
and
they
can't
create
config
files.
So
they
don't
have
an
installation
system,
so
essentially
the
the
enabled
and
disabled
is
just
does
it
show
up
at
the
top
or
on
the
bottom
of
that
list
on
the
themes
page.
C
Well,
there
doesn't
seem
to
be
anybody
at
this
meeting.
That's
opposed
to
the
idea.
On
the
other
hand,
I
think
there's
a
lot
of
questions
that
we'd
have
to
answer
about
it,
including
who's
who
wants
to
work
on
it,
but
I
I
I
want
to
say
some
is
the
person
who's
whined
the
most,
and
I
want
to
be
clear
what
you
know
when
I
say
I
complain
about
basis
a
lot.
That's
not
a
dig
on
basis.
I
think
basis
is
a
great
theme.
That's
not
any
theme
is
going
to
have
problems.
C
You
are
exactly
on
the
point,
the
gregory,
that
the
problem
with
basis
isn't
really
basis.
It's
that
we
don't
have
a
way
to
update
it
without
breaking
existing
sites.
Otherwise
basis
would
be
I'd,
be
happy
to
improve
basis
if
we
could
and-
and
frankly
I
don't
it's
not.
I
I
don't
think
basis-
looks
that
you
know
looks
bad
or
that
dated
myself
when
I
I
do,
but
I
do
think
we
benefit
from
a
fresh
look.
You
know
just
because.
D
C
My
last
point,
and
then
I'll,
let
you
know,
is
that
your
idea,
also
about
just
I
would
be
content
with
like
a
promoted
theme
like,
even
if
it
wasn't
in
core.
If
we
picked
one
that
we
said
that
we
really
encourage
people
to
use
as
a
viable
alternative
to
me.
That
would
also
be
a
good
solution
to
our
existing
problem.
C
A
No,
no
one
thing
that
I
wanted
to
mention
is
that
most
of
the
things
that
I
find
appealing
personally
are
d8
and,
above
so
trying
to
port
this
like
oliveira,
for
example.
I
really
like
it
and
it's
not
that
I,
like
it
visually
or
the
style
of
it.
I
know
that
there's
a
bit
there's
been
a
lot
of
work,
a
lot
of
thought
behind
it,
a
lot
of
usability
tests
and
user
studies
that
have
led
there,
and
this
is
work
that
we
can
leverage.
A
The
problem
is
that
everything
has
been
built
in
twig
and
it's
it
will
be
a
lot
of
work
or
I'm
imagining.
It
will
be
quite
somewhere
to
sort
of
like
port,
all
all
the
d7
themes,
at
least
the
ones
that
I
skimmed
through
now
in
the
list.
They
seem
a
bit
dated
and
a
bit
I
don't
know
decayed
their
style
seems
like
a
decade
old
or
something
yeah.
C
I
get
the
issue
with
twig,
but
I
would
think
that
porting,
a
drupal
8
theme
would
be
a
lot
easier
easier
than
putting
a
droop
light
module
yeah.
Just
because
yeah
supporting
you
know
the
tweak
files.
Aren't
that
different
from
you
know.
I
mean
that
you
know
you
know
I
feel
like
I
could.
I
have
the
skills
where
I
could.
It
would
maybe
take
a
fair
amount
of
work,
but
I
would
at
least
understand
twig
and
be
able
to
translate
those
in
a
better
way
than
you
know
like
trying
to
translate
a
module
which.
A
A
D
C
Well,
probably
the
best
we
could
do
is
come
to
some
sort
of
agreement
that
it
would
be
a
good
idea
to
add
a
new
core
theme
and
then
the
next
step
would
be
to
just
sort
of
promote
that
and
see.
If
we
could
get
somebody
on
board.
I
mean
this
might
be
the
kind
of
thing
that
we
could
create
an
initiative
for,
but
still
one
of
the
requirements
for
initiative
is
somebody
that's
willing
to
delete
it.
So.
A
One
of
the
things
that
I
would
like
to
dis
ask
to
discuss
and
get
opinions
is
the
the
hybrid
idea.
So
this
was
sort
of
mentioned
as
a
solution
to
the
problem
is
that
we
cannot
touch
bases
as
it
is,
but
what,
if
we
sort
of
like
created
something
that
is
basis
but
not
basis?
I
don't
know
basis
too
or
next,
so
we
hide
bases,
we
still
leave
it
there
for
all
sites
and
if
they
are
sub
theming
it
it's
still
going
to
be
there.
A
A
C
Well
sure:
sort
of
building
off
that
and
making
the
idea
one.
C
If
we
wanted
to,
we
could
add
a
new
version
of
basis
to
core
and
hide
the
old
version,
like
sort
of
like
what
you're
talking
about
and
that
would
dramatically
reduce
the
the
work
involved.
You
know,
then
we
could
fix
all
the
problems
in
the
new
version,
but
well.
C
Well,
yeah,
but
that's
the
same
with
your
hybrid
I'm,
I'm
sort
of
building
off
your
hybrid
idea,
yeah
yeah.
I
mean
there
isn't
any
scenario
that
I
mean
the
whole
existing
sites
benefiting
from
these
fixes.
It's
sort
of
been
written
off
the
table
for
this
discussion
right.
If
we
could
do
that,
then
we
wouldn't
be
having
this
discussion
right.
We
were
we're
kind
of
saying
that
we
don't
know
any
way
to
to
improve
base
to
improve
basis
and
you
know
not
break
old
sites
but
also
to
any
extent
to
give
them
the
benefits.
C
But
I
don't
that's
sort
of
been
an
accepted
limitation,
in
my
view,
unless
I
mean
we
could
revisit
the
idea
of
how
do
we
there
are
some
viable
light.
There
are
some
workable
ideas
about
a
fixing
basis
in
a
backward
compatible
way.
The
problem
isn't
that
there
isn't
a
solution.
The
problem
is,
we
can't
unify
on
anything.
A
B
Well,
I
do
go
ahead.
There's
there
is
a
contrib
version
of
basis
that
is
expensive,
that
it's
documented
to
say
it's
used
to
create
experimental
features,
may
add
features.
Does
that
play
a
role
in
this
kind
of
big
big
picture.
C
A
But
it
could
be
yeah,
and
the
other
thing
is
that
this
is
a
name
spacing
issue
or,
I
wouldn't
say
an
issue
or
it's
based
on
name
spacing.
So
basically,
if
you
install
that
theme,
because
its
name
is
basis,
it
will
completely
override,
as
in
take
precedence
over
the
core
theme,
so
because,
because
if
you
add
a
custom
or
contrib
theme
or
module
or
layout,
that
has
the
same
name
as
the
core
ones,
that
can
the
contributing
the
custom
ones
take
precedence.
A
C
Certainly,
we
could
use
a
a
as
we've
said,
a
contrib
theme,
and
it
could
be
the
basis
contrib
theme
to
fix
these
problems.
But
again
that
doesn't
really
address
the
the
question
of
having
like
these
things
fixed
in
court.
Now
we
we,
you
know,
we
could
do
that
and
we
could
promote
that
or
we
could
go.
C
You
know
gregory
your
idea,
I'm
still
thinking
about
of
some
kind
of
hybrid
where,
where
we're
not
we're
kind
of
replacing
the
core
theme
but
keeping
the
old
one
just
hidden
like
isn't
something
I
thought
about,
and
that
could
either
be
kind
of
a
sub
theme
or
it
could
be
just
a
you
know
a
fork
in
a
sense
of
basis
right
where
we
just
start
over
with
basis.
A
Again,
we
can
make
it
ask:
we
can
make
it
a
task
for
2.0
if
we
have
to
do
not
completely
if
we
don't
build
any
completely
new
theme
to
basically
ditch
the
old
basis
theme
and
replace
it
with
with
the
full-fledged
overwritten,
whatever
we
call
the
new
version
of
it.
C
Joseph
does
with
that,
without,
like
your
opinion,
would
that
work
to
have
like
just
a
sub
theme
of
basis
and
then
in
a
sense
but
hide
the
old
basis,
so
we
were
using
that
kind
of
as
the
starter,
so.
D
So
there's
this
file
in
basis
called
skin.css
that
is
essentially
all
of
the
components
folder
in
one
file
and
it
overrides
the
component
folder.
And
if
you
overwrite
the
skin.css
file
and
like
or
if
you,
then
it
completely
wipes
everything
out,
and
I
think
that
because
of
the
because,
essentially
all
the
styles
are
duplicated
like
this.
D
B
A
F
A
We
could
ask
what
wes
thinks
about
it
because
basically
sure
he
might
not
be
around,
but
he's
always
like
it's
time
that
we
think
him
he's
very
responsive.
D
C
Well,
yeah,
okay,
I
have
to
think
more
about
there.
There
seems
like
there
might
what
about
this
idea
if
we
just
replaced
if
we
had
a
new
core
theme
and
hid
basis,
so
that
people
would
be
able
to
continue
to
use
it,
but
not
selected,
they
wouldn't
obviously
be
able
to
select.
Is
that
practical?
I
don't
know
what
and
I'm
not
sure
if
that's
a
real
advantage
to
just
if
we're
going
to
add
a
new
theme
anyways,
you
know,
I
don't
know
hiding
the
old
basis
is
necessary.
B
C
The
goal
would
be
just
to
get
a
new,
but
it's
still
some
interesting
thoughts
came
up
so
well
we're
running
out
of
time.
I
think
we
should
go
ahead
and
wrap
wrap
up.
Actually
what
I
would
like
to
do
is
this
would
be
also
a
great
backdrop,
live
topic
yeah,
and
it
might
be
something
we
could
coax
wes
into
participating.
In
fact,
we
could
tell
him
ask
him
when
his
available
time
slot
is
and
then
schedule
it
when
he's
available.
A
C
That
he
has
chimed
in
on
that
discussion
at
all,
so
that
would
be
a
great
opportunity
to
get
him
like
and
discuss
this
lives
right.
I
could
see
a
topic
on
the
schedule.
That
was
something
like
the
future
of
basis
or
new
contrib
theme
yeah,
so
it
kind
of
leaves
both
of
those
options
open
like
either.
C
How
do
we,
how
do
we
figure
out
a
way
forward
with
drupal
or
or
with
back
with
basis,
or
how
do
we
come
up
with
an
alternative
as
a
topic
and
then
let
the
discussion
go
whichever
way
it
goes.
C
So
does
anybody
want
to
host
that
discussion?
All
you
have
to
do
is
facilitate
okay.
C
I
I
don't
want
I
I
I
could
put
about
10
items
on
the
schedule
to
facilitate,
but
I
don't
want
to
do
that
so
I'll
think
about
it,
though
this
might
be
an
important
enough
one:
okay,
let's,
let's
go
ahead
and
end
this
meeting
and
we
have
a
big
dev
meet.