►
Description
This PnP community demo is taken from the bi-weekly SharePoint Developer Community - General Development Special Interest Group (SIG) call recorded on February 20, 2020.
In this 11-minute video, Andrew Connell gives viewers a guided tour of the newly reorganized SharePoint developer documentation site. Content has been created or updated and is aligned to a predictable navigation structure for each topic - Overview, Getting started, Web part properties, Concepts & scenarios, Tutorials. Older reference content resides in the Scenario guidance and Archive areas of the site.
Demo Presenter: Andrew Connell (Voitanos) | @andrewconnell
Supporting materials:
• SharePoint Development documents | https://aka.ms/spdev-docs
All SharePoint PnP Developer Community demos: https://www.youtube.com/playlist?list=PLR9nK3mnD-OWSbg0o9a7mx_E7s2u7h_o2
Learn more about the SharePoint developer community at: http://aka.ms/sppnp.
A
It's
going
to
take
me
to
the
SharePoint
development
dogs.
Now
the
only
change
that
we
made
was
related
to
the
table
of
contents
on
the
left.
I'm
gonna
walk
through
some
of
the
changes,
but
let
me
come
to
explain
a
couple
things
upfront,
first
of
all,
while
I'm
presenting
this
in
a
while,
if
you
go
back
and
you
look
at
the
commit
history
and
the
PRS
and
everything
yes
I'm,
the
one
that
did
this-
but
this
is
not
me
doing
this.
This
is
similar
to
that
issue.
List
updates
that
we
made
recently
as
well.
A
I
was
just
the
implementer.
This
was
done
in
close
coordination
and
with
the
approval
of
Microsoft
I
kind
of
gave
my
two
ideas:
I
got
input
from
Microsoft
invest,
so
we
worked
a
lot
on
this.
This
was
carefully
planned
out.
It
was
not
just
something
just
happened
out
of
the
blue.
Well,
I!
Guess!
If
you
just
went
to
the
navigation
one
day
and
saw
it
changed,
it
was
either
blue
for
you,
one
of
the
other
things
that
we
looked
at
is
well
with
the
docs.
A
We,
the
the
SharePoint
development
documentation,
has
got
a
lot
of
old
content
in
it.
The
docs
are
absolutely
huge,
there's
a
ton
of
content
here
and
it's
evolved
over
time,
but
there
are
parts
of
the
content
that
are
I,
don't
want
to
say,
they're
outdated,
but
they
could
use
some
refreshing
and
frankly,
it's
kind
of
comes
down
to
a
little
bit
on
availability
of
time.
A
How
often
the
content
is
accessed,
how,
when
the
questions
come
up
about
the
content
and
priorities
and
schedules
and
resource
allocation
and
blah
blah
blah
all
that
stuff
that
you
always
hear
these
things
kind
of
come
up
about
this.
So
yes,
we
know
that
some
stuff
is
older
and
we've
done
something
to
make
it
a
little
obvious.
The
best
the
case
now.
Another
thing
I
want
to
say
before
we
get
started
with
this
is
let's
review
what
the
current,
like
guidance,
is
from
Microsoft,
whether
you're
in
SharePoint,
Online,
SharePoint,
on-prem,
being
SharePoint
20.
A
19
2016,
the
guidance
is
that
you
should
be
extending
SharePoint
customizing
SharePoint
using
the
SharePoint
framework,
and
you
should
be
using
the
modern
experience
when
it's
available.
I
know
that
not
available
in
2016,
but
you
should
be
using
the
SharePoint
framework
when
that
is
not
available
to
you
or
when
that
does
not
meet
your
needs.
We
have
other
development
models
like
prior
to
the
SharePoint
framework.
We
had
the
add-in
model
prior
to
that
we
had
features
and
solutions
and
farm
and
sandbox
based
solutions.
A
None
of
this
stuff
has
been
removed,
them
has
been
D
prioritized,
but
the
order
of
what
you
should
be
using
to
go
through
to
customize
your
SharePoint
environment,
depending
on
which
environment
you're,
using
depending
on
what
you're
trying
to
do
goes
SharePoint
framework,
then
add-ins,
then
legacy
style
customizations.
The
navigation
in
the
table
of
contents
is
designed
around
that,
and
one
of
the
couple
of
things
that
we've
done
is
to
try
and
make
things
easier
to
find
and
the
surface
them
based
on
what
people
are.
Looking
for.
A
We
want
to
make
that
very
easy
for
you
to
find,
but
we
also
wanted
to
make
it
easy
for
people
to
find
stuff
who
were
brand-new
to
the
SharePoint
platform
and
what
am
I
supposed
to
do
so
with
that
with
that
change,
there's
one
gigantic
change
that
I
made
that
at
least
personally.
For
me,
it
drove
me
nuts,
and
that
was
in
the
previous
navigation.
A
We
wanted
to
put
that
stuff
inside
of
one
section
inside
of
capabilities
and
features,
so
it
wasn't
buried
away
somewhere
else,
oh
yeah,
and
if
we
get
too
far
with
this,
if
something
doesn't
make
sense
to
you,
I
definitely
want
feedback.
Send
us
feedback.
Send
us
a
message
here
in
this.
In
this
chat
here,
so
we
can
actually
take
a
look
at
it,
but
mostly
please
go
through
and
put
it
in
the
SharePoint
issue
list
the
SharePoint
dev
Docs
issues
list,
so
we
can
follow
it.
A
One
of
the
other
things
that
you
will
see
too
is
there's
a
lot
of
places.
Actually,
this
is
a
bad
example,
because
I
just
found
a
problem,
there's
a
lot
of
places
where,
when
you
would
open
up
one
of
these
navigation
elements,
you
would
see
the
exact
same
name
as
the
one
you
just
opened
listed
right
here
and
it's
a
little
confusing
it's
like
well.
If
I
went
here,
why
didn't
just
go
here?
A
This
takes
you
to
the
over
the
page
that
you
used
to
go
to,
but
it
doesn't
give
you
like
that,
extant,
that
extra
little
nesting
there
that
might
have
just
bothered
me
it
might
have
bothered
a
few
other
people,
but
if
it
just
bothered
me
I
mean
I
just
want
to
show
you
hey.
We
made
this
change
and
you
can
rest
assured
that
I
now
sleep
better
and
I'm
get
as
frustrated
looking
at
the
docs.
That's
a
joke!
Other
things
we
did
here
so
we're
on
SharePoint
framework.
A
We
did
a
lot
of
reorganization
here,
so
we
got
an
overview
of
what
the
SharePoint
framework
is.
You've
got
a
getting
started
section.
How
can
I
dive
right
into
this
webparts
you're,
going
to
notice
some
things
change
with
webparts,
instead
of
it
just
diving
in
and
start
showing
you
a
tutorial
which
is
now
then
moved
over
here.
Here's
a
tutorial
of
doing
all
these
different
things
or
getting
started.
This
is
really
a
tutorial
like
going
through
one
two,
three,
four
steps.
In
the
past.
A
We
had
those
four
steps
mixed
in
with
a
bunch
of
other
stuff,
and
so
you
couldn't
really
tell
what
was
step
1
step
2.
Now,
we've
kind
of
broken
these
things
up.
You'll
also
see
things
like:
we've
broken
out,
working
with
web
part
properties
and
the
property
pane.
We've
broken
those
things
up
how
to
go
through
and
extend
the
property
pane.
That's
its
own
section.
A
We've
got
things
here
about
concepts
and
scenarios,
so
things
that
are
general
about
webparts,
but
they
aren't
like
you're,
not
gonna,
have
full
sections
dedicated
to
them
like
how
do
I
hide
it
from
the
toolbox
or
how
do
you
configure
the
icon
or
how
do
you
pre
configure
web
part?
Those
things
are
in
concepts
and
scenarios.
You're
gonna
see
anode
concepts
and
scenarios
across
multiple
places
in
the
nav
you'll
see
things
here
like
how
do
I
work
with
Microsoft
teams.
A
So
here's
a
bunch
of
articles
here
about
working
with
Microsoft
teams
or
working
with
add-ins
same
thing,
same
kind
of
organization
concept
with
extensions.
We
did
the
same
thing
now,
you're
gonna
see
here.
We
only
have
three
extensions
listed,
we're
technically
we
have
four.
Now
we
have
app
customizers,
we
have
field
customizers,
ListView
command
sets
in
query
extensions.
A
You
see
app
customizers
is
missing,
that's
kind
of
the
awkward
one,
because
that's
the
one
that's
used
here
inside
the
getting
started
for
going
through
and
deploying
a
new
extension,
so
that
is
covered
and
again
concepts
and
scenarios
tenant
wide
deployment.
Pre-Allocated
placeholders,
oh
yeah,
another
good
copic
here
tenant
wide
deployment,
we'll
check
this
out.
We
have
a
whole
section
now
in
the
sharepoint
development,
not
specifically
sharepoint
framework,
but
around
sharepoint
development
about
all
about
setup
and
deployment.
We
even
have
a
page
dedicated
to
2016
support.
A
We
have
a
page
dedicated
to
2019
support
as
well.
Let's
see
Oh
another
one,
though
this
is
a
change.
I
love
that
we
did
this
well
I
mean
I.
Did
this
so
I'm
happy?
We
did
it
you'll
just
so
anyway,
there's
more
stuff
that
you
can
go.
Take
a
look
at
here
inside
SharePoint
framework
around
SharePoint
add-ins,
or
we
have
actually
not
added
add-ins
is
just.
This
is
all
pretty
obvious.
A
Here's
just
the
same
kind
of
setup
is
what
we
have
with
a
section
before
with
Adams,
but
what
I
really
wanted
to
show
you
here
is
we
have
this
SharePoint
api's?
If
you
know
what
you're
looking
for
oh
my
gosh,
this
is
so
much
better
berry.
We
used
to
have
the
SharePoint
REST
API
buried
away,
and
we
had
a
navigation
I
said:
SharePoint,
REST,
API
and
in
the
ones
in
SharePoint
REST,
API
v2.
We
actually
got
questions
well,
where's
the
v1.
Well,
it's
the
one
that
doesn't
have
anything
listed
by
it.
A
It's
like
so
we
just
added
a
v1,
make
it
simpler,
AOM
and
lifecycle
management
for
a
ALM
ap.
Is
that
got
moved
over
here.
We've
got
PMP
site,
PMP
API
related
links,
they're,
not
buried
with
all
the
other
P
and
P
stuff,
because
maybe
somebody
is
looking
for
an
API,
so
it
makes
more
sense
to
go
to
API
s.
So
we
have
that
here.
A
Scenario:
guidance
in
archive
are
the
two
sections
that
are
the
older
content
that,
yes,
it
would
be
great
if
we
could
have
you
know,
20
people
go
in
and
spend
the
next
three
months
refreshing.
This
content
and
updating
it,
but
right
now
we
wanted
to
just
indicate
if
we
used
to
have
a
section
called
SharePoint
development
overview,
and
that
was
what
archive
was
well.
A
lot
of
people
went
to
that
first
and
that's
not
what
we
wanted
them
to
do.
A
We
wanted
them
to
go
to
like
getting
started
or
SharePoint
framework
or
SharePoint
add-ins,
so
we've
renamed
it
to
archive
it's
the
best
of
all
of
the
worst
options
that
we
had
available
to
us,
and
it's
simply,
we
use
the
word
archive
to
try
and
communicate
if
you
need
some
of
the
old
stuff.
This
is
old
guidance
here
right.
We
these
things,
may
get
moved
around
and
updated
and
refreshed
over
time,
but
right
now
this
is
where
it
is
same
thing
with
scenario
guidance.
Some
of
this
stuff
is
older
guidance.
A
Some
of
it
is
newer
stuff,
like
you've,
got
things
about
remote
provisioning.
That's
that's,
obviously,
that's
current.
That
makes
a
lot
of
sense,
remote,
timer
job
framework
that
was
discussed
earlier,
the
office
365
CLI,
the
PowerShell
reference
all
that
stuff.
That's
inside
this
scenario,
guidance.
The
last
thing
that
I
want
to
highlight
here.
We
had
the
section
here
for
schema
reference.
We've
refactored
this
a
little
bit
to
make
sure
if
you
know
that
you're
looking
for
a
specific
schema
via
JSON
schema,
be
it
a
office.
A
Add
in
schema
feature
schema
solution
whatever
it
is,
it's
all
right
here,
it's
in
one
spot,
and
we
also
have
a
page
here
for
two
pages,
one
for
SharePoint
community
and
one
for
support
and
feedback,
and
we
have
a
whole
thing
where
it
talks
about
on
the
overview
page.
It
explains
you
know
what
kinds
of
things
are
you
looking
for
programming
questions,
here's
where
they
go
documentation
bugs
sample
application,
bugs
go
to
the
different
repos
that
are
available
to
us
to
submit
your
issue
feature
request
guidance:
how
to
go
about
submitting
an
issue
issue.
A
We
explain
that.
Actually
we
redirect
right
over
to
the
issue
list
looks
like
I've
got
some
work
to
do
with
all
these
triage
'iz,
but
anyway,
there's
a
lot
of
stuff
that
we
did
here.
We've
got
the
section
here
for
tutorials
that
was
here
before,
and
it
points
to
the
same
links
of
where
this
stuff
was
before
we
made
this
page
could
definitely
get
updated
as
we
have
more
tutorials
get
launched.
So
lots
of
changes
just
lots
of
reorganization
and
hope
that
is
interesting.