LB (Ben Johnston)

@thibaudcolas as discussed earlier this week, as we start to look at the Stimulus widget adoption we have found that we have a few different approaches to global config/metadata/settings in...

@laymonage yeah I looked at that script approach myself and I think it's good for a small set of cases but has trouble once we need to consider other code...

Ok - I have a rough bit of code working that pulls in some config for `LOCALES` and `MAX_EXPLORER_PAGES` via the Telepath data into the PageExplorer. Same could be done...

@gasman how about we approach this differently. Instead of setting up any global config like this we push towards the individual widgets own their own config 99% of the time....

Getting my head around this again and agree that we should keep things simple, the `meta` idea is probably not worth the complexity, nor is the added hook. Thanks for...

Another idea, for the gaps that cannot be resolved another way, is a fresh take on the [`json_script`](https://docs.djangoproject.com/en/5.0/ref/templates/builtins/#std-templatefilter-json_script) template tag. ```html {{ value|wagtail_config }} ``` With the value (from Python)...

Update: `window.chooserUrls` has gone in a different direction, See https://github.com/wagtail/wagtail/pull/11620 & https://github.com/wagtail/wagtail/issues/11586 - the overall solution is actually much simpler and just passes the chooserUrls down via the Entity's options...

Thanks @salty-ivy - have tagged this for review.

@salty-ivy I really think it may not be worth solving for page_status_tag yet - it will introduce a potentially complex convention of outer tags if we use `use='a'` and it's...

@salty-ivy - Matt's idea above is a great one, it gives us the benefit of keeping the status template tag generic but supports the `a` tag without getting too complicated....