Improve Qute documentation

[neon-dev]

ItemResource should be HelloResource here:

quarkus/docs/src/main/asciidoc/qute.adoc

Lines 148 to 149 in 37873c4

	your `ItemResource` class references two templates `hello` and `goodbye`, place them at `/src/main/resources/templates/ItemResource/hello.txt`
	and `/src/main/resources/templates/ItemResource/goodbye.txt`. Grouping templates per resource class makes it easier to navigate to them.

[quarkus-bot]

/cc @mkouba (qute)

[mkouba]

Well, it's just an example so it's not necessarily wrong but I agree that HelloResource would be better. @neon-dev Would you care to send a pull request?

[neon-dev]

It is wrong because the example continues with HelloResource.java, so the build would fail as the file paths won't match. Also goodbye.txt isn't declared in the class, so this section maybe should be revised too?
I'd prefer to not create a pull request myself, but I can if you insist.

[melloware]

@neon-dev PR submitted please review: #44289

[mkouba]

It is wrong because the example continues with HelloResource.java, so the build would fail as the file paths won't match. Also goodbye.txt isn't declared in the class, so this section maybe should be revised too?

But this paragraph is merely describing the convention for type-safe templates. And then the correct steps to rewrite the example from the previous section follow. That said, I don't mind if we use HelloResource in this paragraph. It's more clear.

I'd prefer to not create a pull request myself, but I can if you insist.

Of course I don't insist but contributions are welcome 😉.

@neon-dev PR submitted please review: #44289

@melloware 👍 Thanks, I'll take a look.

[neon-dev]

But this paragraph is merely describing the convention for type-safe templates. And then the correct steps to rewrite the example from the previous section follow. That said, I don't mind if we use HelloResource in this paragraph. It's more clear.

I see. Thanks for clarifying, I hadn't thought about that.
The way it is written strongly implies everything is already appropriately named for the example code that follows just a few lines after, otherwise it wouldn't make sense to showcase exactly the two *.txt files that are used within the same section.

Of course I don't insist but contributions are welcome 😉.

I'm sorry, maybe next time :)
Thx @melloware

[mkouba]

otherwise it wouldn't make sense to showcase exactly the two *.txt files that are used within the same section.

The thing is we actuallly do not showcase two txt files in the same section. It's one template used in two resources...

[neon-dev]

With section I was referring to the section of the documentation.