►
From YouTube: SharePoint Monthly Community Call - April 2020
Description
April 14th PnP call hosted by @VesaJuvonen with updates from SharePoint engineering, on PnP team expansion, launch of non-dev docs site and an in-depth look at Multilingual portals with SPO. General business updates, Microsoft 365 PnP community assembled and published non-dev focused documentation on governance, features and capabilities. Reviewed top 10 SharePoint focused UserVoice requests, top 3 items to be delivered in weeks. The 2020 PnP Team increases to 26 core members. Thank you's to people and organizations for their contributions in the last month. Featured Topic – a new SPO capability for publishing and consuming content presented by DC Padur, Microsoft Program Manager @dcpadur.
Detailed agenda and links to specific call topics are available in the SharePoint Developer blog post at https://developer.microsoft.com/en-us...
If you have not already done this, download the recurrent invite for this monthly SharePoint Community call at http://aka.ms/spdev-call. Monthly calls happen on the second Tuesday of each month.
More details around SharePoint Developer Community are available at http://aka.ms/m365pnp.
A
Welcome
everybody:
this
is
chip
on
deaf
ecosystem
VMP
community
:.
It
is
April
20
2010,
the
monthly
community
call
it
is
April
14th
to
2020.
My
name
is
Sarah
I'm,
a
program
manager
in
the
Microsoft
in
the
one,
try
SharePoint
platform
team
so
today
and
we're
gonna.
Do
a
quick
recap
on
latest
news:
not
only
actually
up
our
SharePoint
Development,
definitely
mu
news
and
updates
and
summaries
and
other
stuff
and
we're
gonna
talk
about
slightly
usable
and
and
those
kind
of
things
which
we
always
do
in
the
community
course.
A
We're
also
gonna
have
a
look
on
that.
The
community
contributors
for
this
month
and
I
do
apologize.
I
have
a
slide
on
this
one
as
well.
Our
monthly
blog
post,
which
is
the
long
run
away,
will
list
what
has
happened
within
the
last
month
is
slightly
delayed
and
because
yesterday
was
the
public
holiday
I'm.
A
Writing
that
one
is
quite
time-consuming
and
then
today's
main
topic
is
building
modeling
on
portals
with
modern
SharePoint
capabilities,
and
we
have
DC
Butler
whose
to
program
program
manager
and
the
PM
owner
of
this
feature
during
the
presentation,
and
he
is
backed
up
at
least
with
Matt
muti
on
the
call
who's.
Actually,
the
engineer
genius
behind
of
the
implementation.
So
that's
how
we
work
in
Microsoft,
we
have
the
PM's
who
actually
spec
out
things
and
how
they
should
be
working
and
then
there's
the
I
would.
A
Thank
you
cool,
so
let's
actually
get
back
on
the
on
the
track
of
things
and
again
I'm
sharing
my
screen.
So
I'm
not
going
to
give
anybody
else
access
on
on
the
slides
now
and
then,
if
we
have
time
we'll
do
a
Q&A
and
and
as
well,
but
most
likely,
we
can
do
a
Q&A
during
the
DC's
presentation,
we're
going
to
follow
up
on
the
chat
window
and
please
feel
free
on
having
discussions
in
chats
I
will
jump
in
those
as
needed
as
well.
A
Now,
let's
actually
get
moving
on
the
things
stupid,
all
slides
few
things
just
to
recap,
or
let's
say
circles
of
community
and
the
different
areas
of
the
community.
We
have
the
shape
on
different
developer,
community
or
SharePoint
community
in
the
tech
community,
Microsoft
a
community
and
we
can
go
and
have
a
chat
and
questions
as
questions
from
the
BMS
as
well.
Anybody
who's
in
the
in
the
community
can
do
that.
We
also
have
our
bi-weekly
shape
on
the
framework
community
core.
A
Next
one
is
on
23rd
of
April,
where
we
actually
concentrate
on
SharePoint
frameworks
or
building
Microsoft
teams,
tabs
or
personal
applications
or
SharePoint
web
parts
and
extensions
using
SharePoint
framework,
and
then
we
have
the
bi-weekly
shape
one
general
def,
which
has
been
actually
kind
of
repositioned
to
be
a
general
Microsoft,
365
dev
bi-weekly
call
because
we
cover,
for
example,
you
know,
teams
there
and
a
few
other
things
as
well.
So
every
single
Thursday
we
have
a
community
call
at
7
a.m.
Pacific
time
y
7
a.m.
well.
A
It's
a
compromise
between
the
different
time
zones
and
trying
to
maximize
the
reach
across
the
across
the
world.
And
then
we
have
this
monthly
common
area
where
we
try
to
concentrate
more
on
the
engineering
and
protic
Roop
through
in
messaging
and
typically
have
some
PM
or
engineers
doing
a
a
Microsoft
ribbon
demo
in
this
course.
A
By
the
way
on
this
week's
church,
they
call
we
kind
of,
for
example,
talk
about
the
upcoming
taxonomy
API,
so
live
demos
of
the
Ducks
on
the
api's,
which
are
kind
of
gets,
released,
really
really
really
soon
and
a
few
other
things
as
well.
Now
quick
recap
on
the
different
at
resistors,
so
much
stuff
out
there
and
but
want
to
make
sure
that
people
actually
have
all
of
the
URLs
they
Camus
entry,
6/5
BMP
videos,
there's
some
extras
resist.
A
A
Now,
quick
recap
on
the
numbers,
so
the
community
is
growing
really
fast
and
we
do
have
a
massive
growth
in
here.
So
we
have
24%
increase
on
the
shipment
framework
usage
within
March,
which
is
quite
significant
to
be
fair
over
all
the
cloud
use
its
crew
tremendously
in
March.
Do
your
base
reasons?
We
had
almost
50,000
views
in
the
into
BMP
YouTube
channel.
We
have
247,000
watch
time
minutes
in
the
YouTube
channel
as
well,
so
plenty
of
views
plenty
of
activities
over
there.
A
It's
good
to
say
that
those
videos
are
considered
valuable
and
there
was
totally
76,000
445
visitors
in
our
key
top
organizations,
which
really
chose
the
probe
of
the
ecosystem
as
well.
So
people
are
finding
examples
or
and
our
open
source
projects,
but
I'm,
not
that
surprised,
just
in
in
general,
there's
more
than
1
million
one
developers
in
over
the
world,
so
we
can
easily
get
to
75,000
or
100,000
views
and
visitors.
A
Those
things
which
are
abstracting
the
complexity
of
API
sand
for
you
to
easily
get
access
for
more
than
forty
thousand
tenants
are
using
those
and
the
tenant
templates
provisioning
was
used
more
than
four
thousand
tenants
and
overall
we
have
1298
contributors
in
the
github
organization,
so
quite
interesting
and
also
numbers.
So
thank
you
for
being
active
from
your
side
as
well
now,
some
new
stuff.
This
is
something
which
were
it,
went
live
last
week.
A
Actually
we
used
the
SharePoint
plug
for
that
one,
because
it's
not
really
a
diff
topic
as
such,
but
as
part
of
the
the
success
on
the
dev
area
around
the
open
source
and
documentation
and
open
source
projects
and
samples.
We
want
to
actually
extend
the
similar
kind
of
mindset
and
thinking
to
non
dev
areas
as
well.
A
Let's
actually
concentrate
or
let's
centralize
the
stuff
to
one
location,
so
people
can
easily
find
it
and
it
can
absolutely
submit
the
same
article
to
your
own
clock
or
in
in
this
location
as
well,
but
this
is
really
intended
for
those
people
who
are
writing
awesome
stuff
to
get
visibility
through
the
Microsoft
channels
as
well,
a
game
as
mp3
is
desired.
Community
Docs
and
there's
a
nice
blog
post
available
from
the
SharePoint
blog
related
on
what
does
it
means
in
practice?
A
So
it's
a
reminder
also
on
our
BMP
weekly,
which
is
slightly
let's
say,
people
are
getting
more
and
more
rebranded.
It
was
called
SharePoint
dev
weekly
in
the
past,
but
we
know
there's
recovering
in
non
different
areas
in
this
course
as
well,
really
also
depends.
Who
is
our
visitor,
because
every
single
week
we
usually
have
a
MVP
or
on
normal
community
member
as
observer,
and
these
things
everything
is
available.
Obviously,
in
the
video
or
podcast
format,
quick
recap
on
the
youth
voice.
A
Let's
say
a
recap
what's
happening
in
here,
not
a
massive
amount
of
let's
say
change
this
in
here
and
the
number
one.
The
most
requested
thing
is
the
support
for
dotnet
core
of
each
season
and
and
basically
then
share
bond
and
the
powershell
after
that,
and
all
that
there
is
nothing
that's
being
actively
worked
on.
We
aren't
getting
closer
and
closer.
We
know
that
we've
been
working
on
this
one
now
for
a
few
years,
and
we
understand
that
the
ecosystem,
customers
and
partners
really
need
to
have
it.
A
A
I
would
say
almost
modern
days
rather
than
weeks,
so
so
happening
quite
quite
quite
soon
as
well
and
but
other
than
that's,
not
a
massive
amount
of
let's
say
change
this
on
the
top
list
of
deaf
areas
or
responsibility
requests
also
due
to
the
fact
of
the
of
the
covetous
situation
so
there.
Clearly,
some
of
our
development
is
slightly
slowing
down,
but
to
be
fair,
I
think,
we've
been
surprisingly
successful
on
keeping
things
running
and
keeping
keep
on
shipping
stuff
as
well,
but
bear
with
us.
A
We
will
absolutely
want
to
address
all
of
their
requests
as
well.
Quick
recap
also
on
a
really
interesting
topic,
so
we
are
crowing
our
PMP
team.
Quite
significantly,
there
will
be
a
blog
post
later
this
week,
which
is
explaining
the
model
and
explaining
the
new
people
as
well.
The
BMP
is
really
the
group
of
MVPs
and
internal
Microsoft
people
who
are
coordinating
our
open
source
and
community
efforts,
and
since
this
area
has
been
so
dramatically
crewing
within
the
past
years,
we
are
quite
significantly
also
growing
our
BMP
T.
A
What
we've
been
having
in
the
past
is
that
we
don't
have
enough
time
and
the
24/7
24
hours
in
a
day
is
not
enough
to
actually
manage
all
of
the
incoming
stuff
for
the
open
source
stuff
as
well,
so
we're
trying
to
solve
that
by
extending
D
and
also
introducing
quite
a
few
new
projects
around
the
Mike's
of
teams
as
an
example,
and
also
on
other
areas
on
on
the
SharePoint
on
one
part
as
well.
The
plot
of
people
who
are
actively
involved
in
this
in
the
future,
so
letting
everybody
know
on
that.
A
Thank
you,
part
of
it
maybe
is
for
volunteering
on
doing
these
things
as
well
through
April,
20
2008
and
the
blog
post,
which
is
listing
all
of
the
latest
changes,
and
all
of
that
stuff
is
coming
pretty
soon.
It
is
actually
pending
on
my
time
to
write
it
out.
We
have
already
all
of
the
contributors
we
have
all
of
the
components
but
really
making
sure
that
we
list
out
all
of
the
awesomeness.
A
What
you
have
contributed
is
still
missing
from
the
blog
post,
so
it
glute
around
later
today
or
tomorrow,
but
the
amount
of
companies
who've
been
already
involved
is
still
or
is
already
up,
updated
and
based
on.
We
obviously
also
updated
the
list
of
people
who
contributed
within
the
last
month
to
our
open
source
and
community
effort.
So
this
includes
contributions
to
the
documentation,
samples
and
galleries,
and,
let's
say
community
demos
and
all
that
self
is
actually
listed
in
here
and
now.
I
know
that
I
said
it
I
actually
mystery
will
I
bow
from
tree.
A
Mill
is
missing
from
this
list
and
I
do
apologize
on
that
one,
and
that
means
that
I
am
missing.
The
tree
Wells
logo
from
this
screen
as
well,
so
I
do
apologize,
I'm
done,
but
this
is
also
the
group
of
companies
with
being
closely
involved
within
our
open
source
Awards
within
the
last
month
or
those
companies
which
we
have
a
permission
to
show
their
logo
as
part
of
our
messaging
and
by
the
way
again,
I
will
add.
The
tree.
Will
logo
in
here
as
well.
A
I
do
apologize
of
missing
that
from
the
Microsoft
side
of
the
house.
The
list
of
people
is
also
growing
and
there's
nice
to
see
that
we're
getting
more
and
more
also
internal,
PA
fees
and
TSP
is
actually
contributing
an
escalation
engineers
contributing
on
our
open
source
side
of
the
house.
Obviously,
the
set
of
NPMs
and
engineers
already
who've
been
and
there
for
a
while
as
well,
but
that
was
a
quick
week.
A
Super
quick
update
because
I
didn't
want
to
take
too
much
time
on
the
presenters,
and
so
we
can
concentrate
on
the
multilingual
poros
with
the
SharePoint
Online.
Once
again,
thank
you.
Everybody
who
contributed
on
our
open
source
efforts
within
the
past
month
and
we
can
already
see
a
massive
amount
of
contributions
for
April.
So
thank
you
for
those
as
well.
We'll
definitely
keep
on
keep
on
calling
you
out
in
the
community
course
and
showing
your
names
in
the
official
blog
post
as
well,
but
I
think
that's
it
from
my
side.
B
Thank
You
Thank
You
Vera.
Thanks
for
the
introduction,
that's
that's
fantastic
great
to
hear
all
the
cool
stuff
happening
with
our
community
here
and
thank
you
for
the
invitation
to
join.
This
call.
I'm
really
excited
to
get
back
on
the
call
and
share
some
of
the
new
stuff
that
we've
been
working
on
and
do
an
actual
live
demo
walk
through
the
examples
and
answer
questions
so
I
have
a
couple
of
my
colleagues
on
the
line
Matt
Moody
has
mentioned
he's
my
technical
lead
on
this
program.
B
Since
early
on
she's
been
working
closely
with
us
and
I
have
really
appreciate
her
being
on
this
call
and
offering
to
help
answer
specific
targeted
questions,
I'm
not
watching
the
chat
window,
so
I'm
assuming
visa
Matt,
you
would
jump
in
and
answer
questions
or,
if
you
think,
I
should
address
it
widely
or
you
know
by
speaking
to
it
rather
than
just
typing
the
answers.
Please
feel
free
to
interrupt
me
at
any
time
and
we
can
get
going
with
that.
B
So,
let's
get
started
so
the
feature
we
are
here
to
talk
about
specifically,
is
the
multilingual
publishing
experience
that
just
recently
started
shipping.
This
is
for
the
modern
SharePoint
communication
sites
platform.
The
temple
here
is
gonna
focus
on
how
does
the?
How
do
we
build
an
actual
photo
using
this
feature,
so
there
is
sometimes
its.
It
helps
for
the
product
owners
to
be
able
to
place
the
feature
in
the
context
of
the
larger
end,
use
and
experience
or
the
customer
experience.
B
And
what
is
the
outcome
they
would
wish
to
drive
and
how
does
the
feature
into
the
tyre
context?
So
that's
that's
sort
of
the
goal
of
this
call
and,
of
course,
I'm
hoping
many
of
you
have
already
taken
this
feature
for
a
ride
in
your
targeted
of
leased
tenants.
This
features
right,
I
wanted
rolled
out
to
the
targeted
release
entire
organization
customers,
because
this
is
the
site
level
feature
you
can't
enable
it
for
specific
users.
So
that's
why
we
have
rolled
it
out
to
the
target
release
entire
organization
tenants,
and
it's
done.
B
We
hope
to
have
it
generally
available,
starting
in
the
next
couple
of
weeks,
hopefully
by
the
end
of
May,
it'll
be
generally
available
for
all
the
clouds,
including
the
government
clouds.
So
there's
a
more
information
link
and
I'm,
pretty
active
on
Twitter,
so
feel
free
to
hit
me
up.
I
have
several
folks
that
have
already
hit
me
up
with
feedback,
and
we
really
appreciate
that
and
we're
working
on
improving
our
documentation
and
also
take
feature
improvement
feedback
as
well
so
coming
to
the
core
of
this.
B
Essentially,
this
feature,
the
multilingual
publishing
feature
was
designed
to
help
top-level
information
portals
for
customers
to
help
them
build
that,
for
a
diverse
audience
and
by
diverse
audience,
I
mean
folks
that,
like
to
consume
content
in
their
preferred
language,
as
opposed
to
the
you
know,
typically
published
language.
There
is
always
a
language
variation,
around
information,
consumption
and
especially
in
these
times,
with
lots
of
folks
working
from
home
and
being
diverse
globally
distributed,
and
you
know
working
from
different
time
zones
and
language
barriers.
B
It's
extremely
important
to
have
a
sense
of
community
and
it's
great
for
the
internet
experience
for
those
users
to
be
available
their
language,
so
they
can
feel
connected
and
they'll
feel
like
they
belong
to
a
community,
even
though
they
are
geographically
and
linguistically
separated
in
many
kinds.
So
that's
the
goal
of
this
feature.
That's
the
scenario
we
want
to
unblock
and
we
have
a
basic
MVP.
B
It's
a
experience
that
we
have
shipped
out
with
the
publishing
experience
that
ties
in
together
and
had
delivered
a
great
experience
for
the
end
users,
along
with
the
content
creators
and
the
folks
that
set
up
the
site,
a
quick
setting
of
the
context
in
the
scope.
So
obviously
we
are
supporting
multilingual
pages
and
news
in
communication
sites.
That's
the
scope
of
the
project
right
now.
It
also
involves
so
the
site
name,
site
language,
the
site,
navigation
and
site
footer
hub
navigation.
B
All
of
these
things
too
delivers
the
internet
site
experience
and
that's
part
of
the
experience
today
that
you
can
be
working
on.
There
is
no
order
translations.
The
content
is
to
be
provided
by
the
content
owners.
So
that's
an
important
aspect
to
remember.
What
we
are
doing
here
is
enabling
the
publishing
system
that
brings
multiple
language
content
together
and
makes
it
easy
for
publishing
and
importantly
consuming
the
content
as
well.
So
we're
not
focusing
on
collaboration
scenarios
and
we
most
definitely
are
not
reinventing
variations
in
the
in
the
modern
digital
workplace
experience
we
have.
B
We
have
completely
rethought
what
it
means
to
have
a
multiple
publish
it
and
we
are
putting
our
concepts
and
our
research
focused
approach
into
our
feature.
Experience
so
going
into
the
demo
I'm
gonna.
Do
this
slightly
different,
so
I'm
going
to
start
with
the
finished
product,
walk
you
through
what
that
experience
will
looks
like
and
then
we
will
go
into
hey.
How
did
we
get
to
that
place
right?
B
So
that's
what
I
want
to
do
so,
as
you
can
see,
this
is
the
a
charge
site,
the
Human
Resources
site
for
the
best
organization,
the
most
popular
organization,
contoso,
electronics,
sponsored
by
Microsoft,
obviously,
and
you
have
the
site
that
is
showing
content
and
the
language
of
the
user,
which
in
this
case
turns
out
to
be
English.
So,
as
you
can
see,
there
is
always
a
nice
news.
Web
part
that
showcasing
news
is
a
bunch
of
links
in
there
call
out.
B
So
as
a
user,
I
do
not
have
to
remember
any
specific
URLs
the
default
site.
The
same
site
can
be
shared
with
all
of
the
users
and
based
on
the
preferred
language
of
the
end
user.
We
automatically
send
the
user
to
the
corresponding
page
that
they
requested
if
it
is
available
in
their
language.
Obviously,
the
site
has
been
set
up
in
Spanish
and
English
and
obvious
user
being
a
Spanish
user,
automatically
lands
on
the
Spanish
home
page,
and
not
only
that.
B
I
have
some
when
I'm
looking
at
the
news
articles
here
and
as
you
can
see,
if
the
news
is
available
in
my
language,
I
automatically
see
that
language
news
rolled
up,
but
for
if
some
reason
the
news
is
only
published
in
English,
and
you
only
see
the
English
language
news
showing
up
this
way.
We
make
sure
that
the
end
user
is
not
missing
out
on
content
because
it's
not
yet
published.
So
we
want
to
make
sure
that
all
available
content
is
surfaced
to
the
end-user
and
multilingual
aspect
comes
on
top
of
that.
B
So,
if
it's
available
in
your
language,
we
will
show
you
that,
as
your
preferred
experience,
so
I'm
going
to
go.
Click
on
this
first
news-
article
I'm
not
going
out
and
reading
this,
but
it's
about
new
options
for
benefits,
and
you
are
reading
this
article
in
Spanish
and
you
might
want
it
as
a
user
hey.
How
could
I
check
this
out
in
English
as
well?
And
now
you
see
that
there
is
an
affordance
for
that
on
the
top
right
side.
B
There
is
an
up-down
with
the
language
selector,
you
choose
the
English
version
of
it
and
now
oh,
this
is
the
actual
English
version
of
the
actual
of
the
news
article
that
you
are
attempting
to
read
so
from
there
on.
Do.
You
have
indicated
to
the
site
that
you
would
continue
reading
the
page
content
in
English,
you
will
see
that
the
rest
of
the
site,
Chrome,
has
maintained
the
information
architecture
of
the
site
itself
is
anchored
in
the
preferred
language.
This
language,
selector,
is
just
for
the
context
of
reading
the
content
is
switched
over
to
English.
B
You
go
back
to
the
home
page
and
now
you
will
see
that
all
of
the
content
is
now
in
English
and
I
can
continue
consuming
the
content
in
English.
Even
though
the
users
preferred
language
is
Spanish,
they
are
choosing
to
read
content
in
English
at
any
time
they
can
switch
back
to
the
available
Spanish
and
they
will
go
back
to
their
default
user
experience
and
this
were
their
default
user.
B
Experience
will
also
continue
when,
if
they
close
browser
and
come
back
to
the
site
at
a
different
time
or
in
a
different
computer,
their
default
experience
will
always
be
honored
and
the
page
level
language
selection
is
applicable
only
for
the
context
of
that
content.
So,
as
you
can
see,
this
is
the
end
user
experience
that
we
are
after.
B
We
want
to
make
sure
that
the
end
users
can
directly
land
on
the
language
experience
of
their
choice,
as
indicated
by
the
preferred
language
in
their
user
profile,
and
they
also
have
the
added
ability
to
switch
between
available
languages
when
those
content
is
published
by
the
content
creators.
So
with
that
said
now,
let's
step
into
how
did
we
get
to
this
place?
How
did
a
content
creator
get
to
this
place
and,
as
always,
the
journey
begins
with
creation
of
a
site,
so
I've
switched
over
to
another
user?
B
Who
is
an
admin
on
this
tenant
and
will
begin
the
journey
of
a
demo
site
with
the
creation
of
the
site?
Obviously,
I'm
going
to
start
with
the
communication
side,
I'm
going
to
call
this
demo
site
and
you
will
notice
that
there
is
a
select
language
option
in
the
site
creation
experience.
This
is
something
to
keep
in
mind.
It's
extremely
important
in
this
journey,
so
the
default
language
of
a
site
is
picked
at
the
creation
time
and
it
cannot
be
modified
after
the
site
has
been
created.
B
So
if
you
are
building
a
multilingual
portal
for
your
organization,
you
want
to
think
about
what
is
the
default
language
that
I
want
for
the
site
and
the
reason
it
is
important
is
any
page
or
any
news.
Article
SharePoint
news,
article
that
is
created
in
that
site
will
be
first
created
in
that
default
language
and
then
translate
it
into
the
additional
languages.
For
that
reason,
it's
important
to
remember
and
pay
attention
to
the
default
language
again.
B
For
the
ease
of
my
demo,
I'm
going
to
stick
with
the
English
language
and
I
will
pick
a
blank,
and
I
will
finish
so
within
a
matter
of
seconds
now,
you've
created
the
much
familiar
communication
site
and
it
has
the
basic
constructs
set
up.
So
what
I'm
going
to
do
as
the
owner
of
the
site
is
then
go
enable
the
multilingual
feature.
So
you
do
that
by
going
into
the
site
settings
experience.
B
As
you
all
know,
you
go
to
the
site
information
panel
and
then
go
into
view
all
site
settings
and
in
the
site
settings
you
will
notice
that
there
is
a
language
settings
option.
You
click
on
that
and
now
we
have
revamp
this
page
completely
and
that
begins
you
with
a
question
that
asked:
do
you
want
to
enable
pages
and
news,
so
this
basically
enables
pages
and
used
to
be
translated.
This
is
the
multilingual
publishing
feature
modern,
publishing
feature
that
gets
enabled.
B
Obviously
there
is
an
available
English
language
and
then
you
type
in
another
support
and
language
I'm,
going
to
pick
Spanish
I'm,
most
comfortable,
trying
to
juggle
between
Spanish
and
English,
and
as
you
notice,
there
is
an
option
for
translators.
So
this
is
the
experience
where
an
individual
site
will
have
multiple
languages
and
each
language
has
a
translator
associated
with
that
language.
Who
is
then
responsible
for
the
translation
of
the
default
language
content
into
their
language?
And
there
is
notifications
involved
by
having
this
person
in
here.
It
is
completely
an
optional
field.
B
You
can
have
a
multilingual
site
without
requiring
to
provide
a
translator,
email
but
having
a
translator.
Email
results
in
benefits
and
I'll
show
you
with
the
notification
scenarios,
what
those
are
so
I've
already
created
a
Spanish
user
Renata
who's
going
to
act
as
a
translator
in
Spanish
and,
as
you
can
see,
you
can
enable
n
number
of
these
out-of-the-box
available
languages.
Portuguese
Russian
Thai,
your
German
Korean
Japanese.
All
of
these
hours,
you
can
add
in
number
of
these
languages
and
each
of
these
languages
can
have
associated
translators
or
you
could
do
an
alternative
thing.
B
B
You
can
choose
to
have
one
or
a
few
users
or
a
security
group
office
risks
to
a
group
associated
with
every
language
in
your
organization,
and
this
is
as
far
as
the
site
owners
job
goes
so
now
the
site
owner
has
configured
this
site
to
be
multilingual,
enabled
and
selected
another
language
and
assign
the
translator
for
that
language.
So,
with
that
the
site
owners
job
is
complete,
and
now
we
can
begin
the
journey
of
what
it
means
to
start
doing
a
site
experiences
in
multiple
languages.
B
B
Home
page
and
I'm
going
to
add
another
web
part,
which
is
news
which
gives
you
a
roll
up
experience.
Typically,
the
home
page
of
large
intranet
sites.
I
now
have
roll-up
experiences,
have
static
content,
have
quick
links.
For
example,
all
of
these
things
are
translatable
for
the
sake
of
the
demo
I'm
going
to
stick
with
a
text
and
a
news,
roll-up
experience
and
one
thing
I
want
to
notice.
Whatever
the
way
that
works
in
the
news,
roll-up
is
also
how
it
typically
works
with
the
highlighted
content
web
part.
B
Both
these
web
parts
are
enabled
for
multilingual
experiences
and
I'm
going
to
show
you
what
that
means.
So
I
will
call
this
English
news
on
this
demo
site
and
I
am
done
with
setting
up
the
simple
page
on
the
site,
and
what
I
intend
to
do
here
is
engage
with
this
translations
button
here
and
yeah
as
you
notice.
This
button
showed
up
because
the
multilingual
feature
was
enabled
on
the
site.
B
You
click
on
this
and
there
is
a
panel
experience
which
tells
you
you
can
create
a
copy
of
this
page
for
the
translation
experience,
so
English
page
has
been
created
and
once
the
English
is
created,
you
then
make
a
copy
of
this
English
page
for
the
Spanish
translations,
and
that
is
what
this
panel
enables,
because
there
is
just
one
language:
I'm,
just
gonna
click
on
create
here.
What
this
create
gesture
does
is
makes
an
identical
copy
of
this.
B
With
this
content
now
I'm
going
to
switch
over
to
the
Spanish
users
mailbox
and
as
you
can
see
you
as
any,
if
you
think
about
the
flow,
the
Spanish
users
get,
the
Spanish
translator
gets
the
email
that
says
the
require
translation
has
been
requested
and
that
person
can
then
click
off
start
translating
it
okay.
This
is
an
important
thing
to
notice
that
I
missed
in
my
demo,
who
you
want
to
make
sure
that
all
translators
have
access
to
the
site
after
you've
added
them
as
a
translator.
B
So
I'm
gonna
go
back
I'm,
going
to
share
the
fact
that
you've
added
a
person
of
the
translators
does
not
automatically
give
them
share
a
shared
permissions.
So
you
want
to
make
sure
that
this,
the
translator
has
permissions
and
I'm
going
to
replay
that
I
will
start
translating,
and
this
will
basically
land.
B
The
users
can
see
the
call
out
here.
This
page
has
not
been
translated
into
Spanish,
yet
edit
to
start
and
translations.
So
as
the
Spanish
translator
of
the
site,
I
have
been
sent
to
the
Spanish
URL
for
the
home
page,
which
is
a
separate
page
and
now
I
can
just
go
edit.
This
page
and
may
Allen
called
us.
This
is
the
Spanish
homepage,
and
all
of
this
news
is
Spanish
news,
so
I
have
set
up
the
the
basic
home
page
construct
and
I
will
publish
this
page.
B
Typically,
if
the
actions
ad
don't
happen
within
a
20-minute
window,
they
will
be
a
return
notification
that
goes
to
the
site,
administer
the
the
the
English
create
a
content
creator
that
the
Spanish
translation
has
been
published,
but
I'm
going
to
continue
focusing
on
what
it
means
to
update
the
rest
of
the
page
in
here.
So
as
you
can,
as
you
will
notice,
the
the
site
name
and
all
of
the
navigation
contents
are
still
showing
English
and
let's
go
set
up.
B
The
site,
chrome
experience,
the
site
name
and
the
site
navigation
experience
as
the
English
author
first,
so
I've
switched
back
to
this
English
user.
This
English
user
is
going
to
call
it.
The
demo
site
is
fine
that
I'm
going
to
remove
the
out-of-the-box
nodes
that
show
up
with
a
communication
site
and
create
custom
nodes.
So
I'm
going
to
call
this.
B
Let's
see
top
news
how
about
that?
So
these
are
things
that
I
can
quickly
translate
off
the
top
of
my
head
in
Spanish.
So
for
the
sake
of
the
demo,
there
are
two
new
navigation
nodes
and
I'm
going
to
come
to
the
footer
here,
as
you
can
see
at
the
bottom
of
the
page,
and
there
is
a
footer
and
I
click
on
the
Edit
and
I'm
going
to
add
a
footer
item
again
I'm
just
going
to
call
it
a
head
and
so
I
don't
have
to
bother
with
the
URL
I'm
going
to
call
it
feedback.
B
B
B
If
you're
wondering
I'm
copying
it
from
a
notebook
that
I
have
already
have
all
of
this
content,
long
translation
for
top
news,
but
that's
fine,
so
I-
have
translated
the
navigation
content
and
I
will
be
translating
the
footer
content.
So,
as
you
can
see,
all
of
this
content
can
be
translated
when
a
user
with
that
corresponding
language
and
the
permissions
logs
into
the
site,
so
a
Spanish
user
logged
into
the
site
they
are.
They
have
full
control
over
this
side.
They
can
then
add
the
Spanish
labels
for
the
same
navigation
experiences.
B
B
B
So,
as
you
can
see,
this
site
is
now
the
site
name,
because
the
user's
language
is
Spanish
and
I'm
wondering
why
the
Spanish
experience
doesn't
synced
in
yet
so
the
it
typically
takes
for
a
new
site
to
sink
in
the
user
profile
information
of
users,
and
once
it
is
done,
the
the
site
language
strands
will
automatically
respond
to
the
person's
language
experience.
So,
as
you
can
see,
the
English
is
published
and
then
now
the
Spanish
page
is
available
as
well.
So
now
this
is
the
Spanish
page.
B
B
And
I
can
choose
to
say:
I
will
want
to
change
the
image.
We
have
a
wonderful
fight,
bigger
experience
and
one
thing
I
want
to
call
out
the
stock
images
that
we
recently
shipped
out
awesome
images
available
for
free
for
you
to
use
if
I
could
actually
find
the
image
there
you
go.
I
want
to
pick
this.
B
B
You
will
see
that
this
is
the
English
new
system
showing
so
because
I
am
the
Spanish
tab
logged
in
as
a
Spanish
translator,
I'm
going
to
click
on
the
Spanish
I'm
going
to
the
email
arrive
right
now
so
I'm
going
to
do
the
do
the
translation
work
right
now.
So,
as
you
can
see,
Spanish
translation
requested
for
English
used
on
the
translator
will
begin.
You
click
on
this
and
get
into
the
translation
experience.
B
So
the
same
call-out
shows
up-
and
there
is
an
info
useful
text
in
here
that
reminds
the
user-
that
this
page
requires
the
Spanish
translation,
so
I'm
going
to
try
a
translate.
That's
called
the
Spanish
use
one
sample,
Spanish
content.
Ok,
so
one
thing
I
would
like
to
do
is
maybe
for
a
Spanish
user.
I
would
prefer
to
have
a
different
background
image
than
this
green
version.
B
So
one
of
the
things
with
the
language
content
is,
and
the
architectural
approach
that
we
have
chosen
is
it
allows
for
each
of
these
individual
pages
to
be
semantically
connected
to
each
other
as
the
translations
of
each
other.
But
it
also
allows
the
individual
page
to
have
its
own
structure
and
content
that
best
suits
the
person
reading
that
content.
B
So
if
there
is
a,
if
you
can
think
of
a
world
of
an
English
page,
for
you
know
english-speaking
users
and
let's
say
an
Arabic
page
for
Arabic
speaking
users,
you
might
think
that
the
same
I
know
images
might
not
be
appropriate.
You
might
choose
to
have
different
images,
while
the
content
and
the
message
conveyed
might
be
identical.
There
might
be
some
scenarios
where
different
images
make
sense
and
that
that's
the
that
to
enable
the
such
scenarios,
we
have
come
up
with
a
model
of
making
sure
that
the
page
can
have
its
own
image.
B
So
there
is
no
tight
coupling
between
the
default
language
page
and
the
translation
page.
They
are
linguistically
connected
they're
loosely
coupled
to
make
sure
the
end-user
experience
is
seamless,
but
from
a
content
creator
point
of
view.
They
have
full
control
over
the
page
to
do
as
they
will
with
the
page
and
make
sure
that
the
best
experience
is
delivered
for
that
specific
language.
So
just
for
kicks
I'm
doing
I'm
going
to
change
this
to
a
different
image.
B
B
As
long
as
the
content
is
published
in
English
and
in
Spanish,
you
will
notice
that
the
English
content
will
roll
up
when
the
English
homepage
is
visited
and
the
Spanish
content
is
rolled
up
when
the
Spanish
page
is
visited
and
the
Spanish
page
will
automatically
be
the
default
page
for
end-users,
whose
language
the
site
is
understood
and
that
their
end
user
language
is
Spanish
and
the
user
will
automatically
be
routed
to
that
Spanish
language
content.
So
now
what
I
want
to
get
into?
B
B
So,
as
you
can
see,
all
of
this
news
is
available
in
Spanish,
so
I'm
going
to
simulate
the
experience
of
what
happens
when,
let's
say
a
page
is
updated.
So
one
of
the
important
aspects
of
having
content
in
multiple
languages
is
making
sure
that
content
is
in
sync.
You
want
to
make
sure
that,
when
an
update
is
made,
we've
seen
the
scenario
where
the
first
time
a
default
language
page
is
created
and
the
translation
is
kicked
off.
There
is
a
notification
that
goes
to
the
translator,
informing
them
that
a
translation
is
required.
B
B
I
am
the
the
English
author
of
this
page,
so
I'm
going
into
this
page
in
here
and
I
am
going
to
edit
this
and
say
please
stop
by
HR
officers
to
pick
up
401
k,
so
I'm
going
to
edit
this
to
say
by
a
end
of
month,
April
2020
to
pick
up.
So
this
is
an
important
update.
I
think
it
is
important,
so
I've
made
this
update
and
I
now
I've
saved
this
new
update
and
making
sure
that
I
have
the
right
updates
done
and
I
will
go
ahead
and
then
update
the
news.
B
B
If
you
did
not
notice
this
I
actually
clicked
this
item
here
in
the
email
is
a
hyperlink
to
the
the
default
language
content,
I
clicked
on
it
and
it
loaded
the
default
language
page
and
what
I
can
do
is
I
can
I
I'm
on
the
English
page
in
here,
I
clicked
on
the
page
details
and
at
the
bottom
there
is
the
page
differing
experience.
The
visual
page
dipping
experience
that
we
recently
shipped
out
if
the
struggle
means
that
I
can
look
at
it
visually.
B
An
important
update
and
I
would
then
go
back
update
the
translation,
which
will
bring
me
into
the
the
Spanish
version
of
the
page
and
I
would
I'm
just
gonna
call
this
updated
or
eight,
so
just
just
to
I
can't
figure
out
where
to
add
the
Spanish
translation,
so
I'm
just
gonna
do
this
and
I
can
go
ahead
and
publish
this
page.
So
this
is
the
making
sure
that
content
is
aligned
is
again,
individual
pages
can
have
their
own
journey
and
not
all
changes
are
required
to
be
applied.
B
B
So
typically,
all
of
these
notifications
and
changes
happen
on
a
longer
time
scale
than
a
40
minute
demo
window
that
I'm
having
here
so
I'm
I'm
piecemealing
the
experience
together,
but
typically
over
a
page
creation,
takes
over
a
period
of
time
and
once
the
translator
is
notified,
the
translator
is
gonna,
take
X
amount
of
time
before
they
actually
engage
with
this.
So
what
we've
done
from
a
system
point
of
view
is
we've
engineered
some
level
of
heuristic
intelligence
to
make
sure
that
there
is
not
too
much
noise
with
notification.
B
So
that
is
why,
within
a
20-minute
window,
you
will
not
see
too
many
notifications
to
the
same
user.
So
we
want
to
make
sure
that
if,
if
a
person
is
making
changes
and
saving
the
page,
there
isn't
a
constant
stream
of
pages
updated
emails
going
to
the
end
user.
We
want
to
make
sure
that
there
is
a
level
of
batching
logic
associated
with
this
experience,
so
the
translators
can
be
notified
at
an
appropriate
time
or
the
page
creators
can
be
the
outcome.
B
B
So
this
is
the
completion
of
their
experience
where
the
the
primary
page
was
created,
the
default
language
page
was
created
and
it
was
then
submitted
for
translation
and
then
the
translation
was
completed
and
now
you
will
go
and
see
that
the
Spanish
translation
was
published.
This
is
the
email
you
can
expect
when
the
translation
has
been
published
and
the
page
creator
will
be
notified
that
the
Spanish
translation
has
been
published.
B
So
just
to
recap,
the
scenarios
end
to
end,
so
you
would
see,
and
just
like
the
site,
navigation
and
the
site
footer,
you
will
also
be
able
to
have
a
multilingual
experience
for
the
hub
navigation.
So
so,
as
the
English
author
I
am
able
to
come
and
set
up
the
the
full
navigation
in
the
English
language
and
the
same
site,
you
login
as
the
Spanish
author
and
then
you
will
be
able
to
edit
and
add
the
Spanish
labels
to
the
same
navigation
nodes
for
the
hub
navigation.
B
So
essentially
with
the
combination
of
hub
navigation
site
navigation,
site,
name
pages
and
news
being
available
in
multiple
languages
and
the
footer
also
available
in
multiple
languages.
You
now
have
a
cohesive,
multilingual
site
experience
that
can
be
presented
to
your
end.
Users
and
the
end
users
will
make
sure
that
the
preferred
language
content
is
automatically
provided
when
that
language
is
published
and
individual
end-users
can
switch
between
available
languages
using
this
drop-down
experience
and
for
the
creators
when
a
page
is
created,
translate
and
an
translations
are
requested.
B
The
translators
are
notified
once
the
translations
are
published,
the
page
creators
are
notified
and
if
the
default
language
page
is
updated
with
new
content,
the
translators
are
also
are
notified.
In
that
scenario,
I'm
making
sure
that
the
content
can
be
kept
and
sync
across
the
multiple
languages
and
as
I
mentioned
here
is
the
example.
So
you
in
the
English
page
there
is
the
Quick
Links
web
part,
which
is
all
in
English
and
typically.
B
B
A
Pretty
much
that
you
were
covering
pretty
much
all
of
the
questions
actively
on
the
chat
so
that
one's
really
well
and
you
by
the
way,
get
a
lot
of
feedback
on
that
great
demo
and
walked
you
off
the
feature.
I
think
it's
it's
it's
a
great
feature,
absolutely
a
few
questions.
They
say:
there's
a
comments
related
on
deleting
so
there
was
a
comment
related
on
if,
if
the
source
file
is
deleted
or
we
actually
didn't
enter
the
copies,
but
that's
not
the
case
right.
Yes,.
B
So,
yes,
you
know
the
system
does
not
automatically
delete
the
content.
If
the
default
language
page
is
deleted.
Obviously
the
other
pages
are
sort
of
orphaned.
They
do
not
have
a
default
page,
but
the
content
itself
will
remain
in
there.
So
we
will
not
be.
The
system
will
not
delete
content
even
if
the
languages
are
removed,
for
example,
if
if
the
Spanish
language
is
removed
from
the
the
site
experience,
the
Spanish
pages
themselves
are
not
deleted
going
forward.
B
Spanish
will
not
be
supported
as
a
language
for
translation,
but
previously
translated
content
will
just
remain
in
there.
It'll
still
be
available
for
end-users
to
read
and
get
it
and
you
know,
get
access
as
long
as
those
permissions
have
not
been
removed,
but
the
content
itself
will
not
be
deleted.
Yep
now,.
A
There's
a
good
question
from
jack
related
on
demo
on
a
hub
side
and
org
site
and
an
organization-wide
side,
so
to
be
clear
in
a
hub
side,
work
site,
any
site
can
be
enabled
to
be
a
hub
sign
or
disabled
to
be
a
hub
site
and
all
of
these
features,
what
we're
seeing
here
works
on
any
communication
site.
Yes,.
B
That
is
correct,
yes,
correct
exactly,
and
one
thing
I
will
also
call
it.
The
fact
that
this
site
is
a
hub
does
not
mean
that
all
the
Associated
sites
are
also
automatically
multilingual
enabled.
So
the
multilingual
enablement
is
at
an
individual
site
scope
level,
so
the
hub
is
the
hub
allows
you
to
connect
a
bunch
of
sites
together
for
a
cohesive
navigation
and
IA
experienced.
So
if
you
want
a
multilingual
experience
in
your
entire
hub,
you
will
have
to
go.
B
Enable
the
languages
appropriate
language
in
across
every
site
individually,
and
the
reason
we
are
not
I
will
be
taking
feedback
on
this.
One
we'd
love
to
hear
thoughts
around
this.
So
it's
not
that
all
the
sites
in
the
same
hub
will
have
the
same
set
of
languages.
It's
possible
that
there
is
a
you
know,
a
site
with
English
and
Spanish.
Something
else
would
be
Spanish
and
German,
and
some
other
side
would
be.
You
know
you
know
English,
German
and
Korean.
B
For
example,
it's
possible
that
multiple
sites
have
multiple
languages
depending
on
the
content
it's
trying
to
serve
and
the
audience
it
is
intended
for.
But
the
hub
will
make
sure
that
when
a
user
lands
on
this
the
home
page
of
the
hub
site,
they
get
the
language
experience
of
their
preferred
language.
B
But
English
language
is
typically
preferred
whenever
it's
available,
it's
a
historic
construct
of
sharepoint
and
again
that's
another
scenario
where
we
are
taking
feedback,
but
in
general
the
web
default
language
will
be
shown
to
a
user
if
their,
if
their
preferred
language
is
not
available.
For
example,
if
a
Spanish
user
lands
on
a
site,
that's
enabled
only
for
Spanish
and
Joe
I
mean
a
German
and
Korean
and
German
is
a
default.
The
Spanish
user
will
end
up
seeing
the
German
language
experience,
because
that
is
the
site
default
language
experience.
A
B
It
can
be
multilingual
as
well,
and
it
can
also
be
have
enabled
all
of
that
is
true,
so
recapping
here,
so
we
all
will
be
generally
available.
Hopefully
by
the
we
were
working
on
rolling
it
out.
It
takes
a
few
weeks
for
the
rollout
to
complete
so
by
end
of
May.
All
of
you
should
have
this
feature
and
we'll
look
forward
to
engaging
with
you
all
and
getting
feedback
and
look
forward
to
the
usage.
A
You
yep
thank
you.
Everybody
discussion
on
the
chat
window,
few
slides
just
to
recap
on
on
the
things,
because
these
things
are
coming
up:
no
time
for
Q&A.
On
top
of
what
we
were
having
the
recording
will
be
available
in
24
hours
in
our
mics
racist
violence
shape
one
community
YouTube
channel
again,
as
in
365
EMP
videos.
We
have
now
more
paths
to
15,000
subscribers
on
that
one.
So
there's
plenty
of
relevant
content
over
there
as
well.
A
All
of
the
community
calls
are
recorded
and
published
through
the
YouTube
channel.
So
just
to
recap
on
that
as
well.
But
that's
it
from
our
site
and
we
do
have
plenty
of
community
calls.
We
know
that
we
have
plenty
of
community
calls
and
follow
up
on
the
YouTube
channels
on
the
recordings
which
are
the
ones
which
you
actually
wanted
to
pop
in
and
drop
by,
and
thank
you
for
being
again
being
super
active
on
this
call
and
by
the
way
for
those
who
are
watching
the
recording
we
do
apologize.
A
We
hit
at
the
end
250
attend
a
limit,
so
some
people
could
not,
unfortunately,
get
in
to
the
call
we're
trying
to
figure
out
how
to
make
that
happen.
In
the
future.
There
are
certain
scenarios
and
the
limitations
even
with
Microsoft
Ames
events
and
that's
the
reason
why
we
haven't
actually
started
doing
that
we'll
do
that
in
the
future,
but
that's
it
from
our
site.
Thank
you,
everybody
for
joining
and
have
a
great
rest
of
your
day
and
stay
safe
and
hopeful
we'll
see
you
in
the
upcoming
community
costs.