In the translation to pirate english I found a link to the Translations.md which isn't set correctly (current destination throws status 404).
馃悶 Problem
The file README.en-pirate.md has a broken link to Translations.md (both files are located in the translations folder) - the file is linked with a relative link in markdown and points to https://github.com/firstcontributions/first-contributions/blob/master/Translations.md instead off https://github.com/firstcontributions/first-contributions/blob/master/translations/Translations.md (the last one is the correct one)
馃幆 Goal
Have the Translations.md file properly linked in README.en-pirate.md.
馃挕 Possible solutions
I would use a absolute link here, but other relative linking is absolutely ok as long as it's done right 馃憤 I guess it would work if someone would just remove the ../ in the link, but I'm not sure if Markdown linking works similar to linking files in HTML.
馃搵 Steps to solve the problem
Addresses #<put issue number here>Thank you for raising this issue @lkreimann.
I'd suggest to remove link to Translations.md and links to other translations (flag list) from this translation.
In my opinion, links to other translation is relevant only in the main Readme.
When you look at this from a user experience perspective, users to go translations to read the tutorial in their preferred language. Hence, there is no point in having links to other translations there.
I'd love to hear your thoughts on this.
Is this issue fixed?
@ankur54, no, it's not. Still I'd like to know @lkreimann's thoughts on this before taking the next step
Is anyone already looking into it?
@Roshanjossey I guess it's not really necessary to link to Translations.md. In the spanish translation (for example) is no link to any other language or the file metioned above - and I guess that's ok too 馃憤
So I would go with your suggestion and remove all the links like that, like you said.
Cool @lkreimann, @ankur54 would you like to proceed with making the changes suggested?
@Roshanjossey If no-one is picking up this then I would like to pickup this PR.
@arghyaiitb Go for it! But check the PRs first please :) Maybe there's anyone who already fixed that, who just forget to mention the number of the issue in the PR.
Is this issue closed? I am assuming it is fixed because all the links work fine for me.
@Busterz try this one:

No commits to this file in the last 13 days, no PR mentioned this issue - so I guess it's still open, but @umbeebmu seems to work on this, he just needs to start a PR.
link is still broken because my commit has not been merged yet
(not sure what I should do do have it reviewed and merged)