awesome-login-pages VS opendrinks

Awesome Login Pages: Created a Markdown based Readme Contributors section

The repo is opendrinks , a cocktails recipe website built in Vue. I do not code in Vue but I could contribute by adding a new recipe. Ok, let's go read the docs, the contribution guide, clone the repo, create a new JSON file, testing locally... Well, that's it, the first PR is sent. PR accepted 🎉 Horray. Nice, but I was feeling a bit like I was cheating, this is not really coding right?

Next up was a neat project I found, Open Drinks, where contributors can submit recipes for various alcoholic and non-alcoholic drinks. It was another great exercise of git and gh commands as well as familiarizing myself with JSON objects and properties. I decided to submit a drink I enjoyed at the Christmas markets from my time in Germany, Glühwein. Go checkout some other awesome recipes!

Open Drinks

The first one was opendrinks, where the task was to add a new recipe to the page. I added my favourite pumpkin juice recipe. In this project, I made 2 mistakes.

I began with very basic PRs including submission of foundational C++ programmes. In one of the PRs, I wrote a cpp code that prints the elements of a 2 dimensional array in a spiral manner. I also came across a repository in which we had to write a json file for the recipe of awesome drinks. I asked a friend of mine as to what a json file meant (yes, I didn't even know what a json file was!) It took me a while to write a ginger lemon tea recipe (thanks to maa's help) in a json file format. Lastly, I made a PR to a repository maintained by a senior at NIT Rourkela. A friend of mine gave his repo's reference, and after contacting him over the mail, I finally opened my first issue on his repo. I added in a ping pong game that I had learnt to program using Python's turtle module (pygame was too intimidating at that time :/) I was asked to add in a requirements.txt file, which I eventually did :) I also learnt the Pull Request Ettiquete and Writing a Good Issue. These are so very important now that I think about open source. And this is how it all went!