►
Description
Recording of the SIG from 21st of September. Detailed agenda and covered topics from MS Tech Community. You can download invite to bi-weekly special interest group call from http://aka.ms/sppnp-core-sig-call.
A
Good
we're
hitting
on
the
hour.
So,
let's
see
we
didn't
do
any
any
marketing
today,
for
this
particular
call,
and
so
do
much
really
well
to
do
the
reasons
that
super
super
super
busy
with
the
Ignite
stuff,
because
we
need
to
get
stuff
ready
for
next
week
as
well,
which
also
means
that
there's
not
a
massive
amount
of
things
which
we
are
new
things
which
we
can
actually
talk
about
today.
A
So
I
can
show
you
something
which
is
part
of
a
larger,
let's
say
demo
set
up
for
next
week,
but
I
can't
go
to
more
specifics
with
that.
One
related
on
more
on
experience
and
everything
else,
and
we
kind
of
talked
about
and
I'm
going
to
do,
a
quick
demo
also
on
the
new
season
capabilities
which
went
live
last
Friday.
But
let's
do
a
quick
set
up
on
other
things
on
the
and
agenda
and
Oberth.
Let's
make
sure
that
if
there's
any
random
questions
which
we
want
to
go
through,
we
can.
A
We
should
have
plenty
of
time
today
for
KO'ing
audio
and
we
can
stop
earlier
today,
if
needed.
So
we'll
have
the
miscellaneous
announcements
random
stuff.
What
I
collected
on
slides
and
then
two
different
demos
I'll
do
them
both
today,
because
we
didn't
actually
explicitly
prepare
significant
stuff
for
this
week.
Do
upcoming
ignite
and
the
ignite
is
a
massive
developers
day
for
SharePoint,
because
this
and
spring
announcements
are
the
main
things
for
us
in
a
year,
so
typically
in
spring
I
think
this
time
it
was.
It
was
around
15
of
May.
A
Last
time
it
was
4th
of
May.
We
released
those
videos
and
explained
what's
coming
up
and
and
then
during
during
summer
time,
we're
polishing
that
stuff
up
and
hopefully
make
it
ready
to
go,
live
in
ignite
some
of
the
stuff
which
I
saw
in
the
spring
videos
will
go
live
when
ignited.
Some
of
the
stuff
will
go
slightly
later.
A
A
Well,
that's
the
ignite
is
a
massive
thing
fast,
so
and
I
do
apologize,
that
we
haven't
been
able
to
prep
humongous
amount
of
additional
material,
but
there's
time
for
Q&A
and
let's
see,
if
there's
good
questions,
we
can
randomly
talk
about
things
which
we
can.
Obviously,
if
it's
a
question
around
future
stuff,
I
can
talk
about
some
of
that.
Yet
now
on
the
weeknight,
if
you're
coming
to
ignite,
we
do
have
four
different
specific
preconceptions.
A
A
Boy
indeed,
let's
thank
you.
So
these
are
the
specific
sessions
on
the
width
of
75
minutes
in
ignite.
So
if
you
come
into
ignite
and
you
want
to
be
up-to-date
on
what's
happening
on
the
SharePoint
framework
and
what
a
customization
these
are,
the
sessions
where
you
want
to
stop
by
will
start
then
has
the
session
on
Tuesday
around
shape
on
development
in
enterprise.
A
This
is
basically
just
200
level
session
walking
through
what
is
the
new
stuff
what's
coming
up
and
what's
in
the
q4
rest
of
the
year,
we
have
a
lot
of
stuff
that
the
list
is
actually
surprisingly
long,
which
will
be
coming
either
out
on
ignite
or
coming
out
by
end
of
the
year
and
and
then
is
walking
through
all
of
that
stuff,
so
you'll
be
up-to-date
on
on
what
we
are
promising
to
what
happen.
The
second
session
on
the
slide
is
the
advancing
SharePoint
developer
community
I'm,
not
100
titles
of
that
session.
A
But
obviously
this
is
the
the
once
a
year
session
where
we
culture
and
more
details
on
what
is
a
SharePoint
BMP.
What
has
happened?
This
is
not
a
round
summary
only
as
a
summary.
We
will
have
cool
announcements
and
a
new
community
initiatives
announced
on
that
session
as
well
stuff
which
you
can
reuse
immediately
after
that
session
or
actually
during
next
week,
within
your
projects
to
be
more
productive.
A
So
we
are
expanding
our
reusable
components
and
controls
model
and
we
are
expanding
few
other
things
as
well
and
in
that
session,
we'll
also
talk
about
the
modern
intent,
customization
story
for
modern
SharePoint
sites
and
then
there's
the
let's
build
SharePoint,
let's
build
with
SharePoint
session
webparts
extensions
and
much
more
old
story.
Further
for
the
ship
might
be
in
possession.
A
It's
gonna,
be
me,
and
urban
man
Hunan
versus
urban
is
in
a
call
as
well
for
the
next
session,
let's
build
for
SharePoint
and
that's
going
to
be
Luca
from
engineering
and
then
Paul
of
the
LRC
from
the
MVPs
side
and
that's
around
more
on
building
stuff
using
webparts
concert,
webparts
and
extensions,
and
going
through
the
extension
details
and
what's
coming
up
and
what
has
been
announced
and
all
of
that
and
I
can't
confirm
that
extensions
will
be
announced
next
week.
But
obviously
I
can
deny
that
either.
A
So
you
can
make
your
own
conclusions
out
of
that
statement.
The
ga4
extension
has
been
bending
for
quite
a
long
time,
but
I'm
not
gonna,
explicitly
say
that
that's
gonna
happen
next
week
see
I'm
an
ex
consultant.
I
know
how
to
avoid
that
trap,
no
just
a
joke
and
then
the
last
session
building
more
and
SharePoint
experiences
best
practices
from
Microsoft
for
developing
guess.
It
depends
indeed
for
developing
with
SharePoint
framework.
This
is
a
session
where
originally
we
were
supposed
to
have
checks
and
the
wall
deck.
A
Unfortunately,
wall
deck
has
to
cancel
his
trip
on
ignite
so,
while
the
unfortunately
will
not
be
an
ignite,
so
Jax
is
gonna.
Take
care
of
that
one
on
a
Friday
I
think
around
noon.
That's
one
of
the
last
sessions
on
day
on
date,
night
on
Friday,
but
if
you're
interested
on
the
on
the
shape
and
framework
and
SharePoint
development
in
general,
these
are
absolutely
the
sessions
to
buy
to
see
where
we're
heading
or
what's
actually
happening,
because
SharePoint
framework
is
nowadays
also
in
on-premises.
So
it
is
an
immersive
deal
for
us.
A
A
You
have
fabric
people
and,
and
obviously
please
drop
by
if
you
have
any
questions
around
anything
on
the
SharePoint
development
or
or
anything
around
of
well
ship,
one
development
in
on-premises
or
in
cloud
I'm
more
than
happy
to
help
on
those,
and
we
also
have
an
office
pre
day
as
well.
Now,
let's
move
into
the
other
topics
as
well:
I'm,
just
double-checking
that
I'm
double-checking
that
I'm
not
missing
anything
from
the
from
the
a.m.
A
discussion,
you're
starting
to
speak
like
some
of
the
American
politicians,
yes,
Cynthia,
Thank,
You
Dean
working
in
the
American
company
does
have
its
own
impact
cool
thanks
Patrick.
So
let's
move
into
the
actual
topics
and
and
I'll
do
a
like
mentioned
I'm
going
to
do
a
few
demos
as
we
move
along
today,
and
then
we
should
have
plenty
of
time
for
Q&A.
If
there's
any
Q&A
questions,
let's
see
now
one
of
the
things
what
we
released
pretty
recently.
Typically,
we've
been
releasing
the
client-side
object.
Model
version
on
a
monthly
basis
now
do
ignite.
A
We
needed
to
flip
slightly
the
schedule.
So
in
August
we
released
a
new
version
on
the
mid
August
and
also
in
September
we'll
release
the
latest
version
on
last
Friday.
I'm,
not
sure
if
you
followed
up
on
this
one
in
the
social
media,
but
there
is
actually
super
cool
new
capabilities
as
part
of
the
latest
client-side
object
model
version
for
shipment
online
and,
more
specifically,
around
a
diversion,
versioning
information
access.
So
using
the
latest
version
you
can
actually
access
the
pre.
A
Add
the
data
of
a
SharePoint
list
items
in
the
previous
version,
so
you
can
actually
go
back
in
time
to
the
first
version
of
a
SharePoint
list
item
and
have
a
look
on
what
was
the
value
of
that
whatever
field
and
get
that
out
from
SharePoint.
If
you
need
to
do
so,
and
that
has
been
a
super
super
super
classic
request,
people
tend
to
have
that.
There's
a
business
requirement,
two
reasons
or
another,
so
that's
finally
exposed
in
the
CSM
side
as
part
of
this
one,
we
also
released
well.
A
At
least
we
provided
guidance
on
this
one.
This
has
been
actually
available
for
a
while
how
to
get
the
previous
version
of
files
from
SharePoint
Online.
So
as
an
example,
if
you
need
to
export
all
of
the
let's
say,
Word
documents
from
a
document
library
and
their
previous
version,
you
can
easily
do
that.
So
there
is
an
API
to
do
that,
using
the
client-side
object
model
and
writing
many
to
Whitman
its
code.
Technically
there
there
should
be
I,
haven't
actually
double-checked
api's
to
make
this
happen
also
in
the
rest.
A
But
our
rest
story
is
slightly
more
complicated,
so
to
say,
because
the
documentation
is
pretty
horrible,
it's
not
exposed
using
spectra
files,
and
we
know
all
of
these
challenges
which
might
have,
if
you're
more
familiar
and
wonderful
like
to
use
rest
as
well.
Oh,
there
is
a
rest
api
call
good,
so
someplace
confirming
at
least
some
of
it
and
version
information
available
and
a
rest.
Yes,
that
is
available
if
it's
available
in
the
rest
of
ready
right
now,
this
additional
API
should
be
exposed
there
as
well.
A
No
our
documentation
on
the
rest
side
is
pretty
horrible.
We're
trying
to
get
that
sorted
out
and
we've
been
working
on
that
one
for
quite
a
long
time.
There's
multiple
complications
on
that
and
I
do
apologize
on
it,
so
we're
trying
to
get
that
solved
sooner
or
later,
but
for
now
and
for
this
particular
call,
let's
concentrate
on
the
season
a
side
of
the
story
and
then
try
to
figure
out
the
future
risk
story,
hopefully
sooner
or
later
good.
A
So
let's
actually
have
a
quick
look
on
this
one.
So
what
I've
done
here
is
that
I
in
the
plot
post,
which,
where
we
announced
that
in
the
drafter
of
Scone
I
copied
some
code
from
this
small
demo,
but
I
can
actually
show
you
this
directly
from
my
UI
or
from
my
computer.
So
let
me
share
my
screen
and
let
me
walk
through
what
are
we
actually
have
here?
So
somebody
needs
to
confirm
whenever
the
screen
sharing
is
working
properly,.
A
Thank
You
Bert,
so
let
me
actually
go
to
one
of
my
sites
so
apparently
using
my
own
tenant
for
this
demo
and
which
is
absolutely
fine.
So
right
now
we're
in
a
my
tenants
last
sites
last
theme
site
I,
do
have
this
versioning,
add
library
here
which
has
a
one
document
I'm,
making
this
as
simplistic
as
possible,
so
you
can
easily
say
the
values
and
and
the
behavior.
So
in
this
document
there
is
a
document
we
can
actually
go
to
the
document.
Let's
do
a
small
modification
apparently
open
already
in
there.
A
A
There
we
go
so
now
we
updated
that.
Let
me
click
that
one
okay.
Back
on
on
the
library,
we
can
say
that
it
was
just
updated
few
seconds
ago.
We
can
absolutely
also
update
this
additional
values.
So
if
I
select
that
document
in
modern
view,
I
can
go,
for
example,
another
text
or
text
field
and
update
this
one
seek
call
updated
value,
so
we
can
actually
see
to
get
access
on
those
items
as
well.
A
Now
we,
if
we
scroll
down
here
slightly,
we
can
see
that
there's
multiple
versions
of
this
item
and
I
think
we
should
get
the
diversion
history,
so
we
can
actually
see
in
a
modern
UI,
which
is
good.
We
can
say
that
there's
actually
ten
versions
of
the
after
document.
These
two
are
the
ones
which
I
just
did
so.
A
A
This
I
will
flip
to
Visual
Studio
2017
I
do
have
a
already
a
reference
in
the
new
code
packages
quickly,
showing
that
so
the
latest
version
of
the
new
kit
package
it's
now
actually
coming
from
a
local
source,
but
just
as
well
it
is
exactly
the
same
version
which
has
been
released
in
the
nougat
as
well.
So
sixteen
one
and
six
nine
zero
six,
it's
the
exact
version
and
it's
the
max
of
SharePoint
Online
season.
A
So
that
has
been
added
as
a
reference
to
my
solution,
and
that
means
that
I
can
then
use
these
advanced
new
capabilities
within
my
my
code.
So
the
code
itself
is
relatively
simple:
I'm
gonna
be
the
breakpoints
here,
so
we
can
actually
walk
through
what's
happening
and
we
can
start
executing
this
one.
So
it's
gonna
conduct
on
that
site
using
the
client-side
object
model,
and
then
we
are
actually
getting
access
on
the
document.
Library,
with
the
with
the
name
version
test
dog,
so
just
double
checking
that
one.
A
It
is
actually
version
test
dog
because
it's
me
naming
things
in
a
in
a
weird
way,
so
we're
loading
that
we're
also
I
need
them.
Id'd,
one
which
I
know
that
it
there
is
Aida
might
a
one.
You
could
just
as
well
scroll
down
all
of
the
items
in
a
document
library
and
then
start
putting
the
values
from
there
we're
interested.
Also
on
the
version
information
we
interested
on
a
file,
we're
interested
on
the
file
versions
and
then
we're
loading
all
of
these
and
doing
the
execute
query
to
get
everything
loaded.
A
So
now
in
the
next
piece,
there's
kind
of
a
two
sections
here
so
I
can
actually
access,
and
this
is
actually
the
new
part
is
to
field
values.
So
I
can
access
the
individual
versions,
and
now
we
have
this
field
values,
collection,
exposed
and
I
can
double
check
that
if
the
text
field
has
a
value,
I
can
actually
get
the
version
value
and,
as
you
can
see,
I
can't
actually
zoom
this
properly.
It
is
saying
sick
call,
updated
value,
that's
the
value
for
that
one.
That's
the
current
version
of
the
item.
A
A
It,
however,
has
not
been
properly
documented
and
we
do
apologize
and
that
one
that
that
is
technically
a
resourcing
challenge
always
but
I
can
access
the
file
versions
and
with
the
file
versions,
and
we
have
an
open
point
or
a
stream,
and
with
this
one
we
can
do
something
as
simple
as
let
me
open
up
side-by-side,
let
me
actually
get
rid
of
the
my
previous
version
of
the
documents.
I
can
just
save
that
file
directly.
A
We
go
and
now,
if
I
open
up
I'm,
not
sure
actually,
which
one
of
these
is.
The
latest
version.
Is
that
the
oldest
version,
or
is
it's
the
latest
version?
This
is
actually
the
latest
version,
so
we
can
see
the
updated
sequel
value
which
were
updating,
that's
actually
pretty
cool.
So
we
are
basically
now
exposing
all
of
the
need
at
version
information,
the
file
information
and
also
the
field
value
information
in
SharePoint
Online,
for
whatever
business
reasons
you
might
have
related
on
accessing
this
information.
A
These
were
really
really
really
highly
requested
capabilities
using
in
the
user
voice
and
it's
great
to
have
them
actually
closed
in
the
user
voice
as
well,
now
kind
of
related
on
that
one
I'm
kind
of
pinpoint
that
one
quickly.
So
if
I
go
SharePoint
user
voice
and
in
I'll
show
you
the
admin
UI
on
this
one,
we
are
actively
working
on
making
sure
that,
for
example,
all
of
your
dev
requests
and
if
they're
getting
enough
items
and
if
they're
getting
enough
votes,
we're
trying
to
get
them
solved
as
fast
as
possible.
A
There's
certain
scenarios
like
the
taxonomy
field,
REST
API.
We
absolutely
understand
that
that
has
to
happen
for
time
being.
There
are
complications
of
making
that
happen,
which
are
slightly
more
complex.
Then
we
can
get
them
solved
in
a
shorter
time
frame.
We
we
are
aware
of
that
request
and
we
are
working
on
making
that
result.
A
A
So,
if
you're
looking
into
having
something
like
capabilities
in
SharePoint-
and
you
think
that
there's
a
high
demand
for
from
the
other
customers
as
well
and
apartness
and
your
employees,
please
add
an
entry
on
the
user
voice
and
then,
for
example,
just
use
your
internal
DLS
in
your
company
to
send
an
email
to
everybody.
Saying:
hey,
go
there
vote
and
if
the
words
will
go
up,
it
will
definitely
have
an
impact
on
our
prioritization
of
fixing.
These
things
huge.
A
The
next
thing
what
I
had
on
the
on
the
agenda
was
around
the
modern
site
provisioning.
We
did
a
demo
on
this
one
actually
last
time
as
well,
and
but
this
time
and
I
wanted
to
actually
show
you
a
slightly
more
polished
version
of
the
thing.
So
let's
actually
have
a
look
on
that
so
I'm
gonna
flip
again
to
another
tenant
and
this
tenant
is
absolutely
fine,
so
I'm
in
a
splat
tenant.
So
let
me
go
to
the
SharePoint.
A
Welcome
page
I'm,
not
gonna,
do
a
full,
automated
creation
of
the
site
remotely
and
all
of
that
I'm
gonna
rather
modify
a
site
which
the
user
has
already
created.
You
can
absolutely
create
a
site
using
remote
API
as
well,
but
I'm
slightly
simplifying
the
demo,
we'll
have
more
on
the
will
be
announcement
and
stories
and
everything
else
around
the
site
provisioning
in
next
week
in
ignite,
which
I
can
go
into
right
now.
So
that's
why
I'm
keeping
this
relatively
simple.
A
So
what
I
wanted
to
actually
show
that
this
is
definitely
possible,
so
I'm
gonna
do
create
a
modern
theme
site.
Let's
call
this
sick,
sick
call,
demo,
modern,
doesn't
really
matter
and
we're
gonna
create
that
there's
a
policy.
This
is
absolutely
top-secret
stuff,
so
click
Next
the
site
is
going,
create
it
it's
more
inside.
So
it's
getting
create
it
in
matter
of
seconds,
which
is
pretty
cool.
A
So
here's
my
modern
team
site
I
could
obviously
manipulate
this
manually
and
all
of
that,
but
we
can
absolutely
use
our
remote
provisioning
engines
and
the
remote
API
to
modify
and
push
out
our
customization
to
their
sites,
and
in
this
case
we
kind
of
push
out
a
web
part,
and
we
can
push
out
a
station
and
I'm
going
to
explain
how
to
how
that's
actually
happening
here
and
but
for
simplicity
reasons,
and
do
other
reasons.
This
story
will
be
slightly
more
interesting.
A
Next
week,
I'm
gonna
use
a
PowerShell
for
this
one,
so
I'm
moving
into
my
visual
studio
code
or
sirs
to
their
code,
which
is
my
favorite
powershell
development
engine
and
in
here
I'm
gonna,
actually
connect
you
that
we
say
is
token
ESPC,
no
I'm
not
talking
about
that
space
am
talking
about
dick
night
somebody
a
minute
there.
We
go
if
night,
this
next
week
next
week.
So
what
I'm?
A
What
I'm
doing
here
is
that
I'm
connecting
to
a
using
the
SharePoint,
BMP,
PowerShell
and
I'm,
connecting
that
that
previously
created
site,
which
I
just
created
manually
and
like
I,
said
we
can
create
these
slides
using
API
as
well.
I'm
just
making
this
super
simplistic
as
possible.
So
let's
actually
do
this.
I'm
gonna
do
an
f5,
so
we
get
that
variable
in
the
memory.
I'm
gonna
connect
there
using
the
BMP
online
and
in
this
case,
because
I'm
I
don't
have
an
existing.
A
credential
storage.
A
A
So
now,
if
I
do
get
BMP
site,
we
can
confirm
that
we're
connected
using
the
p.m.
a
PowerShell,
no
big
difference,
I
just
clarifying
this.
You
might
be
super
familiar
with
BMP
powershell
versus
the
SharePoint
Online
PowerShell,
but
the
SharePoint
Online
PowerShell
is
the
native
as
part
of
the
stuff.
What
engineering
is
doing
and
with
that
one
you're
always
manipulating
and
connecting
to
the
admin,
admin
URL,
so
you're,
always
controlling
and
manipulating
your
sites
to
the
tenant
perspective
from
a
talent
perspective.
A
A
Well,
basically,
because
BMP
PowerShell
is
using
code
on
underneath
itself,
it's
using
client-side
object,
model,
REST,
API
sand
all
done,
and
it's
a
super
super
easy
way
and
convenient
way,
for
example,
to
define
all
the
Masons
in
the
rush
of
functions,
which
then
can
be
called
choosing,
storage
skews
and
rest
APIs
and
everything
else,
but
using
the
PowerShell.
You
can
easily
modify
your
scripts
in
a
matter
of
seconds.
A
So
here
we
go
I'm
applying
a
pro-v,
BMP
provisioning
template-
and
this
is
an
XML
I'm.
Gonna
show
you
that
in
a
second
and
but
now
we
applied
configurations
on
the
side
which
we
just
created
and
now,
if
I
go
to
that
side
back
in
the
site
and
if
I
do
a
refresh
something
magical,
hack,
sorry
has
happened
within
a
site
if
everything
went
well
and
everything-
and
it
went
well
now,
what's
interesting
on
what
actually
happened.
We
modified
the
Welcome
page
based
on
our
business
requirements,
which
is
such
a
typical
thing
within
a
sharepoint.
A
We
are
gonna,
have
a
standardized
template
which
is
a
condo,
so
template,
which
has
basic
things.
We
did
that
we
also
modified
to
the
actual
web
parts
which
are
on
the
page.
The
key
points
here
did,
however,
also
notice
is
that
we've
added
a
third-party
web
part
on
a
site
automatically
without
doing
anything
yeah
or
just
by
applying
the
template,
plus
we
actually
added
a
customized
footer,
which
is
condoned,
contoso
confidential
powered
by
Microsoft
SharePoint
Online
2017.
A
So
we
actually
pushed
also
SharePoint
framework
extensions
that
there's
these
sites
and
I'm
gonna
quickly
walk
through
how
this
is
how
this
is
working
and
want
to
also
make
sure
that
well,
there
will
be
plenty
of
time
on
time
of
Q&A,
but
this
actually
proves
hopefully
for
you
as
well,
that
you
can
use
templating
systems
with
the
modern
sites.
There
are
certain
things
which
will
make
this
even
easier,
which
will
be
announced
next
week,
but
how
we
actually
make
this
happen
is
that
we
have
obviously
the
third-party
web
part
and
SharePoint
framework
extension.
A
These
have
been
already
deployed,
so
these
have
been
deployed.
If
I
refresh
my
application
and
catalog
I
have
here
those
two
fellows
which
are
being
visible,
it's
it's
that
one
and
that
one
which
are
contoso
fooder
and
that
that
my
reacted,
a
wet
work.
So
those
are
the
two
things
which
are
actually
getting
automatically
applied
on
the
welcome
page
of
the
site.
A
Even
though
we
haven't
installed
anything
on
the
side,
so
you
can
see
that
there's
no
applications
being
installed,
but
regardless
of
that,
if
I
add
a
page
on
the
site
and
if
I
start
adding
content
on
a
bound
on
this
page,
we
can
actually
say
that
our
custom
to
do
web
part
is
available
in
here
and
I
can
actually
start
using
that
and
that's
because
of
the
tenon
scope
deployment
option.
So
as
part
of
the
installing
the
solution
to
that
catalog
boom,
the
web
part
will
be
available
across
the
whole
tenon
and
that's
super
cool.
A
We
don't
actually
need
to
install
that
to
the
actual
site.
Now.
The
next
thing
here
is,
then
the
the
the
footer.
How
did
we
get
our
custom
footer
available
on
the
site?
That's
the
logo.
So
that's
a
shipment
from
New
York
extension,
taking
advantage
of
the
page
placeholders
for
that
one
who
did
something
similar.
So
this
one
has
two
in
scope:
deployment
option
enabled
which
means
that
the
the
extension
is
kind
of
ready
to
be
used
across
all
of
the
sites
within
my
tenon.
A
But
then
we
need
to
enable
that
explicitly
within
a
tenant
by
using
a
remote
API
and
how
we
actually
made
that
happen
was
that
if
I
go
back
in
my
power
shop
and
if
we
open
up
this
visual
studio,
not
the
template,
the
actual
template
which
we
applied
as
part
of
the
powershell
and
let
me
actually
flip
away
I
think
the
Monica
is-
is
probably
more
readable.
So
I
can
flip
under
on
the
theme
so
in
here,
if
we
have
a
closer
look
on
what's
actually
happening.
A
So
this
this
template
has
been
created
by
exporting
values
and
then
slightly
few
modifications
manually.
The
template
structure
and
the
schema
is
documented
completely.
If
we
have
a
data
fluke
on
what's
actually
happening
here,
we
have
a
client-side
page
called
hole,
we're
saying
overwrite
true,
which
means
that
we
are
overriding
the
existing
home
page
from
a
site.
Then
we
do
have
two
sections.
We
have
a
section
one
with
a
one
text
box
and
text
field,
and
then
we
have
a
section
two.
If
I
go
back
on
this
side.
A
Let
me
do
this
and
show
you
the
Welcome
page
and
click
here.
There's
the
section
one
which
has
a
text
field
with
the
Welcome
contoso
team
site
and
a
link
over
there.
If
I
go
back
on
my
template,
we
can
see
that
there's
a
one
column,
a
one
column
type
section.
It
has
a
welcome
to
contoso
team
site
text.
That's
essentially
making
that
section
happen.
No
matter
the
next
row,
we
have
two
sections
or
this
sorry.
This
section
has
two
columns
to
be
precise.
So
if
you
go
back
in
here,
we
have
a
section
order.
A
Is
number
two:
that's
the
second
two
type
is
two
color
and
in
here
we
have
a
few
different,
wet
ones.
We
have
a
Bingham
map
web
part
and
we
have
a
text
web
part
and
then
we
have
a
custom
web
or
the
custom
web
part
is
the
one
which
is
visible
on
here
as
a
to
do
web
part,
and
then
we
have
few
texts
and
that's
the
being
web
part
visible
on
the
Left
zone.
So
how
do
we
do
this?
Is
that
in
our
engine
in
the
provisioning
engine?
A
And
where
is
my
scrolling-
hey
where's,
my
vertical
scroll
bar
there?
It
is,
and
we
can
reference
the
control
ID
and
this
control
ID
is
unique
for
that
particular
web
part.
So
the
control
ID
is
basically
the
manifest
ID
of
the
third-party
web
part
custom
web
part,
because
the
web
part
has
been
installed
to
the
app
catalog
with
two
tenants
code
being
enabled.
We
don't
need
to
do
anything
more
than
say
for
SharePoint
that
hey
we
want
to
have
this
web
part
on
this
page.
A
We're
assigning
the
right
control
ID
here
and
then
we're
saying
that
it's
in
the
column
number
two
which
is
correct,
and
it's
in
the
order
number
two
which
is
correct
because
we
actually
have
a
text
box
in
here
next
to
a
part
in
here.
I
can
actually
show
you
that
we
have
a
text
report
in
here
and
then
we
have
our
core
event
log
and
then,
after
that
we
have
a
one
more
section
available,
and
how
did
we
get
this
whole
XML?
We
actually
got
the
XML
apply
exporting.
A
A
So
that's
the
Welcome
page,
but
there
was
the
extension,
so
the
footer
section
in
here,
which
is
hovering
all
the
time
there,
so
that
is
taking
advantage
of
the
page
placeholders
which
are
in
the
shipment
framework
extensions,
and
we
got
that
one
deployed
already
in
the
App
Catalog
using
the
tenants
curve
option.
But
then
we
need
to
activate
that
in
a
site
and
how
do
we
activate
that
in
a
site?
Is
that
in
the
BMP,
provisioning
or
remote?
A
If
you
want
to
use
season
or
if
you
want
to
use
risk,
that's
absolutely
fine
as
well
and
to
be
in
provisioning.
Just
makes
this
super.
You
see
we
are
using
how
we
are
associating
a
new
user
custom
action
or
a
custom
action
with
the
right
client
side
component
ID
again.
This
is
referring
to
the
manifest
ID
of
the
shipment
framework
control
and
that
is
getting
activated
in
the
location
of
application
customizer
because
it
is
a
SharePoint
framework
extension.
A
What
is
getting
off
to
Reddit
on
the
site
and
this
way
because
it
is
tenant,
scoped
extension,
it
will
light
up
on
the
site
automatically
because
there's
a
user
custom
action
with
saying
hey
whenever
a
page
is
getting
rendered
within
this
site
anywhere
within
this
site,
which
is
the
key
point
as
well.
I
can
go
to
the
site
contents.
We
can
still
see
the
same
footer
and
extension
being
visible.
A
I
can
flip
two
pages
list
view
it
doesn't
really
matter
where
I
am,
if
I'm
in
the
modern
experiences
and
that
extension
is
getting
rendered,
because
we
tell
SharePoint
that
hey
there
is
this
application
customizer,
please
execute
the
application
customize
the
application
customizer
itself.
It's
then
responsible
of
saying,
hey
I,
want
to
actually
write
something
on
the
placeholder
in
here
and
that's
how
we
essentially
make
the
whole
thing
happen.
So
this
way
you
can
absolutely
push
any
updates
on
the
modern
pages.
A
Well,
I
would
say
you
can
any
updates
isn't
available,
but
you
can
push
certain
updates
to
this
modern
experiences
as
well.
Next
week
there
will
be
more
talking
about
the
themes.
We
actually
announce
the
modern
themes
already
in
some
level
there
will
be
obviously
an
API
support
for
some
of
that
stuff
as
well.
We
actually
is
it
that
one.
No,
it's
not
that
one.
Okay,
the
modern
themes,
it's
not
that
one
I
can
I
can't
remember
if
it's
already
public
or
not,
but
there's
already
API
is
available
in
the
latest
season.
A
With
this
current
creator,
which
is
critical-
or
this
case,
we
apply
to
template
on
a
site
which
we
manually
created,
but
you're
going
automate
that
as
well
good.
That
was
all
related
on
that
one.
How
many
questions
did
I,
miss
I,
think
Bert
or
somebody
was
answering
at
least
some
of
the
questions?
What
if
the
site
has
a
mixed
content
like
classic
pages
and
modern
pages?
Yes,
awesome
question
from
Bravo:
no,
that's
still
kind
of
debatable
thing.
No,
let
me
be
super
clear
on
this
one.
This
is
a
modern
croupe
site.
A
Let
me
actually
jump
or
to
a
team
site,
so
this
is
actually
classic
team
site.
So
if
I,
this
classic
team
sign
has
been
slightly
modified,
so
I've
modified,
actually
the
Welcome
page
of
a
classic
team
sign,
but
typically,
if
it's
a
classic
team
site,
let's
actually
go
back
on
the
original
status,
which
says
this
one,
so
the
home
page
is
and
a
classic.
A
So
now,
if
I
actually
go
back
on
the
Welcome
page
of
this
classic
theme
side,
it
looks
like
Athena
site,
it
feels
like
a
team
site
and
it
makes
you
feel
sad
kind
of,
because
it's
it's
old
school,
it's
not
well,
it's
not
as
polished.
That's
the
modern
experience
is
no.
This
is
where
it
actually
gets
kind
of
tricky
and
I
think
we
partly
failed
on
some
of
this
messaging
as
well.
The
the
SharePoint
framework
extensions
they
work
in
the
modern
experiences.
A
If
you
need
to
do
similar
experiences
and
customizations
in
classic
pages,
you
would
have
to
fall
back
on
classic
user
custom
actions
or
chase
link
capabilities.
So
the
difference
is
really
on
the
experience
perspective.
It's
not
on
the
on
the
site
type
because
you
can
actually
have
a
modern
team
site
where
you
still
have
a
classic
page.
You
can
still
create
a
classic
date
in
the
modern
team
side.
If
you
do
that
and
if
you
mix
and
match
you
will
then
need
to
have
both
kind
of
customizations.
A
You
will
need
to
have
modern,
SharePoint
framework
extensions
and
then
also
the
user
custom
action
based
customization,
so
the
old-school,
customizations
and
SharePoint
Online,
and
that
might
get
actually
slightly
complicated.
So
obviously,
if
possible,
you
you
want
to
make
sure
that
you
tribe,
towards
one
single
standard,
I
setup
within
your
turn
on.
Is
it
classic?
Is
it
more
that's
up
to
you
you'll
decide
on
that?
Obviously,
we
would
like
you
to
use
the
modern,
but
there
are
valid
business
cases,
while
people
still
want
to
use
classic.
A
If
this
is
a
classic
team
site,
how
do
I
flip
this
to
be
kind
of
a
modern
feeling?
I,
don't
need
to
do
anything
more
than
flip,
for
example,
to
the
side
pages,
and
this
can
be
done.
Programmatically
really
is
less
well
welcome,
page
make
home
page.
That
is
a
modern
page.
So
now,
if
I
get
back
on
the
Welcome
page
on
the
home,
it
looks
like
a
modern
site
and
I
can
absolutely
modify
how
the
how
the
page
actually
looks
like
as
well.
A
The
only
difference
with
in
this
case,
with
this
classic
site
would
be
that
this
classic
site
it
does
not
have
a
group
associated
to
it
after
this
operation,
but
that's
something
which
we
already
demonstrated
in
the
spring
event
that
that's
coming
in
the
SharePoint
Online
as
well,
so
you
can
associate
office.
365
groups
exist
to
existing
team
signs,
and
that
way
you
can
actually
kind
of
unplug.
A
All
the
other
things
within
the
modern
experiences
as
well,
but
classic
team
site
looks
like
feels
like
modern
team
site,
because
it
is
offering
the
modern
experiences
it
is
consistent
and
if
I
go
to
the
site
contents
or
lists
and
libraries
or
the
Welcome
page
I'm,
always
getting
to
the
modern
experience.
Ok.
A
Currently,
more
and
pages
won't
adapt
the
classic
site
panting
absolutely
correct
on
that,
and
it
will
never
do
that,
so
the
modern
pages
will
never
actually
adapt
or
support
the
classic.
Let's
say
doc
must
debate
based
on
our
customizations
or
CSS,
embedded
CSS
or
in
check
that
user
custom
actions.
It
will
never
do
that.
A
There
will
be
additional
ways
of
achieving
similar
kind
of
capabilities,
not
necessarily
the
same
craziness
as
with
the
classic
dot
master
page,
because
the
dot
master,
even
though
it's
super
super
super
convenient
in
certain
scenarios,
it
actually
is
causing
magnificent
harm
or
can
cause
harm
for
the
customers
as
well.
So
the
modern
experiences
will
never
support
dot
master.
Will
it
support
alternative
layouts?
Absolutely
how
we
are
achieving
those
alternatives?
Layouts,
that's
a
different
discussion,
so
what
kind
of
a
it
will
were?
A
No
doubt
in
still
in
the
transition
phase
between
the
the
classic
and
modern,
but
we're
kidding
there,
and
this
is
the
starts
feeling
pretty
ok
already.
There
was
a
good
comment
from
Chris
Kent
who's
in
this
call.
I
think
I
saw
Chris
here
as
well.
The
one
of
the
downsides
currently
in
the
modern
experiences
which
we're
already
looking
into
is
the
fact
that
in
certain
scenarios,
we
are
actually
showing
this
for
the
NGO
zone.
A
We
know
that
there's
gaps
there
will
be
more
additional
things
all
the
time,
but
we're
kidding
already
on
stage
or
level
that
what
if
we
would
be
fully
modern
and
we
can
automate
to
welcome
pages,
we
can
automate
all
of
that
stuff
and
we
can
automate.
What's
being
here,
we
can
push
out
our
extensions.
It's
it
start.
The
storage
starts
feeling
pretty
ok.
Doesn't
it.
A
So
this
VFX
do
work
and
modern
pages
in
classic
sites.
Yes
correct,
so
to
be
super
clear
on
on
Russell's
question
shipment
framework
extensions
do
work
on
the
modern
experiences,
regardless
of
the
site
type,
so
the
site
type.
Is
it
classic
theme
site
of
modern
themes,
and
that
does
not
have
any
meaning
on
what's
being
supported,
its
extensions,
modern
experiences,
regardless
of
the
site
type,
you
use
a
custom
action
classic
experiences,
regardless
of
the
site
type.
That's
what
it
essentially
means.
A
Good
I
think
that's
some
sup
I'm
just
quickly
scanning.
If
there's
any
any
random
questions
which
I
absolutely
missed,
you
can
please
do
set
them
in
the
on
a
window.
I've
been
I,
have
multiple
screens,
so
I've
missed.
Probably
a
few
of
this.
How
can
we
access
font
details
from
the
current
theme
of
the
modern
classic
site?
A
It's
different
depends
not
a
straightforward
answer.
Unfortunately,
I
don't
want
a
customer.
Stupid
I
just
want
a
top
bar
to
be
the
same
color
you
can
control
the
top
bar.
Oh
you
mean
it
this
bar
in
here
you
can
control
that
that
bar
actually
from
a
tenant
level
settings
you
can
absolutely
go
to
the
admin
settings
and
modify
that
to
be
certain
color
already
today.
So.
A
But
I
have
different
sites
in
it
in
the
gen
on,
so
you
want
to
have
a
different
color
per
site
in
a
tenant.
Yes,
okay,
then
it
gets
slightly
more
complicated,
absolutely
there's
ways
to
achieve
that
in
modern
experiences,
but
you
would
actually
endurance
endurance,
let's
say
common,
absolutely
understandable
comment.
We
know
the
story.
A
I
have
done
that
when
I
was
working
in
field
because
I'm
a
X
field
person-
and
we
know
how
to
make
that
happen-
it'll
just
inject
or
access
the
Dom
structure
in
here
using
HTML
and
JavaScript,
and
then
you
modify
that
style
to
be
something
other
depending
on,
depending
on
the
on
the
structure
of
the
of
the
site
as
an
example.
Now
the
challenge
of
doing
that
is
that,
then
you
have
a
dependency
on
the
dome
you
haven't.
A
You
are
assuming
that
that
colors
scheme
and
that
hi-low
top
level
bar
will
have
the
exact
same
structure
in
the
future
as
well.
Whenever
we
change
that,
because
we
will
change
that,
your
customization
will
break,
and
why
are
we
changing
that?
Well,
we're
changing
that
because
it's
not
just
sharepoint
the
same
bar
is
actually
there
for
any
of
the
other
applications
as
well
and
in
the
same
way
as
sharepoint.
This
bar
is
evolving
all
the
time.
A
So
from
a
let's
say
from
an
engineering
thinking
perspective,
the
thinking
is
that
this
bar
here
should
be
out
of
control
and
should
not
be
modified.
Based
on
the
content
of
the
of
the
below
section,
you
cannot
do
that
in
any
other
applications
than
in
sharepoint
online
in
sharepoint
online.
Technically,
you
can
do
that
because
it's
just
matter
of
injecting
JavaScript
on
the
page
and
making
it
it's
not
to
recommend
it.
However,
because
this
one
is,
will
be
evolving.
A
We
already
announced
again
a
new
design
for
this
one
and
you'll
see
that
one,
for
example,
in
the
Ignite
videos
and
in
date
night
next
week,
so
this
one
it
is
evolving
I
think
I
saw
a
Twitter
tweet
where
they
already
had
a
screenshots
and
explanation
on
on
what
will
happen
on
this
local
section
in
here
cute.
It
makes
a
CSS
achievable,
oh
well.
Obviously,
you
can
always
write
CSS
overwrite,
CSS
stars
as
well.
A
So
it's
not
a
straightforward
thing
and
that's
one
of
the
reasons
why
we
want
would
like
people
to
actually
do
only
modifications
using,
for
example,
that
debates,
placeholders
and
modern
extra
extensions,
because
we
care
indeed
that
this
will
be
here
and
we
don't
pray
queue
rather
than
doing
HTML
Dom
level
structure,
structural
changes
in
the
search
navigation.
We
know
that
you
can
do
that,
but
we
wouldn't
like
you
to
do
that.
But
it's
it's.
We
can't
really
restrict
you
for
not
doing
that
either.
A
As
quickly
creating
Ralph's
comment
around
so
the
question
why
why
there
needs
to
be
a
classic
style
of
branding
at
all?
Since
my
take
is
upon
a
hammer,
would
you
I
think
Ralph
comments
are
on
a
classic
discussion
on
the
on
the
level
of
trending?
What
needs
to
be
done?
How
people
are
so
used
to
do
customizations
in
SharePoint
and
then
there's
the
direction
where
we
are
heading?
That's
understandable.
A
Commerce,
in
future
will
will
have
a
best
practice
method
to
show/hide
more
and
paid
settlements,
such
as
the
left
navigation,
based
on
the
criteria
like
we
used
to
do
with
CSS
and
check
on
Ross's
question.
That
would
be
something
well,
we
know
the
requirements.
I
can't
promise
that
it's
it's
gonna
be
delivered
if
there
will
be
a
demand
for
those
things
like
capabilities
of
hiding
the
left
navigation
easily
based
on
criteria,
if
there's
a
demand
that
will
be
absolutely
absolutely
deliver.
No,
the
demand
doesn't
mean
an
iamb
message
in
a
Skype
discussion.
A
I
have
not
tempered
must
base
based
on
that
much,
but
I
don't
want
to
crutch
the
chains,
the
top
core
color,
to
keep
running
consistent
picture.
It
is
here
and
and
Darin
I,
absolutely
understand
the
story
on
these
things.
This
isn't
really
straightforward
either
and
especially
one
of
the
customers
are
moving
from
on
premises,
sharepoint
deployments
from
on-premises
to
sharepoint
online
in
on-premises
we
used
to
do
whatever
and
yes,
you
can
absolutely
do
that
in
sharepoint
when
you're.
A
Customers
had
a
crazy
master
pages
at
some
point
in
SharePoint
Online
and
then
some
of
the
new
functionalities
were
not
there
and
then
they
were
escalating
and
they
were
angry
because
hey
this
new
functionality,
which
was
announced
in
Twitter,
it's
not
available
in
our
tenon,
and
then
we
investigated
the.
Why
isn't
it
there?
Well,
it's
because
they're
using
a
custom
masterbate,
which
is
plugging
them
to
get
access
onto
new
capabilities
and
that's
not
an
optimal
situation
later.
A
We
need
to
find
that
kind
of
a
right
balance
and
right
compromise
for
getting
access
to
latest
and
greatest
and
then,
but
still
have
flexibility
under
grunting
and
I
think
obviously
we're
in
Cherney.
We
need
to
understand
it's
challenging
for
us
in
engineer.
It's
one
thing
for
you:
it's
charging
of
customers
and
we'll
need
to
find
the
right
way
of
doing
that.
A
So
you
can
absolutely
use
the
Bates
placeholders
extensions,
we'll
go
see
a
quite
soon
and
which
has
been
hindered
quite
a
few
times
or
there
might
or
might
not
be
additional
announcements
on
possibilities
of
a
top
navigation.
In
upcoming
week
in
ignite,
but
I
can't
confirm
or
deny,
if
that
is
the
case-
here's
the
filly,
the
history
issue.
A
If
someone
is
expecting
it,
it's
not
there
than
where
the
daycare
and
how
yes,
so
the
problem,
obviously,
is
that,
if
that,
if
customers
had
are
used
to
something
to
beer
somewhere,
they
want
to
have
that
one
there
in
the
future
as
well.
So
the
change
management
is
always
always
challenging.
It's
obviously
a
fabric
you
I
can
be
used
for
more.
It's
office
tactic
you
I
can
be
used
for
modern
site.
Yes,
so
the
modern
sites
are
using
officer,
I
fabric
UI.
So
all
of
these
are
office,
UI
fabrics
and
components
and
controls.
A
Now
there
are
certain
recommendations
related
on.
How
would
you
implement
your
webparts
and
extensions
which
are
using
office?
You
have
fabric
to
avoid
challenges
when
officer
our
fabric
is
evolving
to
a
new
versions,
and
that
is
documented
in
deaf
toaster
comm.
It's
not
a
straightforward
story:
we're
working
on
getting
that
cleaner
as
well
in
the
future.
Right
now,
it's
it's
I
would
say
even
that
it's
relatively
nasty
story
in
certain
sense,
but
the
fabric
can
absolutely
used.
Well,
that's
a
fair
comment
from
Russell
fabric
can
be
used
in
our
classic
sites.
A
A
A
Let's
get
rid
of
that.
It's
not
gonna
put
my
web
part
right
there.
Let's
do
two
columns
and,
let's
add
a
web
part
from
the
web
part
gallery
if
I
can
actually
locate
that,
because
this
classic
gallery
is
relatively
complex
under
development
to
the
web
part
and
that
one
and
there's
my
fabric
experience
and
the
modern
web
part
in
the
classic,
UI
absolutely
works
and
that's
meant
to
be
working
as
well,
and
you
can
also
have
SharePoint
headings
in
the
modern
experiences
as
well.
A
So
if
you,
if
you
are
dependent
on
an
incidence
of
fully
support
that
will
be
fully
supported
in
the
future,
adding
web
parts
absolutely
suitable
option,
we
are
investing
on
add-ins
in
the
future
as
well.
They
are
different
slightly
different
than
in
SharePoint
framework,
but
it
has
a
story
as
well
and
we're
looking
into
integrating
the
SharePoint
framework
in
a
way
that
you
can
write
easily
add
in
parts
as
well
using
the
SharePoint
framework.
But
they
say
a
fabric
components
rendered
and,
and
the
web
part
modern
web
part
being
rendered
on
a
classic
page.
A
A
Obviously,
a
fabric
UI
core
is
not
current
as
fortifies.
The
effects
as
I
understand,
you're,
absolutely
correct,
there's
certain
ways
of
making
that
happen.
We're
kind
of
a
pending
within
those
documents.
But
yes,
it's
working
progress.
You
can
use
the
office
for
American
classic
yes,
but
with
classic
and
I
reminded
that
that
really
shows
that
there's
a
100
million
office
365
seats
out
there
using
the
bits
I
would
think
twice
at
least
before
second
guessing
the
existing
UI
for
you
or
that
that
is
fair
comment
from
Ralph.
A
Yes,
there
are
many
many
many
reasons
why
people
want
to
use
the
classic
or
move
to
SharePoint
Online
with
the
classic
experience
and
then
maybe
it's
a
change
management
challenge.
We
train
for
5,000
or
250,000
employees
from
a
classic
modern
that
is
actually
superbly
expensive.
Unless
your
chosen
path
is
that
they
push
them
there
and
they
will
learn,
that's
one
option
as
well,
so
any
other
questions.
I'm
doing
now
live
demos
based
on
a
requests,
apparently,
which
was
one
of
the
intentions
of
today
as
well.
A
We
can
close
slightly
earlier
as
well.
If
that
is
the
case,
but
and
if
there's
any
not
any
more
questions,
because
we
didn't
have
any
other
topics
on
the
presentation
either
so
should
I
be
using
more
on
team
science
for
intranet
well
for
internet
experience,
I
would
be
looking
well,
it's
not
a
straightforward
answer
and
it's
not
a
straightforward
question
either,
because
everything
depends.
A
So
if
the
experience,
what
is
what
is
exactly
if
the
experience
is
what
we
currently
provide
from
a
communication
side
or
from
a
team
side,
if
that
is
sufficient
for
your
intranet,
you
should
absolutely
use
that.
So
why
not
because
then
you
are
in
the
modern
platform.
If
your
requirements,
however,
dictate
certain
scenarios
which
are
not
corrected
possible
in
a
communication
sites
and
they
can't
be
achieved
in
a
classic
wzm
science
publishing
sites,
please
do
use
them.
A
Why
presented
sites
will
be
absolutely
supported
to
the
classic
pubs
inside
will
be
supportive
and
not
pulling
a
rack
or
a
mat,
and
then,
if
those
underneath
those
sites-
and
yes
this
is
the
the
new
UI
for
provisioning
sites
that
the
native
modern
UI,
then
obviously
I
can
create
a
communication
site
home
site
and
I.
Think
that's
available,
let's
actually
create
top
secret
site
and
let's
get
that
one
created
if
the
communication
site
template
is
sufficient
for
your
internet
requirements.
Absolutely
use
this.
Why
not?
A
If
it's
not
sufficient,
then
you
need
to
figure
out
alternative
options,
and
this
is
absolutely
available
right
now,
so
any
tenant.
This
is
normal
depth,
tenant
I'm,
using
right
now
for
demos,
not
nothing
special
enabled
on
this
one,
and
this
is
pretty
cool
yeah.
So
there's
a
lot
of
capabilities
or
from
a
classic
requirement
perspective
and
I
can
shuffle
things
and
I
cannot
modify.
Obviously,
the
icons
I
can
do
a
lot
of
other
stuff
as
well.
There's
a
news
capabilities.
There's
evans
capabilities
documents,
all
of
them.
A
So
the
question
is
right:
so
I
go
to
site
contents
on,
say
new
site
nope,
you
go
to
the
SharePoint
welcome
page.
So
if
you
go
here
on
SharePoint
and
then
in
the
SharePoint
landing
or
what
is
this,
this
is
home
shipment
home.
Perhaps
if
I
remember
correct
term
from
a
marketing
perspective
and
from
here,
if
you
start
creating
sites
you'll
get
to
this
new
experience
and
we're
looking
into
announcing,
is
to
support
for
API
support
for
communication
slides
pretty
soon
that's
in
the
roadmap
as
well
and
and
PowerShell
support
for
that
one
as
well.
A
It
might
or
might
not
happen
again
next
week.
Who
knows
it
was
next
week
something
interesting.
Maybe
there
was
some
sort
of
a
big
conference,
I
I
can't
remember.
Some
of
the
new
stuff
will
be
coming
next
week.
Obviously,
and
simultaneous
tough
few
weeks
after
and
and
and
let's
move
on
and
Ralph
has
a
good
comment
so
play
with
it,
get
familiar
with
the
with
the
capabilities.
Absolutely.
A
A
And
Graf
comments
on
them.
The
business
requirement
analyzes
couch,
but
if
there
isn't
ant
that
many
additional
questions
just
to
kind
of
reiterate
on
on
this
one.
So
in
the
template,
the
PMP
PowerShell
was
the
fellow
which
we
used
for
applying
the
template.
The
template
was
actually
created
using
primer
by
exporting
from
an
existing
site
and
we
were
able
to
push
out
our
shipment
framework
stations
to
modern
sites.
We
got
the
modern
sites
to
be
nicely
modernized
based
on
our
business
requirements
up
to
the
certain
level.
A
Now,
if
the
business
requirement
would
have
been
that
hey
I
want
to
have
some
crazy
layout
here,
which
is
hiding
that
one
and
hiding
all
of
those
and
making
this
purple
and
sparkle
and
and
blinking
and
everything
else,
then
maybe
that's
not
possible,
and
maybe
then
we
need
to
fall
back
on
the
classic
conferencing
sites
and
then
do
something
crazy.
So.
A
Quickly,
there
is
still
a
UI
confusion
regarding
the
creation
of
a
collection
or
a
sub-site.
Yes,
I
am
fortunately
highly
aware
of
that,
but
mostly
when
we
get
those
things
moving,
we'll
be
getting
a
belated
credit,
come
site
from
the
admin
center
and
some
organizations
turn
off
self-service
creation
in
the
SharePoint
home.
Yes,
absolutely
so,
communication
sites
are
coming
in
more
wider
support
relatively
soon
as
well.
Relatively
soon
you
can
figure
out
get
the
conclusions
out
of
that
statement.
Is
there
a
way
to
convert
classic
pages
to
modern
pages
on
Raul's
question?
A
So
this
one
is
an
interesting
question.
It
will
still
have
a
few
minutes
this
one.
Obviously
technically
answer
is:
yes,
you
you
can
technically
do
that
or
what
you
will
be
doing
is
something
similar
as
what
we
did
actually
in
where
small,
very
ways
my
team
side
in
this
class
example
teams.
So
this
is
a
classic
teams.
I
know
the
challenges
of
doing
an
automatic
conversion
is
that
the
modern
pages
actually
are
different
and
they
support
different
things
than
the
classic
pages
and
there's
a
different
set
of
weapons.
So
there
is
no
the
web
parts.
A
The
web
set
of
web
parts
in
the
modern
pages
is
completely
different
than
it
was
actually
in
the
classic
pages,
and
these
things
support
something
like
sections
so
I
can
absolutely
add.
Let's
actually
modify
this
one
to
be
three
sections
and
in
I
can
add
additional
Oh
where's,
my
additional
section
section,
additional
section
and
additional
sections.
So
there's
multiple
things.
What
we
can
do
in
a
modern
science
which
is
completely
different
than
in
the
classic,
the
classic,
has
a
certain
set
of
layouts,
and
you
need
to
follow
up
on
that.
A
Technically,
you
can
kind
of
a
figure
out.
What
would
be
the
the
comparison
here
then
the
next
challenge
would
be
okay.
Can
you
do
a
mapping
of
one
to
one
based
on
the
web
parts?
And
the
answer
is
not
really,
then
the
web
parts
election
is
different.
The
capabilities
of
the
web
parts
is
different,
so
which
you
will
Microsoft
at
some
point
provide
a
native
capability
for
my
creating
classic
pages.
A
The
motivators
answer
is
no,
because
we
do
not
want
to
take
that
responsibility
because
potentially
you
might
lose
some
content,
because
if
you
do
make
some
sort
of
a
automated
yes
on
this
web
part
that
there
and
put
there
there.
Yes,
if
you
can
match
the
business
requirements
of
that
migration,
absolutely
feel
free
to
do
that.
We
from
a
Microsoft
perspective.
We
can't
really
take
that
risk
that
somebody
would
be
losing
the
data.
Do
the
difference
between
the
experiences
cute
and
pert
has
an
awesome
comment
on
that
one.
A
Can
you
not
enable
the
site
basis
on
an
existing
site
or
create
a
modern
pages
and
update
the
home?
But
yes,
exactly
what
we
did
here.
So
this
is
a
classic
theme
site
where
we
have
actually
gone
to
the
site,
contents
and
site
pages
library
and
in
the
site
basis.
Library
now
I
can
even
do
this
manually
in
here.
I
can
flip
back
on
my
classic
page
and
make
that
as
a
home,
page
and
voila.
That
bait
is
now
this
site's
homepage,
but
just
as
well,
I
can
create
a
new
page
from
here.
A
Let's
call
this:
let's
call
this
new
home
and
save,
and
let's
click
partners
as
well
and
I
can
go
to
those
site
contest,
and
you
can
absolutely
do
this
in
a
you
know,
using
api's
as
well,
so
I
go
to
the
site
pages
where
some
new
page
new
home
new
home
new
home,
you
know,
there's
the
new
home
and
flipped
that
is
now
our
home
page.
So
now,
if
we
go
back
in
home
yeah,
we
have
a
new
home
page
gute,
a
newsfeed.
It's
that
still
a
thing
I
think
the
old
one
is
way
different.