Add logo to readme

README.md

@@ -2,8 +2,12 @@
 [![Build Status](https://travis-ci.org/fission/fission-workflows.svg?branch=master)](https://travis-ci.org/fission/fission-workflows)
 [![Go Report Card](https://goreportcard.com/badge/github.com/fission/fission-workflows)](https://goreportcard.com/report/github.com/fission/fission-workflows)
 [![Fission Slack](http://slack.fission.io/badge.svg)](http://slack.fission.io)
+[![fission.io](https://img.shields.io/website-up-down-green-red/http/shields.io.svg?label=fission.io)](http://fission.io)
+[![@fissionio](https://img.shields.io/twitter/follow/fissionio.svg?style=social&label=Follow)](https://twitter.com/fissionio)
 
-[fission.io](http://fission.io)  [@fissionio](http://twitter.com/fissionio)
+[![Fission Workflows](Docs/assets/fission-workflows-logo.png)](http://fission.io/workflows)
+
+----
 
 Fission Workflows is a workflow-based serverless function composition framework built on top of the [Fission](https://github.com/fission/fission) Function-as-a-Service (FaaS) platform.
 
@@ -14,6 +18,8 @@ Fission Workflows is a workflow-based serverless function composition framework
 - **Extensible**: All main aspects of the engine are extensible. For example, you can even define your own control flow constructs.
 - **Lightweight**: With just the need for a single data store (NATS Streaming) and a FaaS platform (Fission), the engine consumes minimal resources.
 
+----
+
 ### Philosophy
 
 The Fission Functions-as-a-Service framework provides simplicity and
@@ -50,11 +56,8 @@ most other workflow engines are part of the internal API.
 
 **Workflows** can generally be represented in as a Directed Acyclic Graph (DAG).
 Consider the following example, a common pattern, the diamond-shaped workflow:
-```
-(A) --> (B) ---> (C) ---
-          \              \     
-            --> (D) ---->  (E) ---> (F)
-```
+
+![Workflow Example](Docs/assets/workflow-example.png)
 
 In this graph there is a single _starting task_ A, a _scatter task_ B
 triggering parallel execution of two _branches_ with tasks C and D,
@@ -63,7 +66,7 @@ parallel tasks.
 
 Finally the graph concludes once _final task_ F has been completed.
 
-Although Fission Workflow has additional functionality such as
+Although Fission Workflows has additional functionality such as
 conditional branches and advanced control flow options, it
 fundamentally executes a dependency graph.
 
@@ -150,7 +153,7 @@ issues, checkout the [roadmap](./Docs/roadmap.md) or browse through
 the open issues on Github.
 
 Finally, we're looking for early developer feedback -- if you do use
-Fission or Fission Workflow, we'd love to hear how it's working for
+Fission or Fission Workflows, we'd love to hear how it's working for
 you, what parts in particular you'd like to see improved, and so on.
 
 Talk to us on [slack](http://slack.fission.io) or