Closed IceSentry closed 2 months ago
What if in the example metadata, you could specify a list of important related files that should also be shown on the website?
[package.metadata.example.shader_material]
name = "Shader Material"
# ...
related = ["assets/shaders/custom_material.wgsl"]
Yeah, that makes sense. It would be ideal if it was completely automated but I don't think that's possible
you could imagine going through every call in an example to the asset server and looking at the files loaded, but I think that's way too complex for what it's worth. metadata are probably the way to go, but adding them now to the Bevy repo means they will be available starting with the next release
Objective
The shader examples are missing the actual shader code which is a pretty important part of those examples. We should have a way to also copy the code from those files and show them in a code block below the current code block.