►
Description
Speakers: Tim Pepper, Zach Corleisen, Aiwarya Sundar
A
A
This
is
a
repo
Kay
website
and
as
a
sig,
we
are
responsible
for
kubernetes
io,
managing
the
content
and
the
tool
stack
that
goes
into
the
website,
as
well
as
sort
of
gatekeeping
the
content,
and
if
you
ever
need
to
find
me
on
github,
that's
my
github
ID
zachary.
Sarah
everything
that
I'm
about
to
say
you
can
also
find
at
this
URL
kubernetes
do
slash
docs,
slash,
contribute
and
that
will
cover
everything
that
I
talk
about
here
and
a
whole
bunch
of
additional
stuff.
A
It's
helpful
to
know
so
anyone
can
contribute
to
kubernetes
documentation
and
I
do
mean
anyone.
You
don't
have
to
be
a
member
of
the
kubernetes
org
in
order
to
contribute
to
documentation
whether
that's
documenting
a
new
feature,
updating
information,
updating
code,
samples,
fixing,
typos,
broken
links,
things
like
that
anyone
can
contribute
to
documentation.
It
is
also
a
path
to
organization
membership.
So
if
you
want
to
become
a
member
of
the
kubernetes
org
contributing
to
docs
is
one
of
the
ways
that
you
can
become
a
member
of
kubernetes.
A
So
where
do
the
docs
come
from
and
when
I
say
anyone
can
contribute
to
Doc's?
What
I
really
should
accurately
say
is
everyone
will
contribute
to
Docs
because
feature
developers
write
the
documentation
for
their
features.
Sig
Docs
helps
those
the
future
documentation
that
feature
developers
write,
be
as
accurate
and
as
concise
as
possible.
A
So
if
you
need
help
with
Doc's,
if
you
have
any
questions
about
what
to
do
with
a
PR
where
Doc's
should
go,
this
is
where
you
can
find
help.
This
is
our
slack
channel
in
kubernetes
slack
cig
Doc's,
and
this
is
where
we're
the
most
active.
If
you
we
have
an
email
list
as
well,
if
the
link
is
there,
but
if
you
to
get
a
faster
response,
come
chat
with
us
in
slack
it
is
the
fastest
way
to
get
the
most
helpful
eyes
on
your
question.
A
So
a
little
bit
about
the
docs,
so
kubernetes
I/o
the
website.
We
migrated
the
static
site
generator
this
year
from
Jekyll
to
Hugo.
So
if
you
are
familiar
with
how
Hugo
works,
its
content
conventions
short
codes,
partials
things
like
that,
we
use
those
for
kubernetes
I/o
as
well.
So
that's
a
bit
of
portable
knowledge
that
works,
and
that
means
that
also
that
most
doc
source
files
can
be
found
at
content,
/en,
slash
Doc's,
as
that's
the
way
that
Hugo
works
with
languages.
A
Is
that
there's
no
default
Doc's
file,
except
what
you
specify
everything
is
automatically
internationalized
by
default.
It's
set
up
for
internationalization
by
default,
and
that
was
one
of
a
Hugo's
selling
points
to
us
this
year.
So
branching.
If
there's
one
thing
that
I
would
like
you
to
take
away
from
this
talk,
it's
one
slack
come
talk
to
us
on
slack
and
two.
A
A
If
you
are
working
on
Docs
for
the
current
release
in
this
case,
if
you
are
working
on
updates
to
Docs
for
1.13
base
your
PR
on
master,
if
you
are
working
on
Docs
for
an
upcoming
feature,
release
in
this
case,
1.14
base
your
PR
off
of
dev
1.14
and
those
are
really
the
two
binaries
to
know
about
where
to
branch
from.
If
you
were
branching
for
the
current
release
branch
on
off
of
master.
A
A
Docks
use,
prowl
soak
a
website,
the
the
repository
uses
prowl,
and
that
means
that
the
same
conventions,
the
same
requirements
for
PRS
to
merge
and
other
repositories,
are
equally
true
for
K
website.
That
means
that
it
needs
to
have
a
/lg
TM,
which
anyone
any
kubernetes
org
member
can
give.
So
anyone
can
also
you
don't.
A
Okay,
great
doc,
/
contribute
kubernetes,
do
/
doc.
/
contribute
there's
an
left,
nav
item
for
localization.
If
you
are
interested
in
localizing
kubernetes
documentation
for
a
language
other
than
english
we're
here
to
help
you
out.
We
currently
have
three
localizations
Chinese
Japanese
Korean.
In
addition
to
English
and
there's
room
for
more,
we
are
ready
to
scale.