►
From YouTube: Layer5 Websites Meeting (Jan 31st, 2022)
Description
Layer5 Websites Meeting - January 31st, 2022
Agenda:
- Updates on Static Images issues
- Projects page, Nighthawk, footer, navbar, some callouts #2559
- Newcomers page optimization #2560
- Home Page
- Careers Page #2543 (merged)
- Landscape, Learn Components #2545 (merged)
- Improving the resources library. #2558
- Learning paths quiz. #2549
- Learn TOC collapse on mobile view. #2551
- Search Component for blog
- Reformatting of the single column blog list view #2540
- Updates on the compatibility matrix (#5009).
- error codes navigation updates.
Join the community at https://layer5.io/community
Find Layer5 on:
GitHub: https://github.com/layer5io
Twitter: https://twitter.com/layer5
LinkedIn: https://www.linkedin.com/company/layer5
Docker Hub: https://hub.docker.com/u/layer5/
A
And
yeah
so
like
in
the
original.
We
have
all
these
stacked
up
one
another.
So
I've
changed
the
settings,
so
we
haven't
collapsed,
nav
bar
here
so
like
okay,
one
can
collapse
it
and
go
to
other
page,
and
that
was
pretty
much
it
for
like
it's
given
better
experience
for
the
mobile
users.
So
this
one
wasn't.
C
A
A
B
B
B
So
you
know
what
the
experience
is
like
and
and
there's
a
few
different
variations,
but
but
you
put
one
together
and
and
yeah
you're
precisely
right,
like
the
fro
that
type
of
user
exp,
the
user
experience
the
flow
that
they
would
have,
the
the
actual,
putting
together
of
the
pages
and
the
interactions,
much
of
it
most
of
it
like
like
you've
just
proven
it
can
be
done
without
the
back
end.
You
don't
you
don't
have
to
have
it.
You
can
mock
stuff
up.
B
You
can
use
a
fake
piece
of
json
or
what
like
some
some
response
that
you
might
need
to
use,
but
you
can
all
that
can
be
filled
in
later.
So
it's
just
it's
a
great
example.
I
think
for
everybody
else,
that's
on
the
call
or
everyone
else
that
might
come
later
to
just
highlight
the
fact
that
those
two
don't
have
to
wait
on
each
other.
You
don't
have
to
first
agree
upon
what
the
exchange
will
be,
what
the
xml
or
the
json
or
the
request
and
response
precisely
will
be.
B
It's
like
look
the
if
let's
say
that
the
responses
included
a
bunch
more
information
than
you
had
had
displayed.
Well,
one,
it
didn't
really
matter!
You
don't
need
that
extra
info
two
if
it
was
formatted
different
than
what
you
have
right
now,
it's
very
easy
for
you
to
change
it
around
to
just
update
to
account
for
the
front
end
so
anyway.
B
I
guess
is
what
I'm
saying
like
one
thing:
we
wanted
well
yeah
good,
so
there's
a
couple
of
other
quizzes
that
are
relevant
to
what
we're
doing
that
are
that
are
aimed
really
at
the
same
technologies
at
the
same
at
a
similar
certificate.
That
would
be
good
for
you
to
digest
just
to
get
a
sense
of
what
the
style
of
questions
and
the
style
of
interaction
that
people
are
accustomed
to,
just
as
as
inspiration
or
as
food
for
thought,
but
otherwise
yeah
so
there's
another.
B
So
you
actually
worked
on
this
before
as
well,
so
by
the
way
nikhil.
It's
like
it's
time
for
that
internship
like
like
it's
been.
It's
been
a
long
time
like
it's
something
I
want
to
talk
to
you
about
after
this,
so
you
also
had
a
mock-up
on
measuring
cloud
where
people
would
authenticate
and
sign
in
and
which
was
which
is
pretty
by
the
way
which,
but
but
more
than
that,
the
back
end.
Okay.
So
how
do
I
say
this?
B
The
front
end
to
the
back
end
also
needs
updated,
or
rather,
where
people
authenticate
and
sign
in
they
don't
really
have
many
controls
over
they're,
changing
their
password
or
resetting
their
you
know,
or
changing
their
email
address,
resetting
their
password
yeah,
so
so
great
good.
I
think
you
just
made
it
a
real
thing,
like
the
the
second
phase
of
the
learning
path-
yeah,
let's
do
it,
let's,
so
the
screen
recording
that
you
just
showed
do
we
is
that
posted
somewhere,
it's
probably
on
a
probably
on
a
pr
actually.
B
Oh
okay,
nice
good
I'll
I'll
follow
up
we'll
do
do
other
people
have
feedback
on
any
of
the
specifics.
Some
of
the
steps
that
are
involved
so
so
you
had
this
concept
of
attempts
in
there
was
that
attempts
for
per
question
or
attempts
per
the
for
the
whole
thing,
of
course,
okay,
and
thus
far,
I
think
what
you
were
showing
it
was.
A
B
A
A
B
So
if
we
dis
like
if
one
of
the
questions
isn't,
if
we're
trying
to
make
it
a
little
more
difficult
than
just
simple,
you
know
multiple
choice
that
we
might
say:
hey,
okay,
here's
to
question
five:
it's
base,
it's
just
it's
basically
a
lab,
so
you
follow
and
execute
the
lab.
And
if
you
perform
the
lab
correctly,
then
you
then
you,
then
you
answer
the
question
below
and
so
I'm
just
kind
of
brainstorming
aloud
about
yeah
yep
that
that
might
be
a
better.
B
B
That
could
be
really.
That
could
be
that's
a
good
idea.
This
plays
into
the
surface
mesh
playground
by
the
way,
because
what
we
would
we
have
limited
capability
inside
of
catacota.
They
only
let
you
do
so
much
in
there,
which
which
makes
sense,
because
otherwise
there'd
be
a
lot
of
crypto,
that's
mined
from
within
those
labs.
B
Probably
so,
if
we
end
up
with
the
service
mesh
playground,
which
would
be
a
hosted
instance
of
measuring
that
can
be
used
that
can
be
used
for
people
to
execute
their
labs,
that's
actually
what
the
playground
is
for
for
people
to
go,
learn
about
service
meshes
if
they're
learning
and
certifying
in
the
same
place.
Great
microsoft
has
given
us
10,
000
credits
to
use
their
cloud.
B
B
B
B
C
A
No
actually,
for
example
like
if
someone
has
completed
the
course,
so
he
will
redirect
it
to
this
page,
where
he
can
click
on
the
take
quiz
button,
and
if
he
is
already
login,
then
he
won't
see
the
login
form.
Otherwise,
the
next
step
would
be
the
login
form,
and
then,
after
that
we
have
the
quiz
part.
B
D
D
B
Does
that
make
sense
to
kill
so
if
you've
got
any
number
of
new
pages
or
interactions
going
on,
those
can
actually
be
merged
and
published
publicly
sitting
there
and
the
likelihood
that
someone
will
actually
arrive
at
them
is
very,
very
low.
If
there's
no
take
quiz
button
or
take,
you
know
certify
now,
button
yep.
A
E
B
That's
maybe
just
for
for
the
other
folks
they're
on
just
and
in
part,
because
this
is
this
would
be
part
of
our
next.
The
way
to
advance
this
discussion
a
bit
is
there.
There
are
two
figma
figma
design
files.
I
know
this
is
probably
kind
of
small.
I
don't,
even
if
I
zoom
in
it's
not
going
to
change
it,
but
so
one
of
them
is
measure
ui.
The
other
one
is
layer.
5
designs,
one
of
the
pages
inside
the
layer,
5
designs,
design
file
is
called
learning
paths.
B
When
so,
these
learning
paths
when
they
were
originally
created,
there
was
sort
of
the
concept.
Was
we
do
this
system
in
multiple
phases?
First
phase,
so
we'd
create
more
we'd,
create
the
learning
paths
themselves
and
multiple
of
them
second
phase
would
be
what
we'll
kind
of
kind
of
second
and
third,
I
think,
or
in
part
what
nikhil
is
highlighting,
and
there
have
been
some
some
designs
that
are
a
good,
a
good
starting
point
for
agreeing
that
this
is
what
it
you
know.
B
B
B
Here
so
I
think
this.
This
is
the
second
thing,
so
I
don't
know
that
there
were
a
lot
of
mock-ups
about
the
actual
quiz
or
the
actual,
but
more
mock-ups
about
how
to
sign
in
how
you
might
be
able
to
bookmark
certain
sections,
the
bookmarks
really
they're.
That's
not
that
much
of
a
I
mean,
first
of
all,
it's
really
quite
straightforward,
but
second,
it's
not
the
most
the
highest
priority.
It's
not
that
important.
B
A
A
Yep
so,
for
example,
assuming
there
is
a
person
who
is
first
time
wasting
the
learning
paths,
so
he
will
be
able
to
get
to
this
page
and
he
gets
started
with
it
and
then
he's
like
okay.
So
this
is
the
first
chapter
and
then
he
goes
to
the
next
chapter
and
the
next
chapter
and
then
let's
say
he
left
off
at
expo
expo
services
for
that
day
and
then
he
came
back
later
another
day
and
he's
like
okay:
let's
go
there.
A
A
B
Yeah
yeah
it
is,
it
is
almost
it's
almost
too
implicit
too
too
nice,
maybe
where
users
like
the
level
how
many
clicks
it
takes
people
to
get
to
their
learning
path.
This
isn't
nikhil's.
This
isn't
your
issue,
but
just
the
the
number
of
layers
that
it
takes
people
to
get
down
is
a
hindrance
to
people
really
getting
into
the.
B
It
also
we
would
want
to
make
they
wouldn't
necessarily
know
or
realize
that
the
bookmarking
is
happening.
We
want
to
make
it
explicit
that
they're
I
mean
it
can
happen
like
that.
That's
great,
but
also
we
want
to
give
them,
make
it
explicit
that
they
know,
oh,
that
bookmarks
are
happening
and
that
they
can.
B
You
know
that
that
their
their
progress
is
being
tracked
like
we
might
want
to
show
them
like
like,
given
that
you're
doing
that
automatically
one
thing
to
do
would
be
to
put
a
check
mark
next,
instead
of
where
we
have
the.
I
don't
know
why
it's
so
terrible
why
we
had
such
a
hard
time,
but
this
chapter
that
chapter
menu
list
on
the
left,
where
we've
got
the
vertical
line,
that's
off-centered
from
the
bullets.
B
You
could
change
those
into
check
marks
as
they
go
or
for
the
ones
that
you're
tracking
or,
if
you're,
just
tracking
a
single
page
then
find.
Maybe
you
have
an
arrow
indicator.
That's
like
you
are
here,
yeah
yep.
Actually,
that
would
be
better,
but
and
then
that
way
it
would
be.
You
know
it.
Wouldn't
it
wouldn't
be.
So
it's
too
subtle.
A
B
C
C
B
So
if
you
filter
just
on
events-
and
you
were
to
click
on
one
of
those
events,
the
page
that
you're
taken
to
is
the
actual
events
page
that
you
would
have
otherwise
landed
on
if
you
navigated
to
events
separately
outside
of
resources.
So
it
really
ends
up
just
being
a
different
way
of
browsing
the
collections
themselves.
Now,
that's
true
for
the
events
collection
like
it's.
B
B
That's
going
on
and
that's
the
the
item
that
deborah
priya
just
shared
on
the
recorded
webinar,
it's
like
when
we
recorded
the
webinar
someone
made
a
blog
or
demo
priya
made
a
blog
post
about
it
kind
of
wrote
it
up
and
described
it,
and
it
was
really
helpful,
really
really
great
and
so
good
there's
a
blog
post
out
there.
But
now
there's
also
a
separate
item.
That's
very
brief!
In
nature.
B
It
says
that
there's
a
recorded
webinar
available
and
just
describes
succinctly
the
fact
that
there
is
one
here's,
the
the
video
it
just
kind
of
gets
right
to
it.
Like
here's,
the
presentation
in
the
video
like
go
ahead,
it
doesn't
have
the
longer
blog
post
write
up,
both
of
which
are
great,
so
we
kind
of
have
all
three
things
you
sort
of
have
totally
original
content
the
articles
collection.
B
B
So
so
we
have
these
all
these
types
we
have
like,
like
10
different
types
of
content,
just
as
we
were
putting
together
this
resources
area,
there
was.
We
just
wrote
down
the
various
types
of
content
that
we
think
that
we
might
have
so
frequently
asked
questions
is
one
of
those
types
it
would.
It
might
be
that
someone
wants
to
put
out
not
really
a
full
blog
post
or
definitely
not
a
full
blog
post,
not
a
full
article.
That's
you
know,
but
just
some
quick
factoid,
that's
like
that.
B
Someone
bumps
into
you
know
when
I,
when
I'm
running
mastery,
ctl
I'm
having
trouble
with
minicube
or
whatever,
like
there's
a
common
pitfall
that
people
hit,
maybe
and
so,
and
so
that
was
the
concept
for
faqs
now
right
here
under
resources.
It
says
that
we
have
zero
and
that's
that's
true
in
so
much
as
you
know,
resources
but
like
double
prior
showing
on
the
site
in
general,
we
have.
We
have
a
set
of
faqs
they're
categorized.
B
I
think
in
the
three
category
four
categories
and
they
are
like
that
bottom
internships,
one,
is
an
example
where,
if
you're
on
the
careers
page
the
internships
page,
you
will
see
faq
you'll
only
see
these
four
you'll
only
see
that
category,
because
it's
relevant
to
that
page.
I
think
that
that's
the
only
page
that
we're
doing
that
on.
There
are
other
pages
like
the
mesry
page,
where
it
would
make
a
lot
of
sense
to
have
the
messaging
faqs
on
the
page
and
and
so
on.
B
B
Yeah,
so
we
have
four
categories:
should
we
have
four
individual
faq
pages
that
are
linked
here?
You
know
in
resources
or
like
or
I
guess,
what
sort
of
an
open
question
is
like?
Okay,
if
those
faqs
kind
of
don't
count,
should
we
should
we
link
those
faqs
here
and
if
we
don't
okay,
fine,
but
then
do
we
have
an
example
of
what
would
be
an
faq.
C
Okay,
so
one
major
problem
problem
with
faq,
like
the
reason
why
I
haven't
added,
is
the
way
in
which
we
are
representing,
like
this
entire
page,
which
was
dedicated
to
faqs.
Here
we
have
cards
so
of
course,
each
card
for
one
faq
does
not
make
any
sense.
So,
like
you
said,
we
can
group
them,
like
suppose,
faq
and
then
measuring
will
probably
show
us
that
collection
like
if
we
go
to
that
card,
we'll
probably
we
can
like
probably
display
this
itself
like
this
section.
B
B
B
So
you
might
that
that
page
had
workshops,
meetups
events,
something
else
yeah
as
a
secondary
filter.
So
like
yeah,
I
don't
know,
I
guess
it's
an
open
question.
There's
double
priya
has
a
proposal
to
take
the
take
categories
of
faqs
and
make
those
a
page
a
piece
we
have
four
pages
of
faqs
today
and
then
you
know
adding
more
and
and
part
of,
I
think
her
logic
is
what
I
was
just
saying,
which
is
like
well
geez,
one
page
dedicated
to
a
small
faq,
that's
kind
of
not
a
lot
on
there
like.
C
Yes,
like
this
events,
page
which
I
don't
like
so
much
like
it's
just
the
title,
icon
and
a
button
so
initially
like
this-
is,
I
think,
my
pr
review
right
now
in
the
main
page,
there
is
an
empty
bullet
because
it
does
not
even
have
a
speaker,
so
I've
removed
that
bullet.
For
now,
if
I
show
it,
it's
okay,
you
don't
have
to
see,
but
there's
an
empty
bullet.
D
B
B
Yet
we
should-
and
I
can,
but
we
should
absolutely
include
just
a
snippet
about
what
the
event
is
and
some
it
can
be.
It
can
be
just
some
very
routine
phrase.
It's
like
layer,
five
is
going
to
be
at
this
place.
You
should
come
hang
out
and
talk
to
us
and
we'll
see
you
there.
What
happened
like
it
doesn't
have
to
be
super
special,
especially
for
this
one,
but
it
absolutely
should
be.
What
deborah
priest
is
saying
is
true.
C
D
D
D
C
D
C
D
B
By
the
way,
a
question
so
the
the
data
for
faqs
and
the
data
for
those
present
those
tutorials
for
the
faqs,
it's
in
json,
I
think
and
or
it's
in
a
react
array
which
means
that
it's
programmatically
iterable
or
rather
the
faqs-
are
easy
enough
to
go,
grab
to
inje
import
and
then
display
on
the
page
like
like,
like
the
data
structure's
there.
Already,
it's
easy,
it's
a
straightforward
enough.
B
B
That's
something
to
figure
out
like
a
collection
is
probably
super
cheap.
Like
is
a
lot.
He
is
a
lot
more
powerful
by
collection,
maybe,
like
I
just
mean
like
a
collection
of
individual
markdown
files
like
one
file
dedicated
to
each
tutorial
which,
by
the
way,
if
we're
going
to
be
showing
off
those
tutorials
we're
going
to
have
to
get
some
much
better
tutorials
going
on
those
are
they're
pretty
decent,
but
for
a
lot
of
people.
B
B
C
F
Yeah,
so
I
made
the
search
feature
for
the
blog
page,
which
is
one
of
the
oldest
issue
open.
It
works
perfect
fine,
just
if
we
ignore
the
css
just
one
thing
that
bugs
me
itself
page
origination,
you
know
the
way
it
works.
It
takes
us
to
a
different
url,
so
it
works
for
the
list
on
the
page,
only
not
the
whole
list.
C
F
B
Yeah,
so
when
a
user,
all
right
so
so,
josh
is
working
on
implementing
search
for
well
for
the
blogs
good.
But
then,
potentially,
if
successful
here
for
other
collections
or
just
a
general
search
across
the
site,
maybe
and
commonly
the
way
that
this
is
achieved
is
through
use
of
something
like
leucine
or
or
some
leucine
spinoff,
which
is
just
that
as
your
site
is
being
statically
built.
B
Part
of
that
would
just
would
be
to
run
an
indexing
engine
to
identify
what
words
are
on
what
page
and
in
what
quantity.
Basically
like
do
a
map
reduce
in
some
sense
I
don't
but
anyway,
to
have
that
statically
completed
and
then
to
have
a
plug-in
like
to
have
a
plug-in
to
look
through
that
index
file
for
keywords,
and
so
then,
from
a
user
experience
perspective.
B
Hopefully
there's
kind
of
I
think
kind
of
two
things
that
would
happen.
Maybe
three
one
would
be
that
in
a
very
basic
sense.
If
someone
typed
in
a
search
term
and
hit
enter,
they
would
be,
they
would
be
shown
the
the
search
results,
page
sort
of
the
generic
page.
That
says,
here's
all
the
hits.
Here's
all
the
links
that
have
keyword
hits
for
what
you
typed
in
okay.
B
That
takes
us
back
a
couple
of
decades
in
terms
of
experience,
but,
like
people
understand
that
I
mean
people
still
do
that
today,
on
google,
but
and
they've
got
really
accustomed
to
type
ahead
search,
which
is
sort
of
a
second
phase
of
the
ux
that
could
be
done,
which
is
you're
typing
out
your
term
and
as
you're
doing
that
in
the
drop
down
below
you're.
Starting
to
see
some
results
like
links
to
pages
that
match
and
then
without
hitting
enter.
B
B
You
could
also,
then,
be
doing
a
live
filter,
which
is
to
say
that,
like,
as
you
start
to
type
it
out,
if
the
term
that
you're
typing
in
doesn't
match
meet
the
fall
interns
of
2021,
it
goes
away
like
only
basically,
you
start
to
see
your
actual
search
results
as
a
fill
as
a
live
filter
as
well
so
josh,
I
think,
all
of
those
or
any
any
one
of
those
or
all
three
of
those
user
experiences
is
beneficial
is
helpful.
It's
nice.
D
Yeah,
so
it
goes
to
a
separate
page.
So
that's
why
he's
only
being
able
to
filter
on
the
number
of
cards
that
are
on
the
page?
So
a
blog
is
basically
a
collection
right,
so
you
should
be
able
to.
You
know
tackle
it
by
filtering
on
the
entire
collection.
That's
one
way
to
approach
it
second
way
to
approaching
is
that
the
resources
page?
As
far
as
I
remember
the
pagination
happens
on
the
same
page,
the
url
does
not
change,
so
you
can
implement
that
on
blogs.
D
F
C
D
B
F
B
F
B
Yeah,
maybe
maybe
we
could
but
like
really
really
how
many,
how
many?
If
you
take
a
look
at
the
page
now
the
two
column
page,
is
it
like
nine
posts
that
we
show
or
twelve
or
six?
It's
like?
That's,
not
really
the
use
case,
and
I
get
that
like
you're,
trying
to
do
a
multi-page
multi
anyway.
Here's
the
use
case
is
let's
get
off
of
filter
and
on
to
search,
and
let's
start
by
identifying
what
plug-in
we
think
we
would
want
to
use,
which
I
think
is
called
out
in
the
issue.
B
B
F
B
B
B
Cool
yeah,
I
think
if
you
had
it
done
today,
then
like
if
it
if
it
was
actually
truly
easy-
and
you
were
done,
then
we
probably
would
but
since
you're
not
done
because
you're
hitting
another
issue,
it's
like
it's
not
really
the
goal
anyway.
So
yeah
did.
I
wonder
if
there's
an
example
of
the
ux
for
what
this
might
look
like.
B
B
D
I
guess
I
was
going
to
say
the
same
thing
which
I'm
saying
like
having
a
collapsible
collapsible
view
would
be
a
better
in
general
for
both
the
cases
like
we
have
for
resources
even
without
filtering
it
should
be
collapsed.
There
should
be
a
down
arrow
when
it's
not
collapsed
and
when
it
collapses.
Yeah.
C
B
B
I
would
suggest
that
that
I
know
it's
kind
of
a
joke
actually,
but
that
we,
we
probably
do
focus
our
time
on
other
things
and
hopefully,
in
the
meantime,
fill
in
the
get
the
blog
posts
going
so
that
like
yeah,
hopefully
because
it's
just
a
it's
a
matter
of
time
like
if,
if
we
advance
the
calendar
a
year
from
now,
should
we
have
generally
speaking
so
long
as
people
who
are
writing
the
post?
Don't
go
nuts
with,
like
you
know,
50
tags
per
post.
B
We
would
expect
that
we
have
more
posts
than
we
do
tags,
and
so
at
some
point
it's
just
like
we
would
like,
if
you
put
an
effort
into
fixing
this
symptom
and
have
an
expandable
tag
thing
like.
Hopefully
it
would
never
be
used
because,
hopefully
we
always
have
you
know
like
you
know,
however
many
blog
posts
per
category.
I
don't
know
I
just
it's
just
not.
We
should
do
other
things
like
put
time
into
the
thing
that
nikhil
is
working
on.
G
E
G
Okay
right
so
yeah,
so
this
is
my
progress
like
I
have
done
all
this
now
for
the
stable
version.
The
compatibility
matrix
shows
the
edge
as
well
as
the
stable
version.
So
how
I
figure
configured
is
that
if
the
latest
edge
is
the
the
latest
update
is
the
edge.
This
will
show
it.
But
if
the
latest
one
is
a
stable
version,
the
edge
edge
camera
will
not
show,
and
only
the
stable
version
will
show.
G
B
B
I
think
you'll
find
people
will
be
like.
Oh,
oh,
what
there's
no
there's
no
edge
release
for
such
and
such,
but
there's
a
stable
like
what
like
it
would
take.
They
would,
I
think
they
would
get
confused
before
they
and
then
they
realized
like.
Oh,
oh,
this
thing
is
actually
more
intelligent
than
and
like
it
just
it's.
It's
a
shame
that
we
have
to
write
software
for
the
rest
of
us
dummies.
B
Yeah,
it
might
be
too
now
the
thing
that
you
something
I
think
if
you
did
want
to
spend
more
time
and
take
this
a
step
further,
you
could
do
something
like
a
top
level
right
now.
You
have
columns,
you
could
put
a
top
level
table
nav
or
table
filter
like
global
filter.
That's
like
show
only
stable
show
only
edge,
and
then
it
becomes
obvious
to
people
that
there's
like
basically
two
sets
of
info
for
each
individual
component.
B
G
B
Well,
maybe
there's
an
opportunity
to
expose
more
user-facing
things
to
say
you
know
you
know
like
I
guess,
like
what
I'm
saying
is
like
yeah
part
of
that
there
isn't
a
direct
there,
isn't
a
top
level
link
to
the
compatibility
matrix
to
the
thing
that
you're
working
on
right
now?
Yes,
yes,
there's
a
one
sign,
it's
not
because
it's
insignificant
that
info.
The
biggest
reason
is
because,
right
now
it's
a
misnomer
that
page
that
you're,
that
the
integration
tests
are
being
published
on,
it's
called
compatibility
matrix,
but
it
actually
hasn't
published
a
compatibility
matrix.
B
All
it's
done
is
published
integration
tests
aft
it's
from
the
integration
test
data
we
we
could
then
build
a
compatibility
matrix,
saying
yes
measuring
version
version
such
and
such
is
compatible
with
kubernetes
versions
and
such
it's
from
that
data
that
so
we're
kind
of
on
a
journey
to
getting
there.
And
so
that's
why
the
page
isn't
exposed
top
level,
because
it's
kind
of
contributor
details
so
keep
thinking
about
that
same
thought
that
you
have
like.
You
can
begin
to
expose
that
data
in
other
places.
B
If
you
click,
if
you
go
to
any
given
service,
if
you
go
back
to
the
adapters
page,
real
quick
and
you
click
on
one
of
the
adapter
links,
it
should
take
you
to
the
page
for
that.
Okay,
so
here
so,
let's
see
that
stable
link.
Okay,
so
does
that
take
you
to
github
or
what
is
that
yeah?
It
takes
me
to
github.
B
B
But
yeah
the
goal,
the
goal,
the
current
goal-
that
integration
test
page
is
to
have
each
measuring
component
listed
understand
that,
yes,
there
are
two
release
channels
for
each
component:
stable
and
edge
that
yeah
generally
people
okay,
and
that
beyond
that,
optimizing
beyond
that,
probably
we
don't
want
to
do
it
would
just
be.
We
want
to
show
the
latest
edge
and
the
latest
stable
for
each
component.
B
G
G
D
F
A
Actually,
I
think
first,
we
should
focus
more
on
the
back
end
side,
because
we
can
complete
the
front
and
it's
not
being
much
of
an
issue
I
can
do
that
by
next
week,
but
I
think
we
should
mainly
focus
in
back
and
forth.
So
we
can
fast.
You
know,
like
all
those
functionalities,
like
user,
authentication,
validation
and
question
polling
and
all
those.
So
I
think
the
main
focus
should
be
back
and
for
now
which
I
can
take
the
initiative
and
I
would
love
to
work
on
it.
B
So
there's
nice
yeah
there's
a
couple
of
database
tables
to
be
designed,
mesher
cloud
measuring
cloud
as
a
remote
provider
has
the
has
four.
You
know
it.
It
has
the
identity,
the
social
authentication,
the
identity
providers
that
are
that
are
there.
It
has
that
those
secure
mechanisms
what
it
doesn't
have
is.
B
D
Apart
from
that,
another
thing
was
that
scenario
for
sending
out
a
message
to
the
newcomer
after
two
weeks:
I've
checked
it
out
and
it
is
working
like
we
could
set
it
up.
That
is
not
an
issue
for
that.
We
could
connect
it
with
the
existing
google
sheet
that
we
have
and
it
will
filter
it
out
based
on
the
next
two
weeks.