GithubHelp home page GithubHelp logo

devrel's Introduction

Guide to Integrated Marketing Campaigns (IMCs)

Table of Contents

[TOC]

What is an IMC?

From workshops and tutorials presented by students to massive livestreamed webinars hosted by professors and industry professionals, Bit Project's mission is to provide our student community with the resources they need to successfully implement any project they envision.

Integrated Marketing Campaigns (IMCs) channel Bit Project's multiple teams, resources, and communication platforms to empower our student community to develop valuable technical education content.

Designers, developers, editors, and engineerings all come together to build collaborative and interactive learning experiences

Upcoming IMCs

Fighting COVID19 w/ APIs

Teaching w/ Data Science

8 Week Structure

Our organization works on educational content development by developing 8-week IMCs from ideation to post-production. The 8 week structure provides developers a way to find like-minded peers and create large scale education content together. Each developer creates blog tutorials about their own coding projects and the team works together under a Project Manager to build and promote a webinar to demonstrate the projects.

Below is a guide to the 8 week structure.

Week 0: Proposals

🐣 ==President== IMC Proposal

📌 Open IMC Proposal Issue

Proposals
  • Goal: PM your own IMC
  • All PMs and directors are expected to identify IMC topics and discuss to their supervisors
  • Not all ideas will be used
    • Being more involved in IMC topic generation will likely mean you can PM something you're really interested in
  • Coming up with your own IMC Proposals
    • Check for existing blogs
    • Gage demand and interests
    • What is something you want to work on?
    • What do you need to make this happen?
    • What if many people want to do the same IMC?
      • Most IMCs will be popular and can be repeated
      • Instead of having large IMC teams, it's best to schedule another IMC Proposal for that topic for the future and ask devs to wait until then

🍍 ==Project Managers== IMC Team Building

🍍 ==Everyone== Research

Schedule
  • [Monday] Announce IMC
    • Make announcements in all relevant channels
  • [Wednesday] Hold AMA Social
    • Allow devs to ask you questions and use this opporutnity to sell your idea to them
  • [Friday] Reach IMC team size goal
    • Prepare for devs to leave the group if they don't like the topic
    • Case: 0 devs if enough content exists
    • Case: 3-5 devs typically
    • Case: 5+ devs rare cases of popular IMCs (better to break them down)

Week 1: Planning Phase

🍍 ==Project Managers== Create IMC Plan

📌 Open Content Development Proposal (CDP) Issues 📌 Open IMC Plan Issue 📌 Open Weekly 1:1 Issue

🍍 ==Project Managers== Collect Resource Requests

Check airtable

🍍 ==Developer Relations Team== Create Tech Content Dev Plan :pineapple: ==Developer Relations Team== Begin Development

🍍 ==Marketing Growth Team== Create IMC Growth Plan

🍍 ==Marketing Content Team== Receive Content Requests :pineapple: ==Marketing Content Team== Schedule Content Production

Schedule
  • Monday IMC Development Meeting
    • Complete outlining IMC Plan Issue
    • Set up all 1:1s
  • Friday Complete all 1:1s

Week 2: Development Phase

🍍 ==Project Managers== Create Webinar Slidedeck :pineapple: ==Project Managers== Secure Speakers

🍍 ==Developer Relations Team== Build Code :pineapple: ==Developer Relations Team== + ==Marketing Growth Team== Begin Testing

Schedule

Week 3: Quality Assurance (QA) Phase

🍍 ==Developer Relations Team== + ==Marketing Growth Team== Develop Code Tutorial Blog

🍍 ==QA== Approve Content for Publication

Schedule

Week 4: Publishing Phase

🍍 ==Project Managers== Publish Slidedeck

🍍 ==Social Media Team== Publish Content

🍍 ==Marketing Growth Team== Execute Growth Plan

Schedule

Week 5: Practice Phase

🍍 ==Project Managers== Practice Runs w/ Guest Hosts

Schedule

Week 6: Production Phase

🍍 Host Webinar

Schedule

Week 7: Retrospective Phase

🍍 Led by ==People Team== 🍍 Involves ==Everyone==

Schedule

Submitting Content for IMCs

devrel's People

Contributors

