summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJason Morgan <jmorgan@f9vs.com>2021-04-30 11:34:28 -0400
committerGitHub <noreply@github.com>2021-04-30 11:34:28 -0400
commitb3115472a2fd7156d7e482d9c799f52eb43d3b13 (patch)
treea2c96ac533e4b902b8e6480c4346d77a4a6761f1
parentf8ed71344399097c3091bec2cb891ce8c17651c7 (diff)
Updated workflow
Replaced TODO.
-rw-r--r--communication/marketing-team/role-handbooks/storytellers.md43
1 files changed, 37 insertions, 6 deletions
diff --git a/communication/marketing-team/role-handbooks/storytellers.md b/communication/marketing-team/role-handbooks/storytellers.md
index f4f59c2e..b71b3171 100644
--- a/communication/marketing-team/role-handbooks/storytellers.md
+++ b/communication/marketing-team/role-handbooks/storytellers.md
@@ -9,12 +9,43 @@ TODO add more here
## Workflow ⚡️
-TODO
-document a short workflow here
-1 should be for those who are comfortable going back and forth on a PR
-another option should include agreeing on a *final* version in a separate
-collaborative doc tool and the sig-docs-liaison or Editor will start the PR
-process
+### Upstream Marketing Process
+
+#### Idea Paths
+
+There is no one way to get into the kubernetes blog. Below are some options:
+
+The Kubernetes Upstream Marketing team under ContribEx can help you tell a kubernetes story. With Blog posts you can:
+
+* 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/)
+
+### Tips
+
+Converting gdoc to markdown?
+
+* go to: https://discuss.kubernetes.io/
+* Open a new topic
+* Paste gdoc into window
+* Profit
## Minimum Skills and Experience