►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello
and
welcome
to
the
SharePoint
framework,
a
JavaScript
special
interest
group
biweekly
meeting
is
February
1st
2018
welcome
to
February.
It
is
a
new
month
and
we've
got
a
great
call
for
you
here
today.
As
always,
we're
gonna
start
off
with
a
discussion
of
what
these
calls
are
all
about,
perhaps
you're
new
to
the
call
or
new
to
watching
the
recordings.
A
These
calls
are
part
of
the
overall
SharePoint
patterns
and
practices
program,
and
we
started
these
special
interest
calls
because
we
had
just
grown
too
much
to
be
able
to
cover
everything
in
our
one
monthly
call.
So
we've
started
some
more
frequent
calls.
This
is
one
of
them.
This
is
focused
on
client-side
development,
SharePoint
framework.
We
have
another
one
on
the
PowerShell,
see
some
managed
code
development
as
well
attend
as
many
or
as
few
of
these
as
you'd
like
we're,
always
happy
to
have
folks
on
the
calls
and
we'll
be
covering.
A
Generally
speaking,
we
have
an
agenda
coming
up,
but,
generally
speaking,
we
have
an
open
discussion
around
SharePoint
framework
and
client-side
development
patterns,
as
well
as
the
PNP
Jazz
libraries
which
we're
building
to
help
emphasize
simple,
repeatable
and
tested
designs
for
use
in
your
SharePoint
framework
applications
as
well
as
general
client-side
development.
We've
got
two
links
down
there
at
the
bottom.
The
first
one
AKA
ms
SP
P
and
P
community
takes
you
to
the
Microsoft
tech,
community,
SharePoint,
dev,
specific
area
of
the
tech
community.
That's
a
great
place
for
general
questions.
A
If
you
have
how
do
I
kind
of
questions
or
getting
started
questions,
that's
a
fantastic
spot
to
get
those
asked
and
answered
the
second
link
there.
The
SP
dev
Doc's
takes
you
to
the
official
documentation
for
all
of
SharePoint
development,
so,
whether
you're
getting
started
with
SharePoint
framework
or
whether
you
are
looking
for
details
around
sort
of
SharePoint,
add
in
development
or
classic.
A
You
know
W
SPC
song,
sorry
w
SP
manage
full
blah
I'm,
just
fumbling
that
all
over
the
place,
the
original
w
SP
development,
all
of
the
different
code
details
are
there
in
the
docs,
we're
always
looking
for
feedback
on
those
Doc's,
we're
always
looking
to
improve
those
Doc's
as
well.
So
if
you,
if
you
find
something
missing
or
lacking
just
let
us
know
we'll,
do
our
best
to
get
those
updated,
we
do
have
a
very
small
team
for
managing
the
documentation
so
bear
with
us.
A
A
So
that's
gonna,
be
a
really
cool
demo,
sort
of
an
end
to
end
building
on
a
lot
of
different
technologies,
to
create
news
articles
and
manage
news,
articles
and
they're
publishing
and
at
the
end,
we'll
see
if
we
have
a
little
bit
of
time
for
some
Q&A.
But
as
always,
if
you
have
questions
you
can
ask
them
in
the
IM
window
and
we'll
do
our
best
to
stay
caught
up
there
before
we
get
to
latest
on
the
SharePoint
framework.
A
We
always
like
to
talk
about
opportunities
to
get
involved
in
the
this
special
interest
group,
as
well
as
the
overall
patterns
and
practices
program
in
general.
So
you
can
always
we're
always
looking
for
great
demos,
so
those
demos
could
be
a
SharePoint
framework
solution
or
something
involving
the
PNP
jeaious
libraries
and
you
know
anything
around
SharePoint
client-side
development,
if
you've
written
something
cool
and
would
like
to
show
it
off
to
the
community.
That's
a
great
learning
opportunity
for
all
of
us
in
the
community
to
see
the
awesome
things.
A
People
are
building,
but
it's
also
a
great
opportunity
for
you
to
kind
of
demo
your
work
and
sort
of
show
that
off
so
I
personally,
my
favorite
part
of
these
calls
is
the
community
demos
I
think
it
really
benefits
all
of
us.
We
really
learn
a
lot
from
seeing
what
other
folks
are
doing
out
there
and
the
techniques
they're
using
and
that
sort
of
thing
you
can
also
contribute
on
github,
so
contributing
on
github
can
be
submitted
a
pull
request.
You
could
submit
issues
submit
questions.
A
We
appreciate
all
that
feedback
and
are
always
looking
for
folks
who
want
to
get
involved
on
github
and
help
out
with
the
coding.
That's
super
valuable.
We
definitely
appreciate
the
time
folks,
invest
there
and
I
know
on
lots
of
different
areas.
Folks,
you
know,
have
requests
for
features.
Why
doesn't
this
or
that
library
have
a
certain
capability?
And
it's
not
that
it's
a
bad
idea?
It
might
just
be
restricted
by
time.
So
if
it's
something
you
would
really
like
to
see
in
a
library,
I
definitely
encourage
you
to
write
that
code
submit
a
pull
request.
A
If
you
need
a
little
bit
of
help
getting
started
on
that,
that's
it's
perfectly
fine
to
reach
out
and
let
us
know,
but
sometimes
the
quickest
way
to
get
the
feature
you
want
in
the
library
is
to
submit
a
pull
request
and
then
finally
providing
feedback.
We're
always
looking
for
feedback
on
everything
we
do
within
patterns
and
practices.
So
these
specialist
group
calls
are
monthly
calls.
You
know
the
code,
we're
producing.
The
samples
were
producing.
A
Excuse
me
all
those
sorts
of
things.
We
really
appreciate
the
feedback
and
the
feedback
really
drives
our
growth
and
drives
our
roadmap
around
how
we
prioritize
things
so
appreciate
the
feedback
we've
gotten
in
the
past
and
look
forward
to
the
feedback
from
folks
in
the
future,
so
my
hand
things
over
to
vaison
now
for
the
SharePoint
framework
update
yeah.
B
But
let
me
quickly
update
on
certain
things
and
show
you
some
stuff
on
on
the
shipment
framework
side
and
then,
of
course,
and
the
other
community-driven
topics
and
I'm
trying
to
take
over
the
presentation
to
treat
the
dirty
little
cuckoo.
I'm
saying
loading
Patrick
help
me:
okay,
there.
It
is
what
happened
interesting.
We
went
back
to
slide
number
one.
B
Always
happens
so
really
around
the
latest
on
shipment
framework
from
shipment
engineering
and
just
to
clarify
I
personally
I
work
in
the
splat
team,
and
our
team
is
responsible
of
all
of
the
development
api's
and
their
level
development
patterns
and
guidance
and
documentation
for
SharePoint
development
and
one
tribe
development
as
well
in
the
future.
There's
some
reorg
and
everything
else
happening
in
our
site
so
and
we're
combining
some
of
these
topics
in
our
well.
We
ownership
inside
of
the
engineering
both
be
combined,
but
obviously
the
topics
are
slightly
different.
B
Now,
let's
actually
get
on
going
on
these
few
slides
on
topics.
At
a
reminder,
Patrick
mentioned
this
one
already,
a
kms
s/pdif
docks
essentially
will
is
a
redirection
to
dock
stock.
My
turtlecom
slash
upon
slash
dev,
which
is
our
official
new
location
for
all
of
the
development
documentation.
Now
we
do
you
know
that
these
some
of
these
documents
are
not
quite
up
to
date
and
we're
working
on
that
one
that
is
say
a.
How
would
I
put
it.
B
It's
big
challenge
for
us
to
try
to
figure
out
the
right
balance
on
creating
samples,
creating
docks
and
updating
this
documentation.
Considering
the
resources
which
we
have
so
but
looking
into
reducing
some
of
the
guidance,
for
example,
and
unnecessarily
not
up-to-date
guidance
on
the
add-ins
and
maybe
from
a
solution,
architects,
Ellucian
scenario,
old
scenario,
solution
based
items
and
introduce
them
as
a
more
approachable
documentation
in
future,
so
we're
working
with
few
MVPs
and
few
internal
resources
on
updating
these
things,
but
yeah.
B
So
if
somebody's
wondering
yes,
we,
the
SharePoint
PMP
or
our
virtual
team,
is
also
owning
the
ship
on
development
documentation,
all
up,
which
is
an
interesting
discussion
on
this
side.
If
you
are
interested
on,
if
you
find
any
issues,
please
let
us
know,
and
that
comes
not
back
on
the
second
slide
which
I
wanted
to
quickly
cover.
B
So
if
you
find
any
issues
in
the
documentation
or
within
the
product,
please
let
us
know,
because
in
the
past
we
have
been
having
quite
a
lot
of
challenges
or
people
potentially
finding
issues
and
sure
there's
always
issues
and
box
in
our
service,
but
if
they
call
the
sharepoint
online
support
the
quite
often
the
response
in
our
official
support
has
been
something
in
the
employ
of
no.
We
don't
support
development
or
customizations
and
sure
we
do.
B
We
do
absolutely
support
customizations,
because
sharepoint
online
and
a
sharepoint
in
general
is
a
development
platform
or
hosting
platform
for
your
customizations,
so
we're
trying
to
fix
this
gradually
inside
of
the
microsoft
and
that
unfortunately,
does
take
some
time.
Those
dead
number
one
is
already
that
you
can
easily
reach
the
actual
sharepoint
engineering
people
who
are
building
this
stuff,
which
is
our
team,
the
splat
team
in
the
interpreter
ensign
by
using
this
issue
list.
B
So
there
might
be
still
issues,
even
though
your
buck
or
issue
which
are
reporting
there
might
be
delays
on
getting
that
one
fixed,
because
unfortunately
we
do
not
have
infinite
resources
in
our
consumption
either,
but
we're.
The
key
point
is
to
let
us
know
and
give
us
the
feedback
or
having
a
discussion
on
a
question
which
could
be
potential
enhancement
idea
and
then
will
redirect
you
to
the
user
voice
for
additional
discussion.
B
Moving
on
on
things
from
a
engineering
site,
one
of
the
things
what
I
wanted
to
I
showed
this
one
I've
been
in
a
ship
on
Saturdays,
two
weeks
in
a
row,
so
first
check
on
Saturday,
North,
Germany,
two
weeks
back
and
finish
up
on
Saturday
Helsinki,
which
is
which
means
that
I
haven't
had
a
free
weekend
for
a
long
long
time
and
I'm
gonna
lose
this
weekend
when
were
flying
back
home.
No,
but
one
of
the
things
what
I
shown
in
this
ship
on
Saturdays
and
round
the
ship
one
development
in
general.
B
Is
this
chart
around
the
shape
and
framework
usage?
The
reason
why
we
started
showing
this
now
is
that
people
still
seem
to
be
in
hesitant,
well
I,
wouldn't
say
in
hesitant.
It
is
actually
to
use
it
is
of
the
roof,
but
there
seems
to
be
a
still
AAA
open
kind
of
a
discussion
on
is
people
actually
using
the
SharePoint
Mangrum?
B
Is
it
actually
being
adapted,
and
the
answer
is
absolutely
so
shape
on
framework
is
twice
as
popular
already
in
SharePoint
Online
than
SharePoint
audience,
which
actually
gives
you
some
sort
of
a
a
let's
say,
understanding
on
how
much
people
and
customers
and
partners
are
actually
adapting
the
SharePoint
framework,
one
of
the
things
in
here
I'm
not
going
to
actually
deep
dive
on
the
exact
numbers.
So
they
are
intentionally
hidden
from
this
agenda,
but
you
can
actually
see
the
growth
since
August
I'm
not
going
to
actually
compare
the
exit
numbers
between
other
exit
numbers.
B
Well,
that's
kind
of
well.
This
is
not
at
a
right
time
to
actually
disclose
them
for
the
in
Selenas.
Basically,
we
can
actually
give
you
actual
numbers,
but
you
can
actually
see
the
growth
of
the
SharePoint
framework
usage
and
this
is
actual
usage
people
using
SharePoint
framework,
either
extensions
of
webparts
within
SharePoint
Online
and
adding
those
to
their
portals
or
photos
or
in-game
sites.
Now,
quite
often,
actually,
for
the
time
being,
the
most
the
biggest
usage
for
SharePoint
framework
system
seems
to
be
using
SharePoint
framework
with
bots
in
classic
publishing
sites,
which
is
absolutely
100%.
B
Valid
scenario
because
quite
often,
people
want
to
have
a
call
flow
and
webparts
in
the
pop
in
a
populist
in
porto
style,
experience
and
then
share
framework
is
no
doubt
the
right
or
the
the
best
technique
to
actually
make
that
happen.
Now.
Obviously,
communication
sites
is
kind
of
at
the
future
of
the
portal
site,
total
or
replacement
of
a
classic
publishing
portal.
B
But
it's
not
quite
there
yet
for
some
of
the
scenarios,
so
customers
are
still
building
a
lot
of
stuff
on
the
on
the
on
the
classic
focusing
or
they
might
have
already
classic
Potter's
inside
and
now,
they're,
adding
and
replacing
those
web
parts
or
spirit
editor
webparts
on
the
on
the
classic
portal,
with
a
SharePoint
framework,
specific
implementation.
So
super
cool,
though
I,
wanted
to
show
this
one
to
show
you
and
demonstrate
the
actual
usage.
These
are
live
stats
from
SharePoint
Online,
and
this
is
from
Tuesday
this
way.
B
So
you
can
actually
see
that
even
from
last
week
we
could
I
pretty
big
jump
on
the
usage.
So
there
were
certain
customers
who
took
SharePoint
framework
into
used
in
their
tenants
and
that's
always
increasing
them
to
active
usage.
Anyway,
super
cool
to
see
to
adoption
well
less
than
a
year
ago.
Well,
we
announced
GA
or
SharePoint
framework
with
with
parts
in
February
last
year
and
GA
for
SharePoint
framework
extensions
in
ignite
and
we're
already
past
the
add-ins
by
four
or
twice
as
popular
settings
and
where
the
growth
curve
is
actually
really
really
interesting.
B
So
if
you're
kind
of
in
between
should
I
learn
the
SharePoint
framework.
Well,
if
you're
planning
to
do
customizations
in
SharePoint
Online,
you
absolutely
should
learn
SharePoint
framework
and
one
step
at
a
time.
It
is
I.
It
will
take
some
time
to
learn
that
if
you
haven't
actually
had
a
look
on
down,
maybe
just
to
promote
well
ACS
is
easy.
Has
they
awesome
as
a
awesome
services
on
that
side
as
well
from
vojta,
knows
great
great
great
training
package
around
the
SharePoint
framework,
just
free
training,
material
from
us
as
well?
B
There's
others
provide
us
there
as
well,
but
it
is
also
one
of
the
active
community
members
super
active
community
members
in
our
SharePoint
deaf
community,
so
don't
feel
too
bad
on
promoting
him
in
this
course,
and
you're
welcome
acing,
now
moving
on
on
things
and
moving
on
on
things,
quick
update
on
the
SharePoint
framework
roadmap,
not
actually
that
much
has
been
changed
here.
I
want
to
keep
this
one
in
this
course
to
take
at
least
few
minutes
on
this
one.
Always
whenever
so,
you
don't
know
where
we
are.
B
We've
been
promising
that
what
we've
been
releasing
a
lot
of
stuff
since
September
and
that's
in
signal
now.
The
next
step
will
be
the
more
Microsoft
craft
support.
This
is,
unfortunately,
slightly
delayed.
We
originally
wanted
to
have
this
one
out
by
end
of
last
year,
so
end
of
December,
but
that
was
not
possible.
We
found
out
pretty
late
a
small
issues
on
that,
then
you
are
planning
to
get
it
out
on
end
of
January
and
now
it's
all
ready
for
us
to
prep
the
contract,
and
please
do
remember
to
mute
yourself.
B
Hopefully
it
will
be
early
next
week
if
we'll
still
find
last-minute
issues
in
the
final
testing.
It
might
be
still
delay
for
a
few
days,
but
it
is
really
really
coming
soon.
Perhaps
nights
and
crop
refine
api's,
there's
two
different
scenarios
that
they're
owned
by
two
different
people
in
in
the
Redmond
and
the
four
hub
sites
and
hub
api's
we're
looking
into
getting
that
one
out
potentially
during
this
month,
it's
at
making
sure
that
documentation
is
up-to-date
and
start
to
preview.
B
B
So
that's
gonna
be
our
spring
event,
where
we
check
deeper
and
ask
from
Redmond
our
connect
and
announce
all
of
the
new
stuff
and
explain
what's
actually
coming
so
super
cool
conference
coming
up
as
well.
Personally,
I,
don't
quite
like
the
Las
Vegas,
but
hey
no
can
do.
It
seems
to
be
the
location
where
these
things
and
conferences
are
being
held
in
there
once
and
that's
enough
so,
but
everybody
has
their
own
preference
than
that.
B
Now,
let's
move
on
on
things
because
I
don't
want
to
eat
too
much
time
so
Patrick,
let's
jump
on
the
community
side
of
the
story
and
let's
do
an
update
on
the
BMP
chase
and
then
also
an
update
on
office.
365
stay
ally,
our
reusable
controls
and
then
would
still
have
flight
demons
coming
up
as
well.
But
Patrick
take
it
away.
A
Great
thanks
face
a
great
update,
as
always
on
the
SharePoint
framework,
so
a
quick
update
on
the
PNP
client-side
libraries
so
right
now
we're
still
maintaining
two
separate
libraries
in
parallel.
I
want
to
talk
about
that
a
little
bit,
so
we've
had
some
questions
around
that
after
the
launch.
So
why
have
we
moved?
One
of
the
questions
was
wide.
Have
we
put
these
in
a
different
repo
instead
of?
A
Why
are
we
in
P
and
P
as
a
github
organization
rather
than
SharePoint,
and
the
reasoning
behind
that
is
we
had
a
lot
of
feedback
that
our
library
name
wasn't
matching
the
repo
name
which
wasn't
matching
the
other
things
and
so
forth.
So
we
tried
with
this
new
release.
We
got
control
of
the
P
and
P
org
and
github,
which
is
the
first
thing
after
us,
after
github.com
slash
that
first
thing
there
is
known
as
an
organization
in
github,
and
we
got
control
of
that.
A
So
the
idea
of
using
that,
as
we
now
match
our
scope,
the
at
P
and
P
scoped
to
the
org
that
were
publishing
out
of,
and
that
was
to
try
and
help
simplify
things
other
than
that
structural
move
to
try
and
align
things
with
the
scope
to
the
org
and
so
forth
and
github.
Nothing
else
has
changed.
The
library
is
still
part
of
sharepoint
patterns
and
practices.
It's
still
the
same
folks
behind
it.
It's
still
the
same.
You
know,
ideas
around
community
involvement
and
everything
else.
A
It's
simply
a
structural
move
to
kind
of
better
match
what
we're
seeing
other
folks
out
in
the
open
source
world
doing
and
trying
to
kind
of
align
with
that
does
this
another
question
was:
does
this
replace
the
SPP
and
PJs
and
the
answer
there
is?
Yes,
our
goal
is
to
over
the
next
five
months
or
so
deprecated,
SPP
and
PJs.
But
for
that
period,
what
about
feature
parody?
Are
they
gonna
have
the
same
features?
And
the
answer
to
that
is
yes.
A
So
when
we
get
a
feature
request
on
one
library
or
the
other
will
make
those
changes
and
then
we'll
actually
copy
them
back
and
forth
to
each
library.
So
we
maintain
feature
parity
for
folks
for
this
kind
of
dual
support
period.
So
that's
another
question,
we've
gotten
and
then
another
question,
as
are
these
ready
for
production
use?
An
answer
is
yes:
we've
got
the
first
real
version.
One
zero
one
is
out
of
all
of
the
at
PNP
scoped
libraries
I
encourage
you
to
check
it
out.
It's
ready
for
use
we're
looking
for.
A
We're
gonna
share
the
features
for
the
next
five
months
we
had
said
when
we
launched
the
new
libraries
we'd
support,
SP,
P
and
P
J's
for
another
six
months
and
that's
to
allow
folks
to
have
time
to
transition
as
well
as
to
give
us
time.
You
know
if
there's
critical
bugs
and
things
like
that
that
come
in,
we
want
to
make
sure
we
get
those
fixed
at
SP,
P
and
PJs,
and
then
over
those
six
months.
We
hope
folks
will
take
the
opportunity
to
transition
their
projects.
A
A
The
answer
is:
never
we're
not
going
to
unpublish
the
packages
out
of
NPM
we're
not
going
to
delete
the
repo
out
of
github,
but
we're
gonna
stop
updating
it.
So
if
you've
grabbed
SP,
P
PJs,
say
the
latest
version
and
you're
using
that
in
your
application
and
you
publish
that
and
everything's
working
fine,
that's
wonderful
and
you
have
no
reason
to
change
anything.
That's
going
to
continue
working
you're
gonna
be
able
to
continue
installing
it
from
NPM.
A
I
would
just
encourage
you
if
you're
starting
new
projects
or
have
an
opportunity
to
migrate
existing
projects,
to
start
to
go
to
the
new
libraries
where
possible,
and
that's
because
one
we've
tried
to
make
things
better
in
the
new
libraries
in
a
lot
of
ways
and
that's
where,
after
this
sort
of
five-month
period,
where
we're
going
to
be
putting
new
features
and
new
capabilities,
and
so
if
you
want
to
take
advantage
of
those
things
moving
forward,
you're
gonna
want
to
be
on
the
new
libraries.
So
yes
I
a
hundred
percent
understand.
A
This
is
a
disruptive
change,
but
hopefully
that's
minimized
a
lot
by
the
fact.
The
library
isn't
going
away.
It's
not
going
to
be
unpublished
as
well
as
giving
folks
this
kind
of
six-month
transition
period,
and
we
do
have
some
transition
guidance
out
there
on
moving
to
or
moving
from,
SP
P
PJs
to
the
at
P
and
P
scoped
libraries,
and
that's
something
absolutely
want
to
hear
feedback
on.
If
there's,
if
there's
points
we
can
highlight
better
or
that
we
miss,
that
would
make
things
easier
for
folks
moving.
A
We
want
to
hear
that,
please
let
us
know
and
we'll
do
our
best
to
get
that
document
or
add
additional
documentation
or
add,
perhaps
additional
videos
and
things
like
that
to
help
folks
move
so,
hopefully
I've
kind
of
addressed
some
questions.
We've
gotten
around
that
and
look
forward
to
folks
starting
to
make
that
transition
to
the
new
libraries
and
starting
to
get
feed
back
around
those
new
libraries.
A
I
did
want
to
talk
about
some
usage
tracking
for-
and
this
is
gonna,
be
really
SPP
and
pjs
is
making
up
the
the
bulk
of
these
numbers,
but
we're
well
into
a
billion
requests.
Pretty
steadily
now
we
had
a
little
drop
in
December-
that's
seasonal,
of
course,
with
the
holidays
and
everything,
but
other
than
that.
We've
maintained
about
a
billion
requests
now
since
September,
which
is
really
amazing,
to
see
and
then
down
there
in
the
bottom
right.
A
I
have
requests
by
month,
and
so
I
did
a
year
over
a
year
from
last
January
to
this
January,
and
you
can
see,
we've
had
some
phenomenal
growth
of
the
client-side
libraries
and
I
just
wanted
to
say
thank
you
to
all
of
you.
Who've
made
this
possible
out
there
in
the
community
because
you're
taking
this
work,
using
your
projects
and
then
providing
feedback
and
making
it
better
for
everybody,
so
really
appreciate
folks
using
it
as
well
as
the
feedback
we're
getting.
A
So
thank
you
and
these
numbers
are
just
from
SharePoint
Online,
so
it
doesn't
capture
anything
that
folks
might
be
doing
on-premises
so
just
to
kind
of
frame
those
a
little
bit
and
I
wanted
to
point
out.
This
is
a
new.
This
is
a
3d
object,
I've
added
to
the
slide,
I
just
I,
think
that
adds
a
lot
of
value
here
in
the
slide.
So
that's
a
3d
firework
object,
so
quick
update
here
on
the
office,
365
CLI,
so
new
release
I
believe
just
happening.
A
Hello,
how's
it
going
so
office,
365
office,
365,
CL
I,
had
a
new
release.
I
believe
just
happened
yesterday.
So
new
features
around
site,
scripts,
site
designs,
SharePoint
lists,
custom
actions
and
hub
sites.
There's
a
new
user
manual
was
published.
Alongside
that
new
release,
you
can
see,
there's
a
link
to
a
blog
up
there
at
the
top
blog
dot
master,
carts,
dots,
NL
office,
365,
CLI
o5o,
and
then
it's
included
in
the
official
documentation
for
the
docs
Microsoft
comm
stuff.
So
you
check
the
articles
out
there.
More
articles
are
coming
soon
and
Walt.
A
I
could
ask
me
to
thank
velan,
Robert
and
Daniel
for
contributions
in
this
latest
release.
So
thanks
guys,
I
really
appreciate
that
it's
fantastic
to
see
folks,
jumping
in
helping
all
these
tools
grow,
so
really
really
appreciate
the
contributions
from
you
three
on
the
CLI
and
the
contributions
everyone
does
across
the
P
and
P.
You
know
whole
ecosystem
every
month
and
then
also
nearly
doubled,
the
downloads
in
January
compared
to
December.
So
we
have
sorry
vase.
Oh
no.
A
So
we've
double
the
downloads
from
December
to
January,
so
great
again
to
see
the
usage
grow
alongside
the
library
capabilities
grow.
So
if
you
haven't
check
out
the
office
365
CLI,
it's
a
great
capability,
if
you're
unable
to
use
PowerShell
if
you're
on
a
Mac,
something
like
that
and
there's
a
lot
of
Help
Wanted
issues
tagged
in
there
in
that
repo.
If
you're
looking
to
get
involved,
that's
a
great
way
to
get
involved
as
well
and
I'll
pause,
because
I
think
visa
has
something
that.
B
Was
around
so
let's
be
100%
since
we're
SharePoint,
Online,
PowerShell,
PMP,
PowerShell,
absolutely
the
most
from
feature:
free,
ready
capability
and
now
the
PowerShell,
the
existing
Power
Cells
to
watch
SharePoint
Online.
What
we
are
providing
either
from
engineering
side
or
from
a
PMP
publisher
site,
are
only
working
within
a
Windows
platform.
Now
few
weeks
ago,
two
weeks
ago,
we
Microsoft
announced
PowerShell,
6.0
or
personal
core
and
that
actually
works
cross-platform.
B
So
we're
now
trying
to
figure
out
what
is
our
long
term
plan
also
related
on
SharePoint
Online
native
PowerShell,
but
also
that
the
community-driven
of
PowerShell-
and
it
might
be
at
some
point-
will
combine
some
of
these
things
together,
because
we
don't
want
to
have
a
competing
efforts
within
the
community,
but
for
time
being
office.
365
stay
alive,
absolutely
great
platform
and
tooling
for
configuring
office.
A
And
it's
also
there's
again:
it's
always
neat
to
learn
how
different
people
do
different
things.
So
there's
some
different
techniques
in
that
code
base
as
well,
if
you're
just
looking
to
learn
different
ways
to
sort
of
do
things
and
see
how
people
have
done
stuff,
there's
some
cool
stuff
in
the
code
as
well.
If
you
want
to
dive
into
that,
certainly
worthwhile
and
then
he's
waldek
is
following
the
hashtag
office,
365
CLI
on
twitter
and
as
well
there's
a
Gitter
channel
for
the
office.
365
CLI
work,
so
you
can
check
that
out
as
well.
A
Stepping
now
to
the
SharePoint
framework,
reusable
components.
This
is
a
set
of
reusable
components
that
work
inside
SharePoint
framework.
Hence
the
name,
but
we've
got
a
new
version
now
available.
So
1.2
was
just
released,
also
I
think
yesterday
or
the
day
before,
and
these
are
reusable
content
and
property,
paying
controls
to
help.
You
quickly
build
out
your
applications
with
a
very
rich
experience
and
a
very
sort
of
natively
branded
experience.
A
So
these
use
a
lot
of
this
sort
of
UI
fabric
features
so
stuff
like
that
to
help
your
applications
blend
into
SharePoint
as
much
as
possible
and
look
really
out
of
the
box
and
type
in
a
kms
SPF
SPF
X
controls
link
there
we'll
take
you
to
the
controls,
repo
I
want
to
say
or
the
documentation
one
of
those
two
plays
it'll.
Take
you
to
the
documentation.
Sorry.
A
Had
a
brain
meltdown,
there
that'll
take
you
to
the
documentation
around
using
these
controls
and
if
you're
you,
if
you're
doing
SharePoint
framework
development
and
you
need
to
have
these
field
controls,
in
example
your
property
panes.
These
are
really
fantastic
and
they're,
really
easy
to
use
and
really
drop
nicely
into
your
applications
and
so
updates
on
there.
So
new
major
release,
1.2
went
out
like
I
said
yesterday,
or
the
day
before
you
can
stall
those
those
are
also
within
the
at
PNP
scope.
A
So
at
PE,
p,
/,
SP
FX
react
controls
and
you
can
npm
install
that
as
as
standard
and
then
new
controls.
So
there's
a
field
controls
created
for
field
extensions
and
then
there's
a
new
iframe
dialog
control,
and
you
can
find
all
the
details
about
that
in
the
documentation
as
well,
then
some
fixes
a
theming
issue
with
the
web
part
title
control
in
dark
themes,
so
that
got
fixed
in
this
release
and
you
can
catch
up
on
the
webcast,
which
is
a
nice
introduction
and
overview
to
these
controls
at
AKA.
B
I
am
Patrick
just
elaborate
on
this
one,
because
there's
comments
around
office,
you
have
fabric
in
the
Andorian
window
and
all
of
that,
so
these
controls.
So
there's
two
sets
of
controls.
There's
the
property
being
controls,
they
absolutely
use
office
to
our
fabric
to
render
the
things.
So,
obviously,
my
fabric
react
is
not
a
share
point
of
where
these
controls
are,
and
that's
really
the
abstraction
layers
between
the
initiatives
now
in
the
future.
It
might
be
that
we
are
even
combining
this
stuff
with
office.
B
You
have
appropriate
controls
at
some
level
and
all
will
figure
out.
How
do
we
plan
this?
But
for
time
being?
This
is
a
own
initiative
under
the
ship
on
deaf
ecosystem
umbrella.
Now
the
office
you
are
fabric.
We
are
internally
in
engineering
there
to
try
and
figure
out.
How
do
we
make
that
more
robust,
more
reliable,
more
easily
usable
and
that's
gonna
then
impact
across
the
the
sharepoint
ecosystem,
not
only
on
SharePoint
but
also
on
other
platforms
as
well,
but
more
information
on
that
one.
B
A
A
C
You
first
things:
first
quick
introduction:
my
name
is
Rodrigo
Silva
I'm,
an
independent
SharePoint
developer
and
Technical
Architect
and
I'm
currently
working
for
a
company
named
storm
in
Ireland's.
So
basically
we
well
we.
The
solution.
I'm
going
to
present
today
is
a
proof
of
concept
that
we
developed
for
one
of
our
clients,
because
they
wanted
to
keep
ability
to
tag
news
articles
with
metadata,
as
we
previously
used
to
do
with
page
layouts
and
the
content
types
approach.
C
So
for
that
and
inspired
in
the
part
B&P
part
in
the
pack,
because
I've
used
it
extensively
and
I
quite
liked
it
so.
We've
created
a
separate
site
collections,
called
infrastructure
where
we
store,
where
we
have
a
document
library
to
store
the
templates
and
messages
to
send
messages
to
the
queue
storage.
So
I
could
potentially
call
directly
the
the
flow
via
the
the
web
part,
but
I
actually
like
to
track
it.
So
I
decided
to
have
a
list
to
have
all
the
all
the
messages
that
are
going
to
be
cute.
C
C
Then
we
have
an
azure
function,
it's
going
to
get
two
templates
and
finally,
it's
going
to
apply
provisioning
and
to
a
little
bit
for
workaround,
because
when
it
applies
provisioning
of
a
page,
the
Constance
I,
please
side
page
so
I
then
go
and
change
the
content
type,
but
you'll
see
them.
Okay,
let's
see
some
action,
then
okay,
so
this
is
normal.
This
is
normal
and
out-of-the-box
communication
side
up.
First
of
all,
let
me
just
so
as
as
mentioned,
we
have
the
cue
messages
here.
Empty
now
and
I
have
I.
C
Have
the
templates
just
three
templates:
one
will
be
Department
News,
global
news
and
team
news.
They
have
a
message
and
scope.
Scope
is
because
I
was
thinking
if
I
was
going
to
expand
this
or
not
supervision
sites
as
well,
but
no
I
just
think
it
doesn't
make
much
sense
anymore,
part.
Whatever
it's
still
there,
then
we
have
the
own
page,
the
homepage
and
that's
just
a
discreet
button
here
to
create
news
and
when
I
do
it,
I
have
the
have
the
templates
available.
So
I
will
just
select
global
news.
C
Okay,
so
I'm
going
to
create
anyway.
This
is
a
proof
of
concepts
or
nothing,
visual,
it's
going
to
happen
while
I
create
but
I'll
leave
the
function
here
running
and,
at
the
same
time,
I'm
going
to
show
a
little
bit
of
the
functions
code.
So
okay,
so
basically
this
is
quite
simple,
so
we
we
call
the
provision
method
method,
then
we're
going
to
get
templates,
it's
executing
cool.
So
basically,
basically
we
go
in
hello.
C
Oh
okay,
so
basically
we
connecting
to
the
infrastructure,
side,
side,
collection,
we
get
into
templates,
XML
provider
and
then,
basically,
after
getting
the
template,
we
going
to
apply
the
template,
which
is
basically
connected
targets,
I
pre
priests
and
their
things.
But
then
we're
going
to
apply
the
provisioning
template
and
that's
the
workaround,
because
I
then
get
the
template,
get
the
cage
and
change
the
content
type,
so
I
think
it's
executed.
C
Good
I
did
pray
to
the
gods
of
the
presentations.
So
let's
see
the
pages,
so
here's
the
page
and
let's
see
the
properties.
So
as
you
can
see
the
content
type,
these
storm
news-
oh
I,
didn't
mention
so
we've
created
a
side
column
you
connected
linked
to
to
Twitter
and
Ted,
and
basically,
we've
created
a
Content
site
that
you
know
is
from
from
side
page
and
that's
their
constant
is
called
strong
news.
So,
as
you
can
see,
we
have
fair
enough.
C
We
have
the
the
news
category
here
and
another
cool
thing
now
is
when
I
click
on
a
page.
Okay,
so
there's
already
two
web
parts.
One
is
standard
text,
it's
just
to
confirm
that
we
applied
the
right
template
and
the
other
one,
as
you
can
see,
is
news
category.
So
speaking
about
reusable
controls,
I
have
that
as
well.
So,
basically,
what
we
do
is
we
edit
the
properties
of
the
webparts
and
we'll
go
here.
It's
connected.
C
So
let's
see
business
and
curiosity,
dun
dun
and
let's
just
go
back
here
and
refresh
and
now
it'd
be
cool
if
there
was
other
one
selected,
fair,
nuff,
it's
business
and
curiosity.
So
it's
it's
tagged.
So
we
can.
We
can
now
basically
use
it
on
one
search
or
develop
a
develop
any
web
parts
aggregate
this.
C
Okay,
so
we
basically
have
we
basically
have
two
web
parts
here
right,
so
one
is
the
one
I
showed
first
is
the
one
that
does
the
provisioning,
nothing
really
complex.
So
basically,
that
is
a
few
event
unless,
but
this
is
the
main
thing
is
basically
when
I
show
more
though
I'll
just
get.
The
available
templates
should
have
done
this
in
the
start,
then,
when
we
create
the
news
item,
we
basically
we
we
create
the
news
with
all
the
older
imports
and
information
with
answering.
C
We
then
pass
Jason
and
our
the
message
to
to
to
the
list,
and
then
we
have
the
other
web
part
which
is
to
going
to
show
here,
because
we
just
talked
about
it
so
fair
enough.
We
have.
We
have
the
reusable
consoles,
in
this
case
the
term
pika
and
basically,
what
I
have
is
whenever,
whenever
the
property
has
changed
so
I
have
I.
Have
this
event
here.
C
So,
whenever
the
properties
change,
I'll
call
then
call
the
set
page
metadata
I'll
verify
if
basically
I
compare
the
selected
terms
against
the
ones
in
the
page
and
if
it
has
changed
and
goes
and
updates
and
I
believe,
don't
know
if
I
was
too
fast
or
not,
but
we
do
have
time
for
Kiwi
and
I.
Think
that's
it
for
me.
B
C
B
C
Basically,
I'll
generate
a
query,
but
this
just
for
monitoring
purposes
and
the
message
is
in
in
JSON
format.
So
basically
I
have
all
the
necessary
jason
here.
You
know
and
then
I
have
I
have
a
flow
attached
to
this
library.
I
can
I
can
show
these
three
simple.
It's
just
whatever
an
item
is
habits.
I'll
then
add
this
message
in
particular
to
the
message:
queue
yeah.
B
C
B
I
think
this
is
this
is
an
interesting
discussion
point
as
well.
So,
in
your
case,
technically,
obviously,
in
the
you
know,
optimal
world,
the
the
new
page
could
up
being
created
directly
in
the
client-side
web
part.
Now
the
reason
and
brought
correct
me
if
I'm
wrong.
The
reason
why
using
flow
is
that
you're
able
to
bypass
the
processing
to
the
usher,
storage
or
sorry,
an
external
process
which
is
then
using
the
BMP
provisioning
engine,
because,
yes,.
B
And-
and
why
is
that?
Well
because
we
do
not
have
client-side
version
of
the
PNP
provisioning
engine,
because
that's
actually
super
super
super
super
complex
engine
and
implementing
that's
right
now
in
typescript
or
in
to
be
supported
in
client-side,
is
really
really
really
time
consuming
solution.
There's
some
initiatives
and
discussions
around
that,
but
woke
up,
welcome
back
on,
will
do
in
the
future
yeah.
C
You
understand
correct
phase,
so
basically
I
could
have
created
the
page,
but
then
I
would
I
would
create
the
page
instantly
and
then
I
would
have
to
go
and
are
the
web
parts
and
then
so,
basically,
here
it's
whenever
the
page
is
provision.
He
comes
already
with
everything
on
it,
everything
we
need.
He
comes
already
yeah.
Basically,
it's
basically
that
that
was
the
option.
Why
make.
B
C
And
another
thing
this
is:
we
we
did
opt
one
having
the
difference
in
places
where
I
forgot
to
mention
so
basically
the
one
one
of
the
requirements
of
this
particular
client
was.
They
wanted
to
have
a
centralized
way
to
create
news,
but
they
wanted
the
news
to
be
saved
in
different
site
collections
according
to
its.
So,
if
you
watch
team
news,
you
would
go
to
recycle
X
I
mean
yeah.
So
then
we
can
control
that
quite
easily
with
a
with
a
nature
function.
Yeah.
B
A
B
Coming
back
on
the
road
stay,
absolutely
awesome
demo.
So,
like
said
it's
a
proof
of
concept,
all
right,
but
I
think
it
evolved
to
thinking
on
how
we
can
create
standardized
pages
and
standardized
sites.
Technically,
you
can
do
that
already
today,
with
the
existing
API
sand
with
the
PNP,
PowerShell
and
PMP
provisioning
engine,
you
can
actually
define
your
pages
and
sites
in
a
structural
way.
B
Now
it's
still
the
PMP
powershell,
it's
a
PowerShell
driven
the
MP
MP
provisioning
engine
is
a
managed
code,
trubin
driven
because
there's
hundreds
of
thousands
of
lines
of
code
behind
us
that
the
engine
and
that's
why
it's
not
really
as
optimal
of
maybe
having
the
modern
page
handling
in
a
client-side
but
but
again,
I
think
the
solution.
Design
is
really
nice
and
there's
options
on
on
polluting
that
to
be
more
intrusive,
treyvion
as
well
orange
user
frame,
clear
as
well.
B
So
once
the
Chasen
toaster
dashiki
is,
as
you're
running
the
PowerShell
to
create
a
page
so
and
answering
an
interest
case,
but
it
could
be
a
power
or
skewed
PC
sharp,
so
it's
either
way,
but
there's
a
PNP
provisioning
engine.
The
remote
provision
against
and
for
both
PowerShell
based
and
also
c-sharp
based
operations
in
wrote
is.
Are
you
using
just
out
of
curiosity?
Is
the
PowerShell
or
c-sharp.
B
Thanks
yeah
so
and
and
that's
a
matter
of
a
preference
as
well.
If
it's
c-sharp,
it's
just
you,
you
have
more
control
on
the
process
potentially,
but
to
be
fair
with
the
natural
function,
the
PowerShell
cue
act
recur.
Is
there
as
a
preview
implementation
as
well,
so
that
should
be
should
be
working
as
well.
B
Now
the
the
link,
what
Ryan
is
sharing
is
around
extending
the
site
designs
inside
script,
using
two
BMP
provisioning.
It's
similar
kind
of
thinking.
It
is
actually
90%
of
the
scenarios
the
same
except
that
in
rods
case
he
is
adding
or
initiating
the
request
from
a
webpart,
but
the
back
end
is
exactly
the
same:
yay
Patrick
you,
it
works
awesome.
B
B
A
A
couple
things
I
wanted
to
show
some
new
features,
we're
adding
here
to
the
at
PNP
libraries
and,
like
we
talked
about
earlier,
these
will
also
be
transferred
into
the
SPP
and
PJs.
For
now.
The
first
thing
I
wanted
to
show
is
actually
over
here:
we've
added
a
method
to
get
all
the
items
in
a
list,
and
this
is
something
that
was
requested
a
lot
enough
that
I
finally
broke
down
and
added
it.
This
is
something
I
do
not
encourage
you
to
use
often
because
it's
going
to
get
all
the
items
in
a
list.
A
B
A
Zoom
it
how's
that
hey
Gabe,
better
yeah,
all
right
so
to
get
all
methods
so
we're
gonna
run
this
real,
quick
and
we'll
see
this
spin
up
and
I'm
gonna
get
my
items
dot
length
back
out
of
this
collection,
so
this
is
gonna
return,
an
array
of
any
because
we
don't
really
know
what
we're
gonna
get
back
from
there,
but
you
could
always
type
it
later,
but
this
will
be
our
list
data
and
so
we're
gonna
see
this
come
back
and
we're
gonna
end
up.
A
A
So
now
we'll
run
apologies
for
that.
We
were
getting
ahead
of
ourselves.
So
now
this
will
spin
up
and
we'll
get
all
the
items
out
of
that
list
and
we'll
see
how
many
we
got
and
then
we'll
talk
about
a
couple
of
options
with
using
this
method.
So
we've
tried
to
to
make
it.
So
it's
still
plays
into
that
fluent
API
that
we've
built.
So
you
can
see
it
takes
a
little
bit.
A
You
can
see
requests
going
to
another
request,
we're
doing
this
in
pages
and
by
default
our
page
size
is
2,000
and
we've
got
6,000
846
items
in
that
list
and
that
took
a
little
while
to
operate.
Obviously
we
had
a
few
different
requests,
but
some
of
the
stuff
you
can
do
here-
we've
made
it
so
select
works.
If
you're
gonna
get
all
the
items,
it
makes
a
lot
of
sense
to
filter
down
the
field,
your
brain
back,
so
in
this
case
we
can
just
do
title.
A
Filter
will
also
work,
but
it's
not
going
to
work
for
large
lists.
A
lot
of
the
time.
You're
gonna
get
errors
back
on
the
list,
threshold,
size,
etc.
I'm
sure
we've
all
seen
those
but
filter
will
work.
So
if
you
have
a
list
of
say,
3,000
items
and
you
want
to
do
a
filter,
get
all
the
filter,
command,
will
work
and
then
as
well.
You
can
use
top
to
change
the
page
size
that
that
is
gonna
request.
The
items
in
so
top
will
do
that.
A
You
can
also
pass
to
the
get
all
method
itself,
the
page
size
you
want
to
use,
and
if
you
were
to
do
both
this
top
will
take
precedence.
It
will.
It
will
use
this
number
over
this
number.
So,
if
I
make
this
one
thousand
and
this
4,000
will
use
4,000
and
the
rationale
behind
that
is
simply
I
had
to
make
it
so
I
picked
one.
But
this
will
get
us
all
the
all
the
items
in
the
list
and
if
we
run
that
again,
I'll
just
show
you
real
quick.
A
A
Couple
yeah
a
few
blog
posts
about
it
as
well
out
there.
So
you
can
see
we
were
able
then
to
just
do
this
in
two
requests,
because
our
page
size
was
now
4000
and
you
can
see.
We
were
also
passing
the
select
of
the
title
there.
So
we've
got
in
two
requests:
we've
got
our
6,000
items
and
that's
a
little
bit
faster.
So
that
gives
you
a
little
bit
of
control
over
the
get
all
so
a
new
method.
A
So
if
I
get
my
title
and
we'll
just
do
that,
to
get
a
list
and
I
do
the
items
and
I
do
it
get
and
then
nothing
new
there,
but
by
default
now
all
our
collections
so
items
as
a
collection
fields
would
be
a
collection
content
types
as
a
collection
are
gonna,
come
back
as
an
array.
So
in
the
past
they
were
just
any
and
you
would
have
to
type
it
to
an
array,
but
now
they're
gonna
be
an
array
of
any
so
we've
updated.
A
So
all
those
collection
methods
are
gonna,
come
back
typed
correctly
now
to
be
arrays,
as
opposed
to
just
being
straight
any
to
help
out
again
with
folks
in
a
little
bit
of
the
typing
and
to
make
it
a
little
bit
easier
to
use
those
collection
methods
so
wanted
to
mention
that
and
that's
across
all
of
the
collection
classes
have
that
change
now.
So
that
was
something
very
happy
to
do
that
have
been
requested
in
the
past.
B
B
A
Yes,
it
should,
it
should
work.
You
know
in
terms
of
the
index.
Columns
and
things
in
the
large
lists
should
follow
all
the
standard,
OData
filtering,
because
really,
at
the
end
of
the
day,
we're
just
passing
that
in
as
the
filter
parameter
yeah.
So
so
the
only
I
want
to
show-
and
this
is
very
much
a
work
in
progress.
So
what
I'm
gonna
show
you
works,
but
not
much
past
this
yet,
but
it
will
be
for
the
next
release.
A
So
one
of
the
things
we've
had
an
outstanding
issue
for
a
long
time
was
the
ability
to
add
client-side
pages
so
modern
pages
to
a
site
through
the
the
JavaScript
libraries
and
I
do
want
to
caveat
this
a
little
bit
if
you're
doing
real
hardcore
provisioning.
The
way
to
do
that,
in
my
opinion,
is
still
the
managed
code.
Still
the
you
know,
PowerShell
those
established
the
provisioning
engine.
A
Those
are
really
the
ways
to
do
it
for,
for
all
the
things
we've
talked
about
in
the
past
right
time,
outs
permissions,
all
that
sort
of
stuff,
but
I
think
it's
a
nice
capability.
If
you
wanted
to
have
a
web
part
with
a
button
that
adds
a
new
page
or
something
like
that,
so
got
this.
We're
gonna
go
ahead.
I'm
just
gonna
run
this
while
I
talk
through
the
code-
and
the
first
thing
we
do
is.
This
is
just
a
show.
I've
added
support
to
get
the
clients
webpart.
A
So
that's
just
a
simple
rest
call:
that's
gonna
go
out
and
get
all
the
available
client-side
web
parts
in
in
this
particular
web
I'm
not
doing
anything
with
it
yet
you'll
note,
but
I'm
just
showing
you
can
get
that
stuff
back
and
you'll
get
back
a
nice
array
of
all
the
parts
eventually
you'll
be
able
to
add
those
in
as
controls
onto
the
pages.
So
you
can
see
we're
done.
We've
created
our
page
and
we'll
look
at
that
here
in
a
second.
A
The
next
call
here
is
to
add
a
client-side
page
and
the
only
parameter
I
have
to
give
it
or
that
I'm
going
to
give.
It
is
the
file
name.
So
this
is
the
aspx
file
name
I'm,
just
using
nest
with
a
random
string
after
it.
Just
as
you
know,
I've
been
doing
a
lot
of
these
and
I.
Don't
think
you
have
to
keep
changing
the
names,
but
so
you
can
just
add
a
client-side
page,
and
that
method
gives
you
back.
A
The
page
object
that
just
got
created
and
so
client-side
page
we'll
take
a
look
at
that
in
just
a
second
and
then
we
can
add
a
section
to
that
page.
We
can
add
a
control
to
that
section
and,
like
I
said,
this
is
a
very
controlled
demo.
This
is
all
that
works
right
now,
but
I'm,
adding
a
client-side
text,
control,
here's
my
text
and
then
saving
the
page
will
persist.
Our
content
updates
back
to
the
server.
So
if
I
grab
our
site
here,
I'm
gonna
refresh
this.
A
At
some
point,
I
was
testing,
apply,
theme
and
never
gone
back
and
put
a
different
theme
up
here
and
also
make
sure
visually
I
know
I'm
in
my
site.
So
when
I
start
deleting
things,
that's
you
know
very
clear,
but
you
can
see
here's
our
test
page
here
is
my
text,
so
we've
got
that
added
on
the
page.
I
can
edit
this
and
come
in
and
make
changes.
So
we've
correctly
created
our
page
and
correctly
added
our
web
part
in
here.
So
I
can
discard
changes,
save
and
close.
A
A
So
this
is
using
the
Cheney
and
you'll
see
we're
checking
to
see
if
the
page
exists
or
adding
it
as
a
template
file
and
then
we're
updating
the
item
with
the
client
side,
page
properties
as
needed
to
make
that
into
a
modern
page,
and
then
we
we
have
classes
then
for
sections
and
columns
and
controls
I
won't
dive
into
this.
This
is
all
work
in
progress,
so
this
really
isn't
anything
to
really
show
off
yet.
B
When
we
do
know
that
we
went
to
a
few
minutes
of
the
schedule
now,
whatever
what
we
can't
showed
today
is
the
reason
why
that
worked
all
right
and
adding
a
web
part
of
in-house,
because
that
is
to
use
in
the
BMP
provisioning
engine
now.
What
patrick
is
shown
here
could
be
adapted
by
Roderick
in
his
solution,
and
they
would
be
technically
no
need
to
use
than
the
flow
and
remote
service
whenever
there's
support
for
these
things
would
be
added
on
the
on
the
platform
right.
A
Yep,
absolutely
and
again
with
just
that
caveat
that
is
permissions,
and
then,
if
you
you're
trying
to
create
a
bunch
of
stuff,
there
might
be
time
out.
Somebody
closes
their
browser.
All
that
sort
of
things
I
think
it's
a
nice
capability.
If
you
do
just
want
a
quick,
easy
way
to
add
a
client-side
page
and
then
put
a
couple
of
web
parts
on
it.
I
think
it'll
be
a
nice
thing
for
folks.
A
So
we
saw
Rodrigo's
demo,
which
the
full
title
was
creating
news
and
edit
metadata
using
SPF
x,
webparts
flow
as
your
functions
and
a
PNP
provisioning
engine,
a
really
awesome,
end-to-end
demo,
and
thank
Rodrigo
for
doing
that.
We've
been
trying
to
get
them
on
the
calendar
here
for
a
few
weeks,
so
wonderful
stuff,
no
time
for
Q&A
apologies
for
that.
We
went
a
little
long
again
this
week,
but
I
think
it's
fantastic
for
the
content
we
had.
A
A
Remember
at
learn,
reuse
and
share.
We
appreciate
everybody's
participation,
everybody's
feedback,
Thank
You
Rodrigo,
for
your
demos
today.
Thank
you
face
up
for
the
great
updates.
Thank
you.
Elio
and
wall
beck
for
the
work
on
the
office,
365
CLI
and
the
reusable
controls,
as
well
as
everybody
in
the
community,
contributed
to
all
our
projects.
So
thanks,
everyone
have
a
great
rest
of
your
week
and
we'll
talk
soon.
Bye,
bye,.