►
From YouTube: Preview of the SharePoint Starter Kit v2
Description
In this 17-minute developer focused demo, Eric Overfield gives us a tour of the newly released SharePoint Developer’s starter kit that helps developers’ provision and customize SharePoint sites. This is a developer's (accelerator) tool for use in a developer tenant, as opposed to a production tenant even though the code is production quality. Starter Kit V2 has more web parts, templates, demos, and documentation than V1. Installation amounts to running 2 Cmdlets and waiting 10 minutes. The result: Fully provisioned and graphically stunning hub and team sites. This Kit is the result of countless hours of work by nearly 20 members of this PnP community. Please use, share and contribute. Starter Kit V2 contains: 16 SPFx web parts, 5 SPFx extensions, 1 SPFx library, 3 PnP provisioning templates, SPO provisioning template includes 1 very fully provisioned collaboration site, 2 team sites, populated mega menu, 15 communications site pages, and completely customizable PnP provisioning templates. This demo is extracted from the bi-weekly PnP community – SharePoint Framework and JavaScript Special Interest Group (SIG) call recorded May 21, 2020.
Presenter: Eric Overfield (PixelMill ) | @EricOverfield
Supporting materials:
• SharePoint Starter Kit v2 | https://github.com/pnp/sp-starter-kit/tree/v2
All Microsoft 365 & SharePoint Community - PnP demos: https://www.youtube.com/playlist?list=PLR9nK3mnD-OWSbg0o9a7mx_E7s2u7h_o2
Learn more about the SharePoint developer community at: http://aka.ms/m365pnp
A
Okay,
so
proud
to
announce
were
finally
getting
here
on
a
very
long
journey
and
we're
not
yet
done,
but
that's
all
good.
The
journey
should
never
end
we're
looking
to
release
the
version.
2
of
the
SP,
starter
kits,
I.
Think
that's
super
cool
super
exciting
for
those
of
you
who
are
new
to
the
starter
kit
or
haven't
seen
it.
A
Don't
worry,
we're
gonna
get
to
that
as
well,
but
it's
just
it's
an
evolution
of
this
tool
that
we
really
want
to
see
developers
be
able
to
have
to
help
see
a
end
and
not
only
provisioning
solution,
but
also
to
get
to
see
some
sample
web
parts
all
put
together.
Some
extensions,
some
some
all
kinds
of
cool
stuff
and
see
what
it
does.
So.
A
This
was
released
about
two
three
odd
years
ago:
v1
it
went
through
another
minor
iteration,
and
this
is
now
the
big
one,
and
so
another
really
big
change
is
so
we
had
some
aims
here
on
what
we
were
looking
to
do.
So
one
of
the
things
is
that
the
version
one
included
one
SharePoint
framework
solution
for
all
the
web
parts
and
the
extensions
and
there's
a
big-ass
from
a
lot
of
people.
A
Hey
we'd
like
to
get
just
one
web
part
and
no
Cameron
and
some
others
split
those
out
sort
of
in
a
sense
outside
of
the
project
or
unofficially
outside
of
the
project
which
helped
you
all.
But
we
wanted
that
to
be
a
first
party
experience
directly
within
the
solution
itself.
So
we
want
to
split
all
that
out.
We
wanted
to
be
able
to
offer
some
sort
of
support
for
SharePoint
2019
as
well
as
SharePoint
Online.
A
The
star
there
on
the
20:19
is
that
the
provisioning
template
aspect
for
2019
is
not
yet
ready,
but
the
the
web
parts
that
are
available
for
2019
could
be
used
today,
which
is
helpful.
We
also
wanted
to
do
to
provide
more
demonstration
around
some
of
the
new
tools
that
have
been
coming
out,
such
as
integrating
with
the
graph
API
and
using
the
graph
toolkit
directly
in
SharePoint
Online.
Of
course,
there's
great
demos
already
available
for
that.
But
we
wanted
to
include
that.
A
In
add
this
more
of
a
package
solution,
we
also
wanted
to
include
a
SharePoint
framework,
a
library
so
that
you
could
you
so
that
you
could
sort
of
see
them
together
in
a
full
deployed
solution
as
well
as
that
then
getting
deployed.
So
what
we've
done
so
far
is
we
have
a
library,
shopping
framework
library?
We
have
one
of
the
web
parts,
one
of
the
web
parts,
that's
designed
only
for
sheriff
online
cuz.
You
know
crap,
isn't
a
20-19
thing
really.
A
So
there
are
some
some
web
parts
that
are
not
going
to
be
available
in
the
2019
build,
but
are
in
the
20s
your
funnel
I
built.
So
we've
integrated
one
with
the
library
that
I'm
really
excited
about
how
it
was
put
together.
That
was
Elio
strew.
Some
idea
around
language,
strengths
localization,
would
be
a
library
component.
Some
of
you
might
have
seen
some
blog
posts
that
he's
written
on
that
we'll
be
able
to
integrate
that
directly
into
the
project.
A
Also,
as
that's
the
head
mention
at
the
beginning,
to
demonstrate
the
teens
tab
development
within
SharePoint
framework.
So
the
idea
that
you
could
then
just
build
these
web
parts
and
then
they
could
be
available
directly
within
teams
as
well,
and
then
also
we
wanted
to
demonstrate
some
of
the
new
UX
designs
and
Lape
abilities
that
are
available
within
SharePoint
Online
and
I
put
it
after
there
because
it
is
working
per
se.
It's
we
want
to
extend
it.
A
So
the
new
starter
kit
is
going
to
deploy
a
portal
is
going
to
deploy
some
team
sites
etc,
and
it's
gonna
deploy
pages
and
on
the
primary
portal
landing
page.
It
is
using
the
new
layout
structure
that
Microsoft
is,
has
been
recommending
to
us
all
and
putting
webparts
how
it
should
be,
but
it's
not
as
built
out
as
as
we'd
like
to
see
it.
The
URL
for
this
will
say
this
a
couple
times.
I
know
there's
a
quicker
one
as
well,
but
what
I
always
go
do
is
just
github.com,
slash,
PNP
the
SP
starter
kit.
A
If
you
want
to
get
started
today,
I
am
gonna
have
a
little
piece
in
a
little
bit.
If
you're
gonna
go
there
right
now
or
while
I'm
talking,
the
master
branch
is
still
on
v1.
On
purpose,
I'm
gonna
make
this
change
it,
probably
today
or
tomorrow,
where
the
master
branch
will
be.
The
v2
we'll
talk
about
some
of
the
limitations,
but
one
of
them
is
there's
no
direct
upgrade
path
from
v1
to
v2.
Right
now,
because
of
the
way
the
solutions
are
built
there.
A
If
you
install
this
over
an
existing
installation,
you're
gonna
get
two
copies
of
all
the
web
parts
and
that's
not
normally
ideal
for
most
people
and
we're
not
gonna
delete
those
automatically
for
you.
So
you'll
just
want
to
switch
to
the
v2
branch.
When
you
go
to
github
you'll
see
all
the
documentation
there,
you'll
get
all
the
code
and
all
that
really
cool
stuff.
A
Before
we
continue,
though,
I
really
do
want
to
say
some
big
thanks
to
everyone
who
contributed
here,
the
people
that
have
really
been
helping
me
on
this
on
the
cores,
Bochum
or
big,
big
thanks
there
Elio
has
some
great
ideas.
Of
course
you
got
to
thank
Paulo
and
Irwin.
They
were
the
the
fathers
of
the
starter
kit
and
they
gave
us
such
a
great
foundation
to
work
with,
and
then
we
had
a
whole
bunch
of
other
people
who
helped
us
with
with
the
translation
of
the
web
parts.
A
A
The
documentation
right
at
the
top
is
either
going
to
say
v2
or
it's
not
so
that's
kind
of
we're
gonna
keep
that
in
place,
probably
for
for
many
months,
if
not
many
quarters,
because
it
is
a
pretty
big.
It's
a
pretty
big
change
and
we
know
that
there's
going
to
be
a
lot
of
people
who
are
using
v1
and
they're
still
going
to
be
having
questions,
and
we
want
to
make
sure
they
understand
that
this
new
code
they're
looking
at
is
a
v2
change.
A
It
is
different
and
will
of
course,
link
back
to
the
version
1
documentation,
so
that's
not
lost
we're
looking
to
have.
There
are
16
SP
effect
webparts
in
this
one
solution.
There's
5
extensions
is
the
library
there's
3
PP
provisioning
templates,
there's
gonna
be
the
default
one
for
sharepoint
online,
there's
a
one
for
2019,
and
then
there
was
also
one
that
will
just
install
the
just
install
the
SPF
X
solutions.
A
What's
really
important
for
us
when
we
were
building
this
was
those
provisioning
templates
are
designed
to
absolutely
be
customizable
by
you
that
this
is
a
developer's
tool.
I'm
happy
to
see
many
people
take
the
starter
kit
door
right
in
production.
From
my
perspective,
that's
not
really
what
the
aim
is.
The
aim
is
as
a
developer's
tool
to
see
in
place
on
a
dev
tenant
and
then
to
quickly
get
under
the
hood
and
start
making
the
changes
and
then
pushing
that
out
to
your
to
your
production,
tenants
I.
A
That
means
that
I
I
think
the
code
is
solid
and
I
think
the
solution
is
definitely
the
right
way
to
go.
So
if
it
works
in
production.
For
you,
ok
good
for
you,
the
provisioning
Templin,
our
SharePoint
aligned,
you
get
a
communications
like
just
like
v1
team
sites
that
comm
site
is
gonna,
be
a
hub
site.
The
team
sites
are
automatically
associated
with
it.
Of
course,
this
is
all
done
for
you,
you're
gonna,
see
in
my
installation.
It's
effectively
two
commands
and
you
get
all
of
this.
A
There's
a
populated
mega
menu
that
will
be
that
will
be
deployed.
You
get
a
whole
bunch
of
pages
in
that
comp
site,
15
pages
or
deployed
for
you,
the
full
details
of
what
this
is
going
to
provision
for
you,
including
some
content
types
and
lists
and
libraries.
Some
other
assets
as
well
is
all
found
in
the
provisioning
template
which
I'm
going
to
do
my
best
to
get
to,
as
you
can
least
see
where
it
is
and
again
that's
designed
to
be
reviewed
by
you,
customized
by
you
and
turned
into
your
provisioning
solution.
A
So
it's
fully
fully
customizable
how
you
get
started
on
all
this,
so
it's
a
very
similar
process
to
v1,
of
course,
go
to
go
to
the
github
page
for
now,
as
I
said,
go
to
that
v2
branch,
you're
gonna
connect
to
their
site,
I,
put
in
your
contoso
demos,
s,
Cade
URL.
Of
course
you
want
to
change
that
and
from
the
project,
provisioning,
folder,
you're,
gonna
run
a
apply,
PMP
tenant,
template
command,
lit
and
sit
back
and
wait.
It
takes
about
10
minutes,
or
so
at
least
on
my
in
my
environments.
A
It
takes
about
that
long
with
that.
That's
it
look.
That's
supposed
to
be
how
easy
it
is.
I
worked
for
us
consistently
well
and
I'm.
Also
very
much
looking
for
feedback
from
you.
You
still
need
to
be
a
tendon
admin
to
make
all
this
work,
there's
a
whole
bunch
of
a
whole
set
of
prerequisites
that
are
found
in
the
documentation.
There's
actually
not
that
many,
but
there
are
some
things
that
you'll
need
to
do
as
I
said.
There's
no
current
upgrade
path
from
v1.
A
Don't
really
know
how
to
get
around
this
one
I
definitely
open
for
any
kind
of
ideas,
besides
just
general
documentation,
and
it's
mainly
because
of
the
duplicate
webparts.
The
the
web
parts
that
were
installing
most
of
them
really
are
just
they're
migrated
over
from
v1.
They
were
upgraded
to
a
more
current
version
to
sharepoint
framework,
but
they're
split
up
to
their
own
solution.
So
there's
gonna
be
the
the
personal
calendar
web
part.
Well,
now,
you'd
have
two
of
them.
A
If
you
had
both
v1
and
v2
and
we
did
go
with
new
IDs
because
we
basically
had
to
because
we
had
to
create
new
web
parts
as
well
as
I,
keep
talking
about
2019
that
provisioning
process,
as
I
said,
is
not
yet
finalized.
So
if
you're
looking
to
do
this
install
this
on
the
2019
today,
it's
not
there.
I'd
love
to
give
you
an
eight
ETL,
don't
have
one
it's
just.
It
sits
in
the
top
of
the
backlog,
but
it's
still
in
the
backlog.
A
So
up,
let's
go
ahead
and
let's
look
at
it,
you
can
see
the
you
can
see
right
now.
What
that
is
gonna
be
looking
like,
but
what
I
really
care
about
is
what
is
it
going
to
look
like
as
part
of
our
what's
gonna
look
like
live,
let's
look
at
code
and
let's
look
at
the
design.
So,
first
of
all
the
project
itself,
I
told
you
so
you're
gonna
go
to
the
project.
For
now.
A
If
you
just
go
to
the
v2
branch,
you'll
get
all
the
documentation
about
the
v2
starter
kit
and
please
do
read
through
this
doing
everything
I
can
to
provide
more
documentation
because
I
think
that
as
a
developer
tool,
that's
where
it's
is
gonna
help
so
that
you
understand
what's
there
and
really
try
to
accelerate
the
whole
solution.
Alright,
so
let
me
go
ahead
and
get
will
go
ahead
and
install
this.
A
So,
first
of
all,
of
course,
we're
gonna
connect
and
then,
after
we
connect
we're
gonna
run
a
simple
command
lit
now
this
command
lit
will
take
the
rest
of
the
time
that
I
have
so,
instead
of
actually
waiting
for
it,
I'm
gonna
go
ahead
and
show
you
what
it
actually
looks
like
that.
But
it
really
is
this
easy?
Alright,
so
let's
go
ahead
and
go
back
to
the
starter
kit
itself.
What's
gonna
happen
as
soon
as
that's
installed,
you're
gonna
get
a
nice
portal.
That's
gonna
be
created.
A
For
you,
a
whole
bunch
of
web
parts
are
automatically
added
to
you.
Everything
you
see
here.
This
is
a
default
installation.
I
have
not
done
anything
to
this
besides,
just
loaded
the
page
after
it
got
installed.
So
a
lot
of
content
is
added
for
you.
A
lot
of
web
parts
are
put
in
place.
Some
of
these
are
first
party
web
parts.
Some
of
these
are
the
custom
web
parts
included
as
part
of
the
page,
so
I
think
some
really
super
cool
stuff
there.
A
If
we
go
to
the
app
catalog,
what
you're
gonna
see
is
all
of
the
web
parts
that
have
been
installed,
and
so
now
is
again.
We
with
that
single
solution
per
web
part,
which
I
personally
am
a
big
fan
of
this
in
general
I,
think
this
is
the
right
way
to
be
building
solution.
So
I
know
when
I
first
started:
I
used
to
put
multiple
web
parts
in
a
given
solution
and
I,
just
I
think
for
ALM
I
just
found
that
split
in
the
mount
seems
to
make
a
lot
more
sense.
A
You
can
see
there's
a
whole
bunch
of
solutions
that
are
created
and
again
all
of
this
is
automated.
I've
ran
two
commands
and
I
got
all
of
this
cool
stuff.
So
let's
just
quickly
check
back
yep,
so
it's
still
going
on.
So
let's
go
ahead
and
let's
look
at
some
of
the
code
so
that
you
can
get
some
accelerators
here,
the
if
you're.
If
you've
worked
with
the
starter
kit
before
or
you
looked
at
the
code,
the
code
should
look
very,
very
familiar.
The
main
thing
we
added
was
the
source,
the
source
folder.
A
If
we
look
into
the
source
folder
you're
going
to
see
all
of
the
breakdown
of
all
of
the
web
parts,
the
extensions
etc
as
well
as
you're
going
to
get
down
here
at
the
templates-
and
this
is
where
the
magic
happens
is
down
on
in
the
templates.
So
you've
got
the
templates,
there's
started
katatak.
So
now
you
can
see,
we've
got
the
shells
to
the
other
two,
but
the
starter
code,
XML
is,
is
the
PNP
provisioning
template
that
does
all
of
the
magic
and
I've
started
to
add
some
comment
into
it.
A
To
me,
this
is
a
great
place
to
look
at
because
not
only
in
10
minutes
or
so
will
you
get
of
a
full
provisioned
solution,
but
you
can
then
see
how
the
provisioning
template
is
built.
Okay,
so
I
there's
a
couple
thousand
lines
of
code
there,
so
I
don't
have
time
to
go
through
it.
All
the
other
component
I
wanted
to
look
at
was
the
provisioning
folder,
so
within
the
provisioning
folder
you've
got
the
compiled
starter
kit,
dot,
P
and
P
files.
A
These
are
the
actual
P
and
P
provisioning
files,
and
what
happens
is
what
you
can
do
is
you
can
use
the
read
EMP
template
command
lit
that
is
going
to
allow
you
to
read
those
XML
files
and
then
all
you
do.
Is
you
say
that
PMP
template
tended
to
template?
Excuse
me
command
lit
that
will
allow
you
to
take
the
XML
files
that
are
found
down
in
the
source,
slash
templates
and
create
your
own
dot,
PNP
files,
and
then
you
can
just
do
a
simple
installation,
a
reinstallation
of
the
starter
kit.
A
This
piece
has
not
been
undocumented.
This
is
one
of
the
top
documentation
pieces.
That
I
know.
That's
left,
because
to
me
this
is
the
one
of
the
next
big
steps.
You're
gonna
want
to
do
is
build
your
own
provisioning
template
based
upon
the
examples
that
are
here
and
although
it's
only
two
commandlets,
it's
very
well
documented
in
general
how
to
take
a
PNP,
XML
template
and
turn
it
into
a
dot
PMP
file
and
then
run
the
apply.
Pbt
template
command.
Lit
I
really
want
to
make
sure
that
that
is
spelled
out
for
you.
A
So
I
can
hopefully
try
to
save
you.
You
know
that
extra
3060
minutes
of
thinking
what
am
I
supposed
to
do.
We
just
want
to
make
it
super
seamless
and
easy
for
you
to
be
able
to
do
that.
Okay,
so
I
want
to
ensure
I've
spent
a
lot
of
time
going
through
this
I'm
I'm
sure
there's
a
lot
of
really
fun
cool
stuff.
Here,
the
other
one
I
thought
was
really
cool.
A
Was
the
library
this
one
I
do
want
to
document
with
elio
I
think
it's
interesting
to
see
how
this
was
all
put
together,
where
we
basically
created
a
localization
string
localization
within
the
library
and
then
within
a
web
part
in
particular
of
the
web
part
that
we
activated
here
was
the
was
the
following
sites.
What
we're
doing
is
we're
utilizing
that
library
and
from
that
library
we
can
then
import
the
localization
directly.
A
So
what
you'll
see
is
that
this
particular
web
part
does
not
actually
have
there's
no
localization
folder,
because
it's
grabbing
that
from
the
library
a
great
way
to
have
all
of
your
webparts
utilize,
a
library
for
for
all
of
its
localization.
Ok,
so
let's
go
ahead
and
quickly
wrap
up,
because
we
only
have
so
much
time
left.
A
The
last
thing
I
want
to
do
is
how
you
could
help
so
please
this
is
basically
what
we're
looking
at
is
a
beta
release
so
install
the
solution
in
a
dev
tenant
and
provide
feedback.
I
would
love
to
have
more
people
working
with
this
playing
with
this
finding
bugs
finding
issues
helping
us
find
gaps
in
documentation.
What
are
you
looking
to
do
that
doesn't
currently
work?
What
is
it
that
you're
looking
to
do
you
don't
understand?
A
Please
use
the
issues
list
within
the
project,
VOC
camera
and
updated
the
the
template,
the
issues
template
to
try
to
help
steer
you
the
right
spot
to
help
you
get
the
content
to
us
so
that
we
can
help
you
address
these.
Also,
though,
hey
we're
looking
for
PRS.
If
you
find
a
bug,
please
make
a
PR
for
pull
the
latest
code.
Put
it
on
the
dev
branch,
just
like
you
normally
would
we'd
love
to
get
that
merged
as
soon
as
possible.
A
If
you
find
gaps
and
documentation
solve
them,
please,
if
you
find
something
cool,
let
us
know
create
an
issue
and
say:
hey
I
solved
it.
Could
someone
go
and
create
a
documentation
on
it?
Anything
you
could
do
that
to
to
help
share
I
would
be
greatly
greatly
appreciated,
but
also
as
well
promote
this
on
social
channels.
You
know
let
people
know
this
is
out
there.
Let
people
know
your
experiences,
ideally
if
they're
good,
of
course,
we're
also
definitely
looking
for
videos,
blog
post
recommendations,
insights,
etc.
A
I
want
to
see
a
lot
of
videos
on
using
this,
because
I
think
this
is
a
great
accelerator
tool.
That
being
said,
I
don't
want
to
do
all
those
videos,
particularly
because
it's
not
about
me.
This
is
obviously
about
all
of
us,
so
for
everybody
to
help
you
everybody,
so
please
we
would
love
to.
Have
you
be
a
part
of
this
as
well,
so
with
that
VESA
I'll,
give
you
the
last
minute
back
and
you
wrap
it
up.
Excellent.
Thank
you.
Thank
you,
Eric
for
that
one
and
really
great
for.