►
From YouTube: Contributing to Gatsby - Open Source Friday
Description
Gatsby is a React-based open source framework for creating websites and apps.
Join us live for Open Source Fridays at https://www.meetup.com/GitHub-Virtual-Meetup
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
Google+: http://google.com/+github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
Backstory
I
studied
cs
in
college.
That
was
my
first
time
programming.
But
by
the
time
that
I
reached
my
senior
year,
I
kind
of
decided
like.
Oh
I
don't.
I
don't
want
to
be
a
developer
because
being
a
developer
is
just
like
being
a
code
monkey
in
a
room
by
yourself,
and
I
also
think
I
didn't
really
have
any
good
role
models
when
I
was
in
college
like
people
in
tech
who
looked
like
me,
who
were
doing
work
that
I
wanted
to
do.
A
But
so
one
of
the
things
that
I
did
do
in
college
that
I
really
liked
was
being
a
ta
for
the
like
intro
intro
level,
programming,
cs
class,
and
so
I
really
loved
like
helping
people
go
from
not
understanding
a
thing
and
feeling
really
overwhelmed
to
being
like
okay,
I
kind
of
know
what's
going
on
and
I'm
like
more
confident
in
my
abilities
to
make
a
thing
yeah,
and
so
after
after
college,
I
went
into
education
instead.
A
So
I
did
an
americorps
program
called
city
year
for
a
year
where
I
worked
in
a
third
grade,
classroom
with
students
there
doing
like
in
classroom
support-
and
I
like
taught
my
third
graders-
how
to
code
on
our
lunch
breaks,
which
was
really
fun.
I
would
just
like
bring
a
couple
of
them
upstairs
and
we
would
do
the
like
code.org
curriculum
on
my
ipad,
oh
wow
and
yeah.
It
was
a
lot
of
fun
and
that,
like
seeing
how
excited
they
got
about
it
made
it
feel
me,
I
don't
know
it
just
made.
A
Programming
seem
more
fun,
whereas
you
know
in
college,
it's
like
I'm
doing
this
for
the
grade
and
so
that
I
can
graduate,
and
so
after
after
that
year
was
over.
Then
I
I
went
and
worked
at
code.org
as
an
intern
on
their
educate.
A
Excuse
me
on
their
education
team,
so
I
was
like
helping
write
curriculum
instead
and
then
from
there
I
went
to
work
at
girls
who
code
who
was
a
non-profit
focused
on
like
getting
middle
school
and
high
school
girls
interested
in
computer
science,
and
one
of
the
things
that
we
did
there
was.
A
We
wrote
all
of
these,
like
women
in
tech,
spotlights
to
basically
highlight
the
work
that
a
woman
is
doing
in
in
the
tech
industry
and
just
like
how
they're
using
programming
to
make
an
impact
in
their
communities
and
so
like.
While
I
was
writing
those
I
kind
of
realized
like
oh,
there
are
ways
to
to
like
help
the
world
for
lack
of
a
less
cheesy
phrase
by
by
being
a
programmer,
and
so
after
that
I
got
a
job
like
an
entry-level
software
developer
consultant
job
at
a
consultancy
called
thoughtworks.
B
York
or
which
office.
A
B
Yeah
yeah
international
as
well,
because.
B
Folks
in
brazil
downward
side,
yeah.
B
A
Nice,
that's
awesome,
yeah
they're,
really
great
and
I
love
them,
and
so
I
I
liked
being
a
developer.
A
I
feel
like
I
really
leveled
up
my
technical
skills
while
I
was
working
there,
but
something
that
I
was
really
missing
was
the
education
piece
and
kind
of
having
that
be
a
formal
part
of
my
job,
description,
yeah,
and
so
I
saw
a
couple
months
ago,
posting
on
twitter
for
the
for
the
gatsby
documentation,
team
and
so
applied
applied
to
that
because
it's
it
felt
like
a
much
better
blend
of
the
the
technical
stuff
that
I
had
learned
and
also
the
education
piece
that
I
felt
like
I
had
been
missing,
and
so
I
got
here.
A
Like
yeah,
I
did
a
lot
of
technical,
theater
yeah,
so
I
I
really
liked
lighting
design
when
I
was
like
a
junior
in
high
school,
which
is
when
you're
starting
to
look
at
colleges
and
for
some
reason
in
my
head.
I
thought
like
okay,
I'm
good
at
math
and
science,
but
I
don't
want
to
be
a
doctor.
A
So
that's
how
I
got
to
engineering
and
then
like
computer
electrical
engineers
is
maybe
like
lighting,
which
is
not
at
all,
and
so
I
just
kind
of
picked
it
because
I
don't
know
I
was
18
and
didn't
know
what
I
was
doing.
B
Excellent
yeah:
do
you
know
we're
in
the
bay
area?
Do
you
know
chloe
condon
who's,
a
devrel
at
at
microsoft?
She
originally
came
from
theater
and.
A
A
B
Hackbright,
actually,
what's
the
local
that
bootcamp
or
not,
but
a
bootcamp,
but
yeah,
that's
yeah,
fascinating,
I'm
always
interested
with
people's
transition
stories
of
getting
into
tech.
Because
yeah,
you
have
a
cs
background,
but
you
ended
up
eventually
getting
there
through
education,
yeah.
A
B
Is
yeah?
It's
intriguing,
it's
like
something
to
think
about
too,
as
well
for
folks
who
are
just
now
getting
started.
Is
that
there's
no
like
golden
path
for
getting
into
engineering
or
programming
and
getting
a
tech
job?
It's
it's
just
about
interest
and
sort
of
like
continuing
down
that
path,
which
it
sounds
like
that's
what
you're
doing
with
code.org
and
teaching
kids
and
which
is
amazing.
A
Totally-
and
I
definitely
think
like
as
somebody
who
was
sort
of
a
career
change
like
bringing
in
a
lot
of
skills
from
teaching
or
from
like
whatever
background
you
came
from
before
kind
of
gives
you
a
leg
up
in
a
way,
because
there
are
like
people
who
don't
have
great
communication
skills
or
they're
like
oh,
we
need
to
communicate
this
idea
so
that
other
people
can
understand
it.
How
do
we
do
that?
B
Exactly
and
speaking
of
skills,
those
skills
have
gotten
you
here
to
working
at
gatsby,
now
full
time
for
the
company
and
we're
gonna
talk
about
that
in
a
sec.
But
I
just
want
to
say
hello
to
ritman
for
saying
hello
in
the
chat
and
it's
ishnan,
I'm
not
sure
if
that's
a
hello
or
yeah,
but
you
do
have
a
an
emoji
there
or
emote
and
then
someone's
you
do
have
a
fan
in
the
chat
too.
It's
called
calhousie
kelsey.
B
B
A
Yeah
so
gatsby
like
fundamentally,
is
a
framework
that
helps
you
build
react
sites,
so
one
of
the
nice
things
that
it
does
is
it
kind
of
bakes
in
a
bunch
of
like
things.
A
That
would
be
hard
to
do
if
you
were
just
a
single
developer,
building
your
own
site
or
building
a
site
for
like
an
agency
so
like
we
try
and
think
about
things
like
performance
and
accessibility
and
security
and
kind
of
bake
that
into
the
framework,
so
that
you
don't
have
to
spend
as
much
time
thinking
about
it
and
you
can
just
focus
on
like
how
do
I
build
the
react
components
and
the
pages
and
like?
Where
do
I
pull
in
data
from
so
that's
that's
kind
of
the
gist
of
it.
B
A
B
And
yeah,
I
like
the
the
idea
of
like
static
generation,
which
gatsby
sort
of
came
out
the
gate,
pretty
strong
back
when
react
was
still
sort
of
figuring
itself
out
so
being
able
to
have
that
context,
but
also
in
my
modern
web
development
javascript
framework
world,
which
is
react.
That's
what
I
spent
a
lot
of
my
time
in
so
yeah,
I'm
familiar
with
it.
B
Hopefully
anybody
in
the
chat
if
you've
used
gatsby,
let
us
know,
let
us
know
what
projects
you're
you're
working
on
that
use
gatsby
or
what
projects
you
would
like
to
work
on,
and
then
we
can
see
if
it's
a
good
fit
might
be
an
example.
Actually,
for
you
too,
as
well,
which
I
want
to
talk
about
your
role
at
gatsby
and
what
you're
sort
of
focused
on
day-to-day.
A
Yeah,
so
I
I
am
on
well,
I'm
a
documentation,
engineer
and
the
company's
kind
of
in
a
transition
period
right
now,
where
we're
moving
from
having
like
a
documentation
team
to
having
more
of
this
like
cross-disciplinary
squad
model
where
now
it's
like.
The
squads
are
kind
of
the
new
teams
where
you've
got
like
a
designer
and
developers
and
like
a
product
manager
and
a
documentation
engineer
so
rather
than
rather
than
like,
just
being
the
sole
person
writing
the
documentation.
A
B
Yeah
and
that
at
I
like
that
model,
and
it's
something
that
we
do
at
github,
so
I
don't
do
full-time
engineering
at
github.
I
do
devrel,
so
I
do
a
lot
of
interactions
with
the
community,
as
well
as
with
the
engineering
teams,
but
what
they
do
is
when
they
ship
features
primarily
I've
seen
this
with
the
api
is
we
have
a
change
log
and
everybody
has.
A
B
Ship
a
change
log
and
that
helps
the
documentation.
Actually
documentation
has
to
get
shipped
alongside
the
feature,
and
the
feature
is
new,
which
I
like
I
like
seeing
that
stings
get
blocked.
If
there
are
no
docks,
because
there's
nothing.
A
B
Yeah
and
there's
a
question
in
arn
for
vvv:
I
don't
know
if
you
know
this,
I
know
the
answer
but
I'll
pitch
it
to
you.
What
are
advantages
advantage
to
the
gatsby
besides
server
side,
rendering.
A
A
Ideally,
if
everything
has
gone
right,
your
site
should
be
really
fast
because
at
build
time
it
sort
of
goes
through
and
does
without
getting
too
in
the
weeds
it
like
does
all
of
the
building
of
like
the
specific
pages
and
pulling
in
data
yeah.
B
A
B
Yeah
and
I've
got
the
like
literally
from
the
website,
some
bullet
points
as
well.
B
The
incremental
builds,
so
if
you
do
build
like
your
about
page,
the
about
page
gets
it
built
gets
built
as
opposed
to
the
entire
site.
I
think
the
some
of
the
built-in
image
handling
has
been
nice
and
it's
something
that
people
kind
of
point
to
as
sort
of
the
model
for
progressive
loading
images,
I've
seen
kyle
kyle
being
the
ceo
and,
I
guess,
original
creator
of
gatsby
I've
seen
them
talk
at
different
conferences
and
meet
up
here
about
that
one
feature
and
handstand.
A
B
Been
something
that
I've
been
super
excited
about
since
the
beginning
and
seeing
other
people
sort
of
lead
with
that
as
an
example
of
how
you
handle
images
so
definitely
check
out
the
examples
and
check
out
the
blog
posts
and
talks
around
gatsby
like
there's
a
very
large
community
around
it
so
arn,
you
there's
definitely
plenty
of
information
out
there.
We
can
share
links
later
and
we
can
also
walk
through
that
in
a
moment
too,
and
then
praiag
s
apologies
from
the
pronunciation
of
the
twitch
handle.
B
But
can
you
talk
more
about
the
documentation
engineering
role
which
you're
our
first
documentation
engineer
person
in
that
field?
That's
been
on
open
source
friday,
and
I
think
it
might
be
something
that
most
people
don't
think
of.
As
like
a
like
a
role,
you
could
do
as
an
engineer.
So
do
you
want
to
speak
just
a
little
bit
more
and
like
what
that
entails
and
like
what
sort
of
companies
are
looking
for
that
role.
A
B
A
Some
kind
of
title
where
it's
like
your
focus
is
on
teaching
people
which
still
requires
like
the
technical
background,
because
you
have
to
know
what
you're
talking
about
yeah
but
but
like
trying
to
focus
on
communicating
what's
happening
internally,
either
externally
or
sometimes
even
to
like
other
people
in
the
company,
like
something
something
that
I'm
thinking
about
now
and
full
disclosure.
I'm
also
new
to
gatsby.
I've
only
been
there.
This
is
week
three
or
week
four
or
something
like
that.
A
So
a
lot
of
a
lot
of
things
are
still
kind
of
being
decided
on
in
terms
of
what
I'm
gonna
do,
but
something
something
that
I'm
thinking
about
is
like.
There's
a
lot
of
sort
of
pockets
of
knowledge
internally
that
even
our
internal
engineers
sometimes
are
like.
Oh,
I
only
know
about
this
thing
because
I
heard
it
in
a
slack
channel
or
like
somebody.
I
had
to
ask
for
help
to
figure
that
out,
so
my
goal
is
to
how
to
try
and
figure
out
how
to
make
that
easier.
A
B
Yeah-
and
I
would
say
too,
as
well
like
being
able
to
explain
things
and
being
having
that
being
that
introduction
to
how
people
can
explore
a
feature.
Is
it's
huge
because
I've
used
a
lot
of
products?
I've
used
a
lot
of
open
source
libraries
that
I
had
to
figure
out
on
my
own,
and
I
think
the
when
you
have
that
assumption
of
like
people
will
figure
this
out.
That's
when
you
know
you
you're
failing.
B
It's
something
that's
intuitive
and
like
people
discover
things
naturally
and
can
discover
how
to
sort
of
advance
to
the
next
level.
That's
where
you
want
to
be
so
like
being
able
to
really
slow
down
and
make
sure
people
can
use.
The
thing
super
helpful
and
I
just
want
to
mention
too
as
well.
This
is
this
conversation
is
about
gatsby,
so
folks
are
looking
for.
Comparisons
like
we
are
going
to
do
comparisons,
but
if
you
do
want
to
learn
about
next.js,
we
do
have
an
entire
interview.
B
We
did
with
nexjs,
it's
go
to
youtube.com
github,
where
you
can
learn
about
next
and
their
benefits
and
how
you
can
contribute
this
project.
But
I
do
want
to
know
how
to
I
guess
how,
if
I
wanted
to
jump
in
the
gatsby,
maybe
I've
used
it
a
couple
times
or
maybe
I
just
want
to
try
it
out
for
the
first
time.
I
guess
what
is
the
sort
of
like
central
location
for
folks
to
basically
try
it
out.
A
Yeah
so
there's
kind
of
like
two
tiers
of
getting
started
with
gatsby.
There's
like
how
do
I
get
started
with
gatsby
on
my
own
project
like
I
want
to
use
gatsby
as
a
vehicle
to
build
something
else,
and
then
the
second
part,
I
guess
maybe
more
advanced
is
like
if
you
want
to
contribute
to
gatsby
itself
like
as
a
tool
or
the
documentation.
A
So
if
you're
totally
new
to
gatsby
and
want
to
get
started,
this
is
the
docs
page.
We
do
have
a
tutorial,
that's
kind
of
a
step-by-step
guide
through
how
to
set
things
up
and
tells
you
a
little
bit
of
information
about
like
just
what
even
is
gatsby.
How
do
we
do
styling?
How
do
we
do
data
like?
Where
does
the
data
come
from,
and
so
that's
that's
a
good
entry
point.
A
If
you're
looking
for
like
a
total
introduction
and
then
if
you
want
to
contribute,
there's
kind
of
two
ways
that
you
can
contribute,
you
can
contribute
to
like
the
gatsby
framework
itself,
like
the
code
or
you
can
contribute
to
that
docs
site
yeah,
and
so
this
this
is
the
github
repo
for
both
of
them.
If
you
look
at.
A
B
A
B
Yeah
excellent
yeah:
this
is
the
repo
that
we're
sort
of
just
perusing
through.
I
think,
a
lot
of
people,
they
first
sort
of
jump
into
a
repo
to
for
contribution
and
to
see
what's
happening.
I
like
to
use
it
as
a
gauge
to
see
if,
like
it's
the
thing
of
being
used
so
like
already.
A
B
See,
there's
a
quarter
million
people
using
it
and
projects
at
least
that
are
open
sourced,
I
think,
is
how
that
number
works
and
then,
as
far
as
like
issues,
poor
requests,
you
can
sort
of
get
a
gauge
of
like
how
things
are
sort
of
operating.
You
can
see.
One
hour
ago
we
liko,
which
I
know
liko,
definitely
seen
a
round
he
had
to
commit.
B
They
actually
got
merged
in
an
hour
ago,
which
is
pretty
cool,
so
you
can
see
there's
some
pretty
good
activity
happening,
but
I
think
if
we,
if
we
focus
more
on
the
contribute
to
gatsby
for
the
rest
of
the
conversation,
I
think
we
could.
I
think,
it'll
be
a
lot
of
sort
of
nuggets.
We
can
sort
of
discover
together,
but
I
see
the
contributing
india
is
usually
the
first
place
I
look
at
and
then
I
find
out
it
takes
me
directly
to
here
to
how
to
contribute.
B
So
I
actually
have
this
open
in
the
tab,
thanks
for
folks
who
are
looking
to
get
their
first
contribution
during
hacktoberfest
or
first
contribution
just
in
general,
it's
definitely
a
great
place
to
start
for
sure.
So
do
you?
I
guess
week
three,
but
I'm
curious
to
understand
like
how
gatsby
sort
of
handles
participation
in
the
repo
is
there
like
open
source
managers
maintainers
or
is
it
similar
to
your.
A
Yeah,
so
it's
it's,
it's
definitely
an
open
source
project.
So
we
we
have
in
the
issues
we
have
like
community
members
reporting
things
that
are
wrong
making
suggestions,
and
so
all
of
the
issues
that
are
opened
get
automatically
tagged
with.
A
I
forget
the
exact
label,
but
it's
like
there's
a
bot
that
adds
a
tag.
That's
like
triage
needed
or
something
like
that,
yeah
so
and
then,
and
then
there's
like
a
rotation
within
our
engineering
team
to
to
like
go
through
everything
that
needs
triage
and
basically
decide
like
which
team
within
gatsby
is
responsible
for
this.
So
for
docs
a
lot
of
times,
they'll
add
these
like
status.
A
That's
on
me,
and
so
then
I'll
go
and
like
look
at
it
and
give
comments
and
kind
of
move
it
from
the
point
it's
at
now
to
when
it's
done
yeah.
It.
A
B
And
that's
actually
not
to
move
too
fast
over
that,
but
something
that
I
think
is
missing
a
lot
of
times.
When
people
go
to
do
contributions
in
oktoberfest
or
just
in
general,
you
could
spend
a
lot
of
time
working
on
something
that
you
think
belongs
in
the
code
base
or
belongs
to
the
documentation.
A
A
B
The
maintainer
yeah.
A
A
B
Sean
actually
had
a
question
about:
how
do
you
know
how
do
you
figure
out
going
back
to
documentation
real
quick?
How
do
you
know
what
to
document
and
whether
documentation
is
hitting
the
mark
like?
Is
there
a
way
to
target
and
get.
A
A
The
follow-up
like
you
have
to
do
that
after
you've
figured
out
what
to
write
for
me,
like
the
thing
that
I
try
and
keep
in
mind
so
like
from
from
curriculum
writing.
There's
this
framework
called
understanding
by
design
and
it's
a
it's
a
really
widely
used
framework,
not
in
the
like
technical
sense,
but
of
just.
A
Yeah
there
there's
yeah
it's
it's
a
whole
book
and
there's
a
bunch
of
a
bunch
of
different
people
have
have
written
about
it,
but
the
basic
idea
is,
like
you
start
with
your
end
goal.
First,
like
you
always
start
with.
What
do
you
want
learners
or
like
users
in
this
case,
to
be
able
to
do
and
to
be
able,
there's
a
real
focus
on
transferable
skills
so,
like?
A
What
do
you
need
to
understand
in
this
context,
but
also,
what
do
you
need
to
know
to
like
be
able
to
go
off
and
do
things
on
your
own,
and
so
that's
kind
of
that's
always.
My
starting
point
is
thinking
about
like
what
is
what
is
the
goal?
What
are
we
trying
to
help
users
achieve
and
then
from
there
you
can
kind
of
break
that
down
into
like
okay.
A
I
want
them
to
understand
like
how
data
works
in
gatsby
and
then
you
can
like
break
it
down
from
there
and
go
into
like
what
are
the
like.
The
next
stage's
assessment
like
what?
A
What
are
the
things
that
I
need
to
be
able
to
see
a
user
do
to
prove
that
they
have
this
understanding
and
then
from
there
you
can
kind
of
figure
out
like
okay,
what's
the
best
way
to
teach
students
each
of
those
things
so
for
for
me,
it's
always
about
like
starting
with
the
big
picture
and
then
kind
of
breaking
it
down
and
getting
more
granular
from
there,
and
I
think
I
think
that
sometimes
the
tendency
is
for
people
to
be
like.
A
Oh,
I
understand
this
concept
and
I
want
to
just
like
jump
right
into
teaching
that
thing,
but
I
think-
and
this
is
this
is
maybe
a
kind
of
a
problem
with
the
way
that
our
docs
have
grown
so
far
is
like
then
there's
less
of
a
cohesive
path
through
things,
it's
like
you've
got
a
really
good
dock
on.
You
know
bringing
in
data
from
wordpress
or
whatever,
but
like
how
does
that
fit
into
the
whole
and
into
this
like
learner's
journey
through
your
repository,
oh.
B
Yeah,
I
I
am
very
much
thinking
about
that
right
now
for
myself,
because
I
teach
a
lot
about
github
actions
and
I'm
doing
youtube
videos
primarily
as
the
medium
to
do
that,
mainly
because
I'm
just
exploring
the
medium
right
now
and
I
I'm
thinking
about
how
each
video
connects
to
the
last
one
because
yeah,
I
think
with
like
this
understanding
like
how
youtube
I
don't
understand,
youtube's
algorithm
by
any
means,
but
understanding
how
there
is
an
algorithm
that
you
want
people
to
click
through
to
the
next
one.
B
A
B
I
guess
if
you
have
as
you're
explaining,
if
you
have
the
big
picture,
you
can
then
have
the
sort
of
outline
and
steps
eventually,
as
long
as
you
know
what
the
goal
is,
which
is
right.
A
Don't
don't
get
too
in
the
weeds
before
they
kind
of
have
a
big
picture
understanding,
because
yeah
there's
like
no
sense
in
in
going
into
super
deep
detail
if
they
like,
are
just
it's
just
not
gonna
go
over
their
heads
anyway,.
B
Yeah
and
that's
the
I
don't
know
how
long
you've
been
doing
react
programming
at
all.
Actually,
how
long
have
you
been
doing
react.
B
Okay,
yeah,
so
I've
been
doing
it
since
the
beginning,
which
is
not.
B
B
That
one
meme
of
the
guy
who
talks
about
aliens
on
the
history
channel
documentary
and
it's
like
aliens
like
that's
how
I
feel
about
every
time
someone
talks
about
jsx
or
talk
about
the
virtual
dom
when
at
the
end
of
the
day,
all
I
want
to
do
is
make
a
website
like
I'm
not.
B
And
focus
that
is
something
that
too,
I
talked
to
michael
jackson
and
ryan
florence
about
this,
and
they
do
training
on
specifically
react
training
and
they
spend
way
more
time
talking
about
react
and
they
learn
how
to
do
that.
Even
though
we
have
this
like
virtual,
dom
the
router
like
how
graphql
or
redox
or
whatever
all
that
works
like
they
do
a
very
good
job
of
actually
avoiding
like
talking
about
all
the
stuff.
B
You
don't
need
to
talk
about
and
focusing
just
on
this
thing,
which
is
react
or
at
this
point
like
we're
talking
about
gatsby,
so
just
focus
on
the
feature
and
gatsby
that
we
need
to
share
and
get
get
across
and
be
able
to
have
those
sort
of
like
web,
like
the
internet
of
gatsby.
B
Sort
of
linking
all
to
all
the
way
to
this,
like
one
central
thing
that
we
sort
of
landed
on
so
sorry
my
excitement
and
the
way
you're
explaining
this
is
like
yes,
this
makes
so
much
sense.
This
is
what
I'm
doing
nice
excellent.
So
I
think
we
took
a
little
tangent
on
like
talking
about
like
higher
level
like
how
documentation.
How
do
you
sort
of
like
talk
about
how.
B
I
think,
coming
back
to
this
p
this
issue
and
how
the
labels
are
reviewed.
I
did
notice
that
gasbot.
I
think
it
was
the
bot
you
were
yeah
chatting
mentioning
yeah.
A
So
that
happens
yeah,
I
don't
actually
know
how
it
works,
but
I
know
that
when
you
open
a
new
issue,
it'll
add
that
triage
needed
label
to
it
and
then
one
of
our
engineers
will
go
through
and
decide
like.
Okay,
who
internally
needs
to
look
at
this
and
then
from
there
we'll
sort
of
have
a
discussion
about
like
okay?
A
What's
the
action
plan
for
this
issue,
if,
if
you
are
a
contributor
and
decide
to
open
an
issue,
make
sure
to
have
like
reproducible
steps,
if
you
find
a
bug
or
something
like
that,
because
that
really
helps
us
figure
out
like?
Is
this
really
a
problem?
Is
this
just
a
problem
with
like
your
local
setup
or
like
with
gatsby
as
a
whole?
A
And
so
that's
that's
definitely
something
to
make
sure
that
you
include,
and
then
at
least
something
that
I
try
to
do
is
like
clearly
outline
what
the
steps
are
to
resolve
this
issue
kind
of
like
acceptance,
criteria
or
really
just
like
a
checklist
of
like
these
are
all
the
things
you
have
to
have
before
we
can
close
this
issue
so
that
then
the
sort
of
next
piece
is
either
you
or
some
other
person
who
sees
the
issue
can
decide.
Oh,
this
is
a
problem
that
I
know
how
to
solve.
A
I
want
to
work
on
it,
and
so
then,
at
that
point
you
would
kind
of
comment
on
this
issue.
Saying
like
can
I
work
on
this
and
then
one
of
the
internal
engineers
would
say
like?
Yes,
you
can
and
then
assign
it
to
you
and
then
you
go
off
and
write
code
and
or
docs
yeah.
B
And
yeah
it
sounds
like
a
magical
place
and
makes
me
want
to
go
to
grab
an
issue,
but.
B
At
this
and
what
we
I
think
this
might
I'm
not
sure
if
this
is
a
gatsby
employer.
Actually
I
could
actually
find
out
doesn't
look
like
a
gatsby
employee,
but.
B
Up
a
pr
and
but
there's
no
issue
attached.
B
I
believe
so
documentation.js
example
caption
string,
yeah.
We
don't
have
to
dig
in
specifically
this
one,
but
I
was
just.
I
was
going
to
comment
on
the
fact
that
oh
did
we
just.
We
just
got
a
new
one
triage
needed
two
minutes
ago
wow,
but
I
was
going
to
comment
on
how
little
issues
are
here
that
need
triage.
So
it
seems
like
someone's
working
right
now.
A
Yeah
there
there's,
I
think,
yeah
I
think
I
saw
in
stand-ups.
Somebody
was
gonna
work
on
triaging
things.
Oh.
A
But
yeah
so
then,
then
sort
of
the
next
step
is
to
go
and
look
for
because
because
once
things
get
triaged,
sometimes
it's
like.
Oh,
this
is
a
problem
that
we
need
to
handle
internally
and
so
we'll
have
our
developers
work
on
it.
A
But
sometimes
it's
a
thing
where
like
oh,
this
is
something
that
needs
to
be
fixed
and
is
maybe
a
good
like
entry
point
for
somebody,
who's
new
to
the
repo,
and
so
in
that
case,
there's
a
different
label
that
will
apply
right
now
because
it's
october
fast,
it's
the
octoberfest
label,
yeah.
A
B
A
If
you
want
to
contribute
to
the
repo,
that's
a
good
place
to
start,
it's
like
look
for
those
two
labels
separately
together.
Oh
there's,
also
one
that's
good
first
issue
which,
if
you're
totally
new,
is
a
good
place
to
start.
A
B
A
Yeah,
actually,
for
so
part
of
my
job
when
I
first
started
was
like
identifying.
Oh,
these
issues
would
be
good
for
hacktoberfest
and
like
getting
them
ready
so
putting
in
those
like
lists
of
steps
that
need
to
be
done
for
each
issue.
But
then
it
was
like
you
know,
two
or
three
days
before
october
started
and
I
would
like
add
the
label
and
then
almost
immediately.
A
Somebody
would
pick
it
up
and
I
was
like
I'm
glad
that
you're
so
enthusiastic
about
contributing
but
you're
like
wait
two
days
so
so
yeah
a
bunch,
a
bunch
of
the
issues
have
have
been
picked
up.
Yeah.
B
A
B
Oh
yeah,
it
looks
like
looks
like
it's
doing
something
they
found
an
issue
and
they
have
reproducible
steps
too,
which.
A
B
Valuable
to
have-
and
this
is
something
that
I've
actually
started
doing
for
my
good
first
issues,
because
I
find
good
first
issues
are
not
meant
for,
like
I'm
just
going
to
throw
a
bunch
of
easy
stuff
that
I
don't
want
to
do
it's
more
of
like.
I
want
to
throw
a
bunch
of
easy
things
that
people
can
have
breadcrumbs
into
contributing
to
the
project
and
then.
B
Community
like
join
the
discord,
join
the
slack
or
whatever
it
is
and
feel
like
you're,
a
part
of
it
so
like
actually
having
a
solution
for
how
to.
A
A
Yeah-
and
I
think
that
that's
great-
because
it's
it's
like
scaffolding,
their
experience
pretty
much
because,
like
there's
such
a
huge
learning
curve,
if
this
is
your
first
time
contributing
to
open
source
in
general,
just
like
the
whole,
how
do
I
fork
a
thing
and
then
how
do
I
open
a
pull
request
and
what
is
a
pull
request
like
that?
That's
like
enough
to
focus
on
for
your
first
thing.
Without.
B
B
And
I
would
say
anybody
who
is
a
at
that
point
that
megan
just
described
we
do
have
an
intro
to
github
courses
on
lab.hito.com,
so
definitely
check
this
out.
I
should
probably
I
should
have
had
a
link
ready
for
that,
but
they're
all
self-paced
learning
it's
actually
built
on
the
same
technology
that
your
your
gas
bot
is
built
on.
A
B
So
integrates
with
the
with
the
github's
api
directly,
and
so
you
integrate
you
learn
through
github
prs
and
github
repos.
So
it's
a
unique
way
to
learn
some
of
this
stuff,
but
yeah
now
back
from
our
commercial
break
and
continue
on
this
always
be
always
be
selling.
B
There's
a
lot
of
thank
yous
actually
in
the
chat,
and
I
appreciate
everybody
who's
following
the
channel
if
you
want
to
learn
more
about
open
source
and
how
to
contribute
and
talk
to
project
maintainers
like
megan
from
gatsby
just
hit
the
follow
and
you
get
notifications
every
time
you
go,
live
on
this
channel
to
talk
about
open
source,
so
the
yeah,
so
it
looks
like
based
on
the
the
hacktoberfest
label.
You've
got
a
lot
of
back
and
forth
on
folks
who
are
interested
in
working
on
this.
B
None
of
these
folks
look
like
they're
all
any
of
them.
Look
like
gatsby
employees
looks
like
a
bunch
of
people.
B
B
That
with
companies,
but
not
everybody,
gets
that
privilege,
I
guess,
but
yeah
very
cool,
so
peter
was
in
there
and
providing
even
as
of
two
hours.
One
hour
ago
looks
like
we're.
We
have
some
active
communication
which
sometimes
could
be
a
concern
for
folks
who
want
to
contribute
with
hacktoberfest
and
sometimes
like
myself.
I
have
to
wait
like
a
day
before
I
can
respond,
because
I've
got
a
couple
other
things
to
do.
My
project
kind
of.
B
B
A
Should
have
started
with
that,
I
guess
yeah.
This
is
sort
of
our
like
umbrella
issue,
that's
giving
you
some
introduction
of
like
how
hacktoberfest
works
and
like
how
to
find
good
labels
in
our
repo,
oh
and
also
plug
for
swag.
A
B
Okay,
very
cool,
follow
the
instructions
yeah.
It
looks
like
there's
some
customer
support
tickets
coming
in
too
as
well,
but
yeah
very
cool.
I
like
that
gatsby
actually
took
a
time
to
kind
of
announce
their
intentions
at
hacktoberfest.
I
think
this
year
we've
we've
focused,
and
I
say
we,
the
hacktoberfest
team
has
pivoted
into
the
opt-in
model
for
hacktoberfest,
so
projects
that
are
opted
in,
which
I
know
gatsby
is
I've.
Seen
them
in
the
list
can
help
people
get
their
hacktoberfest
t-shirt
or
tree
planted.
B
B
Yeah,
no,
if
I
had
my
sticker
cam
on
I'd
share
it,
but
I
didn't
have
it
set
up.
I'm
still.
This
is
my
third
week
using
this
setup,
so
I
don't
have
my
all
my
other
cameras
set
up
to
properly
share
my
office,
but
I'm
dead,
everybody
watch
older
videos
to
see
my
my
sticker.
I
have
a.
B
I
usually
switch
to
the
the
sticker
cam
and.
B
A
That
would
have
been
a
good
idea.
I
should
have
picked
one.
Let's
see,
I'm
trying
to
think
of
which
ones
don't
already
have
people
on
them.
B
Yeah,
we
could
also
do
this
little
assigned
to
nobody
flag
and
there's
one
other
thing.
Also
a
brief
commercial
break.
I've
been
doing
a
youtube
series
called
get
action,
traction
and
I
built
this
action
which
I
gatsby
doesn't
have
to
use
this,
but
I'm
just
sharing
it
for
folks
who
have
similar
issues
of
assigning
signing
issues
to
people.
B
I
built
that
action
to
so
people
can
take
action
and
assign
themselves
to
issues,
and
I
do
this
out
of
necessity
for
myself,
because
I
don't
have
a
team
and
like
my
project,
we
have
like
a
handful
of
contributors,
but
it's
an
action
where
you
just
write
dot,
take
in
the
comments
of
the
issue
and
then
that
person
who
said
take
it
assigns
them
to
through
the
action
spot.
So
folks
who
are.
B
In
something
like
this,
all
the
code
is
open,
source
and
freely
licensed
so
feel
free
to
take
it
and
do
your
will
and
whatever
you
would
like
to
do
or
embed
it
into
gas
bot
too
as
well,
which
is
yeah
yeah.
I
wrote
this
in
bash,
mainly
because
I
was
learning
bash
while
writing
this,
but
you
can
see.
I
just
have
a
simple
curl
command
that
assigns
whoever
commented
to
that
issue
and
that's
how
it
works.
B
But
moving
back
to
gatsby
yeah
I
mean
we
don't
have
to
I'm
actually
curious
about
more
inclusive
language
in
docs.
A
Oh
yeah,
that's
that's
one
that
has
been
open
for
a
little
while
and
this
this,
I
guess,
is
a
good
sort
of
more
general
tip
on.
Like
writing
documentation.
You
don't
want
to
make
assumptions
about
what
people
know
and
like
what
is
going
to
be
hard
for.
B
A
And
I
think
I
think
that
the
intention
is
to
try
and
make
it
seem
less
scary
of,
like
you,
just
have
to
do
this
and,
like
it'll,
be
easy
to
do
whatever
yeah,
but
then
to
be
the
person
who
gets
stuck
on
that
step.
It
then
like.
Not
only
do
you
have
a
problem
now,
you've
got
some
kind
of
bug:
something's,
not
working,
but
also
you're,
doubting
yourself
of
like,
oh
god.
This
was
supposed
to
be
easy
and
I'm
having
a
hard
time
with
it
like.
B
Yeah
it
looks
like
they're
they're,
even
linking
to
a
conference
talk,
I
believe,
ooh
nice
talk
yeah.
It
looks
like
the
conference
talks
about
don't
save
simply
which
yeah
so
I
actually,
when
I
worked
at
my
previous
employer,
I
used
to
so
github-
has
a
full
docs
team.
We
actually
opened
source
docs
last
week,
cool
yeah,
so
that's
exciting
and
we're
actually
we're
gonna
have
the
team.
We
don't
talk
about
now,
but
we
held
the
team
on
next
week
to
talk
about
open
sourcing
docs,
which
is.
A
B
Little
intro
talking
to
gatsby
about
docs,
but
I
worked
with
documentation
engineers
in
the
past,
and
this
is
coming
up
in,
like
even
my
writing,
where
I
am.
A
B
B
A
B
Could
be
like
wait
hold
on
slow
down,
I
don't
know
what
git
is
and
yeah
then
you're
like,
oh
you,
don't
know,
get
us
how
you
don't
know
get.
So
that's
like
right
back
to
my
explanation
about
the
react.
Training
folks,
who
kind
of
avoid
all
the
other
stuff
to
just
talk
about
react
like
by
not
saying
simply
and
not
doing
all
that
stuff.
You
can
just
focus
on
the
teaching
the
thing
you
want
to
talk
about
and
if
the
things
are
quote
unquote
simple,
you
don't
have
to
say
they're
simple.
B
A
Myself,
no,
no!
I
I
think
that
that's
a
really
good
point
that
you
make
about
like
trying
to
limit
the
distractions
of
like
you're,
trying
to
teach
them
this
topic
just
focus
on
that
topic
and
like
anything
like
get
things
or
I
don't
know,
just
anything
that
you
don't
actually
need
to
do
that
one
objective,
just
don't
don't
do
it
like
teach
them
that
somewhere
else
and
then
you
can
link
them
to
it,
but
just
focus
like
limit
your
scope,
you
can
only
teach
them
so
many
things
at
once.
B
Yeah
yeah
and
I'm
curious,
though,
like
I'm
sorry
to
go,
understand
more
documentation,
because
I
feel
like
since
having
you
and
I
think,
listen
like
all
the
viewers
are
sort
of
enjoying
the
conversation
as
well
like
what
is
your?
What's
your
approach
to
getting
better
at
documentation
like?
Are
there
like?
If
I
know
if
I
want
to
learn,
javascript.
A
A
A
I
mean
the
like
cheap
answer:
is
you
just
have
to
keep
doing
it?
Yeah.
A
Like
I
something
that
I
something
that
I
try
to
do
is
I
have
a
like
til
today
I
learned
repo,
where
I
just
have
a
bunch
of
folders
and
it's
like
not
meant
for
other
people's
consumption.
Necessarily
it's
just
a
way
for
me
to
track
like
these
are
the
things
that
I'm
learning
about.
A
I
guess
kind
of
like
a
digital
garden,
where
everything's
in
various
levels
of
done,
but
that's
a
good
way
to
practice,
distilling
like
just
the
basic
information
that
you
need
to
know,
and
then
you
can
like
link
out
to
other
things
like
this
is
the
article
that
I
was
reading
when
I
had
this
thought
and
then
also
like
looking
at
other
people's
documentation,
like
I
really
like
looking
at
dev.2
or
to
I
don't
actually
know
how
they
say
it.
I.
B
Think
officially
they're
dev,
but
everybody.
A
A
Yeah
yeah,
but
there's
a
bunch
of
there's
a
bunch
of
different
ways
that
people
explain
things
on
here
and
some
some
of
the
articles
are
better
than
others,
but
I
think
that
it's
a
good
just
like
having
this
sort
of
bucket
of
things
to
choose
from
you
can
look
through
the
way
that
different
people's
different
people
have
explained
the
same
topics
and
see
like.
A
A
A
B
A
A
B
Yeah,
it
looks
like
I'm
not
sure
how
apt
it
is
for
this.
One
has
118
comments.
A
A
B
B
Yeah,
honestly,
like
just
going
through
issues
and
like
understanding
the
history
of
the
project,
is
a
good
way,
if
you
don't
know
where
to
start
and
jump
in,
seeing
if
you
can
understand
the
conversations
that
are
happening
right
now,
like
what
I'm
just
doing
right
now,
while
you're
here
and
keeping
me
honest,
you
can
see
that
there
are
there's
some
type
definitions
that
have
been
imported.
I
don't
write
typescript
or
I
just
sort
of
consume
it.
I
don't.
B
So
I
don't
actually
understand
all
the
ins
and
outs
of
it,
but
it
looks
like
there's
yeah
type
composer,
so
it
looks
like
they're,
adding
typescript
to
files,
which
is
pretty
cool,
which
I
had
a
joke
about
adding
typescript
to
my
project
during
hacktoberfest
and
if
it
would
happen
and
seems
like
it
seems
like
it
happens,.
A
A
B
Looking
to
make
this
migration
happen
so
yeah,
so
basically
shouting
it
out
and
saying
this
is
the
thing
that
we're
looking
for
is
a
great
way
to
get
contribution
like
eyeballs
on
things,
but
it
seems
like
yeah,
very
popular
issue
yeah.
If
we
gave
away
points
for
people
who
open
issues,
we
wouldn't
do
that
for
obvious
reasons
and
spam,
but
blade
would
have
a
lot
of
points
because
a
lot
of
people
have
jumped
on
there
and
uploaded
it
with
their
what
their
responses
yeah.
B
A
I
guess
we
can
talk
through.
We
can
talk
through
at
a
high
level
like
how,
if
you
want
to
get
started.
This
all
sounds
great.
How
would
you
do
that
like?
How
would
you
set
it
up
locally,
so
I
guess
the
first
thing
that
you
would
do
is
go
through
and
like
assign
yourself
to
the
issue,
or
we.
B
B
A
There's
this
whole
docs
thing
and
actually
like
it's
kind
of
confusing
like
our
site.
Now,
when
we,
when
we
merge
the
dot,
org
and
the
dot
com
site,
there's
now
like
a
separate
repo,
that's
actually
building
our
dot
com
site,
but
you
can
still
use
this
repo
to
to
like
run
it
locally
and
you'll,
see
the
docs
in
like
the
old
version
of
the
docs
site,
but
at
least
it'll.
Let
you
like
check
your
mark
down
and
stuff.
B
Yeah,
okay,
it
sounds
confusing,
but
it
sounds
like
there
was
a
migration
between
two
different
places
where
the
docks
were.
So
if
you
are
confused,
when
you
run
it,
I'm
sure
you
can
probably
ask
a
question.
Yeah.
A
Yeah
definitely
there's
also.
I
guess
this
is
a
good
chance
to
plug
there.
There's
like
an
ask
gatsby
js
twitter
that
you
can
at
them
and
then
for
now
you
can
use
the
hacktoberfest
hashtag
and
that
I
think
that
our
customer
success
team
looks
at
this
and
they
can
either
help
you
solve
the
issue
or
they
can
direct
your
question
to
the
right
person
internally
and
then.
B
Oh,
here's
the
the
note
about
typescript.
A
B
B
Tweet
and
check
that
out,
but
sean's
saying
the
ask:
gatsby
is
a
a
great
idea
which
it
is.
I
think
github
has
one
too
as
well.
We
call
it
github
help.
So
it's
easy.
B
Respond
that
way,
especially
especially
someone's,
like
brian
on
twitter,
this
thing
on
github's
not
working
or
you
moved
it
and
I'm
like.
A
B
Oh
yeah,
that's
a
a
good
mention
there
and
forgot
how
we
got
here.
Oh,
we
were
talking
about
the
docs
and
where
they
live.
A
B
A
All
of
our
documentation
is
written
in
markdown
and
then,
if
you
were
gonna
like
where
is
it
it's
yeah?
So
then
this
thing
you
could
see.
I
think
if
you
went
to
like
our
actual
docs
site,
so
like
gatsby.com,
docs
slash
whatever
that
title
was
like
adding
analytics
or
something
like
that
yeah.
A
I
think
you
might
even
be
able
to
just
type
it
into
the
url.
Just
like
add
it
afterwards.
B
Leverage,
the
the
beautiful
search
here.
A
So
when
you
clone
the
repo
you'll
have
to
do,
you'll
have
to
like
cd
change
directory
into
the
www
folder
and
that's
the
actual
like
directory,
where
the
the
site
is
or
like
the
old
version
of
the
site
is
and
then
you'll
have
to
start
you'll
do
like
npm
install
in
there
and
then
you'll.
What
is
the
start
command?
I
think
it's
just
like.
B
A
A
Yeah
and
so
then,
from
inside
of
that
directory,
that's
the
place
that
you
would
like
start
or
start
gatsby
develop
and
then
you'll
like
go
to
localhost
and
be
able
to
see
your
stuff.
So
at
least
for
adding
for
adding
new
documentation.
A
A
Yeah
and
it's
basically
right
now,
it's
it's
just
like
this
giant
list
of
all
of
the
all
the
docs
and
what
order
they
go
in
something
to
like
tease
a
future
change.
A
I
guess
something
that
I'm
hoping
to
work
on
is
sort
of
like
reorganizing
the
documentation
that
we
already
have,
because
there's
a
lot
of
it
and
like
as
the
community
has
found
new
features
that
they've
wanted
to
add
and
we've
kind
of
like
kept
building
this
thing
up
right
now,
it's
a
little
bit
unwieldy
and
hard
to
find
what
you're
looking
for,
especially
if
you're
new
and
don't
know
where
to
look
so,
hopefully,
hopefully,
that'll
that'll
get
easier
in
the
future
cool
all
tbd
yeah.
B
B
Okay,
so
I
just
re-
I
we
have
to
make
you
a
vip
to
allow
you
to
post
links
here
very
important
person
here,
so
I
failed
to
actually.
A
B
All
the
all
the
viewers
too,
as
well
welcome
thanks
for
chatting
with
us
and
learning
about
gatsby
and
contributing
actually
any
any
last
words
you
wanted
to
share
like
where
we
can
find
your
work.
Besides,
the
gatsby.com
docs.
A
B
Yeah
I
saw
a
tweet
of
someone
who
created
a
twitter
list
for
all
the
folks
who
who
are
in
who
are
developers
who
actually
tweet
code.
A
B
Yeah
excellent
well,
thanks
again
for
the
conversations
and
yeah
folks
reach.
A
B
Hit
the
follow
button,
if
you
want
to
hear
more
about
open
source
friday
and
contributions,
this
video
will
be
on
the
youtube
channel,
and
I
guess
a
few
days
give
me
the
weekend
and
also
let
us
know
if
there
are
projects
you
want
to
hear
from
also
a
big
fan
of
getting
projects
here
and
introductions
as
well.