Fix broken images in the contribution.md file of this repo

[TimOsahenru]

You can create an assets/images folder and add the relevant files using this REPO as a guide or source of truth on what files to include in the assets/images

[mbvgua]

Yes images would better help one visualize this.

But a follow up question that adds on that: since this specific repo only has markdown files(as compared to the github.io repo that needs alot of dependecies and packages installed), wouldnt it be easier and better if people were to work on them in their local environment using their favourite editor instead of the Codespaces?

[TimOsahenru]

Not sure what you mean, do you mind clarifying? Mind you, this issue is to fix the broken images in this file https://github.com/BlackPythonDevs/.github/blob/main/CONTRIBUTING.md

[mbvgua]

Okay, great. Your link directs to the page below:

And I think that you are proposing for the links to be fixed such that they will resemble the main repo as below:

Your proposed solution would aim for the images to direct one on how to develop on the Github Codespaces. I am building on your idea by proposing that for this specific repo, instead of working in the codespaces we could instead work in a local environment, whereby after forking the repo you clone it to your device then begin contributing.

If these were the case, the images that would need to be uploaded would not have to for codespaces as you suggested, but instead ones guiding you on how to develop locally.

[TimOsahenru]

Gotcha! Well this issue is to help those contributing using the codespace but, can’t make meaningful sense out of it cos of the broken images

[TimOsahenru]

If there isn’t an issue that deals with contributing locally I’d suggest you create one

[mbvgua]

Yes. I also agree that would be better way forward. Let me do that immediately

[TimOsahenru]

Ensure you confirm that issue has not already been created. Check this out BlackPythonDevs/blackpythondevs.github.io#416 might be related to your issue

[mbvgua]

I think that the organisations repos are supposed to be independent of each other. Because if this were the case, the issue has not been raised on this repository, but if not I have seen it in another repo here .

Edit: after thorough consideration, I think I will just close the issue i had created. If it is fixed on the main repo the changes might reflect here too.

If not, ill be sure to open it again 😄