►
From YouTube: Web Content Meeting 6/9/22
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
Okay
and
then
I
did
notice
that
that
people
were
adding
stuff
to
the
agenda,
which
is
great,
but
I
am
going
to
as
we
jump
down
to
them.
I'm
just
going
to
I'm
going
to
defer
that
conversation
to
the
individuals
that
added
that
information.
So
the
first
thing
on
the
list
is
the
chaos
community
handbook
tasks.
C
A
C
A
A
A
A
A
B
D
A
D
A
I
get
that
because,
as
as
we've
discussed
in
regards
to
the
the
some
of
the
terminology
across
working
groups,
the
that
hierarchy
doesn't
necessarily
hold
up
to
scrutiny,
so
so
I
do.
I
do
understand
that,
but
I
I
guess
my
question
is
kind
of
around
the
the
organization
of
that
navigation
right.
So
if
we
have
a,
if
we
have
a
high
level
navigation,
header
or
tab
for
it,
what
is
it
and
what
would
be
underneath
it
is
it
just?
Is
it
just
those
two
local
communities
or
is
it?
Is
it
these?
A
A
C
A
But
once
again
something
we
don't
need
to
do
right
now,
because
I
think
this
I
think
the
navigation
is
going
to
be.
I
think
we
want
to
look
at
our
existing
navigation
critique.
What's
there
and
decide
what
we
need
to
have
in
that
main
navigation,
and
I
don't
from
a
from
a
website
design
standpoint.
I
don't
think
we're
there
yet.
C
C
C
What's
that,
I
added
that
yeah,
okay,
excellent!
It's
basically
like
with
the
website
redesign
and
the
community
handbook
structure,
also
changing,
and
then
we
have
another
knowledge
base
coming
in.
So
I
think
it's
important
that
right
from
the
start,
we
clear
out
and
define
which
role
and
what
purpose
a
particular
thing
is
going
to
serve
so
like.
E
I
have
thoughts
about
this,
so
here
they
are.
I
see
community
handbook
as
like
a
user
manual
so
like
if
you
buy
an
internet
capable
washer
dryer,
for
instance,
as
we
were
discussing
earlier,
you
have
your
user
manual
which
has
all
of
the
stuff
in
it.
But
then,
if
you
go
to
the
website-
and
you
just
have
like
another,
a
question
or
you
know
like
I'm,
not
sure
you
know
a
question
I
might
have
would
be
like.
E
Oh
can
I
do
this
thing
from
the
app
whatever,
so
I
don't
want
to
maybe
necessarily
look
through
this
whole
user
manual
it's
there,
but
I
would
go
to
like
the
website
and
go
to
their
knowledge
base
and
type
that
in
like
can
I
do
this
thing
from
the
app
and
then
it
will
point
me
maybe
to
the
user
manual,
maybe
somewhere
else,
maybe
to
an
app
like
a
specific
page
on
their
website
about
that
app.
Something
like
that.
E
A
Building
building
on
that,
because
I
agree
the
the
work
of
the
google
summer
of
doc,
students
will
will
likely
include
editing
and
creating
content
for
the
knowledge
base.
That
would
not
be
a
task
that
we
would
have
you
do
right,
so
your
your
job
is
not
to
build
content
for
the
knowledge
base.
Your
job
is
to
basically
create
the
knowledge
base
on
the
website
and
link
it
to
existing
content.
A
However,
I
we
we
don't
want
to
do
any
content
creation
ourselves
for
the
knowledge
base
in
regards
to
you
know
where
the
overlap
is
like,
where
we're
me,
where
there,
where
there's
maybe
some
connection,
that's
maybe
in
the
structure
of
the
information.
That's
in
the
handbook,
because
we
need
to
we
need
to
understand
what
these
these
high
level
chapters
or
organizational
structures
are
in
the
handbook
when
we're
building
the
knowledge
base,
because
we
would
like
to.
A
A
D
C
D
C
A
A
A
If
we
need
to
create
that
that
kind
of
searchable,
dynamic
knowledge
base,
then
perhaps
the
that
knowledge
base
level
is
at
the
at
the
folder
structure
that
the
folder
level
of
the
community
handbook
right,
okay,
that
makes
sense
and
and
maybe
let's
let's
let's
meet
separately
and
talk
about
this.
Yes,
because
we'll
we'll
go
down
we'll
keep
talking
about
this.
If
we
continue
so
do
you
do
you
feel,
like
the
the
roles
are
clearly
defined
for
you.
A
B
A
A
E
Yeah
I
put
that
in
there
just
to
talk
quickly
about
that.
We
did
get
six
responses
to
that.
Little
survey
that
we
did
people
are
either
looking
to
participate
in
the
meetings
and
looking
for
information
or
calendar,
or
something
like
that
or
they're.
Looking
for
metrics
specific
information,
no
surprise
to
us
that
was
extremely
hard
for
them
to
find,
and
even
the
calendar
it
looked
like.
Somebody
had
tried
to
find
meeting
information
and
ended
up
going
to
github
to
find
it,
which
I
thought
was
interesting,
because
we
don't.
E
I
we
have
it
on
github,
but
we
don't
really
make
sure
that
that's
ever
like
in
sync
with
what
the
calendar
like
the
calendar
is
a
single
source
of
truth.
So
I
thought
that
was
kind
of
curious
that
they
ended
up
finding
what
they
needed
on
github,
which
was
unintended.
So
we
could
expand
the
survey
if
we
wanted
to
dig
deeper.
We
can
just
kind
of
take
those
at
face
value,
since
there
are
only
six
responses,
but
whatever.
E
A
E
E
C
C
A
F
A
A
D
I
did
talk
to
the
lf
about
kind
of
updating
the
branding
other
than
like
the
logo
itself,
but
like
that
blue
and
they
were
like
knock
yourself
out.
You
know
what
I
mean
they're
like
we
had
with
the
800
projects.
We
now
have
at
the
lf
for
you
to
put
yourself
in
a
queue
to
ask
for
some
new
design
elements
would
take
maybe
100
years
so
so
we
I
think
we
have
some
latitude
to
do
that
and,
if
you'd
like
to
start
that
now,
we
certainly
can.
A
C
C
A
A
C
C
E
F
I
think
what
he's
saying
is,
instead
of
having
the
photos,
be
these
authentic
live-action
kinds
of
shots
with
a
lot
of
visual
stimulus
in
them
that
they
be
more
of
an
organized
representation
of
what
that
that
that
image
is
about
the
image
becomes
more
of
a
descriptive
asset.
I
think,
is
what
you
say.
A
Yeah,
I
agree.
I
agree,
I
think
that's
that's
what
I'm
that's
what
I'm
hoping
to
grab
from
from
this
con
this
conversation.
So
what?
How
can
we?
So,
if
we're,
if
we're
putting
in
the
requests
for
these
images
to
a
graphic,
artist
or
graphic
designer,
how
can
we?
How
can
we
verbalize
these
requests,
and-
and
yes,
I
agree
with
you
completely
so
the
the
pictures
that
I
put
in
are
just
their
pictures
that
were
there
their
placeholders,
so.
F
I
think
we
would
give
the
graphic
artist
access
to
the
content,
that's
behind
each
section
and
have
them
help
us
to
develop
something
that
accurately
or
meaningfully
visualizes
in
some
way
the
content
of
that
section.
Okay,
so
that
a
user
can
look
at
it
and
have
a
you
know,
be
fairly
well
clued
into.
What's
there
I
mean
that's
what
I
would
trust
a
graphic
artist
to
figure
out.
I
am
not
a
graphic
artist.
A
F
C
A
D
D
Well,
this
is
good
too.
The
prototype
is
good
too,
because
I
think
to
sean's
point.
It
puts
something
in
front
of
people
and
they're
like
oh
okay,
I
kind
of
see
the
size
of
the
assets
that
need
to
be
done.
Oh,
I
kind
of
see
that
they're
like
going
to
be
three
of
them
in
a
row
like
they
probably
need
to
flow
together
a
little
bit.
Things
like
that.
B
C
C
A
A
So
we've
we've
kind
of
moved
into
a
one
column,
one
column
structure
as
we
go
down
and
then
in
each
of
those
columns
we
do
break
it
out
a
little
bit.
I've
only
got
so
other
than
this
slider
navigation,
which
is
going
to
take
us
to
the
three
this.
This
top
part
is
going
to
be
our
three
main
user
pads
and
then
obviously,
we'll
have
regular.
A
A
This
will
be
a
history
and
info
link,
basically
whatever's
in
the
we
can
we
build
out
the
about
page,
but
I
think
the
there
are
a
couple
documents
that
can
be
merged
into
the
about
page,
which
will
actually
remove
some
of
our
navigation
currently,
and
then
we
drop
down
to
the
next
row
and
we
have
a
kind
of
a
news
and
social
twitter
was
removed
from
this.
However,
I
thought
it
made
sense
to
keep
three
on
here.
A
This
should
be
kind
of
the
simpler
than
simpler
than
what
was
there
before
and
also
it
kind
of
it
can
kind
of
take
center
stage
a
little
bit,
and
then
we
drop
down
to
our
supporting
organizations
and
then,
lastly,
we
dropped
into
our
footer
and
the
footer
has
not
been
prototyped,
but
the
the
last.
The
last
section
would
be
our
footer.
A
So
the
the
home
page
becomes
pretty
simple
right.
It's
one,
two
three
four
four
kind
of
content
areas,
and
then
you
also
have
your
main
navigation
and
your
footer,
I'm
wondering
if
that
resolves
some
of
the
the
issues
we've
had
in
the
past,
about
the
structure
being
kind
of
overly
complicated
or
noisy.
B
Yeah
this,
this
really
looks
good
like
compared
to
what
we
had
before
and
some
comments
I
have
will
one
one
is
for
the
graphic
designer,
but
like
the
choice
of
colors
like
with
the
colors,
are
contrasting,
it's
ready.
The
second
two
sections
right,
that'll
be
one
color
and
also
we
could
so.
I
know
usually
news
and
social
comes
like
down
the
page
right.
B
Maybe
we
want
to
move
supporting
organizations
up
after
what
is
chaos
and
then
have
news
and
socials
down
after
supporting
organizations,
and
also,
I
think
there
should
be
some
space.
I
think
there's
some
space
to
add
sweetheart,
because
I
think
that's
also
important
as
well
like
on
that
chaos
class.
There
should
be
some
space
to
add
to
it's.
Not
there.
A
A
A
So
it
is
something
we
could
add.
I
suppose
if
we
wanted
to
or
we
can
link
to
it
in
other
ways
right
so
we
can
have.
There
are
other
pages
where
we
can
specifically
call
out
our
twitter
twitter
content.
There
are
you
know
we
can
do.
We
can
do
twitter
badging
in
other
places,
on
the
website
as
well.
It's
just
about
in
this
nose
and
social
area.
Do
we
want
a
very
explicit
twitter,
scroll.
B
A
And
then,
and
then,
regarding
the
the
design
comments,
I
agree
yeah.
None
of
this
none
of
the
colors
that
I
have
chosen
here
are
probably
appropriate
and
and
I'll
go
even
further-
that
even
these
titles
news
and
social-
probably
not
great
yeah.
This
is
we're
just
yeah
we're
just
looking
at
the
structure
and
regarding
moving
moving
this
news
and
social
to
the
bottom
and
moving
supporting
organizations
up.
I
like
that.
I
think
that
would
I
think
that
could
work.
A
I
think
some
of
that
will
depend
on
how
many
supporting
organizations
we
have
on
the
page.
If
we,
if
we
have
more
than
more
than
what
we
have
here,
then
it
may
make
sense
to
keep
supporting
organizations
on
the
bottom.
If
we're
just
talking
about
a
couple
yeah,
maybe
maybe
we
move
it
up
and
we
have
the
news
and
social
at
the
bottom.
A
None
of
the
formatting
on
this
is
is
what
yeah
the
white
the
amount
of
white
space
that
we
see
here,
isn't
what
would
be
accurate.
The
yeah
the
colors
aren't
accurate.
This
is
it's
just
about
structure
and
the
type
the
type
of
data
that
we
would
have
on
the
or
the
the
type
of
content
that
we
would
have
on
the
website,
so
think
about
the
the
columns
and
rows
and
the
the
things
that
we
need
to
have
on
the
web
on
the
front
page.
A
B
E
E
F
A
C
D
A
Well,
my
argument
is,
if
we
just
say,
hey,
let's
announce
those
in
the
blog
yeah.
It
manages
and
maintains
itself
because
then
you
don't
have
to
when
you,
when
you
announce
a
new
when
you
announce
a
new
badge,
you're
going
to
have
to
go
in
and
edit
a
markdown
page
or
let
me
know
that
it's
changed,
whereas
if
we
just
do
a
if
we
just
do
a
like
a
congratulations
in
the
blog
to
the
the
project,
with
a
link
to
the
project,
the
the
blog,
this
little
blog
scroll
would
update
itself.
E
A
Yeah
we
just
so
the
title
would
be
the
project,
and
then
you
have
a
one
line
and
then
yet
you'd
have
a
date,
and
then
this
this
title
here
would
be
called
it'd,
be
called
badging
of
some
sort,
and
then
the
the
name
of
blog
post
here
would
actually
be
called,
could
be
called
event.
Badging
could
be
called
project
badging,
so
yeah,
it's
just
it's
just
a
way
of
populating
the
the
stuff
on
the
website,
so
don't
think
of
it
as
don't
think
of
it
as
a
traditional
blog.