►
Description
SharePoint Developer Community (SP PnP) call recording from 8th of October 2019. Summary of the activities happened in the past month around SharePoint development guidance, road map updates, future plans for the SharePoint driven experiences.
The host of the call - Vesa Juvonen (Microsoft) @vesajuvonen
- Latest SharePoint community metrics from September 2019 (YouTube, GitHub etc.)
- Latest news and announcements around SharePoint dev
- A quick look on the SharePoint Dev UserVoice top 10 entries
- Community contributors and companies which have been involved in past month
- Topic – DC Padur (Microsoft) @dcpadur – Building intranets in modern SharePoint - Modern SharePoint pages tech update, Root site, Home sites, multilingual publishing for modern SharePoint (live demo). Assisted by Aninda Ray (Microsoft) and Andy Haon (Microsoft)
Detailed agenda an links to specific sections available from https://developer.microsoft.com/en-us/sharepoint/blogs/
You can download recurrent invite for the monthly SharePoint community calls from http://aka.ms/spdev-call. Monthly calls happen on the second Tuesday of each month.
More details around the SharePoint developer community from http://aka.ms/sppnp
A
Welcome
everybody,
this
ship
on
deaf
ecosystem,
VMP
community
called
this-
is
the
monkey
community
Co,
so
October
2019
coal,
where
we
kind
of
go
through
what
has
happened
in
high-level
within
the
past
month
so
agenda
for
the
day.
Is
that
we'll
have
a
quick
look
under
on
the
latest
news,
monthly
summary
and
a
few
other
details?
So
nothing
too
dramatic
all
right
now.
To
be
honest,
a
lot
of
our
engineering
efforts
and
p.m.
A
work
is
spending
for
ignite
announcements
as
well,
so
ignite
is
coming
within
a
month
or
so
where
we
will
definitely
demo
uber
cool
stuff,
and
maybe
some
surprises
for
you
as
well.
So
that's
also
one
of
the
reasons
why
there
has
been
maybe
it's
slightly
slower
amount
of
announcements
within
the
past
month
or
so,
and
definitely
as
part
of
the
community
cause,
we're
gonna
acknowledge
all
the
community
contributors.
A
We
had
a
massive
group
of
people
once
again
contributing
within
the
last
month
helping
everybody
else
in
the
community
to
succeed
as
well
and
which
is
highly
beneficial,
because
the
whole
idea
of
the
open
source
and
community
is
that
we
benefit
from
each
other
rather
than
every
single
one
of
us
banging
our
head
against
the
wall.
We
actually
have
a
joint
objective
and
we
share
our
object.
Knowledge
between
other
and
everybody
will
benefits.
That's
highly
beneficial
model
for
everybody.
A
That's
really
the
open
source
and
community
way
of
thinking
on
I
will
give
you
something
free
and
you
will
hopefully
help
me
and
so
on.
Everybody
benefits
out
of
it
and
without
actually
opposed
to
taking
your
business
away
from
the
from
the
things
that
now
today's
topic,
the
main
topic,
will
be
building
entrance
and
more
on
SharePoint.
So
we're
going
to
talk
about
home
sites,
we're
going
to
talk
about
start,
slides,
we're
gonna,
talk,
multilingual
the
person
who
actually
owns
these
from
a
feature.
Crew
perspective
is
DC
pod
or
so.
A
If
we
think
about
those
things,
we
have
a
ship
on
developer
community.
We
have
a
SharePoint
community
in
the
TIC
community,
Microsoft
a
community
side
of
the
house.
We
have
bi-weekly
SharePoint
framework
community
call
happens,
7:00
a.m.
Pacific
time
on
everything
by
week
on
Thursdays,
and
then
we
have
the
general
SharePoint
developer
community
core,
which
is
more
and
more
actually
not
development.
It
is
also
about
branding
provisioning
site
designs
and
low
code
stuff
as
well.
A
So
it's
maybe
we
should
actually
start
renaming
some
of
this
cost
not
to
explicitly
terrify
people
by
using
the
development
term
in
the
core,
because,
especially
in
SharePoint
in
cloud
and
office
365,
all
of
these
things
are
getting
mixed.
Are
you
an
architect?
Are
you
developer
or
an
API
person
and
everything
else?
It's
it's
kind
of
a
combined
effort
anyway.
Monthly
community
calls
happen
on
second
Tuesday
of
every
single
month.
A
November
one
is
then
coming
in
from
month
from
now
from
12th
of
November,
and
this
all
like
said
more
on
a
quick
summary
from
the
monthly
side
and
then
concentrating
on
a
specific
feature
or
a
functionality
and
presented
by
a
feature
crew,
member
I
haven't
yet
booked
our
November
presenter,
or
it's
going
to
be
probably
something
related
on
provisioning
or
document
management
or
the
new
stuff
which
we
will
announce
they
mcknight
never
know.
I
will
let
you
know
in
the
intro
social
media,
before
quick
recap
on
the
links
shape
on
dev
documentation.
Ok,
mrs.
A
pedak
docks
ship
on
developer
videos,
for
example.
All
of
the
memory
calls
are
getting
recorded
and
they're
getting
shared
in
sharepoint
if
channel,
and
it
has
a
lot
of
additional
videos
as
well,
not
just
about
the
development
and
extensibility
both
about
branding
the
lookbook
sides
and
designs
and
all
that
kind
of
stuff
as
well.
It's
located
in
a
chiffon
def
video
channel
and
then
the
sharepoint
of
issues
is
a
chemist's
SPD
of
issues.
If
you
are
running
in
the
developer
issues
api,
it
doesn't
seem
to
work
properly.
A
Please
use
this
location
for
letting
us
know
and
then
we'll
try
to
jump
on
on
your
reports
as
fast
possible
and
ennobles.
If
there's
something
which
really
seems
to
be
super,
super
super
critical
and
seems
to
be
causing
a
lot
of
headache
and
we've
been
having
few
of
these
over
slavery
now
and
then.
Please
also
feel
free
to
ping
me
as
an
example
in
Twitter
to
let
me
know
that,
there's
now
something
which
is
visible
but
also
used
to
issue
lists
first,
because
if
it,
if
it's
under
issue
list,
everybody
else
can
actually
follow
that.
A
Oh,
it
has
been
now
reported
and
then
we'll
have
a
one
common
location
where
we
can
get
update
you
on
the
progress
of
getting
any
issue
actually
resolved
when
we
work
towards
resolving
them.
Quick
updates
on
the
numbers
perspective,
so
September
2019
had
a
massive
actually
growth
on
the
extensibility
side
of
the
house.
Sharepoint
framework
usage,
the
third-party
SharePoint
train
reviews
it
so
somebody's
has
developed
a
extensibility
and
that's
being
the
used.
It's
a
third-party
SharePoint
framework
usage
crew
15%
within
the
last
month,
and
that's
pretty
awesome.
It's
was
actually
15.4%
and
that
met.
A
That's
insane
6350
seventy-seven
say
requests
in
every
single
second
quote
what
to
a
sharepoint
online,
but
that's
that's
kind
of
understandable
when
you
have
a
look
onto
27,500
tenants
using
those
components
so
and
that
generates
something
like
1617
billion.
If
I
remember
number
correctly,
HTTP
requests
intimate
so
a
lot
of
lot
of
usage
on
these
things
and
and
to
be
honest
and
if
we
think
about
where
we
started
like
five
years
ago,
I'm
building
this
open
source
community
and
community.
A
We
never
have
would
have
even
imagined
that
we're
on
this
level
of
usage
on
the
open-source
components
but
really
good,
and
it
shows
that
there's
a
lot
of
trust
on
their
components
and
we
keep
on
investing
on
them
as
well.
There
was
a
lot
of
changes
this
month
on
those
component
tenant
in
place,
for
example,
was
use
three
thousand
and
two
hundred
and
eighty-nine
tenants
and
there's
more
than
well
this
one
hundred
one
thousand
one
hundred
and
seventy-six
overall
contributors
in
Keith's
hub
for
all
of
the
stuff.
A
What
we
do,
which
is
a
massive
number
as
well.
So
thank
you
for
being
active
on
this
side
of
the
house.
Now,
SharePoint
framework,
just
a
pin
point
again,
the
graph
just
to
show
you
whatever
I,
don't
know
quite
what
happened
again
in
August,
but
it
started
crowing
again
on
a
completely
new
level.
We
are
seeing
across
the
board
a
lot
of
interest
on
the
on
the
SharePoint
Online
office
365
and
the
SharePoint
framework
usage.
So
the
metrics
are
going
crazy
at
this
moment,
which
is
obviously
a
positive
thing
as
well.
A
A
So
it's
slightly
going
down,
which
is
understandable
because
the
numbers
are
so
huge
already
and
that
we
can't
keep
on
crowing
300%
year
after
year
after
year,
because
that
would
multiply
to
be
an
insane
number
absolutely
now
a
few
reminders
on
the
other
assets
before
we
go
to
the
community
contributions
this
month,
shipment
of
weekly
and
if
you're
interested
on
looking
into
what's
happening
in
the
community
and
blog
posts,
announcements
from
Microsoft
side
of
the
house,
chip
on
Saturdays,
we
always
cover
those
in
these
as
well
episode.
55
came
out
yesterday
yesterday
so
know
today.
A
Today
today
is
Tuesday.
Yes,
today
we
release
this.
We
recorded
that
yesterday,
with
wall
deck,
we
did
not
have
a
visitor
system.
We
quite
often
has
a
visitor
here.
Mark
D
Anderson
was
the
previous
visitor
and
we
always
kind
of
cover
a
topic.
We
talk
about
certain
things
and
then
we
go
to
the
community
articles.
These
are
intended
to
be
30
minutes
and
quite
often
there
might
be
60
minutes
and
they're
available
as
a
YouTube,
video
or
as
a
podcast
nowadays.
So
both
options
are
definitely
available.
A
I
think
the
podcast
option
is
growing
quite
fast
now
so
clearly,
there
was
a
demand
for
now
quick
update
on
the
use
of
outside
of
the
house.
Nothing
actually
traumatic,
all
here,
no
chances
from
the
last
month,
which
is
partly
because
I
think
too
busy
and
there's
food.
A
few
things
which
would
be
never
would
have
been
able
to
do
so.
First
of
all,
at
this
report
for
dotnet
core
I
would
see.
A
Some
I
can't
promise
this
yet,
but
it
seems
to
be
that
we're
getting
death
to
preview
during
this
month,
which
would
be
already
good.
We
wanted
to
do
it
in
preview,
so
we
want
to
make
sure
that
it's
working
properly
and
then,
after
that
doodlenet
standard
version
of
season,
is
then
available
in
G
a
relatively
fast.
If
there's
no
problems,
we
are
using
that
closely
within
the
PMP
initiative
as
well.
A
So
that's
is
our
primary
way
of
them
testing
things
and
the
second
thing
which,
from
the
overall
list
of
things
just
a
pinpoint
this
one,
the
provide
an
ability
to
write
to
manage
metadata
term
store.
Api
is
using
app
only
so
it
was
increased
by
a
one-vote
and
last
month,
but
it
is
actually
100%
already
supported.
A
So
if
you
go
to
that
user
voice
item,
you
find
a
note
for
me
calling
it
out
that
it's
reported
and
how
do
we
make
that
happen,
but
we
haven't
actually
updated
the
official
documentation
that
is
on
me
to
make
that
happen
through
my
documentation
channel,
so
I
do
apologize,
if
not
yet,
having
had
time
on
doing
that.
Moving
on
on
the
on
the
articles
just
update
you
on
what's
actually
happening
the
the
october
updates
and
which
is
basically
a
summary.
What
has
happened
within
the
last
month?
What
are
the
new
webparts?
A
What
are
the
new
samples?
What
are
the
new
changes
in
the
tenant,
templates
or
powershell
side
of
the
house
that
is
now
out
in
the
AKMs
SP
dev
blog,
so
in
the
ship
on
developer
blog,
and
there
was
a
lot
of
people
again
contributing
in
the
intamin
released
on
to
level
and
we're
going
to
have
a
look
on
quickly
on
those
next,
so
the
list
of
people
it
isn't
relatively
small
font.
A
I
always
need
to
adjust
this
to
be
in
a
quite
small
font
to
make
sure
that
every
single
person
who
contributed
within
the
last
month
is
able
to
and
is
able
to
be
covered
here
now.
Please,
let
me
know
if
we
missed
you
for
whatever
reason,
if
you're
not
in
this
list
that,
but
you
did
contribute,
I
do
apologize
on
that.
This
is
unfortunately
quite
manual
thing
to
get
a
call
that,
from
the
many
of
the
repos
and
many
of
the
things
what
we
do
is
so
there
might
be
some
issues.
A
There
might
be
some
accidents
which
might
happen,
but
we'll
fix
those
definitely
on
the
blog
posts
in
the
MIS
and
Hindi
messaging.
If
needed,
these
people
a
lot
of
these
people
work
on
the
companies
who've
given
and
their
employees
the
option
to
contribute
in
the
open
source
and
community
side
of
the
house
as
part
of
their
day-to-day
work,
which
is
really
cool,
and
this
other
component
is
who
had
given
us
the
permission
to
call
them
out
from
the
companies
where
the
people
are
working
on
on
the
previous
slide.
A
So
what
if
more
and
more
companies
are
actually
being
actively
involved
in
the
open-source
community
as
well
and
clearly
promoting
the
model
where
we
use
the
open
source
components
and
open
source
initiative
as
together
and
also
contribute
on
those
as
well?
So
thank
you.
Thank
you.
Thank
you
for
crowing.
This
side
of
the
the
model
as
well
and
Microsoft
side
of
the
house
is
definitely
crowing
as
well.
This
is
kind
of
debatable
always
that
which
of
these
some
of
them
are
engineers.
A
Some
of
them
are
documentation
people
some
of
them,
are
or
feel
to
internal
field
people,
and
but
it
is
crowing,
definitely
there's
a
massively
growing
interest
on
taking
advantage
of
the
community
and
open
source
more
efficiently
inside
of
the
one
tribe,
sharepoint
engineering
as
well,
which
is
an
interesting
dimension
and
definitely
in
the
future.
So
you
will
see
more
and
more
active
engagement
for
many
of
the
future
crew
PMS,
which
is
actually
segue
to
the
following
slide.
A
So
as
an
example,
we
there's
a
high
high
high
interest
nowadays,
so
many
of
our
future
crew
members
to
come
to
these
goals
and
actually
present
you
directly
what
we're
building,
because
they're
highly
excited
on
what
they're
actually
designing
and
working
together
with
engineering.
So
today
we
have
DC
Butler
who
stay
Senior,
Program
Manager
from
the
feature
crew
side
of
the
house,
DC
I
think
you
can
insert
yourself
and
we
can
definitely
jump
on
your
side
of
the
house
as
well.
B
Been
with
Microsoft
nine
years
almost
to
the
week,
yeah
fourth
of
October
2010
yeah
nine
years
in
Microsoft,
seven
years
of
that
has
been
with
share
I
spent
five
years
of
those
seven
years
in
the
back-end
systems,
working
with
the
cloud
infrastructure
of
SharePoint,
Online
and
internal
developer
tools.
Then
past
two
and
a
half
years
two
years
have
been
working
on
the
front
end
of
the
product
working
on
the
actual
product
development,
the
SharePoint
experiences,
modern,
SharePoint
internet
experiences.
All
of
that
stuff.
In
the
past
two
years,.
A
B
A
B
Awesome,
thank
you
very
much.
This
is
very
exciting.
I've
I've
seen
bases
internal
news
posts
about
how
well
are
your
community
is
doing,
and
this
is
my
opportunity
to
be
on
the
call
actually
for
the
first
time
and
it's
really
exciting
the
last
I
counted
there
were
some
220
people
on
the
calls.
This
is
probably
my
largest
conference
audience
on
a
phone
call.
This
is
exciting.
Thank
you
all
for
joining
us
this
morning
or
afternoon
or
evening
wherever
you
are
in
the
world.
B
We
deeply
appreciate
this
opportunity
and
the
partnership
that
we
have
with
the
community
and
as
basa
mention
more
of
our
feature.
Pms
are
going
to
be
part
of
this
experience.
Sharing
their
projects
with
you
and
gathering
the
feedback
and
I
would
like
to
talk
about
a
few
things.
That's
top
of
my
mind,
which
all
accrues
towards
what
I
call
is
helping
our
customers
build
awesome,
internet
experiences
on
modern
SharePoint,
that's
sort
of
the
cohesive
theme
around
all
of
this,
and
a
couple
of
the
topics
I
wanna
address
here
are
here.
B
B
The
idea
here
is
that
we've
been
working
on
modern
SharePoint,
which
is
a
client-side
application
and
improving
the
client-side
application
and
we
have
come
to
a
place,
were
made
a
significant
change
to
the
pages
application
as
a
client-side
application,
and
we
really
need
our
community
partners
help
in
testing
out
those
experiences,
and
that
brings
me
to
the
URL
that
I
pasted
anybody,
if
you
have
deaf
tenants
that
you
constantly
use
for
development
and
you
would
love
to
help
us
out.
Please
fill
out
that
survey
and
we'll
get
in
touch
with
you.
B
I'll
quickly
cover
root
sight,
it's
a
very
popular
topic
and
I
want
to
make
sure
I'll.
You
know
address
some
top
questions
in
there,
but
I'm
gonna
quickly,
breeze
through
this
we've
rolled
out
a
bunch
of
poor
blog
posts
about
this
coming
documentation
about
this
and
features
are
rolling
out,
so
I
will
quickly
get
through
that
and
then
we'll
get
to
spend
most
of
our
time
on
home
sites
and
multilingual
publishing
for
modern
SharePoint
with
that,
I
will
go
to
this
slide
and
an
India.
If
you
can
unmute
yourself
and
start
talking,
hey.
C
C
There
isn't
a
net
experience
impact
out
of
it,
but
the
goal
here
is
to
few
things
the
start
of
it.
As
you
might
know,
many
pages
I
was
using
a
proprietary
router
for
navigating
across
all
its
links.
That
was
a
point.
A
react.
Router
did
not
support
a
bunch
of
functionalities
that
we
required
for
large-scale
enterprise
portals
this
switch.
C
We
are
actually
switching
to
react,
router
for
point,
and
we've
built
these
extensions
on
top
of
react,
router
to
start
doing,
link
intercepts
and
the
communication
between
a
mobile
host
and
page,
a
page
posted
as
a
verb
use,
and
so
on
so
forth.
The
actual
implication
from
the
development
community
is
that
going
forward
we
might
be
able
to
start
supporting
custom
routes,
for
instance,
you
might
have
a
part.
The
see
all
experience
is
something
that
you
might
want
to
have
a
custom
solution
for,
and
this
sets
us
up
towards
achieving
such
forms
of
customizations.
C
This
also
aligns
the
pages
application
with
other
applications
like
the
SharePoint
start
page
or
the
soldier,
for
instance,
which
are
all
powered,
react
routers.
So
this
alignment
is
required
because
that
takes
us
to
the
next
part
of
the
motivations
towards
doing
that
work,
which
was
to
provide
a
seamless
experience
as
you
transition
between
all
these
various
shep
and
experiences
that
building
across-the-board
news
lists
start
page.
C
For
instance,
we
want
to
keep
this
as
a
seamless
experience
without
having
the
end
user
have
to
experience
the
full
page,
reload
or,
and
the
suite
nav
and
the
chrome
reloading
we're
kind
of
trying
to
avoid
that
and
switch
to
a
model
of
any
switch
between
all
these
applications.
The
chrome
is
persistent.
The
applications
are
much
performant
because
a
lot
of
the
underlying
components
I
reuse
between
these
applications
within
the
session.
C
The
the
other
thing
that
we
did
as
part
of
this
work
was.
That
was
a
point
in
time,
but
we
weren't
really
sure
about
the
bsd
license.
Had
some
implications,
but
so
we
had
this
unnecessary
interaction
from
a
non
react
view
to
react
view
and
that
interaction
was
a
cause
for
a
lot
of
reliability
and
performance
concerns,
and
we
kind
of
addressed
that
and
now
we
have.
We
are
a
reactive
resolution
and
we
don't
need
to
have
this
unnecessary
interaction.
C
So
these
were
some
of
the
it's
as
I
mean
internally,
it's
a
pretty
big
change,
so
we
really
want
you
guys
to
help
us
out
as
you
build
custom
parts,
as
you
add
extensions
to
the
page
as
you
as
you,
you
know
deep
links
to
your
canvas.
If
things
don't
work
out,
then
we
would
really
like
to
know-
and
we
would
like
you
to
share
your
experiences
with
us.
C
If
you
see
a
significant
impact
on
performance,
for
instance,
you
would
like
to
know
that
it's
a
big
change
and
having
you
guys,
help
us
out
here,
but
really
how
so
DC
has
a
list
and,
as
you
guys
interested
please
sign
in
and
we're
going
to
basically
fight
you
guys
onto
it,
and
you
can
reach
out
directly
to
DC
and
me,
as
you
have
concerns,
as
you
have
expectations
out
of
this
and
you're
definitely
going
to
try
to
solve
them.
Thank
you
so
much
thank.
B
A
Move
on
newts
a
quick
comments:
sorry
just
a
foot
butter
ads
and
for
those
who
are
waiting
at
this
over
suppose
the
technical
piece
and
then
we'll
go
to
the
more
on
the
functionality
side
of
the
house
as
well,
but
just
to
be
important
and
the
community
isn't
necessarily
highly
aware
what
is
an
application
inside
of
SharePoint
Online,
but
just
additional
elaborating
on
that
one.
So
we
built
SharePoint
on
experiences
using
this
application
term
and
application
functionality
and
as
an
example,
lists
and
libraries
or
applications
and
then
site
contents
is
an
application.
A
B
Next
topic,
good
site
I,
want
to
reiterate.
I
think
this
is
clear
to
most
people
who
want
to
reiterate
do
not
delete
the
root
side
of
your
of
your
tenant
or
recommend
it
to
any
of
your
customers.
Anybody
that
you
work
with.
We
are
strongly
dissipating
our.
You
know,
customers
from
deleting
the
root
side,
even
though
it
might
be
technically
possible,
hopefully
shortly
that
will
also
go
away,
and
the
popular
ask
nowadays
is
having
a
communication
site
at
the
root
location
of
your
tenant
of
your
organization
and
new
customers.
B
Signing
up
for
office
365
starting
April
of
this
year
have
been
getting
a
communication
side
of
the
route
and
for
the
existing
customers.
We've
just
about
rolled
out
an
experience
to
swap
an
existing
communications
to
the
URL
of
your
root
site
location,
and
there
is
one
other
feature
which
will
enable
communication
sites
in
situ
and
I
will
quickly
go
over
those,
and
with
these
two
experiences
with
covers
most
of
the
scenario
of
how
users
customers
can
get
a
modern
communication
site
experience
at
their
root.
As
I
said,
the
first
one
is
a
site
swap
experience.
B
It's
already
available
for
in
organizations
with
less
than
10,000
seats.
It's
it's
done
using
PowerShell.
You
need
to
be
an
admin
to
have
access
to
that
SharePoint,
Online,
Management
PowerShell
and
run
this
in
this
documentation.
Here,
it's
a
quick
PowerShell.
It
takes
about
a
minute
to
complete,
and
at
the
end
of
that
you
would
have
an
existing
communication
site
at
a
different
location
would
then
be
moved
to
your
root,
URL
location
and
the
old
root
site.
B
The
next
one
is
enabling
the
communication
side
experience
as
a
feature
as
an
experience
on
an
existing
root
site.
So
for
there
are
scenarios
where
moving
the
root
side
is
not
quite
an
option.
So
as
long
as
classic
publishing
is
not
enabled
on
the
site,
you
will
then
be
able
to
enable
the
communication
side.
Experience
on
that
site,
collection
and
basically
the
root
web
of
the
site
collection,
will
then
have
a
modern
communication
side
experience
again.
This
is
also
documented
in
this
URL
here.
B
A
sharepoint
home
site
is
quite
literally
it's
the
top
of
your
internet.
It
is
the
landing
experience
that
is
built
up
with
care
and
consideration
to
reflect
the
branding
and
the
voice
of
your
organization.
It
brings
together
the
best
parts
of
your
applications
and
makes
it
make
sure
that
the
landing
experience
for
the
for
your
employees
and
your
users
are
top-notch
and,
and
that
site
is
called
the
home
site
and
Microsoft
is
enabling
a
great
home
site
experience
or
successful
experience
in
two
ways.
B
The
first
one
is
to
go
build
that
one
site
with
out
of
box
capabilities
or,
if
required,
extended
with
the
the
awesome
SharePoint
framework
and
community,
integrations
to
build
that
one
site
which
which
reflects
what
you
want
shown
as
a
representation
of
your
branding,
right
and
and
that
was
journey
to
get
to
the
place
where
a
lot
of
this
functionality
is
available
out
of
the
box.
And
then
we
went
one
step
to
see.
How
can
we
make
this
more
successful?
How
can
we
make
that
one
site
successful
by
and
we
came
out?
B
We've
come
up
with
a
couple
of
options
to
begin
with
and,
and
we
are
excited
about
what
this
opens
up
as
a
possibility
in
the
future,
so
it
I
will
explain
exactly
what
that
is,
and
then
this
one
I'm
gonna
quickly
switch
to
my
demo.
So
this
here,
our
is
a
home
site
of
contours
of
electronics
and
I'm.
B
Gonna
quickly
walk
you
through
how
Microsoft
thinks
about
a
home
site
and
why
we
think
the
individual
components
that
come
together
are
really
important
and
we'll
begin
with
search
on
the
top,
who
are
most
interact
with
one
of
the
top
functions
of
an
intranet
landing
pages
to
help
users
discover
content
or
find
the
content.
They
are
looking
for
with
a
quick
search
experience.
B
So
having
the
who
you
Microsoft,
search
experience
at
the
top
of
the
a
the
home
site,
which
is
automatically
scoped
to
search
your
entire
internet
is
functionality
number
one
and,
as
you
can
see,
you
have
the
the
mega
menu
the
out
of
box
mega
menu
that
helps
represent
the
information
architecture
of
your
organization
in
a
nice
visual
way
that
helps
users
discover
content
and
get
back
to
things
find
things
that
they
really
care
about.
Using
the
navigation
links
that
provided
and
in
the
intersection.
B
If
you
look
at
here,
we've
introduced
a
new
vertical
section,
and
this
should
be
a
feature
that's
already
rolled
out.
This
vertical
section
is
allows
you
to
have
denser
content
on
the
page
and
our
hypothesis,
and
our
recommendation
is
that
vertical
section
be
used
for
content
that
is
personalized
to
the
end-user,
and
we
have
a
bunch
of
web
parts
that
are
available
that
target
specific
content
to
the
users.
So,
for
example,
the
my
recent
documents
are
the
my
frequent
sites.
These
are
web
parts
that
are
unique
to
the
user.
B
So
having
this
vertical
section
be
a
personalized
nature
is,
is
a
great
benefit,
and
now
that
you
have
a
vertical
section
that
can
have
a
background
color,
you
can
visually
highlight
what
that,
what
value
that
can
be
derived
out
of
that
section.
They're,
looking
into
the
main
section,
you
obviously
have
the
news
web
part
and
a
carousel
layout.
This
again,
this
news
layout
has
been
rolled
out
to
everybody
and
having
share
for
my
news,
the
powerful
new
system
out
of
box
is
great
for
a
home
site.
B
You
can
have
audience
targeting
enable
you
can
make
sure
the
news
is
targeted
based
on
the
audience
group
of
the
user.
That
visits
the
site
and
the
flexibility
of
the
news
web
part
is
such
that
you
can
have
multiple
web
parts
in
the
same
page
to
showcase
different
news
types,
and
one
thing
I
want
to
call
out
here-
is
also
the
organizational
news
capability
where
you
can
anoint
a
single
site
to
be
a
source
of
authoritative
news
and
news
posted.
There
gets
a
special
visual
treatment
when
users
come
across
that
news.
B
Article
and
this
home
site
will
automatically
be
configured
to
be
a
source
of
authenticated
news
and
then
the
richness
of
social
integration,
using
you
know
having
stream
videos
and
the
new
conversation
web
part.
The
Yammer
web
part
that
lets
you
interact
with
Yammer
conversations
right
then,
and
there
inside
the
SharePoint
site
is
a
cool
new
web
part
that
helps
with
social
interactions
on
the
site
scrolling
all
the
way
to
the
down
near
of
the
out
of
box
I'd
footer.
That
completes
the
story
of
having
communication
site
that
serves
as
the
top-level
internet
landing
page.
B
So
you
might
wonder
like
okay,
this
is
the
communication
site
with
a
bunch
of
good
out
of
box
functionality
and
what
makes
this
a
home
site
and,
as
I
mentioned,
a
home
site
automatically
has
search
scope
to
be
internet
wide.
It
also
has
the
source.
This
site
has
also
said
as
the
source
of
authoritative
news,
and
these
are
things
you
could
anyway,
do
one
a
multiple
other
sites
answer
as
well.
The
unique
value
here
is
that
now
this
home
site
is
integrated
with
the
out
of
box
SharePoint
start
page.
B
The
shape
on
start
page,
as
you
might
know,
is
a
very
popular
for
users
to
get
back
to
their
SharePoint
content,
and
you
will
notice
that
this
is
the
new
UX
and
this
UX
is
also
rolling
out
in
the
in
this
month,
and
this
new
UX
now
inherits
it
brings
the
site
branding
and
the
theming
and
the
navigation
header
footer
functionality
from
the
home
site
over.
So
what
this
means
is
no
matter
where
your
users
start
their
day.
B
It
could
be
the
browser
before
home
site
or
they
go
log
in
to
offers.com
and
click
on
SharePoint
to
get
to
their
word
either
way
the
home
site
and
it's
content
is
available,
just
one
click
away
and
that's
the
value
of
a
home
site.
We
want
to
make
sure
again
reiterating
the
concept
of
me
space
and
we
space
them
out
of
box.
My
SharePoint
start
page
is
the
out
of
box
personalized
start
page
experience.
It
is.
B
It
is
all
about
the
user
that
lets
the
user,
get
back
to
the
content,
the
most
care
about,
discover
things,
that's
most
relevant
to
them,
powered
by
the
intelligence
of
Microsoft
graph.
So
now
this
right.
Next
to
your
home
site,
so
anybody
who
starts
today
can
quickly
click
on
the
home
and
get
back
to
that
home
site
and,
as
you
can
see,
the
suite
single
page
navigation
between
the
start
page
and
the
home
site
experience.
So
now
going
back
to
my
slides.
B
The
other
super
file
superpowers
for
the
home
site
is
where
now,
if
you're,
using
the
SharePoint
mobile
app,
and
we
strongly
recommend
that
you
do.
The
SharePoint
mobile
app
now
will
have
a
unique
entry
point
for
this
one
special
site
in
your
organization.
So
imagine
a
new
employee
join
your
company
and
you
they
have
their
mobile
app
installed.
They
log
in
and
pronto.
They
have
access
to
the
home
site
right
then,
and
there
and
they
don't
have
to
know
the
URL.
They
don't
have
nowhere
to
go.
B
It's
right
there
available
for
access
to
most
important
company
resources
and
that's
again,
the
value
of
a
home
site
is
in
making
sure
that
it's
easily
available
to
where
users
are,
and
we
are
we're
hoping
to
expand
on
this
capability
with
more
integration
across
the
office
365.
In
fact
the
em
365
ecosystem.
B
Communication
side
to
be
the
home
site
and
if
the
demo
gods
are
with
me,
I
will
not
have
a
problem
and
I
have
a
problem
never
mind.
This
is
what
I
was
afraid
of,
and
that's
why
I
have
Prachanda
experiences
so
as
you
K
so
doing
when
I,
even
you
in
CQ
this
command.
This,
my
SharePoint
link,
shows
up
in
the
navigation
and
then
you
have
the
unique
single
page
application
experience
with
the
shared
header,
navigation
and
branding
carried
over
to
the
SharePoint
Start
page.
B
I
showed
you
a
bunch
of
features
that
make
up
a
home
site
like
how
do
you
build
a
home
set
and
I
say
again,
as
this
list
shows
most
of
them
have
already
been
shipped
out.
All
of
these
features
were
conceived
with
the
goal
of
helping
our
customers
build
a
great
home
site
experience
and
those
individual
features
have
baladi
being
shipped
out,
searches
already
rolling
out
and
I
think,
hopefully
done
by
the
end
of
this
year.
B
Again,
quick
overview,
it's
a
it's.
A
home
site
is
a
communication
site
with
superpowers.
Only
one
pertinent
and
home
site
and
have
sites
are
additive
experiences.
If
you
think
about
it,
a
hub
is
essentially
a
site.
That's
been
elevated
to
serve
as
the
hub
of
a
bunch
of
other
sites,
and
you
can
then
elevate
another
that
one
step
more
and
make
it
your
home
site.
So
your
home
site
can
also
be
a
hub
site
and
it
requires
admin
action.
B
So
if
you
have
heard
some
questions
about
this,
so
when
Microsoft
rolls
out
home
sites,
organizations
don't
automatically
get
a
home
site
and
a
tenant
admin
has
to
take
action
to
set
the
sites
to
be
their
home
site.
So
that's
when
there
is
a
conscious
decision
to
roll
out
one
site
to
be
the
top
with
our
Internet
and
that's
a
conscious
gesture.
It's
not
a
new
site
template,
so
there's
no
confusion
about
creating
yet
another
template.
B
It's
just
elevating
an
existing
communication
site
to
serve
a
bigger
purpose
and
it's
not
a
design
for
a
communication
site.
We
we
have
given
you
the
ingredients
that
let
you
mix
and
match
and
put
together
with
the
rich
power
of
the
page,
canvas
and
you
you
can
feel
free
to
make
the
home
site
your
own.
B
With
your
own
customizations,
as
I
said
you,
you
build
a
calm
site
and
one
thing
I
want
to
call
out
is,
after
you
have
a
communication
site
to
serve
as
your
internet,
landing
page
you
if
you
would
like
to
move
it
to
the
root
site
location,
so
your
it
enjoys
a
short
URL
that
most
of
your
users
might
be
familiar
with.
You
could
do
that
with
a
swab
gesture
and
then
run
the
cap,
our
shell,
to
make
it
a
home
site
which
then
elevates
it
to
be
the
top
of
your
Internet.
B
So
as
a
modern
SharePoint
in
from
a
low
information
architecture,
the
home
site
is
the
top
of
your
internet
and
recommendation
is
it's
linked.
We
are
navigation
to
the
other
top
hubs
of
your
element,
so
you
can
think
of
the
air
and
the
HR
system
being
HR
up.
Your
legal
can
be
a
legal
marketing
and
sales.
B
Each
of
them
have
individual
hubs
that
do
take
care
of
the
day-to-day
rhythm
of
business,
but
they
have
a
connection
through
the
navigation
to
the
home
site
of
your
organization,
which
serves
as
the
landing
page
users
start
the
day
on
the
home
site,
quickly
get
to
the
content
that
they
need
to
and
continue
the
day
of
work
that
rounds
up.
My
conversation
about
home
sites
and
leaves
us
enough
time
for
multilingual
publishing
in
modern
SharePoint
and
associated
questions
in
answer
as
well.
So
at
this
time,
I
want
to
take
a
pause
and
Andy.
B
C
B
Okay,
the
root
side
is
the
the
the
one
out
of
box
site
collection
that
is
available
for
all
organizations.
All
customers
who
sign
up
for
an
office
365
SharePoint
in
it.
So
it's
the
shortest
URL.
You
have
the
contoso
door
checkpoint,
calm,
and
that
is
the
that
is
literally
the
one
route
set.
So
I'm
gonna
quickly
go
to
this
there's
a
one
route
site,
so
typically
the
route
there
has
been
a
classic
team
side
up
until
April
of
this
year
and
starting
April.
B
It's
now
a
communication
site
and
a
home
site,
on
the
other
hand,
is
a
communication
site,
a
modern
communication
site,
that's
elevated
to
be
the
top
of
your
internet.
A
route
side
is
more
about
the
location,
the
URL
of
the
you
of
the
site.
That's
what
route
site
means,
whereas
home
site
is
about
the
functionality
of
the
site.
What
does
that
site?
What
can
that
site
do?
What
is
that
extra
super
power?
Does
the
site
have
to
serve
as
the
top
of
your
landing
page
and
as
I
mentioned,
they
can
coexist.
B
B
We
will
be
working
on
it
for
most
of
this
year
and
we
are
really
excited
to
be
sharing
this
with
you,
and
the
idea
here
is
that
in
a
communication
scenario,
we
are
after
what
helps
our
customers
onboard
to
modern
SharePoint
for
communication
scenarios
and
when,
when
I
say
communication,
this
is
about
content
publishing
and
having
a
site
for
users
to
come,
consume
information,
that's
relevant
to
their
notated,
a
business
or
anything
pertaining
to
their
to
their
work
life.
So
curated
content
publishing
scenarios.
B
So
what
we've
done
is
we
started
with
minimal
scope
of
publishing
scenarios
for
pages
and
news
in
modern
communication
sites?
Now
we're
looking
at
a
language
construct
to
begin
with,
so
you
would
have
English
and
French
and
Spanish
as
languages
supported,
but
we
are
moving
away
from
not
having
the
local
differentiation,
for
example,
French
Canada
versus
French
French.
While
there
is,
you
know
a
stylish
and
and
maybe
even
some
language
differences.
B
We
are
betting
on
having
an
individual
language
variant
for
having
this
multilingual
publishing
experience
we're
also
including
the
multilingual
user
interface
as
a
part
of
the
scope
of
this
work
and
which
means
the
site
name
and
the
hair
navigation
footer.
All
of
these
experiences
that
make
up
a
publishing
communication
site
experience
are
part
of
this.
B
What
we
will
roll
out
as
multilingual
publishing
for
it,
and
hopefully
by
the
end
of
this
year
and
explicitly
out
of
scope,
just
to
reiterate
who
are
not
looking
at
collaboration
scenarios,
as
I
mentioned,
multilingual
experiences
can
have
different
flavors
different
facets,
interactive
communication
or
altering
collaboration
on
using
lists
or
process
workflows.
All
of
these
things
can
also
have
a
multilingual
aspect
to
it,
but
that's
not
in
scope
for
what
we're
working
on
right
now.
B
That
obviously
includes
the
lists
and
libraries
at
this
point
and
we're
not
looking
at
a
language
as
a
permissions
construct,
so
we
don't
mean
it's.
This
is
about
facilitating
content,
publishing
and
consumption
in
multiple
languages,
but
not
access
restrictions
based
on
language
as
a
parameter.
So
we're
not
doing
that
then,
obviously
we're
not
trying
to
rebuild
variations
as
a
modern
experience.
We
have
completely
rethought
about
what
does
it
mean
to
have
a
multilingual
experience
in
this
day
and
age
in
a
cloud
experience?
And
that's
what
we're
after
so
with
that?
B
Let
me
see
if
I
can
actually
do
a
demo,
so
the
journey-
and
you
will
all
be
excited
to
know
that
you
are
the
first
audience
outside
of
Microsoft.
Seeing
a
live
demo
of
the
multilingual
experience.
Visa
has
been
a
proponent
of
you
know,
showing
life
code
demo
in
these
things
to
get
the
deaf
community
excited
and
I'm
I'm
happy
to
share
this
with
you.
So,
as
you
can
see,
this
is
a
new
experience
for
site
administrator's.
B
You
know
languages
that
you
want
to
support
and
in
a
code
that's
not
yet
landed
is
where
you
can
select
translators
to
be
associated
with
individual
languages
and
I'll
talk
about
where
those
translators
come
into
play.
So
content
is
created.
This
is
again
a
post
that
I've
created.
Imagine
content
creation,
the
way,
typically
that
happens
and
once
content
is
created
in
the
primary
language.
The
content
creator
can
then
engage
with
the
translations
experience
and
then
kick
off
translations.
B
So
what
this
does
is
makes
copies
of
this
page
as
it
stands
today
and
puts
it
in
separate
folders
for
every
individual
language,
in
this
case
French
and
German.
So
here
I
want
to
call
out
the
fundamental
architectural
choice
that
we've
made.
So
we
have
made
a
single
site,
multi-page
architectural
choice
for
multilingual
page
publishing.
So
what
this
means
is,
if
there
is
an
English
page,
there
is
a
corresponding
French
page
and
a
German
page
backing
up
that
individual
pages,
and
we
make
a
one-time
copy
at
page
creation
time
to
get
started
with
the
translations.
B
So
at
this
juncture,
what
happens
is
based
on
the
email
addresses
provided
with
for
the
translators?
The
translators
have
been
notified
that
a
new
English
page
has
been
created,
with
the
link
to
the
corresponding
French
page
or
the
German
page,
and
then
the
translator
can
then
go
into
the
page
and
then
update
all
the
English
content
in
the
page
to
the
corresponding
French
or
German
language
and
then
publish
the
page.
B
So,
in
this
case,
I
had
pre-prepared
this
to
have
English
and
French
and,
as
you
can
see,
this
English
site
has
a
noose
carousel
experience
that
is
rolling
up
all
the
English
news
and
all
of
these
inner
quicklinks
are
available
in
English,
and
here
is
another
quitting
peppered
aware
with
content
in
English.
In
all
most
of
the
time.
All
of
the
content
here
is
in
English,
so
switching
to
French.
B
Will
now
render
the
site
in
French
and
if
you
are
a
French
user,
we
automatically
render
this
French
site
for
you,
so
you
wouldn't
have
to
go
to
English
and
then
come
back
to
French.
So
you
can
now
be
La
Vie.
We
can
detect
your
language
and
show
the
content
in
that
language
and
what
you
will
notice
this.
B
This
rollup
web
part
automatically
just
picks
up
the
French
variant
of
via
French
translation
of
each
of
the
pages
that
were
shown
in
the
English
language,
and
then
users
can,
you
know,
engage
with
this
and
read
the
content
in
the
French
language.
So
this
language
selection
is
in
the
scope
of
the
site
where,
even
though
my
language,
your
primary
language,
is
English,
I
am
choosing
to
read.
The
content
in
French
and
I
can
continue
reading
the
content
in
French.
B
So
this
kind
of
sums
of
the
multilingual
experience
from
the
consumption
end
so
from
10,000
to
food
view.
If
you
think
about
how
do
I
have
a
multilingual
site
experience,
so
it
begins
with
the
site
administrator.
Turning
on
multilingual
support,
enabling
the
languages
that
he
or
she
chooses
to
have
an
available
on
the
site
and
then
assigning
the
individual
translators
for
those
languages,
that's
optional.
But
if
you
have
translators
we
the
system
will
automatically
do
notifications
for
you.
The
next
step
is
setting
up
the
sides.
B
It's
a
structure
of
the
site,
so
the
site,
the
primary
editor
of
the
language
primary
language,
will
then
have
a
site
name
and
the
create
the
navigation
and
the
out-of-box
site
footer.
And
then
the
translators
with
their
language
in
the
corresponding
supported
languages
would
then
go
and
update
the
site
title
and
update
the
navigation
and
the
footer.
And
now
the
site
structure
is
ready.
Next
comes
the
home
site
and
the
the
home
page
of
the
site
and
the
other
article
pages
in
the
site.
B
So
where
individual
pages
can
then
be
kicked
off
for
translations,
the
translators
will
then
get
notified
and
the
translators
can
go
into
the
individual
pages
and
then
up
and
update
the
translation
update
the
content
in
there.
So
when,
when
a
published
page,
when
a
published
English
page,
for
example
in
this
case,
is
updated,
that
also
sends
a
notification
to
the
translator,
letting
them
know
that
content
has
been
updated
and
then
the
they
would
then
be
able
to
decide
if
that
nation
is
applicable
to
that
language,
and
this
is
where
we
think
the
the
modern
way.
B
B
One
thing
I
want
to
call
out
this
at
this
point.
We
are
not
doing
other
translations.
The
system
does
not
automatically
translate
any
content,
and
this
is
primarily
because
we
we
have
seen
scenarios
around
customers
wanting
a
high
level
of
control
over
what
gets
translated
and
how
its
translated
and
making
sure
that
the
primary
language
content
and
the
translated
content
are
of
high
fidelity.
They
have
the
best
quality
before
it
gets
published,
and
there
are.
B
Webparts,
will
automatically
respect
the
language
settings
of
the
page
so,
as
I
showed,
if
you
have
a
home
page
with
a
news
web
part,
another
highlighted
content
and
multiple
other
search
experiences
and
when
a
copy
of
that
page
is
made
in
a
different
language.
Those
web
parts
will
automatically
filter
content
to
that
language,
so
this
is
the
top
down
view
of
the
10,000
foot
view
of
multilingual
publishing.
So
we
obviously
have
some
time
left
and
I
wanna
recap,
though,
the
four
messages
I
want
to
deliver
the
first
one
being
hey.
B
We
need
your
help
with
testing
the
new
modern,
client-side
application,
though
the
way
we
are
shipping
modern
experiences
with
client-side
application,
we
have
made
a
significant
architectural
change.
We'd,
like
your
help
with
testing.
So
please
respond
to
the
survey
link
here.
It's
also
in
the
chat
window,
root
sight,
don't
delete
it,
swap
it
and
replace
it
with
the
communication
site
and
details
are
here
in
this
URL
and
home
sites.
B
It's
a
quick
way
to
think
about
it
is:
it
is
the
top
communication
side
of
your
organization
with
special
spool
superpowers
and
we're
hoping
to
roll
out
the
the
superpowers
aspect
of
home
sites
later
next
month
and
multilingual.
Finally,
we
have
multilingual
support
for
modern
SharePoint
in
the
publishing
world
with
pages
and
news,
and
we
hope
to
have
that
rolling
out
by
end
of
this
year
as
well.
Possibly
early
next
year
continue
begin.
B
The
journey
this
year
and
then
hopefully
end
up
right
after
the
holidays
and
support
for
multilingual
pages
and
use
in
communication
sites
with
a
single
site
multi-page
model,
and
with
that
I'm
open
to
questions.
That's
my
Twitter
handle
I'm
happy
to
engage
with
our
community
in
twiddle
as
well
and
I.
Look
forward
to
your
participation
with
this.
B
It's
available
in
the
in
the
ad
user
object
and
it's
synced
down
to
SharePoint
User
Profile,
it's
the
name
of
the
service
is
changing
in
the
cloud,
but
it's
typically
it's
what's
known
as
a
User
Profile
service
of
the
SharePoint
service,
and
that
makes
it
available
to
every
SharePoint
experience
when
a
user
logs
in
so
we
automatically
know
users
default
language
choice,
no
matter
what
browser
you
are
using
or
which
country
you
are
in,
but
in
case
that
is
empty.
We
then
default
to
the
browser
language.
So
there
are
scenarios
where
some-some.
B
For
some
reason,
the
users
default
language
is
not
being
set.
In
that
case,
we
will
pick
up
the
browser
language
and
that
would
be
the
language
of
the
user
users
choice
and
then,
if
content
is
available
and
published,
content
is
available
in
that
language
and
you're
trying
to
access
the
site
will
automatically
show
you
that
content
with
the
option
of
having
switching
to
other
published
languages
in
the
drop-down,
hey
DC,
is
really
there's
another
question
about
what.
B
Good
question,
so
we
have
about
50
languages
that
are
supported
and
we'll
make
sure
it's
part
of
the
documentation.
You
can
go
see
that
today
and
if
you
go
to
the
language
settings
of
any
modern
site
collection
today
you
see
a
list
of
about
50
languages,
I
think
it's
49
or
50
in
there
and
that's
the
list
of
languages
we
are
supporting
for
multilingual
publishing.
There.
C
B
Is
that
a
specific
question
about
like
because
it
is
a
communication
site,
its
power
it?
It
behaves
like
any
other
communication
side
with
external
access,
so
the
the
I.
Don't
the
external
access
do
not
have
a
SharePoint
start
page
experience
so
that
integration
works
best
for
users
inside
your
organization.
But
if
you
have
enabled
the
site
to
have
sternal
axis,
they
will
be
able
to
consume
the
content
in
the
home
side
itself,
as
as
they
would
with
any
other
communication
side.
B
That's
externally
shed
it's
the
SharePoint
start
page
integration
that
will
not
work
because
the
start
page
integration
assumes
or
requires
that
the
user
accessing
is
actually
part
of
the
tenant
and
they
have
the
the
the
way
this
page
is
set
up
is
that
it
would
work
only
for
users
that
are
the
they
will
not
work
for
external
users,
green
and
I.
Actually,
don't
I
don't
know
Andy.
Do
you
know
if
external
users
have
shape
on
mobile
app
access?
Oh
yeah,.
C
B
So
that
might
be
a
follow
up
for
us
to
get
back,
but
and
so
the
so
the
mobile
app
is
something
that
we
are
working
on
and
we
are
hoping
to
have
this
the
similar
language
switching
experience,
and
there
is
obviously
a
twist
with
there
is
a
user
language
option.
You
know
problem
and
there's
also
the
device
language
which
were
typical
applications,
end
up
respecting
and
we're
working
through
that
I
I.
Don't
yet
have
a
solution
to
that.
I
can
discuss
with
you
right
now,
but
that's
that's
definitely
top
of
our
minds
right
next.
A
B
We
we
don't
holo
translate
so,
as
I
mentioned
there,
none
of
the
custom
content
from
users,
pH
site
title
or
navigation
names,
live
names
or
footers
or
actual
page
content.
None
of
the
custom
content
I
know
User
Content
is
automatically
translated,
but
it
is
possible,
for
you
know,
at
the
site,
editor
and
the
translators
to
go
in
and
configure
the
site
in
the
various
languages
that
it's
intended
to
support.
So
the
way
it
would
go
is
an
English
user
will
go,
create
the
English
label,
I
mean
and
an
English
editor.
B
I
will
go,
create
the
labels
and
the
navigation
nose
and
the
page
content
or
whenever
they
get
on
the
site.
Footer.
The
translator,
who
also
has
edit
permissions,
will
then
go
and
update
the
label
in
the
french
language
and
we
automatically
detects
that
the
user
is
French
and
they
are
trying
to
update
the
French
language
label
of
the
site
and
we
automatically
do
it
for
you
at
the
back
end.
So
this
is
the
class.
B
This
is
the
the
the
multilingual
you
mean
the
face,
the
multilingual
user
interface
experience
and
that
works
well
with
the
supported
languages
of
the
site.
As
well
so
it's
the
same
set
of
languages
that
will
be
supported
for
the
user
interface,
which
is
the
site,
navigation
label
and
names
and
such
and
the
page
content
the
language
in
which
the
pages
themselves
are
published.
There
are
say
a
question
based
on
yep.
A
Absolutely
absolutely
I
will
flip
actually
back
on
my
slides
because
we're
running
out
of
time
as
well.
There
was
a
one
comment
related
on.
Is
there
an
external
costs
related
on
translation,
and
that
depends
on
our
customers
because
and
there's
no
automatic
translation,
and
it
really
depends
on
a
customer
and
and
deployment
design
who
is
actually
doing
the
translations
and
it's
not
Microsoft
who's
doing
the
translations.
B
A
Cool
so
we're
running
out
of
time
and
there's
always
so
much
questions
to
ask
and
answer
and
like
Lisa
said:
please:
free
I
feel
free
to
reach
out
to
DC
and
it
is
DC
butter,
@dz
butter
in
Twitter
as
well,
and
we'll
definitely
keep
on
having
feature
TMP's
in
this
monthly
course.
We
unfortunately
did
run
into
the
250
s
and
they
limit
today,
as
there
was
the
problems
of
some
people
actually
getting
in
and
we're
looking
into
potential
alternative
options
on
hosting
the
cost
and
outside
of
the
team's.
A
If
that
seems
to
be
a
recurrent
issue,
I
would
say
join
early
and
then
you
will
definitely
get
the
call
right.
But
next
community
call
and
is
the
SharePoint
framework
a
community
call
on
this
Thursday.
That's
7:00
a.m.
this
Thursday
7:00
a.m.
Pacific
time
this
Thursday
at
10th
of
October
and
over
there
we're
going
to
talk
about
the
latest
in
SharePoint
framework
and
development
practices.
A
So
thank
you,
Andy
for
helping
Thank,
You
DC
on
the
on
the
awesome
presentations
and
covering
a
lot
of
ground
there,
and
also
on
the
technical
page
discussion.
That
was
a
really
interesting
thing
as
well
and
potential
future
scenarios
with
that
is
super
super
interesting.
So,
but
let's
definitely
stay
in
touch
and
thank
you
everybody
for
joining
today.
Thank
you
dizzy.
Thank
you,
Andy,
one
more
time
on
on
taking
the
lot
of
questions.
Cheers
thank.