►
Description
This community call demo is taken from the SharePoint General SIG community call recording on 5th of September 2019. In this video, Paolo Pialorsi (PiaSys) demonstrates a solution pattern to synchronize modern page templates across site collections.
Presenter - Paolo Pialorsi (PiaSys) @paolopia
Full details on the community call from https://developer.microsoft.com/en-us/sharepoint/blogs/sharepoint-dev-community-pnp-general-sp-dev-sig-recording-5th-of-september-2019/
More details on the modern page templates - https://support.office.com/en-us/article/page-templates-in-sharepoint-online-faa92408-0c84-4e3d-8460-3c28065e7873
More details on the SharePoint dev community calls from http://aka.ms/sppnp.
A
Welcome
everybody
from
myself
as
well
and
let's
talk
a
little
bit
about
how
we
can
synchronize
page
templates
across
multiple
site
collections.
First
of
all,
let's
start
talking
about
page
template
very
briefly,
just
to
be
sure
that
we
are
all
on
the
same
pages.
So
you
know
that
in
a
modern
site,
especially
if
you
are
in
a
communication
site,
you
can
create
a
new
page
and
you
can
use
a
page
template
if
you
like,
so
that
these
page
templates
can
behave
almost
like
the
page
layout.
A
A
It
is
really
useful
and
powerful,
and
when
you
want
to
create
your
own
custom,
page
templates,
you
simply
need
to
create
a
new
page
in
a
modern
site
and
when
you
will
publish
your
page
of
course,
I
have
to
provide
name
which
of
course,
will
be
named.
And
when
you
publish
a
page,
you
can
select
to
make
that
page
available,
also
as
a
page
template
under
the
cover.
What
will
happen
will
be
that
and
let
me
leave
this
page
because
I
don't
really
need
it.
A
A
So
what
if
we
want
to
share
the
same
set
of
page
templates
across
multiple
modern
site
collections,
so,
for
example,
whenever
we
create
a
new
modern
communication
site
or
modern
tune
site,
we
want
to
have
an
out
of
the
box
set
of
page
templates
available
and
eventually
we
also
want
to
keep
all
of
the
site
collections
in
sync.
So
we
have
exactly
the
same
set
of
page
templates
across
all
of
these
site
collections.
A
Well,
one
option
is
to
use
the
PMP
provisioning
engine
and
to
create
a
PMP
provisioning
template
which
will
do
the
actual
provisioning
of
the
page
templates
across
all
of
your
site
collections.
And
what
is
the
suggested
architecture
for
achieving
this
goal?
I
said
so
far
on
this
line,
because,
right
now,
this
is
a
technique
that
you
can
use
the
one
that
I'm
talking
about,
maybe-
and
that's
my
hope
at
least
in
the
future.
A
To
give
you
an
idea
of
the
overall
architecture
of
a
proposed
solution
for
this
need,
you
can
have
a
custom
set
design
which
will
be
available
in
the
list
of
designs
that
you
can
select
when
you
create
a
modern
site.
Once
you
create
a
sub
design
inside
of
the
site
design,
you
can
use
the
trigger
flow
action,
which
will
be
useful
to
invoke
an
external
max
of
flow
flow,
so
we
are
back
again
home
flow
and
using
flow.
You
can
put
a
message
in
a
queue.
A
The
flow
can
be
an
HTTP
triggered
flow
so
that
you
will
wake
up
the
flow
instance
with
an
HTTP
request.
Coming
from
the
side
design,
you
will
put
a
message
in
a
storage
cube
and
thanks
to
the
message
in
the
storage
cube,
you
will
activate
a
nature
function
which
will
be
used
to
do
the
actual
provisioning
of
the
PMP
provisioning
template,
which
will
include
the
page
template.
So
how
can
we
do
that
in
practice?
A
First
of
all,
from
a
EMP
point
of
view,
we
can
connect
to
a
site
which
can
be
the
repository,
the
source
repository
of
our
page
templates,
and
we
can
get
the
provisioning
template
out
of
that
site.
We
have
to
declare
that
we
want
to
include
all
the
client-side
pages
we
target
the
page
contents
handler
only
so
that
we
will
get
a
very
clean
and
simple
provisioning,
template
and
I
already
did
it
targeting
this
site.
A
So,
basically
the
page
template,
and
if
let
me
say
we
are
smart
enough
to
keep
a
site
collection
dedicated
to
be
the
model
or
the
repository
for
page
templates
that
we
want
to
share
across
all
of
the
site
collection.
We
will
simply
need
to
use
the
common
light
that
I
showed
you
the
gate,
TMP
provisioning
template.
We
will
include
the
client-side
pages
and
we
will
get
back
all
the
page
templates.
A
The
finest
client-side
page
elements
in
the
provisioning
template,
together
with
any
additional
file
like,
for
example,
the
background
image
that
I
selected
for
my
custom,
page
template
and
by
applying
this
template
onto
a
target
site
which
we
need
to
create
right.
Now.
Let
me
do
that.
Let
me
go
to
the
root
of
SharePoint
and
let
me
create
a
target
site
which
I
will
call
page
and
place
target
and
as
soon
as
the
page
will
be
ready,
I
will
be
able
to
create
a
new
communication
site.
A
For
example,
I
will
call
it
like
we
just
so-so
based
in
place
target.
Let
me
create
it
and
in
a
matter
of
few
seconds,
as
soon
as
the
target
will
be
created,
I
will
be
able
to
connect
and
to
apply
my
target
provisioning
template
on
to
this
side.
So
let's
do
that?
Let's
connect.
We
connect
the
MP
on
line
and
let's
apply
the
PMP
provisioning
template,
and
by
doing
that,
you
will
see.
A
So,
as
I
said,
pretty
useful
and
interesting,
really
powerful
scenario,
just
with
few
PowerShell
lines
of
code
and
a
very,
very
simple
and
lightweight
flow
and
site
design
in
place,
and
that's
it
for
this
short
demo.
It
was
a
ten
minute
demo,
so
I
try
to
do
my
best
to
save
some
time
so
that
we
can
eventually
have
some
room
for
any
question
in
the
Q&A
area.
Thank.
B
You
Paula,
thank
you
for
creating
a
quick
one
and
but
it's
super
useful
demo,
because
it
really
shows
to
simplicity
on
on
extracting
and
applying
those
templates
and
lists
as
ray
bates
templates
from
existing
side.
So
just
one
clarification
on
page
template
and
base
layout
usage,
and
these
are
baits
templates,
which
means
that
they're
basically
starting
points.
B
There
are
no
looked
sections
because
that's
not
supported
in
the
more
on
SharePoint
pages,
at
least
for
now,
we'll
never
know
what
will
be
available
in
the
future,
so
the
classic
kind
of
a
Bates
layouts
in
the
Pampas
inside
of
the
house.
They
supported
kind
of
a
lockdown
sections
and
controls
and
that's
not
supported
with
the
modern
side
of
the
house,
but
super
simple
demo,
but
super
powerful
demo
on
using
the
templating
mechanism
for
doing
that.
Now
there
was
a
few
questions
related
on
the
on
the
licensing
and
all
of
that
stuff.
B
Right
now,
at
least
personally
I
don't
want
to
comment
anything
even
spec
of
speculate.
Anything
related
on
licensing
things,
I.
Think
John
responded
on
on
some
of
those
yet
already
so
clarifying
at
least
integration
between
the
the
list
and
and
the
flow
now.
What
does
this
scenario
would
mean
from
a
licensing
perspective?
What
Paula
showed
and
I
I
don't
want
to
speculate
on
that,
and
there
are
licenses.