Skip to content

Commit 0d5f12a

Browse files
Update communication/marketing-team/role-handbooks/storytellers.md
Co-authored-by: Matt Broberg <[email protected]>
1 parent cd99f4b commit 0d5f12a

File tree

1 file changed

+26
-20
lines changed

1 file changed

+26
-20
lines changed

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

+26-20
Original file line numberDiff line numberDiff line change
@@ -16,26 +16,32 @@ TODO add more here
1616
There are multiple ways to successfully a Kubernetes blog. Here are some of the common paths to help you do so:
1717

1818

19-
* Pitch idea to the meeting or Open a [Contributor Comms Requests issue](https://github.com/kubernetes/community/issues
20-
)
21-
* Create initial draft
22-
* Can be a
23-
* gdoc
24-
* markdown
25-
* hackmd
26-
* Get assigned a pair
27-
* Via issue or meeting
28-
* Work with the Upstream marketing team to polish, and format your blog
29-
* No current cannonical format document
30-
* [Technical consideration](https://github.com/kubernetes/community/issues
31-
) provided by the k8s blog team
32-
* Go to the kubernetes/website repo and send a PR
33-
* Upstream marketing will offer to have your pair help with the PR and shepherd it throught the k8s blog process
34-
35-
or if you already have everything you think you need you can simply
36-
37-
* Go to the kubernetes/website repo and send a PR
38-
* There's a kubernetes blog team that will walk you through [the process](https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/)
19+
**To start:**
20+
21+
* 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
22+
23+
**To write:**
24+
25+
* Create an initial draft -- it is always easier to work from some written down ideas than to do so from scratch
26+
* A draft can be written in:
27+
* Google Docs or
28+
* Markdown (and shared via [Gist](https://gist.github.com/) or [HackMD](https://hackmd.io/))
29+
* 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
30+
* Discussion happens via GitHub issue or through working group meetings
31+
* This includes working with Upstream Marketing team to polish, and format your blog post
32+
* 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)
33+
* 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)
34+
35+
When it's ready, submit the blog post:
36+
37+
* Go to the `kubernetes/website` repository
38+
* Open a PR with your added blog post
39+
* 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
40+
41+
Or if you already have everything you think you need you can:
42+
43+
* Go to the `kubernetes/website` repo and send a PR
44+
* There's a Kubernetes blog team that will walk you through [the process](https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/)
3945

4046
### Tips
4147

0 commit comments

Comments
 (0)