Skip to content

[Workshop Dev Proposal] Make Music with Javascript and Tone.jsΒ #270

@bitterb3rry

Description

@bitterb3rry

Content Development Proposal Issue

πŸ“… DUE: Aug 12th

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

Workshop Guide

πŸ’ƒ Before starting

Workshop tracker

  • Contact PM to ask about workshop topics

πŸ“Œ Step 1: Proposal

πŸ”₯ DO NOT MERGE TO MASTER YET
πŸ“…**{{Due_Date}}**

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

πŸ“Œ 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
πŸ“…**{{Due_Date}}**

  • 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: Written Deliverables

πŸ”₯ DO NOT MERGE TO MASTER YET

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions