►
From YouTube: 2023 05 19 Building jenkins io with alternate tools
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
A
A
A
So,
oh
we
haven't,
did
you
have
like
I'm
gonna
ask?
Did
you
share
with
us
the
project
patterns
or.
B
Do
not
talk
about
regard
regarding
to
the
project
plan.
Chris
I
was
thinking
that
I
I
have
tried
to
support
the
things
that
I
had
on
my
proposal.
That
I
was
I
that
were
like
good
enough
in
my
opinion
and
I
was
thinking
can't
just
use
my
proposal
as
the
project
plan
for
now,
because
it
is
really
you
know
how
you'll
say
it.
It
is
like
a
time
taking
process
of
writing
that
same
project
plan
on
the
wiki.
So
can
we
just
for
now
use
my
proposal?
B
We
can
put
the
link
to
my
proposal
on
the
wiki
for
now
and
use
that
as
a
project
plan
I
I
can
I
can
update
my
proposal
with
that
and
when,
like
on
some
weekend
when
I'll
have
the
energy
to
actually
do
that,
I'll
just
put
everything
to
the
wiki.
Would
that
be
us
fine
with
you.
A
Yeah,
but
if
you
want
to
walk
us
through
what
you
have
and
let
me
let
me
let
you
share
the
screen
first.
So
would
you
like
to
walk
us
through
what
you
already
have.
C
So
Chris
I
think
van
did
I.
Believe
Chris's
question
was:
do
you
want
to
walk
us
through
what
we've
already
what
you've
got
because
I
think
a
discussion
amongst
the
four
of
us
of
the
existing
plan
is
a
really
good
idea.
B
Yeah
should
I
just
share
my
proposal
for
that
yeah.
B
All
right,
just
a
second
I
think,
can
you
see?
Can
you
guys
see
my
screen
yep
awesome,
so
what
the
the
first,
the
first
phase
for
the
project
would
be
restructing
the
content,
because
entera
uses
a
complete
file
structure,
then
awestruck
so
I
have
already
on
on
the
on
the
Jenkins
doc
on
the
Jenkins
hyphen
doc
repository
I
have
already
like
started
the
file
structure
like
that
we
can
add
more
modules
and
just
import
the
import,
the
docs.
B
That
would
that
would
that
would
take
maybe
around
two
weeks,
I
guess,
because
some
some
files
would
need
to
be
changed
according
to
the
enter
a
structure
like
in
austruct.
We,
we
Define
some
things
in
the
adoc
file
that
is,
is
not
very
really
necessary
in
enter.
I
have
written
that
here,
somewhere
yeah
conversion
of
files
according
to
antora,
so.
C
Okay,
so
so
I
see,
if
you
could
scroll
back
up
to
the
list
of
of
sections
that
you've
got
enumerated
there,
so
user
guide
I
understand,
that's
the
the
what
the
thing
calls
the
handbook
developer
guide
and
that's
the
one
that
I
could
see
absolutely
needs
to
be
versioned
right.
So
that's
the
one!
That's
antora,
fully
versioned
developer.
B
It
was
it
was
it
I,
I
I,
it
shouldn't
be
here.
It
shouldn't.
B
Is
just
like
to
show
what
it
will
be.
B
It
was
not
written
on
the
project
page
how
if
there
will
be
versions
on
our
version
or
not,
but
I
think
they
should
be,
because
tutorials
must
be
versioned.
According
to
the
version
you
will
be
used
to
Jenkins
and
solution
should
be
also.
C
B
Can
start
we
can
start
the
versioning
from
now
on
because,
like
what
you
said,
the
solutions
page
are
not
that
bulky,
but
they
should
be
versioned
or
conceptually.
They
should
be
versioned.
According
to
the
Jenkins
version
you'll
you,
the
users,
are
using.
C
B
A
developer
guide
shouldn't
be
version
because,
when
a
developer
or
a
you
can
say
a
developer
contributor
who
will
start
contributing
to
Jenkins
or
who,
who
just
want
to
use
Jenkins
API,
he
he
won't
have
access
to
the
old
versions
of
the
API
I
think
he
he
would
obviously
use
the
API
the
latest
apis
that
are,
we
are
using
so
I.
Don't
think
that
should
be
versioned.
That.
B
Moving
on
yeah
I,
don't
think
this.
This
conversion
of
files
according
to
intera
is
the
is
a
tedious
task,
but
I
don't
think
it
will.
I
just
have
to
remove
some
things
from
like
from
the
top
part
of
the
page,
and
it
would
be
good
to
go
I
I.
This
was
we
in
austruct
we
use
dot,
html.html
files
as
the
template
and
and
as
a
template
to
for
other
daughter,
doc
files
in
antora.
B
B
Coming
to
the
main
problem
that
I
faced
was
that
antora
does
not
really
provides
anything
for
DOT
yml
files
in
our
that
are
in
our
code
base,
which
are
road
maps
and
change
logs,
so
I
but
Gatsby
does
we
can
use
Gatsby.
We
can
use
a
Gatsby
plugin
that
will
use
the
dotto
ml
files
as
content
source
and
generate
that
roadmap
and
change
logs
for
us.
D
D
B
We
will
just
use
the
you'll
use
the
content
of
the
yml
and
the
plugin
will
do
most
of
the
work.
We
don't
have
to
do
much
for
this.
They
have
like
written
a
really
great
instructions
for
that
coming
to
yeah
header
and
footer
from
jenkins.io
components.
This
was
something
I
figured
out
during
the
application
period,
so
the
Jenkins
Jenkins
hyphen
Jenkins
Dash
UI
project
already
has
header
and
footer
from
jenkins.io
Jenkins
I
Dash
higher
components
repository,
so
that
would
be
easy
to
implement
because
I
have
already
done
so.
But
what
I?
B
What
I
noticed
was
using
a
header
and
footer
from
another
repository
might
take
some
time
from
on
a
on
a
unstable
internet
connection,
but
I,
don't
I,
don't
think
we
take
that
in
account,
but
yeah
I
I
was
thinking.
It
would
be
awesome
if
we
could
like
create,
create
the
header
and
put
up
from
the
you
from
the
enter
UI
itself,
but
that
is
just
like
we
can
do
that,
but
we
don't
have
to.
E
C
B
I
I
Implement
I
I
just
used
the
header
and
footer
from
Jenkins
IO
components
repository.
So
we
can
do
that,
but
yeah
like
I
said
it
is
something
we
can
do,
but
it
was
open
to
what
the
mentors
would
say.
So
that's
like
yeah
I,
think
I.
Think
after
using
that
I
didn't
put
it
from
jenkins.io
components
would
be
nice
for
now,
because
plugins
and
stories
already
use
that.
B
Plugins
exactly
yeah
yep.
This
is
just
the
instruction
how
I
will
use
that
I?
How
I
implemented
that
we
can
ignore
that
this,
and
this
explains
the
versioning
in
entera,
so
entera
uses
entera.yml
files
as
in
if,
if
we
go
here,
yeah
in
a
root
folder
or
like
any
folder
like
this,
the
inner
structure
would
be
like
this.
We'll
have
an
enter.yml
at
the
source
root.
B
This
will
have.
This
will
decide
if
the
if
this
module
would
be
versioned
or
not,
and
this
will
be
the
entire
file
structure
here.
The
nav.addock
is
the
sidebar
and
have
that
entire
users
will
have
to
will
have
to
add
a
hyper
hyperlinks
in
here
h,
x,
xhref
links
for
to
creating
the
nav
bar.
B
D
B
This
Is
How,
we'll
Implement
versioning
in
user
docs,
because
that's
the
first
Milestone
so
I'll
I
will
create
we'll
create
different
folders,
we'll
use
folder
folders
as
components
in
a
single
repository.
This
is
a
feature
antora
provides,
so
our
documentation
would
be
divided
in
folders
in
directories
and
these
directories
would
contain
modules
and
enter
a.yml,
so
the
enter.yml
of
user
docs
will
be
versioned,
so
it
will
some
look
something
like
it
will
look
something
like
this
with
the
version
and
for
the
unversion
part
I'll.
Just
we
will
just
have
to
replace
this.
B
And
it
will
be
unknown
versioned.
Okay,
also,
the
versions
would
be
on
the
versions
can
be
on
on
tags
or
on
different
branches.
We
can
create.
We
can
create
a
branch,
we
can
create
a
branch,
namely
version
2.0
V
2.0,
and
we
can
create
a
branch
version.
2.1
and
both
will
have
different
documentations,
but
it
will
on
on
our
site.
It
will
a
week
the
user
can
select
the
version
he
wants
to
you.
He
wants
to
read
documentation
or.
C
C
B
Your
experience,
nobody
from
what
I
have
seen
that
nobody
actually
changes,
changes,
documentation
to
weekly
and
most
of
like
the
Entourage
enter
a
dog
site
has
has
documentation
only
for
for
the
LTS
versions
they
released.
Oh.
B
Yeah
they
already
follow
a
pattern,
so
we
don't
collect,
we
don't
clutter,
wait.
Let
me
show
you
yeah
yeah
here,
just
yeah
yeah,
they,
oh
they.
Oh,
they
have
their
version,
they
were
their
versioned
and
Torah
docs
from
3.0
and
3.1.
A
C
B
Coming
this,
this
was:
how
will
we
Implement
an
inversion,
non-version
docs
with
that
till
design?
I
guess
we
call
it
till
day.
Okay,.
B
Yeah
antora
works
on
our
feature
on
a
concept
called
start
path.
Start
paths
are
basically
where
will
antora
start
finding
the
dogs
from
so
the
start
parts
are
written
in
the
enter.ymls
like
this.
This
is
this
is
how
you
will
write
the
you
will
write
the
sources,
the
content,
sources
of
the
documentation,
the
URL
of
our
Repository.
B
Let's
start
pass
start
since
we
have
multiple,
since
we
have
multiple
documentation,
so
we'll
have
to
write
multiple
start
paths
here.
So
this
is
this
will
how
it
will
look.
This
was
an
example
part
two
then
today
that
yml
and
then
the
branches,
the
the
branches
is
where
I
will
write.
The
versions
like
we
can
write
version,
2.1
version
2.2.
A
B
This
was
this
was
the
this.
This
was
the
screen
like
what
I've
created
using
Jenkins
UI,
that
it
uses
the
Jenkins
IO
component,
footer
yeah
this.
That
was
for
phase
one
and
customizing
UI,
which
is
like
the,
which
is
like
the
most
important
part
of
this
project
since
we'll
have
to
Jenkins
spy
everything
so,
like
I
said
and
Torah
uses
handlebars
JS
for
UI
and
it
the
they
they
wait.
I'll
show
you
coming
to
here.
B
This
is
the
Genki.
This
is
the
intora
UI
project
it
contains
these.
It
contains
these
partials.
These
partials
have
this.
These
partials
already
have
the
base
to
start
from
so
I
think
I'll.
First
start
I'll
I'll,
first
see
that
what
will
be
the
files
that
I
would
have
to
change.
What
would
I
would
actually
have
to
change,
or
would
the
default
or
the
out
of
the
box
code
would
be
fine
or
not.
B
That
would
I
would
see
that
and
after
that,
after
that,
I
will
I
will
start
changing
the
CSS
for
each
of
the
component
to
Jenkins
fire
it
children
can
spy
it
yeah.
B
The
JS
is
not
much
it;
it
is.
It
provides
basic
functionality
that,
and
we
don't
have
to
change
much
in
this,
from
what
I,
what
I
have
seen
changing
change?
If
you
have,
it
will
have
to
add
a
new
functionality
we
can
just
edit
to
the
JavaScript
of
the
site.
We
can
do
that
here.
We
can
add
a
new
file
to
here.
B
Customizing,
the
layout
is
all
about
the
CSS
part,
so
yeah
I
just
showed
you
we'll
have
to
I'll,
have
to
change
the
CSS
in
the
CSS
folder
for
each
of
each
of
the
I
I
I
tried
you
I
tried
using
the
existing
CSS,
but
you
can
say
it
is
kind
of
a
mess
on
different
screen
sizes
on
different
screen
sizes.
It
does
not
work
really
well,
so
I
think
I
I
think
we
can.
B
We
can
you
we
can
use
this
as
a
base,
as
it
is
awesomely,
responsive
response,
responsive
and
work
or
build
on
or
build
on
that.
C
Okay
and
that's,
and
so
the
idea
there
is
that
the
the
net
benefit
of
this
is,
we
will
have
a
much
more
responsive
experience
for
users
at
different
sizes.
It
will
certainly
certainly
cause
changes
right.
There
will
be
changes
as
a
result
of
that,
but
the
the
ultimate
goal
is
a
much
more
responsive
layout
as
screen
sizes
change,
yeah.
B
I
I
I'll
try
I'll,
try
to
I'll,
try
that
the
things
that
are
already
there
don't
break
while
change,
while
Jenkins
spy,
while
Jenkins
find
the
site
so
yeah
that
will
build
upon
that
we'll
see
I,
hope,
I,
don't
break
many
things.
Okay,
this
this
is-
and
this
is
this-
is
how
handlebars.js
file
looks.
A
D
B
Yeah
yeah
these
are
partials
and
the
these
these
partials
will
be
in
the
partials
reposit.
These
partials
would
be
here
in
the
partials
repository
and
I
I
I'll
change
these
to
change
the
structure,
the
layout
of
the
the
page,
okay.
B
By
default,
uses
is
much
similar
to
of
our
Jenkins,
since
they
have
their
nav
bar
on
the
side
and
a
table
of
contents
on
the
right
side
of
the
screen
and
the
main
content
on
the
in
the
middle.
So
I
think
it
I'll
just
have
to
Tinker
around
with
CSS
a
lot.
B
A
I
have
a
question,
though:
I
have
a
question
for
you,
but
you
said
like
four:
four,
like
the
check
and
stock
repo,
you
took
two
weeks
to
do,
but
how
about
the
the
the
Jenkins
Dash
UI
Dash
project.
B
A
Okay,
two
so
three
to
four
weeks,
yeah
three
to.
D
B
Okay,
moving
on
to
the
next
part,
Jenkins
or
IO,
uses
algola
doc,
search
for
as
a
search
engine
on
the
on
our
site,
so
they
enter
up.
Antora
provides
the
instructions
on
how
to
how
to
implement
how
to
integrate
algola
to
it.
So
it
would
be
just
me
following
the
instructions
the
tutorial
they
provided.
B
I
would
I
would
like
to
know
how
they
they
have
provided.
The
docker
solution,
but
I
from
but
I
have
I
have
read:
algolia
dogs.
There
are
other
ways
too,
but
yeah
I
I
would
send
this
to
the
guitar
channel.
So
maybe
the
mentors
can
review
it
first
before.
B
B
These
were
all
provided
here
and
from
what
I
have
seen
on
other
repositories.
B
Yeah
yeah
phase
three
is
migrating
blocks
to
gatsui,
so
by
default,
Gatsby
is
normally
used
for
dot
m
a
DOT
MDX
files,
but
we
we
or
we
have
plugins
that
are
you
that
we
can
use
for
DOT
edoc
files
for
our
Sky
dog.
We
can
I
thought
we
could
like
create
another
repo
for
blog.
So
since
it
is
an
expanding
topic
and
blogs
expand,
so
it
would
be
nice
for
to
create
another
Apple
only
for
blogs,
but
yeah.
That
was
like
one
of
that
was
like
we
could.
B
Yeah
yeah.
We
can,
because
that
I
have
what
I
have
structured
the
directory
like
that,
so
we
could
easily
split
it
off
if
you
in.
If,
in
future
we
had
to
okay
yeah,
we
Gatsby
Pro
Gatsby
provides
awesome
starters,
so
I
I
start
I.
You
start
I
use
this
to
to
create
if
from,
if
you're,
if
you
run
the
project
in
the
gaps,
but
in
the
gas
by
block
test
directory
on
Jenkins
talk,
it
would
some.
B
It
would
look
something
like
this
nope,
not
this
I
guess
they
have
changed,
it
would
look.
It
would
look
something
like.
B
Guys
we
start
yeah
yeah
I,
I
I've,
tried,
I,
tried,
start
I've
got
I
have
created
for
my
POC.
Was
the
default
default
starter
that
that
I
created
from
the
CLI,
so
it
looks
different
I'll
I'll?
Send
it
if
I'll
find
it
here
or
it
is
in.
It
is
in
the
documentation.
I
guess
it
is
like
the
default
starter
yeah.
It
is
here.
Okay,
yeah,
it
looks.
It
will
look
something
like
this
for
now
with
Jenkins
logo.
A
B
D
C
B
No,
if
yeah,
if
they're
a
dog,
if,
if
something
is,
if
a
dog,
it
will
be
done
with
antora,
but
if
something
is
dot
yml
we
can't
act.
We
can't
do
it
with
antora
from
now,
because
they
don't
even
provide
any
plugin
for
Dr
ml
source
files.
Okay,
so
that's
we
would
be
the
way
for
that.
B
The
steps
I
have
written
here
uses
the
re
uses.
The
existing
blog
that
I
can
tweak
with
like
I
I
can
delete
I,
remove
the
unnecessary
files
that
won't
be
necessary
for
Gatsby,
but
while
I
was
doing
that,
while
I
was
actually
doing
that,
many
things
were
many,
things
were
necessarily
breaking
and
I
couldn't
figure
it
out.
So
I
think
I'll
just
copy
paste.
The
wiml
files
yeah
modifying,
won't
work
so
that
Gatsby
is
so
easy
to
use.
We
can
just
you
can
just
lay
out
the
layout.
B
We
can
just
customize
the
layout
from
the
source,
layouts
index.js,
that
is
here.
B
This
is
the
layout
of
this
will
be
the
layout
of
our
blog
I
I'm,
not
I'm,
not
very
handy
with
react,
but
I
think
I'll
be
I'll,
be
able
to
I'll
be
able
to
learn
it
on
the
go.
So.
B
A
B
Yeah
they're
using
complex
components,
yeah
yeah-
this
is
this.
B
This
is
this
is
if
we
were
like,
if
we
were
planning
to
use
Gatsby
for
more
ASCII
doctor,
but
I
think
that's
off
the
table,
so
this
would
be
a
necessary
now
yeah
the
integrate
the
integration
parts
of
the
blog
site
if
they,
both
of
them
will
be
in
the
same
repository
I
will
have
to
create
we'll
have
to
create
a
setup
file
that
will
install
the
prerequisite's,
install
and
tour
and
Gatsby
locally
on
someone's
system
and
changing
changing
into
correct
repositories
will
build
it.
B
D
F
So
how
we
are
syncing,
the
design
I
mean
we
have
like
enter
a
site,
some
CSS,
handlebarges
and
Gatsby.
We
are
making
using
some
I
mean
react
components.
So
are
we
going
to
use
the
different
designs
for
both
them
and
fonts
and
all
the?
So?
How
are
you
syncing?
It.
B
I
I
I'll
have
I'll
have
to
I'll
have
to
create
components
that
that
follow
the
current
design
of
the
block
site.
If
you,
if
we
go
here,
the
the
just
a
minute,
where
will
when
yeah
yeah
it
is
dog
yeah,
we
I'll
we'll
follow
this
design
for
now.
B
Okay,
okay,
since
since
I
I'll
I
will
also
will
also
will
also
see
if
we
could
increase
the
user
experience
in
any
way.
F
B
F
Okay
and
the
search
will
also
be
there
for
blog
using
algolia.
F
Okay,
so
you're
going
to
make
a
component
out
of
it.
Okay,
one
more
question
like
so:
you
are
using
that
antora
thing
and
we
have
docs
versioning
thing,
so
we
have
like
some
3.0
and
3.1
and
3.1
is
the
latest.
So
if
some
user
were
going
to
use
Jenkins,
they
Google
a
generation
docs.
So
will
the
3.1
comes
in
the
Google
indexes,
like
the
latest
version?
Should
I
want
to
I
want
latest
version
to
come
to
Google
index
so.
B
No,
no,
no,
no!
No,
the
the!
If
someone
searches
for
Jenkins
dot
IO
like
the
main
side,
the
main
site
will
pull
up
and
the
user
can
see.
The
user
will
see
a
drop
down
here
somewhere
here.
I'll
have
will
have
to
see
where
we'll
put
the
drop
down
most
of
the
sites.
Have
it
right?
Have
it
on
the
right
side
of
the
search
bar
he
would
be
able
to.
He
would
end
up
on
the
latest
latest
documentation
site
he
would
be
able
to.
B
F
So
if
we
search
like
some
user
search,
Jenkins
GitHub
plugin
a
gitlab
plugin,
so
some
docs
will
come
at
the
starting
or
maybe
a
second
time
or
so
when
he
click.
That
link
is
going
to
show
the
latest
version
of
that
yeah
yeah.
F
Okay
and
anything,
you
are
sorry
about
antora
ml
file,
where
we
are
going
passing
that
configurations.
So
are
you
passing
any
anything
like
SEO
related
stuff
like
in
front
matter,
so
maybe
like?
If
I,
if
I
have
a
doc,
so
I
want
that
descript
I
want
to
put
description
of
that
doc
so
that
it
increases
the
SEO
of
that
box.
So,
where
you're
passing
that
in
front
matter
like
in
MDX
and
all
you
pass
in
front
mat
or
something
so
like
something.
B
When
I
was
I
was
I,
don't
think
so
in
Torah,
like
provides
any
documentation
really
I
would
I
would
like
I
would
I
would
study
about
it
and
maybe
then
I
would
have
I
could
answer
your
question
like
I,
don't
know
much
about
print
matter
now.
Right
now
got
it
yeah
yeah.
You
have
raised
your
hand,
yeah.
A
A
C
C
That,
okay,
so
this
is
is
seems
like
a
natural.
Well
it
it's,
it
should
be
non-versioned
I
think,
but
it's
a
doc,
and-
and
this
is
where
I
guess
I
have
to
ask
you
the
do.
You
have
a
were
you
aware
of
this?
If
not,
let's
make
you
aware
so
that
you
understand
how
it's
so
what
this
thing
is
is
there's
a
program
that
reads
all
the
Jenkins
plugins
and
extracts
the
help
from
them
and
then
paste
them
places
them
available
as
adoc
source
files
that
we
use
here.
C
But
these
it
seems
to
me
it
would
be
misleading
to
the
user.
If
these
were
versioned,
because
the
version
number
we
would
assign
doesn't
correlate
with
the
plug-in
version
from
which
we
extracted
the
documentation
so
Chris,
could
you
pick
one
of
those
one
any
one
of
those
or
no
sorry,
Vandy
you're
driving
the
screen
so
pick
any
one
of
those.
C
That's
great
so
when
you
click
that
it
takes
us
to
this
page
that
describes
this
pipeline
step,
but
this
pipeline
step
is
not
associated
with
a
Jenkins
version.
It's
with
a
plug-in
version,
and
so
we
I
don't
think
we
want
this
page
to
be
Associated
to
a
a
Jenkins
version,
because
because
we
don't
know
what
version
the
user
has
running
now,
if
you're,
underneath
the
The
Heading
one
password,
Secrets,
there's
a
view.
This
plugin
on
the
plugin
site
and
on
the
plug-in
site
you'll
see.
Oh
here's.
C
The
here
is
the
actual
version
number
of
this
plug-in
I.
Don't
think
we
need
to
complicate
that
page
by
showing
it
to
the
showing
them
1.0
to
the
user,
but
it
seemed
it
would
seem
poor
experience
if
we
misled
them
to
thinking.
Oh,
that
plug-in
documentation
is
associated
with
2.401.1,
because
that's
not
what
it's
associated
with
It's
associated
with
version
1.0
Is
it
feasible
for
you
to
do
that
as
a
non-versioned
page
yeah.
C
C
B
B
A
C
A
C
B
D
A
B
C
I
well
when,
when
the
the
contributor
last
year
did
it
I
was
so
delighted,
I
it's
hard
for
me
to
express
how
happy
I
was
with
this
change,
because,
prior
to
this,
it
was
a
positively
terrible
experience
to
use
this
page,
because
I
would
have
to
search
with
the
web
browser
and
it
would
jump
all
over.
This
is
a
much
much
better
experience
than
we
had
15
months
ago.
A
B
C
D
B
A
Oh,
it
should
be
okay,
but
it's
like
do
you
want
to
take
a
look
at
the
email
first,
together.
C
C
C
D
C
C
D
C
C
B
Trust
entera
was
not
designed
for
vlogs
yeah
and
the
ratio
makes
it
clear
that
maintenance
yeah
they
are,
and
the
Dan
Allen
explicitly
said,
and
Torah
is
only
for
version
docs
not
for
dogs
right
Vlogs,
don't
need
to
be
I,
don't
need
to
be
versioned
using
intera
and
Torah
for
anything
other
than
a
documentation.
Site
seems
advice,
as
this
is
not
intelligence
into
use
case.
Yeah.
B
Yeah
I'm
maintaining
Gatsby.
If
we,
if
we
add
plug-in
over
plug-in
the
build
time,
increases
exponentially
like
I,
read:
I
read
in
a
blog
that
someone
was
using
Gatsby
and
for
like
for
two
years
and
he
added
so
many
plugins.
His
build
time
was
around
12
minutes,
which
is
a
lot,
so
he
migrated
from
it.
B
C
D
D
B
B
B
F
Yeah
yeah,
so
we
have
like
a
doc
file
right
and
in
that
we
put
all
our
contents.
So
it's
starting
up
that
content.
We
write
some
metadata
right,
name
Yeah,
so
basically
metadata
is
a
front
matter.
So
are
we
going
to
pass
the
SEO
related
metadata
for
that
doc?.
B
B
I,
what
I,
what
I
think
if
like?
Currently
we
don't
actually
add
in
any
anything
in
the
front
matter
for
SEO
like
and
and
Torah,
removes
these
things
like
from
what
I
showed
here
and
like
the
the
file
struck
the
file,
how
the
file
looks
it
it
it.
It
just
provides
the
description
and
the
author
according
to
what
our
ASCII
doc
file
should
look
like
so
and
also
since
the
skydoc
files
are
so
large
in
number,
adding
SEO
for
each
and
every
will
be
like
humongous
task.
B
A
A
Yeah
because
like
we
have
to,
we
have
to
make
plans
about
how
to
do
things
like
how
to
continue
the
the
way
things
are
done.
But
using
given
tooling,
because
if
you're
using
and
taller
things
can
be
configured
a
bit
differently
from
what
they
are
now.
E
I
do
have
one
question
so
in
this
project,
where
we
make
big
changes
in
user
interface.
It's
because
AI
I
see
in
phase
two.
We
will
like
customizing
the
UI
or
styling.
B
Personally,
I,
like
Mo
I,
like
I
like
modern,
you
are
a
modern
user
experience
and
like
UI,
but
I
think
the
it
would
be
correct
if
we
start
on
the.
If
we
first
configure
things
and
customize
things
how
they
are
in
jenkins.io
and
then
maybe
then
maybe
not,
maybe
then
we
we,
then
if
we
have
time
and
I
hope
we
have
time
we
can
work
on
user
experience
and
UI
yeah.
E
Yeah
so
so
my
question
is
So,
based
on
my
understanding.
This
product
is
like
the
migration
of
the
current
Jenkins
IO,
because,
let
me
see
so
most
of
the
parts
will
focus
on
will
will
be
focused
on
the
migration
instead
of
the
customizing,
the
user
interface.
B
E
D
B
I
think
everything
is
clear,
but
what
I
was
thinking
since
what
today
happened?
I
think
we
should
like
change
our
meetings
to
Saturday,
if
that
is
possible
for
everyone,
because
from
from
where
I
commute
from
my
college
around
this
time,
there
is
so
much
traffic
like.
C
That
would
work
for
me
so
roughly
this
same
time,
24
hours
later.
A
B
A
E
Last
question:
will
we
will
we
receive
the
update,
your
the
the
time,
updating
your
email
after
this
meeting.