Jump to content

Template talk:Infobox religious building

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Mapframe

[edit]

Does this currently natively support mapframe? If not it should imo seefooddiet (talk) 22:29, 4 February 2025 (UTC)[reply]

I added it now.
More work could probably be done to better match all the various religious affilications listed at Template:Infobox religious building#Religious affiliation and its color to better default markers. --Joy (talk) 18:35, 23 March 2025 (UTC)[reply]

"designated" parameter still US-centric

[edit]

I see there have been discussions before, but this is still pretty broken, the NRHP isn't the only designation out there. Do we need to bring this up at e.g. bot requests? --Joy (talk) 20:27, 23 March 2025 (UTC)[reply]

It probably makes more sense to recommend embedding {{Infobox historic site}} using |module= rather than trying to recreate that template's features here. – Jonesey95 (talk) 13:45, 26 March 2025 (UTC)[reply]
I was under the impression that if we have a field for a purpose, we shouldn't shoehorn the same purpose into a generic field, because then anyone parsing the source has to needlessly recurse further to figure out what was embedded. --Joy (talk) 22:36, 26 March 2025 (UTC)[reply]
I read your response three times and I don't understand it. Maybe this will help: Embedding {{Infobox historic site}} gives you a full-featured embedded child infobox that should cover all possibilities. Recreating and then maintaining a duplicate of all of that template's code here is a waste of resources and will inevitably lead to forking and confusion. – Jonesey95 (talk) 02:55, 30 March 2025 (UTC)[reply]
No, no, let me rephrase: if our parameter name is "designated", then it needs to cover any common meaning of the word "designated" - by any entity that reasonably does designations, not just one. Otherwise, we might as well have e.g. "coordinates" only cover some specific subset of latitudes and longitudes instead of the whole world, do you see how this would be weird? --Joy (talk) 10:54, 30 March 2025 (UTC)[reply]
I agree. That is why I suggested embedding {{Infobox historic site}}, which covers (or can easily be modified to cover) all reasonable designations. There is no need for us to duplicate that template's complex functionality here. – Jonesey95 (talk) 15:01, 1 April 2025 (UTC)[reply]
Ah, so basically convert a bit more than the parameter name, I understand now. The thing that confused me is your idea of using |module= specifically. I'd switch to a parameter named like |designations= or something like that.
Does the current list of parameters match that of the other one, or is there any mapping necessary? --Joy (talk) 18:40, 2 April 2025 (UTC)[reply]
It looks like we are talking past each other, which is easy to do in written communication. Instead of trying to understand your question, here are some links to examples of what I am talking about: South Manchester Synagogue, Gothenburg Synagogue, Stadttempel. – Jonesey95 (talk) 16:23, 3 April 2025 (UTC)[reply]
Nono, I understand that part, these three examples are all instances of transcluding this template with the use of | module = {{Infobox historic site | embed = yes | ... }}. What I'm asking is are there instances of this template being transcluded that use the local parameters named like designation1whatever where we have a discrepancy between the syntax of the historic site template or the designation list template and the syntax used here, where it's not trivial to convert? --Joy (talk) 20:23, 5 April 2025 (UTC)[reply]
I don't know. It looks like there are 252 articles that use |designation1= and 71 that use |designation2=. Someone would have to look through each of them. Happily, that's not very many. – Jonesey95 (talk) 12:32, 8 April 2025 (UTC)[reply]