►
From YouTube: Backdrop Design + UX - Feb 24th 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
We
have
a
couple
of
items
on
the
agenda,
but
before
we
get
to
that,
I'd
like
to
go
around
and
do
some
quick
introductions
if
everyone
could
share
what
your
name
is
where
you're
from
and
anything
else
you'd
like
to
share
with
the
group,
you
can
go
ahead
and
do
that
and
let's
do
popcorn
so
I'll
go
first
and
then
I'll
call
on
the
next
person
and
then
that
person,
the
next
person.
My
name
is
chan
lampton.
A
I
am
joining
from
oakland
california,
where
it
is
sunny
and
beautiful,
but
unusually
cold
here,
but
my
wonderful
husband
installed
heat
pumps
in
our
house,
and
it
is
finally
nice
and
warm
inside.
So
I'm
very
excited
all
right.
Robert.
Let's
go
next.
B
I'm
robert
line
bud
folder
on
the
internet,
coming
to
you
from
altadena
california,
where
it
is
also
sunny
cool.
D
I'm
greg
I'm
joining
from
greece
genuinely
interested
in
anything
related
to
backdrop
in
any
way
that
can
help.
Let's
go
with
irena.
E
A
That's
great,
thank
you,
everybody
for
our
discussion
items
this
week.
We
have
two
items
about
the
layout
administration
page.
The
first
one
is
five:
zero,
seven
seven.
This
is
something
that
we
were
working
on
before
the
last
minor
release
about
how
to
make
the
layout
page
make
a
little
bit
more
sense
to
people
in
particular.
The
proposed
solution
separates
the
standalone
pages
from
the
pages
that
override
other
pages,
and
we
tried
to
do
that
with
a
visual
distinction,
as
well
as
some
minor
descriptions
about
what
they
were.
A
That
pull
request
is
in
a
needs.
Code
review
needs
testing
state.
I
don't
think
I
can
code
review
it
because
I
worked
on
it
and
I
don't
think
robert
can
code
review
it
because
he
worked
on
it.
So
the
two
of
us
are
like
very
excited
about
moving
it
forward.
I
can't
really
help
anymore,
so
I'll.
A
Ask
anyone
else
who
feels
confident
in
doing
code
review
greg's
really
good
at
that.
Thank
you
to
have
a
look
at
that
and
then
anyone
else
who
wants
to
see
what
we're
doing
to
that
page
could
go
ahead
and
test
it
it.
I
think
it
looks
really
good
and
then
robert
brought
up
our
related
issue.
Do
you
want
to
give
us
an
update
on
55
11.
B
On
the
confirmation
page
for
deleting
the
layout
that
we
give
some
warnings
and
we
also
provide
a
button
to
allow
the
user
to
disable
it
rather
than
deleting
it
since
and
that's
also
problematic,
and
because,
if
we
delete
it
and
it
deletes
a
layout
created
page,
that
also
could
cause
problems.
If
that
page
were
happening
to
be
one
of
the
special
pages
like
the
home
page
of
the
404
403
page.
B
So
all
of
that
stuff
relating
to
the
deletion
was
broken
out
into
this
new
issue
55-11,
and
so
now
it
has
a
pr
and
so
like
people
to
test
it.
But
because
there's
some
human
interface
issues
and
user
interface
experience
issues.
I
wanted
to
get
feedback
and
in
particular,
for
if
the
path
is,
if,
if
it's
a
layout
created
page
and
that
page
is
being
used
as
the
home,
403
or
404
pages,
we
probably
don't
want
the
person
to
be
allowed
to
delete
it,
because
that
would
cause
very
bad
problems.
B
The
next
time
one
of
those
pages
is
brought
up.
So
I
was
just
disabling
the
delete
and
disable
buttons,
but
still
leaving
them
visible
and
just
my
question
was:
should
we
do
that
or
should
I
actually
remove
the
buttons.
D
We
have
a
another
use
case
in
core
where
we
have
this
there's
a
bit
button
disabled
until
we
select
something
and
then
it
gets
enabled,
and
actually
the
text
changes
as
well.
So
it
wouldn't
be.
I'm
not
saying
that
we
should
do
it,
but
it
wouldn't
be
a
pattern
that
we
haven't
used
before
is
all
I'm
saying.
A
Yeah,
I
think
my
concern
is
that
we,
you
know
right
now,
if
you're
using
a
node
for
any
of
those
pages,
you're
allowed
to
delete
the
node,
and
I
think
that
we
have
behaviors.
A
I
don't
know
what
the
home
page,
but
I
think
for
403
and
404.
We
have
a
fallback
behavior
where
it
says.
Does
the
page
exist,
if
not
return
to
system
403
system
404?
I
don't
know
if
we
need
something
like
that
for
the
home
page,
it's
more
important.
Oh
robert,
go
ahead.
B
Yeah
so
I
tested
this
with
the
layout
created
page
as
the
404
and
if
you
delete
it
and
then
you
call
for
a
non-existent
page,
you
get
a
white
screen
with
a
little
tiny
404
on
it.
So
you
you
do
get
a
404,
but
it's
a
pretty
user
unfriendly.
One.
A
Yeah,
that
sounds
like
not
the
system
404,
which
would
be
branded
with
your
site
information
interesting.
This
might
also
involve
follow-up
issues
morphologies
to
fix
some
of
this
other
stuff,
not
blocking
just
so
I'm
just
thinking
about
it.
Okay,
so
my
thought
is
that
there's
also
like
an
order
of
operations
thing
here
right
where
I
don't
think
we
want
to
have
somebody
like
not
be
able
to
delete
their
layout
override
of
the
404
page
like
they're,
going
to
need
to
know
how
to
do
that.
A
A
B
A
Yeah,
I
still
think
making
them
do
that
first
like
why
they
have
to
do
that
first,
like
can't
they
do
that
second
gonna
do
the
layout
and
then
go
to
the
thing.
I
don't
know
that
that
we
need
to
enforce
that.
I
think
it's
great,
that
it
has
the
message,
but
I'm
not
sure
that
we
need
to
disable
the
ability
to
perform
the
action,
especially
if
we
can
show
the
message
again
immediately
after
they've
deleted
the
page.
They
do
a.
A
If
we
could
say
hey,
this
is
the
system
404
page.
We
know
that
because
we
tested
it
now
set
some
submit
handler.
That'll
change
that
value
when
you
save
this
form.
So
it
says
like
this
is
a
system
404
page
when
you
delete
this,
that
will
be
reset
or
something
like
that
and
then
not
have
to
have
a
person
perform
the
action,
but
have
the
robot
perform
that
action
instead,.
A
Not
sure
that
needs
to
be
part
of
this
pr,
I
think
if
this
pr
were
just
to
set
the
messages
and
not
disable
the
buttons,
that
would
be
good
in
a
first
step.
I
think
we
could
then
follow
that
up
like.
I
don't
want
that
to
block
this
with
something:
that's
like
hey,
let's,
be
nicer
and
perform
these
actions
for
people.
D
Yeah
from
a
from
a
workflow
perspective,
what
I
would
do
is
keep
the
disable
the
delete
button,
but
have
it
read
as
danger
as
it
usually
is,
provide
the
disable
button,
which
is
an
option
and
explain
why
they
want
to
do
that,
it's
safer
and
then
a
confirmation
made
if
they
do
decide
to
delete
it.
Maybe
a
confirmation
message
that
says
your
404
and
403
have
been
reset.
The
system
defaults
go
and
change
them.
A
Yeah,
oh,
I
can
also
do
that
too.
If
you
want
more
voices
but
yeah,
I
love
the
fact
that
we're
adding
this
whole
set
of
delete
disabled
features
so
fantastic
with
nice,
helpful
text.
D
Yeah
by
the
way,
there
was
a
discussion
a
really
long
time
ago
in
drupal
land
of
discussion
or
suggestion
for
content.
Editors,
specifically
always
on
publish,
never
delete,
which
falls
into
that
category,
like
you
could
say,
always
always
disable
never
delete.
Unless
you
grow
like
a
really
big
large
list
of
layouts,
then
you
have
to
clean
up,
of
course,
but
yeah
the
safest,
the
safest,
is
disabled.
D
A
Okay,
next
on
the
agenda
is
the
contextual
links,
discussion.
C
Yeah,
so
I
was
working
with
some
people
yesterday
and
they
wanted
to
change
the
change,
the
site
logo,
but
we're
unable
to
figure
out
how
to
change
it
and
one
of
the.
But
one
of
the
first
thing
I
noticed
one
of
the
first
things
they
tried
was
to.
A
D
My
only
my
only
comment
on
this
specific
case
is:
how
often
does
someone
change
the
logo
of
the
site,
so
that
will
happen
once
twice
three
times,
but
when
it
comes
to
things
like
editing
blocks
or
the
layout
itself,
then
that's
a
different
story.
So
there's
a
potential
and
also
this
falls
into
the
80
20
thing,
which
is
very,
as
we
said,
arbitrary,
but
yeah.
I
I
I
doubt
that
there's
a
site
that
daily
or
weekly
changes
their
their
law,
no.
A
But
it
does
also
weigh
in
into
like
first
time
user
experience
where
it's
the
first
thing
people
want
to
do
and
if
it's
a
really
hard
thing
to
do,
it'll
sort
of
set
a
not
great
first
impression.
So
I
would
say
it's
probably
you
know,
100
of
sites
will
need
to
do
it
once
whether
they
do
it
again
is
iffy,
but
that
first
time
experience,
I
think,
is
important
to
consider
too.
C
Yeah
in
a
lot
of
a
lot
of
the
sites
that
the
a
lot
of
the
the
backdrop
sites
that
I
maintain
are
more
like
sites
for
friends
and
in
a
lot
of
these
cases,
I
set
up
a
site
on
the
server,
show
them
the
basics.
So
I'm
like
all
right,
have
fun.
Call
me
if
something
breaks
and
for
those
people
I
feel
like
having
like
they
would
never
like,
never
find
the
how
to
change
the
logo.
In
backdrop,.
A
Yeah,
I
think
I
think
the
header
block,
including
a
contextual
link,
to
locate
the
things
in
the
header
makes
sense.
I
think,
depend
you
know
the
the
site
name,
the
site
slogan.
We
even
have
a
slogan
anymore,.
D
B
A
A
Maybe
we
should
create
some
guidelines
for
people
to
know
when
it
would
be
useful
to
add,
contextual
links
to
blocks
or
not.
I
know
for
what
we
do
in
core
right
now.
They
appear
anywhere.
The
thing
itself
is
content
like
a
note
or
a
comment,
and
they
appear
on
blocks
where
it's
in
administrative
tasks
as
opposed
to
a
content
task
and
then
menus
linked
menu
settings.
A
So
it's
sort
of
like
there
aren't
any
rules,
but
there
are
patterns-
and
I
would
say
if
oh-
and
that
can
trip
modules
have
done
this
too,
like
node
queue,
adds
a
contextual
link
to
a
view
that
uses
a
node
queue
that
allows
you
to
edit
the
queue
directly
and
that
sort
of
sometimes
an
editorial
test,
and
sometimes
an
administrative
test,
depending
on
how
you've
configured
your
site
to
use
it.
A
So
there's
sort
of
sort
of
a
gray
area
there
as
to
like
who
those
links
are
for,
I
think
in
general
anytime.
We
think
it's
going
to
be
a
huge
time
saver
to
be
looking
at
the
thing
and
want
to
change
the
thing
you're
looking
at
and
have
a
link
that
goes
directly
to
that
thing.
It's
a
good
thing.
I
don't
know.
If
there's
a
scenario
I
can
think
of
where
there
would
be
too
many
contextual
links,
but
we
can
talk
about
that
when
we
get
there,
I
think,
for
now.
A
I
you
know
we
sort
of
were
erring
on
the
side
of
too
few.
My
opinion.
A
E
A
I
got
us
a
new
short-term
design
for
the
homepage,
and
this
is
done
by
nika
lorber,
who
did
the
design
for
the
current
homepage
and
said
hey.
We
have
this
need
to
throw
other
stuff
on
our
homepage
all
the
time
and
we
just
throw
it
above
the
header
and
it
looks
really
terrible.
A
Can
you
come
up
with
a
way
to
put
more
information
on
the
page,
and
she
came
up
with
this
in
like
an
hour
and
was
like
hey
here's
the
way
you
can
handle
you
know
if
you
need
to
add
blocks,
we
can
just
give
you
this
backdrop,
sort
of
style,
logo,
block
thing
where
you
can
throw
up
on
the
page,
and
she
said
you
can
adjust
if
you
have
one
or
two
or
three,
depending
on
how
many
you
have
that
it'll
work.
So
irene
is
short
term.
A
I
think
we
should
move
our
backdrop
live
event
into
one
of
these.
If
you
want
to
do
a
featured
site,
I
think
that
was
the
example
you
had
on
there
too.
That
would
be
fine.
My
preference
would
be
that
it'd
not
be
america's
best
boot
fitters,
but
we'll.
A
D
A
Good
yeah,
all
right
and
anything
else
we
want
to
throw
on
the
homepage.
We
can
use
this
style,
so
I'm
currently
well
working
on
doing
this
with
a
block
class,
so
that
anytime,
we
want
to
put
a
block
in
this
region
with
this
class
on
it.
It'll
get
this
style
added
to
it,
but
bigger
picture.
This
is
only
a
short
like
quick
fix
for
the
home
page.
A
I
did
also
reach
out
to
darius
garza
who's,
our
sort
of
brand
ambassador
brand
director
who
created
the
backdrop
brand
originally
and
asked
him
if
you
wanted
to
help
us
with
sort
of
a
larger
project
for
how
to
you
know,
re
imagine
backdrops
brand
today
as
compared
to
how
it
was
10
years
ago
or
whenever
we
started.
A
And
see
if
the
website
needed
an
aesthetic
update,
and
that
was
something
that
wasn't
in
the
forum
recently
and
people
are
talking
about
needing
an
update
and
he
said
that
he
was
interested,
so
we
haven't
moved
beyond
I'm
interested,
but
we
are
starting
to
move
forward
on
the
design
angle
of
things
and
branding.
I
guess,
more
importantly,
so
my
next
question
will
be
like
how
do
we
want
to
move
forward
with
this?
I
was
hoping
tim
would
be
here
for
this.
A
I
think
we
should
he's
a
fan
of
having
committees.
I.
A
Good
to
set
up
a
committee
of
people
who
can
work
with
the
designers
on
answering
the
questions
they
need
and
helping
choose
direction
for
this
stuff.
So
arena
I
was
thinking
if
you
wanted
to
be
on
that
committee.
That
would
be
a
really
great
place
for
you
to
help
sort
of
move
this
forward
and
help
us
land
and
something
we
think
all
right
turn
off.
My
screen
sharing.
A
All
right
did
you
have
any
other
concerns
that
were
not
addressed
arena.
This
was
your
bullet
point.
I
just
wanted
to
I'm.
A
E
E
E
E
I
think
that
backdrop
is
modern
system,
it
is
so
it
is
very
powerful
and
it
can
live
for
a
long
time
and
it
doesn't
need
to
compare
it
to
other
systems.
E
We're
all
grateful
to
drupal
and
drupal
developers
who
develop
triple
seven
triple
nine
is
enterprise
edition.
Her
backdrop
is
community
edition.
They
are
different,
they
have
very
different
backhand.
They
have
very
similar
experiences
for
site
builders,
but
they
are
very
different
and
there's
absolutely
no
need
to
compare
and
this
recent
amount.
I
think
that
it's
very
respectful
of
drupal
association
to
say
we
respect
our
community.
We
see
community
trends
and
if
we
need
to
extend
support,
we
will
extend
support.
E
They
think
recognizing
good
things
what's
better
than
than
the
other
way
out
instead
of
today
is
very
sad
day
for
me,
so
I'm
very
very
preaching.
E
But
I'm
very
excited
to
see
your
design
and
I'd
be
happy
to
volunteer
whatever
time
I
can,
and
I
have.
I
need
a
lot
of
workplace
days
to
get
through
this.
You.
A
E
This
work
so
the
more
work
I
have
the
better
it
is
for
me,
I'm
taking
every
project
that
I
can
and
I
will
be
happy
to
work
with
someone,
but
especially
with
nika
and
darris
and
jen,
to
make
this
layout
happen
and
lay
out
designs
altogether.
So
yeah
just
tell
me,
you
know
how
to
log
into
it
and
I'll
start
coding.
E
A
D
A
Front
page
top
section:
no,
we
do.
This
is
very
specific.
This
is
perfect.
You
reina
wrote
this.
Thank
you
irena
okay.
So
this
is
issue
number
869.
In
the
backdrop
cms.org
q,
just
talking
about
like
how
can
we
use
that
space
to
be
more.
A
And
this
is
an
answer
to
that
question.
So
I'll
I'll
drop
the
a
screenshot
of
this
design
in
there
we
can.
D
If,
if
no
one
else
has
anything
else
to
bring
up,
I
would
like
some
preliminary
feedback
in
one
of
the
issues.
I'll
say
they
should
maybe
maybe
it's
best
fit
for
contrib,
but
it's
related
to
some
of
the
sessions
that
I
will
be
facilitating
in
the
backdrop,
live
with
regards
to
content
editor
experience.
So
this
is
issue
5519.
D
Which
aims
to
allow
allow
site
builders
to
specify
which
menu
they
want
to
use
for
the
admin
menu
per
role.
So
if
they
want
to
use
a
completely
different
menu
for
content
editors,
they
they
could
do
that.
So
there's
a
few
things.
First
of
all,
it
there's
a
few
issues
that
have
been
brought
up
recently.
D
Also
feedback
with
regards
to
such
issues.
Would
they
be
better
instead
of
being
implemented
in
core,
be
a
form
of
a
section
in
the
documentation
which
is
titled
how
to
deliver
a?
I
don't
know
a
better
experience
for
content
editors
out
of
the
box,
which
is
basically
a
set
of
recipes
and
how
to's
for
site
builders
of
you
know
best
practices
when
you're
delivering
your
product.
So
I
don't
know
if
it's
us
putting
the
tools
that
these
people
need
in
core
or
giving
them
a
set
of
instructions
that
they
can
follow.
So
yeah.
D
D
D
I
would
like
us,
if
possible,
to
sort
of
like
make
the
experience
for
this
user
group
as
a
target
audience
much
better.
So
if
a
solution
such
as
backdrop
is
quote
unquote
imposed
on
the
on
the
actual
site
owner,
they
actually
feel
good
about
it.
They
say
yep.
This
is
a
tool
that
I
can
easily
use.
I
don't
have
to
navigate
around
a
lot
of
menus
and
things
like
that
and
content.
A
That's
already
in
backdrop
core,
so
I'm
not
sure
I
see
a
use
case
for
this
feature
in
core
it.
I
could
see
how
some
people
might
want
like
a
different
menu
that
doesn't
include
links
to
the
things
editors
have
ability
to
access,
but
everything
is
already
access
controlled
in
admin
bar.
So
we
already
provide.
A
So
yeah,
I
think
if,
if
you
have
a
use
case
of
like
this
is
not
an
ideal
editorial
experience
with
only
two
menu
links
or
whatever,
I
would
like
to
revisit
that
problem.
Rather
than
being
like,
let's
force
people
to
build
a
new
menu
and
create
the
experience
and
change
the
what
we've
provided
in
core
yeah.
D
Yes,
yes,
actually,
and
that's
why
I
yeah
that's
why
I
added
a
session.
I
want
to
discuss
these
sort
of
things
in
backdrop,
live
and
get
some
feedback
as
well,
but
one
of
the
main
issues
that
comes
to
mind
is
this.
This
is
a
very
obvious
thing.
As
a
site
builder,
you
say
some
some
of
the
menus.
I
want
like
the
primary
navigation
menu.
D
I
want
people
to
be
able
to
edit
it
why
why
do
content
editors
have
to
go
to
a
menu
that
is
called
structure
in
order
to
edit
the
menu,
when
that's
the
only
menu
that
they
will
be
editing,
so
there's
a
need
for
them
to
just
have
three
like
the
admin
bar
for
them
should
be
people
users
whatever
they
call
it
for
those
content,
editors
that
also
manage
user
accounts
on
the
site,
menus
and
content,
that's
it.
So
why
would
why
would
you
hide
a
content?
D
Editor
oriented
feature
other
a
thing
that
is
called
structure,
so
you
need
that
thing
for
site
builders,
but
you
need
the
very
same
item
exposed
to
content
editors.
So
as
a
as
a
developer,
if
I
was
asked
to
provide
a
better
experience,
I
would
create
a
separate
menu
for
that.
Only
targeted
four
content
editors
and
I
would
like
that
menu
to
be
able
to
add
it
as
the
default
for
that
role
in
the
admin
bar
yeah.
A
That's
a
lot
of
assumptions
you're
making,
though
about
what
editors
can
do,
and
I
think
that's
one
of
the
problems
with
backdrop
is
that
if
you
look
at
10
different
sites,
the
number
of
things
in
that
structure
menu
is
going
to
be
different
for
an
editor.
I
think
that
we
could
also
put
some
of
these
things
in
like
into
the
way
that
we
build
menus
where,
like,
if
there's
only
one
child
item,
give
people
the
option
to
remove
the
parent
item.
A
That's
also
true
for,
like
there's
contrib
modules,
that'll
put
in
like
new
top
level
items
with
one
link
in
them
too.
So
I
can
see
this
working
for,
like
not
just
the
items
that
we
are
providing,
but
anything
you
put
into
the
menu
could
follow
that
same
pattern
too.
D
Yep,
that
was
just
an
example,
but
usually
when
the
editors
handle
handle
one
or
two
menu
items
like
the
header,
the
navigation
and
the
footer.
Perhaps
that's
the
most
common
use
case
use
case,
and
then
they
also
handle
one
vocabulary
right,
which
is
called
tags.
Why
again
have
them
go
into
structure,
vocabularies
tags
and
you
know
to
manage
things.
It's
exposed
just
three
items
whatever
they
most
commonly.
D
Do
we
shouldn't
be
exposing
developer
or
site
builder
features
to
content
editors,
because
it
gives
them
more
options
that
they
don't
need
and
that
sort
of
like
complicates
and
gives
the
impression
that
the
the
system
is
more
complex
than
it
is
so
yeah
that
that's
the
goal.
That's
the
that's,
hence
the
ux
bit
at
the
beginning.
You
know
you
said
irena
sorry.
You
said
that
you
wanted
to
ask
yeah.
E
I
think
that
there
is
existing
solution
to
this
program
for
for
a
while
using
secondary
menu
I'll
be
happy
to
showcase
it.
In
the
meeting
I
mean
in
the
backdrop
demo,
because
we
have
this
set.
A
E
For
a
long
time
where
there's
like
preset
default,
the
content
editors
have
their
own
menu
and
it
works
very
well,
because
every
content
editor
will
change
it.
In
addition,
in
addition
to
having
like
default
links,
they
also
keep
adding
their
own
links
that
are
related
to
their
specific
content.
I.
E
Yes,
it
exists
there,
it
just
needs
to
be
highlighted
and
maybe
more
exposed,
but
it
doesn't
require
any
additional
coding
and
also
there's
this
concept
of
shortcuts.
I
apologize.
I
have
to
leave
on
what
students
I
wanted
to
say.
Thank
you
very
much
and
jen.
Where
should
I
expect
communication
about
the
design,
stuff,
email.
E
A
Yeah,
I
I
feel,
like
part
of
isn't
a
removed
shortcut
backdrop
is
because
nobody
used
it
and
that
could
have
just
been
that
it
wasn't
designed
well
enough
to
meet
the.
A
It
might
have
been
too
abstract
or
too
you
know
unfriendly
or
something,
but
yeah
there's
definitely
a
use
for
that,
and
I
think
that
if
we
can
find
a
a
winning
drupal
7
solution,
I
used
it.
You
use
shortcuts.
C
D
So
the
the
trigger
for
these,
these
things
was
a
series
of
blogs
or
something
that
I
was
reading.
I
can't
remember
what
I
was
researching
and
then
I
came
across
it
and
I
was
like,
oh
my
god,
yeah
you're
right.
This
would
be
a
so
much
better
experience
for
quantitative
and
then
the
person
was
arguing
that
if
people
come
to
you
with
small
budget,
then
tweaking
all
these
things
to
provide
that
experience
takes
time,
which,
of
course,
you
have
to
take
down
to
the
customer.
So
you
have
to
build
them.
D
But
if
you
provided
like
a
few
switches
or
one
switch
or
something
out
of
the
box,
that
allowed
small
digital
shops
like
freelancers,
to
tweak
backdrop
in
a
way
that
would
provide
backdrop
out
of
the
box
content
editors
are
ready,
then
they
wouldn't
have
to
to
charge
their
customers
more.
They
just
you
know,
would
make
their
lives
easier.
They
would
provide
that
out
of
the
box
and
then
it's
not
just
the
the
the
developers.
D
D
And
I'm
not
arguing
that
this
can
be
done
in
can
trip
it's
just
that
we
can
also
do
like
a
a
blog
post,
and
you
know,
as
I
said,
best
practices
for
delivering
a
site
that
conjured
editors
would
be
happy
about.
It's
just
that
that
translates
to
time
people
going
through
the
list
and
actually
doing
these
things
instead
of
out
of
the
box.
D
D
The
the
only
thing
is
that
which
is
related
to
that
is
that
working
on
that
issue
most
times
that
when
we
need
to
add
fields
like
form
api
fields
on
a
table,
what
we
usually
do
is
we
have
a
another
theme
function,
and
then
we
do
the
table,
placing
thing
in
that
function
and
I
have
found
a
very
not
I
have
found.
I
have
borrowed
from
the
internet.