Erik Sommer

My preferred solution would be to change/adjust the theme. https://www.mkdocs.org/user-guide/styling-your-docs/

Actually… it looks like the ReadTheDocs (RTD) infrastructure is at fault. The long values aren't even supposed to be there. README has no place in the navigation. Something fishy in...

https://docs.readthedocs.io/en/stable/intro/getting-started-with-mkdocs.html > We strongly recommend to pin the MkDocs version used for your project to build the docs to avoid potential future incompatibilities. We might have to add a configuration....

@bertsky This is quite an old issue but I just checked if it still persists. I have access to two projects on RTD: Both can be built but [*this* official...

>However, did you notice that even in your deployment, within the user section, none of the images resolve correctly? HA! Yesterday I checked this [architecture section](https://kitodoproduction-dev.readthedocs.io/en/master/developer/architecture/) and all the images...

As @solth commented in #4896 any dependencies towards ElasticSearch should be gone with a switch to HibernateSearch (which is currently WIP as far as I know) and OpenSearch might be...

> Could you please explain why you think that this would be "a bad way and a security issue"? I think setting execute permission (`chmod +x`) needs to be done...

> Any script can be executed, no matter whether it has execute permission or not. If it does not have execute permission, you just have to run it with bash...

> In my example above I have explained a scenario on a build host with more than a single user where the current code is a real risk if there...

@solth needs to make a decision here. :)