-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken images on web view #17
Comments
While it hasn't been fixed, I think the reason for this can be found in Issue 11. |
Ah yes, this is a duplicate issue it looks like |
Sorry guys, I'm really busy with work; if someone submits a MR I promise to review it tho. |
Don't sweat it, you've made a fantastic tutorial for free - I just noticed
the same thing, noticed the duplicate issue and wanted to flag it. It's
totally fine in on github and I've been following along that way.
At some point when I have a sec (I'm also completely slammed) I'll see if I
can sort it and post it for review.
…On Tue, Dec 12, 2023 at 2:07 PM maksimdrachov ***@***.***> wrote:
Sorry guys, I'm really busy with work; if someone submits a MR I promise
to review it tho.
—
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEGGVCHRGSHKC75XKRYDHOTYJBJHJAVCNFSM6AAAAAA6TCWZVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJSGAYDCMZVGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I think the image paths only need to two extra parent directory references. For example instead of (And very fantastic tutorial indeed!!!) |
I am willing to take over this issue, is @maksimdrachov still active on his repository? As described in the contribution guide: "In comments claim that you want to take over the issue. The first person who does this will be assigned to the issue." |
Yeah sure, go ahead! |
Yes, see pull request! |
Many pages on the web view have broken images. For example, here https://maksimdrachov.github.io/zephyr-rtos-tutorial/docs/3-threads/introduction.html
The text was updated successfully, but these errors were encountered: