You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: communication/marketing-team/role-handbooks/storytellers.md
+45Lines changed: 45 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,51 @@ Storytelling is welcome in any medium that can be supported by the Upstream Mark
14
14
15
15
Storytellers are constantly building new ways to share, and these resources are gathered in the [storytelling resources folder].
16
16
17
+
### Upstream Marketing Process
18
+
19
+
#### Idea Paths
20
+
21
+
There are multiple ways to successfully contribute a Kubernetes blog post. Here are some of the common paths to help you do so:
22
+
23
+
**To start:**
24
+
25
+
* 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
26
+
27
+
**To write:**
28
+
29
+
* Create an initial draft -- it is always easier to work from some written down ideas than to do so from scratch
30
+
* A draft can be written in:
31
+
* Google Docs or
32
+
* Markdown (and shared via [Gist](https://gist.github.com/) or [HackMD](https://hackmd.io/))
33
+
* 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
34
+
* Discussion happens via GitHub issue or through working group meetings
35
+
* This includes working with Upstream Marketing team to polish, and format your blog post
36
+
* 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)
37
+
* 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)
38
+
39
+
When it's ready, submit the blog post:
40
+
41
+
* Go to the `kubernetes/website` repository
42
+
* Open a PR with your added blog post
43
+
* 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
44
+
45
+
Or if you already have everything you think you need you can:
46
+
47
+
* Go to the `kubernetes/website` repo and send a PR
48
+
* There's a Kubernetes blog team that will walk you through [the process](https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/)
49
+
50
+
### Tips
51
+
52
+
Converting a Google Doc to markdown? Here is a helpful way to do so:
53
+
54
+
* go to: https://discuss.kubernetes.io/
55
+
* Open a new topic
56
+
* Paste the Google Doc into new topic window
57
+
* Discourse will automatically convert it to markdown 🎉
58
+
* Now you can copy the markdown text, with all its original formatting, and paste it into your blog post file (this will often be a text file you are editing on your computer from a text editor like VS Code)
59
+
* Be sure to add the syntax required at the top of the blog post (see links above)
60
+
* Now you are ready to submit it as a PR
61
+
17
62
## Minimum Skills and Requirements
18
63
19
64
- Have a passion for telling stories, technical writing, journalism, and painting pictures with words
0 commit comments