atuljayaram avatar cdhlee avatar chriztopherton avatar cpaluch avatar danzelo1 avatar emily-gui avatar etang01 avatar gisselleibarra10 avatar hackmd-deploy avatar jefftheaggie avatar kylebegovich avatar lazyplatypus avatar minhtumn avatar nians520 avatar shreythecray avatar

Stargazers

avatar avatar avatar avatar

Watchers

avatar avatar

Forkers

alexdoytch kylebegovich gisselleibarra10 manasiabh jhong00 chriztopherton joeyhuaa taimurkashif emily-gui jefftheaggie mukulljangid zanderxu1 saviloj sameeksha22 raymondw9 minhtumn kathyliu20 bitterb3rry narae970210 dadao-xiaoguaishou sashliu danzelo1 deepkakadia tonywu1998 hollycao bowen1zhu hfstarman eden-bouskila mcharming98 allenaavila emilyyu22 etang01 aaronw4ng adriangomez25 isabella232

devrel's Issues

[Karolina's OKRs]

📅 OKR Due: May 24th

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

📅Sat May 23

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

📅Sun May 24

  • 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

Content Development Plan - Unsupervised Learning: K-means Clustering to Uncover Groups

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{K-means Clustering}
  • Topic: {{Applying an Unsupervised Clustering Technique to Uploaded Images}}
  • Sub-topic: {{How to extract color and their proportions from images?}}
  • Structure: {{Insert structure here}}
  • Description (5-7+ sentences): {{Insert description here}}
  • Resources needed: {{Google Colab}}

Step 2

  • Describe target audience (Artists, Painters, Marketing or anyone who might need to create an art physical art piece, such as a wall mural or a billboard. ):

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences):

    • The challenge they are presented is to scale a given image, something someone might show you on paper or online. The goal is to reproduce that for a campaign event using only your artistic ability and a rough guessestimate of how much paint of each color you might need in some measureable quantity such as ounces.

    • (i.e. An image of Spiderman may have mainly red,blue and some black for his costume.)

    • An everyday scenario is as follows: You are a manager of several marketing campaigns and your group is tasked with creating billboards that advertise some effort. Your team includes a handful of artists/painters who are each tasked with creating their own piece of work, based on a set of images/pictures CompanyX has provided. As manager, you're responsible for ordering just the right amount of paint each image would require. Leftover paint is not ideal. You can count on these experienced artists to understand exactly how much paint is needed to achieve a certain shade of a particular color. How can this process of color assortment and quantity measure be automated?

    • Middle (2-3+ sentences):

    • Its going to consist of a step-by-step tutorial code and documentation on the tools, packages and code chunks necessary to go from uploading an image and reaching the end goal of obtaining exactly colors exist in that image.

    • End (2-3+ sentences):

    • You were able to upload an image, and extract however many colors exist in that image. Next time you are tasked with turning a small pixeled image into a massive billboard, and you needed to know which colors are needed and in what quantity, you would be able too. Heck, you can do it for 10,20 or even 100 images all automitically!

  • Submit blog choice on airtable.

  • Create Content Development Issue

[Jason OKRs]

📅 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

[Jeffrey OKRs]

📅 OKR Due: May 24th

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

📅Sat May 23

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

📅Sun May 24

  • 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

Proposal for Intro to Programming [Integrated Campaign]

<--- The DRI for this issue is the President. They will be responsible for keeping this issue up to date at all times --->
<--- Add this issue into the corresponding IMC Milestone --->

🙌 Proposal for {{Insert IMC Name}} Integrated Campaign

President

  • Open IMC Issue
  • Get Project Manager (announce in channel)
  • Get Company sponsor

Project Manager

  • Create #imc-[title] channel on Slack
  • Make announcement on #general channel
  • Build team on Slack (3-4 marketing + 3-4 devs)

Proposal for Intro to R [Integrated Campaign]

<--- The DRI for this issue is the President. They will be responsible for keeping this issue up to date at all times --->
<--- Add this issue into the corresponding IMC Milestone --->

🙌 Proposal for {{Insert IMC Name}} Integrated Campaign

President

  • Open IMC Issue
  • Get Project Manager (announce in channel)
  • Get Company sponsor

