The old cuelang.org supported the concept of tip.cuelang.org. This meant that:

• cuelang.org served the latest version of the docs, using the latest non-pre-prelease version of CUE.
• tip.cuelang.org served the latest version of the docs, blindly regenerated using the tip of CUE.

We need to work out in the new cuelang.org world what versions of CUE we want to "offer".

And as part of that, work out whether each of those versions is fully checked as part of CI. Right now, those checks cover:

• Regeneration of examples etc using the preprocessor
• The version of CUE used in the playground
• ...

The output from the preprocessor is committed, hence if we regenerated any commit of the docs against a different version of CUE it is possible/likely that we will get different results.

The same question of the "matrix" of versions applies to things like the version of Go used in examples.

cc @jpluscplusm