Link in-engine documentation to do a search for demos that use a specific node or node method

[Dinsmoor]

Describe the project you are working on

Just starting out in Godot, I am learning it with my family as we want to make games together as part of our homeschooling.

Describe the problem or limitation you are having in your project

Finding good quality example code of how nodes are used in the documentation takes quite a bit of effort. Right now I have to download demos from assetlib and then manually search the contents if a certain node is instantiated and how it is used. Versioning is annoying too, especially if I'm looking on github for projects.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

I want metadata associated with demos in assetlib that lists what nodes are used and how many to be available.

Basically, parse the .tscn for nodes, then the nodes for attached scripts, then the scripts for calls to built-in functions, and index those references in a database hosted by whoever hosts assetlib.

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

When viewing documentation like below:

Clicking that button, or maybe a little expandable window will be there, and have a scrollable view for examples of the use of a node in scripting.

Clicking a function header examples too, would just narrow the search a little bit.

If this enhancement will not be used often, can it be worked around with a few lines of script?

It can be worked around by manually downloading projects or searching github like we have been doing since the beginning of time, but it takes a very long time and also I think it would be used very often. Also, versioning of projects on github, older versions with slightly different behavior probably throw people off.

Is there a reason why this should be core and not an add-on in the asset library?

It would get used a lot I think, and improve visibility and use of demos in assetlib, and from a 'we have a bunch of projects in a folder and just need to parse them and stick the metadata into a postgresql table and then have the client make a GET request' point of view it really should be pretty easy to implement and save a lot of time.

[Meorge]

The documentation has support for a "Tutorials" section that can point to curated resources, as seen here with AnimationPlayer:

However, these have to be added manually. I think it'd be tricky to automate this process for many nodes, because it's possible a demo project or tutorial may mention or briefly use a node/method, without it being focused on or used in a way that'd be useful for a new user.