►
From YouTube: Layer5 Websites Weekly Meeting (July 7th, 2020)
Description
Building the new layer5.io.
C
B
B
B
B
A
few
topics
one
is
we
can
start
on
because
mccool
is
on
and
so
is
tanooz
who's
been
working
on
this
a
little
while
ago
we
were
discussing
the
notion
of
moving
of
consolidating
repositories
so
moving
the
layer,
5
and
g
code
into
the
layer,
5
repo,
which
had
been
kind
of
the
more
or
less
like
the
plan.
All
along
that
the
layer,
5
ng
repo
is
kind
of
a
temporary
holding
space
for
us
to
become
familiar
with
gatsby
and
try
things
out,
and
it
looks
like
we're.
B
B
C
C
C
C
B
D
B
Oh
okay
got
it
so
so
you're
saying
hey.
Look
when
the
the
way
that
the
the
way
that
the
new
netlafite
netlify
site
is
configured
is
that
it's
going
to
be
pointing
to
this
repository
or
this
directory
right
here
expecting
to
find
the
the
whole
site
right,
yeah,
okay,
and
so
I
think,
okay
and
then
of
what
mccool
is
saying,
something:
we're
cool.
C
C
B
B
I
guess
yeah,
that's
that's!
Maybe
this
is
a
bad
question
to
so,
just
maybe
to
refresh
my
memory,
the
netlify
we're
just
looking
forward
to
do
site
previews,
so
so
long
as
it
retrieves
from
the
correct
source
location,
it's
going
to
build
the
site,
deploy
it
into
a
space
that
netlify
runs
and
beyond
that
we
don't
care
so
much
about
any.
I
guess
anything
beyond
that:
right,
yeah,
okay,
okay,
which
is
good.
So
that
means
that
probably
the
netlify
builds
have
they
been
working
at
all
tanoosh
yeah,
it's
working.
B
D
B
B
That's
when
we
would
manipulate
either
switching
to
a
different
branch
as
being
the
published
branch
or
like
refactoring
the
site,
such
that
all
of
the
old
layer.
5
stuff
is
shoved
into
a
different
folder,
while
the
new
layer,
5
the
next
gen
stuff,
is
pulled
out
of
this
folder
and
made
maybe
at
the
root.
E
E
So
if
they,
if
either
we
downgrade
to
jekyll
3.8
or
something
or
they
upload
a
new
version,
we
could
easily
have
a
central
point
for
our
blog
and
we
can
like
filter
out.
According
to
the
tags
we
have
for
each
block
to
allow
suppose
you
have
a
central
database
of
strappy.
Where
you
put
all
your
blocks,
then
it
also
has
tags
about
which
what
it
is
about
measuring,
cli,
whatever
it
is
about,
then.
E
E
E
B
Right
yeah,
because
yeah
four
has
been
out
for
a
little
while.
So
let
me
let
me
regurgitate-
maybe
what's
part
of
the
potential
value
for
us
here,
maybe
two
so
one
being
as
like
right
now.
I
think
one
of
the
things
that
tanush
has
taken
a
look
at
this
last
week
is
how
it
is
that
we
can
set
up
our
current
markdown
files,
like
our
current
blog
posts
or
project
pages
or
whatever
our
content
and
use
and
set
up
gatsby
such
that
that
content
is
or
gatsby
is
treating
those
markdown
files.
B
B
between
the
docs
from
between
the
three
jekyll
sites
that
we
have
and
potentially
soon
to
be.
Fourth
from
sriti
and
muskin
that
through
strappy,
we
could
have
one
set
of
markdown
files
leveraged
as
a
data
source
across
the
multiple
sites,
and
that
that's
intriguing
and
that
that
can
be
really
helpful.
There's
a
few
areas
where
it's
been
a
little
bit:
it's
not
not
painful.
It's
just
been
a
little
bit
annoying
that
that
we
have
community
members
is
an
example.
B
B
I
think
the
adapter
information
is
stored
three
times,
so
one
is
here
on
layer,
five
io
that
explains
measuring
another
one
is
on
mastery
itself
or
measuring
io
here.
Another
one,
I
think,
is
on
the
you
know:
docs.measuring
io,
and
it's
not
like
it's
the
end
of
the
world.
It's
just
it
would
be
convenient.
If-
and
I.
B
Yeah
yeah,
it
will
get
into
yeah.
I
mean
because
at
some
point
like
we
may
even
want
if
we
get
far
enough
along,
it
would
be
ideal
if
some
of
this
was
automated
like
like
th
this,
that
what
version
we're
supporting
of
this
of
a
service
mesh,
really
that
should
be
defined
inside
the
adapter
repo
for
inside
the
repo
for
one
of
each
individual
adapter.
We
should
be
able
to
read
from
there
and
say
that's
a
little
bit
advanced
and
we,
if
it's
hard,
we
won't.
We
don't
need
to
work
on
that.
B
E
Probably
what
we
would
need
to
do
is
we
need
to
make
one
more
admin
account
for
each
of
the
repos,
which
will
upload
or
change
the
data
rather
of
that
particular
component.
Let's
say
the
component
is
adapters
and
which
stores
different
type
of
adapters,
and
we
link
it
with
a
tag
which,
if
we
wanted
time
to
segregate
them,
not
in
this
case
but
in
case
of
blocks,
I
think
and
then
yeah.
Basically,
then
our
jekyll
site
would
fetch
data
from
it.
If
we
have
a
webhook,
then
they
will
know
whenever
something
has
changed
yeah.
B
B
You
can
create
a
quick
issue
and
ruth
some
of
the
other
contributors
will,
I
suspect,
jump
all
over
it.
We've
been
lucky
with
having
a
number
of
new
contributors
that
want
to
take
on
those
as
a
matter
of
fact,
as
a
matter
of
fact,
they're
being
taken
on
pretty
aggressively,
okay,
good,
so
dhruv,
I
guess
you
know,
since
we've
got
you
talking
and
kind
of
on
the
subject
of
strappy.
E
F
G
H
B
B
G
Yep,
I
have
I've
been
going
through
it
and
there's
a
few
insights
which
might
make
sense.
You
know
there's
some
user
flows
like
from
from
the
starting
page
from
the
landing
page.
What
pages
do
users
visit
the
most
and
I
feel
like
that,
could
help
decipher
some
kind
of
information
which
we
could
leverage.
So
I'm
going
to
check
that.
G
B
Yeah,
it's
always
interesting
to
me
to
see
the
keywords
that
land
people
on
the
site,
some
of
which
are
it's
not
that
they're
unintended.
It's
that
some
of
them,
I
think,
literally,
we
don't
have
one
or
two
of
those
words,
and
maybe
we
should,
but
I
think,
a
lot
a
lot
of
times.
People
are
organically
or
when
they
are
finding
the
site
through
search
term.
It
seems
like
a
lot
of
times.
G
B
And
that's
probably
because
when
they're
searching
for
other
things
that
we
you
know
the
landscape
is
for
that,
but
when
they
are
searching
for
other
things
like
service
mesh
interface
or
other
keywords
that
we
have,
that
we
rank
so
low
that
they
don't
actually
make
it
there
and
so
yeah,
but
that's
changing
some
and
so
on.
Last
friday's
community
call
sriti.
You
gave
an
update
about
some
of
the
new
content
on
the
existing
layer,
5
site.
B
H
H
So
if
anybody
is
interested
in
either
volunteering
to
get
a
post
out
there
or
looking
to
put
some
content
on
the
live
site,
please
do
contact
me.
This
is
a
great
way
to
get
lifi
more
well
known
and
you
can
have
a
look
at
the
blogs
we
have
up
so
far.
I
think
we
had
four
or
five
new
blog
posts
this
week
itself.
H
B
B
H
B
B
Okay,
actually,
in
some
respects,
nikhil
took
on.
I
think
what
this
was
intended
to
be,
which
is
to
say
that
today,
when
you
you
come
here
and
the
convention,
a
lot
of
times
is
when
someone
wants
to
contribute.
So
sometimes
you
know
the
the
readme
will
talk
about
that
or
maybe
point
people
to
contributing
and-
and
here
when
we,
this
hyperlink
takes
you
to
this
contributing
markdown
right
here,
and
the
convention
is
just
that
you
would
have
a
file
of
a
certain
name
in
the
root
directory.
B
As
a
matter
of
fact,
github
even
reinforces
that
convention.
If
you
go
to
insights
on
any
repo,
I
think
under
community
they'll
give
you
that
repo
or
this
community,
if
you
will
a
score
saying
oh,
do
they
have
a
description?
Do
they
ever
read
me?
Do
they
have
a
code
and
when
they
have
when
they're
saying
oh,
yes,
they
do
they're
linking
they're
looking
explicitly
for
a
file
of
that
name
in
the
directory.
As
a
matter
of
fact,
with
code
of
conduct,
it
needs
to
be
like
of
that
format
like
underscore
underscore.
B
So
the
point
is
right
now,
the
contributing
that
we
have
is
for
how
to
how
to
work
with
how
to
work
with
jekyll
and
what's
nice,
and
so
that's
fine.
What's
nice
about
this
one
actually
is
that
we
say
there
was
something
that
people
were
commonly
doing
and
that
was
updating
the
landscape,
because
we
were
pinging
a
lot
of
people
like.
Can
you
update
the
landscape
and
add
information
about
your
project?
B
Even
the
like.
The
most
of
this
will
be
the
same.
It
would
be
kind
of
the
same
flow
as
fork
to
repo
make
you
do
do
these
things.
It'll
probably
still
be
a
make
site,
but
yeah,
so
so
that
I
think
under
the
new
folder
and
nikhil
had
landed
a
pr
not
too
long
ago.
I
don't
know
if
this
is
it
or
not,
but
he
was
updating
the
site
build
instructions.
B
D
B
D
B
B
D
B
Got
it
okay,
got
it
yeah.
Let
me
go,
let's
go,
let's
go,
take
a
look.
This
is
a
good,
so
I
think
what
we're
seeing
in
that
preview
is
success
with
using
the
gatsby
source
file
system,
plug-in
to
read
markdown
files
and
then
take
and
apply
a
template
that
you
have
included
in
here
and
lay
the
temp.
You
know
merge
the
template
and
the
content
together.
D
B
This
is
an
example
right
here:
yeah
mdx,
okay,
I'm
learning
something
new
in
the
x
and
then
is
that
is
that
sort
of
all
that
there
is
to
know
about
that.
Like
hey,
because
of
that
file
extension
gatsby
will,
you
know,
try
to
interpret
it,
will
look
for
curly
braces
and
try
to
interpret
what's
in
there
as
not
jekyll,
oh
yeah,
I
guess
yeah
it'll
try
to
interpret
that
as
gatsby.
D
B
B
D
B
Okay,
that
makes
sense
and
yeah
like
long
term.
We
wouldn't
want
to
mess
it.
I
mean
there
wouldn't
be
any
reason
really
for
us
to
keep
those
blog
posts
outside
of
the
site
direct.
You
know,
folder
structure.
I
guess
I
guess
the
the
question
there,
and
maybe
it's
it's
evident
from
just
looking
at
the
mark
down
here
that
yep
that
we
wouldn't
we're
not
really
anticipating.
D
D
B
I
see
okay
yeah,
it's
not
it's,
not
an
issue
with
html
being
interpreted
as
much
as
it's
an
issue
with
like
the
style
of
that
html
yeah,
okay,
nice,
okay,
and
so
I
guess,
educate
me
a
little
bit
more.
If
you
would
within
this
pr,
you
have
like
you've
created
a
single
page.
You've
created
a
template
here,
I
think
wait.
B
B
D
No,
I
didn't
create
as
much
means
that
the
template
which
have
used
it
was
inside
the
pages
folder,
so
the
catback
separate
page
automatically.
So
I
need
to
take
it
out
from
the
pages
page
because
we
didn't.
It
was
also
using
graphql
query
to
search
the
markdown
file.
So
if
that
period
is
already
existed
and
somebody
went
there
good
unable
to
find
the
markdown.
B
B
Nice,
yeah
and
and
that's
treaty
to
your
point
like
that's
something
that
can
be
done
more
or
less
now,
now-ish,
because
those
posts
really
shouldn't
be
changing.
You
know
much
like
we
can
it's
not
a
time
critical.
It's
not
like
you
have
to
do
it
within
the
hour
that
we're
migrating
or
something
like
the
data
is
pretty
static.
So
yeah.
D
B
C
D
B
E
E
Where
are
we
yeah?
So
basically
it
start
over.
Here
we
have
certain.
What
can
you
say,
users
which
will
have
access
to
our
data
and
can
change
our
data?
We
can
define
which
users
which
one
we
want
and
which
access
do
they
have
like
for
publicly.
We
can
decide
if
our
articles
are
free
to
find
free
to
count
free
to
create
or
free
to
delete
or
something
like
that.
E
All
of
this
things
works
based
on
api
itself.
If
for
public
right
now,
articles
and
categories
are
free,
but
if
you
want
like,
if
block
can
only
be
uploaded
by
certain
users
in
users,
I
mean
a
particular
web
website
or
some
client
itself,
then
we
need
to
make
a
authorized
account
for
them
itself.
If
you
want
and
we
can
define
what
they
can
do
means
we
have
a
flexibility
over
here
and
in
content
type
builder.
We
can
basically
define
what
kind
of
collection
types
do
we
want
to
have
suppose.
E
I
want
the
article
which
has
a
title
content
image,
and
it
is
also
linked
to
one
more
content
type
like
category
itself,
which
can
be
like
tags
of
which
type
of
article
it
is
they
can
be
joined
together
and
then,
if
we
search
for
category,
we
can
all
together
search
for
which
articles
are
under
those
categories.
If
we
link
them
together,
it's
it's
pretty
simple.
Actually
they
also
have
a
way
in
which
we
can
define
how
they
are
interconnected
together.
E
E
Yeah
they
have
different
edwards
setting
for
different
type
of
context
we
want.
So
this
is
how
we
define
a
particular
content
type
which
you
want,
and
then
we
can
define
a
particular
objects
of
that
content
type.
If
I
want
to
article
suppose
I
can
add
a
new
article
or
change
articles,
which
are
already
there
and
stuff
like
that.
This
is
the
basic
thing
which
I
guess,
a
person
publishing
the
article
would
be
would
be
more
familiar
with
this.
E
E
D
D
B
B
Since
you
know-
and
I
mean
one
I
mean
I
think
you
can
try-
you
can
probably
answer
that
with
a
couple
of
things,
one
there
might
be
others
who
come
through
who
aren't
as
comfortable
you
know.
So
they
might.
This
might
be
better,
but
then
there's
a
bunch
of
other
reasons
why
it
makes
sense
to
use
strappy
and
that's
because
just
even
as
you're
writing
down
markdown
and
trying
to
make
sure
your
image
sits
properly
and
things
that
the
ability
to
preview
it
real,
quick.
Oh
that's
nice,
without
having.
D
B
E
Oh,
no,
I
don't,
we
can
add
a
link,
but
now
I
guess
what
we
can
do
over
here
is.
We
can
go
to
content
type
builder
itself
and
we
can
add
one
more
option
itself.
If
we
want
someone
to
add
one
or
two
videos
itself
right,
something
like
a
small
text
and
we
can
convert
it
itself
to
a
link
or
something
like
video,
and
then
we
can
hard
code
it
to
the
gatsby
side
itself
that
this
particular,
if
this
particular
type
is
available,
then
make
a
video
attach
it
right.
B
There's
we're
using
a
lightbox,
javascript
library
that
will
read
through
all
the
elements
on
the
page,
see
if
there's
a
hyperlink
that
points
to
youtube
and
if
it
does,
it
will
create
this
nice
little
lightbox
effect
I'll.
Send
you
guys
an
example,
so
you
can
see
it,
but
that
was
something
that
we
haven't
been
using.
Oh
thank
you
yoshida!
B
E
B
E
B
B
B
What
else
that's
cool,
so
you
can
define,
maybe
even
your
own
add
a
new
component,
your
own
emote,
your
own
icons,
your
own
okay.
This
is
good.
There's,
probably,
I
suspect,
we're
just
kind
of
scratching
the
surface,
especially
as
you
consider
like
as
you
look
through
some
of
the
plug-ins
and
kind
of
the
marketplace,
there's
probably
a
whole
other
world
over
there.
E
B
B
B
B
Oh
okay,
yeah!
No
in
my
starcat,
it's
also
an
issue
where
my
sarcasm
doesn't
make
it
through
the
network
either.
No,
but
you
good
good
school's
off
for
you
so
now
that
summer's
over
you
can
start
to
enjoy
it
drove
and
hey.
Here's!
Here's
a
an
item
that
that's
probably
understood
enough
tenuous
what
you
did
with
the
blog
post
and
stuff,
though
that's
fantastic.
That's
awesome!
There's
something
that
jumps
out
to
me
as
being
kind
of
an
an
easier
opponent
to
maybe
tackle
would
be.
B
E
B
The
then
you
want
to
push
and
drive
sort
of
much
of
what
we
do
to
go
through
there.
I
think
that
would
be
naive
to
assume
that
everything
would
be
through
there
in
part,
because
some
things
might
be
updated
automatically
or
because
we're
going
to
be
inviting
people
to
update
the
landscape
and
when
they
do,
we
want
for
them
to
update
their
data.
B
You
know
about
their
projects
and
we're
not
going
to
hand
them
a
strappy
login,
not
because
we
would
be
opposed
to
that,
because
we
can
lock
down
their
permissions
to
do
what
they
need
to
do,
but
because
it
just
wouldn't
be
the
norm.
We
would
you
know
that
they
would
be
expecting
to
update
that
in
github.
B
E
I
I
I
I
B
I
Didn't
I
edited
the
navigation
dot
js,
so
basically
what
they
had
done
in
this
layer,
5
ng
one
was
they
had
created
like
a
data.json
file
that
has
all
the
elements
of
the
navigation.
So
I
changed
that
to
have
not
just
the
so
like
you
know
like
we
have
on
strappy.
On
the
left
hand
side
we
have
all
our
all
our
like
page,
like
item
list
and
on
the
right
hand,
side.
I
We
have
the
images,
so
I
sort
of
integrated
that
that
we
can
have
like
a
link
like
two
big
urls,
because
you
know
for
each
and
every
mega
menu.
We
can.
Let's
say
there
are
blogs.
We
can
have
two
featured
blogs
on
the
left
hand,
side
and
some
relevant
links
on
of
the
blog
on
the
on
the
right
hand,
side.
Similarly,
for
let's
say
for
our
programs,
we
can
have
like
the
two
main
programs
and
list
of
all
the
programs.
B
J
B
As
moderately
straightforward
is
the
footer
that
that
component
on
the
new
site,
that
oh
boy,
I
just
even
glanced
at
it,
but
like
it's
probably
fine,
like
the
styling
of
it,
is
probably
about
right,
like
I
don't.
You
know
we'll
see
eventually,
but
right
now
the
links
that
they
have.
We
need
to
displace
those
with
our
own.