Feature/Docs Request: Link to the example code next to the interactive demos.

[alanscodelog]

Description

I noticed while reading the rapier docs, that for example the custom collider example code is confusing, that is, the interactive example shows multiple meshes but the code below is just showing a regular single collider. To get the real example code I had to go to the repo.

Suggested solution

Could the code be linked to after each example?

I'm willing to submit PR to have every example link to it's full github demo code.

Alternative

Even better would be to have the code in like a separate "tab" in the docs, but that's a bit more complicated.

Additional context

No response

Validations

• I agree to follow this project's Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[tresjs-cube-bot]

Hey @alanscodelog! 🧊

This looks like a feature request — awesome ideas belong in Discussions where the community can upvote and discuss!

I'm closing this issue, but please create a discussion so the community can weigh in. Thanks for contributing! 💚

🤖 I'm an AI assistant and can make mistakes.

[linear-code]

TRES-386

[alanscodelog]

I wouldn't mind but I feel this belongs in the issue tracker. Also the contributing guidelines which I did read, say "Open an issue first to discuss the feature". If maintainers would prefer the flow be discussion first maybe that should be edited?

[alvarosabu]

Hi @alanscodelog you are right, I have to tweak the bot to not close this kind of issues. Thanks a lot for reporting this, feel free to open a PR.

About the tab, where you thinking on something like this?

@Neosoulink for visibilty