Editor documentation for Engine V2

[kpal81xd]

Overview

• Added documentation for Editor V2

Preview

Engine Compatibility

Editor Migrations

[Maksims]

Please, don't call it Editor V2, there is nothing for it to be called V2.

[mvaligursky]

I would suggest a reorg into two separate pages.

1. ---

• I would call the document Engine Compatibility, and the document would live under the Editor section of the manual. I would not mention Editor V2. From the user point of view, there is only one Editor.

In the introduction I would explain that the Editor supports two major release streams of the engine:

• latest release of engine 1.x.x (engine V1) - this provides support for WebGL1 and WebGL2, but does not receive any new features, and only critical bug fixes.
• latest release of engine 2.x.x (engine V2) - this has no support for WebGL1 and supports WebGL2 and WebGPU for rendering, and receives new features and fixes.
  I would also mention that you can change which release a project uses.

The following section would be Switching project between Engine V1 and V2 - this corresponds to your Project V1 to V2, but should mentioned V2 to V1 as well.

2. ---

And then I would suggest a separate document on Editor upgrades, called Editor Migrations. Similarly to how we have this new Engine Migrations (#687) and existing Shader Chunk Migrations. It should introduce the document as describing major changes during Editor releases. And first chapter would be Migration from x.x.x to x.x.y (use actual Editor versions), where we could describe this as Editor internally switching to use Engine V2, and what the impact is for the users. This corresponds to your Editor Changes section.

[mvaligursky]

Looks good to me, leaving suggestion for one clarification.

It'd be fantastic if @willeastcott had a chance to look at this as well.

[willeastcott]

Approving with some minor tweaks.