Merge pull request #630 from msfussell/master

Adding links to videos from the community calls.

FAQ.md

@@ -14,11 +14,13 @@ Dapr can be used alongside any service mesh such as Istio and Linkerd. A service
 
 That is where Dapr comes in. Dapr is a language agnostic programming model built on http and gRPC that provides distributed system building blocks via open APIs for asynchronous pub-sub, stateful services, service discovery and invocation, actors and distributed tracing. Dapr introduces new functionality to an app’s runtime. Both service meshes and Dapr run as side-car services to your application, one giving network features and the other distributed application capabilities.
 
+Watch this [video](https://www.youtube.com/watch?v=xxU68ewRmz8&feature=youtu.be&t=140) on how Dapr and service meshes work together.
+
 ### Understanding how Dapr interoperates with the service mesh interface (SMI)
 
 SMI is an abstraction layer that provides a common API surface across different service mesh technology.  Dapr can leverage any service mesh technology including SMI.
 
-### Differences between Dapr and Istio
+### Differences between Dapr, Istio and Linkerd
 
 Read [How does Dapr work with service meshes?](https://github.com/dapr/dapr/wiki/FAQ#how-does-dapr-work-with-service-meshes) Istio is an open source service mesh implementation that focuses on Layer7 routing, traffic flow management and mTLS authentication between services. Istio uses a sidecar to intercept traffic going into and out of a container and enforces a set of network policies on them.
 

howto/components-scopes/README.md

@@ -75,3 +75,4 @@ scopes:
 - app1
 - app2
 ```
+Watch this [video](https://www.youtube.com/watch?v=8W-iBDNvCUM&feature=youtu.be&t=1765) for an example on how to component scopes with secret components and the secrets API.

howto/consume-topic/README.md

@@ -6,6 +6,8 @@ Using Pub/Sub, you can enable scenarios where event consumers are decoupled from
 Dapr provides an extensible Pub/Sub system with At-Least-Once guarantees, allowing developers to publish and subscribe to topics.
 Dapr provides different implementation of the underlying system, and allows operators to bring in their preferred infrastructure, for example Redis Streams, Kafka, etc.
 
+Watch this [video](https://www.youtube.com/watch?v=NLWukkHEwGA&feature=youtu.be&t=1052) on how to consume messages from topics.
+
 ## Setup the Pub Sub component
 
 The first step is to setup the Pub/Sub component.

howto/get-secrets/README.md

@@ -18,6 +18,8 @@ The second step is to configure the secret store with Dapr.
 
 Follow the instructions [here](../setup-secret-store) to set up the secret store of your choice.
 
+Watch this [video](https://www.youtube.com/watch?v=OtbYCBt9C34&feature=youtu.be&t=1818) for an example on how to use the secrets API. Or watch this [video](https://www.youtube.com/watch?v=8W-iBDNvCUM&feature=youtu.be&t=1765) for an example on how to component scopes with secret components and the secrets API.
+
 ## Calling the secrets API
 
 Now that the secret store is set up, you can call Dapr to get the secrets for a given key for a specific secret store.

howto/pubsub-scopes/README.md

@@ -9,6 +9,8 @@ In addition to this general component scope, the following can be limited for pu
 
 This is called pub/sub topic scoping.
 
+Watch this [video](https://www.youtube.com/watch?v=7VdWBBGcbHQ&feature=youtu.be&t=513) on how to use pub/sub topic scoping.
+
 To use this topic scoping, three metadata properties can be set for a pub/sub component:
 - ```spec.metadata.publishingScopes```: the list of applications to topic scopes to allow publishing, separated by semicolons. If an app is not specified in ```publishingScopes```, its allowed to publish to all topics.
 - ```spec.metadata.subscriptionScopes```: the list of applications to topic scopes to allow subscription, separated by semicolons. If an app is not specified in ```subscriptionScopes```, its allowed to subscribe to all topics.

howto/send-events-with-output-bindings/README.md

@@ -3,6 +3,9 @@
 Using bindings, its possible to invoke external resources without tying in to special SDK or libraries.
 For a complete sample showing output bindings, visit this [link](https://github.com/dapr/samples/tree/master/5.bindings).
 
+Watch this [video](https://www.youtube.com/watch?v=ysklxm81MTs&feature=youtu.be&t=1960) on how to use bi-directional output bindings.
+
+
 ## 1. Create a binding
 
 An output binding represents a resource that Dapr will use invoke and send messages to.

howto/setup-monitoring-tools/setup-prometheus-grafana.md

@@ -2,6 +2,8 @@
 
 This document shows how to install Prometheus and Grafana to view metrics.
 
+Watch this [video](https://www.youtube.com/watch?v=8W-iBDNvCUM&feature=youtu.be&t=2580) for a demonstration of the Grafana metrics dashboard.
+
 ## Prerequisites
 
 - Kubernetes (> 1.14)