diff --git a/.gitbook/assets/after-cover.jpg b/.gitbook/assets/after-cover.jpg new file mode 100644 index 0000000..1527d6b Binary files /dev/null and b/.gitbook/assets/after-cover.jpg differ diff --git a/.gitbook/assets/blank-diagram.jpeg b/.gitbook/assets/blank-diagram.jpeg new file mode 100644 index 0000000..83969eb Binary files /dev/null and b/.gitbook/assets/blank-diagram.jpeg differ diff --git a/.gitbook/assets/coverupdated.jpg b/.gitbook/assets/coverupdated.jpg new file mode 100644 index 0000000..0817474 Binary files /dev/null and b/.gitbook/assets/coverupdated.jpg differ diff --git a/.gitbook/assets/data-science-roadmap.png b/.gitbook/assets/data-science-roadmap.png new file mode 100644 index 0000000..7fa79c4 Binary files /dev/null and b/.gitbook/assets/data-science-roadmap.png differ diff --git a/.gitbook/assets/devrel-flowchart-1 (1).png b/.gitbook/assets/devrel-flowchart-1 (1).png new file mode 100644 index 0000000..4244a86 Binary files /dev/null and b/.gitbook/assets/devrel-flowchart-1 (1).png differ diff --git a/.gitbook/assets/devrel-flowchart-1.png b/.gitbook/assets/devrel-flowchart-1.png new file mode 100644 index 0000000..d94dac8 Binary files /dev/null and b/.gitbook/assets/devrel-flowchart-1.png differ diff --git a/.gitbook/assets/devrel-flowchart-page-1.png b/.gitbook/assets/devrel-flowchart-page-1.png new file mode 100644 index 0000000..17f676c Binary files /dev/null and b/.gitbook/assets/devrel-flowchart-page-1.png differ diff --git a/.gitbook/assets/devrel-flowchart-page-2.png b/.gitbook/assets/devrel-flowchart-page-2.png new file mode 100644 index 0000000..5049502 Binary files /dev/null and b/.gitbook/assets/devrel-flowchart-page-2.png differ diff --git a/.gitbook/assets/devrel-flowchart-page-3.png b/.gitbook/assets/devrel-flowchart-page-3.png new file mode 100644 index 0000000..a026136 Binary files /dev/null and b/.gitbook/assets/devrel-flowchart-page-3.png differ diff --git a/.gitbook/assets/devrel-flowchart-page-4.png b/.gitbook/assets/devrel-flowchart-page-4.png new file mode 100644 index 0000000..3bd0b5c Binary files /dev/null and b/.gitbook/assets/devrel-flowchart-page-4.png differ diff --git a/.gitbook/assets/devrel-flowchart-page-5.png b/.gitbook/assets/devrel-flowchart-page-5.png new file mode 100644 index 0000000..50111da Binary files /dev/null and b/.gitbook/assets/devrel-flowchart-page-5.png differ diff --git a/.gitbook/assets/devrel-flowchart-page-6.png b/.gitbook/assets/devrel-flowchart-page-6.png new file mode 100644 index 0000000..ef0096a Binary files /dev/null and b/.gitbook/assets/devrel-flowchart-page-6.png differ diff --git a/.gitbook/assets/devrel-flowchart-page-7.png b/.gitbook/assets/devrel-flowchart-page-7.png new file mode 100644 index 0000000..a90b3ec Binary files /dev/null and b/.gitbook/assets/devrel-flowchart-page-7.png differ diff --git a/.gitbook/assets/devrel-flowchart-part-1.png b/.gitbook/assets/devrel-flowchart-part-1.png new file mode 100644 index 0000000..7b9b74b Binary files /dev/null and b/.gitbook/assets/devrel-flowchart-part-1.png differ diff --git a/.gitbook/assets/devrel-flowchart.png b/.gitbook/assets/devrel-flowchart.png new file mode 100644 index 0000000..7eaeb20 Binary files /dev/null and b/.gitbook/assets/devrel-flowchart.png differ diff --git a/.gitbook/assets/fruitnewsletter.pdf b/.gitbook/assets/fruitnewsletter.pdf new file mode 100644 index 0000000..35a64be Binary files /dev/null and b/.gitbook/assets/fruitnewsletter.pdf differ diff --git a/.gitbook/assets/gitbooks (1).jpg b/.gitbook/assets/gitbooks (1).jpg new file mode 100644 index 0000000..d4b3776 Binary files /dev/null and b/.gitbook/assets/gitbooks (1).jpg differ diff --git a/.gitbook/assets/gitbooks.jpg b/.gitbook/assets/gitbooks.jpg new file mode 100644 index 0000000..14cf130 Binary files /dev/null and b/.gitbook/assets/gitbooks.jpg differ diff --git a/.gitbook/assets/growthmarketingflyer_4.5-02.png b/.gitbook/assets/growthmarketingflyer_4.5-02.png new file mode 100644 index 0000000..0e7d705 Binary files /dev/null and b/.gitbook/assets/growthmarketingflyer_4.5-02.png differ diff --git a/.gitbook/assets/image (1).png b/.gitbook/assets/image (1).png new file mode 100644 index 0000000..5d4aa62 Binary files /dev/null and b/.gitbook/assets/image (1).png differ diff --git a/.gitbook/assets/image (10).png b/.gitbook/assets/image (10).png new file mode 100644 index 0000000..0659515 Binary files /dev/null and b/.gitbook/assets/image (10).png differ diff --git a/.gitbook/assets/image (11).png b/.gitbook/assets/image (11).png new file mode 100644 index 0000000..fafa8ac Binary files /dev/null and b/.gitbook/assets/image (11).png differ diff --git a/.gitbook/assets/image (12).png b/.gitbook/assets/image (12).png new file mode 100644 index 0000000..90ab267 Binary files /dev/null and b/.gitbook/assets/image (12).png differ diff --git a/.gitbook/assets/image (13).png b/.gitbook/assets/image (13).png new file mode 100644 index 0000000..3ac0e42 Binary files /dev/null and b/.gitbook/assets/image (13).png differ diff --git a/.gitbook/assets/image (14).png b/.gitbook/assets/image (14).png new file mode 100644 index 0000000..8751dcd Binary files /dev/null and b/.gitbook/assets/image (14).png differ diff --git a/.gitbook/assets/image (15).png b/.gitbook/assets/image (15).png new file mode 100644 index 0000000..3555e70 Binary files /dev/null and b/.gitbook/assets/image (15).png differ diff --git a/.gitbook/assets/image (16).png b/.gitbook/assets/image (16).png new file mode 100644 index 0000000..463ac74 Binary files /dev/null and b/.gitbook/assets/image (16).png differ diff --git a/.gitbook/assets/image (17).png b/.gitbook/assets/image (17).png new file mode 100644 index 0000000..f90e5a1 Binary files /dev/null and b/.gitbook/assets/image (17).png differ diff --git a/.gitbook/assets/image (18).png b/.gitbook/assets/image (18).png new file mode 100644 index 0000000..3bb7b2e Binary files /dev/null and b/.gitbook/assets/image (18).png differ diff --git a/.gitbook/assets/image (19).png b/.gitbook/assets/image (19).png new file mode 100644 index 0000000..9db86e1 Binary files /dev/null and b/.gitbook/assets/image (19).png differ diff --git a/.gitbook/assets/image (2).png b/.gitbook/assets/image (2).png new file mode 100644 index 0000000..2247831 Binary files /dev/null and b/.gitbook/assets/image (2).png differ diff --git a/.gitbook/assets/image (20).png b/.gitbook/assets/image (20).png new file mode 100644 index 0000000..7f6eb27 Binary files /dev/null and b/.gitbook/assets/image (20).png differ diff --git a/.gitbook/assets/image (3).png b/.gitbook/assets/image (3).png new file mode 100644 index 0000000..cc17c1f Binary files /dev/null and b/.gitbook/assets/image (3).png differ diff --git a/.gitbook/assets/image (4).png b/.gitbook/assets/image (4).png new file mode 100644 index 0000000..bc10693 Binary files /dev/null and b/.gitbook/assets/image (4).png differ diff --git a/.gitbook/assets/image (5).png b/.gitbook/assets/image (5).png new file mode 100644 index 0000000..b9a5bab Binary files /dev/null and b/.gitbook/assets/image (5).png differ diff --git a/.gitbook/assets/image (6).png b/.gitbook/assets/image (6).png new file mode 100644 index 0000000..97749d8 Binary files /dev/null and b/.gitbook/assets/image (6).png differ diff --git a/.gitbook/assets/image (7).png b/.gitbook/assets/image (7).png new file mode 100644 index 0000000..3555e70 Binary files /dev/null and b/.gitbook/assets/image (7).png differ diff --git a/.gitbook/assets/image (8).png b/.gitbook/assets/image (8).png new file mode 100644 index 0000000..c8bbe57 Binary files /dev/null and b/.gitbook/assets/image (8).png differ diff --git a/.gitbook/assets/image (9).png b/.gitbook/assets/image (9).png new file mode 100644 index 0000000..a538396 Binary files /dev/null and b/.gitbook/assets/image (9).png differ diff --git a/.gitbook/assets/image.png b/.gitbook/assets/image.png new file mode 100644 index 0000000..a538396 Binary files /dev/null and b/.gitbook/assets/image.png differ diff --git a/.gitbook/assets/newsletter-2pg2-02.png b/.gitbook/assets/newsletter-2pg2-02.png new file mode 100644 index 0000000..e940eee Binary files /dev/null and b/.gitbook/assets/newsletter-2pg2-02.png differ diff --git a/.gitbook/assets/newsletter2_4.9.pdf b/.gitbook/assets/newsletter2_4.9.pdf new file mode 100644 index 0000000..5442014 Binary files /dev/null and b/.gitbook/assets/newsletter2_4.9.pdf differ diff --git a/.gitbook/assets/onboarding-2.png b/.gitbook/assets/onboarding-2.png new file mode 100644 index 0000000..f114679 Binary files /dev/null and b/.gitbook/assets/onboarding-2.png differ diff --git a/.gitbook/assets/pictur8.png b/.gitbook/assets/pictur8.png new file mode 100644 index 0000000..1dd1cae Binary files /dev/null and b/.gitbook/assets/pictur8.png differ diff --git a/.gitbook/assets/picture1.png b/.gitbook/assets/picture1.png new file mode 100644 index 0000000..cb3e3c3 Binary files /dev/null and b/.gitbook/assets/picture1.png differ diff --git a/.gitbook/assets/picture11 (1).png b/.gitbook/assets/picture11 (1).png new file mode 100644 index 0000000..a908b58 Binary files /dev/null and b/.gitbook/assets/picture11 (1).png differ diff --git a/.gitbook/assets/picture11.png b/.gitbook/assets/picture11.png new file mode 100644 index 0000000..a908b58 Binary files /dev/null and b/.gitbook/assets/picture11.png differ diff --git a/.gitbook/assets/picture12.png b/.gitbook/assets/picture12.png new file mode 100644 index 0000000..b22f38d Binary files /dev/null and b/.gitbook/assets/picture12.png differ diff --git a/.gitbook/assets/picture2.png b/.gitbook/assets/picture2.png new file mode 100644 index 0000000..7888037 Binary files /dev/null and b/.gitbook/assets/picture2.png differ diff --git a/.gitbook/assets/picture3.png b/.gitbook/assets/picture3.png new file mode 100644 index 0000000..540b52b Binary files /dev/null and b/.gitbook/assets/picture3.png differ diff --git a/.gitbook/assets/picture4.png b/.gitbook/assets/picture4.png new file mode 100644 index 0000000..789bfc0 Binary files /dev/null and b/.gitbook/assets/picture4.png differ diff --git a/.gitbook/assets/picture5.png b/.gitbook/assets/picture5.png new file mode 100644 index 0000000..25d7f1b Binary files /dev/null and b/.gitbook/assets/picture5.png differ diff --git a/.gitbook/assets/picture6.png b/.gitbook/assets/picture6.png new file mode 100644 index 0000000..e505a9b Binary files /dev/null and b/.gitbook/assets/picture6.png differ diff --git a/.gitbook/assets/picture7.png b/.gitbook/assets/picture7.png new file mode 100644 index 0000000..c5d023e Binary files /dev/null and b/.gitbook/assets/picture7.png differ diff --git a/.gitbook/assets/picture9.png b/.gitbook/assets/picture9.png new file mode 100644 index 0000000..c60a8a6 Binary files /dev/null and b/.gitbook/assets/picture9.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-12.31.30-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-12.31.30-pm.png new file mode 100644 index 0000000..af3179a Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-12.31.30-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-3.20.28-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-3.20.28-pm.png new file mode 100644 index 0000000..d9721d2 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-3.20.28-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-3.23.56-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-3.23.56-pm.png new file mode 100644 index 0000000..877c8bc Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-3.23.56-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.28.58-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.28.58-pm.png new file mode 100644 index 0000000..27c8812 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.28.58-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.29.05-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.29.05-pm.png new file mode 100644 index 0000000..d917205 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.29.05-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.29.11-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.29.11-pm.png new file mode 100644 index 0000000..cde33fe Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.29.11-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.40.44-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.40.44-pm.png new file mode 100644 index 0000000..d083dae Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.40.44-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.40.46-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.40.46-pm.png new file mode 100644 index 0000000..008eb5d Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.40.46-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.41.46-pm (1).png b/.gitbook/assets/screen-shot-2020-04-04-at-4.41.46-pm (1).png new file mode 100644 index 0000000..f983c31 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.41.46-pm (1).png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.41.46-pm (2).png b/.gitbook/assets/screen-shot-2020-04-04-at-4.41.46-pm (2).png new file mode 100644 index 0000000..3ae8eff Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.41.46-pm (2).png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.41.46-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.41.46-pm.png new file mode 100644 index 0000000..f983c31 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.41.46-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.45.16-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.45.16-pm.png new file mode 100644 index 0000000..beb0760 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.45.16-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.45.22-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.45.22-pm.png new file mode 100644 index 0000000..bb18f26 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.45.22-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.45.30-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.45.30-pm.png new file mode 100644 index 0000000..1395398 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.45.30-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.45.38-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.45.38-pm.png new file mode 100644 index 0000000..3a60a37 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.45.38-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.45.59-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.45.59-pm.png new file mode 100644 index 0000000..c42f04d Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.45.59-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-4.46.03-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-4.46.03-pm.png new file mode 100644 index 0000000..fde06af Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-4.46.03-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-7.03.19-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-7.03.19-pm.png new file mode 100644 index 0000000..b8bf5ff Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-7.03.19-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-7.03.25-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-7.03.25-pm.png new file mode 100644 index 0000000..24a296b Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-7.03.25-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-7.03.29-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-7.03.29-pm.png new file mode 100644 index 0000000..30384cf Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-7.03.29-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-7.03.33-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-7.03.33-pm.png new file mode 100644 index 0000000..935fd07 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-7.03.33-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-7.03.54-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-7.03.54-pm.png new file mode 100644 index 0000000..50710ad Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-7.03.54-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-7.04.05-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-7.04.05-pm.png new file mode 100644 index 0000000..fa22af8 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-7.04.05-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-7.04.25-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-7.04.25-pm.png new file mode 100644 index 0000000..2e44fb8 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-7.04.25-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-7.04.31-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-7.04.31-pm.png new file mode 100644 index 0000000..bba1ad0 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-7.04.31-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-8.13.44-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-8.13.44-pm.png new file mode 100644 index 0000000..fd93962 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-8.13.44-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-04-at-8.16.51-pm.png b/.gitbook/assets/screen-shot-2020-04-04-at-8.16.51-pm.png new file mode 100644 index 0000000..88cdb28 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-04-at-8.16.51-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-05-at-3.43.24-pm.png b/.gitbook/assets/screen-shot-2020-04-05-at-3.43.24-pm.png new file mode 100644 index 0000000..85227dc Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-05-at-3.43.24-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-05-at-3.43.34-pm.png b/.gitbook/assets/screen-shot-2020-04-05-at-3.43.34-pm.png new file mode 100644 index 0000000..a5dfb64 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-05-at-3.43.34-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-05-at-4.01.27-pm.png b/.gitbook/assets/screen-shot-2020-04-05-at-4.01.27-pm.png new file mode 100644 index 0000000..788299f Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-05-at-4.01.27-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-08-at-8.31.47-pm.png b/.gitbook/assets/screen-shot-2020-04-08-at-8.31.47-pm.png new file mode 100644 index 0000000..2ca5f41 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-08-at-8.31.47-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-08-at-8.55.14-pm.png b/.gitbook/assets/screen-shot-2020-04-08-at-8.55.14-pm.png new file mode 100644 index 0000000..40e200a Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-08-at-8.55.14-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-08-at-9.20.43-pm.png b/.gitbook/assets/screen-shot-2020-04-08-at-9.20.43-pm.png new file mode 100644 index 0000000..50bd991 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-08-at-9.20.43-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-08-at-9.32.45-pm.png b/.gitbook/assets/screen-shot-2020-04-08-at-9.32.45-pm.png new file mode 100644 index 0000000..edd8ae0 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-08-at-9.32.45-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-08-at-9.41.50-pm.png b/.gitbook/assets/screen-shot-2020-04-08-at-9.41.50-pm.png new file mode 100644 index 0000000..44c1924 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-08-at-9.41.50-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-09-at-10.00.22-pm.png b/.gitbook/assets/screen-shot-2020-04-09-at-10.00.22-pm.png new file mode 100644 index 0000000..14e1e2d Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-09-at-10.00.22-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-09-at-10.00.34-pm.png b/.gitbook/assets/screen-shot-2020-04-09-at-10.00.34-pm.png new file mode 100644 index 0000000..1f11dc3 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-09-at-10.00.34-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-09-at-10.00.49-pm.png b/.gitbook/assets/screen-shot-2020-04-09-at-10.00.49-pm.png new file mode 100644 index 0000000..55a9487 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-09-at-10.00.49-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-09-at-10.01.00-pm.png b/.gitbook/assets/screen-shot-2020-04-09-at-10.01.00-pm.png new file mode 100644 index 0000000..11aea7b Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-09-at-10.01.00-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-09-at-9.38.05-pm.png b/.gitbook/assets/screen-shot-2020-04-09-at-9.38.05-pm.png new file mode 100644 index 0000000..1669917 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-09-at-9.38.05-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-09-at-9.42.46-pm.png b/.gitbook/assets/screen-shot-2020-04-09-at-9.42.46-pm.png new file mode 100644 index 0000000..820459d Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-09-at-9.42.46-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-09-at-9.45.00-pm.png b/.gitbook/assets/screen-shot-2020-04-09-at-9.45.00-pm.png new file mode 100644 index 0000000..a06895d Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-09-at-9.45.00-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-09-at-9.50.08-pm.png b/.gitbook/assets/screen-shot-2020-04-09-at-9.50.08-pm.png new file mode 100644 index 0000000..35f61b7 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-09-at-9.50.08-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-09-at-9.52.39-pm.png b/.gitbook/assets/screen-shot-2020-04-09-at-9.52.39-pm.png new file mode 100644 index 0000000..2d7beca Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-09-at-9.52.39-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-09-at-9.54.32-pm.png b/.gitbook/assets/screen-shot-2020-04-09-at-9.54.32-pm.png new file mode 100644 index 0000000..44a7e07 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-09-at-9.54.32-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-09-at-9.56.38-pm.png b/.gitbook/assets/screen-shot-2020-04-09-at-9.56.38-pm.png new file mode 100644 index 0000000..5ebc7cf Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-09-at-9.56.38-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-04-12-at-11.27.57-pm.png b/.gitbook/assets/screen-shot-2020-04-12-at-11.27.57-pm.png new file mode 100644 index 0000000..29fca01 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-04-12-at-11.27.57-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-01-at-10.13.55-pm.png b/.gitbook/assets/screen-shot-2020-05-01-at-10.13.55-pm.png new file mode 100644 index 0000000..42dd23f Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-01-at-10.13.55-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-01-at-10.19.10-pm.png b/.gitbook/assets/screen-shot-2020-05-01-at-10.19.10-pm.png new file mode 100644 index 0000000..acbb21f Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-01-at-10.19.10-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-01-at-10.25.06-pm.png b/.gitbook/assets/screen-shot-2020-05-01-at-10.25.06-pm.png new file mode 100644 index 0000000..91f785d Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-01-at-10.25.06-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-01-at-10.31.35-pm.png b/.gitbook/assets/screen-shot-2020-05-01-at-10.31.35-pm.png new file mode 100644 index 0000000..ed91422 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-01-at-10.31.35-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-01-at-11.35.17-pm.png b/.gitbook/assets/screen-shot-2020-05-01-at-11.35.17-pm.png new file mode 100644 index 0000000..6a08433 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-01-at-11.35.17-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-01-at-8.59.26-pm.png b/.gitbook/assets/screen-shot-2020-05-01-at-8.59.26-pm.png new file mode 100644 index 0000000..682e5c8 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-01-at-8.59.26-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-01-at-9.21.38-pm.png b/.gitbook/assets/screen-shot-2020-05-01-at-9.21.38-pm.png new file mode 100644 index 0000000..f4239ee Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-01-at-9.21.38-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-01-at-9.29.11-pm.png b/.gitbook/assets/screen-shot-2020-05-01-at-9.29.11-pm.png new file mode 100644 index 0000000..6b259dd Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-01-at-9.29.11-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-02-at-3.18.55-pm.png b/.gitbook/assets/screen-shot-2020-05-02-at-3.18.55-pm.png new file mode 100644 index 0000000..c77219f Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-02-at-3.18.55-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-02-at-3.29.05-pm.png b/.gitbook/assets/screen-shot-2020-05-02-at-3.29.05-pm.png new file mode 100644 index 0000000..94df78f Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-02-at-3.29.05-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-02-at-3.35.22-pm.png b/.gitbook/assets/screen-shot-2020-05-02-at-3.35.22-pm.png new file mode 100644 index 0000000..1c8fa94 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-02-at-3.35.22-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-02-at-3.35.46-pm.png b/.gitbook/assets/screen-shot-2020-05-02-at-3.35.46-pm.png new file mode 100644 index 0000000..30c79c2 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-02-at-3.35.46-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-02-at-3.37.56-pm.png b/.gitbook/assets/screen-shot-2020-05-02-at-3.37.56-pm.png new file mode 100644 index 0000000..176494e Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-02-at-3.37.56-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-02-at-3.51.03-pm.png b/.gitbook/assets/screen-shot-2020-05-02-at-3.51.03-pm.png new file mode 100644 index 0000000..2f4747e Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-02-at-3.51.03-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-02-at-4.21.33-pm.png b/.gitbook/assets/screen-shot-2020-05-02-at-4.21.33-pm.png new file mode 100644 index 0000000..bf164d8 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-02-at-4.21.33-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-02-at-4.22.34-pm.png b/.gitbook/assets/screen-shot-2020-05-02-at-4.22.34-pm.png new file mode 100644 index 0000000..96cd592 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-02-at-4.22.34-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-02-at-4.23.29-pm.png b/.gitbook/assets/screen-shot-2020-05-02-at-4.23.29-pm.png new file mode 100644 index 0000000..b568414 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-02-at-4.23.29-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-02-at-4.31.47-pm.png b/.gitbook/assets/screen-shot-2020-05-02-at-4.31.47-pm.png new file mode 100644 index 0000000..cc5b932 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-02-at-4.31.47-pm.png differ diff --git a/.gitbook/assets/screen-shot-2020-05-05-at-9.02.52-am.png b/.gitbook/assets/screen-shot-2020-05-05-at-9.02.52-am.png new file mode 100644 index 0000000..71cc788 Binary files /dev/null and b/.gitbook/assets/screen-shot-2020-05-05-at-9.02.52-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-04-at-8.49.08-am.png b/.gitbook/assets/screenshot-2020-04-04-at-8.49.08-am.png new file mode 100644 index 0000000..b17f46e Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-04-at-8.49.08-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-04-at-8.49.58-am.png b/.gitbook/assets/screenshot-2020-04-04-at-8.49.58-am.png new file mode 100644 index 0000000..296e4f1 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-04-at-8.49.58-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-04-at-8.50.57-am.png b/.gitbook/assets/screenshot-2020-04-04-at-8.50.57-am.png new file mode 100644 index 0000000..5da7d23 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-04-at-8.50.57-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-04-at-8.52.16-am.png b/.gitbook/assets/screenshot-2020-04-04-at-8.52.16-am.png new file mode 100644 index 0000000..7127137 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-04-at-8.52.16-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-04-at-9.14.29-am.png b/.gitbook/assets/screenshot-2020-04-04-at-9.14.29-am.png new file mode 100644 index 0000000..bc31095 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-04-at-9.14.29-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-04-at-9.14.48-am.png b/.gitbook/assets/screenshot-2020-04-04-at-9.14.48-am.png new file mode 100644 index 0000000..ddc8182 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-04-at-9.14.48-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-04-at-9.17.54-am.png b/.gitbook/assets/screenshot-2020-04-04-at-9.17.54-am.png new file mode 100644 index 0000000..4d01606 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-04-at-9.17.54-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-08-at-5.50.16-am.png b/.gitbook/assets/screenshot-2020-04-08-at-5.50.16-am.png new file mode 100644 index 0000000..1f6940c Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-08-at-5.50.16-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-09-at-3.42.53-am.png b/.gitbook/assets/screenshot-2020-04-09-at-3.42.53-am.png new file mode 100644 index 0000000..2fafeaf Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-09-at-3.42.53-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-09-at-3.56.48-am.png b/.gitbook/assets/screenshot-2020-04-09-at-3.56.48-am.png new file mode 100644 index 0000000..518b71c Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-09-at-3.56.48-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-09-at-5.23.01-am.png b/.gitbook/assets/screenshot-2020-04-09-at-5.23.01-am.png new file mode 100644 index 0000000..10b9322 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-09-at-5.23.01-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-09-at-5.24.19-am.png b/.gitbook/assets/screenshot-2020-04-09-at-5.24.19-am.png new file mode 100644 index 0000000..9dc26ad Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-09-at-5.24.19-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-09-at-5.28.37-am.png b/.gitbook/assets/screenshot-2020-04-09-at-5.28.37-am.png new file mode 100644 index 0000000..2e42b53 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-09-at-5.28.37-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-09-at-5.28.42-am (1).png b/.gitbook/assets/screenshot-2020-04-09-at-5.28.42-am (1).png new file mode 100644 index 0000000..a3a72ab Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-09-at-5.28.42-am (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-09-at-5.28.42-am.png b/.gitbook/assets/screenshot-2020-04-09-at-5.28.42-am.png new file mode 100644 index 0000000..a3a72ab Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-09-at-5.28.42-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-09-at-5.42.56-am.png b/.gitbook/assets/screenshot-2020-04-09-at-5.42.56-am.png new file mode 100644 index 0000000..762b42a Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-09-at-5.42.56-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-09-at-6.17.53-am.png b/.gitbook/assets/screenshot-2020-04-09-at-6.17.53-am.png new file mode 100644 index 0000000..b974d1d Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-09-at-6.17.53-am.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-7.57.36-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-7.57.36-pm (1).png new file mode 100644 index 0000000..37af1ff Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-7.57.36-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-7.57.36-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-7.57.36-pm.png new file mode 100644 index 0000000..37af1ff Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-7.57.36-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-7.58.13-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-7.58.13-pm (1).png new file mode 100644 index 0000000..f35a480 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-7.58.13-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-7.58.13-pm (2).png b/.gitbook/assets/screenshot-2020-04-28-at-7.58.13-pm (2).png new file mode 100644 index 0000000..9563da1 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-7.58.13-pm (2).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-7.58.13-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-7.58.13-pm.png new file mode 100644 index 0000000..9563da1 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-7.58.13-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-7.59.29-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-7.59.29-pm (1).png new file mode 100644 index 0000000..c3fdf5c Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-7.59.29-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-7.59.29-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-7.59.29-pm.png new file mode 100644 index 0000000..c3fdf5c Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-7.59.29-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-7.59.51-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-7.59.51-pm (1).png new file mode 100644 index 0000000..f65997a Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-7.59.51-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-7.59.51-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-7.59.51-pm.png new file mode 100644 index 0000000..f65997a Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-7.59.51-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.00.06-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.00.06-pm (1).png new file mode 100644 index 0000000..7bef77f Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.00.06-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.00.06-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.00.06-pm.png new file mode 100644 index 0000000..7bef77f Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.00.06-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.00.42-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.00.42-pm (1).png new file mode 100644 index 0000000..c6e8b3f Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.00.42-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.00.42-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.00.42-pm.png new file mode 100644 index 0000000..c6e8b3f Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.00.42-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.01.04-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.01.04-pm (1).png new file mode 100644 index 0000000..b69ec46 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.01.04-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.01.04-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.01.04-pm.png new file mode 100644 index 0000000..b69ec46 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.01.04-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.01.30-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.01.30-pm (1).png new file mode 100644 index 0000000..14ca976 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.01.30-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.01.30-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.01.30-pm.png new file mode 100644 index 0000000..14ca976 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.01.30-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.01.38-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.01.38-pm (1).png new file mode 100644 index 0000000..2d42c2b Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.01.38-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.01.38-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.01.38-pm.png new file mode 100644 index 0000000..2d42c2b Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.01.38-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.01.51-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.01.51-pm (1).png new file mode 100644 index 0000000..97d830a Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.01.51-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.01.51-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.01.51-pm.png new file mode 100644 index 0000000..97d830a Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.01.51-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.01.57-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.01.57-pm (1).png new file mode 100644 index 0000000..0f86cb0 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.01.57-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.01.57-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.01.57-pm.png new file mode 100644 index 0000000..0f86cb0 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.01.57-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.02.04-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.02.04-pm (1).png new file mode 100644 index 0000000..619306f Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.02.04-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.02.04-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.02.04-pm.png new file mode 100644 index 0000000..619306f Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.02.04-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.02.26-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.02.26-pm (1).png new file mode 100644 index 0000000..ebbc97b Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.02.26-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.02.26-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.02.26-pm.png new file mode 100644 index 0000000..ebbc97b Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.02.26-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.02.31-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.02.31-pm (1).png new file mode 100644 index 0000000..06e45d0 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.02.31-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.02.31-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.02.31-pm.png new file mode 100644 index 0000000..06e45d0 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.02.31-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.02.36-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.02.36-pm (1).png new file mode 100644 index 0000000..de047b0 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.02.36-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.02.36-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.02.36-pm.png new file mode 100644 index 0000000..de047b0 Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.02.36-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.03.05-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.03.05-pm (1).png new file mode 100644 index 0000000..8e7726e Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.03.05-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.03.05-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.03.05-pm.png new file mode 100644 index 0000000..8e7726e Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.03.05-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.03.25-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.03.25-pm (1).png new file mode 100644 index 0000000..e0504cf Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.03.25-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.03.25-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.03.25-pm.png new file mode 100644 index 0000000..e0504cf Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.03.25-pm.png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.03.51-pm (1).png b/.gitbook/assets/screenshot-2020-04-28-at-8.03.51-pm (1).png new file mode 100644 index 0000000..aa2c4ff Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.03.51-pm (1).png differ diff --git a/.gitbook/assets/screenshot-2020-04-28-at-8.03.51-pm.png b/.gitbook/assets/screenshot-2020-04-28-at-8.03.51-pm.png new file mode 100644 index 0000000..aa2c4ff Binary files /dev/null and b/.gitbook/assets/screenshot-2020-04-28-at-8.03.51-pm.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-11-12-41-20 (1).png b/.gitbook/assets/screenshot-from-2020-04-11-12-41-20 (1).png new file mode 100644 index 0000000..0f0f84b Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-11-12-41-20 (1).png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-11-12-41-20.png b/.gitbook/assets/screenshot-from-2020-04-11-12-41-20.png new file mode 100644 index 0000000..8d86db4 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-11-12-41-20.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-12-17-58-42 (1).png b/.gitbook/assets/screenshot-from-2020-04-12-17-58-42 (1).png new file mode 100644 index 0000000..8e3839b Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-12-17-58-42 (1).png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-12-17-58-42.png b/.gitbook/assets/screenshot-from-2020-04-12-17-58-42.png new file mode 100644 index 0000000..471ca2e Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-12-17-58-42.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-12-17-59-21.png b/.gitbook/assets/screenshot-from-2020-04-12-17-59-21.png new file mode 100644 index 0000000..be3c532 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-12-17-59-21.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-12-17-59-36.png b/.gitbook/assets/screenshot-from-2020-04-12-17-59-36.png new file mode 100644 index 0000000..2fb9081 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-12-17-59-36.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-12-18-13-45 (1).png b/.gitbook/assets/screenshot-from-2020-04-12-18-13-45 (1).png new file mode 100644 index 0000000..e87bff6 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-12-18-13-45 (1).png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-12-18-13-45.png b/.gitbook/assets/screenshot-from-2020-04-12-18-13-45.png new file mode 100644 index 0000000..0426881 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-12-18-13-45.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-12-18-36-01.png b/.gitbook/assets/screenshot-from-2020-04-12-18-36-01.png new file mode 100644 index 0000000..6609dc8 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-12-18-36-01.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-16-57-10.png b/.gitbook/assets/screenshot-from-2020-04-15-16-57-10.png new file mode 100644 index 0000000..34d5183 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-16-57-10.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-16-57-50.png b/.gitbook/assets/screenshot-from-2020-04-15-16-57-50.png new file mode 100644 index 0000000..5eb7372 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-16-57-50.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-16-59-12.png b/.gitbook/assets/screenshot-from-2020-04-15-16-59-12.png new file mode 100644 index 0000000..a44bcd5 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-16-59-12.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-17-00-06.png b/.gitbook/assets/screenshot-from-2020-04-15-17-00-06.png new file mode 100644 index 0000000..5343c66 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-17-00-06.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-17-02-16.png b/.gitbook/assets/screenshot-from-2020-04-15-17-02-16.png new file mode 100644 index 0000000..86f043c Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-17-02-16.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-17-03-36.png b/.gitbook/assets/screenshot-from-2020-04-15-17-03-36.png new file mode 100644 index 0000000..bb84dad Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-17-03-36.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-17-04-18 (1).png b/.gitbook/assets/screenshot-from-2020-04-15-17-04-18 (1).png new file mode 100644 index 0000000..8926967 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-17-04-18 (1).png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-17-04-18.png b/.gitbook/assets/screenshot-from-2020-04-15-17-04-18.png new file mode 100644 index 0000000..fe5ba3a Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-17-04-18.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-17-05-02.png b/.gitbook/assets/screenshot-from-2020-04-15-17-05-02.png new file mode 100644 index 0000000..9814b62 Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-17-05-02.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-17-06-34.png b/.gitbook/assets/screenshot-from-2020-04-15-17-06-34.png new file mode 100644 index 0000000..060cbde Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-17-06-34.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-17-07-08.png b/.gitbook/assets/screenshot-from-2020-04-15-17-07-08.png new file mode 100644 index 0000000..dd2f32f Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-17-07-08.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-17-07-22.png b/.gitbook/assets/screenshot-from-2020-04-15-17-07-22.png new file mode 100644 index 0000000..cd4d26f Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-17-07-22.png differ diff --git a/.gitbook/assets/screenshot-from-2020-04-15-17-17-48.png b/.gitbook/assets/screenshot-from-2020-04-15-17-17-48.png new file mode 100644 index 0000000..b2120ff Binary files /dev/null and b/.gitbook/assets/screenshot-from-2020-04-15-17-17-48.png differ diff --git a/.gitbook/assets/sponsorcover-01.png b/.gitbook/assets/sponsorcover-01.png new file mode 100644 index 0000000..066b56a Binary files /dev/null and b/.gitbook/assets/sponsorcover-01.png differ diff --git a/.gitbook/assets/step-1.PNG b/.gitbook/assets/step-1.PNG new file mode 100644 index 0000000..fa44d61 Binary files /dev/null and b/.gitbook/assets/step-1.PNG differ diff --git a/.gitbook/assets/step-10.PNG b/.gitbook/assets/step-10.PNG new file mode 100644 index 0000000..dde49f1 Binary files /dev/null and b/.gitbook/assets/step-10.PNG differ diff --git a/.gitbook/assets/step-11.PNG b/.gitbook/assets/step-11.PNG new file mode 100644 index 0000000..1bdbb7c Binary files /dev/null and b/.gitbook/assets/step-11.PNG differ diff --git a/.gitbook/assets/step-12.PNG b/.gitbook/assets/step-12.PNG new file mode 100644 index 0000000..2e53dc6 Binary files /dev/null and b/.gitbook/assets/step-12.PNG differ diff --git a/.gitbook/assets/step-13.PNG b/.gitbook/assets/step-13.PNG new file mode 100644 index 0000000..f5d6410 Binary files /dev/null and b/.gitbook/assets/step-13.PNG differ diff --git a/.gitbook/assets/step-14.PNG b/.gitbook/assets/step-14.PNG new file mode 100644 index 0000000..eff7600 Binary files /dev/null and b/.gitbook/assets/step-14.PNG differ diff --git a/.gitbook/assets/step-15.PNG b/.gitbook/assets/step-15.PNG new file mode 100644 index 0000000..57e4861 Binary files /dev/null and b/.gitbook/assets/step-15.PNG differ diff --git a/.gitbook/assets/step-2.PNG b/.gitbook/assets/step-2.PNG new file mode 100644 index 0000000..1b6ff39 Binary files /dev/null and b/.gitbook/assets/step-2.PNG differ diff --git a/.gitbook/assets/step-3.PNG b/.gitbook/assets/step-3.PNG new file mode 100644 index 0000000..c1f44dd Binary files /dev/null and b/.gitbook/assets/step-3.PNG differ diff --git a/.gitbook/assets/step-4.PNG b/.gitbook/assets/step-4.PNG new file mode 100644 index 0000000..fcf64f9 Binary files /dev/null and b/.gitbook/assets/step-4.PNG differ diff --git a/.gitbook/assets/step-5.PNG b/.gitbook/assets/step-5.PNG new file mode 100644 index 0000000..7bcad33 Binary files /dev/null and b/.gitbook/assets/step-5.PNG differ diff --git a/.gitbook/assets/step-6.PNG b/.gitbook/assets/step-6.PNG new file mode 100644 index 0000000..e2c26c4 Binary files /dev/null and b/.gitbook/assets/step-6.PNG differ diff --git a/.gitbook/assets/step-7.PNG b/.gitbook/assets/step-7.PNG new file mode 100644 index 0000000..63af671 Binary files /dev/null and b/.gitbook/assets/step-7.PNG differ diff --git a/.gitbook/assets/step-8.PNG b/.gitbook/assets/step-8.PNG new file mode 100644 index 0000000..9751e95 Binary files /dev/null and b/.gitbook/assets/step-8.PNG differ diff --git a/.gitbook/assets/step-9.PNG b/.gitbook/assets/step-9.PNG new file mode 100644 index 0000000..b824efa Binary files /dev/null and b/.gitbook/assets/step-9.PNG differ diff --git a/.gitbook/assets/untitled-diagram-1 (1).png b/.gitbook/assets/untitled-diagram-1 (1).png new file mode 100644 index 0000000..5cd868c Binary files /dev/null and b/.gitbook/assets/untitled-diagram-1 (1).png differ diff --git a/.gitbook/assets/untitled-diagram-1.png b/.gitbook/assets/untitled-diagram-1.png new file mode 100644 index 0000000..5cd868c Binary files /dev/null and b/.gitbook/assets/untitled-diagram-1.png differ diff --git a/.gitbook/assets/untitled-diagram.png b/.gitbook/assets/untitled-diagram.png new file mode 100644 index 0000000..55e075e Binary files /dev/null and b/.gitbook/assets/untitled-diagram.png differ diff --git a/.gitbook/assets/workshop-flowchart-page-1-2.png b/.gitbook/assets/workshop-flowchart-page-1-2.png new file mode 100644 index 0000000..b28c4f9 Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-1-2.png differ diff --git a/.gitbook/assets/workshop-flowchart-page-2 (1).jpeg b/.gitbook/assets/workshop-flowchart-page-2 (1).jpeg new file mode 100644 index 0000000..2107922 Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-2 (1).jpeg differ diff --git a/.gitbook/assets/workshop-flowchart-page-2-1.png b/.gitbook/assets/workshop-flowchart-page-2-1.png new file mode 100644 index 0000000..e9203cc Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-2-1.png differ diff --git a/.gitbook/assets/workshop-flowchart-page-2.jpeg b/.gitbook/assets/workshop-flowchart-page-2.jpeg new file mode 100644 index 0000000..4e85c68 Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-2.jpeg differ diff --git a/.gitbook/assets/workshop-flowchart-page-3.png b/.gitbook/assets/workshop-flowchart-page-3.png new file mode 100644 index 0000000..e2e2a40 Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-3.png differ diff --git a/.gitbook/assets/workshop-flowchart-page-4 (1).png b/.gitbook/assets/workshop-flowchart-page-4 (1).png new file mode 100644 index 0000000..1fb5e25 Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-4 (1).png differ diff --git a/.gitbook/assets/workshop-flowchart-page-4.png b/.gitbook/assets/workshop-flowchart-page-4.png new file mode 100644 index 0000000..1fb5e25 Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-4.png differ diff --git a/.gitbook/assets/workshop-flowchart-page-5.png b/.gitbook/assets/workshop-flowchart-page-5.png new file mode 100644 index 0000000..8f1189f Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-5.png differ diff --git a/.gitbook/assets/workshop-flowchart-page-6 (1).png b/.gitbook/assets/workshop-flowchart-page-6 (1).png new file mode 100644 index 0000000..6669ad9 Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-6 (1).png differ diff --git a/.gitbook/assets/workshop-flowchart-page-6.png b/.gitbook/assets/workshop-flowchart-page-6.png new file mode 100644 index 0000000..6669ad9 Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-6.png differ diff --git a/.gitbook/assets/workshop-flowchart-page-7.png b/.gitbook/assets/workshop-flowchart-page-7.png new file mode 100644 index 0000000..61a82bb Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-7.png differ diff --git a/.gitbook/assets/workshop-flowchart-page-8.png b/.gitbook/assets/workshop-flowchart-page-8.png new file mode 100644 index 0000000..d1354db Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-8.png differ diff --git a/.gitbook/assets/workshop-flowchart-page-9.png b/.gitbook/assets/workshop-flowchart-page-9.png new file mode 100644 index 0000000..e0444f7 Binary files /dev/null and b/.gitbook/assets/workshop-flowchart-page-9.png differ diff --git a/README.md b/README.md index b373760..2cb9de4 100644 --- a/README.md +++ b/README.md @@ -42,23 +42,17 @@ We make software engineering and computer science education accessible to studen * [API Development/Microservices ](teams/developer-relations/teams/api-development-microservices.md) * [Blockchain](teams/developer-relations/teams/blockchain.md) - - ## Engineering - - ## Marketing - - ## People -[Talent Acquisition]() +[Talent Acquisition](./) [Inclusion & Diversity](organization/values/inclusion-and-diversity/) -[On-Boarding]() +[On-Boarding](./) ## Join Bit Project diff --git a/join.md b/join.md index 411b1af..b719b7f 100644 --- a/join.md +++ b/join.md @@ -2,5 +2,3 @@ {% page-ref page="teams/developer-relations/joining-the-core-team.md" %} - - diff --git a/organization/communication.md b/organization/communication.md index 97ce9a8..b4102df 100644 --- a/organization/communication.md +++ b/organization/communication.md @@ -1,10 +1,10 @@ # Communication -{% embed url="https://www.youtube.com/watch?v=2f9TkttynIk&feature=youtu.be" %} +{% embed url="https://www.youtube.com/watch?v=2f9TkttynIk&feature=youtu.be" caption="" %} **Effective Communication Webinar**, Becca Tran -## What is Communication? +## What is Communication? Communication is the exchange and sharing of ideas and information between two or more persons. Our organization is built upon **transparency** and learning different ways to **improve our communication skills. I**t is crucial for us to practice clear communication in ways that will help stay connected and work efficiently! @@ -47,8 +47,6 @@ Template: ### The Meeting Notes Template - - ![](../.gitbook/assets/screen-shot-2020-03-31-at-1.26.07-am.png) ![](../.gitbook/assets/screen-shot-2020-03-31-at-1.26.13-am.png) @@ -101,13 +99,11 @@ Before making an account, you must download slack onto both your computer and mo ![A good example of when to send a message through private DM versus Public Channels ](../.gitbook/assets/screen-shot-2020-03-31-at-8.11.56-pm.png) - - ### Hey Taco! Hey Taco is an application that is integrated with Slack. It is a way to give shoutouts and appreciation to people in your organization! What’s the point of all this taco giving? To put it simply: unity, recognition and gratitude. You name it and someone has probably given out a taco for it. Team member appreciation, a birthday, gratitude for leadership, or welcoming a new team member are all just a few of the reasons we give out tacos. You get 5 tacos a day! -![Example of one of colleague giving appreciation to other members for their hard work! ](../.gitbook/assets/screen-shot-2020-03-31-at-8.13.14-pm.png) +![Example of one of colleague giving appreciation to other members for their hard work! ](../.gitbook/assets/screen-shot-2020-03-31-at-8.13.14-pm.png) ## Zoom @@ -124,7 +120,7 @@ Hey Taco is an application that is integrated with Slack. It is a way to give sh ![](../.gitbook/assets/screen-shot-2020-03-31-at-8.15.52-pm.png) -### How Your First Meeting Will Generally Go +### How Your First Meeting Will Generally Go 1. Make a round of introductions 2. If we plan to record the meeting, the host of the meeting will get your consent to record @@ -140,7 +136,7 @@ Hey Taco is an application that is integrated with Slack. It is a way to give sh ![Supervisor's Calendly links are in their profile ](../.gitbook/assets/screen-shot-2020-03-31-at-8.18.12-pm-1.png) -## Google Calendar +## Google Calendar Google Calendar is a time-management and scheduling calendar service. Google Calendar allows users to create and edit events. Reminders can be enabled for events, with options available for type and time. Event locations can also be added, and other users can be invited to events. Google Calendar helps us all stay on the same schedule even with differences in time zones. **Going remote means having A LOT of virtual meetings:** @@ -148,7 +144,7 @@ Google Calendar is a time-management and scheduling calendar service. Google Cal * All Calendly events will be linked to the Calendar * All virtual socials will be updated on the Calendar -**If you are invited to any Google Calendar event, please RSVP as soon as possible.** +**If you are invited to any Google Calendar event, please RSVP as soon as possible.** ![](../.gitbook/assets/screen-shot-2020-03-31-at-8.20.23-pm.png) diff --git a/organization/mission-statement.md b/organization/mission-statement.md index 5e8f3eb..f6160cc 100644 --- a/organization/mission-statement.md +++ b/organization/mission-statement.md @@ -73,8 +73,6 @@ Our programs can and should expand over time in the following ways but balanced Note that expansion is important but as noted, should not come at the cost of sacrificing our program quality and outcomes. We need to find the right balance {% endhint %} - - **References** * [http://opensource.com/education/13/10/open-business-model-free-education](http://opensource.com/education/13/10/open-business-model-free-education) diff --git a/organization/organizational-structure/untitled.md b/organization/organizational-structure/untitled.md index d9225e6..2e1fd0a 100644 --- a/organization/organizational-structure/untitled.md +++ b/organization/organizational-structure/untitled.md @@ -2,7 +2,7 @@ **President** Daniel Kim -**People Department \( 1 Vacancy \)** +**People Department \( 1 Vacancy \)** | Role | Team | Person | | :--- | :--- | :--- | @@ -13,7 +13,7 @@ | Onboarding Manager | Onboarding | Minh Tu Nguyen | | Recruiter \(2\) | Onboarding | **VACANT** | -**Marketing Department \(4 Vacancies\)** +**Marketing Department \(4 Vacancies\)** | Role | Team | Person | | :--- | :--- | :--- | @@ -29,7 +29,7 @@ | Role | Team | Person | | :--- | :--- | :--- | | Director of Engineering | \*\*\*\* | Bryan Wong | -| Frontend Architect | Frontend | Bryan Zhang | +| Frontend Architect | Frontend | Bryan Zhang | | React.js Developer \(2\) | Frontend | **VACANT** | | Backend Developer | Backend | Jason Livinghouse | | Backend Developer \(2\) | Backend | **VACANT** | @@ -41,13 +41,13 @@ | Director of DevRel | \*\*\*\* | Kevin Vuong | | Content Development Manager | | Sarah Gerard | | Content Development Manager | | Owen Gao | -| Content Development Manager | | Ismail | +| Content Development Manager | | Ismail | | Content Development Manager | | Michelle Hu | | Content Development Manager | | Jeff Chhen | | Content Development Intern \(4\) | | **VACANT** | -| Content Developer \(5\) | Data Science | **VACANT** | -| Content Developer \(5\) | Block Chain | **VACANT** | -| Content Developer \(5\) | Frontend | **VACANT** | -| Content Developer \(5\) | API Development | **VACANT** | +| Content Developer \(5\) | Data Science | **VACANT** | +| Content Developer \(5\) | Block Chain | **VACANT** | +| Content Developer \(5\) | Frontend | **VACANT** | +| Content Developer \(5\) | API Development | **VACANT** | | Content Developer \(5\) | DevOps | **VACANT** | diff --git a/organization/style-guides/writing-style-guides.md b/organization/style-guides/writing-style-guides.md index 3ec45e6..229f979 100644 --- a/organization/style-guides/writing-style-guides.md +++ b/organization/style-guides/writing-style-guides.md @@ -1,6 +1,6 @@ # Writing Style Guides -## Punctuation +## Punctuation ### Case @@ -12,34 +12,31 @@ Use sentence case for titles, headings, labels, menu items, and buttons. Use tit Always capitalize the first word in bulleted lists. This includes sentences that complete an introductory stem. +| Do | Don’t | +| :--- | :--- | + + - - - - - - - - -
DoDon’t
+

This is an introductory stem:

  • Completed by this capitalized sentence.
  • Also completed by this capitalized sentence.
- -
+ +

This is an introductory stem:

  • completed by this uncapitalized sentence.
  • also completed by this uncapitalized sentence.
- +
### Periods - -A period signals to a speaker or reader that a sentence has come to an end, and it assists users in visually breaking up content. Follow these guidelines: + + +A period signals to a speaker or reader that a sentence has come to an end, and it assists users in visually breaking up content. Follow these guidelines: Place a period after a link that is followed by a sentence. @@ -55,113 +52,101 @@ Place periods after sentences that follow a link. Use a period after every bullet point that is a sentence. +| Do | Don’t | +| :--- | :--- | + + - - - - - - - - -
DoDon’t
+
  • This is a complete sentence.
  • This is also a complete sentence.
- -
+ +
  • This is a complete sentence, it needs a period
  • This is also a complete sentence, it also needs a period
- +
Use a period after every bullet point that completes the introductory stem. + + +| Do | Don’t | +| :--- | :--- | + - - - - - - - - -
DoDon’t
+

This is an introductory stem:

  • Completed by this sentence.
  • Also completed by this sentence.
- -
+ +

This is an introductory stem:

  • Completed by this sentence
  • Also completed by this sentence
- +
Use no punctuation after bullets that are not sentences and do not complete the stem. + + +| Do | Don’t | +| :--- | :--- | + - - - - - - - - -
DoDon’t
+

These are just words in a list:

  • One item
  • Two item
- -
+ +

These are just words in a list:

  • One item.
  • Two item.
- +
Use all sentences or all fragments in a bulleted list, not a mixture. + + +| Do | Don’t | +| :--- | :--- | + - - - - - - - - -
DoDon’t
+
  • Consistency is key here.
  • Item.
  • Don’t mix sentences and individual items in a list.
- -
+ +
  • Consistency is key here.
  • Item
  • Don’t mix sentences and individual items in a list.
- +
### Contractions - -We encourage the use of contractions to make writing simpler and easier to read. However, don’t make a sentence harder to understand just to follow this rule. For example, “do not” can give more emphasis than “don’t,” when needed. + + +We encourage the use of contractions to make writing simpler and easier to read. However, don’t make a sentence harder to understand just to follow this rule. For example, “do not” can give more emphasis than “don’t,” when needed. | Do | Don’t | | :--- | :--- | @@ -196,15 +181,13 @@ Use punctuation to add clarity or be grammatically correct. | Hyphen | **-** | | Use to represent negative numbers, or to avoid ambiguity in adjective-noun or noun-participle pairs. Example: “anti-inflammatory”; “5-mile walk.” Omit in commonly understood terms and adverbs that end in _ly_: “frontend”, “greatly improved performance.” Omit in the term “open source.” | | Parentheses | **\( \)** | | Use only to define acronyms or jargon: “Secure web connections are based on a technology called SSL \(the secure sockets layer\).” Avoid other uses, and instead rewrite the text or use dashes or commas to set off the information. If parentheses are required: If the parenthetical is a complete, independent sentence, place the period inside the parentheses; if not, the period goes outside. | - - ## Voice and tone Copy and messaging are meaningful aspects of the GitLab experience and the conversation with our users. The copy for GitLab is clear and direct. We strike a balance between professional and friendly. We can empathize with users \(such as celebrating completing all items on the To-Do List\) while remaining respectful to the importance of their work. We are a trusted, friendly, helpful, and understanding coworker. -### Active voice +### Active voice Whenever possible, write in [active voice](https://www.grammarly.com/blog/active-vs-passive-voice/), instead of passive voice. Active voice is easier for users to understand and often results in shorter content. @@ -215,7 +198,7 @@ Sometimes, using passive voice is appropriate. Make sure it’s an intentional c | **\(Active voice\)** Ask someone with write access to this repository to merge this request. | This request can be merged by someone with write access to this repository. | | **\(Passive voice\)** The Kubernetes cluster is being created on Google Kubernetes Engine. | We are creating the Kubernetes cluster on Google Kubernetes Engine. | -### Brevity +### Brevity Users will skim content, rather than read text carefully. Copy should be concise and short whenever possible. A long message or label is a red flag hinting at a design that needs improvement. @@ -237,7 +220,7 @@ For each of these content types, look for ways you might rephrase text that seem | To link Sentry to GitLab, enter your Sentry URL and Auth Token. | In order to link Sentry to GitLab, enter your Sentry URL and Auth Token. | | Use this token to validate received payloads. | Use this token to validate the received payloads. | -#### Avoid Latin abbreviations +#### Avoid Latin abbreviations While we aim to brief, we also avoid Latin abbreviations as they can be easily misinterpreted. @@ -245,7 +228,7 @@ While we aim to brief, we also avoid Latin abbreviations as they can be easily m * Instead of “e.g.”, use “for example.” * Instead of “etc.”, either use “and so on” or consider editing it out, since it can be vague. -### Clear error messages +### Clear error messages When something goes wrong, it’s important for us to be clear about what happened, why it happened, and what the next steps to take may be. Vague messages frustrate users and can even block them from completing their task. @@ -256,47 +239,44 @@ When writing an error message, leave out extraneous words like _sorry_ and _plea | Unable to complete your request. Enter a valid email address. | 400 Bad Request | | Enter your email address to sign up with GitLab. | Please enter your email address to sign up with GitLab. | -### Parallelism +### Parallelism [Parallel structure](https://writingcenter.gmu.edu/guides/parallel-structure) ensures that related content takes the same grammatical form; for example, all related items in a list are either a noun or a verb, not a mixture of both. Maintaining parallelism is important, because it’s grammatically correct and much easier to read. +| Do | Don’t | +| :--- | :--- | + + - - - - - - - - -
DoDon’t
+

A project is where you:

  • House your files
  • Plan your work
  • Publish your documentation
- -
+ +

A project is where you:

  • House your files
  • Plan your work
  • Publishing your documentation
- +
### Objective focused - -When users engage with our product, they’re focused on getting tasks done, thinking first in terms of the problem they’re trying to solve, and then how to solve it. Objective-focused content that starts with the task first and then offers the solution can make it easier for users to quickly find and understand the information they need. + + +When users engage with our product, they’re focused on getting tasks done, thinking first in terms of the problem they’re trying to solve, and then how to solve it. Objective-focused content that starts with the task first and then offers the solution can make it easier for users to quickly find and understand the information they need. | Do | Don’t | | :--- | :--- | | Monitor your errors by integrating with Sentry | Integrate with Sentry to monitor your errors | | To see what’s changed, choose a branch or enter a commit. | Choose a branch or enter a commit to see what’s changed. | -### Point of view +### Point of view In most cases, it’s appropriate to use the [second-person](https://www.quickanddirtytips.com/education/grammar/first-second-and-third-person?page=1) point of view, because it’s friendly and easy to understand. @@ -308,9 +288,9 @@ To write in second person, focus on eliminating words like “can” or “will | :--- | :--- | | To get started, link this page to your Jaeger server. | Users can get started by linking this page to their Jaeger server. | -### Verb tenses +### Verb tenses -#### Recent past \(instant feedback\) +#### Recent past \(instant feedback\) For a status update on something that has just happened in response to a user action or when a user is otherwise watching for an update, use the **present perfect** tense. This is ideal for toast messages and terminal output. @@ -319,7 +299,7 @@ There are two options: * When brevity is the priority, use only the noun and verb \(omitting articles and prepositions\); for example, “Pipeline scheduled.” * When you want to use a full phrase for a human feel, use a complete sentence; for example, “The pipeline has been scheduled.” -#### Distant past \(earlier than instant feedback\) +#### Distant past \(earlier than instant feedback\) Use **past tense**. @@ -327,7 +307,7 @@ Use **past tense**. | :--- | :--- | | The pipeline was last run on October 3. | The pipeline has been run on October 3. | -#### State +#### State Use **present tense**. @@ -335,7 +315,7 @@ Use **present tense**. | :--- | :--- | | The pipeline is scheduled to run on October 3. | The pipeline will be run on October 3. | -#### Instructions +#### Instructions Use the **present tense** with an imperative form \(also known as a command\). diff --git a/organization/values/inclusion-and-diversity/README.md b/organization/values/inclusion-and-diversity/README.md index ad74330..cbe1a24 100644 --- a/organization/values/inclusion-and-diversity/README.md +++ b/organization/values/inclusion-and-diversity/README.md @@ -6,5 +6,3 @@ description: Promoting Diversity and Inclusion at Bit Project {% page-ref page="guide-to-inclusive-language.md" %} - - diff --git a/organization/values/inclusion-and-diversity/guide-to-inclusive-language.md b/organization/values/inclusion-and-diversity/guide-to-inclusive-language.md index 8f6a044..a7abc18 100644 --- a/organization/values/inclusion-and-diversity/guide-to-inclusive-language.md +++ b/organization/values/inclusion-and-diversity/guide-to-inclusive-language.md @@ -18,7 +18,7 @@ As my teammate, [Niel](https://twitter.com/nieldlr) shared with me, “Communica If that spirit of self-improvement resonates with you, perhaps this inclusive language guide for startups/tech will help. And if you can think of any words, phrases or examples we didn’t cover here, please share in the comments! -### 6 overall inclusive language principles +## 6 overall inclusive language principles It’s not always necessary to fret over every word. A few big principles can take you quite far. Here a 6 that many folks involved with diversity and inclusion recommend. @@ -35,7 +35,7 @@ It’s not always necessary to fret over every word. A few big principles can ta * **If you aren’t sure, ask.** Strive to include language that reflects peoples’ choice and style in how they talk about themselves. -### 37 key phrases for talking about diversity and inclusion in tech +## 37 key phrases for talking about diversity and inclusion in tech Our quest to be as inclusive as possible means that quite a few new vocabulary words might pop up from time to time as we learn from each other. Here are some words that can offer a greater entry point into the inclusion conversation. @@ -134,7 +134,7 @@ _Example:_ [_http://confcodeofconduct.com/_](http://confcodeofconduct.com/) **Underrepresented group/underindexed group:** This terms describes any subset of a population that holds a smaller percentage within a significant subgroup than it holds in the general population. Women are often an underrepresented group in science, technology, engineering, and mathematics, for example. -### 18 phrases it might be better to avoid +## 18 phrases it might be better to avoid As language evolves and our understanding and empathy increases, it’s often a good practice to dive deeper into specific word choice. Some of these words and phrases are benign, while many carry a fraught history or connotation. In all cases, there’s likely a better and more specific option \(we’ve tried to provide alternatives!\) @@ -157,7 +157,7 @@ As language evolves and our understanding and empathy increases, it’s often a * **Open the kimono:** Problematic business jargon for disclosing information about the workings of a company. It has [sexist and racist overtones](http://www.npr.org/sections/codeswitch/2014/11/02/360479744/why-corporate-executives-talk-about-opening-their-kimonos). * **Peanut gallery:** This term for heckling or unwanted disturbance originates in the 1920s when the peanut gallery referred to the back section of theaters, which were the only places that people of color were allowed to sit at the time. The phrase was [meant to poke fun](https://www.youtube.com/watch?v=QhENGl3XviM) at the idea of people of color engaging in intellectualism. -### Plus 8 quick language substitutions +## Plus 8 quick language substitutions Some habits are hard to break! If you’re anything like us, you’ve tried to change a language pattern and fallen back into old habits at least a few times. Here are some quick language substitutions for common situations that might help: @@ -187,7 +187,7 @@ _More inclusive:_ Marginalized groups or underrepresented groups _Less inclusive:_ [Minorities](https://twitter.com/betterallies/status/869642678337536000) \(Not all marginalized groups are minorities, and a broader term is generally inclusive of more than race and gender\) -### A special note on the generic “he” in tech +## A special note on the generic “he” in tech Particularly in tech conversations and job descriptions, sometimes the pronoun “he” is used to describe technical roles or executive roles by default. Here’s an [example from an old job listing at Buffer](https://open.buffer.com/diversity-mistakes/): @@ -210,7 +210,7 @@ For more information on gender neutral job descriptions, including more lists li [![](https://open.buffer.com/wp-content/uploads/2017/06/original.jpg)](https://d2mxuefqeaa7sj.cloudfront.net/s_C401446AA445AEE117575D0B1AC31E4D67258C7E9A7C8716D486FA2D59E0D958_1496340284573_pronouns.jpg) -### Over to you! +## Over to you! This guide is definitely imperfect, but with your help it can become more useful! What words did we miss? What definitions here don’t feel quite correct to you? Share any thoughts in the comments and I’ll do my best to keep the post up-to-date for anyone who might want to reference it. diff --git a/teams/developer-relations/guide-to-being-a-manager/README.md b/teams/developer-relations/guide-to-being-a-manager/README.md index f8aca27..e27c717 100644 --- a/teams/developer-relations/guide-to-being-a-manager/README.md +++ b/teams/developer-relations/guide-to-being-a-manager/README.md @@ -1,5 +1,7 @@ # Guide to Being a Manager +**Italics indicate sections that still should be reviewed.** + Reviewers are in charge of **curriculum teams.** Each team consists of 4-6 people who work on different modules of curriculum. They will be tasked with a project, usually covering a topic, and a deadline. By this deadline, all activities, labs and workshops for that project should be completed. ## Starting Off: Receiving Module Assignments @@ -29,6 +31,54 @@ All reviewers will be assigned an issue in the **bitproject** repository, to be This checklist will be posted within the issue and should all be completed within 3 days of assignment. +### Pre-approval: What To Do + +* [ ] For each module,create a document that outlines the planned curriculum\(make sure to format it properly and according to the example\) + * [ ] Make sure learning objectives are written and formatted properly + * [ ] Make sure activity titles and descriptions written and formatted properly + * [ ] Make sure lab titles and descriptions written and formatted properly + +## _Module Assignments Documentation \[Ismail\]_ + +### Role of Epics + Assigning Epic Points + +Epics represent long-term \(in the form of GitHub issues\) that will keep you on track to finish weekly assignment,activities & labs, and entire modules. These epics should be assigned points not based on how long they will take to complete but the overall, implementation based difficulty. Activity,Lab ,and workshop epics are assigned different points and they add up to represent the total weight/points of an entire module. + +### Explanation of Role of Issues \(curriculum issues\) + +Issues are assigned weekly to developers and represent a week's work that will help you reach your epics. These issues should help you push yourself further down your Epics. They should be succinct enough\(and must also follow the given format on GitHub\) for developers to understand but not get overwhelmed by too many details or work. + +### Explanation of Role of Milestones + +Milestones represent a person's and a team's weekly goals. They are comprised of curriculum issues and represent how much progress a team or person has made during a week. They will help you keep track of everyone's weekly work quota and your own work. + +### Adding Issues to Epics \(Modules + Activities + Labs\) + +Issues\(GitHub\) should be added to Epics. On a higher level, they represent what things need to be down in order to take down an Epic and will help you breakdown your goals into more tangible ideas and tasks. Module,activities, and lab Epics will be given smaller issues that break them into more ,as previously stated, bit-sized chunks that you can further break down into weekly issues and Milestones. + +### Long-term Plan + +A long-term plan should be clear for not only yourself but outsiders who might view it as well. It should follow a set format\(as shown below\) and should outline both major points that need to worked on and the time frame on when these issues will be dealt with. It should be realistic and extra care should be taken into considering that deadlines that you set might need to be adjusted\(so give yourself some "wiggle room"\) + +`Overview of things to do:` + +* `Create section on Python Class and other OOP concepts` +* `...` +* `Recycle older tutorials into new sections for the current module` +* `Add more descriptive visuals to currently-made activities` + +`Weekly Goals:` + +`Week of April 23th: Start outlining foundation cards` + +`Week of April 30th: Start recycling older cards for the new Python tutorial module` + +`...` + +### ZenHub Calender + +You should use ZenHub as a visual deadline guide and reminder. You will create Epics that will represent blocks on ZenHub. You will then adjust their size according to their perceived start date and deadline. You will also create sub-epics\(i.e activity,workshop labs, etc.\) that will also have their own deadlines\(that will build up the main module epic\). + ## Weekly Manager Checklist * [ ] Review developers' work and provide a review according to the Pull Request Checklist @@ -41,12 +91,79 @@ This checklist will be posted within the issue and should all be completed withi * [ ] Adjust long-term plan and epic points for each module epic based on feedback and progress * [ ] Ensure General Review Checklist is being updated based on the developers' progress * [ ] Adjust timeline in Zenhub Calendar +* [ ] Weekly Team Sync +* [ ] 1:1s with devs + +## _Weekly Manager Checklist Documentation \[Owen\]_‌ + +### Deadlines: + +Friday: Friday deadlines are the fist draft deadlines for your team. This means that your team members should have finished their issues and submitted a pull request\* to your branch for review. You should take Saturday to work on any problems that come up after review. + +Sunday: Sunday deadlines are the final draft deadlines for you team. This means that you should submit a pull request\* to master with your team's completed work for the week. There will also be a form that documents your team's work for the week that is due. + +Monday: Monday deadlines are for the issues that need to assigned to your team. + +_**\*Both Friday and Sunday Pull Requests should follow the given Pull Request template in GitHub found below**_ + +**Don't forget a stage label and to set a reviewer and assignee to your reviewer. \(please remove this line before starting your PR\)** + +**Issues Closed** + +_Please make one new line for each issue, otherwise not all issues will be accounted for!_ + +Closes \#xxx + +Closes \#xxx + +Closes \#xxx + +... + +Changes proposed in this pull request: + +* Bullet point summary + +@reviewer/kavuong + +Here is and example of a completed Pull Request: + +![](../../../.gitbook/assets/screen-shot-2020-04-04-at-3.20.28-pm.png) + +### Issues: + +Issues are unresolved problems that developers need to address. As a manager, it is your job to raise issues for your developers and assign them each week. You should make sure that there are enough issues each week to be worked on, raising issues as you review your developer's work as well as in line for your long-term goals.‌ + +There are also other issues that should be raised and given as first-timer issues. These issues are generally less complicated resource wise compared to other issues. This does not mean that they are less difficult content wise. Managers should raise two of these first-timer issues a week. These issues carry over to the next week if no one joins the team. The first-timer issues are for the new people to a team filling in vacancies. + +An example of a first timer issue would be something like: + +_Give a description and explanation of why and what a cursor is and why we need a class for it._ + +All issues addressed should fully address the long-term plans set up! + +### Milestones: + +Milestones are used to organize your weekly team's weekly tasks. Issues are placed into your milestones to keep track of your team's work for the week. To create a milestone go to the issues tab in GitHub and there should be a milestones button to the left of the new issue button. Here you can create new milestones as assign tasks to your milestones. In addition your milestones should follow the naming convention of your team-week of- Monday of week. To assign issues to milestones, one can either go to the issue and assign it to a milestone on the right-hand side of of the issue or click on the milestone and search for issues to add from there. + +Here is an example of a milestones: + +![](../../../.gitbook/assets/screen-shot-2020-04-04-at-3.23.56-pm.png) + +### Adjustments: + +After all your weekly tasks are completed, assess your long-term plan and make any changes necessary. If a part of your activity is completed, assign the appropriate epic points. If there was not as much progress as originally thought, modify the long-term deadlines. Adjust overall long-term plan according to the week's progress and any feedback from developers.‌ + +### Github Projects: + +Github Projects are another source of organization for your long-term plans. You can use them to group issues of your long-term plan for a module and track the progress of completion. You should have you Github Projects set up like a kanban board where there are columns for projects todo, blocked, in progress, and done. Create each column click the add column button. Then fill the column with the cards representing the modules your team is working on with each card having checkboxes of what needs to be accomplished. To keep your kanban board updated with your team's progress you just check off your checklist and drag and drop the cards to their appropriate columns. All of the issues that a manager is responsible for ultimately doing \(short-term and long-term\) and the status of these issues should be kept track in here. ## Pull Request Checklist Every week, there are a couple essential things that every manager should take care in pull requests. This checklist applies to both pull requests from developers' branches to managers' branches and from managers' branches to `master`. * [ ] **Branch updated from `master`** + * [ ] Resolving all Merge Conflicts * [ ] Spelling and grammar errors fixed * [ ] Correct Markdown Formatting * [ ] Adjust timeline in Zenhub Calendar @@ -68,6 +185,46 @@ Every week, there are a couple essential things that every manager should take c This checklist should be pasted into each review, and checked off completely by Sunday. +## _Weekly Code Review Documentation \[Michelle\]_ + +Performing code reviews is an incredibly important step, and this function has to be done for every pull request for each of the developers every week. To start you dev should have requested a review from you. If not, please gently remind them or just request yourself. Then you should see a geen "leave a review" button and pressing that will lead you to a page displaying the code differences. You should leave comments on the code that you are viewing with specific things that they can improve on in their nect iteration. + +These specific changes should all contribute one way or another to the "Pull Request Checklist" as shown above. This checklist has to be pasted into each pull request. When reviewing, it is important to focus on both the "macro" and the "micro" issues that need to be resolved. This check list helps reviewers raise issues and review in a more efficient manner. + +Stemming from an effort to be more transparent and let developers be aware of how their work contributes to the organization as a whole, this list both ensures proper workflow and a more stylistically workflow. As more and more of the list is checked off, the developer is able to see their progress. Ideally, the list for a specific PR is completely checked off by the end of the week. + +## _Quality Assurance Procedures for Managers and Developers \[Jason\]_ + +We want the developers and the managers to provide their input for each aspect of our projects. Therefore, we need procedures that allow the developers and managers to quickly and effectively work together to complete tasks while maintaining a standard of quality. + +All developer work will be assessed with code reviews through Github. When conducting code reviews, managers will check all issues assigned to the developer to ensure that all necessary changes requested in the issues are addressed. The developer should use the issues as a guideline when reviewing the work of their developers, but should also check that the changes proposed by the developers fit the activity as a whole. + +Every time developers make Pull Requests, in the description, they must provide a list of check boxes that condense the issues they addressed in their Pull Request. The manager must be able to check off each box in the lists to ensure the quality of the developers' work. + +Each of the check boxes must be addressed with a comment from the code reviewer. The comment can acknowledge the quality of the work or give constructive feedback to the developers. + +Example of constructive feedback: + +* The explanation of binary heaps is unclear. Organize the explanation in steps and provide a visual to help the students’ understanding of the concept. + +Example of unproductive feedback: + +* I don’t like the way you explained binary heaps. + +## _Revision by Head of Developer Relations and President \[Jeff\]_ + +Here at Bit, we place heavy emphasis that all content and material developed by Bit is up to our standards. In addition to material being reviewed by respective managers, the material will undergo further review by the Head of Developer Relations, as well as the President of Bit Project. We have many developer teams at Bit and this process is necessary to ensure all material is synchronous and consistent. + +The Head of Developer Relations will occasionally audit a random Pull request from a developer to a manager and ensure proper feedback is being provided. While the Head is auditing, he will be looking to ensure the content matches Bit Project's long term goals and is consistent with the other material. He will refer to the pull request template mentioned above while performing his audit. This means ensuring all content fulfills the criteria specified by the pull request template which will result in more thorough content. + +The president, will also occasionally audit the Head of Developer Relation's pull requests to ensure quality is consistent through all curriculum by Bit Project. It will conducted in a similiar process to Code Reviews performed by managers and the Head of Developer Relations. + +In order for curriculum to have a level of quality expected of Bit Project, we have implemented 3 checks. + +1. Approval by Manager +2. Approval by Head of Developer Relations +3. Approval by President of Bit Project + ## General Development Review Checklist The following checklist must be fully completed before an Epic deadline, and also serve as a general guide to development. @@ -158,5 +315,3 @@ With regards to this checklist, reviewers should do the following: * Activities: Predetermined amounts * [ ] Have curriculum proofread by writing team \(currently Victoria Xu @vkxu657\) - - diff --git a/teams/developer-relations/guide-to-being-a-manager/raising-issues.md b/teams/developer-relations/guide-to-being-a-manager/raising-issues.md index d116787..e2cb92e 100644 --- a/teams/developer-relations/guide-to-being-a-manager/raising-issues.md +++ b/teams/developer-relations/guide-to-being-a-manager/raising-issues.md @@ -6,7 +6,7 @@ description: Reflexive clauses are your friends ## **Content** -It is each individual's job to make sure that their own code snippets are formatted and commented correctly—this is in terms of the functionality of the code. If the code works, but the spacing is off, this must be fixed by the developer themselves most likely during their second revision, but **before** merging. +It is each individual's job to make sure that their own code snippets are formatted and commented correctly—this is in terms of the functionality of the code. If the code works, but the spacing is off, this must be fixed by the developer themselves most likely during their second revision, but **before** merging. 1. [ ] The code is functional and devoid of runtime errors * [ ] If you can think of a case where the code fails, this must be addressed @@ -20,7 +20,7 @@ It is each individual's job to make sure that their own code snippets are format * [ ] Semantically named variables * [ ] Comments are preceded by a space. Ex: `// this is a correct comment` * [ ] Spaces between operators. Ex: `snake = 'Voldemort'` - * [ ] Not `snake='Voldemort'`, `snake ='Voldemort'`, or `snake= 'Voldemort'` + * [ ] Not `snake='Voldemort'`, `snake ='Voldemort'`, or `snake= 'Voldemort'` * [ ] Has proper language selected so that there is helpful highlighting ## **Context** @@ -41,8 +41,8 @@ It is each individual's job to make sure that their own code snippets are format * [ ] Pass by reference or pass by value * [ ] Returns * [ ] \(Base\) Cases - * [ ] Explain the condition - * [ ] Explain the return + * [ ] Explain the condition + * [ ] Explain the return * [ ] Mention how we are going to return the correct value—switch cases, if else statements, recursion, etc #### Methods \(body\) @@ -56,7 +56,7 @@ It is each individual's job to make sure that their own code snippets are format * [ ] Use technical terms when possible * [ ] The **first instances** of these in each lab/activity are bolded and followed by a reminder or an explanation - * [ ] **Reflexive clauses** are your friends + * [ ] **Reflexive clauses** are your friends * [ ] If you use non technical terms \(ex: left or right\), please have them be accompanied by **more** technical terms \(ex: less than, greater than\) * [ ] Be careful that your tone does not become too dry—we still want to sound personable and engaging * [ ] Adding more adjectives and adverbs do not make your explanations more clear. Just because an explanation is prefaced by "simply" or any other similar word, it does not mean that the explanation is that. diff --git a/teams/developer-relations/joining-the-core-team.md b/teams/developer-relations/joining-the-core-team.md index 0ae31af..fe26c3e 100644 --- a/teams/developer-relations/joining-the-core-team.md +++ b/teams/developer-relations/joining-the-core-team.md @@ -6,17 +6,17 @@ description: The process of joining the core team. ## Introduction -In our efforts to go remote, we have established a very streamlined recruitment process for students to join our cause. Students from all over will be able to join as the onboarding process no longer requires an in-person meeting. It will utilize the following applications heavily: Zoom and GitHub. +In our efforts to go remote, we have established a very streamlined recruitment process for students to join our cause. Students from all over will be able to join as the onboarding process no longer requires an in-person meeting. It will utilize the following applications heavily: Zoom and GitHub. -This process involves multiple people: the applicant\(s\), managers, mentors, and more. It is expected to last about two weeks to ensure that you are smoothly integrated into one of the developer relations teams. The following list below is our breakdown of the onboarding process, assigning various tasks to certain individuals on specified dates. +This process involves multiple people: the applicant\(s\), managers, mentors, and more. It is expected to last about two weeks to ensure that you are smoothly integrated into one of the developer relations teams. The following list below is our breakdown of the onboarding process, assigning various tasks to certain individuals on specified dates. ## Contributor Onboarding Checklist -Contributor Name: +Contributor Name: -Manager Name: +Manager Name: -Mentor Name: +Mentor Name: ### Pre-Interview Tasks: @@ -130,31 +130,31 @@ Cover topics within next two weeks to ensure that the contributor is onboarded p ## Checklist Breakdown -### Pre-Interview Tasks: +### Pre-Interview Tasks: -These are tasks for the manager in charge of onboarding. They are required to contact the applicant\(s\) through email once the applications are received. A zoom link is sent to them with a time and date for the Welcome Webinar. The manager is also in charge of notifying the president of Bit Project, and the applicants' prospective manager and mentor. +These are tasks for the manager in charge of onboarding. They are required to contact the applicant\(s\) through email once the applications are received. A zoom link is sent to them with a time and date for the Welcome Webinar. The manager is also in charge of notifying the president of Bit Project, and the applicants' prospective manager and mentor. ### Manager Tasks: -The manager is essentially the team leader of the applicant's potential team. They are in charge of making sure that you are caught up to speed with their current work and have a strong foundational understanding of the general curriculum. +The manager is essentially the team leader of the applicant's potential team. They are in charge of making sure that you are caught up to speed with their current work and have a strong foundational understanding of the general curriculum. #### Day 1: -The manager would first confirm that all applicants are on Slack as Slack is our main form of communication. Having everyone on one platform that has multiple communication accessories make the remote process much simpler for everyone. +The manager would first confirm that all applicants are on Slack as Slack is our main form of communication. Having everyone on one platform that has multiple communication accessories make the remote process much simpler for everyone. -An introduction is necessary so applicants are aware of who is the person they should turn to. The manager would send a greeting to the applicants, providing the following information: name, team name, position, ways to contact the manager, and the mentor. The mentor is a member of the team that is familiar with working with the manager and is comfortable with the work given. Applicants can contact the mentor whenever they are struggling and are in need of help. Mentors are essentially another source of reference that is available. +An introduction is necessary so applicants are aware of who is the person they should turn to. The manager would send a greeting to the applicants, providing the following information: name, team name, position, ways to contact the manager, and the mentor. The mentor is a member of the team that is familiar with working with the manager and is comfortable with the work given. Applicants can contact the mentor whenever they are struggling and are in need of help. Mentors are essentially another source of reference that is available. -An info session will be scheduled. For now, this will be administered by another member of Bit Project until managers get settled with the new onboarding process. A more detailed explanation of the info session is provided in the Contributor Task Breakdown. +An info session will be scheduled. For now, this will be administered by another member of Bit Project until managers get settled with the new onboarding process. A more detailed explanation of the info session is provided in the Contributor Task Breakdown. -Managers will assign the member a first-timer task after the info session. These tasks vary based off of each individual team's current project. It is catered towards the project's focus. +Managers will assign the member a first-timer task after the info session. These tasks vary based off of each individual team's current project. It is catered towards the project's focus. #### Day 2-5: -Throughout these few days, the manager and mentor will be helping contributors with their first-timer task whenever needed. They would review the task once it is officially submitted and take note of any major or minor mistakes. If there are major issues, these will be communicated through Slack soon after the task is submitted. It is best to review these as soon as possible to avoid the same mistakes from reoccurring in the future. +Throughout these few days, the manager and mentor will be helping contributors with their first-timer task whenever needed. They would review the task once it is officially submitted and take note of any major or minor mistakes. If there are major issues, these will be communicated through Slack soon after the task is submitted. It is best to review these as soon as possible to avoid the same mistakes from reoccurring in the future. #### Day 6: -The manager should confirm the 1:1 meeting with each applicant. This should happen before Day 14 \(the end of the onboarding process\). +The manager should confirm the 1:1 meeting with each applicant. This should happen before Day 14 \(the end of the onboarding process\). #### Day 7-14: @@ -164,50 +164,50 @@ During the scheduled one-on-one above, it will consist of a team introduction an #### Day 0 \(Thursday\): -Applicants are contacted via email and are invited to attend the welcome webinar. A zoom link will already be provided within the email with a set date and time. It is important to notify us whether or not you are able to attend by responding to the email with a confirmation of attendance. +Applicants are contacted via email and are invited to attend the welcome webinar. A zoom link will already be provided within the email with a set date and time. It is important to notify us whether or not you are able to attend by responding to the email with a confirmation of attendance. -During the welcome webinar, the president of Bit Project will present to you an introduction to Bit Project and the various teams \(developer relations, engineering, people, and marketing\). Then the next step of the process is introduced where every applicant is required to join slack and create a GitHub account. Managers and mentors will give a brief introduction about themselves and welcome the applicants. +During the welcome webinar, the president of Bit Project will present to you an introduction to Bit Project and the various teams \(developer relations, engineering, people, and marketing\). Then the next step of the process is introduced where every applicant is required to join slack and create a GitHub account. Managers and mentors will give a brief introduction about themselves and welcome the applicants. -The info session time for the next day will be scheduled at the end of the webinar. +The info session time for the next day will be scheduled at the end of the webinar. #### Day 1 \(Friday\): On this day, applicants will attend the info session. The info session will cover the following listed topics: general breakdown of the week, onboarding presentation, introduction to the team, task explanations, GitHub/GitHub desktop set-up, activities/lab introduction, complete slack set-up, and first-timer task. -The breakdown just goes over what to expect in the upcoming week with meeting the team, new tasks, and one-on-one meetings. +The breakdown just goes over what to expect in the upcoming week with meeting the team, new tasks, and one-on-one meetings. -The onboarding presentation will provide a brief introduction to Bit Project \(as the Welcome Webinar should have already presented this information\), GitHub & GitHub desktop tutorial, introduction to what exactly our curriculum entails with activities and labs. +The onboarding presentation will provide a brief introduction to Bit Project \(as the Welcome Webinar should have already presented this information\), GitHub & GitHub desktop tutorial, introduction to what exactly our curriculum entails with activities and labs. -Towards the end of this info session, the managers will double check that the applicants are all on slack and the team manager will provide the applicants with their first-timer task. This first-timer task is meant to introduce each applicant to the team's project, giving them an insight to how the work of a developer on this specific team. Applicants are able to refer to their mentor and team manager for help in this process. +Towards the end of this info session, the managers will double check that the applicants are all on slack and the team manager will provide the applicants with their first-timer task. This first-timer task is meant to introduce each applicant to the team's project, giving them an insight to how the work of a developer on this specific team. Applicants are able to refer to their mentor and team manager for help in this process. #### Day 2-3: \(Saturday - Sunday\) -Throughout the weekend, applicants are expected to finish their first-timer task and become familiar with the use and format of issues on GitHub. Once the task is complete, the applicant will wait for their manager / reviewer to review their work. +Throughout the weekend, applicants are expected to finish their first-timer task and become familiar with the use and format of issues on GitHub. Once the task is complete, the applicant will wait for their manager / reviewer to review their work. Applicants are expected to watch the provided webinars that discuss important aspects and values of Bit Project. \(Communication, culture, etc.\) #### Day 4 \(Monday\): -On Slack, every team manager should have a Calendly already set-up. Schedule a one-on-one meeting with your team manager. +On Slack, every team manager should have a Calendly already set-up. Schedule a one-on-one meeting with your team manager. * [ ] Schedule meeting with Manager * Schedule a 1:1 meeting through Calendly for Day 8-9 #### Day 5 \(Tuesday\): -On this day, applicants should focus more on the breakdown and specifics of labs and activities. +On this day, applicants should focus more on the breakdown and specifics of labs and activities. -During the one-on-one, the applicant will give the manager feedback on their activity / lab experience if the applicant is given one. +During the one-on-one, the applicant will give the manager feedback on their activity / lab experience if the applicant is given one. -Applicants are to send a greeting message into Slack, notifying their team of who they are. +Applicants are to send a greeting message into Slack, notifying their team of who they are. #### Day 8-12: -Within these days, the applicant should be meeting with their team manager. The applicant will be taught how to take meeting notes with GitHub, and will practice taking notes throughout or after the meeting. +Within these days, the applicant should be meeting with their team manager. The applicant will be taught how to take meeting notes with GitHub, and will practice taking notes throughout or after the meeting. -They will discuss the onboarding task and the manager will provide feedback. The contributor will then provide feedback on the labs and activities process \(if it is given\). Then the applicant will schedule a one-on-one with a member of onboarding. The link will be provided by the team manager. +They will discuss the onboarding task and the manager will provide feedback. The contributor will then provide feedback on the labs and activities process \(if it is given\). Then the applicant will schedule a one-on-one with a member of onboarding. The link will be provided by the team manager. #### Day 12-14: -The final step of the onboarding process will be completed with a one-on-one meeting between the applicant and with onboarding. Applicant will provide feedback to onboarding about the whole process, and onboarding will ensure that the applicant is ready to be fully integrated into the Bit Project team. +The final step of the onboarding process will be completed with a one-on-one meeting between the applicant and with onboarding. Applicant will provide feedback to onboarding about the whole process, and onboarding will ensure that the applicant is ready to be fully integrated into the Bit Project team. diff --git a/teams/engineering/readme-formats.md b/teams/engineering/readme-formats.md index 21982d8..c9983f2 100644 --- a/teams/engineering/readme-formats.md +++ b/teams/engineering/readme-formats.md @@ -474,12 +474,14 @@ To include the md\_content for the step, give the md\_content with a markdown h2 ```text ### md_content ``` + ### Hello world in js + This is how you do it -``` -``` +```text +``` #### Optional Fields @@ -490,8 +492,11 @@ To include the code snippet for the step, give the code snippet with a markdown ```text ### code_snippet ``` -def pls_work(): return True... maybe -``` + +def pls\_work\(\): return True... maybe + +```text + ``` #### Image @@ -520,21 +525,20 @@ How to install VSCode ### md_content ``` -Hello world in js -This is how you do it -``` +Hello world in js This is how you do it + +```text ### code_snippet ``` -def pls_work(): return True... maybe -``` +def pls\_work\(\): return True... maybe + +```text ### image ``` - - ### Concept Format #### Concept Name \(This is required\) @@ -570,8 +574,11 @@ Under the hint name, you have to give the step a name with a markdown h2 tag. ** ```text ## name ``` + How to install VSCode -``` + +```text + ``` #### Md\_content \(You need to include this for each step\) @@ -581,12 +588,14 @@ To include the md\_content for the step, give the md\_content with a markdown h2 ```text ## md_content ``` + ## Hello world in js + This is how you do it -``` -``` +```text +``` #### Optional Fields @@ -597,8 +606,11 @@ To include the code snippet for the step, give the code snippet with a markdown ```text ## code_snippet ``` -def pls_work(): return True... maybe -``` + +def pls\_work\(\): return True... maybe + +```text + ``` #### Image @@ -625,19 +637,22 @@ Topic1/Module2_test/concepts/ ## name ``` + How to install VSCode -``` +```text ## md_content ``` -Hello world in js -This is how you do it -``` +Hello world in js This is how you do it + +```text ## code_snippet ``` -def pls_work(): return True... maybe -``` + +def pls\_work\(\): return True... maybe + +```text ## image ``` diff --git a/teams/engineering/roles/backend-developer.md b/teams/engineering/roles/backend-developer.md index 98fdd9a..4d0f00b 100644 --- a/teams/engineering/roles/backend-developer.md +++ b/teams/engineering/roles/backend-developer.md @@ -31,9 +31,3 @@ description: >- * Running code through a series of load testing to fix existing bugs to enhance the speed of enpoints * Documenting/updating endpoints on Postman - - - - - - diff --git a/teams/engineering/roles/frontend-architect.md b/teams/engineering/roles/frontend-architect.md index 196963b..9ca739f 100644 --- a/teams/engineering/roles/frontend-architect.md +++ b/teams/engineering/roles/frontend-architect.md @@ -25,5 +25,3 @@ * Collaborating with other React.js Developers and Designers to determine the structure and design of components for the LMS * Collaborating with Backend developers to determine the necessary data needed to implement components - - diff --git a/teams/engineering/roles/react.js-developer.md b/teams/engineering/roles/react.js-developer.md index 891935f..bdb6ace 100644 --- a/teams/engineering/roles/react.js-developer.md +++ b/teams/engineering/roles/react.js-developer.md @@ -30,5 +30,3 @@ description: >- * Collaborating with other React.js Developers and Designers to determine the structure and design of components for the LMS * Collaborating with Backend developers to determine the necessary data needed to implement components - - diff --git a/teams/people/README.md b/teams/people/README.md index 7821c58..2b38e48 100644 --- a/teams/people/README.md +++ b/teams/people/README.md @@ -8,9 +8,9 @@ description: >- ## What is the People Team? -The Bit Project has grown quickly, and plans to continue grow while maintaining our culture and remote working, embracing development, and building scalable people-oriented policies. Our team oversees recruiting and learning and development functions. We are responsible for investing in the engagement and development of members, as people, which first benefits the members, and as a result, the organization as a whole. The People team is about designing work so that you want to be there – present, engaged, and proud of what you do in Bit. In this team, we focus providing members proactive learning materials to make operations easier, especially in the times of change management. Moreover, we focus on on-boarding new members from around the United States. Please do not hesitate to reach out to any People members with questions! In the case of a conflict between the organization and a team member, the People Team is always here to assist you. +The Bit Project has grown quickly, and plans to continue grow while maintaining our culture and remote working, embracing development, and building scalable people-oriented policies. Our team oversees recruiting and learning and development functions. We are responsible for investing in the engagement and development of members, as people, which first benefits the members, and as a result, the organization as a whole. The People team is about designing work so that you want to be there – present, engaged, and proud of what you do in Bit. In this team, we focus providing members proactive learning materials to make operations easier, especially in the times of change management. Moreover, we focus on on-boarding new members from around the United States. Please do not hesitate to reach out to any People members with questions! In the case of a conflict between the organization and a team member, the People Team is always here to assist you. -## The Core Objectives of the People Team, Are to: +## The Core Objectives of the People Team, Are to: Shift from task-based management to objective-based management \(MBO\) – **Higher productivity, measurable performance results** @@ -28,9 +28,9 @@ Cross pollination and collaboration – **Build capable managers with fresh idea ## Our Actions and Goals -As a team, we are always trying to find new ways to improve Bit Project. We want to create a well-rounded for all members. On that notes, we decided to implement webinars for new members in our on-boarding process to allow a smoother transition. We created a training guide on how to be a successful and effective manager at Bit. Additionally, we are constantly creating learning and development guides such as communication, internal feedback, diversity and inclusion, and how to use applications like Github are all provided on this Handbook. Lastly, we try to document as much information to increase our transparency as well as provide you all the materials on how to be successful as Bit Project. +As a team, we are always trying to find new ways to improve Bit Project. We want to create a well-rounded for all members. On that notes, we decided to implement webinars for new members in our on-boarding process to allow a smoother transition. We created a training guide on how to be a successful and effective manager at Bit. Additionally, we are constantly creating learning and development guides such as communication, internal feedback, diversity and inclusion, and how to use applications like Github are all provided on this Handbook. Lastly, we try to document as much information to increase our transparency as well as provide you all the materials on how to be successful as Bit Project. -## Responsibilities +## Responsibilities * Provide an enriching experience for all members by creating materials for learning and development. * Maintain appropriate level of process, program, and policy knowledge in order to assist team members. @@ -42,5 +42,3 @@ As a team, we are always trying to find new ways to improve Bit Project. We want * Announcing changes and improvements * Engagement survey administration & implementation. - - diff --git a/teams/people/joining-the-team.md b/teams/people/joining-the-team.md index af1b159..d38f8a1 100644 --- a/teams/people/joining-the-team.md +++ b/teams/people/joining-the-team.md @@ -37,18 +37,18 @@ Once you are on slack, please complete the following tasks: * [ ] DM Becca Tran to set up a 1:1 Meeting * [ ] Send an introduction of yourself to the \#newmembers channel * include: - * Name - * Team - * Major - * Year - * Favorite Memory - * Ex: "Hi! My name is Carl from New York studying at NYU as an Economic major! I am a third year and I am so excited to work you today. I will be joining the best team which is the People Team! My favorite memory this year was going to Disneyland. Can't wait to get to know you guys more!" + * Name + * Team + * Major + * Year + * Favorite Memory + * Ex: "Hi! My name is Carl from New York studying at NYU as an Economic major! I am a third year and I am so excited to work you today. I will be joining the best team which is the People Team! My favorite memory this year was going to Disneyland. Can't wait to get to know you guys more!" ## Day 2 ### 3. 1:1 Meeting With the Manager of People -During your meeting with the Manager \(Becca Tran\), the Manager will go over what exactly the People Team is, the purpose of the team, and what the team does. The Manager will then assign you your tasks, consisting of watching a set of webinars and giving you a case on a workflow issue. This will be taken place over Zoom. +During your meeting with the Manager \(Becca Tran\), the Manager will go over what exactly the People Team is, the purpose of the team, and what the team does. The Manager will then assign you your tasks, consisting of watching a set of webinars and giving you a case on a workflow issue. This will be taken place over Zoom. ### 4. Watching Our Webinars @@ -65,13 +65,13 @@ There are three webinars that you must watch: Communication, Team Feedback, and * [ ] Google Calendar * [ ] [https://calendar.google.com/calendar?cid=dWNkYXZpcy5lZHVfMGhpZzcwNmdlMWRuZmpsMWVyc3V1YmFyaHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ](https://calendar.google.com/calendar?cid=dWNkYXZpcy5lZHVfMGhpZzcwNmdlMWRuZmpsMWVyc3V1YmFyaHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ) -You can access to this by asking for the Becca Tran if the links do not work +You can access to this by asking for the Becca Tran if the links do not work ## Day 3 -### 5. People Issue Case +### 5. People Issue Case -You will be given a scenario regarding an issue with the workflow, diversity and inclusion, internal feedback process, or onboarding. Where you would address the issue and find a solution for it in a proposal \(written\) and you will present it during the follow-up with Becca Tran. +You will be given a scenario regarding an issue with the workflow, diversity and inclusion, internal feedback process, or onboarding. Where you would address the issue and find a solution for it in a proposal \(written\) and you will present it during the follow-up with Becca Tran. * [ ] Complete the proposal before the next meeting with Becca Tran * [ ] Email the proposal to Becca Tran \(rhtran@ucdavis.edu\) diff --git a/teams/people/recruitment/general-event-volunteer-training.md b/teams/people/recruitment/general-event-volunteer-training.md index 62a4f6d..114c700 100644 --- a/teams/people/recruitment/general-event-volunteer-training.md +++ b/teams/people/recruitment/general-event-volunteer-training.md @@ -1,9 +1,6 @@ # General Event Volunteer Training - - -\*\*\*\*[**General Event Volunteer Training**](https://www.youtube.com/watch?v=QEdVY4sYBAw&feature=youtu.be) **\(Video\)** - +\*\*\*\*[**General Event Volunteer Training**](https://www.youtube.com/watch?v=QEdVY4sYBAw&feature=youtu.be) **\(Video\)** ## **Introduction** @@ -31,7 +28,7 @@ It all comes down to these three things. ## **UC Davis Rules when Working with Minors** -Since the events are organized by a UC Davis student organization, we are required to abide by certain school policies. For instance: +Since the events are organized by a UC Davis student organization, we are required to abide by certain school policies. For instance: 1. Minors will be treated with respect at all times: regardless of race, sex, age, or religion 2. Staff and volunteers must avoid showing affection with minors, not use profanity or tell jokes with innuendos that contain racist or indecent commentary. @@ -41,9 +38,9 @@ Since the events are organized by a UC Davis student organization, we are requir 1. If students need to go on bathroom breaks, contact your volunteer lead. 6. You must prohibit minors from engaging in inappropriate behavior such as hazing, bullying, -Example of a Situation: Dodging hugs. +Example of a Situation: Dodging hugs. -We expect volunteers to set an example for the students +We expect volunteers to set an example for the students ## **Method of Control** @@ -51,7 +48,7 @@ The second thing we need to introduce is a method of control. This involves an a ## **Discipline and Praise** -The third thing we need to do is establish a fair discipline system. Most teachers have this already implemented in their class and all classrooms are different. Before an activity, ask the teacher how they discipline their students. +The third thing we need to do is establish a fair discipline system. Most teachers have this already implemented in their class and all classrooms are different. Before an activity, ask the teacher how they discipline their students. Remember, in order to have effective discipline, the three expectations must be clearly communicated first. Methods of discipline may involve different signals but they are all very similar and typically involves four steps: @@ -72,12 +69,12 @@ The role of a volunteer is to help teachers and students conduct the activity. A * Don’t get carried away… Focus on helping students learn and understand various difficult concepts. If you feel there is too much information help make sure key concepts are understood! * If you feel uncomfortable with any of the concepts, check out the Learn More page at the end of each designated activity. Feel free to ask other volunteers for help. -Make sure you watch two other videos if you haven’t done so already: +Make sure you watch two other videos if you haven’t done so already: 1. Activity: This video explains the activity to be done at your event! -2. “BitCart Logistics” +2. “BitCart Logistics” -The “BitCart Logistics” will contain information on: +The “BitCart Logistics” will contain information on: * Logistics for general events * Location - transportation options diff --git a/teams/people/roles/README.md b/teams/people/roles/README.md index f53fee2..ad90f0a 100644 --- a/teams/people/roles/README.md +++ b/teams/people/roles/README.md @@ -2,5 +2,3 @@ Here are the roles within the People Team: - - diff --git a/teams/people/roles/director-of-people.md b/teams/people/roles/director-of-people.md index 0703d4b..cc09164 100644 --- a/teams/people/roles/director-of-people.md +++ b/teams/people/roles/director-of-people.md @@ -2,12 +2,10 @@ ## Description -The Director of People leads to effort to ensure that everyone in the organization is constantly updates, included, and valued. The Director will ensure that the people within the organization have full access to +The Director of People leads to effort to ensure that everyone in the organization is constantly updates, included, and valued. The Director will ensure that the people within the organization have full access to ## Responsibilities ## Requirements * - - diff --git a/teams/people/roles/diversity-and-inclusion-specialist.md b/teams/people/roles/diversity-and-inclusion-specialist.md index f99ffa3..2883b8c 100644 --- a/teams/people/roles/diversity-and-inclusion-specialist.md +++ b/teams/people/roles/diversity-and-inclusion-specialist.md @@ -6,7 +6,7 @@ Bit Project's Diversity and Inclusion Specialist is responsible for supporting t ## Responsibilities -* Provide subject matter knowledge to help design, implement and manage initiatives and programs that advances the inclusion and diversity strategy. +* Provide subject matter knowledge to help design, implement and manage initiatives and programs that advances the inclusion and diversity strategy. Analyze and interpret inclusion and diversity data/metrics specific to business lines. Confer with senior leaders to help find opportunities and develop a plan to improve metrics. @@ -24,5 +24,3 @@ Bit Project's Diversity and Inclusion Specialist is responsible for supporting t Experience in sales and/or marketing - - diff --git a/teams/people/roles/learning-and-development-manager.md b/teams/people/roles/learning-and-development-manager.md index 4d5ef45..5b34d47 100644 --- a/teams/people/roles/learning-and-development-manager.md +++ b/teams/people/roles/learning-and-development-manager.md @@ -2,7 +2,7 @@ ## Description -The Learning & Development Manager is responsible to guide members within a dynamic and fast-pace organization with the resources to succeed professionally and +The Learning & Development Manager is responsible to guide members within a dynamic and fast-pace organization with the resources to succeed professionally and ## Responsibilities @@ -15,5 +15,3 @@ The Learning & Development Manager is responsible to guide members within a dyna * Ability to work well with teams to identify needs * Strong public speaking skills \(experience with public speaking preferred\) - - diff --git a/teams/people/roles/onboarding-manager.md b/teams/people/roles/onboarding-manager.md index 516b354..50f9f2b 100644 --- a/teams/people/roles/onboarding-manager.md +++ b/teams/people/roles/onboarding-manager.md @@ -2,12 +2,6 @@ ## Description +* **Responsibilities** +* **Requirements** * -## Responsibilities - -* -## Requirements - -* - - diff --git a/teams/people/roles/people-experience-associate.md b/teams/people/roles/people-experience-associate.md index 25ffc6b..f9502b5 100644 --- a/teams/people/roles/people-experience-associate.md +++ b/teams/people/roles/people-experience-associate.md @@ -17,5 +17,3 @@ We are looking for an ambitious and self-motivate People Manager with strong lea * Strong organization and written and verbal communication skills * Strong interpersonal relationship building skills - - diff --git a/teams/people/roles/recruiter.md b/teams/people/roles/recruiter.md index 5011772..93b3520 100644 --- a/teams/people/roles/recruiter.md +++ b/teams/people/roles/recruiter.md @@ -2,12 +2,6 @@ ## Description +* **Responsibilities** +* **Requirements** * -## Responsibilities - -* -## Requirements - -* - -