chore: prepare for docs versioning

[jeluard]

Motivation

Prepare for future versioning. For now only support one version, and display it in the main toolbar.

Fixes #6548

[codecov]

Codecov Report

Merging #6559 (b92d355) into unstable (4686ad1) will not change coverage.
Report is 4 commits behind head on unstable.
The diff coverage is n/a.

❗ Current head b92d355 differs from pull request most recent head 9a67a0f. Consider uploading reports for the commit 9a67a0f to get more accurate results

Additional details and impacted files

@@            Coverage Diff            @@
##           unstable    #6559   +/-   ##
=========================================
  Coverage     61.39%   61.39%           
=========================================
  Files           556      556           
  Lines         58751    58751           
  Branches       1848     1848           
=========================================
  Hits          36073    36073           
  Misses        22638    22638           
  Partials         40       40           

[wemeetagain]

shouldn't this match whats in our packages/cli/package.json?
What is the process for synchronizing this?

[jeluard]

My bad, my intention was to match the repo versions. Ideally the latest version would be updated via the release scripts.

It's not clear to me when we would want to introduce a new doc version. FWIW, introducing a new doc version requires duplicating the whole doc content in a specific repo (a script can help this process)

Maybe @nflaig can shim in, as was interested with the versioning support.

[nflaig]

Maybe @nflaig can shim in, as was interested with the versioning support.

The idea was to have something similar to what teku does https://docs.teku.consensys.io/.

We could always build docs from unstable branch (on each commit), have docs from stable branch as default as we do now, and then just a few previous releases back.

FWIW, introducing a new doc version requires duplicating the whole doc content in a specific repo (a script can help this process)

Previous docs bundle would have to be hosted somewhere, maybe this is possible via github pages, or another source is required. Might wanna check out how teku does it https://github.com/Consensys/doc.teku

[jeluard]

Previous docs bundle would have to be hosted somewhere, maybe this is possible via github pages, or another source is required. Might wanna check out how teku does it https://github.com/Consensys/doc.teku

Sorry I meant in a specific folder, it's fine in current repo/gh-pages hosting. So the repo would ultimately contain multiple copies of the whole documentation, with just a couple changes (see how it looks like for teku).

Maybe we can decide to not introduce doc version per lodestar release, but only introduce new doc version when significant docs changes have been introduced.

[nflaig]

Will this just show the latest version for now?

[nflaig]

Suggested change

	[]
	[]

[jeluard]

Closing for now. Will address once we have a better idea of what we want.

[nflaig]

Closing for now. Will address once we have a better idea of what we want.

The ideal case would be the same as Teku docs, have unstable / stable, and a few releases back

But if that's too much effort to realize it's definitely not that high prio, so can postpone that for now