Project Manager

  • Create #imc-[title] channel on Slack
  • Make announcement on #general channel
  • Build team on Slack (3-4 marketing + 3-4 devs)

[Content Development Plan] Responsive Web

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{Insert title here}}
  • Topic: {{Insert topic here}}
  • Sub-topic: {{Insert sub-topic here}}
  • Structure: {{Insert structure here}}
  • Description (5-7+ sentences): {{Insert description here}}
  • Resources needed: {{Insert resources here}}

Step 2

  • Describe target audience (3-5+ sentences):

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences):
    • Middle (2-3+ sentences):
    • End (2-3+ sentences):

  • Submit blog choice on airtable.

  • Create Content Development Issue

[Code Deliverable] AI Capable of Dialogue

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Insert Tech Here}}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

[Atul's OKRs]

📅 OKR Due: May 24th

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

📅Sat May 23

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

📅Sun May 24

  • 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

[Code Deliverable] Unsupervised Learning: K-means Clustering to Uncover Groups

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Google Colab}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

Content Development Plan - Technical Blogs

Step-By-Step Technical Blog Guide

Step 1

  • Title: "Yes,and...": Conversation between Humans and Machines
  • Topic: AI
  • Sub-topic: NLP
  • Structure: IMC
  • Description (5-7+ sentences): Right now, there are AIs that we can indeed talk to. However “talk” is a bit of a stretch. At best, we can ask questions that are pre-defined in the software and get back a pre coded response. I’m referring to devices like Siri or Alexa. As they are now these AIs are little more than a limited, speech version of Google. However, it is both possible and highly desirable to create AI capable of dialogue. Machines that can interpret your words in context, understand that a conversation is taking place, and respond accordingly.
  • Resources needed: Articles, research papers, talks given on subject.

Step 2

  • Describe target audience (3-5+ sentences): This would ideally be targeted toward a general audience. The discussion about AI is very basic and focuses on what it's currently capable of rather than how it works. As such, no technical background is needed. However, college students can also read the blog to spark their interest in computational social science, and research in AI.

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences): At first, I'll discuss what AI are currently capable of. Then, I'll go over the challenges of getting AI to truly have a conversation with humans.
    • Middle (2-3+ sentences): This part will be devoted to the progress and achievements that have been made in this field. I'll also go over what is not solved yet and what problems cannot be solved.
    • End (2-3+ sentences): At this point, I'll discuss the future of AI research on this matter and what new progress we can look forward to. I'll also discuss why this is important and what other innovations are possible if we manage to realize this idea.

  • Submit blog choice on airtable.

  • Create Content Development Issue

