Skip to content

Commit c4ae027

Browse files
authored
Merge pull request #5752 from JasonMorgan/patch-1
Updated workflow
2 parents 923adb2 + 800f837 commit c4ae027

File tree

1 file changed

+45
-6
lines changed

1 file changed

+45
-6
lines changed

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

+45-6
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,51 @@ TODO add more here
99

1010
## Workflow ⚡️
1111

12-
TODO
13-
document a short workflow here
14-
1 should be for those who are comfortable going back and forth on a PR
15-
another option should include agreeing on a *final* version in a separate
16-
collaborative doc tool and the sig-docs-liaison or Editor will start the PR
17-
process
12+
### Upstream Marketing Process
13+
14+
#### Idea Paths
15+
16+
There are multiple ways to successfully contribute a Kubernetes blog post. Here are some of the common paths to help you do so:
17+
18+
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/)
45+
46+
### Tips
47+
48+
Converting gdoc to markdown?
49+
50+
* go to: https://discuss.kubernetes.io/
51+
* Open a new topic
52+
* Paste gdoc into new topic window
53+
* Discourse will automatically convert it to markdown 🎉
54+
* 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)
55+
* Be sure to add the syntax required at the top of the blog post (see links above)
56+
* Now you are ready to submit it as a PR
1857

1958
## Minimum Skills and Experience
2059

0 commit comments

Comments
 (0)