►
From YouTube: Contributing To the Kubernetes Website: A Guide For Everyone - Divya & Rey, Tim , Natali, Arsh
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe in Amsterdam, The Netherlands from April 17-21, 2023. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Contributing To the Kubernetes Website: A Guide For Everyone - Divya Mohan & Rey Lejano, SUSE; Tim Bannister, The Scale Factory; Natali Vlatko, Wayfair; Arsh Sharma, Okteto
Are you curious about how a large project like Kubernetes maintains its documentation? Whether it be guides, reference documentation, or the official blog, SIG Docs is responsible for maintaining all the content you see on the Kubernetes website. Yes, even the localized versions! This session gives you a behind-the-scenes glimpse of how we do it with a quick tour through the tech stack, the people powering it, and some of the things we’ve worked on in the past. We will then dive deep into some of the ongoing efforts of the SIG as well as some targeted initiatives with a particular focus on how you (yes, YOU!) can get involved. This talk is for total newcomers, experienced Kubernetes contributors who want to document their new features, web developers, localization team members, people who would like to help a localization team, and anyone else interested in improving the main Kubernetes website.
A
B
B
A
A
A
Like
to
possibly
look
at
also
approachable
and
enable
and
interesting
to
folks
who
are
from
different
areas
of
the
world,
understanding
the
local
script
and
then
what
the
actual
language
is.
You
know
your
breakfast.
There
is
something
that
is
you
that
we've
recently
introduced,
but
having
all
of
our
docs
you
know,
array
of
different
languages
is
something
that
we
find
really
important.
B
A
Only
for
the
proliferation
of
the
kids
across
the
world,
but
also
to
make
sure
that
we're
welcoming
in
welcoming
in
new
contributors
or
from
all
different
places
all
around
the
globe.
Oh
we
like
to
believe
it's
a
part
of
that
too,
in
a
lot
of
different
areas
of
the
world
too
yeah
representing
this
world
through
our
documentation
as
well
with
that,
though,
a
lot
of
work
wants
to
be
done
when
it
comes
to
localizing
jobs,
a
village.
Basically,
what
we
want
to
do
is
make
sure
that
folks
who
are
creating
localized.
B
A
Specifically,
localizing
requires
a
lot
of
Community,
Health
and
support,
and
so
what
we
try
and
do
is
create
those
channels
for
localization
or
the
cdos
main
Channel
and
get
folks
to
speak
about
their
ideas
about
wanting
to
either
spin
up
in
your
localization
or
contribute
to
a
current
one.
This
is
actually
something
really,
interestingly,
in
the
works
right
now
for
a
nap
localization
area,
where
we've
got
some
folks
trying
to
get
some
Community
Support
so
that
they
can
get
a
few
more
contributors
ready
to
start
working
on
something
like
this.
B
A
You
usually
require
is
that
two
to
three
approvals
of
a
breaking
through
a
localization
to
go,
live,
don't
communicants.
Do
you
say
too
I
like
to
add
pictures
and
there's
not
a
lot
of
bus
Factor,
but
what
we
mean
by
this
is
that,
just
like
any
other
kind
of
work
that
you're
doing,
if
you
are
a
single
source
of
approving
anything
that
goes
live
eventually,
that's
not
going
to
be
a
recipe
for
failure.
A
Sure
there's
a
lot
of
folks
who
can
to
improve
the
work
going
on,
and
that
also
has
really
greatly
mentioned
in
the
previous
talk
by
Country
Max
by
number
one.
That
folks
are
focusing
on
the
amount
of
time
that
they
contribute
and
they
can
dedicate
to
the
community
and
they'll,
be
you're
thinking
about
Technologies
or
what
they
can
contribute
to
YouTube.
A
So
we
like
two
or
three
approvers
to
being
a
localization,
so
that
we're
not
pushing
all
of
the
work
on
one
SQL
scores
in
person
and
then
finally,
we've
got
some
project
leads
and
interestingly,
Evan
McCarthy
is
a
sub
particularly
to
liberalization.
Who
I
have
you
in
the
back
and
previously
Brad
at
America's
localizationally
of
the
folks
who
want
to
make
sure
that
there's
consistency.
B
A
A
Localization
Channel
there
and
then
in
terms
of
how
communities
actually
organize
their
work
around
their
localized
stocks,
the
Coq
you
can
see
you've
got
kubernetes
Dash,
docs
Dash
and
the
specific
language
code
that
that
is
required.
I
went
there
in
the
slides.
The
language
are
in
bed
about
folks
will
be
able
to
have
access
to
it's
also
about
our
general
public
organization
guidelines.
A
Sure
that
folks
understand
that
we
have
a
minimum
required
when
it
comes
to
studying
dogs,
the
tldr.
We
want
you
to
find
Community
find
some
folks
who
want
to
work
on
this
together.
We
want
you
to
join
the
GitHub
organization
so
that
you
can
be
a
profile
as
team
people
mentioned
previously
and
I
do
have
that
yeah,
and
then
we
want
you
to
get
started
with
your
localization
team,
with
a
minimum
minimum
for
a
localization
to
go
like,
as
I
mentioned
before,
some
localizations
are
still
in
the
works.
A
I
mean
they're
still
working
on
the
minimum
content
that
they
need
to
look
like
before
we
can
publish
to
the
website
and
that
can
really
take
any
kind
of
amount
of
time.
Interestingly,
localization
that
just
launched
up
to
about
a
year
to
get
started
with
all
of
that
work.
But
it
was
an
amazing
Community
effort
and
it's
something
that
hopefully
over
time
gets
a
lot
more
contributors
across
a
lot
more
difficult,
localization
as
well,
and
then.
A
Finally,
the
one
last
thing
that
we
really
think
is
really
important
to
a
lot
of
learning
is
the
community
code
of
conduct.
This
is
something
that
is
should
be
translated
into
all
their
localized
languages.
We
have
a
specific
group
that
I've
also
linked
here
that
contains
all
the
localized
codes
of
conduct
too,
which
is
super
important
all
of
the
localizations
tab
and
with
that
being
said,
I'm
going
to
hand
it
over
to
my
presenter.
Thank.
B
You
Natalie
so
I'm
here
to
talk
about
the
website
so
project
it
is
a
subproject
I,
understood,
box
and
and
I
just
have
a
question.
What
do
you
do
when
you
try
something
new
I
read
the
topics
and
if
the
dogs
aren't-
and
you
aren't
good
I,
go
to
your
YouTube
video
or
a
blog
post
everything,
but
so
for
kubernetes.
If
you
want
folks,
your
organization
is
to
adopt
your
project,
we.
A
B
Sync
docs,
along
with
the
whole
community,
maintained
the
documentation
for
the
current
urgent
and
for
previous
version,
there's
only
one
Upstream
source
of
kubernetes
documentation,
something
that
didn't
get
said
in
live
yesterday
was
that
the
code
is
not
self-documented
or
it's
a
code.
Self
documenting
does
not
work.
It
does
not
work
for
everyone,
especially
to
live
in
large
sales,
Source
building
a
contract,
so
we
need
to
have
a
good
documentation
and
we
don't
rely
just
odds
and
thoughts.
We
rely
on
everyone
in
the
community
and
other
states
as
well.
B
B
Is
a
dark
section
though,
and
it
relates
to
them
so
the
release,
so
the
release,
docs
team
and
you
kept
owning
or
an
African
mistakes
that
have
any
new
when
you
graduating
enhancements,
go
into
each
release
but
they're
really
stocks
in
currents
and
make
sure
that
there's
proper
documentation.
Because
if
there's
a
new
feature
in
kubernetes,
we
need
to
tell
users
how
to
use
that.