fix-2025-07-17-what-we-learned-from-the-chaoss-data-science-hackathon.md

[rajvi0106]

fixes/part of #2
Fixes the broken image markup on the what-we-learned-from-the-chaoss-data-science-hackathon blog post as part of #2.

[MoralCode]

Thanks for contributing this

I noticed some extra things when comparing the two sites:

1. the image on the main site (https://chaoss.community/what-we-learned-from-the-chaoss-data-science-hackathon/) has alt text specified when the version on my local build doesn't. Can you make sure to copy the alt text over as well?
2. I'm noticing that the built page also seems to include a lot of markdown in the page itself. I know you didnt touch these lines of code, but I'm curious if theres something causing this page to not show up correctly (happy to address this in a new issue if you prefer)

3. I think it should be possible to embed this image using markdown syntax ![alt text here](link to image) - could you try that and see if that works? then we can avoid confusing newcomers with a mix of markdown and HTML syntax if possible

Thanks so much for your contribution!

[MoralCode]

Since this image exists in this git repo already, could you update this URL to refer to it, so that the site can still build and be viewed offline?

Suggested change

	<img src="https://chaoss.community/wp-content/uploads/2025/07/leif-christoph-gottwald-iM8dxccK1sY-unsplash-2048x1152.jpg">
	<br>
	<img src="{{ "wp-content/uploads/2025/07/leif-christoph-gottwald-iM8dxccK1sY-unsplash-2048x1152.jpg" | relURL }}">
	<br>

[rajvi0106]

Thank you for the feedback!

1. I have added the alt text.
2. I found the issue with the raw markdown links -
   the reference links at the bottom are using
   {{ baseURL }} which doesn't get processed in
   markdown files. I can fix these by replacing
   {{ baseURL }} with / ,should I include this
   fix in the current PR or open a separate one?
3. I've updated the image to use markdown syntax
   with the relative path.

[MoralCode]

2. I found the issue with the raw markdown links -
the reference links at the bottom are using
{{ baseURL }} which doesn't get processed in
markdown files. I can fix these by replacing
{{ baseURL }} with / ,should I include this
fix in the current PR or open a separate one?

i guess do that in a new issue - / is not always a valid substitute for the base url, so it would be nice if we could get this to work.

I think theres also a lot of other pages where I find-and-replaced the url in the markdown links to use the baseURL variable, so we should probbaly find a solution that works for all of them