►
From YouTube: Layer5 Websites Meeting (Nov 9th, 2020)
Description
Welcome @_willcodes, and Piyush Thange! A new page for Newcomers presented by @sudo_navendu.
A
We
discuss
anything
related
to
the
left
five
side
projects
on
this
particular
call,
including
the
layer,
5
ng
site,
the
mystery
dockside,
the
meshri
site
you'll
find
links
to
all
of
them
somewhere
in
the
meeting
minutes
in
the
older
meeting
minutes.
If
you
can't
ping
in
the
chat,
if
you
provide
the
links,
the
doc
that
you
can
now
see
on
call
there's
a
link
to
that
in
the
meeting
minutes,
you
should
have
access
to
it
again.
C
B
B
D
D
D
Happy
happy
monday
to
everybody.
Thank
you.
I'm
most,
I'm
mostly
kidding
on
the
critiques.
I'm
good
question,
so
tunisia
understand.
Thank
you
for
demoing
this.
I
understand
it's
a
work
in
progress,
given
the
that
that
you're
working
on
the
maintaining
state
across
the
pages,
the
so
just
thinking
aloud
with
everyone.
I
guess
part
of
the
behavior
here
is
when
you
navigate
to
a
new
page.
D
D
B
D
D
D
D
Okay,
so
no
no
change
in
behavior
really
or
the
pagination
isn't,
based
on
a
strict,
a
static
number
of
blogs
per
page.
Is
it's
potentially
something
to
look
into
because,
like
conceptually,
if
we
just
have
the
number
of
blogs
that
we're
looking
at,
you
might
expect
that
there
might
be
like
six
pages
or
or
there
would
be
more
than
three
yeah?
Actually,
the
problem
with
that
was.
B
Like
what
this
pagination
plugin
from
gatsby
does
is
takes,
it
takes
a
single
p
template
and
renders
it
continuously
so
how
we
are
switching
currently
between
the
grid
view,
and
the
list
view
is
that
we
just
simply
instead
of
changing
the
page,
which
would
change
the
url.
We
are
just
simply
is
switching
out
the
components,
so
the
gatsby
plugin
doesn't
know
that
a
view
has
changed.
It
knows
that
only
that
page
still
exists,
but
inside
the
view
has
changed.
B
D
D
D
And
so
I'm
calling
all
that
out
so
that
because,
as
we
discussed
today,
probably
I
expect
a
large
part
of
our
focus
is
probably
on
well
may
or
may
not
be,
but
is
often
on
this
next
generation
site
know
that
there
are
other
challenges
on
other
sites.
So
a
couple
of
challenges
there's
a
lot
of
challenges
on
the
layer,
5ng
site
because
it's
new
and
has
yet
to
be
published,
but
one
of
them
is
a
redesign
of
the
grid
and
list
view
buttons.
D
B
D
If
we
go
live
with
this
site
relatively
soon,
I
know
tanuge
and
josh
and
anyone
else
going
to
iit
jud
poor
I've
got
exams
this
week.
So
I'm
I'm
really
pleased
that
both
tunisia
and
josh
are
actually
josh
are
actually
on
and
I'll
be
curious.
If
anybody
else
has
got
exams
going
on
this
week
as
well,
but
yeah
it's
a
tuneus,
we
might
want
to
just
press
forth
it.
May
it
might
still
be
the
right
thing
to
do
to
kind
of
wait
for
strappy
for
something
it
could
be.
D
Is
if
you're
not
familiar
with
strappy,
it's
a
piece
of
tech
that
we
are
looking
at
using
there's
a
link
to
it
in
the
chat
content
management
system.
It
is
to
interface
with
gatsby
the
system.
That's
running
layer,
5
ng,
the
site
that
you're
looking
at
right
now
and
it
is
to
be
a
wysiwyg
interface.
It's
to
be
the
in
an
authoring,
an
editing
interface,
primarily
for
the
different
collections
that
have
been
created
on
this
site.
So
blogs
are
a
collection
of
posts
or
the
blog
is
a
collection
of
posts.
B
D
D
D
D
If
we
could
just
change
that
to
programs
and
consolidate
all
three
of
those
that
would
be
nice,
we
also
want
to
go
ahead
and
ax
the
languages
plug-in
or
set,
I'm
pretty
sure,
I'm
pretty
darn
sure
that's
not
going
to
make
the
cut
we.
We
could.
Let's
list
that
as
something
to
chop
and
we'll
say
a
few
words
when
that
happens.
I
know
josh
and
some
others
have
worked
on,
that.
D
We
have
to
one
spread
out
the
buttons
a
little
bit,
they're
sort
of
suffocating
each
other
and
they
might
spread
a
communicable
disease
between
them
if
they,
but
they
also
would
be
nice
if
something
happened
when
people
rolled
over
them
on
the
other
sites
we're
doing
a
it'll
it'll
colorize
the
button,
but
we
don't
have
to
there's
no
requirement
that
the
new
site
look
like
the
old
one.
As
a
matter
of
fact,
that's
a
large
part
of
the
point
that
it
doesn't.
D
A
A
A
G
Okay,
so,
basically,
first
of
all,
I
shifted
the
three
card
design
to
the
four
card
design
in
the
members
page
and
before
we
had
the
same
card
that
we
had
outside
inside
the
profile
page
for
everyone,
and
I've
shifted
it
to
this
format,
as
suggested
by
lee,
and
I've
added
four
new
fields.
First,
is
the
location.
G
E
G
E
The
heading
and
the
subheading,
you
can
just
add
yeah
yeah,
so
basically
you
can
just
add
it
like
it
differentiates
between
the
title
and
the
body
or
something
so
like.
After
the
name
and
the
contributor
designation,
you
can
just
add
a
horizontal
line,
not
a
full
size
but
somewhere.
So
it's
it's
basically
part
of
design
not
for
differentiating
but
yeah.
So
that's
a
few
things
that,
like
can
be
added
for
a
better,
better
design.
All
that
can
say:
okay,
yeah.
E
C
D
As
a
matter
of
fact,
I'm
sure
that
that's
the
case,
which
means
that
every
person
on
this
call
most
of
you
have
not
can
had
a
chance
or
have
taken
the
time
to
contribute
to
this
site
or
to
using
gatsby
there's
a
there
are,
and
actually
two
news
or
whomever
is
sharing
vanayack.
Maybe
you
could
show
those
issues
and
people
go
pick
them
up.
D
For
myself
for
me
to
have
gone
through
and
just
listed,
all
the
linkedin
profiles
on
all
of
them
would
have
been
less
time
probably,
but
is
I'm
actually
doing
it
to
help
encourage
folks?
I
know
that
there's
a
number
of
people
on
this
call
who
don't
know
what
gatsby
is.
But
I
know
that
for
sure
that
each
of
those
people
that
don't
they
could
go
make
this
update,
because
it's
just
a
one-line
thing
and
that
would
and
force
them
to
go
through
the
process
of
building
the
site
and
beginning
to
become
comfortable.
D
E
D
The
master
branch
is
the
one
that
has
the
current
layer
5.io
website,
that's
based
on
jekyll
there's
another
branch
called
layer,
5,
hyphen,
ng,
ng,
just
being
next
generation
like
the
next
version
that
next
version
actually
actually
is
not
based
on
jackal
it's.
What
vinayak
and
tanuj
were
just
sharing
it's
based
on
gatsby,
yet
both
sites
are
in
the
same
repo.
D
If
you're
curious
as
to
why
that
is
I'll,
explain
that
to
come
ping
me
and
I'll.
Explain
it
to
you
at
some
point,
the
the
master
branch
will
be
will
go
away
and
the
site
will
just
or
I'm
sorry
the
repo
will
just
be
lair.
Five
ng-
and
so
I
I
mention
this
because
josh
and
the
collection
of
all
of
you
that
are
maintaining
the
two
sites
are
having
to
we'll
do
just
that
you're
having
to
maintain
changes
in
both
and
anymore.
D
We
want
to
try
to
optimize
for
changes
going
into
layer,
5,
ng
and
trying
to
get
that
site
live.
There's
a
couple
of
things
that
we
do
have
to
update
on
the
current
site.
Just
based
on
timing.
Like
hey
we're,
I
think
we're
speaking
this
week
at
a
conference
we're
speaking
next
week.
I
think
it's
next
week
at
another
conference,
and
so
small
updates
need
to
go
on
to
the
current
site,
to
let
people
know
of
our
activities,
but
really
any
and
like
to
the
extent
that
we
can.
D
D
E
E
Oh,
like
any
of
the
github
or
any
links,
yeah
yeah,
so
I'm
I
was
talking
about
this
issue
that
the
the
click
on
links
also
directs
it
to
the
individual
page
and
not
to
those
links,
but
right
clicks
do,
but
the
left
clicks
don't
so.
I
think
the
on
over
effect
on
click
effect
of
the
card
is
like
dominating
over
the
effect
of
the
social
links
on
this
component.
C
D
All
right
that
sounds
like
a
bug,
yeah
a
couple
things
yeah.
So
to
do
news
raises
up
an
interesting
thing.
I
think
for
people
to
give
some
consideration
to.
I
guess
it's
kind
of
an
open
question
for
for
everyone
on
the
call
like
do
you
consider
that
at
like?
Well
one
do
you
consider
that
these
are
getting
a
little
skinny?
D
If
we
look
even
with
javier's
name
that,
if
that's
the
case
there
might
be
some
extra
room,
some
room
to
be
removed
here,
maybe
you
know
just
maybe
that's
enough
to
bring
it
back
into
order.
I
don't
know
otherwise.
Tunisia's
open
question
is
like
hey.
You
know
these.
These
links
they're
going
to
be
potentially
repetitive
of
what
you'll
find
here.
D
That's
true,
a
comment
that
I'll
place
on
that
is.
That
is
that,
if
we
do
remove
these,
this
in
particular,
is
something
of
a
well
I'd,
say
something
of
a
badge
of
honor.
This
is
represents
quite
a
bit
of
work
from
these
individuals,
and
so
it
might
be
nice
to
be
able
to
capture
it
somewhere.
Maybe
it
just
overlays.
D
You
know
on
the
but
it'd
be
nice
like
if
you're,
if
you're
going
to
fil,
and
it
could
be
kind
of
the
same
thing
for
maintainers
as
well.
We
don't
have
a
desi,
a
visual
designation
for
that,
but
that,
like
yeah,
there's
some
badges
that
I
would
say,
people
have
certainly
earned
that
nice
to
show
somewhere.
I
J
D
Yeah,
that's
a
good,
that's
an
interesting
thought
here.
Let
me
bring
up
a
site
that
I
think
does
kind
of
that
which
is
hey.
There's
a
collection
of
individuals.
They've
got
social
links.
I
if
you
click
their
picture,
you
get
a
modal
and
you
get
an
overlay
and
it
looks
decent.
I
think
some
of
them
are
longer
than
others.
H
K
A
Yeah,
the
social
buttons
are
fine.
When
you
click
on
any
particular
member
page,
they
could
maybe
have
the
time
zone
of
the
particular
member
or
what
they're
good
with
or
what
they're
working
with
in
lay
five.
That
way,
you
won't
have
to
change
the
entire
grid
view.
They'll
still
have
a
page,
and
yes,
I
agree
with
the
zeus.
The
having
an
individual
link
to
every
member
makes
sense
because
they
can
point
back
to
it
whenever
they
want.
L
Yeah
hi
guys,
like
I'm
yash,
agarwal
and
studying
in
iit
body,
finally
graduate
undergraduate
and
like
yeah,
I
just
joined
one
more
meeting
before
I
think
before
I'm,
I
think,
15
or
20
days
before,
like
where
I
present
my
graph
space,
part
and
yeah.
So
today,
like
I
joined
one
more
time,
yeah
and
yeah.
Definitely
I
will
start
contributing
from
the
december
part,
but
he
told
me
to
ramp
up
in
the
month
of
november
to
get
familiar
with
all
these
things.
L
A
M
M
D
D
D
D
D
Yeah,
I
know
I
do
it
every
time,
there's
a
link
to
the
new
there's
like
a
hashtag
newcomers.
I
think
like
we're
mentioning
the
newcomers
channel
down
below,
which
is
great
there's
a
bit
of
a.
I
don't
know
that
it's
obvious
to
everyone.
It
wasn't
to
me,
but
inside
of
slack
I
think
whether
you're
in
the
app
or
the
web
page
you
can
right
click
on
a
channel.
D
D
D
Thank
you
for
this.
This
is
it's
not
hey.
I
know
you've
only
been
around
for
just
a
short
little
while,
but
you're
already
showing
off
some
nice
work
a
whole
new
page,
one
that
will
be
highly
referenced.
I'm
not
there's
no
doubt
in
my
mind.
You
actually
have
some
great
test
testers
if
you
will
on
the
call,
so
so
like
wilfred
and
piyush
and
josh.
D
Some
of
they
might
have
been
through
some
of
this
content
before,
but
but
a
lot
of
it
should
still
be
fairly
fresh
for
them.
So
between
the
three
of
them,
would
you
mind
point
pointing
your
pr
out
to
them
that
would
give
them
an
opportunity
to
give
you
some
great
feedback
as
well
as
for
them
to
get
into
kind
of
a
review
mode.
D
I'm
not
sure
if
it's
obvious
to
everyone
on
the
call,
but
everyone
that
is
here
is
certainly
welcome
to
review
pull
requests
one.
It
can
be
a
bit
of
work
for
a
small
few
if
they're
the
only
ones
providing
review,
but
then
two
by
reviewing
others
work.
It's
an
excellent
way
to
to
learn
because
you
get
because
you
get
to
look
at
the
code
and
see
what
it's
doing.
You
know
under
a
confined
use
case
without
having
had
to
take
on
the
challenge
of
actually
creating
that
code.
H
H
D
Well,
maybe
we
should
I
mean
we
should
talk
about
that
yeah
jesus,
I
don't.
I
don't
think
that's
a
great
that's
a
great
suggestion.
I
don't.
I
don't
know
that
we've
we've,
I
think
a
lot
of
you
will
notice
that
we
use
google
docs.
We
have
a
community
shared
drive
and
there's
a
lot
of
things
and
there's
a
lot
of
website
assets,
a
lot
of
svgs
and
logos
and
docs
the
meeting
minutes
that
we're
looking
at
and
sharing
today.
D
In
part,
we
use
google
docs
because
it's
a
real-time
collaboration
tool
which
really
helps
an
asynchronous
collaboration
tool.
It's
a
good
review
to
all
the
things,
but
it's
also
quicker
to
get
some
information
online,
but
over
time
to
jesus's
point
like
the
the
webs,
the
welcome
guy,
the
layer
5
welcome,
guide,
it's
been
pretty
static
for
a
while
and
it
can
be.
D
D
It's
you
can
actually
remember:
oh
yeah,
hey
it's
a
layer,
five
io
community
newcomers
or
community
welcome
or
just
layer,
five
io
community
and-
and
that
is
an
index
that
should
have
a
link
to
newcomers.
It
should
have
a
link
to
as
opposed
to
and
if
there's
a
layer,
5
ao
community
welcome,
or
you
can
actually
remember
that,
because
it's
english
as
opposed
to
some
really
long,
github
or
google
doc
mumbo
jumbo
in
the
url
that
you
could
never
remember.
D
I
guess
part
part
of
my
point
is
like
hey
it's
it's.
That
makes
some
sense.
Your
suggestion
makes
sense
from
that
perspective.
Jesus.
It
also
makes
sense
from
the
perspective
that,
while
it
was
easy
enough
up
front
to
publish
that
information
into
a
google
doc
and
then
change
it
and
change
it
and
change
it
after
some
time
that
information
has
congealed
and
the
updates
to
it
are
infrequent
and
so
yeah.
D
I
think
it
would
give
the
it
would
give
layer,
five
and
the
layer,
five
io
site,
even
more
of
a
community,
feel
like
there
are
a
number
of
pictures
and
things
that
we've
taken
and
people
that
have
spoken
on
stage
or
written
blog
posts
or
gotten
jobs
or
other
like
there's
those
or
like
people
that
have
given
workshops.
You
know
to
new
contributors
like
that.
It
would
be
nice
to
get
some
of
that
up
as
well
like
when
we're.
You
know
we
have
the
generic
navindu
like
right.
D
Now
you
have
the
generic
graphic
with
the
question
mark
and
the
the
two
people
that
I
suspect
came
from.
Is
it
undraw
that
site
probably
yeah
yeah?
That's
that's
a
modern
looking
flat.
You
know,
can
you
know
it's
contemporary
style?
It
also
looks
just
like
it
came
from
andra,
because
you
and
I
didn't
talk.
I
didn't
know
that
you'd
done
that,
but
but
but
like
it
looks
good
and
it
also
looks
totally
generic
and
in
some
respects
like
it's
fine,
we
want
it
to
be
generic,
it's
not!
D
I
guess
my
point.
My
point
is
this
is
a
great
initiative.
We
should
make
things
a
bit
personal.
We
really
do
try
to
make
it
personal,
which
I
think
is
awkward
for
some
people
who
will
join
the
call.
It's
like
wait.
A
second
I
just
wanted
to
hang
out
in
the
background,
stop
calling
me
out
that
makes
me
uncomfortable,
which
I
it's
unfortunate.
F
D
For
us
in
many
respects,
the
layer
five
io
site
wasn't
is
intended
to
be,
and
itself
is
intended
to
be
an
awesome
repository
of
service
mesh
things
right
now.
It's
not
like
the
the
new
site
is
set
up
to
be
that
way.
We
will
have
thousands
of
pages
soon
after
that
site
goes
live,
but
until
then,
maybe
it
makes
sense
to
have
a
github
repo.
That
is
an
awesome
service.
Mesh
repo.
K
B
I
C
E
A
A
We
already
asked
a
particular
person
shankar
ghosh,
to
work
on
it
haven't
had
a
reply
from
yet,
though
so,
if
anybody
else
is
wanting
to
work
on
it,
please
come
talk
to
me
all
possible
links
that
you
need
to
get
familiar
with.
The
issue
are
provided
in
the
media
minutes,
so
go
ahead,
have
a
look
and
if
it
interests
you
get
back
to
me,
nicole,
you
can
go
ahead.
E
Is
it
busy
yep?
So
I
was
working
on
the
announcement
of
this
page,
so
I've
made
few
modifications
not
completely.
I
just
want
to
feedback
if
that's
good
or
I
should
refer
back
like
I've
changed
few
colors.
She
added
this
icon
in
the
timeline
button.
Like
content,
icon
itself,
I
don't
know
if
this
looks
good,
I
shall
remove
it
as
well.
E
E
E
D
Yeah,
so
sorry,
since
we're
low
on
time,
I
won't
stop
making
jokes
and
say:
oh
my
gosh,
thank
you
for
putting
the
for
organizing
the
information
into
menus
like
yeah
that
that
was
nice.
You've
still
got
the
call
out
for
people
to
submit
an
issue.
That's
nice
as
well.
At
some
point,
I
guess
it
still
makes
sense
for
them
to
submit
an
issue
yeah,
it's
still
very
much
a
community
curated
thing
the
smi
table
is
probably
forthcoming.
D
The
on
the
the
timeline
yeah:
this
is
an
interesting
thought.
Well,
one
item
with
the
timeline
is
that
it
takes
up.
I
don't
know
I'm
up
two
minds:
it
takes
up
a
lot
of
room,
but
which
is
I'm
saying
that
as
a
negative
that
on
the
positive
side
is
like
well,
people
are
able
to
walk
through
the
timeline,
because
it's
just
so
they
sort
of
take
it
in
as
they
go,
and
I
think
that's
helpful.
It's
not
overwhelming.
In
that
sense,
it
is
an
interesting
thing.
D
If
the
icon,
the
project
logo,
does
go
into
the
bubble
itself.
The
then
what's
left
is
the
date
that
that
occurred
and
potentially
the
name,
but
if
the
logo
does
a
good
enough
job
and
it's
self-identi.
Actually
I
don't
know
that
all
the
logos
are
self-identifiable
like
network
service
mesh,
for
example.
We
would
probably
want
to
have
still
have
the
date
plus
capture
the
name
and
so
yeah
the
tool,
the
the
call
outs,
the
tool
tips.
So
what
you
know
the
persistent
tool
tips,
if
you
will
those
labels
they
we
yeah.
D
D
But
this
is
an
interesting
thing.
Maybe
what
it
would
be
is
like:
hey,
let's
go
ahead
and
remove
the
large.
I
called
it
a
tool
tip
just
now,
but
it
the
the
large
label.
If
that's
removed,
you
get
a
lot
of
space
back.
That
might
mean
that
we
could
open
up
the
bubble.
A
little
bit,
maybe
make
the
timeline
thicker
open
up
the
bubble,
a
little
bit
to
give
space
to
the
logo
and
then
just
have
the
the
annotation
that's
coming
off.
The
timeline
is
just
the
name
and
the
date.
E
D
Oh
wow,
okay,
that's
pretty
cool
yeah,
because
then
it
could
have
a
short,
a
brief
description,
potentially
as
well
like
it
wouldn't
have
to
have
the
date
and
it
wouldn't
it.
It
could
be
a
bit
dense
because
people
are
already
getting
the
visually
attractive
view
and
the
over
the
bird's
eye
view
and
when
they
hover
they
are
expecting
and
anticipating
a
bit
more
de
info,
like.
E
D
Yeah
so
yeah,
if
it
doesn't
fit
like
that,
probably
the
horizontal
suggestion
is
probably
a
bad
one.
Yeah,
I
guess
you'd
have
to
be
you'd,
have
to
have
a
frame
that
you
scroll
through,
maybe
not
the
maybe
not
the
best
suggestion
and
plus
it's
just
more
work
and
so
leaving
it
vertical
is
probably
the
right
thing
to
do.
E
D
D
D
E
E
D
E
D
D
Or
you
know
how
you
know
how,
when
you
I'll,
send
you
a
link
to
an
example
like
if
you
go
to
the
layer,
five
io
slash
meshery
that
table
it
the
table
of
many
service
meshes.
It
just
has
a
light
background.
Coloring
that'll
occur
as
you,
even
though
it
doesn't
like
you.
Can
it's
not
like
you
can
click
on
a
blank
area
of
the
row,
but
it's
just
for
effect.
It's
just
to
make
people
feel
nice.
L
E
D
E
D
D
D
And
then
I'll
say
shiva's
name
a
couple
of
more
times
see
if
shiva.
If
you
have
a
mega
menu
update,
I
would
love
to
hear
it
and
then
there's
one
last
one
on
austin.
You,
I
think,
had
a
second
go
at
design
for
the
service
mesh
trail
map.
If
you
will,
I
I
haven't
looked
at
it,
it
might
be
nice
to
show
it
here
if
you've
got
it
handy.
C
C
F
D
There
was
merit
to
the
crumbs
somewhere.
I
don't
it
might
be
one
of
those
things
that
that
we
would
comment
out
to
potentially
bring
back
at
some
point,
because
what
might
end
up
happening
is
that
here
we're
conceptually
three
deep
and
if
there's
a
community
newcomers
and
if
there's
a
community
newcomers
welcome,
it
might
be
that
we
would
be
4d
like
there's
now
granted.
As
I
say
this,
it's
not
the
best
user
experience
to
sh.
To
sometimes
show
bread
comes
and
sometimes
not
it
might
be.
It
might
be
too
early
to
call
hulk.
D
D
So
then
the
other
and
navindo
had
asked
hey.
Is
there
a
date
for
when
layer,
5
ng
might
go,
live
and
I'd
like
to
set
one?
I
feel
like
I
feel
like
for
my
part,
I'm
not
necessarily
in
control
of
what
that
might
be
I'd
like
for
us
to
start
optimizing
a
bit
toward
that.
That
might
mean
pulling
some
things
out
or.
D
Don't
end
up
having
everything
on
the
first
release
on
its
go
live
but
but
there
may
be
a,
but
at
some
point
there
will
be
enough
to
go
live.
There's
a
couple
of
couple
of
things
that
we
kind
of
need
before
we
go
live,
so
one
is
an
understanding
of
how
it
is
that
we
switch
these
out
like
how
easy
is
it
to
change
these
call
outs
per
per
menu?
You
know
per
top
level
menu.
G
So
I
just
had
one
other
question
that
are
you
also
trying
to
somehow
manage
like
the
breadcrumbs
that
you
just
spoke
about
with
the
mega
menu
so
because,
like
as
you
showed
right
now
that
let's
say
there
was
like
the
community
section,
which
was
two
layers
deep.
So
is
that
something
also
we
should
have
in
the
menu
itself,
or
that
would
be
something
that
would
be
shown
later
like
once
we
go
to
one
of
the
other
menu.
Some.
D
G
D
I
think
there's.
That
is
an
interesting
question.
I
I
do
know
that
there's
one
use
case
for
a
significantly
different
menu
or
to
it
can
be
the
same
menu
component,
but
it
would
be
a
significantly
different
choices
and
that
use
case
is
a
basically
a
whole
section
of
the
site
for
learning
and
for
working
on
labs.
D
We
refer
to
it
as
learn.layer5.io
yeah
that
whole
section
like
we
want
it
to
feel
like
they're
on
the
same
site.
Yet
there
will
be
so
much
to
show
them
because
there
will
be
individual
courses,
every
there'll,
be
learning
paths
with
courses
and
each
course
will
have
labs
and,
like
it'll,
be
dense,
and
it
might
be
a
better
user
experience
if
the
mega
menu
is
yeah.
G
Yeah
and
just
like
you,
since
you
were
talking
about
the
menu
items
that
you
see
on
the
right
hand,
side
the
two
different
blog
style
links.
Can
we
like
probably
get
the
content
that
needs
to
be
filled
out
for
each
one
of
them
so
that
we
can
get
that
replaced
since
everything
is
like
all
the
other
menu
items
are
showing
the
same
two
links
all
right.
D
I'm
taking
I'm
taking
a
note,
yeah
I'll
I'll.
Do
that
provide
the
content,
understanding
that
that's
some
like,
ideally
well,
yeah
yeah
yeah.
Ideally
it
would
be
nice
if
there
was
a
system
wherein
we
could
use
a
an
annotate,
an
attribute,
an
annotation,
a
label
or
something
on
like
for
a
given
block
for
a
given
menu
top
level
menu.
D
Like
let's
say
you
know,
let's
say
that
we've
got
projects
and
blogs.
Okay,
well,
which
project
which
two
projects
do
we
want
to
highlight?
Well,
let's
just
set
a
flag,
a
label
on
two
of
the
projects
and
the
mega
menu
would
iterate
through
that,
would
you
know,
go!
Do
a
quick
query,
identify
two
that
carry
that
flag
and
show
them.
D
I
guess
what
I'm
saying
is
like
we're
going
to
know
understanding
that
we're
going
to
need
to
change
this
out.
Ideally,
it
would
be
a
little
bit
dynamic.
We
still
want
to
control
it,
but
it
does.
We
will
want
to
frequently
change
it
like
if,
if
there's
an
events
top
level
menu-
and
you
hover,
like
those
events,
will
change
you
know
every
month.
D
D
It
doesn't
have
to
be
news
news.
It
might
be
a
new
blog
post
or
we're
speaking
here
or
there's
a
new
project,
whatever
it's
just
an
announcements
area
that
I'm
bringing
up
as
a
related
concept
that
hey,
I
think,
josh
and
tunisian
everybody.
I
think
we
need
an
announcements
area,
one,
but
then
two,
the
mechanics
by
which
we
determine
what
content
is
going
to
show
in
the
announcements
area,
could
be
a
very
similar
mechanism
for
determining
what
content
to
show
in
the
mega
menu.
What
exploded
content
to
show.
D
Cool
we're
way
over
time.
I
know
this.
I
wanted
to
make
sure
to
give
austin
a
moment
to
show
an
idea.
I
it's
very
frequently
asked
by
anyone.
That's
looking
at
adopting
a
piece
of
technology
like
a
service
mesh.
The
question
is
like
hey:
when
when
should
I
implement
a
service
mesh,
or
how
do
I
know
when
it's
time
like
is
this
is
a
service
mesh?
Is
it
worth
it
to
me
to
go,
deploy
it
and
it's
one
of
those
answers?
D
D
C
So
sorry
about
that's
that
subscriber
every
time
everyone
over
the
past
one
week,
we
we
tried
creating
epm
page
for
the
github
issue
that
was
raised
about.
When
should
I
deploy
service
mesh?
When
do
I
know,
I
need
a
service
mesh
so
with
the
issues
will
to
create
something
and
something
very
nice
for
the
users
and
for
us
to
ourselves.
C
So
first
we
started
with
an
eu
the
euro
section,
and
then
we
gave
a
brief
discussion
about
what
service
mesh
is
and-
and
my
idea
is
on
this-
this
section
when
the
service
mesh
has
been
explained.
Maybe
you
can
click
on
the
image
or
little
button
to
download
a
pdf
for
edf
containing
water
service
mesh
is
then
factors
to
consider
when
adopting
or
to
consider
when
and
why
it's
in
a
service
match.
Then
we
brought
up
the
card
like
structure.
C
So
when
someone
overs
on
this,
they
respond
and
maybe
scale
or
or
glue
a
bit
and
have
a
little
bit
of
interaction.
So
the
user
knows
okay,
there's
something
here,
and
maybe
we
could
direct
them
to
a
section
or
a
different
page,
for
example,
when
they
are
clicked,
they
go
to
a
different
page
for
a
better
understanding
of
that
factor
and
then
or
when
they
click
they
give
you
they
go
to
this
section.
C
If
the
click
number
of
service
same
thing
gives
you,
then
observability
gives
you
a
visualization
of
what
alterability
is
about
and
the
factors
to
consider
then
a
very
critical
session,
which
we
added
was
do
you
need
a
service
mesh,
because
maybe
someone
might
still
feel
okay.
I
still
don't
understand
why
and
the
service
mesh,
so
this
section
is
going
to
be
like
a
q
and
a
section
and
when
the
user
clicks
yeah,
it
takes
them
to
a
section
like
this
because
on
the
github
issue-
and
it
was
proposed
for
a
air
table
form.
C
So
this
idea
was:
we
went
with
this
idea
so
anything
when
the
user
comes
here.
We
give
maybe
about
eight
to
ten
questions
and
the
user
enters
these
our
answers
and
we
get
give
them
feedback
and
when
they
are
done
answering
the
question
they
return
back
to
the
page,
and
then
we
now
give
them.
When
should
I
implement
a
service
make
another
short
survey
this
time
all
they
have
to
do
is
just
play
with
the
range
like
you
just
draw
a
slider
service
communication
address,
like
that.
C
We
know
how
how
and
severe
your
consent
is
and
when
you're
done
with
all
these
surveys,
we
provide
you
with
with
an
answer,
maybe
like
after
a
little
spinner
yeah
provide
you
with
an
answer.
They
will
say,
get
started,
and
that
is
the
sign
up
for
service
mesh
using
the
service
mesh
and
then,
if,
after,
if
they
do
proceed
to
sign
up,
we
we
we
move
to
a
different
page,
but
if
they
don't,
we
then
move
to
getting
them
as
subscribers
or
getting
their
concerns.
C
D
E
Yeah,
the
when
you
require
service
mesh
thing
is
like
a
pretty
different
and
yeah
like,
but
I
didn't
like
much
of
understand
the
the
later
part
in
that
like
where
there
was
some
bars
representing
some
percentages
for
those
observability
and
other
factors.
So
like.
I
think
we
don't
we'll
be
using
those
things
or
something
like
there's.
D
A
little
more
explanation
needed
as
to
I
think
the
one
a
little
more
explanation
needed
to
the
user
as
to
how
if
observability
is
important
to
them.
How
much
does
that
factor
in
and
weigh
on
their
decision
to
use
a
service
mesh?
What
in
part
was?
Maybe
the
part
of
the
missing
link
there
is
that
those
slider
bars
wouldn't
necessarily
be
shown,
or
they
wouldn't
be
shown
to
the
user
until
the
user
has
filled
in
the
survey.
D
D
D
Do
you
have
do
your
services
have
a
lot
of
communication
between
them,
which
would
be
this?
You
have
high
inter-service
communication
or
in
your
environment.
Do
you
have
low
inter-service
communication
and
people
like
in
the
questionnaire
that
air
table
which,
by
the
way,
ideally
we
don't
actually
literally
use
an
air
table,
because
the
thing
is
is
that
looks
just
like
buoyant
stuff
and
it
basically
looks
like
a
ripoff
of
buoyancy
stuff
and
that's
not
what
we
want,
not
that
we
can't
write
our
own
form.
D
We
can
part
of
actually
answering
the
questions
might
be
presenting
them
a
slider,
so,
instead
of
them
answering
filling
in
a
form,
they
move
the
slider
to
say
well,
actually
we
do
have
high
inter-service
communication
and
the
results
of
that
of
them.
Having
slid
the
bar
over
saying,
oh
yeah,
we
have
a
lot
is
then
that
we
would
give
them
in
the
report.
D
We
can
still
have
a
section
like
this
that
talks
about
how
a
service
mesh
facilitates
inter-service
communication,
and
what
does
that
mean?
We
can
explain
what
does
that
mean
to
them,
but
in,
but
these
three
things
here
are
really
part
of
the
question,
because
the
question
is:
are
you
in
a
low
or
a
high
environment
and
depending
upon
which
one
we're
going
to
give
you
some
feedback
on
that?
How
meaningful
it
is?
It's
it's
actually
the
whoops,
it's
the
same
thing
for
the
other.
D
For
this,
it's
like
hey!
How
many
services
do
you
have?
Do
you
just
have
a
few,
or
do
you
have
a
lot?
If
you
have
a
lot,
you
need
a
mesh.
If
you
don't,
you
know
like
we're
going
to
give
them
the
response.
So
it's
okay
to
expl.
You
know
like
talk
about
some
things
here,
but
but
this
was
these.
This
was
intended
to
be
the
question
like
the
question.
The
question
is:
do
you
have
a
few
or
a
lot?
D
The
same
thing
here
is
like
did
this
actually
does
the
job
of
explaining
the
fact
that
service
meshes
provide
a
lot
of
insight
with
little
effort?
Like
this
is
fine,
this
is
like
a
marketing
pitch
for
the
value
of
a
mesh,
but
these
two
would
need
to
be
refactored
to
just
talk
about
the
value,
not
the,
because
this
this
will
go
into
the
questionnaire.
The
questionnaire
is
great,
like
this
looks.
This
is
pretty.
This
is
great.
D
D
D
D
It
would
take
more
infrastructure
on
our
end,
to
give
them
a
to
persist.
Their
report
we'll
have
to
not
to
think
about
that,
but
a
lot
of
good
stuff
in
here
really
the
only
thing
to
potentially
iterate
on,
is
just
these
two
sections
of
like
changing
them
into
a
section
that
talks
about
the
the
fact
that
there's
value-
and
I
I
need
to
provide
you
probably
some
of
this
content,
but
that
there's
value
when
you
have
when
you're
working
with
a
lot
of
services.