ToC not getting rendered properly

[sayakpaul]

Source: https://github.com/sayakpaul/portfolio/blob/master/posts/attn_diffusion.qmd

Render: https://sayak.dev/posts/attn-diffusion.html

When I preview it locally, it works perfectly fine:

I have no clue why the ToC is not getting automatically rendered on the right-hand side of the render. Other webpages like https://sayak.dev/posts/streamlined-releases.html are completely rendering it fine.

[mcanouil]

@sayakpaul There is an issue template to ensure the maintainers have all the information needed to work on an issue.
Here you shared a highly complex project.
The Quarto team does not have the manpower nor the time to go through your entire project to figure out what's wrong.
You need to trim down your project to figure out what is triggering the issue.

Meanwhile, as this issue is incomplete, I'm converting it to a discussion where you can add additional informations.

In future, we would appreciate if you could follow the guidelines.

• https://github.com/quarto-dev/quarto-cli/issues/new?template=bug_report.yml

[mcanouil]

@sayakpaul You have bad HTML which is not safe as you are using bare HTML.
I recommend you take a second look at the authoring basics from the documentation, especially the part about using non markdown in your document: https://quarto.org/docs/authoring/markdown-basics.html#raw-content

I also suggest to avoid blind copy/paste of blocks, since you've copied five times the same wrong bare HTML code.

[sayakpaul]

Thanks for your help. Fixing the raw HTML content like suggested in the guide fixed the issue.

[mcanouil]

Great to hear!

[sayakpaul]

Thanks for the help.

I also suggest to avoid blind copy/paste of blocks, since you've copied five times the same wrong bare HTML code.

Could you point to the location where I have done so? Update: Got it.

It also seems like you were able to point out issues from the info I actually provided.

Regarding providing incomplete information in an issue, I think I understand your point of view. I am a core maintainer of a fairly popular repository myself: https://github.com/huggingface/diffusers. So, I mean it when I say I understand your point of view. In this case, I thought the issue was simple to convey with the information I provided. The gist of the issue was that the stuff worked as expected offline, but didn't when it was published to the web. I am happy to stand corrected, however, I am not sure what else I could have provided here from my side. So, I would also suggest you to contemplate a bit before an answer and marking an issue invalid. Like yourself, I get a flurry of issues, too, and I say that from experience. So, a friendlier tone goes a long way.

[mcanouil]

Could you point to the location where I have done so?

You'll want to look for about five instances where HTML tags (block with images) weren't properly closed.

It also seems like you were able to point out issues from the info I actually provided.

Actually, I suspect the HTML formatting might be causing the page issues. You'll need to fix those HTML problems first and then check if that sorts out the problem.

Regarding providing incomplete information in an issue, I think I understand your point of view. I am a core maintainer of a fairly popular repository myself: https://github.com/huggingface/diffusers. So, I mean it when I say I understand your point of view. In this case, I thought the issue was simple to convey with the information I provided. The gist of the issue was that the stuff worked as expected offline, but didn't when it was published to the web. I am happy to stand corrected, however, I am not sure what else I could have provided here from my side.

The template does ask for a minimal reproducible example rather than a full project, which can help isolate whether issues stem from Quarto itself or specific content.
It also includes fields for details like the Quarto CLI version, which can be relevant for troubleshooting.
If the issue is related to HTML tags not properly closed (as it might be in this case), creating a small reproducible example often helps identify the root cause more quickly.
The template also suggests using discussions for cases where it's unclear whether the issue is with Quarto or the content itself.

"invalid" is a label nothing more stating that the issue does not conform to what is expected.
The description of that label is "This doesn't seem right".
I can set the "support" label but it does not change anything.

So, a friendlier tone goes a long way.

Thanks for pointing that out! As a non-native English speaker, I appreciate the feedback. I was aiming to be factual and helpful, but I can see how my directness might have come across as a bit blunt.

[mcanouil]

Note sure why do you resort to this

<div align="center">
<img src="https://huggingface.co/datasets/sayakpaul/sample-datasets/resolve/main/attn_diffusion/llama_header.png" width=700/>
-<p><small>Image generated with <a href="https://huggingface.co/black-forest-labs/FLUX.1-dev">Flux.1-Dev</a>.</small>
+<p><small>Image generated with <a href="https://huggingface.co/black-forest-labs/FLUX.1-dev">Flux.1-Dev</a>.</p></small>
</div>

instead of

![Image generated with [Flux.1-Dev](https://huggingface.co/black-forest-labs/FLUX.1-dev)](https://huggingface.co/datasets/sayakpaul/sample-datasets/resolve/main/attn_diffusion/llama_header.png){fig-width=700}

Source: Figure basics