►
From YouTube: SPFx JavaScript SIG 26th of October, 2017
Description
Bi-weekly community call around SharePoint Framework and JavaScript development in SharePoint platform. This is recording from the 26th of October call. You can download recurrent invite from http://aka.ms/SPPnP-JSSIG.
A
Good
so
welcome
everybody.
This
is
the
SharePoint
patterns
and
practices
bi-weekly,
a
special
interest
group
for
SharePoint
framework
and
JavaScript
development-
and
this
is
talk,
talk,
wer,
2016
edition,
so
the
autumn
is
coming
actually
in
Helsinki.
It
is
snowing
first
time
this
year
of
first
time
this
autumn
and
we
got
like
5
to
7
centimeters
now
in
the
in
the
yard,
which
is
pretty
weird
anyway.
Thank
you,
everybody
for
joining
and
let's
see
how
many
people
we
get
on
this
call.
A
This
time
everything
is
obviously
getting
recorded,
will
get
again
the
video
and
recording
and
demos
everything
shared
in
YouTube
within
24
hours,
so
in
the
in
the
PNP
YouTube
channel,
you
can
always
find
the
previous
recordings
as
well.
My
name
is
Josiah
Vernon
I'm,
a
Senior
Program
Manager
from
the
SharePoint
engineering
site
and
I'll
be
again
leading
the
call
today
we
do
have
two
different
demos
coming
up
today,
but
before
we
go
to
the
actual
agenda
quickly
explaining
what
this
special
interest
group
is
all
about.
A
So
the
this
is
the
the
SharePoint
framework
special
interest
group.
It's
a
bi-weekly
call
where
we
actually
concentrate
on
having
community
demos
and
also
the
updated
situation
around
the
SharePoint
framework
we
actually
in
the
PMP.
We
do
have
two
different
special
interest
group
sessions
and
every
single
Thursday.
We
do
have
a
call
so
bi-weekly
it's,
but
it's
about
SharePoint
framework
and
JavaScript
development
and
bi-weekly.
It
is
around
p.m.
A
Now
to
in
today's
call,
we
actually
again
kind
of
skip
the
BMP
JavaScript
core
section
explicitly,
because
Patrick
who's
leading
that
effort
is
still
happily
on
parental
leave.
I
was
just
chatting
with
him
on
a
slack.
Yes,
we
are
using
slack
to
numerous
reasons-
let's
not
actually
tackle
on
that
one,
but
he's
coming
back
on
end
of
November
and
will
absolutely
get
a
speed-up
on
the
BMV
javascriptcore
side
and
when
he
is
back
as
well,
there
is
actually
stuff
happening
on
there.
A
People
are
using
that
quite
nicely
and
there's
new
development
even
happening
by
community
contributions.
Today,
what
we're
going
to
do
anyway
and
we'll
concentrate
on
the
SharePoint
framework
latest
news,
so
kind
of
a
update
it.
If
what
has
happened
within
the
past
two
weeks
and
I'm
gonna
show
a
preview
again
on
something
which
I'm
not
can
actually
explain
in
here,
something
which
is
coming
out
relatively
soon
as
well,
and
then,
after
that,
we'll
have
to
lift
separate
demos.
A
So
my
camera
line
will
have
start
with
an
introduction
of
community
solutions,
and
these
are
essentially
set
of
polished,
more
polished
samples
which
are
ready
to
be
used
for
you
within
your
production
and
Mike
is
gonna,
go
through
what
is
available
right
now.
What
what's
the
plan
for
the
future
on
that
one
and
how
you
can
actually
use
them,
and
then
we
have
nicholasvincent
in
the
call
as
well,
so
Michaels
can
actually
talk
about
the
run
once
SharePoint
framer
application
customizer.
So
this
is
done.
A
This
is
super
super
simplistic,
actually
implementation
or
code
piece,
but
it's
an
interesting
pattern
and
it's
an
interesting
pattern
for
those
who've
been
hanging
alone
within
the
SharePoint
for
quite
a
long
time,
because
quite
often
we
have
that
business
requirement
that
hey.
We
need
to
execute
something
whenever
to
use
her
first
come
to
the
site.
We
need
to
make
something
happened
whenever
the
user
comes
to
the
site
the
first
time,
and
after
that,
we
don't
wanna,
actually
do
that
so
Michael
I'll
actually
contribute
at
this
nice
simplest
example
showing
a
one
pattern
on
that
one.
A
We
can
talk
about
alternative
options
and
all
of
that
during
that
section
as
well,
depending
on
how
much
time
and
Mimi
and
Mike
and
Michael
actually
kind
of
take,
we
should
have
some
time
for
the
Q&A
and
open
discussion
as
well.
So
if
you
have
any
random
questions,
if
you
have
challenges,
if
you
want
to
provide
feedback
on
the
engineering
on
our
documentation,
samples
guidance
whatever,
please
do
so
and
during
obviously
during
the
call
feel
free
to
use
the
I
window
as
much
as
possible.
A
Well
try
to
follow
up
on
on
the
questions
and
as
we
move
along
now,
let
me
actually
start
Oh
before
we
go
to
the
SharePoint
framework
news
and
latest
on
that
one,
a
few
notes,
and
here
as
opportunities
for
participate
in
the
PNP
to
SharePoint
SharePoint
framework
special
interest
group
and
I'm
gonna
mute
somebody
from
here.
So
we're
not
actually
kind
of
have
some
background
notice.
There
we
go.
So
if
you
are
interested,
we
obviously
are
always
looking
for
community
contributions.
A
And
so
one
way,
if
you
have
to
contribute,
is
to
actually
be
in
this
course
and
also
do
a
demo
around
your
sample
or
a
solution
which
might
be
contributed
in
the
github,
but
that
not
necessarily
even
required.
So
if
you've
done
something
super
cool
in
SharePoint
framework,
why
not
actually
demonstrate
that
to
the
others,
get
some
credits
out
of
that
on
as
well?
And
we
can
talk
about
the
sample
during
this
call.
You
can
absolutely
contribute
in
a
github
in
the
SharePoint
github
organization,
and
we
have
quite
a
few
repositories
there.
A
But
if
you
go
through
our
monthly
communications
in
the
dev
tariffs
that
comes
last
blocks,
you'll
find
out
the
meaning
of
each
repository
hopefully,
and
they
they
should
have
pretty
okay,
a
readme
files
and
clarification.
What
the
repositories
are
all
about.
You
can
absolutely
also
demonstrate
the
usage
of
the
SPP
and
BJ's
in
the
project
and
that
these
are
BMP
J's
core
component,
where
the,
where
the
story
of
this
special
interest
group
actually
started,
and
that
was
before
SharePoint
favorite
game
live
and
also
provide
feedback.
So
please
keep
on
that
feedback.
A
Coming
we're
super
interested
on
helping
you
if
you
feel
bad
around
chip
and
framework
or
the
direction
of
our
development,
something
as
guidance
is
missing.
The
samples
is
missing.
Please
let
us
know
we
actually
want
to
address
those.
So
the
open,
negative
feedback
absolutely
welcome
as
well.
It
doesn't
have
to
be
a
positive
you.
We
want
to
address
and
help
you
to
be
successful
with
SharePoint
in
the
future
as
well.
Now,
let's
actually
move
on
to
the
SharePoint
framework,
so
I
have
few
slides
and
I'm
gonna.
A
So
hopefully,
your
company
does
not
have
a
policy
that,
if
it's
not
in
MST-
and
it's
not
true,
that
would
be
false
because
all
of
our
latest
and
greatest
documentation
will
be
in
this
platform.
One
of
the
advantages
of
this
Dogstar
microsoft.com
platform
is
that
you
can
actually
contribute.
There's
commenting
systems,
there's
alerting
systems,
there's
a
lot
of
other
benefits
on
this
one
as
well.
Msdn
essentially
was
too
old
and
not
flexible
enough
for
community
contributions
and
not
fast
enough
for
us
to
contribute
and
to
provide
guidance
for
the
community,
but
have
a
look.
A
If
something
is
missing.
If
something
is
wrong,
let
us
know
we'll
fix
it
and
we'll
move
along
in
the
future
by
using
this
one,
a
lot
of
our
existing
active
MST
and
articles
will
be
moved
here
as
well,
and
all
those
who
are
looking
into
adding
additional
content
here
as
well,
one
of
the
examples
being,
for
example,
the
rest
api
documentation,
which
it's
I
think
it's
fair
to
say
that
it's
not
in
the
right
level
right
now
and
we
need
to
get
some
additional
investments
on
the
REST
API
documentation.
A
So
people
actually
know
what
are
the
rest.
Api
is
which
are
available,
which
are
supported
which
we
can
use
and
how
you
how
to
achieve
our
typical
scenarios
now
and
just
out
of
letting
you
know.
I
was
just
checking
the
statistics
this
morning
from
the
docstore
microsoft.com
and
the
most
active,
obviously
pages.
They
are
SharePoint
framework.
They
are
REST
API,
so
people
are
looking
more
and
more
on
the
future
ways
and
the
future
proven
ways
of
doing
customizations
within
the
SharePoint.
A
A
Chris
Chris
can't
actually
contributed
already
with
a
one
additional
control
and
looking
additional
things
here
as
well,
but
this
is
a
set
of
controls
which
are
super
easy
for
you
to
use
within
our
implementation
and
they
are
hosted
within
the
within
the
NPM
and
there
will
be
a
referent.
They
will
be
relative,
histone
reference
and
available
in
CD
ends
as
well.
A
Oh
there's
a
good
comment
from
Russell
Cove
should
move
office,
UI
fabric
dogs,
the
dogs
to
my
staff
come
absolutely
agree
on
that,
and
that
is
actually
in
progress,
but
it
will
still
take
a
while,
but
that's
gonna
happen.
Absolutely
we
want
to
make
them
do
available
in
there
in
a
one
centralized
location.
Technically,
the
office
you
have
fabric
is
is
one
of
those
things
where
we,
it
doesn't.
A
It's
not
really
around
just
sharepoint,
obviously
high
fabric
components
and
their
styles,
and
course
styles
are
used
outside
of
sharepoint
context
as
well,
so
we'll
see
where
it
actually
lands,
but
it
is
in
progress
to
get
to
the
cost
of
Microsoft
ago.
Now,
the
last
the
one
thing,
what
I
wanted
to
also
pinpoint
I
didn't
update
the
picture,
but
I'm
gonna
do
a
quick
demo
on
this
one
as
well.
We
should
be
interested
on
actually
getting
your
feedback
on
this
one.
A
So
one
of
the
things
what
we
are
constantly
getting
as
a
feedback
from
the
community
is
that
a
especially
for
let's
say
people
who
are
more
used
to
old,
SharePoint
farm
solution
development.
Is
that
hey
I,
don't
like
the
SharePoint
framework,
because
I
need
to
do
stuff
in
the
console
and
doing
that?
All
of
those
commands
in
a
console,
I
can't
remember
done
so.
A
I
want
to
have
a
native
or
I
want
to
have
a
better
experience
in
Visual
Studio
IDE,
not
within
the
visual
studio
code,
and
we
do
have
this
community
open
source
driven
extension
where
well.
It
has
been
originally
created
by
Paul,
shuffling
and
Eric
jobs
and
I
want
to
help
slightly
just
small,
posing
things
here
here
and
there
we're
looking
into
evolving
this
one
in
the
future
as
well.
A
So,
but
we
want
to
understand
a
is
it
useful,
B
is
their
interest,
or
is
it
something
that
people
are
just
saying
that
yeah
I
want
to
do
this
in
a
visual
studio,
but
they're
not
actually
really
willing
to
do
so?
So
what
I
wanted
to
do
today
before
we
go
to
the
mics
and
makalah
session,
is
to
quickly
show
you
how
that
works.
I'm
gonna
actually
run
it
in
the
debug
mode
directly
in
Visual
Studio,
but
show
you
what
does
it
actually
provide
and
how
does
it
actually
work?
A
So
you'll
get
some
sort
of
a
feeling
and
what
does
it
actually
do?
But
we
would
absolutely
appreciate
feedback
on
this
one,
for
example,
using
the
issue
lists
in
the
in
the
github,
where
this
development
happens
or
then
in
the
s-pen
dev
talks
issue
list
or
in
the
social
media.
If
something
is
missing,
let
us
know
and
we'll
try
to
address
that
in
the
future.
A
The
realities
of
our
let's
say,
investments
and
the
engineering
also
in
Microsoft
is
that
we
need
to
understand
the
demand
and
then
we'll
obviously
assign
our
resources
for
those
areas
where
we
have
to
be
customer
and
without
understanding
the
demand,
for
example,
for
this
one.
We
don't
know
if
we
will
be
investing
on
this.
So
please
let
us
know
how
useful
this
one
is,
or
you
can
use
time
window
right
now
during
my
demo
as
well,
oh
yeah.
Let's
actually
do
that.
A
So,
let's,
let's
have
a
quick
demo,
and
so
this
is
kind
of
an
ad-hoc
demo.
I
didn't
super
super
prepare
this
before
the
call
so
and
let's
see
if
everything
is
working
properly,
but
there's
two
things:
what
I
wanted
to
quickly
demo
before
we
go
to
the
mics
and
Myka's
sections,
one
number
one
thing
into
the
visual
studio
extension.
So
how
does
it
actually
work?
What
does
it
actually
do
and
explain?
Is
it
useful
or
not?
The
second
thing
is
around
an
upcoming
exchange
or
upcoming
improvement,
which
is
around
office
UI
fabric
or
support.
A
So
we
will
have
an
office
or
a
fabric,
core
support
improvements
coming
up
for
quite
soon,
and
you
are
able
to
start
using
the
fabric
also
with
nonreactive
projects,
and
this
improvement
is
coming
out
correlative
as
soon
with
the
new
version
of
the
SharePoint
framework,
yeoman
templates
and
the
packages
as
well,
not
quite
sure,
somebody's
sharing.
Why
is
somebody
somebody
knows
my
password?
How
is
that
possible
speaking
of
fabric.
A
He's
the
East
uff
reaches
dead
and
run
turn
to
getting
startling,
always
says
you
to
react.
Reason
I'm,
asking
because
I
want
to
incorporate
this
to
the
MVC
adding
so
the
the
idea
of
officer
a
fabric
core
core
is
that
you
can
actually
use
that
within
the
not
within
not
in
a
non
react
areas
as
well,
but
so
it's
not
definitely
dead.
Definitely
not
that
good.
A
A
So
please
tell
me
and
I
window
whenever
the
screen
sharing
is
working
loading
and
Mikhail,
cadet
and
Ralph
correct
good.
So
just
quick
resources
on
the
Visual
Studio,
IDE
extension
and,
like
I,
said
I'm,
going
to
show
this
one
in
practice
here
as
well.
We're
super
interested
of
collecting
feedback
on
the
is
this
actually
needed.
We
are
people
truly
looking
into
doing
this
and
they
want
to
have
this
and
that's
absolutely
fine.
If
that
is
the
case,
we'll
keep
on
investing
or
will
increase
the
investments
on
this
area.
A
Let's
put
it
this
way,
so
in
github,
in
github.com,
SharePoint
SPF,
FX
TT
s
extension,
pretty
long
name
for
the
revelatory
but
SharePoint
development
framework,
Visual
Studio
extension.
We
have
the
source
code
of
this
one
if
you're
not
interested
on
what
does
it
the
source?
Actually
look
like
you
can
go
to
the
releases
tab
and
you
can
actually
install
the
extension
from
here
or,
alternatively,
you
can
actually
go
to
the
visual
studio
marketplace
and
also
get
this
free
extension
from
here
as
well.
A
This
is
so
I'm
doing
something
which
you
don't
have
to
do
if
you
install
the
vs
IX
and
which
says
I'm
actually
now
going
to
start
debugging
session
against
this
verse
to
do
because
I'm
running
my
extension
in
a
debugging
mode
in
a
visual
studio,
which
sounds
weird
that
I'm
debugging
visual
studio
with
visual
studio,
but
that's
a
different
discussion,
but
essentially
when
you
have
installed
the
template
or
deck
station.
If
you
go
to
the
new
project,
you
will
actually
have
this
additional
project
available.
A
So
underneath
the
sharp,
which
is
slightly
could
be
slightly
miss
well
difficult
to
find,
but
underneath
to
c-sharp
underneath
deficiency
open,
we
have
a
SharePoint
framework
selection
and
we
have
a
new
shape
on
framework
project
option
available,
which
is
mark
to
be
a
c-sharp,
which
is
something
which
would
probably
change
in
the
future.
That
is
slightly
confusing.
The
reason
why
the
c-sharp
was
used
here
is
that
just
that
the
classic
SharePoint
farm
solution
development
was
a
write
about
in
the
same
section
as
well.
So
you
could
easily
find
this
SPF
X
project
from
here.
A
So,
let's
give
this
one
a
name
so
in
my
web
part
that
8
is
fine
and
let's
select
the
template
and
can
actually
create
this
and
let's
see
what
it
actually
does.
So
it's
going
to
start
my
creation
of
the
project
and
hopefully
in
any
given.
Second,
we
defecate
so
there's
my
creation
Visser.
So
what
this
one
is
doing
is
that
it's
basically
asking
all
of
the
questions
what
the
yeoman
template
would
be
asking
as
well.
So
it's
gonna
ask
the
framework.
A
And
why
is
that?
Well
that's
how
long
do
the
yeoman
scaffolding
actually
takes?
So
what
this
one
is
doing
on
the
background,
you
can
see
it
in
the
Advanced
tab
as
well.
It
actually
executes
the
scuffled,
the
yeoman
commands,
but
it's
hiding
that
if
you
choose
to
do
a
height
that
so
essentially
this
is
just
a
wrapper
behind
of
the
yeoman
and
NPM
commands.
You
will
still
need
to
install
the
yeoman
templates.
A
You'll
still
need
to
make
sure
that
you
have
an
NPM
and
you
human
installed
on
your
machine,
but
using
this
one
you
actually
can
just
make
this
creation
of
the
project
and
adding
items
without
going
to
the
console
side.
In
this
case,
let's
actually
check
this
one,
so
we
can
actually
see
what's
happening.
So
that's
the
command
which
the
template
generator
will
actually
execute,
because
I
have
to
check
box
enabled
and
I
click
generate.
It's
gonna
actually
pop
up
a
console,
so
we
can
see
what's
actually
happening
on
behind
off
the
scenes.
A
So
there
we
go.
There's
my
project
is
created.
What
what
happened
was
that
it's
called
my
project
but
because
I
didn't
do
I
wanted
to
do
any
install
it
didn't
take
that
long
and
now,
if
I
close
this
one,
that's
why
I
exit?
We
can
actually
see
that
within
a
visual
studio.
It
will
now
do
the
following
step
and
create
my
solution
at
items
to
the
solution
and
all
of
that
and
there's
my
solution
structure.
A
So
now,
if
I,
let
actually
I
mean
that
one.
So
we
can
say
that
it's
exactly
the
same
structure
as
it
was
being
researched
earlier
code.
Clearly
because
in
this
that
structure,
which
is
the
SharePoint
favored
instruction-
and
we
can
also
find
the
web
part
in
here-
and
we
can
do
then
typescript
development
in
Visual
Studio
also
if
I
want
to
now
add
something
here:
I
can
go
ant
and
new
hide
them
and
in
the
new
item
selection
we
can
actually
see.
A
Let's
see,
if
is
named
extent,
that
one
and
that
one
we
can
actually
see
a
SharePoint
framework
item
here
as
a
selection
and
that's
then
that's
then,
and
that's
gonna
actually
start
the
process
of
creating
the
item.
So
let's
actually
start
that
and
there
we
go
now.
We
can
actually
again
select
the
component
type
and
if
it's
an
extension,
the
extension
type
now
I
can
see
all
online
somebody
actually
unmuted
himself.
So
I
can
hear
some
background
noise.
So
please
do
mute
yourself,
but
Paul.
A
A
So,
if
I
add
that
one
there,
no
there
we
go
and
generate,
we
can
actually
see
that
it's
now
adding
that
additional
web
part
it's
gonna,
take
a
while
it's
executing
that
it's
once
the
yeoman
generator
in
the
same
way
as
you
do
that
manually,
under
on
the
command
line
as
well
and
come
on
in
a
second,
it's
connected
that
item
in
the
installation.
It
doesn't
actually
matter
now.
You
get
the
point
and
what's
actually
happening
now.
A
What
we
want,
like
mention
feedback,
so
please,
if
this
is
useful,
let
us
know
so
we
know
that
we
can
keep
on
investing
on
things.
If
you
have
enhancement
ideas,
please
let
us
know
so
we
can
actually
get
things
moving.
There
is
some
small
challenges
which
we
are
already
addressing
and
try
to
address.
Like
f5
experience
on
the
on
the
visual
studio,
that's
actually
slightly
challenging.
Do
visual
studio
not
do
the
template
and
AB
model,
but
that's
a
different
discussion
where
we
don't
actually
need
to
go
good.
A
The
other
thing
what
I
wanted
to
quickly
show
before
we
go
to
the
I
think
Mike
will
start
is
the
upcoming
updates
on
on
the
office
of
Iraq
tech
support.
So
pretty
soon
we'll
have
an
update
at
templates
coming
up
and
that's
gonna
actually
do
quite
significant
chains
on
our
styling
model
and
the
reason
why
we
do
that
is
that
we
want
to
make
sure
that
you
are
able
to
use
obviously
our
fabric
or
styles
in
a
non-degree
act
with
parts
as
well.
A
So,
basically,
what's
gonna
happen,
and
like
said
this
is
previous
stuff,
you
don't
have
access
on
this
one
yet
so
so
don't
don't
even
try
to
update
your
stuff
right
now.
What
will
happen
is
that
will
actually
provide
an
updated
package
which
will
be
called
SP
office
unify
procore,
and
this
package
will
then
essentially
enable
you
to
use
office.
Your
fabric
styles
in
a
non
react
web
fonts
as
well
in
a
safe
way.
A
Round
s-curves
Kwadwo,
not
one
I'm
gonna,
actually
quickly
jump
to
a
one
of
the
test.
Tenants.
So
I
can
share
this
one
in
practice
and
there's
the
crude
and,
let
me
add,
workbench
underneath
the
group
side,
so
I
can
share
the
workbench
or
the
web
part
in
this
context
as
well.
So
let
me
go
to
that
and
select
hello
world
right
now.
That's
blue!
Nothing
too,
fancy,
but
because
it's
used
in
the
office
in
fabric
styling
it
natively
understands,
for
example,
the
theming
of
the
side.
A
So
if
I
go
to
the
site
level
and
flip
the
look
and
feel
of
the
site
to
be
something
super
cool,
that's
pretty
cool-looking
style
which
I
created
for
one
of
the
demos
which
we
recorded
one
back,
not
that
cool,
looking
style.
But
now,
if
I
go
to
the
workbench
and
if
I
refresh
the
Workmen's-
and
you
can
actually
see
that
my
web
part
is
a
DEP
thing
that
that's
styling
automatically
as
well.
So
you
don't!
A
Actually,
if
you
don't
want
to,
you,
can
follow
up
on
the
styling
directly
if
you
need
want
to
override
and
want
to
look
down
to
a
specific
colors
in
office,
UI
fabric,
that's
possible
as
well
so
you're
able
to
then
do
that
you're
able
to
then
do
that
within
the
code
as
well.
So
everything
will
be
actually
the
the
trick
here
is
that
in
our
styles
and
the
CSS
class
we
are
referencing
the
fabric
course
miles
and
we
were
able
to
dimension
and
reference
those
dynamically
here.
A
If
I
want
to
override
to
a
specific
style,
that's
possible
as
well,
but
there
will
be
more
documentation
more
additional
stuff
available
in
the
future
on
this
one
just
wanted
to
quickly
pinpoint,
what's
coming
quite
soon,
good
I'm
gonna
flip
back
on
the
slides,
where's,
the
slides,
that's
the
26th.
So
let
me
jump
back
on
the
slides.
This
is
one
slide
which
I
wanted
to
quickly
go
through
hello,.
A
Somebody
animated
themselves
clearly
kid
so
there
was
a
one
slide
which
I
wanted
to
quickly
quickly
do,
which
was
this
one
just
to
update
people
on
the
latest
on
the
SharePoint
development
side,
so,
on
the
roadmap
side,
nothing
too
much
changes
from
the
past
two
weeks.
Obviously
the
the
on-premises
support
game
live
as
part
of
the
SharePoint
2016
feedback
too.
So
that's
for
on-premises
we're
not
planning
to
do
a
trip
on
26
a
SharePoint
framework
on
SharePoint
2013
for
time
being.
A
If,
if
people
are
wondering
that
we
do
have
a
tenant
scope,
deployment
available,
the
yeoman
generator
together
with
SharePoint
framework
extension,
general
availability
happened
in
ignite
week.
To
turn
on
properties
is
in
dev
preview.
That's
documented
unavailable.
Also.
We
had
a
demo
on
that
one
two
weeks
ago
by
checks
showing
how
that
actually
works.
You
can
have
a
little
condo
on
the
recording
if
you're,
interesting
and
then
there's
tomalak
Austin
themes
which
are
now
in
preview
as
well.
No
coming
soon
office.
Do
my
fabric
core
support,
that's
coming
quite
soon,
so
that's
pretty
much
ready.
A
We
are
working
on
updates,
updating
of
the
documents,
updating
of
the
and
double
checking
and
testing
the
functionalities.
There
will
be
more
Microsoft
crafts
support,
so
you're
able
to
enable
additional
scopes
to
be
available
through
the
Microsoft
craft
client,
which
is
a
common
request.
Alm
api's
you're
able
to
deploy,
install
upgrade
sharepoint
framework
solutions
and
SharePoint
add-ins
automatically
using
code,
and
that
was
already
recorded
as
a
preview
from
last
week.
Actually,
so,
please
have
a
look
on
our
YouTube
channel
if
you're
interesting.
One
interesting
thing
is
the
assets
included
in
the
deployment
packages.
A
So
if
you
are
using
office,
365
CDN,
you
can
configure
your
packages
and
way
that
you
do
not
need
to
explicitly
copy
the
JavaScript
files
to
a
CDN.
All
of
that
will
be
happen
automatically
when
the
SBB
gate
a
file
is
connect,
getting
deployed.
That's
what
that
means:
site-specific
app
catalog
for
allowing
scope
deployment
so
point
being
on
the
fact
that
you're
able
to
have
a
dedicated
app
cattle,
app,
catalog
or
a,
for
example,
for
your
global
intranet
or
a
subset
of
sites.
A
Well,
let's
put
it
this
way:
it's
a
site,
collection,
scoped,
app
catalog,
which
can
be
enabled,
and
by
the
administrator
to
be
a
supporter
and
then
site
designs
with
the
next
time.
Stability
point
is
coming
relatively
soon
as
well.
Now
that's
a
quick
update
on
the
on
the
roadmap.
You'll
see
more
announcements
in
the
depth
of
us.
That
comes
last
blocks.
If
you
follow
up
on,
Twitter,
Facebook
will
keep
on
and
posting
those
updates
as
we
move
along
with
in
this
journey.
A
If
you're
wondering
what
happens
after
these
and
there's
a
lot
of
stuff
in
the
roadmap,
what
we
want
to
do,
we
want
to
bring
shape
on
framework,
for
example,
for
add-ins,
so
you're
still
able
to
you
write
a
shipment
framework,
you
eyes,
but
then
you
you're
able
to
host
them
in
an
iframe
from
a
security
perspective,
we're
looking
into
improving
the
ISV
story.
There's
a
lot
of
market
a
store
market
and
store
improvements
coming
up
in
the
in
the
pipeline
as
well.
A
A
A
B
Okay,
well
great
everyone
thanks
for
jumping
on
so
I'm,
like
a
Merlin
I
work
with
Mesa
and
I
work
with
the
shear,
pointing
my
work
on
the
marketing
side.
So
you
will
see
marketing
written
code
today,
so
I
apologize
in
advance,
but
we
also
have
code,
that's
written
by
a
number
of
other
kin
readers
as
well.
B
So
you
know
the
the
main
idea
behind
this
is
a
new
repository
on
the
patterns
and
practices,
site
called
community
solutions,
so
community
solutions,
the
idea
behind
it
is
to
have
you
know
a
bit
higher
level
sort
of
business
application,
samples
and
patterns
that
are
a
bit
more
ready
to
run.
So
you
can
actually
take
them
and
you
know
hopefully
use
them.
You
know
test
them,
make
sure
that
they
sort
of
you
know
suit
your
needs.
B
You're
gonna
want
to
adapt
them
all
that
kind
of
fun
stuff,
but
the
idea
is
that
these
are
solutions
that
you
can
use
as
a
foundation
for
deploying
to
your
SharePoint
sites
and
working
through
it.
So
whereas
we
have
you
know
an
awesome
repository,
what's
your
point
developer
web
parts
that
you
know
typically
sort
of
focus
on
one
particular
facet,
maybe
using
angular
in
a
particular
way,
these
samples
aren't
intended
to
necessarily
show
a
particular
developer
technique,
they're,
really
just
designed
to
show
kind
of
an
end-to-end
solution.
B
Now
these
five
apps
that
we
have
that
are
part
of
these
community
solutions.
They're,
you
know
definitely
still
in
preview,
we're
still
working
on
them.
I
think
part
of
the
great
thing
about
this
is
that
it
gives
us
an
opportunity
to
try
to
model
different
types
of
UX
patterns.
So,
of
course,
we
have
office
UI
fabric.
We
have
updated
guidelines
up
on
the
docks
at
Microsoft
comm
site
around.
You
know
how
you
should
sort
of
try
to
express
your
user
experience,
but
there's
still
a
lot
to
try
to
standardize
on
and
try
to
improve
upon.
B
With
respect
to
you
know
more
complicated
UX
patterns,
things
like
master/detail
relationships
and
the
like,
and
so
this
is
kind
of
a
good
foundation
for
us.
You
know
internally
to
try
to
talk
about
it
and
work
on
it,
but
you
know
with
your
feedback
as
well,
we
can
sort
of
try
to
work
towards
you
know
trying
to
establish
better
UX
patterns.
What
works,
what
doesn't
work
in
those
kinds
of
things?
So
it's
up
on
github
comm,
it's
under
the
SharePoint
repository.
You
know,
we
love
your.
You
know,
pull
requests
your
feedback,
your
issues.
B
You
know
your
additional
solutions.
We
already
have
a
solution
that
was
contributed
by
Shire,
which
all
very
briefly
demo,
later
on
and
we'll
go
from
there.
Okay.
So
the
first
solution
that
we
have
here
is
just
a
very
simple
one
called
contact
management.
So
you
know
this
isn't
intended
to
be
sort
of
a
full
CRM
system,
but
the
idea
behind
it
is
that
you
typically
want
to
track
organizations
and
people,
and
you
want
to
do
that
fairly
quickly.
B
Now,
of
course,
we
have
modern
SharePoint
lists
and
that
user
experiences
massive
improvement
upon
the
list
user
experience
from
before,
but
sometimes
there's
even
room
to
have
a
higher
quality,
more
targeted
type
of
user
experience.
In
this
case,
you
know,
as
you
might
imagine,
it's
a
little
bit
of
a
relational
database
from
a
SharePoint
list
perspective.
B
So
that
was
a
little
bit
of
an
inspiration,
so
you'll
see
that
throughout
these
samples
you
know
the
one
thing
that
I
wanted
to
show
with
this
particular
web
part
I'm
gonna
come
over
to
my
site
over
here.
Let
me
go
to
my
let's
say:
let's
say,
for
example:
I
needed
to
go
ahead
and
manage
a
set
of
vendors
for
my
contoso
travel
equipment,
adventure
company.
So
in
this
case,
what
we
have
here
is
a
very
simple.
You
know
database
of
a
list
of
vendors.
This
is
the
SharePoint
framework
web
part.
B
You
can
do
things
like,
of
course,
drill
in
on
a
particular
company,
so
we've
got
wingtip
over
here.
You
know,
there's
a
lot
of
fields.
You
know,
there's
there's
room
to
do
things
with
a
SharePoint
framework
web
part
to
make
the
form
more
customizable,
but
the
cool
thing
about
this
is
that
then
you
can
do
things
like
add
contacts
and
add
people
to
this
as
well.
So
if
I
want
to
add
John
Doe
yeah,
this
is
gonna
end
up
John
Doe.
B
This
will
get
added
to
a
separate
share
point
list,
but
it's
sort
of
all
pulled
together
in
this
SharePoint
framework
user
experience.
Now
the
other
cool
thing
about
this
sample-
and
this
is
not
really
library
of
five
yet
so
to
speak,
but
I
want
to
work
towards
library,
library
of
fiying
this,
if
that's
a
verb,
is
this
idea
that
it's
a
it's
also
extensible?
So,
for
example,
you
know:
how
do
you
want
to
track?
Organizations
is
always
going
to
differ.
B
You
know
over
time
and
from
company
to
company,
so
you
want
to
use
the
benefit
of
sharepoint.
You
want
to
use
the
fact
that
we've
got
this
SharePoint
list
infrastructure
to
let
people
go
ahead
and
add
a
new
field.
So
in
this
case,
maybe
what
I'm
gonna
do
is
I'm
going
to
you
know
this
is
the
list
of
organizations
that
stores
the
backing
list
of
organizations
behind
the
scenes.
Maybe
I
want
to
add
a
custom
field
called
you
know,
preferred
you
know
airline
or
something
like
that.
B
Maybe
I
want
to
track
their
preferred
airline
or
something
along
those
lines.
I
can
add
a
custom
feel
to
this.
I
can
even
misspell
it
and
if
I
come
back
to
my
solution,
the
beauty
of
this
is
that
it's
adaptable.
So
if
I
come
back
to
my
SharePoint
framework
web
part,
I
drill
into
a
wing
tip
and
I
hit
edit
now,
what
you'll
see
is
that
it's,
you
know,
got
a
preferred.
Airline
field
and
I
can
say
well,
not
Delta,
Alaska
Airlines,
or
something
like
that.
So
you
know
this.
B
This
solution
is
extensible
so
that
you
can
actually
add
custom
fields
on
to
it
and
they
end
up
showing
up
in
the
web
part
without
needing
to
recompile
the
code.
So
just
taking
a
look
at
the
code
behind
the
scenes
for
this
solution
in
particular,
you
know
you
know
this
is
kind
of
a
standard,
SharePoint
framework
web
part.
We
have
our
web
part
here,
but
it's
implemented
in
react.
B
We
have
a
number
of
different
components
for
showing
you
know
lists
of
organizations
and
display
items
as
well,
but
the
thing
that
makes
that
sort
of
extensibility
possible
is
that
I
have
a
number
of
different
components
here,
for
you
know
implementing
a
very
basic
you
know.
Date,
field
editor
experience
a
date
field
display
experience,
you
know
things
like
a
lookup
field,
editor
experience
a
multi-line
text
field.
B
It's
got
a
number
of
different
controls
and
components
here
that
are
designed
to
make
it
possible,
for
you
know,
anticipating
new
fields
in
your
sharepoint
list
and
then
letting
you
it.
You
know
edit
them
there's
an
item.
Where
is
that
there
is
a
item
field,
iterator
control
which
we
can
see
over
here.
You
know
what
this
does
is
a
very
simple
way
to
you
know,
take
an
arbitrary
list
of
fields
that
are
on
a
list
and
then
just
render
them
in
a
sort
of
a
two
column
format.
B
You
know
a
little
bit
extensible,
but
the
idea
is
that
you
know,
as
new
fields
get
rendered
over
time
and
added
to
that
list.
It
will
automatically
render
those-
and
you
know,
if
you're,
at
all,
familiar
with
sharepoint
forms
from
2007.
Goodness
you
just
know,
as
I
am
you
know,
some
of
these
control
names
are
kind
of
a
little
familiar,
the
concept
of
a
field
iterator
and
those
kinds
of
things
you
know,
maybe
I'm,
you
know,
die
hard
for
some
of
that
old
stuff,
but
anywho
the
idea
behind
the
contact
management.
B
You
know
it
shows
these
concepts
of
multiple
lists
working
together.
You
know
there's
things
like
a
tagging
functionality,
so
I
can
go
ahead
and
you
know
tag
this
says.
Okay,
this
is
a
you
know,
a
company
that
sells
me
water
type
goods,
that's
coming
from
another
SharePoint
list
as
well.
So
the
idea
behind
the
scenes
is
that
it's
pulling
on
these
lists
together
and
it's
also
allowing
for
extensibility,
and
so
this
is
just
one
of
the
set
of
solutions
that
we're
looking
to
you
know
basically
work
on
and
polish.
B
B
B
I'm
gonna
go
through
the
other
ones,
a
little
bit
more
quickly,
but
you
know
it
does
show
that
pattern
of
using
fields
to
allow
for
easy,
customization
part
of
what
I
want
to
do
with
these
solutions,
as
well,
just
from
the
sort
of
the
marketing
point
of
view
to
give
you
sort
of
the
the
idea
there
is
I.
You
know,
I
think
SharePoint
really
makes
a
great
business
application
platform
there's
so
many
services
that
come
with
SharePoint.
You
know
things
like
extensible
feel
it's
things
like
integration
with
flow.
B
You
know
the
fact
that
your
list
has
a
recycle
bin
for
making
sure
that
you
can
preserve.
You
know,
data
that
are
really
great
utilities
for
developers.
That
I
think
it's
a
really
compelling
option
a
lot
of
times
to
build
these
kinds
of
solutions
on
top
of
SharePoint.
So
you
know
just
trying
to
use
these
as
a
way
to
kind
of
demonstrate
those
kinds
of
concepts
to
different
types
of
developers.
Okay,
so
next
solution
is
just
a
very
simple
inventory
and
check
out
list.
B
So
I'm
gonna
come
back
to
my
page
over
here,
and
so
here.
I
just
have
a
very
simple
list
of
items
that
are
in
our
venture
equipment
inventory.
So
in
this
case
we
have
an
internal
frame
backpack.
We
have
five
of
those
that
are
in
a
storage
closet
over
by
my
office.
People
can
come
in
to
this
website
and
they
can
say:
okay,
it's
checked
out.
B
You
know
to
me
and
I'm
gonna
plan
to
bring
that
back
after
Halloween
and
you
know
well,
maybe
I
won't
fill
that
in
yet,
but
you
know
and
then
I
can
go
ahead
and
say:
I
wanted
to
go
check
out
two
of
those
backpacks.
Oh
wait.
I
can't
check
it
out,
twelve,
because
there's
only
five
and
then
from
here
what
it
will
do
is
it'll
just
create
a
separate
check
out
for
me
and
then
later
on
down
the
line
when
I
come
back.
B
I
can
go
check
this
in
you
can
see
that
it'll
sort
of
track,
the
set
of
things
that
I've
checked
out
and
the
like
as
well.
So
just
a
very
simple,
you
know
fairly
common
scenario.
If
you've,
you
know
ever
had
like
a
device
lab
or
something
like
that,
where
you
know
you've
got
different
types
of
you
know,
Android
and
iPhone
type
devices
that
you
want
to.
Let
people
lend
and
borrow
just
a
very
simple
scalable
solution
for
that
and
again
a
lot
of
what
this
does.
Is
it
actually
pulls
together?
B
You
know
just
different
lists
together
into
one
user
experience
as
well.
So
that's
just
a
very
simple
example:
you
know
lending
library
and
simple
checkouts.
You
know
there's
different
ways
to
track
it
as
well.
You
know
one
of
the
benefits
again
of
building
this
on
SharePoint
is
that
you
can
do
things
like,
for
example,
integrate
a
flow
with
this
list
so
that
you
know
somebody
checks
something
out.
B
You
can
build
a
custom
flow
process
that
notifies
people
that
somebody's
check
something
out
or
do
different
types
of
things
so
again,
another
great
proof
of
concept
of
using
SharePoint
as
a
lending
library.
Now
some
of
you
might
be
saying
well,
but
I
could
actually
pull
this
entire
experience
in
power
apps.
That
is
a
great
example
as
well.
You
could
build
a
lending
library
and
power
apps,
there's
templates
for
that,
but
the
benefit
of
using
SharePoint
framework
here
is,
of
course,
that
you
get
a
highly
performant,
very
tailored
experience
on
your
website.
B
Anyway,
you
know
just
trying
to
demonstrate
that
concept
as
well.
Okay,
another
one
is
just
the
you
know
the
old
you
know
classic
hit
called
change
requests,
which
is,
of
course,
every
organization
has
a
need
to
track
change
request.
Maybe
you
want
to
put
a
very
simple.
You
know
login
issue
button
on
your
website.
That
then
goes
into
a
queue,
and
you
know
again.
B
One
of
the
key
concepts
here
is
that
you
want
to
have
a
way
for
end-users
to
come
to
your
site
and
log,
a
change
request,
but
then
what
you
want
to
do,
maybe
behind
the
scenes,
is
assign
it
to
a
person.
Have
your
own
internal
triage
have
your
own
way
to
track
that
information
that
gets
kept
separately
from
the
from
what
the
end
user
sees
like.
B
Maybe
you
know
if
somebody
reports,
a
plumbing
issue
you
want
to,
you
know,
make
sure
that
you
handle
it,
but
if
it
doesn't
repro,
you
know
maybe
that
conversation
between
you
and
your
team,
you
want
to
keep
a
little
bit
private,
so
it
uses
two
separate
SharePoint
lists
to
implement
this
concept.
You
know
so
that
you
can
independently
secure
the
the
set
of
change
request
from
the
actual
discussion
around
it.
So
in
this
case,
I've
got
a
web
part
on
my
home
page.
B
Did
you
experience
an
issue
with
some
equipments
log,
an
issue
you
can
click
create
a
new
change
repair
request.
We
have
maybe
a
little
bit
of
UX
cleanup
here.
So
I
apologize
right
on
that
you
can
say.
Okay,
you
know
water
is
leaking
near
building
two
like
this,
and
so
this
will
create
a
change
request
behind
the
scenes
and
then,
when
you
actually
come
over
here,
there's
a
separate
wet
part.
So
this
actually
has
two
wet
parts.
B
One
is
a
web
part
that
you
put
you
know
in
front
of
your
users
and
then
the
second
is
sort
of
a
triage
application.
A
triage
web
part
that
you
probably
put
on
a
separate
page,
and
then
you
know
you
can
see
this.
This
request
that
we
just
created,
you
know
again
as
I
was
mentioning.
We
need
to
work
a
little
bit
through
the
user
experience
and
the
user
experience
patterns
here,
because
this
type
of
scrolling
experience
is
not
super
optimal,
but
you
know
you
can
see
all
the
different.
B
B
Complete,
but
you
can
then
give
it
a
priority
in
a
sub
status,
and
you
know
you
can
say
well,
you
know
we're
just
gonna
leave
that
leak
in
place,
because
why
not
and
then
hit
save
and
it
goes
back
to
the
user.
So
the
idea
is
the
idea.
Is
you
have
this
sort
of
separate
triage
process?
You
know
the
other
nice
thing
about
this
is
that
it's
designed
to
be
customizable
so
that
you
can,
you
know,
make
this
about.
B
You
know,
you
know
you
can
change
the
sort
of
the
nouns
and
verbs
that
are
used
in
this
web
part,
so
you
can
actually
tailor
it
to.
You
know
whether
you're
talking
about
website
issues
or
whether
you're
talking
about
plumbing
issues.
You
can
use
the
right
language
with
your
customers
so
that
you
can
see
it.
Let's
take
a
look
at
the
code,
I'm
kind
of
going
through
this
a
little
quickly,
but
what
you'll
see
here
is
so
you
see
in
this.
We
have
the
different
types
of
solutions
that
are
available
here.
B
The
change
request
one
is
over
here:
we've
got
those
two
webparts
that
I
talked
about.
So
there's
a
change
request
management
web
part,
which
is
the
overall.
You
know
triage
tool
for
working
with
the
webparts,
and
then
we
have
the
my
change
request
web
part,
which
is
that
sort
of
website
component
that
lets
you
go
ahead
and
then
sort
of
you
know
solicit
new
change
requests
from
a
particular
person
and
those
kinds
of
things,
and
you
know
for
all
of
these
webparts.
What
you'll
see
is.
B
Excuse
me
for
all
those
webparts.
What
you
would
see
is,
you
know
basically
sort
of
broken
down
into
a
set
of
reactive
components
using
office,
UI
fabric,
those
kinds
of
things,
and
then
you
know
we
have.
You
know
you
know
both
a
mock
data
provider
as
well
as
sort
of
ones
that
connect
to
underlying
SharePoint
lists
to
go
implement
it.
B
The
other
thing
that
these
solutions
do-
and
maybe
this
is
sort
of
leading
into
what
Michaels
Michaela's
going
to
talk
about
in
just
a
second,
is
that
they
do
also
have
a
provisioning
process,
that's
associated
with
them,
so
the
first
time
I
come
to
a
web
site.
If
I
want
you
know.
So
this
is
just
a
brand
new
site
that
I
created
like
an
hour
ago
if
I
go
back
to
a
home
page
and
I.
Add
the
web
part
for
the
for
the
first
time.
B
What
you'll
see
the
first
time
you
do?
It
is.
Let
me
go
add
that
change
request
management
web
part,
the
first
that
time
you
use
it.
It's
gonna
say,
create
a
change
request
and
change.
Request.
Discussion
list
now:
I
have
an
item
to
go,
integrate
that
new
patterns
and
practices
controls
for
doing
placeholders,
so
I
need
to
go.
Do
that,
but
the
idea
is
behind
the
scenes.
B
What
this
is
gonna
do
is
it's
gonna,
go,
create
the
write
lists
and
set
them
up
so
that
you
know
the
web
part
now
becomes
configured
and
it
does
the
right
things
with
respect
to
to
checking
to
make
sure
that
I've
got
permissions
and
then
I
can,
you
know
actually
go
create
lists
in
my
site.
So
you
know,
of
course
you
can
use
feature
based
provisioning
to
do
the
same
thing
and
in
fact
we
do
have
feature
provisioning
behind
the
scenes
as
well
to
kind
of
backstop
this.
B
But
the
idea
behind
this
is
that
you
know
this
makes
it,
for
example,
tenant
deployable
and
those
kinds
of
things,
so
that
you
know
you
can
make
this
webpart
available
across
your
tendenci
and
that
doesn't
come
with
feature
deployment.
But
there
is
some
JavaScript
code
here
to
actually
go
ahead
and
create
things
now.
You
know
the
thing.
B
So
so
let
me
just
move
along
and
then
the
final
ones
are
just
a
really
simple
one.
This
is
just
a
very
simple
time
away
calendar
so
that
you
can
let
peep
go
ahead,
and
you
know
log
there
they're
out
of
office
and
those
kinds
of
things,
so
this
webparts
up
right
here,
so
you
can
see
that
you
know
we
have
a
simple
list
of
across
our
team
who's
away
this
week,
who's
away
next
week,
if
I
so
choose,
I
can
go
ahead
and
add
my
own
time
away.
B
So
maybe
I'm
going
to
you
know,
take
this
Friday
off
and
you
know
all
the
way
through
next
Monday
and
then
hit
save.
So
what
this
will
do
is
just
let
people
go
ahead
and
log
it
now.
The
cool
thing
about
this
is
that
it
also
integrates
with
things
like
SharePoint
list
approvals.
So,
for
example,
if
you
wanted
to
you
know,
have
your
manager
go
approve
it
first
before
you
before
it
actually
showed
up.
As
you
know,
here's
someone
who's
away.
You
could
do
that
and
it
will
make
sure
that
it.
B
If
the
item
is
not
approved,
it
won't
show
up
in
this
calendar
so
again
trying
to
integrate
what
the
capabilities
of
SharePoint
you
know
behind
the
scenes.
As
you
can
imagine,
this
is
just
a
SharePoint
list
that
it's
using
to
go,
pull
in
more
data
and
then
go
render
them.
You
know
obviously
there's
more
work.
We
can
do
here
to
go,
improve
the
overall
visuals
to
make
it
more
compelling.
B
The
final
thing
I
just
wanted
to
show
was
that
we
already
have
a
solution
from
the
shire
folks,
so
the
shire
folks,
including
Dave
Feldman
and
Scott
Hillier
and
Julie
Turner
and
Darcy
Hesse
and
Bob
German
and
Mike
Thalia,
probably
I'm,
forgetting
a
couple
other
folks.
They
actually
built
a
set
of
hub
web
parts
and
so
I
expect
that
they
may
demo
them
someday.
So
I'm
not
gonna
steal
their
thunder
and
demo.
It
end
to
end,
but
just
to
give
you
a
little
bit
of
a
taste.
B
These
are
a
set
of
web
parts
that
you
are
designed
to
be
used
on
things
like
communication
site.
So,
for
example,
a
lot
of
times
you
want
to
have
big
giant
call-to-action
buttons
on
your
web
site.
So
this
is,
you
know
a
a
you
know.
Link
button
can
wet
part,
so
you
can
do
things
like
add
a
you
know,
a
button
control
here.
So
I
can
say
you
know
PMP
jeaious
samples
likes
arrow
and
of
course
you
know
control
how
it
looks
like
you
know:
I
can
use
a
font,
awesome
link
it.
B
You
know
button
for
that,
so
you
can
do
a
lot
of
different
things
that,
just
you
know,
add
those
little
small
widgets
that
need
to
sort
of
finish
off
your
site.
Again
it
was.
It
was
developed
by
kind
of
the
some
of
the
some
of
the
superstars.
If
you
will
of
you
know
it
had
some
really
awesome
developers.
B
So
take
a
look
at
that
as
well
and
there's
there's
other
samples
here
too,
that
I
won't
demo
and
hopefully
they'll
demo
on
a
future
call
and
they'll
go
through
that,
including
one
that
actually
uses
JavaScript
and
handlebars
templates.
Now,
obviously,
you'll
want
to
be
careful
about
deploying
that
and
making
sure
that
it's
secured
properly,
but
for
this
audience
you
know
JavaScript
and
handlebars
templates
anyway.
So
that's
that's
a
cool
one
and
again,
hopefully
we'll
see
a
little
bit
more
of
a
detailed
drill
down
on
that
one
as
well.
B
So
that's
just
a
very
quick
overview
of
patterns
and
practices.
Commune
solutions,
we're
still
you
know,
we're
still
working
on
it-
we're
soul,
polishing
off
a
lot
of
these
samples
to
make
them
even
more
robust
to
make
sure
that
we
sort
of
nailed
the
UX
patterns,
we're
working
with
the
SharePoint,
and
you
know,
office
design
teams
to
sort
of
further
iterate
on
them
as
well.
B
A
lot
of
these
webparts
I
should
mention
work
developed
by
canvas
and
Todd
Baginski
as
well.
So
you
know,
thanks
to
his
team,
for
doing
a
lot
of
great
work
on
those
as
well
make
sure
I
call
that
out.
But
if
you
want
I'd
love
to
see
you
over
on
our
github
repository,
hopefully
the
code
I
take
a
look
and
you
know
sort
of
see
if
how
it
works
for
you
and
I
appreciate
any
pull
requests
or
new
samples
or
feedback
or
those
kinds
of
things.
B
A
Excellent,
so
we're
going
to
paste
in
the
link
under
window
and
I
think
we'll
be
moving
to
Michael.
So
thank
you
Mike
for
that
one.
So
Wes
I
was
talking
again
too
long.
So
that's
why
we're
running
low
on
time,
but
Michael
I
think
we
can
tackle
this
in
ten
minutes
right,
because
the
idea
is
good
and
and
what
Michael
is
going
to
present
in
a
second
I
think
the
most
important
thing
about
this.
Well,
this
isn't
run
breaking
this
isn't
rocket
science.
C
Yep,
thank
you
so
this
sample
it's
an
application
customizer.
Basically,
when
you
go
into
a
site
the
first
time
it
will
do
whatever
cold
logic
you
need
so
I
actually
created
it
in
the
in
solution
building
for
a
customer
to
set
the
group
logo,
because
you
can't
really
set
the
group
logo
using
app
tokens
right
now.
You
have
to
do
it
in
user
tokens.
So
then
I
figured
well
I'll.
Do
it
the
first
time
someone
enters
the
group
site.
C
So
if
we
just
take
a
look
at
the
code,
which
is
very
simple,
I
mean
I
can
actually
fit
all
the
code
in
one
screen.
So
on
the
on
in
it,
it
just
checks
first,
that
you're
actually
a
an
admin
on
the
site,
and
the
reason
for
that
is,
since
the
application
customizer
is
15
as
a
custom
action.
In
order
to
remove
it,
you
have
to
be
an
admin
to
remove
it,
so
it
checks
if
you're
inside
admin,
and
it
actually
uses
the
old
underscore
SP
context
to
find
that
information.
C
C
C
So
if
I
get
all
my
custom,
action
and
I
see,
I
have
three
and
let's
go
back
to
the
site:
exists,
alert,
sickle
high
vessel
and
I'm
going
to
open
the
debug
tools.
I
click!
Ok!
So
if
we
watch
down
here
we
will
accession
removed,
reload,
the
page,
no
alert
and
if
I
list
all
my
extensions
see
is
extension.
It's
called
so
it's
very,
very
simple
sample.
C
A
Like
that,
the
reason
like
said
the
relatively
simple
thing,
but
the
whole
point
being
on
the
fact
that
this
is
probably
gonna,
be
one
way
of
ensuring
that
you
will
execute
some
code
related
on
whenever
somebody
is
accessing
the
site.
First
time
that
that
code,
which
is
getting
executed,
that
could
be
showing
a
panel,
it
could
ask
metadata
from
the
end
user
around
the
site
and
store
that
metadata.
Let's
say
using
a
chef
function
and
elevated
mode
to
a
centralized
location
or
whatever,
but
I
think
that
the
portion
is
quite
compelling.
C
A
A
Correct
and
most
likely,
if
we
would
do
that,
a
user
case
with
a
new
discussion
as
well,
we
would
actually
store
that
in,
for
example,
in
a
user
profile,
so
you
would
add
a
let's
say:
use
a
profile
property
which
would
use
for
storing.
Have
we
tackled
this
guy
already
in
or
not
so
one
way
of
doing
that
or
store
the
list
of
people
who've
been
processed
already
in
the
list.
This
way
this
is
essentially,
this
is
the
site
level,
first-time
executable
and
getting
something
done
and
then
hiding
them
yeah,
because.
C
C
I
guess
all
of
this
I
guess
I'll
just
note
since
since
you're
talking
about
metadata.
So
this
is
this
web
part
right
here.
Yeah,
that's
actually
metadata
stored
stored
in
the
graph,
so
there's
a
web
part
on
the
front
page
where
you
can
done
since
I'm
an
owner
I
can
actually
change,
for
example,
who's.
Why
it's
my
responsible?
Yes,.
A
C
A
Yes
and
then
well,
there's
multiple
other
ways
of
them
doing
elevation
of
priorities,
and
maybe
we
should
actually
do
a
demo
on
that
one
sooner
or
later,
as
well,
but
I
think
that's
it
we're
running
out
of
time
as
well.
Any
random
questions
around
topics
which
we've
gone
through
today,
I
think
my
cancer
on
the
hop
web
part
example.
A
Was
at
the
coal
ash
your
function
for
shipment
framework
and
it's
iframe
patterns
to
recommend
it?
That
would
be
one
way
of
doing
that.
Yes,
if
you
would
need
to
do
authorization
or
authenticated,
call
against
all
dedicated
Asha
function,
and
that
would
be
the
way
to
do
using
the
hidden
iframe
model.
A
A
Not
yeah
I'm,
not
quite
sure
if
there
is
non-alignment
on
there,
we're
using.
Obviously
our
fabric
react
an
officer
a
fabric
or
within
those
components
as
well.
So
that's
really
the
way
we're
planning
to
do
in
the
future
as
well,
making
sure
that
they're
consistent
and
they
are
using
the
same
UI
as
as
SharePoint
in
general.
A
A
One
based
on
officer
yep,
that
is
absolutely
Todd
here,
using
the
officer
why
fabric
making
sure
that
they're
consistent.
Yes,
now
that
doesn't
that
means
the
office
UI
and
sorry,
the
the
ex
the
reusable
controls
will
be
using
officer
eye
fabric.
Yes,
it
will
be
good
for
all
the
material
for
samples
would
be
doing
that
in
a
multiple
different
technologies.
There's
certain
challenges
still
on
angular
side,
we'll
have
some
news
announcements
on
that,
one
sooner
or
later,
which
is
pretty
cool,
but
that's
not
because
of
sharepoint.
B
A
quick
shout
out
and
plug
or
I
think
we're.
A
lot
of
us
are
gonna,
be
at
the
European
SharePoint
conference
and
yes,
we'll
be
talking
through
a
lot
of
developer
scenarios
there
and
probably
talking
about
some
new
things
as
well.
So
you
know
it's
a
quick
plug
that,
even
if
you're
not
going
you
know,
maybe
stay
tuned
to
the
European
SharePoint
conference,
which
is
13
through
the
16th.
Yes,.
A
We
always
schedule
our
large
announcements
on
these
conferences,
but
couch
I
think
we
ran
out
of
time.
So
thank
you,
everybody
for
joining.
Thank
you,
Mike
and
thank
you
Michael
for
your
demos.
Hopefully
there's
new
ideas
from
the
demos
as
well,
and
additional
assets
and
resources
which
you
can
use
within
your
cut
your
work
day
to
day
work
as
well.
So
thank
you.
A
Everybody
and
we'll
have
the
following
special
interest
group
meeting
around
SharePoint
framework
on
November
9th
and
then
the
general
shape
and
development
special
interest
group
within
the
next
week,
and
we
won't
probably
talk
about
Japan
framework
and
we'll
see
what
we're
going
to
talk
about
there,
but
hoping
to
see
also
in
ESPC
and
we'll
get
there
as
well
and
have
fun
visual
studio
extensions
for
the
win.
Yes,
thanks,
Paul
for
reminding
on
that
one.
A
Please
have
a
feedback
coming
up
on
that
one
as
well,
but
a
recording
will
be
available
within
24
hours
in
the
YouTube
channel,
we'll
post
some
social
media
tweets
when
that
happens.
But
thank
you,
everybody.
Thank
you
for
joining.
Thank
you
for
your
feedback.
Thank
you
for
your
input
and
let's
keep
that
communication
channel
open.
Thank
you.
Bye,
bye,.