This is just an idea -- I'm unsure if it could work in practice, but it would be neat if we could develop a sphinx extension that could substitute output of flux command examples in the docs directly during the docs build.
There already exists a sphinxcontrib-programoutput extension that can substitute program output into docs at build time, e.g.:
.. command-output:: python -V
Output:
Perhaps starting from this implementation, someone clever could create an extension that was capable of interacting with a Flux instance and would substitute output of commands. Perhaps our deployed docker images could be used in the Readthedocs build (not sure if that is possible).
This is just an idea -- I'm unsure if it could work in practice, but it would be neat if we could develop a sphinx extension that could substitute output of flux command examples in the docs directly during the docs build.
There already exists a sphinxcontrib-programoutput extension that can substitute program output into docs at build time, e.g.:
Output:
Perhaps starting from this implementation, someone clever could create an extension that was capable of interacting with a Flux instance and would substitute output of commands. Perhaps our deployed docker images could be used in the Readthedocs build (not sure if that is possible).