Problem to Solve
Even if we implement tabs in a very good way with all the blocks (code-blocks, note-blocks, tables, images, etc.) working properly inside tabs there is still a notion to have a single page with a lot of content where only some of the content will be adjusted for the selected language.
Current Workaround
Just use huge tabs with all the content in every tab and try not to use a lot of different blocks, as some note blocks, for example - can break the rendering (in the old documentation engine).
Proposed Solution
That could be achieved by using multiple tab sections on the page to contain language-specific content only and leaving the common content as usual, but with synchronized tabs (choose Java anywhere and all of them on the page will switch to Java).
But there are still a few things to think about. For example, we would want to be able to link to this page and even to some sections (titles) of this page with a language selected. I see that the language could be stored in the URL as ?=java parameter or something like that (something like that - #148). But it should be compatible with the ability to link to the title (or preferably also to an invisible anchor ).
Additional Information
That might also be combined with a version selector (#144), but that could be achieved with different solutions.
Problem to Solve
Even if we implement tabs in a very good way with all the blocks (code-blocks, note-blocks, tables, images, etc.) working properly inside tabs there is still a notion to have a single page with a lot of content where only some of the content will be adjusted for the selected language.
Current Workaround
Just use huge tabs with all the content in every tab and try not to use a lot of different blocks, as some note blocks, for example - can break the rendering (in the old documentation engine).
Proposed Solution
That could be achieved by using multiple tab sections on the page to contain language-specific content only and leaving the common content as usual, but with synchronized tabs (choose Java anywhere and all of them on the page will switch to Java).
But there are still a few things to think about. For example, we would want to be able to link to this page and even to some sections (titles) of this page with a language selected. I see that the language could be stored in the URL as
?=javaparameter or something like that (something like that - #148). But it should be compatible with the ability to link to the title (or preferably also to an invisible anchor ).Additional Information
That might also be combined with a version selector (#144), but that could be achieved with different solutions.