[Content Dev Proposal] {{Title}} : Azure Functions

[c-d-r]

Content Development Proposal Issue

📅 Due: July 31, 2020

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/webinar labels

Step-By-Step Technical Blog Guide

💃 Before starting

Blog tracker

• Submit blog choice on airtable

📌 Step 1: Proposal

🔥 DO NOT MERGE TO MASTER YET
📅July 6, 2020

• Complete proposal template
• Compete Resources Request Form
• Check the blog tracker to find your Technical QA expert (or ask your PM if you can't find it) and Writing QA expert
• Open Tutorial QA Issue and assign it to 1. yourself 2. your Technical QA expert
• Open Tutorial QA Issue
• Submit Proposal

How to: Submit Proposal

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

- 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 a pull request to merge into the #{{insert-blog-title}} branch on bitprj/devrel

- Assign your PM to the pull request

• How to fork a repo video

📌 Step 2: Testing Code

🔥 DO NOT MERGE TO MASTER YET
📅**{{Due_Date}}**

• Tested run code to check for completion

📌 Step 3: Submitting Code Deliverables

🔥 DO NOT MERGE TO MASTER YET
📅July 27, 2020

• 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 Technical QA expert and PM to the pull request

📌 Step 4.1: Blog Deliverables

🔥 DO NOT MERGE TO MASTER YET

• 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 Technical QA expert, Writing QA expert, and PM to the pull request

📌 Step 4.2: Workshop Deliverables

🔥 DO NOT MERGE TO MASTER YET

• 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 Technical QA expert, Writing QA expert, and PM to the pull request

📌 Step 5: QA

📅**{{Due_Date}}**

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

📅**{{Due_Date}}**

:checkmark: PR TO THE MASTER BRANCH

• Finalize blog based on QA feedback