►
From YouTube: Non-Developer Contribution Demo
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
One
of
the
one
of
the
one
of
the
things
that
we
have
focused
on
a
lot
is
really
making
the
the
project
as
accessible
as
possible
to
to
everyone.
So
bottom
line.
One
of
the
things
that
we've
done
is
we've.
We've
really
put
everything
as
as
much
as
we
can
we've
put
in
to
get
or
github
really
sort.
The
idea
of
putting
everything
in
get
is
really
central
to
the
spirit
of
the
project
antidote.
What
I
mean?
What
antidote
enables?
Is
this
idea
of
curriculum
as
code,
meaning?
A
You
know
everything
that
we
put
into
the
curriculum
and
then
therefore
represent
on
the
on
the
Unreal
lab
site?
Is
it
represent?
It's
represented
in
an
NRA
learning
repository
somewhere,
specifically,
the
curriculum
is
represented
in
the
NRA
labs
curriculum
repository,
but
we
do
that
for
not
just
the
curriculum.
Of
course
we
do
that,
for
you
know
code.
So,
like
the
platform
itself
as
well.
A
You
know
we
have
the
antidote
web
front-end
and
the
syringe
back-end,
and
all
that
kind
of
all
that
kind
of
stuff
is,
is
obviously
you
know
open
source
in
the
in
the
github
sense.
We
have
the
source
published,
but
we
didn't
stop
there
pretty
much.
Everything
is
also
everything
else
is
also
on
github,
and
this
includes
things
you
might
not
think
of
as
being
able
to
be
put
into
into
github
as
a
result,
I
think
actually
tying
everything
together.
A
The
results
for
doing
all
of
this
is
that
anyone
can
see
or
contribute
to
anything
that
we
do
in
the
exact
same
way.
So,
no
matter
what
kind
of
area
of
the
project
you're
interested
in
you
can
get,
you
can
get
access
to
that
in
the
same
way,
whether
it's
the
blog,
whether
it's
a
governance,
doc,
whether
it's
enery,
labs,
lesson
or
source
code,
doesn't
really
matter
what
it
is.
A
Now
that
raises
an
interesting
question:
if
you
have
everything
in
github
and
github
is,
is
one
of
those
developer
things
right
like
you,
you
use
github
for
developer
stuff,
so
that
means
I
must
be
need
to
be
a
developer
in
order
to
contribute,
and
the
answer
is
no
I.
It's
probably
obvious.
This
is
the
kind
of
the
point
of
the
video
but
yeah.
My
answer
to
that
is:
no.
You
don't
need
to
be
a
developer
to
contribute.
So
here's
what
you
need.
A
So,
if
you're
not
a
developer-
and
you
want
to
contribute
to
some
of
the
areas
of
the
project
that
don't
require-
that
kind
of
a
skillset,
for
instance
the
documentation,
the
the
blog
any
one
of
our
governance,
Doc's,
any
anything
like
that,
you
you
don't
need
you
don't
need
to
have
some
sort
of
like
full-on
developer
environment.
Configured
on
your
machine,
what
you
really
need
are
these
three
things.
A
First,
off
a
github
client
github
has
now
clients
for
both
Windows
and
Mac
that
are
vote,
both
very
easy
to
use
and
I'm
gonna
walk
you
through
that
here
shortly.
The
next
thing
you'll
need
is
a
decent
text.
Editor
vs
code
is
nice
because
it
has
a
lot
of
the
features
of
of
what
you
might
expect
from
like
more
of
a
full-blown
development
environment,
but
it
doesn't
require
you
to
use.
It
doesn't
require
it
sort
of
in-depth
knowledge
of
any
of
that
stuff.
Vs
code
is
nice
because
a
it's
easy
to
install,
be
it.
A
It
contains
out-of-the-box
support
for
anything
we're
gonna
be
working
on
in
this
video.
The
third
thing
is
less
on
what
you
need
from
a
tooling
perspective
and
more
on
an
understanding
of
plain
text
formats.
So
there
are
two
formats
that
are
in
use
in
many
open-source
projects.
In
fact,
the
two
were
using
our
markdown
and
restructured
text.
Now,
basically,
what
these
are
are
it's
a
way
for
you
to
have
some
some
basic
formatting
control
over
a
plain
text?
Medium.
A
So
imagine
if
you
open
something
in
like
notepad
like
vanilla
of
Windows
notepad,
you,
you
can't
do
things
like.
You
know,
create
bold
text
or
headers,
or
you
know
any
anything
that
you're
used
to
being
able
to
do
in
like
Microsoft
Word
right
well,
these
two
formats
actually
help
you
meet
in
the
middle.
They
allow
you
to
store
things
as
plain
text
which
which
is
useful
for
us
when
we're
working
with
git.
Because
again
you
need
to
be
able
to
see
the
source.
A
I
don't
know
if
you've
ever
looked
at
like
the
source
of
like
a
word
doc.
But
it's
it's
not
readable.
It's
not
usable.
You
have
to
open
that
within
Word,
which
is
challenging.
So
if
we
were
to
store
a
word
doc
and
get
that
would
be
really
difficult
to
contribute
to,
whereas
markdown
to
restructure
text,
they're
designed
to
do
exactly
that,
they're
designed
to
be
stored
as
if
they
were
source
code
for
you
know
as
if
they
were
like
application
code.
A
So
the
first
thing
we
want
to
do
is
we
want
to
install
a
github
for
Windows.
Now,
if
you
have
Mac,
that's
fine,
as
they
say
here,
it's
actually
built
on
a
on
a
cross
platform
framework
called
electron.
So
in
theory
the
UI
should
be
very,
very
similar
with
some
minor
changes,
I'm
sure,
whether
you're
on
Mac
or
Windows,
but
generally
speaking,
they
should
be
the
same
so
cool
we
have
it
installed
and
we
need
to
set
it
up.
A
The
first
thing
we
want
to
do
is
is
connect
this
client
with
our
github
account,
and
if
you
don't
have
one
you
should
definitely,
you
should
definitely
create
one
I
am
signed
in
under
my
username,
which
is
me
written,
and
you
can
see.
I
have
here
on
the
screen,
the
NRI
learning
organization
we'll
be
playing
around
with
some
of
these
repositories.
Very
shortly
now,
going
back
to
the
desktop
client
here,
you'll
see
that
we
have
a
few
options.
A
We
need
to
clone
a
repository
from
the
internet.
We
could
also
create
a
new
repository
or
add
an
existing
repository,
but
since
we
just
installed
this,
neither
of
these
things
are
true.
We
don't
want
to
create
a
new
repository
because
we
already
have
repositories
in
github
now.
So
this
isn't
an
option
we
want
and
we
don't
have
any
existing
repositories.
So
what
we
want
to
do
is
we
want
to
take
an
existing
repository.
We
want
to
clone
it
from
the
internet
now.
This
will
pop
up
this
box
where
we
sign
into
github.
A
This
allows
us
to
you
know
very
easily
tie
our
contributions
back
to
our
username,
so
I'm
gonna,
sign
in
real,
quick,
okay,
so
I'm
signed
in
and
I
now
see
all
of
the
repositories
that
I
have
access
to
as
part
of
my
account,
which
again
will
include
some
of
these
NRA
learning,
repos
that
we
saw
earlier
now
before
we
do
any
of
that.
What
we'll
really
want
to
know
is
the
three
repos
that
we
can
the
the
three
primary
repos
that
you
might
want
to
know
about,
if
you're
not
really
in
developer
type.
A
These
are
the
three
that
you're
probably
going
to
stick
around
with
most
the
first
one
is
antidote
I'm
going
to
open
these
in
new
tabs,
antidote,
energy,
Labs
curriculum
and
then
proposals
and
actually
lets
you
know
what,
instead
of
curriculum,
because
that
has
some
other
considerations.
Let's,
instead
of
the
curriculum,
let's
do
the
NR,
the
blog
NRI
blog
there
we
go
alright.
So
here
are
the
three
repos
that
we
want
to
contribute
to
now.
A
These
are
underneath
the
NRA
learning
organization
and
the
way
that
you
contribute
to
repositories
on
github
is
you
don't
actually
have
permissions
to
push
to
really
any
repository
that
doesn't
explicitly
grant
it
to
you
so
the
way
that
most
people
contribute
to
github
repositories?
Is
they
fork
them,
which
means
basically
creating
a
copy
on
your
account.
So
I'm
gonna
do
that
here
and
we
will
fork
it
to
me
written
and
same
thing
here
on
any
blog.
A
And
so
that's
done
so.
Basically
what
this
means
is.
We
have
a
copy
of
the
project
of
the
repository
as
it
existed
at
the
time
we
forked
it,
so
it
doesn't
keep
it
up
to
date.
So
if
there's
any
changes
to
the
upstream
repository,
then
it
will
it
will
not.
It
will
not
keep
it
up
to
date.
For
us,
that's
something
we
have
to
do
ourselves,
but
at
the
very
moment
they
are
both
in
sync.
So
the
antidote
repository
is
where
we
have
our
Docs.
That's
why
you
see
the
docs
directory
there.
A
Next
thing
is
our
blog,
so
our
blog
is
built
from
Hugo,
that's
kind
of
what
the
software
that
we
use
to
convert,
readme
or
rather
markdown
files
into
blog
content,
but
everything,
basically
that
you
might
want
to
contribute
to
is
underneath
content
here,
and
these
are
just
markdown
files.
That's
all
these
are
the
dot
MD
here,
that's
the
markdown
file.
You
can
see
that
you
can
see
kind
of
the
body
here.
You'll
see,
github
actually
renders
the
markdown
file
into
HTML
here
as
a
preview.
A
If
you
want
to
see
the
actual
markdown
text,
you
can
click
raw
and
you
can
see
that
it
outputs
the
raw
text
here,
we'll
look
at
that
in
a
in
a
in
a
in
an
actual
text
editor
very
shortly,
so
you
can
kind
of
get
a
better
view
of
that.
Also,
if
you
look
at
underneath
post
you'll
see
all
of
our
actual
blog
posts
here
so
and
you
can
see
if
you
look
at
raw
here,
you
can
see
that
there's,
the
the
you
know,
I'll
go
through
this
later.
This
is.
A
A
Ok,
so
that
has
that
that
that
that
has
us
in
a
good
position
to
start
contributing,
because
what
this,
what
we'll
do
is
we'll
actually
clone
our
fork
of
each
of
these
repositories.
Not
the
upstream
repository
will
quote
we'll
clone
our
copy
and
then
we'll
push
any
changes
to
that
and
and
we'll
we'll
be
able
to
we'll
be
able
to
contribute
from
there
using
a
pull
request
which
we'll
get
to
shortly.
A
A
A
A
Okay,
so
if
you
click
the
drop
down
now,
you'll
see
the
three,
the
three
repositories
that
we've
cloned
locally.
So
that
should
be
all
we
need
to
do
at
the
moment.
Really,
all
we've
done
with
the
github
client,
thus
far
as
we've
just
checked
out,
are
with
the
three
the
three
repositories
that
we
forked
we've
cloned
them,
which
which
creates
a
copy
of
those
repositories
locally.
So
all
the
content
that
you
saw
here
and
here
and
here
are
now
stored
on
our
hard
drive
locally,
which
means
we
can
change
them.
A
A
So
to
do
that,
let's
open
it
folder
and
if
you
go
to
on
Windows
its,
if
you
go
to
documents
and
then
the
the
subdirectory
github
you'll
see
the
three
folders
that
we
cloned
locally
each
of
these
folders
represents
the
one
of
the
three
repositories
that
we
cloned.
So
the
first
thing
we
want
to
do
is
go
to
NRA
blog
and
we're
gonna
use
this
as
an
example,
because
I
think
this
is
probably
one
of
the
more
common
things
that
people
might
want
to
contribute
to.
A
Actually,
instead,
one
of
the
one
of
this
is
actually
a
really
cool
way
to
do
this.
If
you
just
go
to
the
top-level
folder
here
and
you
say,
select
folder,
then
what
it'll
do
is
it'll
actually
open
the
entire
folder
here
over
to
the
left,
and
you
can
look
at
any
one
of
them
and
anytime
I
on
my
development
machine.
What
I
normally
do
is
I
opened.
The
I
have
a
folder
on
my
user.
It
within
my
user
directory
called
code
and
I
just
put
everything
underneath
that
it's
a
pretty
big
directory.
A
It's
got
a
lot
of
stuff
in
it,
but
what
I'll
do
is
I'll
open
that
folder
and
then
that
way
everything
is
accessible
to
me
here.
So
underneath
NRA
blog,
we
can
expand
that
you
can
see
again
that
the
the
content
that
you
saw
in
github
is
now
is
now
copy.
Basically,
is
its
what
that's,
what
a
clone
does
where
we
clone
the
content
here
locally
and
we'll
expand
a
content
and
will
expand
post
now
the
way
that
we,
the
way
that
I
usually
create
new
blog
posts,
is
rather
than
just
write
everything
from
scratch.
A
What
I'll
do
is
I'll
just
take
the
latest
blog
you'll,
see
that
we
have.
Let
me
make
this
a
little
bit.
Bigger
you'll,
see
that
we
have
the
the
latest
blog
here,
and
this
is
marked
down
by
the
way
these.
This
is
a
markdown
file,
so
dot
MD.
This
is
actually
not
markdown.
This
top
this
stuff
here
at
the
top,
is
actually
a
gamal,
but
you
really
only
need
to
just
copy
that
in
place
and
adjust
it.
A
If
you're
writing
a
new
blog,
if
you're
contributing
a
new
blog,
we
can
kind
of
help
you
out
with
this
stuff.
The
rest
of
it
is
marked
down
and,
as
you
can
see,
most
of
it
is
just
text.
It's
just
like
writing
stuff
every
once
in
a
while
you'll
run
into
something
that
looks
kind
of
funky.
If
you
look
at
this,
for
instance,
this
is
this
is
the
way
that
markdown
has
you
represent
links
where,
in
brackets,
you
have
the
text
of
the
link
and
then
in
the
parentheses
that
follow
you
have
the
actual
link.
A
Url
you'll,
also
notice
that
there
are
places
where
we
have
HTML.
This
is
really
not
super
necessary,
in
fact,
is
not
at
all.
The
only
reason
I
did.
This
is
because
I
want
I'm,
pretty
particular
with
how
images
get
represented,
and
sometimes
markdown
doesn't
let
you
do
the
specific
things
you
want
to
do,
but
there
is
a
way
to
represent
an
image
with
pure
markdown,
and
if
you
want
to
go
that
route,
that's
totally
fine.
A
Another
thing
here
you
can
see
is:
is
this
is
a
header,
so
headers
in
markdown
are
represented
using
these
hash
marks,
so
h1
would
be
a
single
one,
h2,
h3
and
h4,
and
so
on
and
so
forth.
You
can
see
this
is
a
list
so
again
just
space
and
then
the
list
item.
So
this
is
I'm
not
going
to
do
an
overview
of
markdown
entirely.
A
There's
there's
actually
really
good
documentation
that
I'll
point
to
at
the
end
of
this
that
you
can
use,
but
in
short,
let's
just
say,
we
know
how
to
write
markdown
and
we've
written
a
blog
post
again.
The
way
that
I
like
to
do
things
is
I
just
do
a
new
file
and
I'll
name.
It
follow
the
naming
convention.
That's
here
in
the
directory,
you
2:01
nine
say
what
is
it?
What
is
today?
A
Oh,
the
second
I
think
yep,
the
second
test
post
MD,
so
I'll
just
copy
an
old
blog
post
and
then
just
take
out
all
of
the
text
and
then
I'll
do
you
know
edit
the
I'll
edit
the
date
so
that
it
matches
today
because
that's
important
we'll
leave
the
featured
image
there.
That's
fine.
The
title
of
the
blog
post
is
important.
This
is
a
test
blog
post
and
yeah
I
wrote
it
so
I'll
do
that
and
I'll
say
hello
world
and
then
a
header
new
header.
A
This
is
cool
check
out
our
repo
and
then
in
that
I'll
just
do
a
link.
Github.Com
enter
a
learning,
ok
basic
blog
posts.
This
is
something
that's
compatible.
Hugo.
You
can
see
that
the
majority
of
this,
the
actual
body
of
this
is
just
simple
mark
down
with
some
llamo
at
the
top
that
tells
Hugo
what
to
do
about
the
post.
So
just
as
an
example,
that's
what
we've
done.
Let
me
undo
all
of
my
changes
there
and
close
that
file.
A
So
this
is
a
pretty
common
thing
that
you
might
want
to
do
if
you
want
to
write
a
new
blog
post
and
you'll
you'll.
Just
continue
on.
This
is
obviously
a
really
simple
blog
post,
but
let's
say
you've
finished
it
you've,
written
it
and
and
you're
happy
with
the
way
that
it
looks
I
and
you
want
to-
and
you
want
to
actually
contribute
this
upstream.
A
So
the
way
to
do
that
is
to
go
back
to
our
github
client
and
make
sure
you've
saved
it
by
the
way
I'm
using
keyboard
shortcuts
and
I,
probably
shouldn't
for
the
sake
of
the
video
you
can
go
to
save
here
or
you
can
hit
ctrl
s
like
I
like
to
do.
Basically,
if
there's
an
X
here,
then
you've
saved
it.
If
v/s
code
detects
that
you've
made
changes,
it'll
change
that
to
a
dot
indicating
that
you
need
to
save
it
so
make
sure
that's
done.
A
A
So
what
we
want
to
do
is
we
want
to
tell
oh,
this
is
just
one
file,
but
if
we
change
multiple
files
or
list
them
off
here,
you
want
to
make
sure
that
you
have
the
files
that
you
want
to
include
checked.
So
it
looks
like
it
checks
it
by
default,
but
just
make
sure
that
all
the
files
that
you
want
to
include
are
checked
there.
If
you,
the
best
thing
to
do
is
is
is
instead
of
saying
it
github.
A
The
client
adds
this
very
basic
commit
message
for
you,
I
like
to
do
something
a
little
bit
more
sort
of
friendly
and
human
readable,
so
contributing
a
sample
blog
post
and
then
give
it
a
good
description.
I
wrote
this
as
an
example
for
a
video
I
am
making,
and
this
is
useful.
The
description
is
actually
very
useful
because
it
gives
the
folks
that
are
going
to
review
your
post
a
lot
of
context
around
what
you're
doing
so.
Don't
try
not
to
leave
anything
blank.
Try
to
fill
in
and
you
know
more
information
is
always
better.
A
So
try
to
do
that
looks
like
you
can
add.
Co-Authors
I'm
not
gonna,
get
into
that,
and
that's
that's
that's
a
different
thing.
So
this
button
here
commits
to
master
basically
in
get
the
idea
of
a
commit
basically
says
it's
like
saving.
It's
basically
saving
a
record
of
the
changes
that
you've
made.
It's
like
a
point
in
time,
saying,
like
I,
would
like
to
update
the
the
knowledge
of
the
repository
with
the
changes
that
I
that
I've
made
here.
So
we'll
click
commit
to
master,
and
it's
done
no
command-line
needed.
A
A
One
thing
you
do
have
to
do
to
to
communicate
your
changes
to
github,
because
this
is
all
just
locally
changing
things
you're
going
to
want
to
push
origin-
and
this
is
a
fancy
word
for
saying
upload
your
upload,
your
changes,
so
you've
made
a
record
of
them.
You
saved
your
changes
to
the
file
as
it
pertains
to
get,
but
you
need
to
inform
the
upstream
repository
which
isn't
Hubb
about
those
changes,
so
go
ahead
and
do
that.
A
Very
cool
now
the
the
last
step
to
get
to
getting
this
change
integrated
with
the
actual
upstream
repository.
So
remember,
we've
pushed
all
of
our
changes
now
into
our
fork.
So
if
we
were
to
go
to
the
site
the
github
site
here-
and
we
go
to
our
our
Fork
NRA
blog
and
we'll
refresh
you
can
see,
it
says
this
branch
is
one
commits
a
head
of
NRA
learning
master,
meaning
the
upstream
repository
from
which
we
forked
this
one,
which
and
then
and
actually
prompts
you
to
open
a
pull
request
here.
A
You
can
also
do
that
here
in
the
client.
In
fact,
if
you
do
a
or
is
it
yeah
create
pull
request
so
you're
on
your
for
and
you
want
to
create
a
pull
request
and
it'll
automatically
open
that
same
link
for
you,
so
you
can't
do
a
pull
request
in
the
client
that
takes
you
back
to
the
web
UI,
which
is
fine,
because
you're
you're
not
again
you're,
not
using
any
sort
of
command
line,
client
or
anything
like
that.
A
Basically,
what
this
does
is
it
shows
you
the
difference
between
the
the
thing
you're
trying
to
contribute
to
and
the
thing
you're
trying
to
contribute
from
so
what
you're
doing
now
is
you're,
comparing
your
fork
with
the
upstream
repository,
so
the
two,
the
two
blog
repositories.
Yours,
is
more
up-to-date
and
what
you're
trying
to
do
is
you're
trying
to
say:
hey,
I
want
you
to
catch
your
fork
or
your
your
the
the
not
fork
the
base
repository
I
want
you
to
catch
your
your
copy
up
with
the
changes
that
I've
made.
A
That's
what
a
pull
request
means,
and
so
we
create
a
pull
request
and
you
can
kind
of
see
if
we
have
a
single
commit
here,
it'll
just
copy
in
the
title
of
that
commit
and
the
description
we
wrote.
If
you
have
more
than
one
commit
which
is
possible
like
say
if
we
made,
if
we
made
more
changes,
we
which
we'll
do
in
which
we'll
do
in
a
second,
then
the
the
description
might
not
be
correct,
so
just
make
sure
as
you
when
you
open
this,
don't
don't
just
accept
this.
A
Just
may
take
your
take
your
time
and
make
sure
that
the
description
is
the
way
you
wanted
the
head.
The
title
is
the
way
you
want
it.
You
can
set
these
if
you
want,
if
you
have
permissions
to
do
so,
I'm
logged
in
as
me
and
I
have
admin
permissions
over
this
reap
over
this
repo.
So
you
may
not
be
able
to
do
some
of
these
things,
but
just
make
sure
that
everything
can
to
add
more
detail.
You've
done
that
and
then
you
create
the
pull
request.
A
Now
again,
this
is
just
a
request,
so
you're
not
actually
integrating
the
changes.
Yet
that's
something
that
somebody
who
has
permissions
to
do
that
has
to
do
so.
What
will
happen
now
is
somebody
will
come
in
and
actually
review
the
content
and
they'll
go
to
this
tab
or
they
see
the
changes
you've
made.
They
might
provide
comments
here
so,
like
say,
like
hey,
maybe
add
some
tags.
A
As
an
example,
they'll
start
a
review,
they
might
say
like
hey-
and
this
is
this
is
really
short-
maybe
add
more
here
as
an
example.
Those
are
two
examples
and
then
what
they'll
do
is
they'll.
They'll
add
their
their
review
and
they'll
say
you
know,
comment
on,
looks
yeah
I
can't
I
can't
approve
my
own
pull
request,
which,
which
actually
makes
a
lot
of
sense,
so
they'll
comment,
and
this
is
pretty
common.
What
you'll
do
here
is
you'll.
Just
read
these
these.
A
These
excuse
me
you'll,
read
these
comments
and
make
changes
accordingly,
which
again
I'll
get
into
shortly.
One
interesting
thing
also
that
you
might
that
you
might
want
to
take
a
look
at
is
because,
for
the
blog,
specifically
we've
integrated
with
metla
Phi,
which
is
a
site
that
actually
builds
our
blog
for
us
and
you
can
see
we
have
a
deploy
preview,
which
means
you
can
actually
see
the
changes
that
you've
made.
So
if
you
open
this
link
this
details
link
here
in
the
deploy
preview,
you
can
actually
see
the
site
rendered
with
your
change.
A
So
it's
not
in
our
in
in
the
main
energy
lab
site,
but
it
actually
created
a
temporary
site
for
us
just
for
the
change
that
you've
made,
which
allows
you
to
see
it,
which
is
really
really
useful
and
and
and
especially
again,
if
you
don't
want
to
set
anything
up
on
your
local
system
with
like
hugo,
which
is
not
it's,
I
think
it's
easy,
but
I'm
a
developer.
So
a
lot
of
folks
that
aren't
used
to
dealing
with
that
kind
of
stuff.
It
isn't
actually
that
easy
in
retrospect.
A
So
this
is
an
extremely
useful
thing
to
have
integrate
and
that's
one
of
the
reasons
I
did
it.
So
definitely
take
a
look
at
that.
Let's
say
you,
you
either
saw
something
in
the
in
the
output
here
that
you
didn't
like,
or
you
saw
one
of
these
comments
here-
that
you're,
like
man,
you
know
I
they're
totally
right.
I
should
have
added
some
tags
or
maybe
I
should
have
added
more
content.
So
you
know
you
might
thank
okay.
This
is
sort
of
a
wanted
thing,
but
it's
not
true.
It's
not
true
at
all.
A
A
It's
all,
it's
all
public
and
I
would
recommend
that
the
way
that
you
do
the
way
that
you
continue
to
work
on
something
once
you've
pushed
it
is
you
just
make
the
changes,
so
the
pull
request
hasn't
been
merged,
meaning
you
can
continue
to
push
changes
and
all
of
those
changes
will
continue
to
get
integrated
with
that
pull
request.
So
let's
say
we
read
that
comment
that
says
you
need
tags
test
actually
needs
to
be
a
string
so
test
blog.
A
We've
addressed
those
two
comments
and
again
we
want
to
save
so
ctrl
S
or
go
to
save
and
we
have
those
changes.
If
we
go
back
to
the
github
test,
if
we
go
back
to
the
github
desktop,
you
can
see
a
little
bit
of
a
different
image.
Now
the
file
already
existed
and
we've
committed
that
that
that
new
file
was
created.
So
instead
of
seeing
another
new
file
change,
we
see
actually
an
existing
file
change
and
we
see
a
much
more
detailed
diff
between
those
two.
A
Okay
back
to
github,
and
if
we
just
refresh
the
pull
request,
we
can
see
that
at
the
very
bottom
here
we
have
a
new
commit
added
content
and
tags
per
comments.
You
can
see
all
the
net
Liffe
I
stuff
got
reach
triggered
it's
rebuilding
an
entirely
new
preview
site
for
us.
You
can
see
that
you
can
see
that
github
automatically
outdated.
This
comment
because
the
tags
line
that
was
commented
on
previously
has
actually
changed.
A
It
looks
like
the
comment
on
adding
more
content
hasn't
been
outdated
because
we
didn't
actually
change
this
line,
so
we
can
say
we
can
manually
mark
this
as
resolved.
This
is
pretty
common.
So
if
you,
if
you
see
a
review-
and
you
see
some
comments
and
you
fixed
those
comments
in
a
new
commit-
you
can
go
ahead
and
click
those
as
resolve
as
long
as
they
are
truly
resolved.
A
Don't
don't
ignore
comments
that
say
you
haven't
actually
fixed,
but
if
the,
if
you,
if
you,
if
you're
confident
you
fix
the
comments,
you
can
mark
them
as
resolved
and
and
that
way
it
keeps
things
nice
and
tidy.
All
of
these
things
again
have
checked
out.
If
we
had
any
issues
like
building
the
site,
some
of
these
might
turn
into
red
X's,
which
you
can
see
in
the
output
of.
If
you
click
details.
A
So
if
you
see
any
issues
there,
you
know
either
ask
for
help
or
take
a
look
at
the
details,
and
you
can
fix
some
of
those
issues
yourself.
But
if
you
look
at
the
new
preview
site
which
will
open
it
in
a
new
tab
and
we
go
to
blogs
and
we
go
to
test
blog
post,
you
can
see
we
have
the
tags
here
at
the
very
very
bottom
and
we
can
see
we
have
the
new
content
that
was
asked
for
so
very
cool,
and
that
is
really
it
at
this
point.
A
You
know
it's
it's
sort
of
a
back
and
forth
between
the
person.
That's
reviewing
your
content,
they'll
provide
helpful
cry.
It'll
always
be
constructive,
helpful
comments
aimed
at
making
the
content.
You
know
better
quality
and
making
sure
that
the
things
are
represented
properly
and
at
the
very
end
somebody
will
merge
the
post
and
again.
This
is
something
that
you
have
to
have
sort
of
permissions
to
do
so.
A
A
So
that's
it
basically
back
and
forth
between
the
person
reviewing
your
content
and
you
making
changes
to
respond
to
those
comments,
and
then
eventually
there
will
be
no
more
comments
and
the
merge
will
take
place
so
that's
contributing
to
the
blog.
There
are
other
areas
of
the
blog
that
you
might
want
to
contribute
to
I'll.
Just
mention
very
briefly.
A
Everything
underneath
content
is,
is
fair
game
you'll
see
that
each
dedicated
page
has
a
separate
directory
so
where
we
have
the
the
NRA
live
page,
for
instance,
you
can
see
that
there,
if
you
want
to
make
changes
again,
it's
just
marked
down.
There's
some
there's
some
very
minimal
yamo
at
the
top,
which
again
is
mostly
playing
English.
You
can
just
edit
that,
and
then
everything
here
is
is
markdown.
So
again
links
links
this
iframe
here,
I
didn't
actually
write
this
myself,
I
just
exported
it
for
myself
from
twitch.
A
A
Creating
a
new
page,
of
course,
is
also
fairly
easy
to
just
create
a
new
directory,
and
you
create
a
new
file
inside
that
directory
called
slash
or
underscore
index
MD.
So
there's
some
things
there
that
can
be
done.
Everything
else
under
themes.
You
kind
of
do
need
to
know
how
a
web
development
works,
so
I
would
I
would
say
stay
away
from
that
if
at
all
possible,
one
thing
you
might
also
want
to
know
is
underneath
the
static
directory.
A
All
of
the
images
excuse
me,
custom,
pickups,
all
of
all
of
the
the
images
that
we
use
are
stored
here,
so
you
might
want
to
pop
an
image
in
there.
If
you
have
a
new
image
you
want
to,
you
want
to
show
in
a
blog
post
or
something
like
that,
all
right,
so
that's
NR
a
blog.
The
last
thing
I
want
to
show
is
sort
of
the
same
process,
but
for
contributing
to
the
docs.
So
if
you
go
to
the
antidote
repo
you'll
see
that
we
have
directory
here
called
Doc's.
A
This
is
where
our
entire
documentation
site
is
shown.
Now.
This
is
actually
very
similar
to
the
way
our
blog
works,
because,
again,
the
source
is
in
github
and
it's
stored
using
something
kind
of
similar
to
markdown,
but
it's
actually
a
little
different.
It's
called
restructured
text,
but
it's
it's
basically
the
same.
If
it
the
same
purpose
as
markdown.
Just
does
it
a
little
differently?
You
can
see
that
all
of
our
Docs,
you
know,
are
on
this
antidote
project.
A
Read
the
docs
I/o
site
and
everything
kind
of
just
is
formatted
nicely,
and
it's
all
visual
and
there's
all
kinds
of
stuff
like
images
and
whatnot.
But
the
cool
thing
about
the
way
you
the
way
that
this
content
is
created
is
is
very
similar
to
the
blog,
where
it
uses
a
much
more
plain
text:
format
on
the
backend
inside
the
repo
and
then
the
read
read
the
docs.
A
Software
is
what
renders
that,
from
a
plain
text
format
into
the
nice
web
UI
that
you
see
there,
everything
inside
of
the
Doc's
is
organized
into
these
sub
directories,
so
you've
got,
for
instance,
let's
take
a
peek
at
the
the
page.
We
were
just
looking
at
where
we
see
the
contributing
page,
for
instance,
or
better.
Yet,
let's
look
at
the
community
resources
page,
because
this
is
something
that's
been
changing
frequently,
so
you
see
community
resources,
we've
got
a
few
headers
here:
weekly
stand-ups
community
forums,
github
all
kinds
of
stuff
like
that.
A
If
you
go
to
the
if
you're
editor
here
and
you
click
on-
let's
actually
close
all
of
these
the
blog
posts
we
were
working
on
before,
if
you
close
the
NRA
blog
all
right
back
to
Docs.
So
if
you
go
to
the
community
rst
file
again,
this
is
not
markdown.
This
is
restructured
text
and
it
looks
like
this.
This
actually
doesn't
have
syntax
highlighting
by
default.
So
you
should
definitely
do
that.
A
You
can
see
now
we
have
syntax
highlighting
so
kind
of
similar
to
what
we
had
in
markdown.
We
have
mostly
just
plain
English,
that's
kind
of
this.
The
story
here
there's
exceptions
to
that.
Of
course,
just
like
I
said
with
with
links,
there
are
specific
ways
that
you
need
to
represent
links
in
markdown.
We
have
the
bracket
and
parentheses
in
restructure
text.
A
We
have
this
backtick
on
both
sides
followed
by
a
underscore,
and
then
you
have
the
link
text
and
then
inside
these
two
carrots,
you
see
the
the
actual
link
contents
a
little
bit
more
complicated
than
markdown,
but
also
fairly
simple.
You'll
see
that
mostly
the
formatting
that
I
use
here
is
is
similar
to
markdown
in
the
in,
for
instance,
the
lists.
Those
are
the
same.
You
have
the
hyphens,
that's
that's
how
we
get
that's
how
we
get
these
lists
here.
You
see
the
links
here,
the
headers.
Those
are
also
kind
of
interesting.
A
If
you
look
at
the
top-level
header,
you'll
see
that
the
very
the
h1
has
all
of
these
equal
signs,
underneath
it
and
you'll
see
it's
the
same
length
as
the
header
text
same
thing
with
the
h2,
it's
just
a
different
header,
it's
just
a
different
character
to
represent
the
h2
underneath
so
instead
of
in
markdown,
we
have
the
hash
marks
in
front
in
restructure
text.
We've
got
this
stuff
underneath
and
everything
else
is
pretty
much.
The
same.
A
Like
I
said
the
majority
of
what
you'll
find
in
these
restructure
texts,
or
these
Mar
or
markdown
files
is
just
plain
English.
It's
just
that
whenever
you
need
some
extra
formatting
you'll
see
that
highlighted
the
way
that
you
contribute
changes
is
exactly
the
same
as
we
saw
in
the
blog.
So
if
you
made
a
change
here,
let's
say:
let's
just
add
something
sample,
foo
bar
and
again
save
and
you
go
to
github
you'll
need
to
change
your
current
repository
because
we're
not
working
in
the
NRA
blog
repository
anymore.
A
You
were
working
in
antidote
and
you
can
see
that
we
have
the
change
there.
So
again,
it's
an
exist
it.
The
file
already
existed,
because
this
is
part
of
the
existing
Doc's.
We
didn't
create
a
new
file,
but
you
can
contribute
this
exactly
the
same
way.
Now
again,
I
would
recommend
once
you're
once
you've
done
with
that.
A
The
next
step
is
to
open
a
pull
request,
because
again
this
is
a
new
repository
and
we
we
don't
actually
have
a
pull
request
and
is
it
existing
yet
so
we
would
need
to
create
that
just
like
we
did
last
time,
alright,
so
in
parting,
I
want
to
leave
you
with
some
resources
for
learning
the
two
things
that
I
really
don't
have
time
to
cover
here,
because
there's
a
lot
of
really
great
resources
for
more
about
them
in
that
is
those
that
is
the
to
plain
text
format
that
we
mentioned
previously,
which
are
marked
down
and
restructured
text.
A
So
the
best
place
to
go
for
learning
markdown
within
the
context
of
github,
because
it's
kind
of
what
we're
using
it
for
markdown
isn't
specific
to
github,
but
what
some
of
the
best
guides
for
learning
markdown
are
done
by
github,
because
they
actually
have
some
specific
things
they
built
into
the
way
that
they
use
markdown,
and
we
take
advantage
of
a
few
of
those
things.
So
I
would
highly
recommend
using
this
guide
for
learning
markdown.
A
There's
a
lot
there's
a
lot
that
you
learn
here
that
isn't
specific
to
github,
but
it
will
cover
some
of
the
some
of
the
some
of
the
ways
that
github
uses
markdown
as
well,
and
this
is
a
very,
very
good
overview.
You'll
learn
how
to
do
things
like
headers
how
to
emphasize
things
with
bold,
bold
text
and
italics.
A
Creating
lists
links
quotes
all
kinds
of
stuff
syntax
highlighting.
If
you
want
to
embed
some
code,
you
know-
maybe
not,
but
that's
that's
useful
anyway.
Get
a
guide,
github.com,
/features,
/font,
markdown,
very
useful
next
thing
is
restructure
text
a
little
bit
a
little
bit
less
attractive,
I.
Think
of
a
specification,
but
much
of
the
same
stuff
is
still
there.
So
if
you
wanted
to
search
for
things
like
you
know,
bullet
lists
you'll
find
that
here
and
it'll
explain.
You
know
just
have
hyphens.
A
You
can
also
do
other
things,
but
there
there
are
some
things
there
so
definitely
check
this
out.
This
is
under
doc,
utils
sourceforge.net
and
then
the
the
link
that
you
see
there,
doc
/r,
f,
/,
r,
st
slash
restructured
text
HTML
and
those
are
the
two
things
I
would
I
would
recommend
bookmarking
those
because
again
you'll
probably
use,
maybe
the
for
you
know
the
three
things
that
I've
showed
and
marked
down
immediately.
A
Basically
like
links
and
headers,
those
are
kind
of
the
big
things
that
you
might
want
to
use
in
in
either
format,
but
having
the
reference
within
reach
is
always
a
good
idea.
So
I
would
recommend
that
you
do
that.
Okay,
so
that
is
it
if
you
have
any
questions,
feel
free
to
pop
into
our
community
site.
So
if
you
go
to
the
that
the
docs
that
I
mentioned
earlier,
if
you
go
to
community
resources,
you'll
see
we
have
weekly
stand-ups,
we
have
community
forums
so
community
forums.
Here,
obviously,
everything
is
done
under
github.
A
We
also
have
a
discord
channel.
So
if
you
need
some
really
quick
help-
and
just
you
know
simple,
like
hey
what
helped
me
out
with
the
formatting,
for
you
know,
you
know
running
a
bold
text,
for
instance
or
bold
links,
something
so
you
know
maybe
combining
two
things.
Well,
we're
happy
to
help
you
out.
Discord
is
probably
the
best
place
for
that,
because
it's
nice
and
quick
and
easy
and
of
course,
all
the
other
ways
that
you
can
get
in
touch
with
us
are
here
and
yeah.
A
Hopefully
this
helps
get
over
that
hump,
where
you
don't
feel
like
you
need
to
be
a
developer
to
contribute
to
energy
labs.
This
was
a
little
bit
of
a
deep
dive,
but
hopefully
you
know
the
the
resources
here
can
help
you
out
with
contributing
to
the
to
the
various
parts
of
the
project.
Thanks
for
listening.