Skip to content

Commit 02c4359

Browse files
Update ep-hop-article-template.md
1 parent aaa5069 commit 02c4359

1 file changed

Lines changed: 8 additions & 11 deletions

File tree

docs/epresources/ep-hop-article-template.md

Lines changed: 8 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -16,15 +16,12 @@ Suggested max article length: 500 words
1616

1717
Include a few images of your final HOP, or code snippets, to break up the text. More is better!
1818

19-
## Timeline
20-
21-
- **Friday of Week 1** - You’ll create a rough skeleton blog article using tips in [Rough structure and writing prompts](#rough-structure-and-writing-prompts). Take this time to fill in some blanks as you’ve now selected your demo idea.
22-
- **Monday of Week 2** - Begin answering prompting questions in [Rough structure and writing prompts](#rough-structure-and-writing-prompts) and start incorporating them into your blog. It can help to draft a few bullet point ideas to start.
23-
- **Tuesday and Wednesday of Week 2** - Turn your focus to fleshing out bullet points and on building a more robust version of your article. Aim to have a draft ready for Thursday morning.
24-
- **Thursday of Week 2** - Your draft is ready and you’ll be attending a session called “*Commit Onboarding: Working out loud*” where you’ll meet with Commit’s copywriting team. This is an excellent opportunity to get feedback and ask questions! Following this session, you’ll make revisions to your blog and will have a final version ready for tomorrow EOD.
25-
- **Friday of Week 2** - You’ll have a final version of your blog post ready by EOD today and will submit it to our copywriting team for review.
26-
- **Week 3** - You'll expect final revisions from the copywriting team on your article. You’re now ready to showcase all your hard work by making a LinkedIn post about your blog! This article is an excellent accomplishment to include in your record of work and is a great talking point in interviews.
27-
- **Add your blog to your Record of Work (RoW)** - You should be proud of your HOP demo (we are!) and suggest you sharing this blog published blog post on your online profiles (LinkedIn, Github etc)!
19+
## Suggested Timeline
20+
21+
- **Week 1** - You’ll create a rough skeleton blog article using tips in [Rough structure and writing prompts](#rough-structure-and-writing-prompts). Take this time to fill in some blanks as you’ve now selected your demo idea. Once you start working on your HOP, begin answering prompting questions in [Rough structure and writing prompts](#rough-structure-and-writing-prompts) and start incorporating them into your blog. It can help to draft a few bullet point ideas to start.
22+
- **Week 2** - Turn your focus to fleshing out bullet points and on building a more robust version of your article. Aim to have a draft ready by the end of the week.
23+
- **Week 3** - At the beginning of the week, share the article with the Engineer Success team. You'll receive final revisions from the team on your article by the end of the week. Once edits are finished, you’re now ready to showcase all your hard work by making a LinkedIn post about your blog! This article is an excellent accomplishment to include in your record of work and is a great talking point in interviews.
24+
- **Add your blog to your Record of Work (RoW)** - You should be proud of your HOP demo (we are!) and suggest you sharing the published blog post on your online profiles (LinkedIn, Github etc)!
2825

2926
## Example
3027

@@ -66,8 +63,8 @@ You don’t need to address all of these questions. They’re just thought-start
6663
6764
2. **What’s your title?** Make it short, snappy and interesting. Example: *Polishing the platform: My hackathon onboarding project*
6865

69-
3. **Write a compelling Linkedin post** to encourage people to read your post. Not just "I wrote a blog post for Commit,” but a personal anecdote about the experience or a few lines about what you learned. You can even pull from the article if you like. (Our Content team can help)
66+
3. **Write a compelling Linkedin post** to encourage people to read your post. Not just "I wrote a blog post for Commit,” but a personal anecdote about the experience or a few lines about what you learned. You can even pull from the article if you like. (The Engineer Success team can help)
7067

7168
4. **What photo should you use for your blog header?** We’ll use your photo from your Humi onboarding checklist unless you provide another one. Keep in mind that it should be in landscape format, not portrait. Make it representative of yourself and your interests, not just a headshot
7269

73-
5. **Write a tweet to share your article** (Our Content team can help).
70+
5. **Write a tweet to share your article** (The Engineer Success team can help).

0 commit comments

Comments
 (0)