Docs code block standards

[shaedrich]

When checking code block contents in the docs, I saw a lot of inconsistencies:

• Should the <?php be included or omitted?
• Should the class ClassName { … } be included or omitted when describing a method?
• Should the namespace be included or omitted?
• Should the use statement for used classes, traits, and interfaces be included or omitted?
• Is highlighting, focusing, or collapsing preferred?
• Semicolon after last statement?
• ``` or indent?

[marius-mcp]

@shaedrich I see you want to clean up and put stuff in order:)

[shaedrich]

If that's not vetoed 😅

Especially, Torchlight brings some features that might not have been available when some code samples were originally written.

[shaedrich]

Apparently, this won't be necessary anymore since Taylor decided to rework the docs and reject changes he himself requested. How the rework will look, probably only he know, so we'll see.

[Sophist-UK]

As a coder I prefer to have things consistent in my editor - but the choice of which of the current multiple ways is also important, and personally I would prefer to have things inconsistent if the choice of way is one I absolutely dislike (better to have some that are OK rather than none that are OK).

It seems to me that @shaedrich Sebastian is looking for input from the community here on what choices to narrow down to. And personally, for the sake of absolute clarity, I would like to see a detailed comment here giving examples of the choice to narrow to for each of the inconsistencies. Sebastian, is this something that you can provide?

[shaedrich]

Apparently, this won't be necessary anymore since Taylor decided to rework the docs and reject changes he himself requested. How the rework will look, probably only he know, so we'll see.