Update communication/marketing-team/role-handbooks/storytellers.md

Co-authored-by: Matt Broberg <matt@opensource.com>

1 files changed, 26 insertions, 20 deletions

diff --git a/communication/marketing-team/role-handbooks/storytellers.md b/communication/marketing-team/role-handbooks/storytellers.md
index b7cee0c2..c52c22eb 100644
--- a/communication/marketing-team/role-handbooks/storytellers.md
+++ b/communication/marketing-team/role-handbooks/storytellers.md
@@ -16,26 +16,32 @@ TODO add more here
 There are multiple ways to successfully a Kubernetes blog. Here are some of the common paths to help you do so:
 
 
-* Pitch idea to the meeting or Open a [Contributor Comms Requests issue](https://github.com/kubernetes/community/issues
-)
-* Create initial draft
-  * Can be a
-    * gdoc
-    * markdown
-    * hackmd
-* Get assigned a pair
-  * Via issue or meeting
-* Work with the Upstream marketing team to polish, and format your blog
-  * No current cannonical format document
-  * [Technical consideration](https://github.com/kubernetes/community/issues
-) provided by the k8s blog team
-* Go to the kubernetes/website repo and send a PR
-  * Upstream marketing will offer to have your pair help with the PR and shepherd it throught the k8s blog process
-
-or if you already have everything you think you need you can simply
-
-* Go to the kubernetes/website repo and send a PR
-* There's a kubernetes blog team that will walk you through [the process](https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/)
+**To start:** 
+
+* Open a [Contributor Comms Requests issue](https://github.com/kubernetes/community/issues) to share your blog idea, or attend an [Upstream Marketing team](https://github.com/kubernetes/community/tree/master/communication/marketing-team) meeting to discuss it ahead of time
+
+**To write:**
+
+* Create an initial draft -- it is always easier to work from some written down ideas than to do so from scratch
+  * A draft can be written in:
+    * Google Docs or
+    * Markdown (and shared via [Gist](https://gist.github.com/) or [HackMD](https://hackmd.io/))
+* Connect with a storyteller -- if you reach out to Upstream Marketing, you will be paired with someone to help you through writing, editing, and getting your article published
+  * Discussion happens via GitHub issue or through working group meetings
+* This includes working with Upstream Marketing team to polish, and format your blog post
+  * There is not a single canonical format for documents, but we do have [guidelines for effective articles](https://github.com/kubernetes/community/blob/master/communication/marketing-team/blog-guidelines.md#how-to-write-an-effective-blog)
+  * There are further technical considerations by the [Blog team](https://github.com/kubernetes/community/blob/4026287dc3a2d16762353b62ca2fe4b80682960a/sig-docs/blog-subproject/README.md#submit-a-post)
+
+When it's ready, submit the blog post: 
+
+* Go to the `kubernetes/website` repository
+* Open a PR with your added blog post
+  * If you need help with this process, Upstream Marketing will look to pair you with someone for PR and shepherd it through the review cycle
+
+Or if you already have everything you think you need you can:
+
+* Go to the `kubernetes/website` repo and send a PR
+* There's a Kubernetes blog team that will walk you through [the process](https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/)
 
 ### Tips