Onboarding: Sourabh

### Prerequisite
- You have done the steps in this wiki page for onboarding new team members https://github.com/hackforla/guides/wiki/Joining-the-Team

### Overview
We need you to review all the user make a guide presentations so that we can get you up to speed

#### Additional Details
You will be using a guide during this issue as your pretend guide to work on, but the purpose of this issue is to understand all our guide making presentations.
- Any notes you have about the guide you will be making should be noted in the issue related to the Guide you choose.
- Any notes about the presentations should be in the document you create.

### Action Items
- [ ] Create a Google doc, with the name ```GT: Notes on whole guides process - YOUR NAME HERE``` in the Guide Creation Presentations folder (resource 1.01) and customize with your name
- [ ] Add the link to the document and its name on Resource 2.01 below
- [ ] Add to the notes document (resource 2.01) as you go, with observations about the each of the Presentations. You will encounter some issues, such as font size or other types of formatting changes, what we are looking for though is material changes to the instructions. For instance, if something could use a screenshot to make it clearer, and it doesn't have one or when you try to follow the steps, something is missing.
- [ ] If while looking at the presentations (not the guide), you encounter any words that you think should be added to our glossary, please add them to the Glossary issue (Resource 1.02) as comments.
- [x] Pick a guide using the Guide Tracker (Resource 1.03)
- Add the guide info to the resources below
- [x] Add the URL of the guide issue to Resource 2.02.01
- [x] Add name of guide to Resource 2.02.02. It should be something like "How to ..."
- [ ] Use the presentations to pretend working on the guide
- [ ] Leaving comments in the presentation if you have a suggested improvement
- [ ] Putting any notes about the guide either in the guide or in the issue for the guide (as appropriate)
- [ ] Clean up your presentation notes
- [ ] Present to the Guides Team

### Resources/Instructions
#### Links to use for this issue
- 1.01 Folder for Team notes and Guide Presentation: [Guide Creation Presentations](https://drive.google.com/drive/u/0/folders/1NW2uH2izj-g2nvL_X1ndJHu1CXgL3vdH)
- 1.02 #88
- 1.03 [Guides Tracker](https://github.com/orgs/hackforla/projects/40/views/1): Search for a guide by using this global project board. The Guides team uses this board to track progress of all the guides

#### Links you will create or gather while working on this issue
- 2.01 Your presentation notes document file:
- 2.02 Guide you are looking at
- 2.02.01 URL of guide Issue : https://github.com/hackforla/knowledgebase-content/issues/63
- 2.02.02 Name of guide: How To Create Logos and favicons

#### Presentations
1. Getting Started
- Overview of whole process
- Part 1: [What is a Guide & Picking Your First Guide](https://docs.google.com/presentation/d/1WvHkRja7McjraE-QIjMSPluEOwBbLhFletlCYnzGLb0/edit#slide=id.g150d6ff717d_1_193)
1. How to Gather Examples
- Part 1: [Gathering Examples With Github: Wiki, Issues, Project Board, Resources Provided](https://docs.google.com/presentation/d/1XWY-OMiomzpKw_aCL1JkdgAhqpgGDZ2bu_XuReTO1zw/edit#slide=id.g150e30fd48b_0_443) (WIP)
- Part 1.5: [How to Use Github Search](https://docs.google.com/presentation/d/1M2f2Q9vefNAzQ4lvcw13x-7McPbrb8NZIVFgJUrefzE/edit?usp=sharing)
- Part 2: [Gathering Examples With Slack](https://docs.google.com/presentation/d/1-Kg7yLRXsdGo4Ln8L-WiunOOO3Uc7TuXvH5afcp3AKQ/)
- Part 3: [Connecting with Other Teams & Moving the Conversation Forward](https://docs.google.com/presentation/d/15WxdSc_YFVLdytCZ-SxZaWPt8y6-OQTxJb8dcppZHVE/)
- Part 4: [Making a Special Issue + Last Check w/ Org Rep](https://docs.google.com/presentation/d/1egg1WUxIt9lz4mFXiR7OeKb6dTz-5HCxi5Ai8uEL4Ps/)
1. [How to Find a Guide that is Ready to Write a Template for](https://docs.google.com/presentation/d/10VrfFJ2fy2erkCw-7qZqRoJZqbCmV-GzLrWap1aw_iQ/edit?usp=sharing) (WIP)
1. [How to Peer Review a Guide (PM/UX CoP presentation)](https://docs.google.com/presentation/d/1srOj8VsNfIdqQK5fH2hxTrSA7JJ94APnoYoghAa09pM/edit?usp=sharing)
1. [How to Work on an Unfinished Guide (PM CoP presentation)](https://docs.google.com/presentation/d/1SEGphLSuZDkYZLtlST5oANdL_tbKepTBABzs3kxUo8U/edit?usp=sharing)
1. How to suggest a new guide:
- Check the Guide Tracker to make sure no one has started it (it could be on a different community of practice)
- Write an idea for new guides by adding a card in the New Issue Approval column of your Community of Practice Board
- Ideally the guides should be written for novices so that they are useful to all people who read them, including people from other Communities of Practice and people outside Hack for LA.

### When you do your update please provide
Instructions

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

You can use this template
```
1. Progress:
2. Blockers:
3. Availability:
4. ETA:
5. Pictures (if necessary):
```