►
From YouTube: 2023-02-01 - Dashboards working group
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
C
A
That
was
just
something
I
was
thinking
about
over
the
last
week
or
so
like,
maybe
just
get
rid
of
that
term.
And
then
we
also
Define
like
what
is
an
app
landing
page,
a
page
that
someone
can
interact
with,
but
is
not
clearly
not
a
dashboard.
C
A
A
B
A
C
I
think
we
could
delete
it
from
the
robot
and
in
our
description
be
specific
and
say
a
dashboard
is
not
a
XYZ
explanation
of
what
a
landing
page,
what
the
app
landing
page
for
you
style
is
because
there
is
a.
As
you
said,
there
are
a
lot
of
things
that
The
Landing
base
doesn't
have
that
a
dashboard
would
have
yeah,
so
I
I,
yeah
I,
wouldn't
expect
to
just
like
the
Project's
list
to
be
a
dashboard.
Necessarily
it's
a
listing.
It's
not
the
same
thing.
Yeah.
A
A
That
was
one
thing
Christy
asked
to
me
last
week
was
just
like:
are
you
getting
towards
what
a
dashboard
is
not
and
the
definitions
for
those
other
landing
pages?
Can
we
get
those
too?
So
if
we
could
take
a
stab
it
kind
of
decide
like
deciding
or
at
least
giving
them
like
a
definition,
even
if
we
don't
go
deeply
on
them
as
the
counter
to
the
dashboard.
A
A
D
C
For
me,
I
am
just
waiting
for
people
to
say,
yay
or
nay,
before
I
go
through
and
write
descriptions
out,
so
I'm
happy
for
it
to
be
async
and
people
just
go
through
the
comments
or,
if
they
add
their
own.
C
A
C
The
drag
drop
could
go
in
with
grid
attributes,
but
I
see
what
you
mean
about
we're
not
describing
like
the
ability
to
move
panels
around
necessarily
just
that
we
you
can
position
them
in
a
grid.
So
that
could
be
added
to
the
description
because
we're
going
to
talk
about
grid
layout
and
row
columns
Etc.
But
we
don't
actually
say
you
could
move
them
around
in
the
UI
in
any
way.
C
A
C
Yeah,
the
great
attributes-
State
XY,
coordinates
for
the
panel,
so
that
would
instantly
give
you
the
order,
the
ability
to
sort
them
you're
right
that
it
could
be
turned
on
or
off
based
on
the
needs
of
these
of
that
Dash
particular
dashboard.
If
it's
custom
made,
then
it's
going
to
need
a
way
refuses
to
move
them
around.
But
if
it's
built
by
us
as
a
static,
you
know
uneditable
dashboard,
then
maybe
not.
We
wouldn't
have
that
functionality
it'd
be
specifically
designed
to
be
rendered
in
this
way.
A
C
Is
the
aim
once
we
have
these
definitions
to
convert
these
into
some
kind
of
output
like
pajamas
guidelines
or
some
product
guidelines,
or
some
kind
of
guideline?
Is
that
the
general
aim
out
of
this?
So
we
have
a
list
of
things
of
do's
and
don'ts.
A
D
A
C
I
personally,
as
an
engineer,
the
first
place,
I
look,
is
pajamas
guidelines
on
how
a
page
should
interact
and
look
visually
with
the
user.
So
if
I
was
going
to
look
up
Dash,
what
a
dashboard
is.
That's
probably
where
I'd
go.
First
I'd
probably
look
at
the
pajamas
guidelines
because
they're
normally
pretty
extensive
or
they
point
you
in
the
direction
of
our
of
another
documentation
on
their
handbook,
which
explains
that
from
a
product
point
of
view
or
whatever
it
might
be,.
F
F
G
C
I,
don't
know
it
could
be
a
pattern
foreign
describing
how
a
dashboard
should
be
behaviorally,
look
and
feel
to
our
users,
and
you
should
repeat
and
follow
this
pattern
for
all
additional
dashboards.
You
create
and
in
the
same
way
as
navigation
like,
and
we
describe
about
how,
in
general,
when
I
know
on
navigation,
you
should
have
auxiliary
actions
on
on
one
side
and
destructive
actions
on
another.
That
sort
of
thing.
G
C
G
Good
point:
there
is
sort
of
guidance
on
how
to
use
this,
even
if
it
will
be
new
components
which
some
of
them
might
be.
It
will
be
guidance
on
how
to
use
them,
basically
in
a
patterned
way.
E
Mintages,
there's
something
that
we
don't
have
yet
in
the
pajamas
UI,
because
we
just
don't
have
an
example
of
it,
and
that
is
like
page
templates
as
well,
and
so
when
I
was
working
on
the
the
Ia
updates
last
at
the
end
of
on
last
fall.
E
That's
a
page
that
or
a
section
that
we've
added
between.
Let
me
figure
out
where
this
is
at
here:
I'm,
just
looking
locally
quick
one.
Second,.
E
Right
yeah,
so
between
patterns
and
objects,
there's
a
page
templates
category,
but
we
just
have
nothing
to
add
under
that.
Yet
so
it's
not
revealed
in
the
pajamas
navigation,
but
anyway,
page
templates
is
another
section
that
originally
I
had
dashboards
under,
but
we
left
it
out
and
part
of
that
was
just
because
of
the
definition
of
dashboards
it
was.
It
was
all
over
the
place,
so
that's
another
consideration.
We
can
leave
it
out
there.
We
could
also
parse
it
out
in
a
few
different
areas
and
really
tie
it
together
too.
So
yeah.
G
C
Yet
that
I
agree
product
and
design
and
management
are
going
to
be
the
first
Port
of
Call
when
it
comes
to
creating
these
new
features
and
areas
in
the
product,
and
you
know
that
you've
as
a
designer-
that's
you
know,
first
port
or
call
as
well
is
to
go
look
at
what
we
already
have
agreed
as
a
group
in
pajamas.
C
So
having
that
block,
there
stops
it
from
getting
down
to
engineering
when
engineering
starts
questioning
it,
because
in
our
engineering
handbook
it
doesn't
match
up
with
what
we're
saying
I
do
know,
we
don't
have
anything
related
to
dashboards
in
the
engineering
handbook,
though.
Well
we
do.
We
have
a
custom
dashboards
page
which
describes
the
functionality,
which
we
could
then
link
to
the
pajamas
documentation
to
be
fair.