►
From YouTube: How anyone can contribute to the MS Docs website!
Description
docs.microsoft.com is the home for Microsoft documentation. It is a valuable resource for IT pros to learn how various Microsoft services and products work. What may not be well-known is that the docs website is open source! Anyone can contribute, edit, change, add to the documentation available. The question is how to does someone make a change and what happens after they submit a change?
This discussion explores how ANYONE can make a change to the docs website and what Microsoft does after someone submits a change. The discussion is led by representatives from Microsoft who are responsible for the docs website. They pull back the covers and show what happens when a change is submitted as well as what what they do on their side to approve a change and make it show on the website.
Our presenters are Michael Bender, Sean Wheeler and Chase Wilson. Sean and Chase are content developers for Microsoft supporting the docs system. Michael Bender is a author evangelist for PluralSight and former Microsoft employee. These gentlemen have planned an interactive demo that will highlight how easy the process is for someone to participate.
Research Triangle PowerShell Users Group (RTPSUG) is the largest PowerShell group in the world! We meet twice a month to discuss all topics related to PowerShell and automation. Our topics cover beginner to advanced concepts and offer people a chance to learn new skills and ask questions. One of the foundations that we live by is to create a space to for all to attendees to feel welcome, have a chance to ask questions and be part of a community. For more information on our group, please visit any of following links:
WEB: https://rtpsug.com
MEETUP: https://www.meetup.com/Research-Triangle-PowerShell-Users-Group
LINKEDIN: https://www.linkedin.com/company/rtpsug/
TWITTER: https://twitter.com/rtpsug
GITHUB: https://github.com/rtpsug
A
A
B
B
We're
not
going
to
do
any
slides
we're
just
going
to
have
some
talking
heads,
we're
gonna
talk
about
some
stuff.
We're
gonna
show
you
how
to
do
some
stuff
and
like
phil
mike
both
said.
If
there's
any
questions,
we
should
have
plenty
of
time
for
questions
feel
free
to
throw
those
in
the
chat,
and
then
we
will
be
good
to
go
so
like
mike
said.
What
we're
going
to
be
talking
about
tonight
is
we're
going
to
be
talking
about
docs
on
microsoft.com
or
microsoft's
newest
iteration
of
documentation.
B
That
really
is
the
source
of
truth
for
everything
as
you're,
whether
you're
working
in
azure
powershell,
or
what
have
you
and
so
just
kind
of
a
brief
intro
to
who
I
am
again.
My
name
is
michael
bender.
I've
been
a
member
of
the
powershell
community
for
a
number
of
years,
I'm
an
author
evangelist
at
close
site.
I've
got
a
number
of
courses
on
powershell
azure
system
admin.
B
I
used
to
work
at
microsoft
for
a
smidge
at
a
time,
so
that's
kind
of
why
I'm
kind
of
also
up
on
the
doc
stuff
and
prior
to
that
I
was
a
college
school
teacher
for
a
number
of
years
teaching
in
the
same
state
as
mike
tuske,
who
I
think
you've
had
on
your
on
your
user
group
as
well.
So
I
wanted
to.
I
wanted
to
give
a
shout
out
to
sean
and
chase
and
just
have
them
do
some
quick
intros
and
then
we
will
dive
into.
B
C
C
When
I
started
in
the
content
group.
At
microsoft
there
were
six
people
working
on
powershell
and
for
a
long
time
after
I
took
over
it
was
just
me.
So
it's
been
a
long,
hard
row
to
hoe,
but
hopefully
you'll
appreciate
the
progress
we've
made
in
the
last
couple
of
years
and
a
little
bit
about
me.
I've
been
at
microsoft
for
almost
21
years.
C
C
D
But
he's
just
being
nice
right
now,
because
I'm
here,
my
name
is
chase.
I've
been
with
microsoft
for
coming
up
on
four
years
now
and
been
on
the
powershell
content
team
for
coming
up
on
a
year
in
december,
I
was
in
the
military
prior
to
microsoft
and
then
joined
us
to
a
consultant
out
of
military
service,
and
I
worked
in
powershell
pretty
much
from
then
until
I
joined
the
content
world.
That
was
about
two
and
a
half.
D
Years
later,
I
worked
on
a
lot
of
different
things
with
dsc
pester
and
some
of
the
bigger
projects
out
there
in
the
services
and
yeah.
I
was
very
fortunate
enough
to
get
on
the
team
with
sean
he's,
been
learning
a
lot
about
content
and
doing
my
best
to
help
out
the
community
and
being
more
involved
with
the
community
as
well,
which
has
been
great.
So
that's
what
I'm
here
for.
B
Awesome
great
to
have
you
guys
here,
so
what
I
would
you
know
what
I
wanted
to
kind
of
just
get
from
the
two
of
you
is
you
know
we
could
talk
about
docs
all
night,
and
you
know
I
kind
of
like
to
get
from
you.
I
don't
know
how
many
people
on
the
call
have
dealt
with
the
27,
odd
silos
of
documentation
that
have
existed
at
microsoft
over
the
years,
and
you
know
many
of
them
never
got
updated
in
any
way,
shape
or
form.
B
B
C
Well,
yeah,
so
technet
and
msdn
library
are
dead,
long
live,
msdn,
librarian
tech
net,
they've
been
totally
replaced
by
the
docs
platform,
and
the
biggest
difference
is
now
there's.
There's
one
place
to
go,
msdn
was
supposed
to
be
developer,
focused
technet
was
supposed
to
be
it
pro
focused
and
in
a
devops
world
that
we're
in
today
it's
all
one
thing
anymore
and
so
docs
is
that
one
thing
and
it's
from
a
content
perspective.
It's
a
fully
open
source
platform.
C
Most
of
it
is
in
public
repos,
where
you
can
comment
open
issues,
comment
on
the
documentation
and
you
can
even
contribute
to
the
documentation,
and
that
really
has
allowed
us
to
be
much
more
agile
and
address
the
needs
of
you,
guys
the
users
much
more
quickly
and
much
more
efficiently
and
really
deliver
the
content
you're
looking
for,
rather
than
trying
to
guess
it.
What
it
is
you
need.
C
D
C
And
show
us
how
that
yeah,
we'll
certainly
talk
about
that
and
that
varies
from
content
set
to
content
set
and
based
on
the
people
that
are
assigned
to
those
content
areas.
But
basically
a
content
owner,
like
myself,
is
responsible
for
managing
the
issues
that
come
in
and
responding
to
them
over
in
the
azure
space,
the
azure
documentation.
We
also
have
a
whole
team
of
support,
folks
that
sort
of
triage
those
issues
as
they
come
in
and
try
to
resolve
them
before
getting
the
writers
involved.
C
D
So
I
have
a
question
related
to
that
something.
I've
always
wondered
so,
and
this
is
no
disrespect
to
the
two
of
you.
But
how
much
do
you
actually
know
about
powershell
tech
as
opposed
to
just
being
someone
that
knows
the
english
language
and
how
to
produce
good
technical
documentation
like
what
is
the
the
role
of
a
content,
content,
dev.
C
C
So
I
don't.
I
don't
consider
myself
a
writer.
I
play
a
writer
at
work,
but
I
came
from
you
know
I
was.
I
was
a
pfe
for
many
years,
so
I
was
on
the
front
line
supporting
customers
and
helping
build
solutions
with
scripting.
I
taught
vb
scripting
classes
and
powershell
scripting
classes
to
my
premier,
customers,
so
yeah
you're.
Using
consider
myself,
I
mean
I'm
a,
I
would
say,
I'm
a
power
user,
but
I
work
with
experts.
I
consider
myself
an
expert
like
the
powershell
team.
D
Itself,
well,
the
reason
I
ask
is
because
there's
a
gentleman
from
the
community,
his
name
is
joe
salo
who's
working
on
powershell
and
making
commits,
and
while
I'm
a
friend
of
joel's
and
he's
presented
for
our
group,
there
are
many
topics
that
he
can
comments
on
that
I
have
no
idea
what
the
hell
he's
talking
about.
You
know
so
at
some
point
someone
has
to
look
at
that
and
go
like.
This
is
just
that
side
of
my
wheelhouse.
C
D
C
D
But
that's
also
a
good
lead-in
as
to
like
why
it's
an
open
source
product
right.
There
are
people
in
the
community
that
can
make
meaningful
commits.
Yes,
just
absolutely
help
you
guys
get
to
the
point
you
want
to
get
to.
So
it's
not
a
bottleneck
of
two
gentlemen
sitting
at
microsoft.
We
have
all
these
things
we
want
to
do.
We
just
can't
get
to
it.
C
A
A
If
you
figured
it
out-
or
you
can
say
this
doesn't
say
this
and
if
it's
possible,
then
you
guys
can
actually
you
know,
talk
to
the
team
and
get
it
done
or
it's
just
like
all
right.
Well,
here's
here's!
The
example
that
I
have,
and
this
is
how
I
solved
it:
okay.
Well,
then,
if
that's
a
viable
solution,
that's
been
effectively
vetted
and
go
through
that
process.
It
is
there
to
be
now
be
better
for
the
community
at
large.
B
D
Hey
sean
and
michael
chase,
just
interject.
This
is
rob
this
great
opportunity
to
talk
to
you
guys
tonight,
because
I
was
on
docs.microsoft
a
couple
days
ago
and
I
picked
up
on
one
little
trend
in
the
lower
left
hand
corner
how
some
areas
of
it
have
a
little
button
that
says
generate
pdf,
but
others
don't
yeah.
C
C
C
It's
on
their
list
of
things
of
many
things
that
they're
trying
to
work
on.
I
don't
know
where
it
is
the
priority,
but
yeah.
So
here
is
the.
If
you
can
see
my
screen,
this
is
the
the
doc's
homepage
for
powershell
and
just
let
me
walk
through
the
anatomy
here
of
of
a
typical
docs
page
up
here
we
have
the
breadcrumbs
and
below
that
some
documentation
sets
support
content
for
multiple
versions
of
a
product.
C
All
of
this
in
when
you're
looking
at
the
toc
here.
Everything
up
to
above
reference
is
what
we
are
calling
conceptual
content
and
if,
if
this
doc
set
was
conceptual
only
then
we
could
turn
on
pdf
generation,
but
this
section
below
here
the
reference.
This
is
the
commandlet
reference
and
the
way
that
this
content
is
generated,
works
a
little
differently
and
the
pdf
generation
does
not
support
this
at
this
time
and
and
that's
really
the
big
issue,
but
a
little
more
about
the
the
user
interface
here.
C
C
C
C
C
So
if
what
you're
trying
to
report
is,
if,
like
a
feature,
request
or
something's,
not
working
the
way,
you
expect
might
be
a
bug,
that's
more
product
feedback
than
something
you
found
that
works
one
way,
but
the
documentation
says
something
different
than
that's.
You
want
to
report
that
about
this
page,
not
about
the
product.
C
Recently
restructured
the
table
of
contents
added
some
more
content.
We
have
a
new
powershell
101.
This
was
mike
robbins
donated
his
book
to
us
and
allowed
us
to
republish
it
here,
and
so
this
is
it's
written
for
powershell,
five
one,
but
the
basics
apply
to
any
version
of
powershell,
and
so
this
is
a
good
place
to
start
learning
powershell.
C
If,
if
you're
still
learning
and
then
I
reached
out
to
kevin
marquette,
he
had
a
whole
series
on
his
blog
called
everything
you
want
to
know
about
x
and
some
great
articles,
and
it
was
all
information
that
would
be
as
I
was
reading
through.
It
would
be
great
to
have
in
our
docs,
but
it
kind
of
it's
a
deep
dive
kind
of
out
of
scope
for
the
type
the
documentation,
especially
the
reference
documentation,
where
we're
trying
to
be
a
little
more
succinct
and
have
simpler
examples
to
get
you
started.
C
C
So
if
you
click-
and
I
and
I've
collected
these
by
calendar
quarter
so
we're
currently
in
the
third
quarter
of
2020
and
here's
the
highlights
for
august,
we
have
two
new
articles
that
we
published
a
new
about
calculated
properties
and
a
new
article
about
doing
multi-threaded
getting
using
right
progress
with
inside
of
4-h
parallel
loops.
So
it's
sort
of
multi-threaded
progress,
updates,
kind
of
kind
of
interesting,
and
this
will
link
you
right
to
the
articles.
C
C
B
B
So
before
we
jump
in
we're
gonna,
what
we're
gonna
do
is
we're
gonna
show
you
we're
gonna
show
you
the
easy
way
to
go
about
requesting
a
change
for
something
and
then
we're
going
to
show
you
some
a
little
bit
more
more
complex
ways
to
do
that.
So
the
first
thing
what
I
wanted
to
do
is
I
just
wanted
to
also
you
know.
Just
kind
of
tag
on
to
what
sean
was
talking
about.
B
Is
that
one
of
the
things
that
I
found
that
that
is
often
missed
by
people
when
they're
trying
to
use
docs
is
what's
the
right
way
to
use
docs,
because
if
you
look
at
the
previous
things
we
have
like
msdn
and
technet,
there
was
really
no
rhyme
or
reason,
and
many
of
them
were
just
blogs
and
others
were
like
500
level,
deep
things.
It
was
really
hard
to
tell
when
you
went
through
a
search
engine.
B
What
you're
going
to
find
with
most
of
the
products
is
that
they're
going
to
have
an
overview.
That's
going
to
basically
tell
you
about
virtual
machines.
So
if
you're,
just
starting
out
with
virtual
machines,
you
kind
of
start
at
the
top,
and
you
make
your
way
down
the
quick
start,
what
those
are
gonna
end
up
being
and
let's
take
a
look
at
creating
the
vm
with
powershell
that
is
going
to
be
these.
These
things
are
like
five
minutes
long.
B
B
This
is
basically
going
to
be
a
step-by-step
15
steps
through
doing
a
large
type
scenario,
so
these
are
going
to
be
more
in
depth
than
we
had
with
the
different
quick
starts.
So
when
you're
looking
to
go
a
little
bit
deeper,
you
know
take
a
look
at
the
the
tutorials
samples
are
often
just
going
to
be
samples
of
different
types
of
code,
how
to
do
different
things,
whether
it
be
with
powershell
or
with
azure
cli
the
concepts.
B
B
So
for
those
of
you
that
are
looking
for
more
depth
than
just
the
creation
of
vms
and
some
of
the
general
stuff,
this
is
going
to
be
that
place
for
you
to
go
to
really
start
diving
into
the
product
and
to
find
find
out
how
how
to
work
with
it,
then
there's
going
to
be
an
often
depending
on
the
products
they're
going
to
have
how-to
guides
that
are
going
to
be
basically
like
nuts
and
bolts.
Here's
how
you
actually
work
with
a
specific
product.
B
B
Then,
of
course,
you're
going
to
have
different
references,
they're,
often
going
to
be
going
to
the
reference
architecture.
You
know
we've
got
powershell
here
again
going
to
the
powershell,
the
azure
powershell
documentation
for
virtual
machines,
so
the
the
references
are
going
to
be
more
of
kind
of
a
footnote
of
hey.
We
talked
about
azure
cli
in
here.
What
really
is
azure
cli?
B
So
that's
going
to
have
a
reference
down
there
to
the
things
that
aren't
specifically
about
what
we're
talking
about
and
then
there's
there's
different
resources
in
here
as
well,
so
you'll
find
that
the
table
contents
for
for
many
of
the
the
products
are
going
to
be
like
that.
The
powershell
area
is
a
little
bit
different.
I
think,
just
because
of
the
platform
that
it
is
that
they
have
it
laid
out
a
little
bit
differently.
I
actually
like
the
way
that
it's
laid
out
yeah.
C
C
B
Cool
so-
and
I'm
not
sure
if
you
showed
this
before-
but
you
know
if
you
go
into
just
the
powershell
documentation
at
docsetmicrosoft.com,
powershell
and
here's
here's
an
interesting
tip
that
I
learned
when
I
worked
at
microsoft-
is
that
if
you
remove
the
en
us
slash
and
just
put
that
url
in
that
url
is
going
to
reference
to
the
language
of
the
user.
That's
getting
it!
B
So
if
you
want
to
make
these
say,
you're
sharing
these
urls
with
somebody
for
a
presentation
or
what
have
you
this
is
going
to
make
that
more
inclusive
for
the
end
user.
So
it's
going
to
get
it
in
their
preferred
language,
just
kind
of
one
of
those
little
tips
that
I
learned
going
through.
So
what
we
wanted
to
do
is
we
wanted
to
take
a
look
at
because
we
found
that
there
were
some
issues
in
the
stop
dash
process,
documentation.
D
B
B
B
B
B
B
C
C
A
And
be
assured
that
chase
and
sean
will,
you
know,
keep
you
on
your
toes
if
you
happen
to
submit
something
wrong,
but
that's
still
the
good
point
and
I
think
the
value
here
is
that
hey
look.
I
can
easily
change
this.
I
don't
need
some
extra.
You
know
development
tools
in
order
to
edit
anything.
I
can
just
do
this
all
from
the
web
page
right
absolutely.
C
B
B
And
we
were
working
on
seven
and
you
can
just
put
an
x
in
here.
We'll
also
show
you
a
way.
I
think
we'll
show
you
how
you
can
actually
do
this
afterwards.
Key
thing
that
I
learned
from
sean
was:
when
you
put
an
x
in
here,
you
actually
have
to
remove
the
space.
So
if
you
notice
that
I
put
an
x
in
there,
but
then
I'd
remove
the
the
space
that
was
in
there
or
an
easy
way
I
figured
out
is
if
you
double
click
in
there.
B
B
C
A
C
B
A
D
A
A
D
A
A
B
Just
a
couple
couple
things:
while
we're
we're
waiting
for
sean,
if
you
remember
that
list
that
I
was
painfully
trying
to
go
through
and
check
the
things
off,
you
could
actually
do
it
on
this.
The
pr
summary
page
here
so
you
could
you
know
if
I
need
to
save
for
is
a
different
version.
I
can
do
that.
B
I
don't
want
to
change
too
much
because
I
don't
want
to
break
anything,
but
you
can
make
that
that
change
as
well
yeah,
just
some
common
things
is
you're
going
to
have
the
your
commits
listed
here.
So
we
see
that
we
have
the
the
commit
that
we
had
put
in
there
and
you
could,
you
know,
go
in
and
take
a
look
at
that
again,
if
you
needed
to
take
a
look
at
that
notice,
it
moved
over
to
the
file,
changes,
tab
and
so
notice
up
here.
B
B
You
know
clone
you
know,
forking
the
repo
and
then
you
know
cloning
it
down
and
then
working
through
that
process.
So
you
see
I'm
looking
to
merge
a
commit
into
microsoft.staging
from
the
michael
bender
dot
or
colon
patch
dash
one
so
patch
dash.
One
is
when
you
go
through
the
process
that
we're
going
through
now
of
doing
it
through
github,
I'm
not
doing
it
say
locally
in
say,
like
vs
code
or
something
like
we're
gonna,
do
it
it's
going
to
do
it
off
with
your
account
and
it's
gonna.
B
C
C
So
now
I
come
in
here
and
I
look
at
this
and
I
go
to
the
files
changed
and
it
will
show
me
what
was
changed
side
by
side,
and
I
can
I
can
see
here.
If
there's
anything,
you
know
make
sure
that
I
agree
with
the
changes
that
are
being
made
and
so
there's
some
things
here
that
I
would
want
to
change
that
don't
match
our
style
guide.
C
Classes
and
object
types
things
like
that
properties
and
other
things
are
bolded,
so
in
markdown,
that's
the
the
double
asterisk,
the
the
backtick
is
a
code
fence,
and
so
I'm
going
to
start
a
review,
and
that
adds
a
comment
and
same
thing
here
now.
This
is
this
one's
bold
and
so
the
formatting
was
inconsistent
within
the
article
that
wasn't
anything
that
michael
did.
C
C
D
C
B
C
B
C
C
But
at
this
point
I
will
I
will
turn
this
over
to
michael
so
but
before
I
turn
it
over.
Let's
talk
about
the
contributor's
guide
so
out
here
in
the
community
section,
there's
a
contributor's
guide,
and
this
gives
you
everything
you
need
to
know
about
how
to
get
started.
What
tools
we
use,
how
to
get
set
up,
talks
about
filing
issues,
submitting
changes
and
our
guidelines
for
each
of
those
and
then
there's
a
style
guide
here
that
talks
about
our
formatting
requirements
and
terminology
common
terminology
like
it.
C
When
you
talk
about
visual
studio
code,
you
need
to
spell
it
out
the
first
time
and
then
it's
abbreviated,
vs
space
code
and
not
as
one
word
vs
code,
things
like
that
use
of
blank
lines
and
spaces
and
tabs
how
we
do
our
headings,
markdown,
headings
lists
and
so
on.
So
if
you're
not
familiar
with
markdown,
this
will
help
you
get
started,
and
this
covers
our
style
requirements.
C
This
one
about
editing,
command
reference,
there's
specific
requirements
for
formatting
in
the
commandlet
reference,
so
that
it
works
with
our
tools
that
process
and
publish
the
documents
the
markdown
source
you
see
out
here
serves
two
purposes:
it
creates
it's
the
source
code
for
the
web
pages
that
get
published
and
it's
the
source
code
for
the
in
console,
help
displayed
by
get
help,
and
so
the
tools
we
use
to
transform
the
markdown
to
for
get
help
require
a
certain
format
structure
to
command,
let
reference.
So
these
are
all
the
rules
for
how
that
works.
C
A
C
And
then
some
other
things
here
under
additional
resources,
this
editorial
checklist.
This
is
sort
of
a
summary
of
everything,
that's
in
the
style
guide,
but
this
is
a
good
bullet
list
summary
that
you
can
use
to
go
through
your
the
documents
that
you've
worked
on
and
make
sure
you've
covered.
All
of
the
things
that
we
do.
C
C
And
then
these
other
two
articles
here
how
we
manage
issues
this
this
kind
of
gets
into
our
triage
process
and
the
labeling
we
use
and
so
on,
and
how
we
manage
pull
requests.
We're
trying
to
give
you
know,
make
this
transparent
to
everyone,
so
you
know
there's
no
hidden
agendas
here.
This
is
this
is
how
we
try
to
operate,
and
this
is
how
we
want
you
to
engage
with
us.
C
C
Go
back
to
the
top
files
yeah,
so
there's
two
buttons
there
there's
commit
suggestion
and
when,
if
you
did
commit
suggestion
that
adds
a
commit
which
triggers
the
build
to
start
over
and
if
there's
multiple
suggestions
to
be
committed,
you
can
commit
them
as
a
batch,
but
that's
the
other
button
and
that
requires
to
be
in
the
files
changed
view.
Yes,.
B
C
C
C
B
B
I
have
cloned
that
down
to
my
local
system,
so
I
should
be
ready
to
go
we'll
see
that
in
a
in
a
second
here,
because
we
are
dealing
with
with
git
here-
and
I
am
an
id
pro,
so
those
two
things
put
together
mean
that
we
might
may
or
may
not
get
this
right
so
first
area
that
I've
gone
into.
If
you
see
in
the
reference
area
once
these
are
cloned
on
see,
we
have
seven
one,
seven,
six
and
the
five
one.
B
B
B
A
C
C
C
C
B
C
C
A
7.1,
so
if
somebody's
more
familiar
with
you
know
this
process
than
living
in
kit,
it
is
a
very
easy
process
for
them
to
just
jump
in
here
and
move
them
things
around
and
even
yeah
copy
code
around
you
know,
use
the
format.
So
I
think
it
is
worthwhile
to
know
that
hey
this
is
available
to
you.
If
you
wanted.
A
A
C
So
we
rarely
get.
You
know
big,
weighty
contributions,
but
we
are
open
to
to
accepting
those
and
depending
what
it
is
that
you
want
to
do
we
you
know
we
may
either
push
back
or
it
may
be
better
to
start
with
an
issue
to
discuss
the
change
you
want
to
make
before
spending
a
lot
of
time,
making
the
change
cool
all
right,
yep
now
yep,
you
need
to
add
your
changes.
C
D
C
There's
the
open,
publishing
build
and
then
there's
the
partial
doc
ci
and
the
powershell
doc
ci
is
what
actually
builds
the
cab
files
for
updatable
help.
It's
doing
you
know
the
the
get
help
portion
of
the
build.
The
open,
publishing
build.
Does
the
website
portion
of
the
build,
but
the
other
thing
that
happens
when
you
make
a
contribution,
you
need
to
sign
the
contributor
license
agreement,
so
you'll
notice
that
this
is
still
yellow.
It
hasn't
this.
This
check
hasn't
passed
it's
pending
and
there
is
a
comment
here
from
the
microsoft
cla
bot.
C
C
C
D
A
So
also,
a
lot
of
this
is
focused
directly.
You
know
we're
talking
about
powershell
the
powershell
document.
The
same
overall
process
is
still
applicable,
for
you
know
if
you
wanted
to
update
the
azure
help
or
azure
docs
or
other
things
now
granted
some
of
their
their
pipeline
may
be
slightly
different,
but
the
overall
arching
you
know
process
is
close
to
this.
C
It's
very
much
the
same.
They
might
have
different
style
guidance
based
on
the
the
needs
of
their
content
set,
but
it
it's
the
same.
The
other
thing
that's
a
little
bit
different
in
the
azure
space
is
when
you
make
a
contribution,
you're,
making
a
contribution
to
a
public
repository,
but
there's
the
source
of
truth
is
a
private
repository
and
the
changes
are
synced
between
the
public
and
the
private.
B
C
C
You
provide
a
url
to
link
to
the
the
source
in
github
or
the
docs
page.
That
helps
us
know
which
dock
you're
talking
about,
and
then
we've
got
check
boxes
here.
For
you
know
what
portion
of
the
docs
does
it
relate
to?
Is
the
problem
platform
specific
like
it
only
applies
to
windows
or
linux
or
whatever,
and
then
here's
a
detailed
description.
C
C
Well,
this
is
an
example
of
one.
This
is
one
that
was
entered
using
the
feedback
control
on
the
bottom
of
the
web.
Page
so
remember
when
I
showed
you
that,
and
it
links
to
the
version
specific
document
that
you
were
viewing
at
the
time
you
clicked
the
feedback
button,
and
so
all
of
this
information
here
is
created
automatically
when
you
click
that
feedback
button.
C
Well,
it
is,
but
you
can
see,
there's
people
that
this
is
an
example
of
a
community
contributor,
that's
very
prolific,
and
he
gives
very
detailed,
in-depth
information.
He
knows
more
about
powershell
than
chase
or
I
and
we
often
have
to
work
with
the
devs
and
the
pm's
to
review
what
it
is
he's
saying
and
how
we
respond
to
this
stuff.
C
C
C
D
C
C
C
A
C
Yes-
and
the
important
part
here
too,
is
that
the
staging
branch
is
our
branch.
Where
we
do
all
of
our
work,
I
mean
you
should
you
should
create
a
and
we'll
get
to
the
git
hub
workflow
here
in
a
minute,
but
you
should
create
a
working
branch
and
then
submit
a
pull
request
to
merge
your
working
branch
into
staging
and
then
once
a
day
monday.
Through
friday,
the
staging
branch
is
merged
into
the
live
branch
and
we
build
the
website
from
the
live
branch.
C
C
So,
let's,
let's
dig
in
a
little
deeper
to
the
github
workflow,
so
really
there's
three
copies
of
the
repo
at
work.
Here,
the
the
microsoft
docs
slash,
powershell,
dot,
dash
docs
repository,
that's,
that
is
the
the
master,
the
the
source
of
truth
for
all
of
the
content
and
as
a
community
contributor,
you
don't
have
rights
to
make
changes
directly
there.
So
what
you
have
to
do
is
you
have
to
make
a
copy
of
it
and
that's
called
in
github.
C
C
C
C
The
blue
steps
are
the
things
that
you
do
on
a
regular
basis
when
you're
making
contributions.
So
the
first
thing
you
need
to
do
is
you
need
to
pull
the
latest
version
from
upstream
since
upstream
points
to
microsoft,
docs,
what
you're
doing
is
you're
you're
copying
all
the
changes
that
have
happened
in
the
staging
branch
down
to
the
staging
branch
in
your
local
machine,
and
then
you
want
to
push
all
of
those
changes
from
your
local
machine
up
into
your
fork.
When
you
do
that,
the
three
repositories
are
all
in
sync.
Now.
C
So
at
that
point
we
can
go
to
this
next
step,
where
you
check
out
your
working
branch.
So
you
do
a
git
check
out
dash
b
and
you
you
can
create
a
branch
and
you
can
name
it
anything
you
want-
and
this
is
what
this
does
is.
It
creates
a
safe
space
for
you
to
make
changes
you're,
not
making
them
directly
in
the
staging
branch.
You're
doing
it
in
a
working
branch.
C
A
A
C
B
D
B
D
So
also
one
thing
I
didn't
hear
mentioned
and
I'm
sorry
I
had
to
step
away
before
I
heard
that
when
you
make
the
commit
it's
sort
of
live,
but
it
doesn't
show
up
on
the
web
for
about
a
day.
I
understand
that
what
about
the
process
to
make
it
back
to
the
code
that
would
get
run
when
you
do
an
update
help?
How
long
does
it
take
for
that.
C
C
Because,
right
now
we
don't
have
a
a
way,
a
reliable
way
to
bump
the
version.
So
the
way
update
help
works
is
it
looks
at
the
version
of
the
help
that's
installed
on
your
machine
and
then
it
goes
and
looks
at
the
version
of
help
that's
available
for
download
and
if
the
version
is
the
same,
it
won't
download
it.
Unless
you
do
dash
force
and
right.
C
C
D
C
C
C
A
I
want
to
certainly
open
it
up
and
if
anybody
has
any
more
questions,
but
I
think
that
was
pretty
informative
and
I
like
to
look,
I
really
enjoyed
seeing
behind
the
curtain
and
seeing
what
it
takes
to
get
content
updated
and
just
even
what
docs
look
like
overall.
So
I
think
it's
been
a
really
good
session.
C
A
C
D
I
feel
like
a
lot
of
this
help.
Information
has
been
hiding
in
plain
sight,
because
I've
gone
to
docs.microsoft
many
times
and
used
help,
but
I
don't
know
that
I
actually
did
the
content
picker
the
drop
down
list,
and
I
don't
know
that
I
realized
that
there
was
a
lot
of
like
conceptual
stuff
in
there
as
well
and
and
and
I'm
not
saying
that
it's
not
there,
it's
just
a
habit
that
I
go.
I
find
my
help
and
I
move
on
not
realizing.
There's
a
lot
of
ancillary
information.
That's
useful.
There.
C
D
Like
the
needs
in
the
middle
of
those
square,
those
those
buttons
on
the
bottom,
I
I
take
a
little.
I
take
a
little.
I
have
a
little
issue
with
the
buttons,
because
the
button
says
lead
feedback
leave
feedback,
so
feedback
could
be
hey.
I
think
this
is
great,
but
what
it
actually
does
is
open
an
issue.
C
Let
me
share
my
screen
so
with
these
buttons
here
it
used
to
be
when
you
clicked
on
this.
You
would
see
all
of
the
open
issues
that
had
been
submitted
through
the
feedback
control
but,
like
I
said
there
was
inappropriate
content
being
put
in
those
in
that
feedback,
and
it
would
sit
there
for
hours
or
days
before
somebody
could
triage
it
and
it
it
was
just.
It
was
bad.
They
were,
and
there
was
legal
issues
and
things.
C
D
A
Yeah-
and
I
think
one
of
the
other
cool
things
is
actually
he
was
down
there
at
the
bottom.
Is
I
never
realized
it,
or
at
least
I
saw
somebody
do
it,
but
that
it
has
a
theme
at
the
bottom.
You
can
change
the
theme,
so
I
like
mine,
black
on
a
white
and
if
you
go
to
the,
if
there's
a
high
contrast
in
it,
so
you
can
choose
different
themes
and,
oh,
it's
so
much
better
click
dark.
B
To
that,
if
you're
presenting
as
a
presenter
dark
mode
is
the
absolute
worst
presentation
theme
that
you
can
use
that
when
you
put
this
onto
a
projector
and
oftentimes
even
through
zoom
meetings,
it's
very
very
difficult
to
read.
So
you
might
like
using
personally
that,
but
I
would
highly
dissuade
you
from
if
you're
going
out
and
presenting
somewhere
of
using
any
form
of
dark
mode,
because
as
much
as
it's
inclusive
and
it's
very
good
for
people
when
they're
watching
it
for
presentations
it.
C
But
yeah,
this
is
the
article
I
was
talking
about
and
this
this
walks
you
through.
This
is
the
the
the
flow
chart
that
says
how
we
use
platyps
and
and
the
steps.
So
the
article
takes
you
through
the
steps
you
see
in
the
flowchart
here,
so
you
could.
You
could
create
help
files
for
your
own
modules,
compile
them
into
mammal
and
ship
them
with
your
module
or
host
them
on
a
website.
So
you
could
have
updateable
help.
D
So
this
feels
like
a
natural
break
here,
since
we
haven't
had
too
many
other
questions.
Let
me
let
me
click
stop
on
the
record
here.
I'll
just
end
by
saying
thank
you
to
microsoft
for
spending
time
with
us
this
evening,
thanks
for
michael
bender
for
coming
along
and
helping
us
get
through.
This
content
really
appreciate
this
guys.
This
turned
out
to
be
another
fantastic
meeting
and
really
appreciate
the
efforts
by
you
guys
so
with
that,
we're
going
to
say
goodnight
to
all.