Spencer Bliven

#1758 Starts on this by extracting the text content to config variables. I wonder we could make this even more flexible with a template-based approach to configuration, where sites can...

@HenrikDK Your examples don't quite match the schema intent. I think you are suggesting this work-around: ``` complex_list: any(include('person'), list(include('person'))) complex_single: any(include('person'), list(include('person'))) ``` While this works, it's much more...

> Do you mean like we have from derived dataset to their input datasets? Yes, just like that.

The most obvious solution would be to stop using the `human_readable_name` feature. 🤷 Or maybe the json key should be shown on mouseover?

I think the discussion of how to serve facility-specific frontend components should be primarily discussed in #1519 (and https://github.com/SciCatProject/scicat-backend-next/issues/862 on the backend). For now I expect we will continue to...

@GBirkel thanks for the summary. At PSI we deploy the frontend and backend at different URLs, so we have to override `/assets/config.json`. I like your proposal. So if I'm understanding...

Isn't this solved in #1952? I think we can close now.

I agree that this PR needs to be refactored to only include the help/about changes. Even then, this adds only the most basic level of configuration. For #1745 we might...