Content Development Plan - Memory Game in Vanilla JavaScript

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{Introduction to Vanilla JavaScript along with HTML/CSS: Building A Memory Game}}
  • Topic: {{Front-End Developments}}
  • Sub-topic: {{HTML/CSS, JavaScript}}
  • Structure: {{A step-by-step tutorial to build a memory game page}}
  • Description (5-7+ sentences): {{This blog is a tutorial to guide the audience to write a set of HTML, CSS, and JS files to create a memory game. In this blog, it covers some basic techniques in HTML/CSS, such as containers. It also introduces JS, by adding flipping, matching functions to make the game work. The code for HTML/CSS would be presented first, as a interface of the game. Then the code in JS would add functions to make the game work.}}
  • Resources needed: {{https://hq.bitproject.org/how-to-write-a-technical-blog/}}

Step 2

  • Describe target audience (3-5+ sentences):
    The target audience would be teens and young adults who do not have much experience with HTML/CSS or JavaScript. However, they should be older enough to understand the logic behind the game and each function. This blog could be a fun introduction to HTML/CSS and JavaScript since it is creating a game, so people that are interested in gaming is also welcomed to read this blog.

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences): Brief introduction about HTML/CSS, and JavaScript and their applications. Then, introduce that the blog is going to guide you through creating a memory game by using some basic and typical techniques in HTML/CSS and JS. The beginning part of the blog would emphasize on its simple, quick, and entertaining aspects.
    • Middle (2-3+ sentences): Since this blog would be a tutorial, the middle part would include a lot of codes. The codes would be presented with the explanation of logic behind them, and also the basic tool/function they need to use. More attention is needed to clearly show that which codes are in which file. Graphs and GIFs of the resulting game interface should also be shown in the process to help the audience follow through it.
    • End (2-3+ sentences): End the tutorial by congratulating that they created a game! Then, encourage them to explore more uses of HTML/CSS, and JavaScript to create more fun games or applications. Maybe give an example of another game they should try to make (which is similar to the memory game, like a little assignment).

  • Submit blog choice on airtable.

  • Create Content Development Issue

Content Development Plan - Implementation of Shoe Bot

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: Implementation of Shoe Bot
  • Topic: Back-End Development
  • Sub-topic: Machine Learning
  • Structure: Step-by-Step
  • Description (5-7+ sentences): For this blog, I am really hoping to educate others on how powerful AI's are. AI's are not quite fully integrated into our society, but we definitely will have more AI related technologies as time progresses. Not many people, or even students, in this generation know about how AI's work, so I wanted to create a blog and educate others about how it works by showing how to implement the code, how others can integrate the same algorithm into other AIs, and how the program works. Furthermore, I want to create a post about a shoe bot. When we do online shopping, it is usually done manually and not automatically. Sometimes when we want to get the new Supreme drop, the item is usually sold out. However, with a fully developed shoe bot, the user will be able to make purchases very quickly with very little information / action required.
  • Resources needed: IDE (text-editor is fine)

Step 2

  • Describe target audience (3-5+ sentences):

    • My target audience is beginner coders who are still trying to learn how to code and start on small projects of their own to build their portfolio. I am not by any means professional at Python, as I have only taken one or two courses on it, so this blog is for people who are at the same level as me. All in all, I am hoping to attract an audience who have the ambition to use the provided knowledge to create similar projects of their own.

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences): I will talk about what AI's are and why they are so important in modern day society. Transitioning into my topic, I will establish the baseline of how AI shoe bots work and how they are so powerful. Also, how it is relevant to the shoe industry is a key element to discuss.
    • Middle (2-3+ sentences): This is where I explain how to actually code the AI shoe bot. Every line of the implementation of the AI shoe bot will be explained line by line. As I stated before, this blog is for beginner coders so I will be establishing what libraries are, what specific libraries need to be implemented for this AI shoe bot to work, and why we need those libraries. Furthermore, functions that are usually not used in a normal CS class will be explained to make sure that the audience understands every single piece of information in the blog.
    • End (2-3+ sentences): In the conclusion, or ending statement, I will diverge away from the code deliverable as best as I can because the purpose is to learn why the blog is important not how it is done. Although this blog is primarily about how to code the AI shoe bot, I still want to provide an ending statement that will connect back to why the topic is relevant.

  • Submit blog choice on airtable.

  • Create Content Development Issue

[Code Deliverable] Memory Game in Vanilla JavaScript

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used:
  1. how to build a timer and count down
  2. how to add event when the card/button is clicked (breifly, since it is discussed in the original blog). function to check clicked status.
  • Time Taken on Blog: 1-1.5h
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

[Zander's OKRs]

📅 OKR Due: May 24th

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

📅Sat May 23

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

📅Sun May 24

  • 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

Proposal for Static Site Generation [Integrated Campaign]

<--- The DRI for this issue is the President. They will be responsible for keeping this issue up to date at all times --->
<--- Add this issue into the corresponding IMC Milestone --->

🙌 Proposal for Static Site Generation [Integrated Campaign]

President

  • Open IMC Issue
  • Get Project Manager (announce in channel)
  • Get Company sponsor

Project Manager

  • Create #imc-[title] channel on Slack
  • Make announcement on #general channel
  • Build team on Slack (1-2 marketing + 3-4 devs)

[Content Development Plan] DIY ADHD Medication Reminder

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{Insert title here}}
  • Topic: {{Insert topic here}}
  • Sub-topic: {{Insert sub-topic here}}
  • Structure: {{Insert structure here}}
  • Description (5-7+ sentences): {{Insert description here}}
  • Resources needed: {{Insert resources here}}

