►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 9th of May. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI, Reusable SPFx controls and PnP SPFx Yeoman extension.
Detailed covered content from SharePoint Dev Blog at http://aka.ms/spdev-blog.
- Vesa Juvonen (Microsoft) – @vesajuvonen - Preview on building Office add-ins using SharePoint Framework (10:22)
- Demo - Kyle Schaeffer (Spiritous) - @kyleschaeffer - My Bookmarks extension - Failed due to recording issue (28:23)
- Demo - Julie Turner (Sympraxis Consulting) – @jfj1997 - Custom multilingual page solution implemented using SharePoint Framework (28:40)
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
You can find more details around the open-source and community work from http://aka.ms/sppnp
A
A
It's
a
really
neat
thing:
it's
got
a
couple,
different
components
so
excited
to
see
both
of
those
and
then
as
well.
Part
of
phases,
update
I
believe
is
gonna,
be
some
of
the
demos
from
build
which
he
was
attending
this
week.
Just
a
quick
note,
we
often
get
asked:
why
aren't
we
using
Microsoft
teams?
A
We
will
use
Microsoft
teams
just
as
soon
as
it
supports
all
the
things
we
need
it
to
support
in
terms
of
doing
these
sessions,
which
involves
being
able
to
promote
certain
people
to
be
presenters
and
then
letting
folks
outside
of
our
organization,
be
presenters
and
be
promoted.
So
there's
a
few
limitations,
we're
waiting
for
those
to
be
resolved
and
we
will
move
to
teams
just
as
soon
as
we
can
so
a
few
opportunities
to
participate
in
the
patterns
and
practices.
A
You
can
always
demo
anything
SPF
X,
so
that
could
be
a
web
part,
an
application
customizer
something
around
provisioning
or
anything.
You
might
create
related
to
SPF
X.
We're
always
excited
to
see
those
as
well
the
at
P
and
P
stuff,
so
always
neat
to
see
the
demos
so
on
p.m.
PJs,
the
CLI
or
usable
controls,
or
things
related
to
the
yeoman
generator.
Of
course,
those
play
well
with
SPF
X
demos.
So
it's
a
great
way
to
combine
a
lot
of
stuff
into
a
very
cool
demo.
A
We've
seen
a
lot
of
that
already
in
the
past
and
I'm
sure
we'll
see
much
more
of
that
in
the
future.
But
it's
very
exciting
to
see
the
demos
and,
like
I've,
said
many
many
times,
I
think
the
demos
are
one
of
those
movies
call,
because
we
really
do
get
a
chance
to
see
a
lot
of
the
great
work
you
all
are
doing
out
there
in
the
community,
which
I
think
is
particularly
interesting
to
me
to
see
and
I
think
as
well
to
everybody
else.
A
You
can
also,
of
course,
contribute
on
github
lots
of
ways
to
contribute
on
github.
You
can
report
issues,
you
can
submit
pull
requests
and
then
as
well.
You
can
help
if
you
see
issues
or
questions
that
you
might
be
able
to
help
out
an
answer
you
can
always
jump
in
and
your
help
is
always
welcome
on
those
issues.
A
So
that
could
be
about
these
calls
that
we
do
about
documentation,
needs
get
AB
feedback
about
other
places
we
can
help
or
how
we
can
make
it
easier
for
you
all
to
help
and
get
involved.
We're
always
looking
at
ways
to
smooth
that
path
and
then
as
well.
Positive
feedback
is
okay
too.
We
do
get
a
lot
of
will
say:
constructive
feedback
but
positive
feedback.
So
it's
good
to
hear
as
well
about
what
you
all
like
about
what
we're
doing,
because
it
does
help
us.
A
You
know
again
do
more
of
the
things
people
like,
as
opposed
to
just
not
doing
the
people
the
things
people
don't
like
so
appreciate.
All
the
feedback
appreciate
everybody's
help
across
all
of
hip-hop
and
then
again,
thank
you
to
everybody
who
puts
together
the
demos
for
these
calls.
So
our
updates,
VESA,
I,
think
you're
back
on
the
call
yeah.
B
I'm
here
I'm
here,
so
so
from
the
Shepherd
engineering
side-
let's
see
oh
there's,
I
will
actually
get
to
move
slice
moving.
So,
first
of
all
quick
recap:
a
chemist,
a
dip
Docs
the
documentation,
a
chemist
says:
they'd
have
videos
all
of
the
recordings.
The
community
coils
dimmers
everything
else
available
out
there.
It
actually
crossed
10000
subscribers
last
week,
which
is
a
pretty
cool
achievement
and
after
that,
there's
already
200
additional
subscribers
on
that
YouTube
channel.
So,
apparently
people
are
finding
that
much
really
useful.
B
You
cannot
find
all
of
the
getting
started
on
SharePoint
framework
development,
tutorials
free
material
available
on
there
as
well
and
then
SharePoint
of
issues.
Anything
related
on
SharePoint
development.
Apa
is
Chevron
framework.
You
can
run
into
something
please
please
let
us
know
and
open
up
an
issue
in
the
SPF
issue
list,
so
we're
able
to
start
addressing
that
internally
and
on
the
quick
note
on
that
one.
B
So
every
single
issue
on
that
the
issue
list
is
getting
redirected
and
copied
to
our
internal
engineering
systems,
and
that
is
precisely
why
we
want
you
to
use
that
issue
list,
so
we
actually
get
it
inside
of
our
official
process
as
long
as
we
open
up
and
to
issue
in
the
issue
list.
So
please
please,
please
let
us
know
over
there
now,
a
few
other
few
updates
from
the
engineering
side.
So,
first
of
all,
as
Shere
Khan
favorite
usage
crowing
crowing
strong,
we
did
have
a.
B
We
can
see
a
let's
say
a
normal
spring
break
around
the
eastern
time
frame.
You
can
actually
see
that
on
the
usage,
but
again
on
Monday
this
week
we
did
a
all-time
record
and
in
both
users,
tenants
and
actual
users
on
a
SharePoint
framework
in
SharePoint,
Online
or
in
office
365
in
general,
so
in
the
usage
is
way
out
of
any
metrics
and
any
estimate
Asians,
which
were
thinking
of
having
SharePoint
framework
at
two
years
after
it
has
been
released.
B
So
adoption
has
been
tremendous
and
thank
you
for
everybody
for
contributing
also
on
the
success
as
well,
because
your
input
is
trading.
The
next
steps
off
to
Japan
framework,
so
super
important
thing,
quick
updates.
What
has
happened
so
last
week
we
released
actually
this
week,
I
think
it
was
Tuesday
and
we
pushed
out
SharePoint
framework.
One
point
eight
point
two
and
this
one
was
a
small
maintenance
release,
but
it
actually
did
also
include
official
support
from
no
J's
version,
10
and
few
other
adjustments,
so
they
will
say
a
few.
B
Let's
say:
regressions,
requestion,
xin
1.8,
release
of
SharePoint
framework
and
which
so
we're
now
getting
a
trust
with
the
small
releases.
1.9
release
is
currently
planned
to
happen
in
early
June,
so
that
is
slightly
always
well.
It
depends
on
what
I
we
find
and
what
are
the
issues
which
we
are
able
to
address?
What's
really
cool
about?
B
One
point:
eight
point:
two:
it
also
exists
some
of
the
requests
and
understandable
requests
related
on
as
your
ad
and
crafts
usage
from,
for
example,
from
Microsoft,
Eames,
desktop
client
and
mobile
clients,
so
all
of
that
functionality
should
be
now
working
properly.
So
you
are
able
to
use
craft
api's
through
SharePoint
brain
work,
using
themes,
themes,
mobile
client
or
themes,
desktop
client
and
so
on.
B
So
that
should
be
really
really
create
change
on
the
official
support
on
noches
Thank
You
Oscar
for
asking
that
so
eight
is
still
fully
supported,
but
sooner
or
later
beneath
we
will
reduce
the
support
for
noches
to
eight.
So
looking
into
moving
to
ten
should
be
the
right
way
of
thinking
this
and
it
doesn't
actually
change
anything
inside
of
the
solution
for
you,
so
everything
should
be
working
as
long
as
you're
upgrading
to
the
latest
version
of
SharePoint
framework
and
if
you're
looking
into
doing
tasks,
please
have
a
look
on
to
office.
B
365
CLI,
because
it
has,
it
will
give
you
step
by
step
guidance
on
how
do
I
upgrade
from
whatever
versions
you
are
using
to
the
latest
version
of
SharePoint
framework,
a
few
kind
of
an
updates
on
the
roadmap
side
of
the
things
so
obvious.
The
one
point
eight
point
two
point
light
this
week.
One
point:
nine
is
now
planned
to
go,
live
in
early
June
and
we're
moving
into
this
model
where
we
want
to
actually
release
a
one
version
once
a
month.
B
So,
basically,
if
a
functionality
or
feature
inside
of
engineering
is
not
ready,
then
it's
going
to
be
postponed
from
next
month,
but
we
will
looking
into
doing
this
kind
of
unknown
cadence
on
release
in
SharePoint
framework.
Now
that
how
about
I
put
it?
It's
more
mature
and
the
basic
scenarios
which
were
planned
to
do
the
initial
scenarios
are
already
there.
So
now
we're
moving
more
on
this
additional
once
a
month.
B
Let's
add
additional
value,
additional
capabilities,
extensibility
and
all
of
that
in,
and
you
will
then
know
when
the
new
version
is
always
coming,
which
will
probably
help
you
to
manage
your
internal
processes
as
well.
So
that's
something
which
we've
been
to
go
well
to
do
it
as
soon
or
later,
anyway,
on
SharePoint
framework,
additional
content,
extension,
placeholders
content,
security
policy,
open
sourcing,
artworks,
yeoman
generator,
but
that's
one.
We
don't
have
a
timing,
we're
looking
into
doing
that
as
well,
and
that
one
then
will
impact
on
the
on
the
existing
BMP
yeoman
generator.
B
So
we'll
figure
out.
How
do
we
do
those
together
as
well
store
an
absolute
story
for
SharePoint
framework
is
in
progress
as
well,
and
I
can't
give
you
any
actual
insights
on
that
one,
but
it
is
actually
progressing,
and
so
we
get
that
one
sorted
out
hopefully
within
I
would
have
got
it
in
months
rather
than
any
years.
B
Finally,
getting
to
the
moment
where
you
can
build
your
own
SharePoint
framework,
our
solutions
and
put
it
in
the
store
and
then
offer
that
for
the
customers
using
the
SharePoint
device,
and
then
that's
really
cool
thing
more
detail.
So
there's
not
that
one
whenever
we
can
share
more
additional
things.
B
So
now
we're
looking
into
extending
this
to
office
add-ins-
and
this
is
a
relatively
early
rough
demo,
but
it
gives
you
the
idea
where
we
are
with
this
one.
We
are
actually
already
at
the
moment
or
of
these
things
barely
working
also
already
in
desktop
clients,
but
we're
adding
additional
capabilities
like
Outlook,
adding
built
using
SPF
X
before
we
can
release
this
one
for
you,
but
relatively
simple
demo.
I
can
see
that
people
can
actually
see
from
the
conversation
that
you
can
symma
screen
Patrick.
Just
out
of
curiosity,
can
you
get
it
as
well.
A
B
B
Can
earth
do
a
search
on
the
documents
and
do
a
search
and
it
will
actually
highlight,
and
then
the
text
in
the
document
so
we're
using
office
chairs
inside
of
the
inside
of
the
of
the
SharePoint
framework
solution
to
talk
directly
to
the
document
and
then
also
our
concluded
a
replace
view.
So
this
is
again
a
SharePoint
framework
web
part
technically
right
now,
but
it's
going
to
be
called
something
else.
Whenever
we
get
to
that
moment
and
I
can
do
something
like
let's
flip
Earth
to
Mars.
B
Hopefully
it
doesn't
happen
and
I
can
actually
do
those
replacements
for
that
didn't
work
out
that
well,
but
let
me
actually
show
the
other
one
or
I
can
actually
communicate
to
SharePoint
Online
by
clicking
to
get
codewords.
So
all
of
the
connectivity
between
your
tenant
is
available
all
of
the
craft
API
access
all
of
the
management.
B
All
of
the
simple
deployment
all
of
the
the
azure
ad
securely
call
Apple
API,
is
all
of
that
is
available
in
his
panels
as
well
as
long
as
you're
authenticated
against
your
tenant,
now
you're
able
to
authenticate
and
operate
this
top,
and
in
this
case,
let's
do
something
simple.
You
can
see
here:
somebody's
using
most
2007
words
or
MS
exchange,
and
those
are
not
official
word
so
I
can
absolutely
do
a
replacement,
and
that
will
then
change
the
code
word
based
on
that
mapping.
So
the
most
has
been
change
which
office
office
sharepoint
server.
B
Here
we
go
2007
and
then
there
was
much
of
a
mess.
Exchange
has
been
changed,
marshal
testings,
simple,
the
most
a
relatively
rough
demo
like
mentioned,
but
this
basically
shows
that
we're
using
two
office
chairs
inside
of
the
SharePoint
framework
solution,
and
then
we
are
able
to
communicate
between
the
the
office
documents
and
also
whenever
we
get
this
live.
Also,
together
with
you
can
use
SharePoint
framework
to
build
office.
Sorry
outlook
add-ins
as
well,
so
you
can
easily
build
this
office
silence
without
worrying
deployment,
without
boring
hosting,
without
worrying
to
typical
challenges.
B
What
people
are
having,
which
is,
which
is
by
the
way,
exactly
the
same
reasons
why
we
introduced
the
shape
types
of
teams
with
SharePoint
framework,
so
don't
have
to
worry
about
the
deployment
hosting
management
governance
and
all
of
that
because
or
everything
is
taken
care
of
by
the
SharePoint
framework
capabilities
now,
potentially
I
can't
promise
this
for
sure
we're
looking
into
getting
this
one.
We're
planning
indicating
this
one
as
a
release.
That's
part
to
preview
as
part
of
the
1.9
release,
and
then
your
feedback
is
super
important.
So
we
need
to
understand.
B
Is
it
an
interesting
scenario?
Is
it
something
what
you
would
be
would
make
you
feel
more
interested
on
building
office
add-ins
if
you
can
actually
use
the
same
code
base
and
same
technologies
for
those
as
well,
and
obviously
did
this
one
is
a
contextual
implementation.
So,
in
the
same
way
as
with
Microsoft
teams
tabs,
you
can
I
get
access
on
the
document
you
can.
B
You
know
always
that
they
might
hosted
us
a
web
part
in
a
SharePoint
page
as
a
march
of
team's
time,
or
it
might
actually
hosted
as
a
task
pane
in
this
case
and
also
the
context
of
contact
contextual.
What
are
the
contents?
Add-Ins
are
contagious,
reported
as
well
they're
able
to
have
added
inside
of
the
of
the
documents,
so
that's
really
pretty
cool
as
well,
but
whenever
we
get
to
the
preview
I've
mentioned
I'm
going
to
stop
recording,
I'm
sorry
I'm
sharing
whenever
we
get
to
the
Reid
previewed,
hopefully
in
1.9
version.
B
Please
do
give
us
feedback
using
the
feedback
channels
which
will
be
available
at
that
points.
So
we
can.
We
can
show
the
interest
of
the
community
towards
this
kind
of
functionalities
as
well,
but
pretty
cool
and
pretty
it's
an
eclipse
status
already,
it's
great
to
see.
Actually
the
interest,
also
in
the
IM
chat
window
around
this
one,
but
that's
all
on
my
side.
So
Patrick,
let's
jump
on
you,
oh.
A
Right
so
updates
on
the
PNP
GS
client-side
libraries,
let's
talk
v2,
so
we
are
pretty
well
focused
now
on
preparing
for
the
version
to
release
a
lot
of
work
has
been
done
behind
the
scenes
there,
but
now
we're
sort
of
rolling
that
out
publicly
so
to
speak.
There's
a
new
branch
you'll
see
dev
V.
That
branch
is
in
no
way
compatible
with
the
previous
dev
branch.
A
So
if
you're
gonna
submit
pull
requests
and
things
to
PNP
GS,
please
be
aware-
and
please
focus
on
submitting
to
the
correct
branch
if
you
are
still
developing
for
v1
or
want
to
submit
something
for
v1.
Please
absolutely
do
so
just
submit
that
as
normal
to
the
dev
branch,
just
de
vie,
dev
branch,
if
you'd
like
to
help
us
work
on
the
v2
work
we
have
just
created
or
we
Simon
and
David
have
just
created
a
whole
ton
of
issues.
If
you've
looked
at
the
issues
list
there
lately
you
will
see.
A
Oh
I,
don't
know
80
some
new
issue.
Well,
not
80
some
new
issues,
maybe
some
total
issues
and
many
of
those
are
related
to
2.0
and
we'll
be
talking
a
little
bit
more
about
that
in
the
future
on
how
to
help
out.
But
if
you
check
out
those
issues,
you'll
see
and
I'm
not
going
to
go
through
each
of
these
bullet
points,
but
you
will
see
sort
of
a
checklist
of
the
tasks
to
do
for
each
of
the
sub
modules,
so
we'll
be
providing
a
little
more
guidance.
A
A
There
is
a
ton
of
room
for
folks
to
help
out
here
and
have
a
real
impact
in
getting
v2
out
the
door,
as
I
said
before.
I
think
on
this
call,
or
maybe
not
v2
is
less
about
amazing,
new
technical
features
and
all
about
paying
off
a
lot
of
our
technical
debt
from
the
previous
years.
So
making
sure
we've
got
tests
making
sure
we've
got
documentation,
making
sure
we
do
some
code
cleanup
and
stuff
like
that.
There
will
be
some
very
cool
tech
stuff
which
we
will
talk
about
in
the
future.
A
But
that
is
what
skill
rolls
do
you
need
all
skill
rolls.
So
if
you
are
a
developer,
would
love
to
have
your
help
developing
if
you
are
just
a
documentation
document,
writer,
technical
writer,
sorry
brain,
not
brainy.
Currently,
if
you're
a
technical
writer-
and
you
still
want
to
help
out-
please
reach
out-
let
us
know
we
can
certainly
you
know,
make
use
of
your
skills
find
a
way
to
get
you
involved
so
I'd.
Rather,
if
you
want
to
help
and
aren't
sure
how
just
reach
out
we'll
find
a
way
to
get
you
involved.
A
So
don't
worry
too
much
about
that
and
we
are
here
all
of
us
to
help.
You
know
get
get
folks
lined
up
and
able
to
contribute
as
efficiently
as
possible,
and
we
will
have
a
beta
coming
soon.
A
little
winky
face
there,
because,
if
you're
paying
attention,
there
might
already
be
a
to
dotto
beta
out
there
in
the
world,
but
just
a
heads
up,
no
support
on
to
do
betas.
Yet
please,
at
this
point,
do
not
submit
issues
for
the
2.0
beta,
which
it's
not
released.
It's
a
true.
A
It's
really
an
alpha
version,
but
you
can't
pull
that
down
and
play
with
it.
We
don't
have
Docs
for
it,
yet
we're
working
on
that,
but
so
we're
really
starting
to
ramp
this
up
and
we'll
things
will
start
to
get
a
little
bit
more
solid
over
the
next
couple
weeks
and
we
are
looking
sometime
mid
summer
release
for
v2
no
hard
dates
yet
because
we
will
not
release,
and
so
we
have
all
the
tests
and
all
the
docs
written
for
v2.
A
So
that's
our
real
focus
is
making
sure
we
get
that
with
a
you
know,
real
solid
release.
Will
there
be
compatibility
with
older
versions?
They
will
not
work
side
to
side.
It
is
a
brand-new
version,
so
you'll
either
use
stuff
from
the
one
tree
or
the
diversion
to
tree,
but
your
existing
code
and
we'll
have
a
guide,
just
as
we
have
had
in
the
past
when
we
do
major
version
releases
on
how
to
migrate.
A
So
the
goal,
as
always,
is
your
existing
code
will
have
no
or
minimal
changes
to
move
to
2.0,
so
we're
gonna
do
our
best
there,
but
with
certain
considerations
in
place,
because
there
are
some
changes,
there
may
be
some
breaking
changes
and
that's
I
mean
is
why
it's
a
v2
and
not
a
one
dot,
something
else.
So
there
will
be
some
breaking
changes,
but
again,
as
always,
we
aim
to
minimize
those
completely
as
much
as
possible.
A
So
current
documentation
for
the
one-dollar
stuff
is
still
always
as
always
at
PMP,
github,
bio,
slash,
PJs.
You
can
follow
the
PM
pjs
hashtag
on
twitter.
You
can
always
follow
me
at
mediocre,
bowler
on
twitter
and
with
all
the
focus
on
tutored.
Oh
I
did
want
to
mention
that
again
for
the
month
of
April,
we
were
over
three
billion
requests
on
the
library
into
SPO.
A
For
the
library
moving
forward,
because
we've
seen
such
phenomenal
growth
over
the
last
excuse
me
I'm
really
over
the
last
eight
years
so
or
eight
years,
Wow,
eight
months,
so
it's
really
time
I
to
really
sit
down
and
solidify
the
library
and
really
make
it
a
lot
easier
to
get
in
use
and
understand
and
a
big
thank
you
as
always
to
everybody.
That's
helped
out
on
that
journey.
A
A
Support
for
upgrading
your
SP
FX
project
so
already
has
support
for
upgrading
to
the
new
18.2
of
SP
FX
and
then
enable
as
well
as
new
features
around
enabling
communication
sites
renewing
office.
365
group
expiration,
removing
users
from
groups
upgrading
your
share
from
projects
to
one
eight
one
and
then
well,
which
is
now
one
eight
two
as
well.
A
Sorry
I
should
have
taken
that
bullet
point
out
and
then
also
as
well
now
handling
throttling
and
gzip
compression
in
progress,
more
commands
for
teams
flow
power,
apps
and
SharePoint
simplifying
the
login
experience,
as
well
as
improving
the
command
name
consistency.
You
can
always
install
the
latest
beta
NPM
installed,
SG
/
@
PQ
/
office
uses
5
CLI
at
next
and
then
more
information
at
a
kms,
/,
OS,
365,
CLI
and
hashtag
office
uses
five
CLI
on
Twitter,
there's
a
gator
channel
and
as
well
again
the
docs
link
there
in
the
corner.
A
If
you
haven't
tried
out
the
CLI,
it's
a
really
fantastic
cross-platform
way
to
manage
your
SharePoint
assets.
It
really
is
super
helpful
with
your
SPF
X
projects,
especially
I
mean
I,
say
this.
The
capability
of
upgrading
your
projects
alone
makes
this
a
super
valuable
tool,
and
then
you
get
all
the
administrative
capabilities
as
well
so
yeah
I
haven't
checked
this
out.
Do
please
check
it
out
it's
another
great
tool
to
have
in
your
tool:
bag
for
SPF,
X
development
updates
on
the
reusable
controls,
new
release,
113
one
of
the
react
controls.
A
These
are
the
controls
designed
to
be
used
in
the
body
of
your
webparts,
so
just
really
kind
of
a
maintenance
release,
couple
of
fixes,
webpart
title
fixed
to
the
class
name
property
and
a
rich-text
fix
for
an
issue
with
the
control
turning
dropdowns
black
special
thanks
to
Hugo
for
contributing
on
this
release
and
as
well
there's
two
links
down
there
at
the
bottom.
The
first
is
to
the
property
controls
and
the
I
should
have
said
this
at
the
top,
but
the
there's
two
sets
of
reusable
react
controls
distributed
here.
A
The
first
is
a
set
of
property
controls
that
really
help
in
your
edit
pane.
Allow
you
to
create
rich
editing
experiences
with
little
effort,
so
drop
these
in
use
them
they're
already
styled
with
the
office.
You
have
fabric,
so
it's
gonna,
look
very
out
of
the
box
and
blend
in
to
your
sharepoint
designs
and
allow
you
to
provide
a
rich
editing
experience
for
your
webparts
and
then
as
well.
There's
a
second
set
of
controls,
more
designed
for
the
body
of
your
webparts.
A
So
these
display
data
and
graphs
allow
people
to
interactively
view,
information
and
things
like
that.
So
very
very
useful
and
really
again
a
great
way
to
jumpstart
your
SP
FX
development,
whether
it's
webparts
or
application
customizers.
You
can
get
a
lot
of
great
functionality
by
simply
importing
these
libraries
and
dropping
the
controls
into
your
react
projects
so
really
exciting
to
see
these
continued
to
grow.
A
Thanks
to
hugo
again,
and
thanks
to
everybody
else,
there's
been
a
whole
lot
of
other
folks
that
are
contributed
in
the
past
to
these
so
great,
to
see
and
again,
if
you're
looking
to
get
involved
and
you
like-
writing
controls.
This
is
a
great
project
within
the
PNP
sphere,
the
PNP
cinematic
universe
to
get
involved
in,
and
the
latest
addition
for
folks
that
might
not
have
heard
about
it
is
our
PNP
generator.
A
So
this
is
a
yeoman
generator
built
on
top
of
the
out-of-the-box
SharePoint
framework
generator,
so
you're
gonna
get
a
a
real
in
quotes
real
SharePoint
framework
project
with
all
the
same
backing
code,
dependencies
and
so
forth
that
you
would,
by
using
the
standard,
out-of-the-box
SharePoint
framework
generator.
But
this
one
builds
on
top
of
that
and
provides
you
the
ability
to
include
some
extra
stuff
and
use
different
frameworks
that
might
not
be
or
the
supported
by
the
out-of-the-box
one
things
such
as
view
and
handlebars
and
stuff
like
that.
A
So
again
would
ask
folks
please
stay
on
mute.
Let
me
find
that
person
oops
there
we
go.
So
if
you
get
a
chance
to
do
check
this
out
is
a
great
way
to
jumpstart
again
your
SharePoint
framework
development
and
we
have
a
new
version
out
172
that
has
an
update
to
the
latest.
Again
we're
just
cutting
edge,
updated
to
the
latest
out-of-the-box
generator
behind
the
scenes.
A
You
can
find
more
information
at
a
kms,
P,
&,
P
generator
and
then
hashtag
PNP,
SP
FX
generator
on
Twitter,
and
this
is
again,
if
you
like,
to
do
yeoman
development
if
you're
interested
in
scaffolding
things
and
improving
that
experience
another
another
way
for
you
to
get
involved
in
PNP
and
get
a
little
bit
deeper
involved
and
contribute
there.
If
that
happens,
to
strike
your
fancy
so
moving
forward,
we've
got
our
demos,
so
Kyle.
If
you
are
ready
to
go
and
want
to
take
over
the
presentation
excited
to
see
your
my
bookmarks
extension.
C
Right
well
so
I'm
planning
on
only
doing
a
demo,
because
there's
a
lot
of
a
lot
of
work
here
and
not
spend
very
much
time
at
all,
looking
at
code,
but
basically
we're
talking
about
in
the
SP
dev
Solutions
repo,
the
multilingual
pages
solution,
and
so
there's
a
big
long
ravine.
Here,
that's
going
to
go
through
a
lot
of
what
I'm
going
to
demo
today,
but
that's
what
we're
talking
about,
and
so
the
other
thing
I
want
to
just
point
out
before
I
lose
time
on
it
is
at
the
sharepoint
conference.
C
In
a
couple
of
weeks
I
will
be
demoing
this
again
and
vcpr
from
Microsoft
will
be
giving
some
roadmap
for
Microsoft's
plans
on
multilingual,
so
I
just
wanted
to
sort
of
give
a
shout
out
to
to
that
session,
because
I'm
sure
for
the
people
who
are
really
interested
in
multilingual.
That's
going
to
give
you
a
lot
of
insight
to
what's
what's
happening.
Okay,
so
this
is
a
SharePoint
framework.
Solution
builds
on
the
1.7
version
of
the
framework
or
we
have
not
updated
it.
Yet.
This
was
originally
built
for
the
shire,
slash
Takeda,
Pharmaceuticals
merger.
C
That
happened.
This
last
fall
where
they
had
a
a
need
for
multilingual
and
so
between
David
Feldman
who's,
another
MVP
and
myself.
We
designed
this
solution
and
then
I
built
the
extension
and
another
guy
named
Scott
Hillier,
who
many
of
you
probably
heard
of
built
the
redirector
web
part
that
goes
with
this
solution.
So
basically,
once
you
add
in
the
application
to
your
site
collection,
it
builds
itself
out
by
adding
some
site
columns
and
to
the
site
information
panels.
C
Let
me
go
show
this
whew
all
site
settings
and
if
we
go
into
site
columns,
we
can
see
that
it
adds
some
site
columns
that
support
this
multilingual
solution.
So
you
have
a
language
folder
so
which
folder
is
the
page
in
which
variants
of
the
languages
does
this
page
support?
When
was
it
last
synced
from
the
page
that
is
defined
as
faster?
What
is
the
master
translation
pages
ID
and
if
there's
a
redirector
page,
what
is
that
URL?
C
And
then
we
added
all
those
site
columns
to
the
site,
page
content
type
in
here,
so
that
every
page
in
your
site,
pages
library
gets
those
properties,
and
so
this
is
done
on
a
site
collection
by
site
collection
basis,
and
so,
if
I
come
back
to
my
home
here
and
then
go
into
pages
library,
the
other
thing
it
does
is
then
provision
these
folders.
Now
these
folders
come
from
a
tenant,
app
property
that
has
a
JSON
blob
that
defines
the
languages
and
I'm
hoping
I
can
quickly
come
up
with
this
whoops.
C
Storage
entity
and
so
we're
getting
the
storage
entity,
which
is
the
language
configuration
and
you
can
see
the
value
in
here,
has
a
JSON
blob
that
defines
all
the
languages
we're
going
to
support
in
this
tenant.
Okay,
so
shutting
that
down,
we've
got
a
folder
for
every
language
and
right
now
this
is
a
pretty
empty
site.
C
Cos
library
I
only
have
the
home
page
in
here,
but
I
also
did
go
ahead
and
I
have
the
all
pages
library,
where
I
added
my
property,
so
I
could
see
it
and
then
I
also
created
a
flat
view,
so
that
I
could
see
it
flattened
by
library
and
that
sometimes
helps
so
that
you
can
see
what
pages
you
have
going
on.
So
now,
if
we
go
ahead
and
create
a
new
site
page.
C
So
by
default,
every
page
gets
tagged
with
all
the
languages
you
support
and
if
we
come
back
over
here,
we
can
now
see
that
we
have
this
multilingual,
not
configured
indicator
down
here
and
if
I
go
into
edit
mode.
I
get
a
language
details
button
when
I
get
the
language
details.
I
can
then
see.
Okay,
we
haven't
started
a
translation
of
this.
We
are
identifying
this
page,
the
master
translation
as
English,
and
we
can
get
more
information
about
this
page
like
that.
C
It
knows
based
on
the
settings
either
the
regional
settings
or
the
tenant
settings
or
the
user's
personal
language
settings
and/or.
It
falls
back
all
the
way
to
the
browser
settings
of
which
language
the
user
wants
to
see,
and
if
there
is
a
translation
that
matches
their
language,
it
will
redirect
them
to
that
translation.
Otherwise
it
will
stick
to
the
master
translation,
so
we're
gonna
go
ahead
and
hit
apply
language
changes,
and
this
can
take
a
few
minutes
fast
today,
and
so
now
we
have
some
translations
out
there.
C
C
We've
want
to
that's
not
really
important
right
now,
but
they,
the
user
experience
for
users
that
come
to
this
page,
would
be
that
they
get
this
selector
that
allows
them
to
switch
languages
if
they
want.
So
it
shows
them
what
language
they're
in,
but
if,
for
whatever
reason,
maybe
their
language
settings
are
set
to
English
but
their
native
Japanese
speakers,
they
want
to
see
the
Japanese
translation,
they
can
come
down
here
and
say:
okay,
well,
I
want
to
go
to
the
Japanese
translation.
C
Okay,
so
you
can
tell
now
that
I'm
in
the
Japanese
folder
here
and
because
I'm
an
editor
I'm
going
to
edit
this
page
and
I
can
now
say
this
is
the
Japanese
page
and
I
could
do
something
else
too,
to
sort
of
make
it
stand
out
so
that
we
can
really
see
that
this
is
a
different
page
and
so
I
can
make
that
change.
And
let's
save
that
as
a
draft
and
just
let's
even
publish
that,
and
so
now
we
can
see
we're
on
the
Japanese
page.
C
But
if
I
come
back
over
to
the
English
page,
excuse
me
and
we
edit
this
page,
we
can
see
on
the
language
details
under
the
Japanese
version
that
this
version
has
been
modified
since
the
last
time
it
was
synced.
It
is
published
and
we're
seeing
this
new
translator
comments
section
here.
So
what
the
functionality
is
here
is
that
if
we
want
to
change
the
English
version
and
say
and
change
this
and
save
it,
and
then
we
decide
that
we
want
to
open.
C
C
That's
because,
okay,
so
we
can
do
that
and
what
will
happen
then
is
for
the
German
page,
because
we
haven't
changed
it.
It
actually
will
replace
the
German
page
and
for
the
Japanese
page,
it's
going
to
send
an
email
to
this
person
here
with
the
translator
comments
in
it,
letting
them
know
that
the
the
the
trans,
the
page,
the
master
page,
has
been
changed
and
that
we
need
some
read
translation.
There
is
also
the
ability
to
replace
all
existing
pages.
C
So
if
you
have
a
massive
redo
of
a
page,
you
could
just
override
all
of
the
changes
and
apply
it
to
every
single
translation.
So
if
I
apply
this
change
and
it
doesn't
take
too
long
and
we
publish
yeah
I,
know
and
then
I
come
back
over
to
the
Japanese
version,
we're
gonna
see
we're
still
in
the
way
the
Japanese
version
was.
But
if
we
go
to
the
German
version,
we
can
see
that
it's
still
unchanged
and
that
we
haven't
really
done
anything
with
that.
C
C
This
actually
takes
a
little
bit
of
time
because
it's
actually
using
the
awesome
code
that
Patrick
reverse-engineer
to
do
the
client
pages
library
and
the
PM
pjs,
so
that
was
super
helpful
I
was
ecstatic
to
see
that
he
had
done
all
that
work
for
me
and
I
didn't
have
to
do
it.
So
now,
if
I
put
this
page
in
we're,
gonna
see
a
quick
blink,
but
then
it's
taken
me
to
the
English
version
of
this
page.
C
If
I
put
this
back
in
here
and
put
stay
equals
true
in
here,
then
the
web
part
knows
to
stay
on
the
page
and
I
can
donations
yes,
I
know,
I
should
absolutely
donate
to
you,
because
that'd
save
me
a
ton
of
time.
So
now
I
can
see
that
this
webpart
started
telling
us
what
we
what
it
was
trying
to
do,
what
it
was
trying
to
take
us
to
him.
We
can
edit
it
and
look
at
what
the
redirects
are
and
can
see
that
for
Japanese.
C
It's
gonna
try
to
take
you
to
the
Japanese
page
for
German.
It's
going
to
take
me
the
German
page
and
for
everything
else.
It's
gonna
to
stay
it's
going
to
redirect
back
to
the
English
page,
so
this
is
a
way
that
you
can
have
a
link
to
one
page
that
will
take
you
to
whatever
language
for
whatever
users.
So
if
you
need
to
have
a
link
in
like
a
navigational
menu
or
something
like
that,
this
is
a
handy
way
to
make
that
work
so
that
you
can
get
the
redirects
to
the
right
pages.
C
You
can
also
add
this
webpart
manually
to
any
page
and
and
and
configure
it
but
the
web,
but
the
extension
will
configure
it
for
you,
so
you
don't
really
have
to
know
how
to
do
this.
I
just
wanted
to
show
what
it
was
doing
under
the
covers
that
this
was
getting
created,
but
the
users
don't
have
to
know
about
this.
They
don't
have
to
configure
it.
It's
all
done
by
clicking
that
little
slider
in
the
extension
to
send
them
to
the
redirector.
So
where
was
I
so
over
here
back
over
here?
C
It's
all
managed
through
this
redirector
page.
So
as
I
add
new
translations
and
apply
those
changes,
because
this
redirector
page
is
here,
the
redirector
page
will
get
updated
with
the
new
translations
and,
as
you
take
things
off
and
add
things
on
that,
all
will
just
happen.
So
yeah
there
was
I've
got
two
minutes
and
there
was
one
other
thing
I
wanted
to
show.
There
is
it's
from
a
code
perspective.
Let
me
see
if
I
can
get
up
here.
So
this
is
the
the
code
base.
We
have
the
multilingual
extension.
We
have
the
redirector.
C
The
one
thing
I
wanted
to
point
out
on
this
extension
is
that
there
is
on
the
init.
There
is
some
code
in
here
to
handle
some
issues
that
are
in
in
SharePoint
framework
about
page
loads
across
site
collections,
now
I
sort
of
understand
this
was
supposed
to
be
fixed,
but
I
am
currently
not
seeing
it
be
fixed.
C
A
Really
great
stuff,
thank
you
very
much
for
that.
Let
me
try
and
get
back
to
the
slide,
so
we
can
close
out
really
impressive
demos
today,
a
great
sample
there
from
Kyle
from
what's
possible
and
then
I
think
from
Julie
a
really
outstanding
solution
that,
while
complicated,
is
a
great
way
to
handle
what
is
a
complicated
problem
in
topic,
so
sometimes
that
goes
hand
in
hand,
but
really
fantastic
stuff
for
both
of
you.
Thank
you
very
much
for
those
demos.
A
As
always,
if
you'd
like
to
demo
on
a
future
call,
please
just
reach
out,
and
let
us
know
our
next
SharePoint
framework,
JavaScript
sig
will
be
May
23rd
and
that
will
be
a
great
call
then
expect
some
p.m.
PJs
to
dotto
updates
general
SharePoint,
dev
sig
will
be
next
Thursday
May
16th,
look
forward
to
seeing
everybody
there
as
well
and
as
always,
learn,
reuse
and
share.
Thank
you
all
for
joining
the
call
very
much
appreciate
it.
Everybody
have
a
great
rest
of
your
week,
no
time
for
Q&A
today
and
we'll
talk
to
you
soon
thanks.