Martin Fitzner

@AVHopp rendered version on fork https://scienfitz.github.io/baybe-dev/userguide/envvars.html

@RimRihana following our discussion I will abandon this PR in the expectation that you will create a new implementation on a new branch (this branch here will remain available nonetheless)

This kind of formatting issue happns ons everal example pages, here for [desirability](https://emdgroup.github.io/baybe/examples/Multi_Target/desirability.html): 

In general, getting rid of progress bar outputs or at least just having one line (to show the user that somethign WAS computing) would be nice. The caching outputs should...

@AVHopp thats right I thought I still saw progress bars somewhere but it seems theyre gone and I probably confused some of the cache notifications with them

This table in the searchspace userguide looks badly formatted in light mode:  simply fixed by removing the code formatting in table headers

@brandon-holt this Issue is just about the documentation, where progress bars have been removed. The progress bars when using our simulation module should still be there

@brandon-holt thanks for spotting that! technically your points are not visual but about a bug and content suggestions, so we should not discuss these in this thread. Would you be...

autodoc page badly cutoff to the right: 

building the doc now has ugly warnigns all over covering the progress bars in case examples are built