Step 2

  • Describe target audience (3-5+ sentences):

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences):
    • Middle (2-3+ sentences):
    • End (2-3+ sentences):

  • Submit blog choice on airtable.

  • Create Content Development Issue

Proposal for Azure Functions (w/ Microsoft) [Integrated Campaign]

<--- The DRI for this issue is the President. They will be responsible for keeping this issue up to date at all times --->
<--- Add this issue into the corresponding IMC Milestone --->

🙌 Proposal for {{Insert IMC Name}} Integrated Campaign

President

  • Open IMC Issue
  • Get Project Manager (announce in channel)
  • Get Company sponsor

Project Manager

  • Create #imc-[title] channel on Slack
  • Make announcement on #general channel
  • Build team on Slack (3-4 marketing + 3-4 devs)

Content Development Plan - Simple side-scrolling platformer game

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{Insert title here}}
  • Topic: {{Insert topic here}}
  • Sub-topic: {{Insert sub-topic here}}
  • Structure: {{Insert structure here}}
  • Description (5-7+ sentences): {{Insert description here}}
  • Resources needed: {{Insert resources here}}

Step 2

  • Describe target audience (3-5+ sentences):

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences):
    • Middle (2-3+ sentences):
    • End (2-3+ sentences):

  • Submit blog choice on airtable.

  • Create Content Development Issue

[Code Deliverable] Business Model of Open Source Companies

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Insert Tech Here}}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

Proposal for Intro to Programming [Integrated Campaign]

<--- The DRI for this issue is the President. They will be responsible for keeping this issue up to date at all times --->
<--- Add this issue into the corresponding IMC Milestone --->

🙌 Proposal for {{Insert IMC Name}} Integrated Campaign

President

  • Open IMC Issue
  • Get Project Manager (announce in channel)
  • Get Company sponsor

Project Manager

  • Create #imc-[title] channel on Slack
  • Make announcement on #general channel
  • Build team on Slack (3-4 marketing + 3-4 devs)

[Content Development Plan] Business Model of Open Source Companies

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{Insert title here}}
  • Topic: {{Insert topic here}}
  • Sub-topic: {{Insert sub-topic here}}
  • Structure: {{Insert structure here}}
  • Description (5-7+ sentences): {{Insert description here}}
  • Resources needed: {{Insert resources here}}

Step 2

  • Describe target audience (3-5+ sentences):

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences):
    • Middle (2-3+ sentences):
    • End (2-3+ sentences):

  • Submit blog choice on airtable.

  • Create Content Development Issue

Proposal for MakeCode (w/ Microsoft) [Integrated Campaign]

<--- The DRI for this issue is the President. They will be responsible for keeping this issue up to date at all times --->
<--- Add this issue into the corresponding IMC Milestone --->

🙌 Proposal for {{Insert IMC Name}} Integrated Campaign

President

  • Open IMC Issue
  • Get Project Manager (announce in channel)
  • Get Company sponsor

Project Manager

  • Create #imc-[title] channel on Slack
  • Make announcement on #general channel
  • Build team on Slack (3-4 marketing + 3-4 devs)

[Ethan's OKRs]

📅 OKR Due: May 24th

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

📅Sat May 23

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

📅Sun May 24

  • 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

[Code Deliverable] Simple side-scrolling platformer game

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Insert Tech Here}}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

Proposal for Integrating GraphQL APIs to Projects [Integrated Campaign]

<--- The DRI for this issue is the President. They will be responsible for keeping this issue up to date at all times --->
<--- Add this issue into the corresponding IMC Milestone --->

🙌 Proposal for {{Insert IMC Name}} Integrated Campaign

President

  • Open IMC Issue
  • Get Project Manager (announce in channel)
  • Get Company sponsor

Project Manager

  • Create #imc-[title] channel on Slack
  • Make announcement on #general channel
  • Build team on Slack (3-4 marketing + 3-4 devs)

