Skip to content

[Jason OKRs] #32

@shreythecray

Description

@shreythecray

📅 OKR Due: May 25th

The DRI for this issue is the Content Developer. They will be responsible for keeping this issue up to date at all times.

FOR IMCs: Add project manager and content developer as assignees

Add this issue into the corresponding IMC Project

FORMAT: Add blog/video labels

Step-By-Step Technical Blog Guide

💃 Before starting

📌 Step 1: Proposal

📅Sat May 16

How to: Submit Proposal - Fork the bitprj/devrel repo
- Create a file in the following folder: bitprj/devrel/{{imc_topic}}/{{imc_name}}/{{blog_title}}/proposal.md

- Commit + Push proposal.md

- Create branch called #{{insert-blog-title}}

- Create a pull request to merge into the #{{insert-blog-title}} branch on bitprj/devrel

- Assign your PM to the pull request

📌 Step 2: Testing Code

  • Tested run code to check for completion

📌 Step 3: Submitting Code Deliverables

📅Wed May 20

  • Submit Code Deliverables
How to: Submit Code Deliverables - Fork the bitprj/devrel repo
- Upload Finished Code on CodeSandbox

- Check that all code is commented well

- Link CodeSandbox in comments of this issue

- Commit + Push starter code into your pertinent folder under /starter and solution code under /solution

- Create a pull request to merge into the #{{insert-blog-title}} branch on bitprj/devrel

- Assign your PM to the pull request

📌 Step 4: Written Deliverables

  • Submit Written Deliverables
How to: Submit Written Deliverables - Fork the bitprj/devrel repo
- Commit + Push written content (step-by-step blog tutorial of code) under blog.md within the pertinent folder

- Create a pull request to merge into the #{{insert-blog-title}} branch on bitprj/devrel

- Assign your PM to the pull request

📌 Step 5: QA

📅Sun May 24

  • Presented blog draft and code on Loom Video
  • Send Loom and Collect feedback from QA and PM

📅Mon May 25

  • Finalize blog based on QA feedback
Merging to Master
- Open a Pull Request to Merge #{{insert-blog-title}} to #master

- Assign QA Specialist to Pull Request

- Assign Writing Specialist to Pull Request

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions