►
Description
In this 41-minute demo targeted to site owners, Microsoft Program Manager - DC Padur, helps viewers appreciate how Multi-Lingual Publishing (MLP) for modern SharePoint delivers a cohesive multilingual site experience for publishers and end-users. This new capability makes it easier for publishers to systematically deliver information in other languages. For users, the capability presents options for locating content in the language they are more comfortable. The system assists the publisher with organizing/managing multi-lingual pages, news, navigation, and as well delivering actionable notifications to keep the single multi-language site-in-sync. General Availability rollout begins in May with availability in all clouds including government by end-of-May, 2020. End-to-end configuration and usage shown in demo.
This PnP community demo is taken from the monthly SharePoint Community (PnP) call recorded on April 14, 2020.
Presenter: DC Padur (Microsoft) | @dcpadur
Supporting materials:
• Create multilingual communication sites, pages, and news |
http://spo.ms/MLP
All SharePoint PnP Developer Community demos: https://www.youtube.com/playlist?list=PLR9nK3mnD-OWSbg0o9a7mx_E7s2u7h_o2
Learn more about the SharePoint developer community at: http://aka.ms/m365pnp.
A
Thank
you
for
the
invitation
to
join
this
call.
I'm
really
excited
to
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.
A
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.
A
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
example
here
is
gonna
focus
on
how
does
the?
How
do
we
build
an
actual
photo
using
this
feature,
so
they
sometimes
it's?
It
helps
for
the
product
owners
to
be
able
to
place
the
feature
in
the
context
of
the
large
end-user
experience
or
the
customer
experience.
A
And
what
does
the
outcome
they
would
wish
to
drive
and
how
does
the
feature
fit
into
the
tyre
context?
So
that's
that's
sort
of
the
goal
of
this
call
and,
of
course,
I'm
hoping
when
a
few
have
already
taken
this
feature
for
a
ride
in
your
targeted
to
release
tenants.
This
feature
right
now
already
rolled
out
to
the
targeted
release
entire
organization
customers,
because
this
is
the
site
level
feature
you
can't
for
specific
users.
So
that's
why
we
have
rolled
it
out
to
the
target
release
entire
organization
tenants,
and
it's
done.
A
We
hope
to
have
a
generally
available
starting
in
the
next
couple
of
weeks.
Hopefully
by
the
end
of
May,
it
will
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.
A
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
in
a
working
from
different
time
zones
and
language
barriers.
A
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.
A
It's
a
experience
that
we
have
shipped
out
with
the
publishing
experience
that
ties
in
together
and
her
delivers
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're
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.
All
of
these
things
together
delivers
the
internet
site.
A
Experience
and
that's
part
of
the
experience
today
that
you
can
be
working
on
there
is
no
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.
A
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
neighbor
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?
A
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
all.
Is
a
nice
news
web
part
that
showcasing
news
is
a
bunch
of
links
in
there
call
out.
A
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,
this
site
has
been
set
up
in
Spanish
and
English
and
obvious
this
user,
being
a
Spanish
user,
automatically
lands
on
the
Spanish
homepage,
and
not
only
that.
A
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
surface
to
the
end
user
and
multilingual
aspect
comes
on
top
of
that.
A
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.
There
is
a
pop
down
with
the
language
selected.
A
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've
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.
A
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
prefer
languages
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
was
their
default
user.
A
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.
A
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?
A
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
who's,
an
admin
on
this
tenant
and
we'll
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.
A
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.
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.
A
For
that
reason,
it's
important
to
remember
and
pay
attention
to
the
default
language
again
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
with
that
matter.
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.
A
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.
A
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.
A
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
what
the
notification
scenarios,
what
those
are
so
I've
already
created
a
Spanish
user
Renata
who's
going
to
act
as
a
translator
for
Spanish
and,
as
you
can
see,
you
can
enable
n
number
of
these
out
of
the
box
available
languages,
Portuguese
Russian
Thai.
You
have
German
Korean
Japanese
all
of
these
hours.
A
You
can
add
in
number
of
these
languages
and
each
of
these
languages
can
have
associated
translators
or
you
could
do
an
alternative
thing.
You
can
have
all
translators
in
a
security
group
and
just
basically
add
that
security
group
to
all
the
languages.
So
all
all
translators
get
the
notification
about
all
languages.
It
might
not
be
preferred
in
some
Sanaa,
yes,
but
that
flexibility
is
or
is
completely
in
your
hands.
A
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
assigned
a
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
site
experiences
in
multiple
languages.
A
A
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
internet
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
note-
is
whatever
the
way
that
works
in
the
news.
Roll-Up
is
also
how
it
typically
works
with
the
highlighted
content
web
part.
A
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.
A
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
page
is
created.
You
then
make
a
copy
of
this
English
page
for
the
Spanish
translations,
and
that
is
what
this
panel
nimble's,
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.
A
English
page
puts
it
in
a
special
folder
for
the
Spanish
language
and
makes
that
available
for
the
Spanish
user
to
continue
translations.
If
you
all
notice,
there
was
a
soft
pink
sound,
and
that
is
the
sound
of
my
email
that
was
sent
out
so
I'm
going
to
switch
to
the
email
tab
and,
as
you
can
see,
the
email
was
sent
to
Renata,
who
is
a
translator
for
the
Spanish
language
and
it's
a
Spanish
translation
is
requested
so
because
the
the
English
admin
who's
created
the
page
and
requested
the
translation.
A
The
Spanish
translator
received
the
email
so
I'm
going
to
go
ahead
and
complete
the
English
content
creators,
job,
which
is
actually
publishing
the
home
page.
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.
A
This
is
an
important
thing
to
notice
that
I
missed
in
my
demo,
so
you
want
to
make
sure
that
all
translators
have
access
to
the
site
after
you've
added
them
as
a
translator.
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
sharing
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.
A
The
users
can
see
the
call
out
here.
This
page
has
not
been
translated
into
Spanish,
yet
edit
to
start
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
even
call
this,
the
sirs,
the
Spanish
homepage
and
all
of
this
news
is
Spanish
news,
so
I
have
set
up
the
the
basic
homepage.
Construct
and
I
will
publish
this
page.
A
Typically,
if
the
actions
don't
happen
within
a
20-minute
window,
they
will
be
a
return
notification
that
goes
to
the
side
administered.
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.
A
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.
A
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
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.
A
A
A
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
these
content
can
be
translated
when
a
user
with
that
corresponding
language
and
the
permissions
logs
in
to
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.
A
A
A
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
trans
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.
A
A
And
I
can
choose
to
say:
I
will
want
to
change
the
image.
We
have
a
wonderful
five,
bigger
experience
and
one
thing
I
want
to
call
out
with
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.
A
A
You
will
see
that
this
is
the
English
news
is
still
showing
so
because
I
am
the
Spanish
I
have
logged
in
as
a
Spanish
translator,
I'm
going
to
click
on
the
Spanish
I'm
going
to
throw
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.
A
So
the
same
call-out
shows
up-
and
there
is
an
useful
text
in
here
that
reminds
the
user-
that
this
page
requires
the
Spanish
translation,
so
I'm
going
to
try
a
translator,
that's
called
the
Spanish
use
one
sample,
Spanish
content.
Okay,
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.
A
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.
A
So
if
there
is,
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's
the
third
to
enable
that
such
scenarios,
we
have
come
up
with
a
model
of
making
sure
that
the
page
can
have
its
own
image.
A
So
there
is
no
tight
coupling
between
the
default
language
page
and
the
translation
page.
They
are
linguistic,
connected
they're,
loosely
coupled
to
make
sure
the
end-user
experience
is
seamless,
but
from
a
content
created
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
am
going
I'm
going
to
change
this
to
a
different
image.
A
A
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
at
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?
A
A
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.
A
A
A
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
offices
to
pick
up
401
K,
so
I'm
going
to
edit
this
to
say
by
a
end
of
month,
April
2022
pickup.
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.
A
A
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,
differing
experience
that
we
recently
shipped
out.
If
the
struggle
means
that
I
can
look
at
it
visually.
A
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
later
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.
A
A
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.
A
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
a
person
is
making
changes
and
saving
the
page,
there
is
an
accountant
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.
Our
the
page
creators
can
be
the
outcome.
A
A
So
this
is
the
completion
of
the
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.
A
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.
A
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.
A
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.
A
A
B
Pretty
much
I
thought
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
they
actually
intend
to
the
copies,
but
that's
not
the
case
right.
Yes,.
A
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.
A
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,.
B
There
is
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
site
or
a
network
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,
person
on
any
communication
side.
A
Yes,
that
is
correct.
Yes,
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
enable
meant
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
experience.
So
if
you
want
a
multilingual
experience
in
your
entire
hub,
you
will
have
to
go.
A
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.
A
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
homepage
of
the
hub
site,
they
get
the
language
experience
of
their
preferred
languages.
The
preferred
language
experience
which
includes
the
hub
navigation
site
navigation
and
the
site
footer,
and
the
news
and
the
pages
if
they
are
available
in
their
language,
will
automatically
roll
up.
And
if
it's
not
available,
the
default
language
of
the
web
will
be.
A
As
shown
and
there's
caveat
there
was
they
with
the
English
language,
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
injure
I
mean
a
German
and
Korean
and
German
is
a
default.
A
B
A
It
can
be
multilingual
as
well,
and
you
can
also
be
have
been
able.
All
of
that
is
true,
so
recapping
here,
so
we
will
be
generally
available,
hopefully
by
the
we
were
working
or
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.