Content Development Plan - How to Build Your Own Website - Introduction to HTML, CSS, and Javascript

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{How to Build Your Own Website - Introduction to HTML, CSS, and Javascript}}
  • Topic: {{Front-end Development}}
  • Sub-topic: {{HTML/CSS, Javascript}}
  • Structure: {{Step-by-step tutorial}}
  • Description (5-7+ sentences): {{This blog will be a step-by-step tutorial on how to create a personal website. Since this blog is beginner-friendly, it will also recommend and briefly step through how to download and set up a code editor. Also, before the actual tutorial, the blog will introduce its sub-topics as what is need to create a website, HTML/CSS and Javascript, and define those terms. This will inform the reader of the basic tools of web development and provide a foundation in preparation before diving into the tutorial. This blog will not exactly cover the details on how to customize and decorate, but it will give the reader a solid start to creating a functional website.}}
  • Resources needed: {{workshops.hackclub.com/personal_website, docs.microsoft.com/en-us/learn/modules/build-simple-website}}

Step 2

  • Describe target audience (3-5+ sentences):
    This blog will serve as an introduction to HTML/CSS and Javascript for people who are interested in web development and are beginners with code. For people who interested in the idea of creating something on their own but do not know where or how to start, this guide will be open to people who do not have any experience and jumpstart their journey into coding. The content of this blog will be geared towards people interested in computer science and design, such as designers wanting to create an online portfolio to display their work and track their personal progress.

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences):
      The blog will start by introducing the end goal--creating a basic personal website--and how this will serve as a basic foundation for web development and design. Then, the blog will teach the reader how to set up their developer environment and briefly outline the process of creating a website using HTML/CSS and Javascript.

    • Middle (2-3+ sentences):
      Now, the blog will expand on each step that was outlined in the beginning. The first part will teach the reader how to set up the structure of the website with HTML coding. Then, the blog will go into how to stylize with CSS and add interactivity with javascript, and also explain how these files interact with each other to form a functional website. With each step, there will be screenshots and code snippets to supplement the tutorial and help the reader visualize the process.

    • End (2-3+ sentences):
      Here, the blog will prompt the reader to run their files and show how to interact with the website. Then, because this is a basic start to creating a complex customized website, the blog will encourage the reader to continue to build their site as stylize however they want, such as an online portfolio and so on. The blog will suggest how to learn more about web development and provide resources the reader may look for in enhancing and developing their website.

  • Submit blog choice on airtable.

  • Create Content Development Issue

[Emily's OKRs]

📅 OKR Due: May 24th

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

📅Sat May 23

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

📅Sun May 24

  • 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

[Code Deliverable] Intro to Supervised Learning

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Insert Tech Here}}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

[Code Deliverable] Game Theory: Making Statistical Decisions

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Insert Tech Here}}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

[Alex OKRs]

📅 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

[Ruby's OKRs]

📅 OKR Due: May 24th

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

📅Sat May 23

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

📅Sun May 24

  • 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

[Code Deliverable] How to Build Your Own Website - Introduction to HTML, CSS, and Javascript

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Insert Tech Here}}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

[Kyle OKRs]

📅 OKR Due: May 24th

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

📅Sat May 23

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

📅Sun May 24

  • 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

[Code Deliverable] Introduction k-means cluster analysis

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Insert Tech Here}}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

[Content Development Plan] Introduction k-means cluster analysis

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{Insert title here}}
  • Topic: {{Insert topic here}}
  • Sub-topic: {{Insert sub-topic here}}
  • Structure: {{Insert structure here}}
  • Description (5-7+ sentences): {{Insert description here}}
  • Resources needed: {{Insert resources here}}

Step 2

  • Describe target audience (3-5+ sentences):

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences):
    • Middle (2-3+ sentences):
    • End (2-3+ sentences):

  • Submit blog choice on airtable.

  • Create Content Development Issue

Proposal for Online BitQuest Events [Integrated Campaign]

<--- The DRI for this issue is the President. They will be responsible for keeping this issue up to date at all times --->
<--- Add this issue into the corresponding IMC Milestone --->

🙌 Proposal for {{Insert IMC Name}} Integrated Campaign

President

  • Open IMC Issue
  • Get Project Manager (announce in channel)
  • Get Company sponsor

Project Manager

  • Create #imc-[title] channel on Slack
  • Make announcement on #general channel
  • Build team on Slack (3-4 marketing + 3-4 devs)

