►
Description
SharePoint Developer (SP PnP) Community call recording from 11th of September 2018. Summary of the activities happened in the past month around SharePoint development guidance, roadmap updates, future plans for the SharePoint development.
Demo - Centrally deployed configurable footer with SPFx for your whole tenant
Demo - Using Angular Elements with SharePoint Framework
Demo - Introducing new PnP Yeoman Template project
Detailed agenda an links to specific sections available from https://developer.microsoft.com/en-us/sharepoint/blogs/
You can download recurrent invite for the monthly SharePoint community calls from http://aka.ms/spdev-call.
A
So
welcome
Emily.
This
is
Shep
on
patterns
and
practices,
Sochi
upon
deaf
ecosystem
ash
upon
deaf
community
September,
2018
monthly
community
call-
and
this
is
the
subtitle
exit
September
11th-
is
today-
and
this
is
the
monthly
community
call
where
we
kind
of
go
through
what
has
well
in
high-level
happened
within
past
month.
So
technically
today
we
have
three
different
demos
who
are
gonna,
concentrate
absolutely
on
the
demo
sign
and
we're
slightly
adjusting
the
messaging
around
this
monthly
summaries
and
monthly
call
as
well,
because
I
think
it's
it's
technically.
A
People
are
more
interested
on
seeing
live
demos
and
having
a
discussion
on
what's
actually
happening
and
what's
the
new
stuff,
rather
than
looking
back
on
what
has
happened
because
looking
back,
you
can
always
go
to
our
blog
posts
and
you
always
see
what's
available
from
there.
So
what
kind
of
a
slightly
adjusting
did
this
be
slightly
more
forward-thinking
and
concentrate
on
the
demos?
More
and
more
now.
A
A
I
think
I
might
have
a
slide
on
the
user
voice
update,
but
we
don't
actually
have
that
much
progress
on
the
user
voice
or
any,
let's
say
massive
new
things-
announcements
in
here,
because
the
ignite
is
within
the
two
weeks
and
obviously
we'll
keep
our
some
of
our
announcements
waiting
so
that
there
will
be
announcement
in
the
ignite
timeframe.
Let's
talk
about
that
one
in
a
second,
so
we'll
also
have
three
different
demos,
so
I
will
start
by
having
a
a
pre.
Well,
it
helps
if
I
would
update
the
slide.
A
So
I'm
not
gonna
have
a
preview
on
SharePoint
framework
1.6
it
this
actually
out
so
I'm
gonna
actually
demonstrate
you
and
really
cool,
enter
and
a
centralized
deployment
of
a
footer
which
is
reusable
and
configurable,
which
is
available
for
you
today
already
as
part
of
the
September
release
of
stuff.
Now
and
I'm
gonna
explain
how
it
actually
works
and
and
how
you
can
actually
control
a
configure,
a
centralized
from
a
centralized
location,
a
standardized
footer
for
your
tenants.
A
That's
super
interesting
topic
as
well,
and
then
the
Stefan
Power
on
the
end,
it's
going
to
do
a
live
demo
on
our
new
open
source,
yeoman
template
project
which
is
going
to
be
announced
today.
So
basically
well
I.
Don't
have
a
slide
for
that,
but
announcing
it
today
and
Stefan's
going
to
show
that
one
in
practice.
The
whole
point
of
that
one
is
that
we
can
actually
now
start
building
together.
A
Two
custom
templates
on
a
SharePoint,
sorry
JavaScript
frameworks
which
are
not
natively
support
it
in
the
out-of-the-box
yeoman
and
it
sounds
slightly
tricky.
But
this
difference
gonna
walk
through
the
process
and
then
I'm
gonna
actually
talk
about
what
does
it
mean
in
practice
and
why
well
potentially
might
open
source
starters
the
Box
run
at
some
point,
but
for
now,
for
time
being
we
don't
actually
do
that
so
we're
introducing
a
new
site
by
side,
out-of-the-box
open
source
project
to
support
this.
A
So
let's
see
how
that
goes,
but
so,
if
I
was
going
to
show
that
one
in
practice
now,
let's
go
to
some
of
the
slides
so
I'm,
connecting
intentionally
quite
fast
on
some
of
the
slides
and,
like
I,
said
I'm
chopped
some
of
the
contents,
which
were
typically
go
through
onto
monthly
communication
call
to
avoid
that
we're
taking
too
much
time.
First
of
all,
just
quickly
explaining
what
this
is
all
about.
So
we
have
quite
a
lot
of
call.
We
have
quite
a
lot
of
community
things
and
def
on
the
SharePoint
dev
side.
A
So
the
whole
point
of
that
one
is
that
you
can
decide
which
of
these
you
actually
furniture
which
just
needs
which
of
how
do
you
want
to
actually
engage
together
with
community.
So
we
have
the
SharePoint
developer
group
in
the
Microsoft
tech
community.
We
have
bi-weekly
SharePoint
framework
community
cause
where
they
actually
concentrate
on
what
is
the
SharePoint
framework
and
SharePoint
framework
and
demos,
and
only
SharePoint
framework
and
JavaScript
Avilan
and
treatment
development.
A
Then
we
have
a
general
chip
on
def
call,
which
is
by
a
meeting
by
weekly
as
well,
which
is
then
concentrating
more
on,
let's
say,
site
designs
and
provisioning
and
column
formatting
and
all
of
those
things,
so
everything
which
is
not
related
on
SharePoint
framework
because
well,
let's
face
it.
Sharepoint
a
platform
is
quite
big
and
there's
quite
a
lot
of
topics
and
what
a
lot
of
ways
of
customizing
Chevron.
So
we
want
to
make
sure
that
that's
too
different
so
to
say,
focus
groups
on
these
topics
and
then
we
have
this
monthly
community.
A
Corbett's
carnauba
once
a
month
walking
through
what
has
happened.
This
typically
is
right
after
we
released
our
monthly
summary
where
we
actually
acknowledge
the
people
who've
been
working
with
us
within
the
past
month.
Now
few
numbers
and
few,
let's
say,
numbers
on
this.
What
has
happened?
Let's
see
if
I
can
actually
slightly
adjust
certain
things
on
my
slides
there
we
go
now.
I
can
actually
see
the
site's
much
better,
and
so
in
here
this
is
just
a
show.
A
You
some
level
of
a
numbers
if
you're
wondering
if
there
are,
is
there
any
other
people
out
there
so
sure?
Within
this
call,
we
are
already
hitting
139
140
141,
but
participants
I,
think
our
record
was
230
or
something
like
that
on
spring
and
then
the
whole
sky
went
down
so
that
wasn't
super
successful.
Now
150
we
can
probably
do
properly
now
in
that
there's
always
a
lot
of
activities
what's
happening
in
the
SharePoint
deaf
community.
So
in
our
YouTube
channel
we
had
a
187
thousand
minutes
watch
time
within
the
last
month.
A
So
clearly
people
are
appreciating
recording
of
this
course
and
then
looking
into
what's
happening
in
a
key
tough.
We
had
close
to
50,000
unique
visitors
in
the
past
two
weeks,
which
is
pretty
cool
as
well,
which
was
250
forty-five
thousand
views.
So
there's
a
lot
of
other
people
looking
into
using
this
stuff
as
well.
In
the
docs
we
went
slightly,
it's
a
bit
sit
down
from
July,
which
is
actually
as
expected
because
there's
a
summer
vacation
time
in
Europe
during
August
as
well.
We
were
in
8880
thousand
views,
the
PMPA
reusable
component.
A
So
this
is
the
open
first
part
of
things
which
we've
been
using
for
years
already.
The
users
of
this
one
is
crowing,
so
the
BMP
power
shall
be
NBC's,
encore
and
BMP
jeaious
with
just
a
JavaScript
layer
of
things.
So
there
were
17,000
unique
tenants,
actually
using
BMP,
reusable
components
which
generated
altogether
twelve
point
six
billion
requests,
and
you
don't
actually
it's
really
hard
to
figure
out
what
is
a
twelve
point:
six
billion
requests,
but
it
actually.
A
It
means
that
true,
these
components,
the
billion
PMPC,
ISM
and
BMP,
PowerShell
and
bnbg-
is
a
chase
and
being
a
JavaScript
component.
We
are
kidding
four
thousand
more
than
four
thousand
seven
hundred
requests
per
minute
per
sorry
per.
Second,
all
around
the
world,
and
that
will
give
you
a
scale
of
the
open
source
inside
of
the
sharepoint
online
as
well,
and
that's
pretty
mind-blowing
and
obviously,
on
top
of
this
there's
the
on-premises
side
of
the
story
as
well.
A
So
sharepoint
is
huge
and
shape
and
user
to
scrolling
quite
significantly
now
good
example
of
the
growth
again,
we
can't
actually
show
you
the
numbers
in
here,
but
I
can
give
you.
The
scale
is
the
adoption
of
sharepoint
framework,
and
this
is
really
mind-blowing.
We
crew,
two
hundred
and
forty
percent
on
the
usage
of
sharepoint
framework
from
January
2018
and
already
at
the
January
2018
SharePoint
framework,
was
the
widest
and
most
widely
used
share
extensibility
model
in
the
whole
office
365.
So
the
uses
is
to
crowing
insane.
A
Few
slides
has
to
reminder
and
different
akms
SPD
Docs
is
the
location
or
just
of
myself
become
7/8
point.
The
official
documentation
is
here
the
lot
of
new
articles
lot
of
new
updates,
which
we
did
last
week.
Sorry
actually
last
week's,
and
actually
that
is
pretty
precise
as
part
of
the
1.6
release
and
also
there
was
a
new
articles
related
on
the
the
SharePoint
framework
usage.
We
also
refreshed
all
of
our
tutorials,
which
is
a
big
thing.
A
So
if
you're
not
super
familiar
with
you
upon
framework
development,
the
tutorials
are
updated,
videos
are
updated
and
everything
should
be
up
to
date,
already
matching
the
versions
which
are
available
for
you
to
take
advantage.
The
second
thing:
if
we're
running
into
dev
issues
or
potential
Bach
in
the
service
or
whatever,
please
let
us
know-
and
we
are
significantly
falling
behind
of
this
issue
list-
we
are
now
making
clear
actions
to
how
to
catch
up.
A
This
is
your
list,
but
the
whole
point
of
this
one
is
that
you
will
have
a
channel
to
report
issues
on
the
underlying
api's
or
customizations
or,
if
you
think,
there's
a
problem
or
if
you
want
to
have
a
discussion
with
somebody
else
on
the
community.
You
have
a
clear
one
location
where
you
can
actually
do
that
and
that's
the
SB
dev
dogs
issue
list.
You
can
get
their
AKMs
SP
depth
issues
or
SP
dev
dogs
repository
in
the
github.
Now,
unlike
that,
we
are
now
catching
up
on
on
this
one.
A
Quite
heavily,
we've
been
falling
behind
to
numerous
reasons
and
ignite
this,
to
be
honest,
messing
up
our
schedules
pretty
significantly,
and
that
always
happens
every
single
year,
but
it's
just
there's
no
way
for
getting
prepared
for
that.
Now
on
the
ignite,
so
contesta
a
quick
reminder
on
that
one.
We
actually
have
a
lot
of
sharepoint
developer
platform
content
in
ignite
at
some
point.
This
was
slightly
awkward
whenever
the
ignite
catalog
went
live
and
there
was
none
and
actually
some
people
were
like
super
worried
on
what
does
it
actually
mean?
A
Why
isn't
there
any
ship
on
developer
platform
content?
And
that
was
because
we
had
a
small
delay
on
getting
all
of
the
the
content
and
topics
are
finalized.
But
now
there's
like
four
three
at
least
three
to
four
actual
big
breakout
sessions.
There's
like
four
different
terror
sessions.
We
have
a
PNP
and
SharePoint
frame
reports.
We
have
a
SharePoint
crafts,
poof
and
everything
is
available
in
ignite.
A
So
there
is
a
blog
post
in
the
desktop
calm,
I'm,
sorry
and
developer
my
stuff
that
comes
last
ship,
one
where
you
can
actually
find
all
of
the
breakout
sessions
and
all
of
the
details
what's
happening
within
the
ignite
side.
Ignite
is
within
one
and
a
half
weeks,
horrifying
we're
running
out
of
time
quickly.
Now
what
else?
One
thing
what
I
wanted
to
remind
if
you're
interested
on
following
up
on
on
things-
and
this
is
something
what
we
also
want
to
have
feedback.
A
Also,
you
can
provide
us
feedback
on
social
media
or
during
this
course
or
or
any
way
you
prefer.
So
we
started
this
new
series
called
ship
on
dev
weekly,
and
this
is
really
meant
to
be
a
discussion
between
me,
waldek
and
then
a
visitor
on
the
last
one.
We
had
a
see
and
sure
kono
open
chopping.
Bian
we've
had
a
basically
discussion
on
different
topics.
A
What's
actually
what's
the
latest
articles
and
samples
and
tooling,
what's
of
what
has
been
released
within
the
past
week,
so
we
typically
do
recount
this
on
Thursdays
and
the
the
video
goes
live
on
Friday.
So
it's
relatively
fresh
content.
We
aren't
debating
actually
slightly
adjusting
the
schedule
but
more
details
on
that
one,
so
it
might
be
that
in
future
will
actually
record
on
Monday
and
push
this
one
out
on
Tuesday.
Now,
if
you
look
if
you're
interested
on
following
up
what?
A
So
if
you
missed
this
one
last
week,
just
making
sure
that
everybody
is
aware
of
this,
this
was
a
big
release.
For
so
now
we
have
an
ADA
types
of
craft
support
in
SharePoint
framework,
so
you
can
actually
centrally
control.
What
are
the
scopes
and
ap
is
which
the
SharePoint
framework
components
can
actually
call
from
lights
of
graph,
there's
a
secure
way
of
calling
third-party
abis.
A
My
deployment
of
extensions
and
I'll
show
you
that
one
in
practice,
but
from
a
centralized
location,
you
can
enable
the
SharePoint
framework
extensions
on
the
existing
sites,
and
what
it
means
is
that
you
can,
as
an
example,
push
footers
or
headers
and
navigation
items
or
whatever
elements
to
all
of
the
sites,
form
a
single
location.
So
don't
actually
have
to
explicitly
install
the
extensions
in
every
single
site.
You
can
easily
do
this
from
a
one,
centralized
location
and
that's
huge.
A
That's
gonna
help
enormous
Lea
for
people
to
take
advantage
of
SharePoint
framework
and
I'll
show
you
that
one
in
a
practice
after
few
slides,
quick
reminders
on
the
on
the
roadmap
and
the
dev
roadmap.
So
obviously
one
point
six
was
life
is
from
last
week
we're
not
going
to
release
a
new
version
in
two
weeks
so
and
that's
kind
of
understandable.
Hopefully
we're
not
that
fast,
but
the
ETA
for
one
point:
seven
is
now
October
2018.
A
Well,
we
were
really
targeting
that
to
happen
on
October
end
of
October
2018
and
then
we're
releasing
a
few,
a
few
capabilities
with
which
community
and
customers
are
asking
quite
a
lot
and
also
two
new
capabilities
to
preview.
So,
for
example,
the
preview
SharePoint
framework
built
a
Microsoft
team
snap
is
coming
with
1.7
and
also
preview
of
myself
teams,
applications
and
SharePoint
Online,
so
we're
kind
of
aligning
the
development
experience
within
the
Microsoft
themes.
The
SharePoint
do
also
obvious
reasons,
so
she
open
framework
is
adapt.
A
All
of
the
ignite
sessions
are
also
recorded,
so
you
can
easily
follow
up
on
the
recordings
I
think
day
after
the
session
has
happened
or
well,
they
might
have
been
actually
message
that
their
live
streamed,
which
is
pretty
cool
as
well
now,
moving
on
on
things
and
I
do
apologize
them
I'm
slightly.
Rushing
because
I
want
to
make
sure
that
we
have
plenty
of
time
for
the
demos
as
well.
So,
first
of
all
thank
everybody
for
your
assistance
within
the
last
month.
A
I'm
do
apologize,
the
the
size
of
the
name
is
getting
smaller
and
smaller
on
their
slides,
and
that's
because
we
are
getting
more
and
more
people
actively
participating
on
the
SharePoint
deaf
community,
so
contributing
by
having
a
demo
in
the
community
course
or
contributing
by
editing
or
contributing
a
sample
or
contributing
by
having
a
submission
towards
the
SharePoint
developer.
Documentation.
There's
some
really
simple
thing
to
do
if
you
as
an
example,
find
a
typo
in
the
existing
documentation.
A
There's
is
an
edit
button
on
the
page
in
the
dorset
life
stuff
come
and
you're
able
to
actually
contribute
back.
But
thank
you.
Thank
you.
Everybody
for
your
help
on
making
this
the
best
and
the
most
active
community
out
there,
at
least
from
our
perspective
and
I,
don't
think
we
really
want
to
compare
the
stats
between
others,
but
I
know
that
we
are
actually
one
of
definitely,
if
we're
not
the
most
active,
definitely
one
of
the
most
active
ones
in
the
in
the
Microsoft
cloud.
A
So
thank
you,
everybody
for
your
assistance
on
this
now
so
SBHC.
The
debate
client
that
should
be
in
release
mode
but
I
need
to
confirm
that
on
the
question
now,
they're
also
the
companies
who
interpret
contributed-
or
these
are
the
companies
which
we
have
a
name
which
we
have
a
permission
to
show
in
the
slides.
A
So
these
are
companies
which
allow
their
employees
to
work
on
the
open
source
community,
so
contributing
back
for
those
people
which
they
learn
from
or
contributing
back
to
those
Procrit
projects
and
programs
which
they
actually
use
on
the
day-to-day
basis,
and
thank
you
also
from
what
behalf
of
Microsoft
for
these
companies
to
let
their
employees
to
actually
openly
contribute
back
in
Akita
and
in
our
open
source
channels.
Thank
you.
Thank
you.
Thank
you
for
that
Oh
on
a
Microsoft
site.
The
list
is
crowing.
Well,
it's
it's!
It's
a
live
list.
A
It
would
help
if
I've
adopted
slides.
Actually,
it's
not
a
preview
of
SharePoint
framework
1.6,
it
is
1.6,
is
out
so
I'm
going
to
show
you
the
global
footer,
which
you
can
take
advantage
today
in
the
SharePoint
in
your
tenants
and
the
code
is
available
and
it's
open
sourced
and
and
you
can
use
it
any
way
you
want.
So
let
me
show
this
one
in
practice
and
then
we'll
get
the
the
country
and
Stefan
after
that.
A
So
let
me
actually
share
my
screen
and
one
of
these
four
screens
is
the
one
which
I
should
be
screen
sharing.
It's
that
one
there's
a
question
from
Daniel.
Is
this
a
non
flow?
The
footer
answer
is
no
right.
Now
all
of
the
footers
are
floating
footers
and
let
me
actually
open
one
as
well,
and
what
we
want
to
do
screen
sharing
is
probably
now
working
right.
A
Somebody
has
to
confirm
that
it's
fine,
yes,
cool
on
Daniels
question
around
the
non
floating
footers
we
are
looking
into
having
additional
placeholders,
including
the
non
floating
footer,
but
I
can't
give
you
a
timeline
right
now
for
that
cool.
So
one
point:
six
SharePoint
framework
didn't
only
provide
new
packages
in
NPM.
It
actually
also
had
an
underlying
server-side
updates,
and
one
of
those
things
is
the
tenant
wide
deployment.
So
if
we
extend
she
upon
framework
in
the
dev
ducks
and
extensions,
we
can
actually
find
details
around
the
didn't
wide
deployment.
A
So
this
contains
all
of
the
details
around.
How
do
we
actually
take
it?
Then
that's
of
it.
What
does
it
actually
mean?
How
you
feel
there
the
extensions
to
a
specific
site,
and
all
of
that
and
this
we
could
actually
modify
slightly
the
formatting
of
this
one,
but
that's
a
separate
discussion
and
it
goes
to
the
details
on
the
solution
structure
as
well.
Now,
let
me
actually
explain
and
show
this
one
in
practice.
A
So
what
I've
done
here
is
that
I'm,
taking
advantage
of
this
global
food
or
solution
which
is
available
in
the
github
as
an
open
source
solution,
this
is
actually
implemented
by
Waldeck,
even
though
they
chose
to
last
edit
by
me.
That's
because
I
did
a
small
edit
here,
but
while
they
can
muster,
courage
implemented
this
one
for
you
to
take
advantage
and
the
cool
thing
about
this
one
is
that
we
we
intentionally
actually
included.
Also
the
SPP
cage
you
file
here,
so
you
don't
have
to
even
have
source
code.
You
don't
have
to
compile.
A
You
don't
have
to
install
anything.
You
can
just
take
this
bpk
to
file
and
take
that
into
you.
So
if
you
want
to
do
that,
if
you
want
to
test
it
in
your
test
anon,
you
can
just
go
to
the
SharePoint
folder
solution.
Folder
and
you
can
download
this
baby
aka
far
from
here
now
in
my
case-
I've-
actually
done
that
already
so
here's
my
SP
bak
to
file,
which
is
precisely
that
file
from
internet
and
now
what
I'm
gonna
do.
A
Is
that
I'm
going
to
actually
install
that
to
my
tenancy,
but
let's
actually
have
a
look
on
quickly
under
tenants
before
I.
Do
that?
So
let's
go
to
a
random
group
site,
and
you
can
say
that
this
is
a
random
group
associated
team
site.
So
it's
a
modern
team
site,
then
there's
no
special
functionalities
available
here.
A
Let
me
actually
add
another
one
here,
so
let
me
go
to
a
communication
site
and
I
just
that
one
there,
and
we
can
actually
say
that
there's
no
special
functionality
is
available,
except
there's
a
funny
apparently
funny
logo
on
the
on
the
side,
but
that's
not
a
thing
whatever
what
we
have
done
here
now
in
this
case,
what
I
want
to
do?
Instead,
I
want
to
install
the
solution
to
our
application
catalog,
and
this
is
really
the
key
related
on
SharePoint
framework.
So
we
have
a
centralized
control.
A
A
We
then,
when
we
install
the
solution,
we're
showing
something
slightly
new.
This
is
part
of
now
the
1.6
relate
so
I'm
going
to
zoom
in
first
of
all,
we
are
sharing
and
that
we
can
actually
host
these
assets
from
SharePoint
Online.
This
means
that
we're
taking
advantage
of
office
traces
to
five
CDN
and
I
said
packaging.
That's
in
one
point
four
point:
one
release
one
point:
four
release
of
SharePoint
framework,
so
nothing
in
it.
That's
a
tenant
scope
deployment
which
basically
means
that
I'm
enabling
enabling
the
tenant
as
a
solution
in
a
tenant
level.
A
Now,
with
extension,
with
webparts.
This
is
actually
the
only
thing
what
you
need
to
do,
that
click
that
check
box
and
the
web
part
is
available
in
a
web
part
picker.
Now,
in
the
extension
case,
there
is
no
such
thing
as
extension
picker,
so
we
need
to
still
explicitly
install
the
extension
to
a
site
to
actually
make
that
work
or
enable
that,
in
the
site
level,
even
though
you
deploy
that
in
a
8:10
our
scope
levels
and
which
is
slightly
confusing,
but
that's
where
we
actually
now
entered
the
tenant
wide
deployment
and
support.
A
So
in
this
case,
this
solution
contains
an
extension
which
will
be
automatically
enabled
cross
the
sides-
and
this
is
good
reminder
that
in
this
case,
especially
as
an
example,
this
JavaScript
will
be
automatically
then
activated
in
the
whole
tenant
when
it's
actually
activated
on
the
underside.
So
a
catalog
means
that
you
aren't
deploying
a
solution
to
your
tenants
over.
So
it's
a
good
practice,
the
first
and
this
the
random
solution
file
in
some
other
tenants,
rather
than
in
your
production,
just
a
bit
of
a
warning.
A
But
basically
what
we
are
doing
is
that
we're
adding
an
entry
on
this
tenant
wide
extension
list,
which
is
an
app
catalog
site
collection
and,
let's
see
what
that
means.
In
practice.
I'm
gonna
enable
this
internal
scope
and
that's
now
available.
So
that's
now
deployed
its
tenant
deployed
and
everything
is
happening
by
default.
Now,
right
now,
the
tenant
by
deployment-
let's
say
the
the
admin
experience
isn't
quite
optimal,
but
we're
potentially
looking
into
providing
a
nice
UI
is
in
the
central
admin
at
some
point
for
this
one
or
the
tenant
admin.
A
It
doesn't
have
any
any
other
things
that
it
actually
is
saying
that
hey
component
ID
is
following
and
then
if
the
component
has
properties,
so
no
what
it
means
is
that
if
I
could
any
site
within
my
tenant,
we
actually
light
up
that
component,
because
then
what
the
solution
actually
contained-
and
we
have
a
standardized
header,
footer
available
for
all
of
the
sites,
new
sites
existing
sites.
It
doesn't
really
matter.
The
extension
is
automatically
available
within
the
sides.
In
this
case,
this
is
a
relatively
small
footer.
It
has
three
buttons
in
which
you
can
click.
A
You
can
hopefully
say
that
small
reaction
there,
and
then
it
has
a
standard
text
which
is
sharing,
is
caring
and
control.
So
sharing
is
caring,
now
relatively
simple
scenario,
but
this
is
quite
often
actually
what
customers
want,
and
in
this
case,
obviously,
because
we
didn't
have
any
filtering.
If
I
refresh
a
communication
site
or
if
I
create
a
new
communications,
it
actually
has
the
same
setting
and
same
configuration
inside
in
here
now
we
can
actually
do
something
else
as
well,
so
we
can
actually
filter
this.
A
So
let
me
actually
first
of
all
take
a
small
modification
in
here.
Some
can
actually
modify
the
entry
slightly.
So
let
me
actually
modify
that
there's
a
small,
it's
a
bit
say
encoding,
interesting
encoding
in
here,
but
I'm
gonna
actually
paste
in
the
updated
value
which
I
had
from
a
visual
studio
code.
So
just
explaining
I'm,
taking
a
entry
from
a
visual
studio
code
from
another
screen
and
in
here
I'm,
actually
very
able
to
say
that
I'm
updating,
canto
to
be
lets
say
lit.
A
Where
electronics
sharing
is
caring
and
let's
say
that
explanation
mark
there
as
well.
Oh,
where
is
it
a
keyboard
which
doesn't
actually
have,
whereas,
if
one
HTML,
it's
actually
over
there,
learning
from
the
Scandinavian
keeper
to
the
u.s.
international
key
port
way
out,
so
that
long
story
I'm
not
going
to
explain
that
now
we're
adding
here
a
funeral
entries
we
are
adding
here,
delete,
read
electronics
and
voila
saving
that
one
stop
editing.
Actually,
let's
do
a
small
one
more
edit
here.
A
It's
actually
only
talk
at
this
one
to
a
specific
template,
so
I'm
gonna
go
to
our
documentation,
I'm
sure,
I'll,
scroll
down
and
I'm
gonna
actually
associate
this
extension
only
the
group
associated
team
signs.
So
let's
go
back
on
the
list.
Let's
add
a
filter
on
that
one
and
let's
stop
editing
to
entry
data.
Everything
is
fine.
Let's
go
the
croup
site
refresh.
A
What's
going
to
happen,
it
is
no
longer
cantos
or
electronics,
it
is
literary
electronics
and
you
can
actually
see
the
new
entry
and
there
and
it
has
to
updated
values
now
same
time
because
we
added
the
filter
based
on
the
template.
The
extension
is
no
longer
in
the
in
the
communication
site
level.
I,
don't
because
we
basically
filter,
and
we
say
that
this
is
only
to
be
applied
on
the
croup
side.
You
can
do
that
if
you
want,
you
don't
have
to
do
that.
A
If
you
don't
want,
let
me
out
here
one
more
entry
as
I'm
gonna,
actually
nope.
Let
me
actually
do
following
such
as
to
copy
the
values,
so
I'm
gonna
actually
copy
the
values
from
here
I'm
going
to
slightly
modify
the
entry
floor,
communication
side
to
complete
the
demo,
I'm,
not
gonna,
deep
dive
on
the
code
because
it
doesn't
really
in
this
case
it
doesn't
really
make
that
much
sense.
We're
gonna
cook,
a
JSON
file
code
is
available
for
you
today
from
Vsauce.
To
do
oh
sorry
from
github,
you
can
download
the
code.
A
You
can
take
advantage
of
that
one
I'm
gonna
still
one
more
thing:
let's
see
I'm
gonna
target
this
one
to
a
the
communication
side.
So
let's
actually
copy
that
one.
You
cannot
write
extension
target.
This
configuration
the
communication
side.
I
could
actually
target
if
I'm
actually
creating
a
list
view
command
set.
I
can
actually
add
this
one
to
be
in
a
separate,
separate
list
as
well.
There's
a
question
related
from
toad
can
I
add
a
multiple
entries
here.
A
If
I
remember
correctly
the
code
behind
of
this,
the
answer
is
no,
it
is
actually
filtering
based
on
de
the
web
template,
but
you
can
absolutely
have
multiple
Alliance
of
rows,
but
you
can
also,
if
you
have
a
list
we
have
common
set,
basically
want
to
have
buttons
for
all
of
the
document,
libraries
or
lists,
which
will
then
activate
and
run
code.
You
can
actually
target
your
list
via
common
sets
using
the
list
template
as
well.
A
So
I
can
naturally
they
one
on
one
here,
which
would
then
mean
that
it's
if
it's
a
list
view
common
set,
it
would
only
activate
on
a
document
library
in
this
case
we're
talking
about
a
footer
implementation.
So
that's
not
what
actually?
What
is
what
I
want
to
do?
I'm
gonna
take
the
location,
entry,
I'm
gonna,
put
this
one
in
the
location,
entry
and
save
it
in
in
the
list.
So
now
we
have
a
one
configuration
for
communications:
nine
one
configuration
for
croup
associated
team
sign.
They
are
both
application
customizers.
A
So
there
it's
a
application,
customized
or
entry.
So,
let's
actually
go
and
proving
you
that
it
is
actually
rendering
that
if
I
go
here,
there's
my
new
entry
and
you
can
actually
see
that
it
has
now
four
or
five
actually
buttons-
and
it's
now
saying
contoso,
electronics
in
this
side,
and
but
if
I
go
to
the
croup
side
and
filter
the
crude
side,
it
still
has
the
three
different
buttons
available
and
it
still
says
that
were
electronics
and
obviously
test
a
a
make
sure
that
everybody
gets
this.
A
This
is
on
run
time
happening
in
your
tenant.
So
if
I
create
a
new
site,
let's
create
a
communication.
Sign,
doesn't
really
matter
monthly
monthly,
called
demo.
It's
great
a
communication
side
they
are
pretty
fast,
actually
create.
So
let's
use
the
showcase.
That
looks
good
click,
a
finish
one,
two,
three
four
five
right
about
now
we
have
a
site
created
and
we
can
say
that
the
communication
site
footer
is
available
here
and
you
could
absolutely
configure
the
target
of
this
buttons
right
now
disappointing.
A
If
I
go
back
on
the
list,
they're
pointing
to
a
relative
paths
which
do
not
exist
within
distant,
so
I'm
not
going
to
even
click,
it
click
the
the
buttons
but
basically
we'd
configure
them
related
on
your
channel
toward
is
asking
is
the
data
into
my
extension,
cached
or
loaded
every
time
a
page
is
rendered,
so
it
is
technically
cached,
but
whenever
there's
a
change
in
the
Tanakh
whitelist
we're
refreshing
the
cache.
So
this
way,
basically
this
it
is
caching
in
the
right
way,
so
to
say
so,
works
in
the
right
way.
There's
no
delays!
A
If
you
do
a
modification,
your
changes
are
immediately
available
within
the
sites
which
is
super
super
cool.
There
was
one
thing,
one
thing
what
I
wasn't
meant
to
say,
but
maybe
I'll
well
we'll
talk
about
this
one
absolutely
later.
Oh,
yes,
the
one
thing,
but
I
wanted
to
still
pinpoint
ok.
Obviously,
in
this
case
still,
this
is
relatively
rough
from
the
admin
perspective
obvious
and
the
developer
can
define
if
they
want
these
kind
of
solutions
to
be
available
or
they
if
they,
if
they
want
this
kind
of
automation,
to
be
available
within
their
solution.
A
So
let
me
quickly
quickly
quickly
quickly.
This
is
only
gonna.
Take
it
one
second,
that
SP
dev
solutions.
We
started
my
machine
just
before
the
call
just
in
case
to
avoid
any
any
issues
with
the
with
the
skype.
So
here
we
go
so
here.
My
here
is
my
visual
studio
code,
so
the
the
developer
in
this
case
is
actually
defining
the
automation
which
will
be
applied
whenever
we
actually
install
the
solution
to
the
tenant
in
the
real
world.
A
In
the
future,
we
important
potentially
looking
into
having
a
nice
administrative
UI
where
the
admin
can
go
and
see.
Oh,
what
kind
of
components
do
I
have
available
and
then
check
check,
check
and
from
a
drop-down,
then
target
The
Temper
for
our
specific
templates
or
a
specific
entire
lists,
and
all
of
that
so
right
now
using
this
kind
of
a
list
based
configuration
and
it's
relatively
rough,
but
obviously
it
already
works
so
and
then
potentially
in
the
future.
A
If
there's
a
high
interest
by
the
administrators
for
this
to
make
make
it
more
simpler,
we
can
absolutely
expose
this.
This
kind
of
a
functionality
also
in
the
modern
admin
UI
and
yes,
absolutely
good
example-
is
the
SharePoint
starter
kit.
So
a
shipment
artist
has
a
portal
footer
and
the
co-op,
footer
and
cola
four
is
a
perfect
sample
for
this
one.
The
this
is
intentionally
slightly
more
simplified
because
the
coop
footer
actually
has
a
dependency
on
a
user
profile
property
which
you
cannot
automate
to
get
created
on
a
tenon.
A
So
this
clover
folder,
which
is
completely
configurable
by
anybody
and
reusable
by
anybody
just
by
configuring.
The
the
URL
entries
in
here
is
a
good
example.
How
to
make
these
things
happen,
cool,
but
that's
all
on
my
side,
I
think
it's
time
to
flip
to
AC
on
this
one
and
I
will
check
if
I
missed
any
any
questions.
As
AC
starts,
presenting
hey
just
making
sure
you
can
hear
me.
A
B
Okay,
awesome,
so
thanks
a
lot
for
giving
a
chance
to
show
this.
So
let
me
just
give
everybody
just
a
quick
heads-up
on
this,
so
I'm
not
I'm,
not
able
to
watch
the
chat
as
the
as
I'm
doing
this
little
presentation
here.
So
if
you
have
a
question
specifically
for
me,
if
you
just
do
it
at
a
C
on
your
question
when
I'm
done
and
Stefan
is
presenting,
I'll
go
back
and
look
at
the
questions,
then
an
answer
on
that.
So
what
do
I
want
to
show
here?
B
I'm
sure
I've
got
a
link
up
here
for
a
blog
just
give
you
a
chance
to
grab
it.
If
you
want
I've
got
a
four-part
blog
series
that
I
posted
last
week
about
the
topic
that
I'm
a
demo
on,
and
let
me
just
really
quickly
set
the
stage
if
you
on
what
you're
going
to
see
here
since
the
SharePoint
framework
came
out
a
lot
of
people
who
had
experience
using
angular
had
expressed
some.
You
know
they
wanted
to
be
able
to.
B
As
far
as
the
SharePoint
framework
is
concerned,
let's
just
say
that
react
is
one
that
they're
just
a
little
more
embracing
of,
because
that's
the
one
that
they
use
for
all
their
stuff
and
they
give
us
access
to
all
the
components
that
they
use,
but
there's
absolutely
nothing
that
SharePoint
engineering
team
has
done
to
make
it
harder
for
us
to
use
angular
inside
the
SharePoint
framework.
Really
the
challenges
that
we've
kind
of
come
in
that
we've
had
with
using
angular
or
the
SharePoint
framework,
is
all
rooted
in
how
the
how
angular
is
engineered.
B
So
it's
nothing
to
do
the
SharePoint
framework
and
there's
honestly,
nothing
that
Microsoft
can
do
to
make
this
easier
for
us.
So
there's
really
been
up
until
May
we
had
one
option,
which
is
to
build
an
angular
application
and
when
I
say
anger,
I'm,
meaning
like
the
current
versions
of
angular,
so
angular,
2
or
4,
or
5
or
6.
B
So
what
we
which
you
could
do
is
there's
blog
posts
that
show
you
how
to
do
this
about
how
to
build
an
angular
application
and
then
load
that
are
hosted
inside
of
a
web
part.
The
challenge
with
that
is
that
the
thing
that
anger
or
wants
is
that
it
needs
to
has
this
concept
of
one
component
on
the
page
or
one
root-level
component
on
the
page.
That
angular
looks
to
be
the
bootstrapper
for
everything
else,
angular
on
the
page.
So
the
challenge
we
were
building
a
normal
website
or
normal
web
app.
B
That's
not
a
big
deal,
because
it's
a
developer.
We
own
everything
on
the
page,
but
in
SharePoint
or
what
I
like
to
refer
to
this
as
a
a
composable
page,
one
that
as
a
developer
I,
can
build
something.
But
there's
no
telling
what's
going
to
be
on
the
page
that,
where
my
components
going
to
go
it
you
know,
Vesta
could
be
adding
other
webparts
on
the
page
and
the
challenge
with
that
is
that
if
I
have
two
angular
webparts
are
going
to
be
on
the
page.
B
Well,
I
no
longer
have
this
one
top
level
component
that
can
orchestrate
the
bootstrapping
of
everybody
else
in
the
page.
There's
a
couple
little
tips
and
tricks
that
people
have
come
up
with
on
how
to
do
this
dynamically.
But
the
challenge
in
doing
this
dynamically
is
that
we
can't
take
advantage
of
some
of
the
performance
stuff,
and
so
what
angular
did
is
back
in
in
May
when
they
released
angular
6.
B
All
a
custom
element
is:
is
it's
just
a
piece
of
JavaScript
that
registers
itself
into
the
native
API
in
the
browsers
that
support
this
concept
and
the
pros
that
don't
have
polyfills
to
fix
this,
and
you
then
can
just
use
your
component
on
the
page.
So,
for
example,
just
to
show
you
it
looks
like
I
could
write
a
component
that
is
called
the
Microsoft
cloud
show
and
would
render
out
or
know
how
to
how
to
work
with
this
component
and
know
how
to
deal
with
the
properties
coming
in
as
well
as
with
the
event.
B
What
anger
elements
does
is
it
gives
us
the
ability
to
to
do
this.
So
let
me
show
you
how
to
do
this
there's
a
couple
different
ways.
You
can
do
it
or
there's
really
two
options
of
how
you
can
do
this
one
option
is
to
create
a
SharePoint
framework
project
using
the
yeoman
SharePoint
framework
generator
and
I'm
not
going
to
go
through
doing
this
I'm
just
going
to
show
you
this.
B
But
what
you
see
here,
if
I
created
a
standard,
SharePoint
framework
project,
so
you
can
see
all
the
SharePoint
framework
II
stuff
up
here
and
there's
your
hello
world
web
part
and
what
I
did
is
I
then
went
through
and
I
added
all
the
stuff
to
my
project,
so
specifically
all
the
NPM
packages
that
are
needed
for
angular.
So
that's
the
stuff
that
I've
highlighted
up
here
and
there's
a
couple
other
things.
B
Actually,
these
three
guys
down
here
are
angular
II
kind
of
things
as
well
and
manually
add
that
stuff
and
then
you
have
to
go,
make
another
change
to
your
gulp
file.
Where
you
add
in
all
of
the
stuff,
you
see
that
I
have
highlighted
right
here
and
what
this
is
effectively
doing.
Is
it's
telling
the
the
gulp
task
when
you're
building
the
project?
B
It's
telling
it
that
when
it
needs
to
go
through
and
not
only
also
build
stuff
from
for
angular
in
a
certain
way,
but
it
also
tells
it
of
things
that
needs
to
get
sucked
into
the
bundle
for
this
component
to
work
so
I'm
doing
this
all
in
one
single
project,
so
I
call
this
option.
One,
the
big
omnibus
project,
so
here
I've
got
my
angular,
my
angular
application.
So
it's
got
my
top-level
angular
module
that
I've
created
and
then
I
have
my
component
that
I've
created
as
well
and
so
in
this
component.
B
Here
all
I
have
is
just
a
div.
That's
gonna
write
a
message:
that's
being
passed
in,
as
you
can
see
here
is
an
input
parameter
and
then
I
have
an
input,
tag
and
a
button.
That's
gonna
raise
an
event
called
the
element,
button,
click,
and
so,
when
I
click
this
button,
it's
gonna
fire.
This
event
that
you
see
down
here
and
then
that's
gonna
get
a
message
back
all
right
now.
How
do
we
handle
this
or
how
do
I?
How
do
I
go
about
making
this?
What's
called
an
angular
element
or
a
custom
element?
B
Well,
the
way
that
that's
done
is
in
an
angular.
Is
that
you
import
this
thing
called
the
create
custom
element
and
you're
gonna
there's
a
usually.
You
would
see
a
bootstrap
option
right
here
on
the
ng
module,
you're
gonna
get
rid
of
that
and
instead
replace
it
with
entry
components
and
then
down
here
in
this
method
called
ng
butdo
bootstrap.
What
this
is
gonna
do
is
this
is
going
to
check
to
see.
B
Is
there
already
an
HTML
tag
in
the
browser
it's
been
registered
called
a
pillow
world
and
if
there's
not
we're
gonna
create
one
and
then
we're
gonna
create
an
instance
of
our
component
and
then
as
a
custom
element
and
then
we're
going
to
tell
custom
elements
that
define
that's
gonna
tell
the
browser
pay.
This
tag
is
really
associated
with
this
javascript
class.
So
how
do
I
use
that
well
I
come
over
here
and
my
back
into
my
web
part.
What
you
see
here
is
I'm
doing
a
few
things.
B
I
am
I'm
going
to
import
it
right
here
and
I'll.
Explain
some
stuff
above
in
just
a
minute.
I'm
gonna
import
right
here
and
then
in
the
render
method.
I
have
to
tell
it
that
I
want
to
use
this
platform.
Browser
dynamic,
that's
coming
from
angular
and
it's
telling
it
how
to
how
to
bootstrap
the
application
visa
can't
sell
bootstrap
itself
for
various
reasons
of
how
the
thing
is
built
and
then
I'm
simply
gonna,
say:
let's
write
out
our
new
custom
tag.
B
You
see
here,
I'm
assigning
the
message
property
equal
to
the
description
that's
being
passed
in,
which
is
a
property
on
our
web
part
and
then
I'm
going
to
get
a
reference
to
that
element
and
just
add
to
the
page
and
then
I
add
an
event
listener.
So
I
can
see
what
happens.
So.
Let
me
go
ahead
and
run
this
and
I'll
show
you
how
this
works.
B
So,
let's
come
over
here,
open
up
the
sky
and
I'm
gonna
do
a
gulp
serve
and
that's
because
IBM
used
to
be
eight
and
then
do
a
gulp
serve
and
not
spending
a
lot
of
time
on
the
code
here,
because
Stefan's
got
a
good
demo
write
that
for
me
and
so
I
want
to
make
sure
I
don't
take
up
his
time.
But
my
blog
post
series
does
explain
this
quite
a
bit
as
well,
if
you're
interested
alright.
So
how
does
this
work?
Well,
let's
go
over
here,
I'm
gonna,
add
in
a
new
web
part.
B
Oh,
so
it
takes
a
second
for
you'll
notice
that
the
build
process
takes
a
second
or
two.
So
me,
let
me
jump
back
here,
make
sure
it's
done
yep.
It's
done.
Okay
takes
a
bit
longer
normally
with
an
angular
project.
So
here
we
go.
We
can
see
that
are
those
our
message,
helloworld
being
passed
in
so
here
I'll
change
our
description
here,
hello
angular,
so
you
can
see
here
a
component
is
being
written
out.
B
It
is
getting
the
message
being
passed
in
and
I
can
send
a
message
back
to
my
web
part
as
hello
SharePoint
and
send
it
to
the
hosting
web
part,
but
you
see
was
being
tagged
or
is
being
captured
as
an
event
and
raised
as
an
alert.
Now
that's
all
fine
and
good,
and
you
see
it
work,
but
there's
a
with
this
approach.
B
There's
there
is
the
challenge:
2.8
Meg's,
all
right
now.
This
is
gonna,
be
a
little
bit
smaller
when
you
deploy
it
because
I'm
not
doing
gzip
compression.
These
is
all
coming
from
my
local
web
server
that
gulp
the
gulp
serve
task
fired
up.
So
when
you
put
this
inside
of
office,
365
CLI
or
your
own
sorry,
the
office
365
CDN,
it's
gonna
be
smaller,
but
it's
not
gonna,
be
that
much
smaller,
and
why
is
that?
The
reason
for
this
is
because
there's
a
lot
of
details
to
it.
B
But
let
me
just
I'll
spare
you
a
lot
of
the
details
that
essentially
we
can't
do
this
concept
called
dynamic
or
ahead
of
time
compilation.
The
way
angular
works
is
that,
let's
say
the
angular
library
is
a
Meg
big.
Well,
that
is
a
compiler.
That's
going
to
compile
your
application
dynamically
at
runtime,
but
one
of
the
things
that
angular
can
do
is
ahead
of
time
compilation.
B
So
it
can
say:
I
can
build
your
application
and
throw
away
all
the
parts
of
angular
that
I
don't
need
that
your
application
isn't
using
and
have
that
as
the
final
outputted
bundle.
So
that
means
that
now
the
angular
library
is
half
as
big,
because
the
compiler
is
gone
and
I'm
able
to
do
this
concepts
of
tree
shaking,
which
gets
rid
of
all
the
parts
of
angular
that
my
app
doesn't
use.
Now.
B
The
challenge
with
that
is,
we
can't
do
that
in
one
project
because
well
we,
the
SharePoint
framework,
currently
uses
web
pack
3
the
äôt
needs
web
pack
for
äôt
is
ahead
of
time.
Compilation
needs
web
pack
4.
So,
let's
just
say
you,
it's
not
gonna
work
and
if
you
want
to
know
more
details,
go
read
the
blog
post,
but
if
you
come
over
here,
this
is
a
project
that
I've
created
using
the
angular
CLI.
B
If
I
come
look
at
this
angular
module,
it
looks
the
exact
same
as
the
one
I
just
showed
you
a
second
ago.
In
fact,
this
one
over
here,
the
app
component.
He
looks
the
exact
same
as
well.
The
only
difference
is
is
that
his
template
is
an
HTML
file
and
it's
the
same
code.
Now,
what
I
did
to
make
my
life
a
little
bit
easier
is
in
the
package.
Die
JSON
file,
I
created
a
new
task
here
and
what
this
task
does
is.
B
This
is
going
to
first
build
the
project
for
production,
which
is
going
to
run
ahead
of
time.
Compilation
this
little
setting
here
just
changes
how
I
look,
output
files
are
going
to
get
generated,
and
then
this
next
step
that
you
see
right
here
is
going
to
say,
go,
take
all
the
files
that
are
created,
which
is
runtime,
polyfills
scripts,
name,
J
s,
which
you
can
see
those
guys
listed
right
here,
main
polyfills,
runtime
and
scripts,
and
it
says,
combine
all
those
into
one
file
and
stick
those
into
another
folder.
B
That's
right
beside
you,
which
is
my
SharePoint
framework
project.
So
I
have
this
one
called
ng,
HelloWorld
J
s.
So
to
run
this
task,
I
would
say:
NPM
space
run
space,
SPF
X
build
well.
What
do
I
have
been
in
my
SharePoint
framework
project?
Well,
here,
what
have
done
is
I've
created
a
SharePoint
framework
project
like
I
normally
would
create
nothing
special
about
it.
So
here
there
you
don't
see
anything
special
with
this
guy,
except
I,
do
have
two
additional
packages
that
I've
included.
These
are
polyfills
for
browsers
that
don't
support
custom
elements.
B
Natively
here
is
the
JavaScript
file
that
was
generated
by
the
angular
compiler
right
and
then
to
use
it
notice
here.
Gulp
file,
no
changes,
but
in
the
web
part
itself,
all
I'm
doing
is
importing
that
javascript
file
that
I
just
talked
about,
and
then
the
usage
of
this,
where
the
rendering
method
is
much
cleaner
than
what
you
saw
just
a
minute
ago,
when
I
had
to
do
that
platform,
browser
dynamic
because
I'm
no
longer
doing
a
dynamic
compilation.
It's
all
it's
already
done
so
now.
B
When
I
run
this
project
and
I
say
nvm
use
v8,
that's
just
a
thing
with
my
machine.
You
know
I'm
normally
do
that
and
then
I
say
gulp
serve
now
watch
this.
This
is
gonna,
be
a
much
better
story
and
then
the
story
gets
even
better
and
then
I'm
gonna
wrap
it
up
and
give
stuff
on
at
least
10
minutes
at
the
end,
all
right.
So
this
one.
Let
me
go
through
and
open
up.
B
B
B
Here's
one
using
the
new
IV
rendering
engine.
This
is
a
beta
check.
This
out,
I'm
gonna
go
over
here.
I'm
gonna
first
show
you
the
source
of
what
this
page
looks
like.
There's
nothing:
fancy
with
this
I'm
simply
going
through
and
having
a
script
tag
right
here:
loading
in
bundle,
j
s
and
then
I'm
using
my
new
hello
world
component
notice,
there's
no
angle
reference
or
anything
on
the
page.
B
Now,
let's
refresh
the
page
and
tada
gzipped
3.5
k
so
workers,
we
should
see
that
demo
I
just
ran,
which
is
about
300,
K
and
I,
said
that
it
should
get
down
to
about
80
K
when
you
gzip
it.
We
should
see
when
angler
seven
comes
out
that
she
followed
well
below
30
or
40.
K
need
to
get
even
smaller
so
with
that.
I
now
think
that
Inger
elements
is
a
decent
option
for
building
your
angular
based
applications.
B
A
Stefan,
it's
gonna
be
crowded
as
tight
for
you,
but
thank
you
AC
for
this
one
as
fun.
Can
you
start
sharing
and
while
they're
doing
this
moving
over,
so
it's
obviously
the
question
for
the
we've
been
having
a
lot
of
many
many
many
times
might
have
been
asked
the
question:
why
don't
you
support
angular
like
Asus,
and
we
actually
do?
A
We
do
support
angular,
which
has
done
support
angular
by
default
in
the
yeoman
scaffolding,
and
that's
a
completely
different
discussion
now,
even
though
we
would
be
supporting
the
default
scaffolding,
we
would
have
that
size
problem
which
they
say
actually
and
showed
as
well,
so
obviously
we're
looking
into
now.
How
do
we
make
this
happen
in
the
future
in
the
optimal
way,
but
moving
from
angular
is
slightly
on
angular
topics
to
some
other
frameworks
as
well.
A
Quite
often,
we
covered
a
question
on
why
wouldn't
okay,
angular
has
the
size
problem
potentially
which
well
and
Google
or
Microsoft,
should
fix
and
that's
a
different
discussion,
and
they
are
what
about
handlebars?
What
about
views
chairs?
What
about
the
other
stuff?
Why
aren't
those
actually
support
it
in
the
yeoman
templates
and
that's
where
Stefan
is
coming
in
Stefan
yeah?
You.
A
C
So
actually,
the
SPX
yeoman
generators
based
on
the
yeoman
template
engine
that
has
been
released
and
this
really
popular
on
the
web
and
this
yeoman
generators
have
some
called
functionality,
which
means
composability,
which
basically
means
you
can
use
whatever
it.
Generator
is
out
there
in
the
world
to
use
in
your
own
generator
that
you
build
upon
and
what
I
actually
did
I
like
to
show
you
I
created
a
complete
new
generator
based
on
the
default
SPF
x,
sharepoint
generator,
and
let
me
show
you
quick
this
one
actually
does
so.
C
The
name
is
P
and
P,
slash
s
P
of
X,
and
the
first
thing
you
notice,
once
it's
launched,
that
we
will
have
a
nice
logo
so
yeah
and
the
first
thing.
What
you
have
here
is
dissolve
PNP
community
generator.
We
have
support
currently
over
the
handlebars,
but
there
is
potentially
few
chairs
coming
out
pretty
soon,
and
you
can
also
to
also
do
the
feet
of
fall
tech
on
react.
She
has
not
that
she
hasn't
no
framework
GS.
These
are
the
default.
C
Ffx
generators
in
this
case
I
currently
use
the
handlebar
generator,
and
the
next
question
I
get
asked
is
what
libraries
do
you
want
to
have
in
my
project?
So,
for
example,
I
want
to
use
jQuery
and
you
want
to
use
pink
peach
s.
This
second
question
also
works
for
the
default
generator.
So
when
you
create,
for
example,
react
project
or
a
local
project,
then
jQuery
and
PMPs
will
be
automatically
added
on
top
of
the
default
generator.
C
So
next
question
I
can
chew
two
flavours
for
jQuery
the
version
3
or
diversion
I
choose
here
now
the
version
3
and
what
you
see
now.
This
is
default.
Dialog
of
the
SPF
X
generator
to
ask
me
some
additional
things
so
I'm,
currently
in
a
folder
that
is
named
community
I'm
fine
with
that
I
want
to
build
for
the
lastest
latest
Shepherd
online
I
use
the
print
folder
I'm
not
decided
yet
and
I
want
to
create
a
web
part.
Web
part
is
hello,
world
description
and
now
it
starts
the
NPM
install.
C
But
what
you
see
up
here
so
this
appear
is
default
s
P
of
X
generator
that
creates
all
the
assets
that
we
need
for
our
development.
But
on
top
of
that,
if
you
update
that
these
years,
a
CSS
file,
I've
updated
the
web
part
file,
I
have
deployed
an
additional
file
which
is
called
handlebar
but
HPS,
which
is
a
handlebar
sprout
and
cope
with
some
configuration
for
the
copy
static
assets
in
there.
C
So,
while
this
is
installing
what
is
already
in
this
project,
you
see
here
what
you
already
have
seen
in
in
every
demo
that
we
need
to
have
to
run
in
an
SP
FX
project
to
run
handlebars.
We
have
to
have
the
configure
backpack
here.
We
have
some
additional
gulp
tasks
here,
configure
it
in
order
to
to
work
that
this
properly
work,
but
what
we
also
do.
It
is,
for
example,
when
I
go
here
to
the
web
part
code
and
say
hello,
world
Bach
TS.
C
This
code
actually
has
a
little
bit
changed
instead
of
the
default
non
framework
generator
because
I
already
have
important
here.
The
handle
bars
to
make
using
bar
apart
from
was
was
this
framework
and
also
load
here,
a
template
file
which
is
stored
in
this
folder
HPS
component
and
handle
that
the
whole
idea
behind
handlebars
is
to
have
a
simple
template
engine.
So
what
you
see
actually
in
here
is
some
property
binding
and
just
simple
plain
HTML.
C
Already
you
have
the
type
so
jQuery
installed,
you
have
a
fennel
bars
and
also
Jake
very
installed
the
version
3.
So
you
basically
you're
fine
to
start
with
development
was
the
development
was
pink,
PJs
and
and
handlebars.
So
let
me
run
the
code,
so
I
have
to
go
through
the
debugging,
so
little
tricky
serve.
C
So
and
what
you
I
can
now
add
the
web
part
to
my
page,
so,
let's
say
hello
world,
and
just
because
this
is
just
an
HTML
template.
What
I
can
do
in
here?
Let's
say
I
want
to
have
this
really
dirty,
but
for
style
and
want
to
have
the
background
colors
that
to
think,
for
example,
as
just
safety
HBS.
Well
now
you
see
that
the
building
comes
in
and
automatically
the
bad
part
was
to
change.
C
The
things
will
be
loaded
on
the
page,
so,
but
also
can
do
here
is,
for
example,
change
the
text
at
P&P,
slash
aspect,
x4,
handlebars
and
I.
Even
can
edit
the
properties
to
hello,
there's
our
so
basically
fine
to
go,
and-
and
this
comes
from
the
need
that
I,
you
have
to
always
configure
a
lot
of
things
when
you
want
to
start
a
new
project,
but
this
yeoman
generator
helps
you
a
lot
to
make
things
easier,
and
this
is
basically
how
it
works
on
the
backend
side.
C
A
Good,
so
from
a
timing
perspective
I
do
apologize
as
Stefan.
We
didn't
give
you
too
much
time,
but
let
me
reiterate
what
you
were
seeing,
so
we
are
basically
announcing
an
availability
of
a
new
open
source
project
underneath
the
BMP
print,
which
is
the
SharePoint
framework,
yeoman
generator,
and
this
is
actually
extending
the
out-of-the-box
yeoman
generator,
which
is
coming
from
engineering.
We
in
engineering
are
looking
into
making
that
one
potentially
an
open
source
at
some
point,
but
this
is
the
way
we
can
then
right
now
already
provide
handlebars
or
support
for
p.m.
A
PJs,
and
it
is
actually
using
the
art
of
the
box
one
under
under
the
hoods.
So
this
is
just
extending
the
out-of-the-box
human
yeoman
projects,
and
we
know
that
there
are
certain
community
members
who've
been
building
some
of
these
templates
and
we're
looking
into
now
and
let's
say,
consolidating
that
work
on
the
one
single
print
so
to
say,
or
one
single
project
so
that
we
get
handlebars.
A
We
could
potentially
even
angular
elements,
even
though
that
doesn't
quite
fit
that
well
on
this
model
and
view
chaise
and
other
frameworks
inside
of
the
one
simple
solution
and
then
what
you
can
do.
You
can
just
run
a
npm
install
to
be
the
SPF
x,
PM,
p,
SP,
FX
generator,
and
that
will
actually
pull
down
everything
what's
needed
and
it
will
then
basically
add
new
options
available
when
you're
creating
a
project.
A
That's
what
it
means
in
practice,
so
you
can
really
easily
also
use
whatever
additional
JavaScript
frameworks
you
prefer,
or
if
you
really
want
to
have
some
you're
coming
up
with
some
new
JavaScript
framework.
You
want
to
provide
that
to
be
available
for
SharePoint
framework
and
developers.
You
can
absolutely
contribute
on
this
project
and
provide
your
framework
to
be
available
as
one
of
the
options,
cool
and
I
think
that's
it
for
this
one.
So
I'm
gonna
flip
the
slide
back
on
just
for
closure.
A
So
we
did
a
pretty
busy
call
again
we're
kind
of
a
debating
on
three
demos.
Typically,
Nicole
is
slightly
too
much,
but
at
this
time
I
barely
got
it
in
and
maybe
we'll.
We
need
to.
Definitely
concentrate
on
having
to
in
the
future.
It
was
me
actually
change
the
agenda
again
squeezing
in
the
data
not
quite
excellent
option,
but
we
don't
have
a
time
for
Q&A
today.
A
If
you
have
any
questions
related
on
SharePoint
framework
or
the
topics
bits
of
winter
today,
we
will
have
a
time
for
Q&A
on
the
Thursdays
SharePoint
framework
by
via
click
on
call.
So
that's
on
Thursday,
if
you
don't
have
that
recurrent
invite
in
your
calendar-
and
you
want
to
have
it
in
your
calendar-
go
to
AKMs
and
p
scroll
down
on
that
page.
There's
an
invites
available
for
you
to
put
on
your
calendar
and
then
you
can
ask
questions
more
on
these
things.
Now.
A
On
many
I
think,
that's
it
we're
running
out
of
time
anyway.
Thank
you,
everybody
for
watching
this,
the
video
will
be
a
video,
was
recorded
successfully,
no
skype
issues
this
time.
So
the
video
is
available
in
YouTube
channel
within
24
hours.
There
will
be
a
blog
post,
also
in
the
SharePoint
dev
blog,
and
you
can
see
the
social
media
communications
immediately
when
that
happens.
A
But
thank
you,
everybody
we'll
add
all
of
the
links
on
topics
which
we
went
through
to
that
blog
post
and
associate
that
in
the
YouTube
videos
and
all
of
that
and
a
final
thing,
maybe
to
say:
if
there's
anybody
in
this
call,
who
wants
to
contribute
and
wants
to
do
a
live
demo
in
any
of
these
course
just
reach
out
in
the
social
media
and
let's
see
what
you
contributed
or
Buddhism's,
but
you
want
to
show
your
sample
from
a
key
table.
That's
absolutely
welcome
in
our
future
course
as
well,
but
down
here
buddy.