Regression: L0 documentation structure change broke external links & searching

External links to L0 docs are now broken

Links in L0-using application's documentation and code comments to L0 documentation rely on specific structure of the L0 documentation and its link references. Changing how documentation is structured, broke all such links, e.g:

• https://github.com/intel/xpumanager/blob/v2.1.0/xpumd/level-zero-go/sysman/types.go#L14
• https://github.com/collectd/collectd/blob/collectd-6.0/src/gpu_sysman.c#L2135

Besides breaking such links, splitting the documentation to have different API subsets under their own pages, makes automated link generation for L0 documentation (based on function and type names) significantly less convenient e.g. for L0 bindings.

API searchability lost

With earlier one-page API docs for L0 API components, it was possible to easily search the whole (e.g. Sysman) API doc for features that (potentially) cover several API subsets, using browser's page search. Splitting the API to separate pages, breaks that, and would require some kind of search functionality for the API docs site instead.

Earlier doc versions missing / site's own links are broken

Additionally, older documentation with the old structure seems to be missing, or at least is not discoverable, see e.g:

• https://oneapi-src.github.io/level-zero-spec/level-zero/1.15/index.html
• https://oneapi-src.github.io/level-zero-spec/level-zero/
• https://oneapi-src.github.io/level-zero-spec/
• https://oneapi-src.github.io

Those give either:

• an error page with an invalid link,
• directs to latest spec version instead of allowing user to select specific version of the documentation, or
• a completely empty page

Expectation

Single API page which can be used to search whole API, and to reference all types & functions in generated L0 bindings documentation, preferably under versioned directory (at least major version).

Start by comparing the linked current and older documentation paths, including level-zero/1.15/index.html and the level-zero-spec roots, and trace how the API pages and site links are produced. Done means a single searchable API page is available, type and function references remain usable for generated bindings, and versioned documentation links resolve to the requested version.