Content Development Plan - AI Capable of Dialogue

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{Insert title here}}
  • Topic: {{Insert topic here}}
  • Sub-topic: {{Insert sub-topic here}}
  • Structure: {{Insert structure here}}
  • Description (5-7+ sentences): {{Insert description here}}
  • Resources needed: {{Insert resources here}}

Step 2

  • Describe target audience (3-5+ sentences):

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences):
    • Middle (2-3+ sentences):
    • End (2-3+ sentences):

  • Submit blog choice on airtable.

  • Create Content Development Issue

[Content Development Plan] Variables and data types

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{Insert title here}}
  • Topic: {{Insert topic here}}
  • Sub-topic: {{Insert sub-topic here}}
  • Structure: {{Insert structure here}}
  • Description (5-7+ sentences): {{Insert description here}}
  • Resources needed: {{Insert resources here}}

Step 2

  • Describe target audience (3-5+ sentences):

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences):
    • Middle (2-3+ sentences):
    • End (2-3+ sentences):

  • Submit blog choice on airtable.

  • Create Content Development Issue

Content Development Plan - Game Theory: Making Statistical Decisions

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{Insert title here}}
  • Topic: {{Insert topic here}}
  • Sub-topic: {{Insert sub-topic here}}
  • Structure: {{Insert structure here}}
  • Description (5-7+ sentences): {{Insert description here}}
  • Resources needed: {{Insert resources here}}

Step 2

  • Describe target audience (3-5+ sentences):

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences):
    • Middle (2-3+ sentences):
    • End (2-3+ sentences):

  • Submit blog choice on airtable.

  • Create Content Development Issue

[Code Deliverable] DIY ADHD Medication Reminder

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Insert Tech Here}}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

Proposal for NoSQL Database (with Redis + MongoDB) [Integrated Campaign]

<--- The DRI for this issue is the President. They will be responsible for keeping this issue up to date at all times --->
<--- Add this issue into the corresponding IMC Milestone --->

🙌 Proposal for {{Insert IMC Name}} Integrated Campaign

President

  • Open IMC Issue
  • Get Project Manager (announce in channel)
  • Get Company sponsor

Project Manager

  • Create #imc-[title] channel on Slack
  • Make announcement on #general channel
  • Build team on Slack (3-4 marketing + 3-4 devs)

May [DevRel OKRs]

The DRI for these OKRs is @shreyagupta98 (devrel)

Deadline:

Soft Deadline: May 23rd
Schedule for Social Media Team: May 25th

Onboarding Members

[Code Deliverable] Responsive Web

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Insert Tech Here}}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

[Code Deliverable] Implementation of Shoe Bot

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Insert Tech Here}}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

Content Development Plan - Intro to Supervised Learning

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

<-- Add this issue into the corresponding IMC Milestone -->

Step-By-Step Technical Blog Guide

Step 1

  • Title: {{Insert title here}}
  • Topic: {{Insert topic here}}
  • Sub-topic: {{Insert sub-topic here}}
  • Structure: {{Insert structure here}}
  • Description (5-7+ sentences): {{Insert description here}}
  • Resources needed: {{Insert resources here}}

Step 2

  • Describe target audience (3-5+ sentences):

Step 3

  • Outline your learning/teaching process:

    • Beginning (2-3+ sentences):
    • Middle (2-3+ sentences):
    • End (2-3+ sentences):

  • Submit blog choice on airtable.

  • Create Content Development Issue

[Chris's OKRs]

📅 OKR Due: May 24th

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

link to Google Colab: https://colab.research.google.com/drive/16qGlkkoVm5tjU_-gXBARKk0Oz_NLSKO8#scrollTo=dgwdMBygpsjr

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

📅Sat May 23

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

📅Sun May 24

  • 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

[Code Deliverable] Variables and data types

IMC Code Deliverable

Fill out the following checklist to close the issue!

  • Technology Used: {{Insert Tech Here}}
  • Time Taken on Blog
  • New Repo on bitprj created for the tutorial
  • Merge Starter Code in starter/
  • Merged Finished Code in finished/
  • Upload Finished Code on CodeSandbox
  • Link CodeSandbox to the Content Development Plan Issue
  • Check that all code is commented well

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.