This template is within the scope of WikiProject Infoboxes, a collaborative effort to improve the coverage of Infoboxes on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InfoboxesWikipedia:WikiProject InfoboxesTemplate:WikiProject InfoboxesInfoboxes
This template is within the scope of WikiProject Architecture, a collaborative effort to improve the coverage of Architecture on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ArchitectureWikipedia:WikiProject ArchitectureTemplate:WikiProject ArchitectureArchitecture
This template is within the scope of WikiProject Religion, a project to improve Wikipedia's articles on Religion-related subjects. Please participate by editing the article, and help us assess and improve articles to good and 1.0 standards, or visit the wikiproject page for more details.ReligionWikipedia:WikiProject ReligionTemplate:WikiProject ReligionReligion
This template was nominated for deletion. Please review the prior discussions if you are considering re-nomination:
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]
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.
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]