For example, the file packages/next/components/landing/r-libraries.tsx hardcodes two columns for two R environments and their names&descriptions. This is just going to break, because the definition of available environments per language is in the compute-inventory.json file, under the key julia, octave, python, and R. The keys inside of each mapping are defined in the language_exes entry, where the key name holds the name, and shows the appropriate description in doc.
For example, the file
packages/next/components/landing/r-libraries.tsx
hardcodes two columns for two R environments and their names&descriptions. This is just going to break, because the definition of available environments per language is in thecompute-inventory.json
file, under the keyjulia
,octave
,python
, andR
. The keys inside of each mapping are defined in thelanguage_exes
entry, where the keyname
holds the name, and shows the appropriate description indoc
.reference implementation: https://github.com/sagemathinc/cocalc-landing/blob/master/views/_base.pug#L163