To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. We'd like the specific information to replace those placeholder texts

📋 Step by Step
Step by Step

• 🙋 Claim this issue by commenting on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)

The change I suggest is go to the Conferences Table, starts around line 164. Edit the YOW Conferences line so that it reads:

| [YOW Conferences](https://yowconference.com/) | YOW | 10 | Emerging technologies and best practices in the software industry |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add QCon New York to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. Take a look at one of those resources and see if you can figure out a more descriptive comment to tell readers what they will get out of looking at it. Only choose one for now - to give others a chance.

Alternatively... perhaps you would like to add content to this list. Feel free to do that to, but make sure that what you suggest we add in as really useful. We don't want people to be overwhelmed with too many choices, or demotivated by content that is not accessible to beginners. Make suggestions for resources/people that you have used yourself and comes with your most heartfelt recommendation.

📋 Step by Step
Step by Step

• 🙋 Claim an issue: By commenting on it.
• Click on the Readme.MD and then click on the little pen (top right) to edit the file
• Add this line underneath the last entry in Step 4, Follow some mentors:
  | [Jessica White](https://github.com/wordshaker) |DDD East Midlands | 4 | Microsoft MVP in Developer Technologies, an international speaker and a mentor |
• Commit your change Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add SuperConf to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add Developer Week to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for Developer Week (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add Vanessa Aristizabal to the Mentors section
• See below for link to step-by-step tutorial
• Go down to Mentors section - it starts at around line 83
• Paste the following information underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Vanessa Aristizabal](https://github.com/vanessamarely) | Vanessa Aristizabal | 4 | Frontend Developer GDE in Angular & Web Technologies |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add Monica Powell to the Mentors section
• See below for link to step-by-step tutorial
• Go down to Mentors section - it starts at around line 83
• Paste the following information underneath the last row in the table, ensuring there is still an empty row before the next table.

| [M0nica](https://github.com/m0nica) | Monica Powell | 4 | Founder of React Ladies a community for React JS developers |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. We'd like the specific information to replace those placeholder texts

📋 Step by Step
Step by Step

• 🙋 Claim this issue by commenting on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)

The change I suggest is go to the Get Involved Section, starts around line 104. Edit the 100DayOfCode line so that it reads:

| [100 Days of Code](https://www.100daysofcode.com/) | Alex Kallaway | 5 | Official Website for the Challenge that gets you addicted to coding |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. We'd like the specific information to replace those placeholder texts

📋 Step by Step
Step by Step

🙋 Claim this issue by commenting on it.

• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)
• The change I suggest is go to the Conferences Table, starts around line 164. Edit the Web Directions Summit line so that it reads:

| [Web Directions Summits](https://www.webdirections.org/) | Web Directions | 10 | A conference for the whole team |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. Take a look at one of those resources and see if you can figure out a more descriptive comment to tell readers what they will get out of looking at it. Only choose one for now - to give others a chance.

Alternatively... perhaps you would like to add content to this list. Feel free to do that to, but make sure that what you suggest we add in as really useful. We don't want people to be overwhelmed with too many choices, or demotivated by content that is not accessible to beginners. Make suggestions for resources/people that you have used yourself and comes with your most heartfelt recommendation.

📋 Step by Step
Step by Step

• 🙋 Claim an issue: Comment on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)
• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
Add

📋 Step by Step

• 🙋 Claim an issue: By commenting on it.
• Click on the Readme.MD and then click on the little pen (top right) to edit the file
• Add this line underneath the last entry in Step 10, Conferences ensuring there remains a new line/space after the step 10 table:

`| Signal Conf | Twilio | 10 | Twilio’s Annual Customer & Developer Conference |'

• Commit your change Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Comment on Issue or Pull Request, asking @all-contributors to add a contributor:

@all-contributors please add <username> for <contributions>

See the Emoji Key for a list of valid contribution types.

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc. that have the same generic comment to describe them. Take a look at one of those resources and see if you can figure out a more descriptive comment to tell readers what they will get out of looking at it.

Only choose one for now - to give others a chance.

📋 Step by Step
There is a Step-By-Step Guide to bring you From Issue to Pull Request in the docs folder - called Getting-Started.md
Else, if you know what to do - comment on this issue to say you'll do it. Then Branch, Commit, Pull - and all being well, we'll be happy to merge you in.

Happy Hacktoberfest!

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. We'd like the specific information to replace those placeholder texts

📋 Step by Step
Step by Step

• 🙋 Claim this issue by commenting on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)

The change I suggest is go to the Get Involved Section, starts around line 104. Edit the Get Involved line so that it reads:

| [Get Involved](https://www.pluralsight.com/courses/get-involved) | Pluralsight | 5 | Scott Hanselman and Rob Conery offer suggestions and advice on how you can get out there, and get involved |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add ConFoo to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
Around line 104 of the Readme, is the Get Involved Section, add in the Stack Overflow details

📋 Step by Step

• 🙋 Claim this issue by commenting on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)

The change I suggest is go to the Get Involved Section, starts around line 104. Add an entry after the last one in the section that reads:

| [Stack Overflow](https://stackoverflow.com/) | Stack Overflow | 11 | Stack Overflow is a question and answer site for professional and enthusiast programmers |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add Wenli Zhang to the Mentors section
• See below for link to step-by-step tutorial
• Go down to Mentors section - it starts at around line 83
• Paste the following information underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Ovilia](https://github.com/ovilia) | Wenli Zhang | 4 | Passionate Dataviz Developer & Creative Designer; PPMC of Apache ECharts (incubating) |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
Around line 175 of the Readme, is the And Then What Section, add in the Coding with Rockstar details

📋 Step by Step

• 🙋 Claim this issue by commenting on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)

The change I suggest is go to the And Then What Section, starts around line 175. Add an entry after the last one in the section that reads:

| [Code with Rockstar](https://codewithrockstar.com/) | Dylan Beattie | 11 | Rockstar is a computer programming language designed for creating programs that are also heavy metal power ballads - it's not for the faint of heart |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add Facebook F8 to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add Open Source Summit to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add PowerShell and DevOps Global Summit to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add Chrissy LeMaire to the Mentors section
• See below for link to step-by-step tutorial
• Go down to Mentors section - it starts at around line 83
• Paste the following information underneath the last row in the table, ensuring there is still an empty row before the next table.

| [potatoqualitee](https://twitter.com/cl) | Chrissy LeMaire | 4 | SQL & PS MVP, creator of @psdbatools member @thelivecoders & @PowerShellLive author http://dbatools.io/book |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add FOSDEM to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

This repository is aimed at helping more people get into coding with confidence. It has 10 (ish) sets of resources to enable that. If you notice there is anything or anyone missing - a resource or person that has helped you start or grow - please submit a pull request to add it / them in. Use the existing format (copy a line and then overwrite it) and put it in the most relevant section.

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add Apple WWDC to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

Describe the bug

This project's configuration file has malformed JSON: .all-contributorsrc. Error:: Unexpected token ] in JSON at position 2843

Does anyone know the fix for this? I have uninstalled the bot and files for now

Describe the bug
The links redirect to 404 page

To Reproduce
Steps to reproduce the behavior:

1. Go to '10-Easy-Steps/docs/emoji-key.md'
2. Scroll down to 'What's next'
3. Click on 'Notes for repository maintainers' and 'Automating the process using tools'

Expected behavior
Clicking on these links lead to a 404 page

Screenshots

Desktop (please complete the following information):

• Browser: Microsoft Edge
• Version: Version 85.0.564.63

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add DockerCon to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add CodeMash to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

GitHub uses repository topics to help people find projects that might be of interest based on their search patterns or the projects they are working on.

We'd like to add a few topics to this repository. Can you help us out?

⌨️ Activity: Adding Topics to the repository

• On the Code tab, click the gear icon located next to the About section of the repository and just above the repository description.
• In the Topics field, GitHub might have some Suggested topics for this repository.

After entering a topic (or topics), click Done.

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add DevOpsCon to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. We'd like the specific information to replace those placeholder texts

📋 Step by Step
Step by Step

• 🙋 Claim this issue by commenting on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)

The change I suggest is go to the Conferences Table, starts around line 164. Edit the Microsoft Build Conferences line so that it reads:

| [Microsoft Build](https://news.microsoft.com/build2020/) | Microsoft | 10 | Empowering Developers to Fuel Business Performance |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. We'd like the specific information to replace those placeholder texts

📋 Step by Step
Step by Step

• 🙋 Claim this issue by commenting on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)

The change I suggest is go to the Conferences Table, starts around line 164. Edit the JS Conf line so that it reads:

| [JSConf](https://jsconf.com/) | JSConf | 10 |Locally run events driven by passionate individuals dedicated to the community |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add Diana Rodriguez to the Mentors section
• See below for link to step-by-step tutorial
• Go down to Mentors section - it starts at around line 83
• Paste the following information underneath the last row in the table, ensuring there is still an empty row before the next table.

| [alphacentauri82](https://github.com/alphacentauri82) | Diana Rodriguez | 4 | Python Developer Advocate @ Vonage, GDE: web/cloud/maps/firebase, Microsoft MVP, Auth0 Ambassador |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. We'd like the specific information to replace those placeholder texts

📋 Step by Step
Step by Step

• 🙋 Claim this issue by commenting on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)

The change I suggest is go to the Conferences Table, starts around line 164. Edit the DDDPerth Conference line so that it reads:

| [DDD Perth](https://dddperth.com/) | DDDPerth | 10 | An inclusive non-profit conference for the Perth software community |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add DEVintersection to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add OSCON to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

Add the below line into the Readme.md at line 77 or after the last line in the "Try Some Code" / Step 3 table:

| Twilio Quest | Twilio | 3 | Learn to Use APIs While Playing a Game |

📋 Step by Step
Step by Step

• 🙋 Claim an issue: Comment on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)
• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. We'd like the specific information to replace those placeholder texts

📋 Step by Step
Step by Step

• 🙋 Claim this issue by commenting on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)

The change I suggest is go to the Conferences Table, starts around line 164. Edit the GitHub Universe line so that it reads:

| [GitHub Universe](https://githubuniverse.com/) | GitHub | 10 | Explore the future of software development |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

Add content to this list:

Add this line to the line below the last line in step 4, Follow some Mentors section. Ensure a space remains after you insert your entry:

| [Florin Pop](https://www.florin-pop.com/) |Freelance | 4 | JavaScript enthusiast 🙌, Front-end developer 💻, Blogger and YouTuber |

📋 Step by Step
Step by Step

• Click on the Readme.MD and then click on the little pen (top right) to edit the file
• Add this line to the line below the last line in step 4, Follow some Mentors section. Ensure a space remains after you insert your entry:

| [Florin Pop](https://www.florin-pop.com/) |Freelance | 4 | JavaScript enthusiast 🙌, Front-end developer 💻, Blogger and YouTuber |

*Commit your change Make it a good one

• Make a Pull Request Tell us what you did
• We'll review it and merge it in

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
Add content to this list: Eddie Jaoude Community

📋 Step by Step

• 🙋 Claim the issue by commenting on it.
• Step-by-Step
• For the edit - go down to the Get Involved section that starts around line 103 and add this beneath the last entry in the table, ensuring there is still a blank line before the next section starts

`| Eddie Jaoude Community | Eddie Jaoude | 5 | OPEN SOURCE is NOT about code, it is about people and collaboration |'

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

Describe the bug
Broken link 'Code of Conduct' in contributing.md

To Reproduce
Steps to reproduce the behavior:

1. Go to '10-Easy-Steps/contributing.md'
2. Click on 'contributing.md'
3. Scroll to 'line 7'
4. Edit link to the correct link of Code of Conduct (https://github.com/msandfor/10-Easy-Steps/blob/master/code_of_conduct.md)

Expected behavior
The link should go to Code of Conduct (https://github.com/msandfor/10-Easy-Steps/blob/master/code_of_conduct.md)

Screenshots
If applicable, add screenshots to help explain your problem.

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. We'd like the specific information to replace those placeholder texts

📋 Step by Step
Step by Step

• 🙋 Claim this issue by commenting on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)

The change I suggest is go to the Conferences Table, starts around line 164. Edit the NDC Conferences line so that it reads:

| [NDC Conferences](https://www.ndcconferences.com/) | NDC | 10 | high-end events for software developers |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. We'd like the specific information to replace those placeholder texts

📋 Step by Step
Step by Step

• 🙋 Claim this issue by commenting on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)

The change I suggest is go to the Conferences Table, starts around line 164. Edit the YOW Conferences line so that it reads:

| [PyCon](https://pycon.org/) | Python.Org | 10 | See what's going on in the Python world |

• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. Take a look at one of those resources and see if you can figure out a more descriptive comment to tell readers what they will get out of looking at it. Only choose one for now - to give others a chance.

📋 Step by Step

• 🙋 Claim an issue: Comment on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)
• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself to the list of contributors by going to the bottom of the Readme.md and adding yourself to the list using the same format as the others

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

Add content to this list:

Add Dylan Beattie to the line below the last line in step 4, Follow some Mentors section. Ensure a space remains after you insert your entry:

📋 Step by Step
Step by Step

• Click on the Readme.MD and then click on the little pen (top right) to edit the file
• Add this line to the line below the last line in step 4, Follow some Mentors section. Ensure a space remains after you insert your entry:

| [Dylan Beattie](https://dylanbeattie.net/) | Ursatile | 4 | Creator of the [Rockstar](https://codewithrockstar.com/) programming language, a Microsoft MVP for Visual Studio and Development Technologies |

*Commit your change Make it a good one

• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself as a Contributor to the bottom of the Readme.md using the same formatting as the others in the list

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
The README for this project has some repeat/placeholder comments. If you look at the look at the Readme you will see resources, articles, webpages, videos etc that have the same generic comment to describe them. Take a look at one of those resources and see if you can figure out a more descriptive comment to tell readers what they will get out of looking at it. Only choose one for now - to give others a chance.

Alternatively... perhaps you would like to add content to this list. Feel free to do that to, but make sure that what you suggest we add in as really useful. We don't want people to be overwhelmed with too many choices, or demotivated by content that is not accessible to beginners. Make suggestions for resources/people that you have used yourself and comes with your most heartfelt recommendation.

📋 Step by Step
Step by Step

• 🙋 Claim an issue: Comment on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)
• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add WeAreDevelopers to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:
Perhaps you would like to add content to this list. Feel free to do that to, but make sure that what you suggest is really useful. We don't want people to be overwhelmed with too many choices, or demotivated by content that is not accessible to beginners. Make suggestions for resources/people that You have used yourself and comes with your most heartfelt recommendation. 💝

📋 Step by Step

• 🙋 Claim an issue: Comment on it.
• Create a New Branch How to branch, Commit, Pull, Merge - start at step2
• Make your change - I use Github Desktop and Visual Studio Code so I don't have to do anything via the command-line, but if you like the command-line git on with it ;-)
• Commit it Make it a good one
• Make a Pull Request Tell us what you did
• We'll review it and merge it in
• Add yourself to the list of contributors by going to the bottom of the Readme.md and adding yourself to the list using the same formatting as the others

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful

🆕🐥☝ Beginners Only:
This issue is reserved for people who are new to Open Source. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

To do:

• Add O’Reilly Software Architecture Conference to the Conferences Section
• See below for link to step-by-step tutorial
• Go down to Conferences section - it starts at around line 173
• Using the following template, put in the correct info for that conference (Search for it on the internet to find the correct details) underneath the last row in the table, ensuring there is still an empty row before the next table.

| [Conference Name](Website Address) | Conference Name or Organising Org | 10 | Description of the Conferences, found on their website |

• Add your details in the contributors section at the bottom of the page using the same formatting as the last one

📋 Step by Step
Step-By-Step Tutorial

Remember to observe the Code of Conduct - by which we mean, in short - Be Kind, Be Positive, Be Helpful