Skip to content

Update instructions for creating Resource objects#12114

Open
hvdyinv4688hbv wants to merge 1 commit into
godotengine:masterfrom
hvdyinv4688hbv:patch-1
Open

Update instructions for creating Resource objects#12114
hvdyinv4688hbv wants to merge 1 commit into
godotengine:masterfrom
hvdyinv4688hbv:patch-1

Conversation

@hvdyinv4688hbv

Copy link
Copy Markdown

Clarify instructions for creating a new Resource object in the Inspector.

Clarify instructions for creating a new Resource object in the Inspector.
@hvdyinv4688hbv
hvdyinv4688hbv requested a review from a team as a code owner June 28, 2026 22:49
@AThousandShips

Copy link
Copy Markdown
Member

I'm not sure this is needed or if we should really make this so verbose and explicit here, this is already covered in the introduction so I doubt anyone will be confused by this if they've read things that anyone should have read when looking at this part of the documentation

@hvdyinv4688hbv

Copy link
Copy Markdown
Author

i guess my question is: is the editor introduction a standard prerequisite for other sections of the documentation? if not, i think it is a good addition. You are right about it being verbose. There is probably a better way to word it. maybe: Create a new Resource object in the Inspector by clicking the top left icon.
or
Create a new Resource object in the Inspector by clicking [image of icon goes here].

@AThousandShips

Copy link
Copy Markdown
Member

Yes people are expected to have read the introduction, I do not believe we should write the documentation for the case where users haven't read the basics, otherwise we'll bloat the text with obvious things

Have anyone actually reported issues with this?

@Mickeon

Mickeon commented Jun 30, 2026

Copy link
Copy Markdown
Member

the file icon with the green plus sign

This is the kind of overly-specific details that are prone to become invalidated in the future, turning what would look helpful in the moment into confusing instructions that don't quite match the current editor. Because they're a big maintenance burden, there's an on-going effort to minimize these cases, so this PR doesn't quite help as much as one may think.

@Calinou Calinou added enhancement area:manual Issues and PRs related to the Manual/Tutorials section of the documentation labels Jul 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:manual Issues and PRs related to the Manual/Tutorials section of the documentation discussion enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants