Template talk:Infobox grapheme

This disaster infobox
levels some good criticisms of this template, above, but unfortunately any effort to improve it seems to have stalled, and anyway even in the sandbox version I'm not sure the biggest issues have really been addressed.

I'm NOT a subject-matter expert, but to provide a layperson's perspective (something that, it seems, is sorely needed here), the infobox just seems overwhelmed by questionably-useful cascades of apparently-related glyphs, presented absent any useful context and rendered (due to the default 88% font size for Infobox text) too small to really appreciate (or even make out, in some cases). But honestly, I feel the bigger problems are with not the template itself, but the input being provided to it on the various articles where it's used. Guidance, more than design effort, may be what's really needed.

I get why the "Ancestors" hierarchy is presented as a nested bulleted list, and presumably it's at least possible for certain graphemes to have a more complex ancestry than the simple linearly-increasing indentation found on articles like A or J.

But why are the "Descendants" and "Sisters" presented vertically (descendants with bullets, sisters without), when all it does is waste a ton of space and stretch the infobox far down length of the article? Why are the "Phonetic usage" items presented symbolically (and, again, wastefully-vertically), when the articles those symbols link to have actual, descriptive titles that are, most likely, far more meaningful to the average Wikipedia reader?

Surely at least "Sisters", and probably "Descendants" as well, can make use of to present their respective series of glyphs in a more compact manner? Aesthetically, it feels like an easy fix, to trade one of these for the other:

(Combining the three representations of Aleph — presented on three separate lines in the original format — into a single, space-separated hlist bullet item also helps make it clearer that, just like Ա and ա, they all link to the same article.)

Regarding the phonemes. (And I now see that the IPA notice at the bottom isn't conditional on there being arguments to the phonemes parameter, when it obviously should be. ...But that's a relatively simple fix.) With the phonemes, as I was saying above I suspect it might be more helpful to readers if we're less conservative in how we present those links, and instead include the actual title of the article that's represented by the symbol (in addition to the symbol). That may require the templates that create those links to support, and output, an "expanded form" for cases (like these) where the symbol isn't being used to represent itself, but rather is actually meant to represent the article about itself. i.e... →

That could be achieved with a simple adjustment to Module:IPA symbol and the family of templates that call it — say, perhaps, a new title parameter, so that  transforms  into. FeRDNYC (talk) 18:31, 30 April 2023 (UTC)


 * Actually, I see now that the "real" A presents those items in a nicely-formatted s, which solve that issue. But not all of the letter articles follow suit (J looks much like the A samples here), so I guess what's really needed is for editors to go update the rest of those articles to emulate A.
 * Actually, I guess it's not possible, because the way the fam N cascade is implemented, the hierarchy is fixed to only descend linearly. So, now we're back to that being of questionable usefulness.
 * Those issues aside, I've created a new version of the template in the sandbox. (Overwriting the prior work did, with regret — but it's still in the history!) My version fixes some of the actually-technical issues I found with the template:
 * Display of the is now conditional on there being arguments to the phonemes parameter
 * The cascade logic for the fam N parameters is now markedly simpler and more intelligent. The original implementation had it so close to correct, but whoever wrote it failed to realize that if both the opening and (in reverse) closing of each level of the list hierarchy were made conditional on each parameter level being present, then the final, central self-reference only had to be written once, and it would always end up at the correct level. So, now, that's how it works.
 * I fixed the spelling of to be, so that parameter can actually work now. (Or, will if the sandbox is taken live.)
 * Like, I removed the brute-force categorization (though it was already in a noinclude, and therefore pretty pointless anyway). While I considered adding a wrapper and bringing it back to mainspace, as the docs for that very template note that isn't supported by the guidelines. Best to just skip it.
 * I'll write some additional test cases for the aspects I changed, and change the sample content to match A in its use of . Hopefully then, more editors will be inspired to spread that feature to the real mainspace articles that could sorely use it. FeRDNYC (talk) 20:10, 30 April 2023 (UTC)
 * Thank you very much for taking up the initiative of improving this box. I'm afraid I lacked the energy to go through with it last time. But yes, please do go ahead with any restructuring you see fit; this already looks a lot better. Fut.Perf. ☼ 08:43, 1 May 2023 (UTC)
 * OK, I've had some more time to spend on this:
 * I completely refreshed the test cases formatting and content. They now use to show the two infobox versions side-by-side, they're y so they'll fold up automatically when the sandbox output matches the live rendering, and the actual code passed to the test transclusions now borrows "best-practices" code from the live A article at the time of this writing, so that the test is more representative of what the infobox should look like in the wild.
 * In the sandbox, I added y to the transclusion, so now headings that don't contain any rows will be suppressed completely. An example can be seen in the second testcase.
 * I also changed how the Development infobox item renders, so that unless at least fam1 is set in the transclusion, Development will be completely suppressed, instead of just uselessly repeating the infobox title. Again, the second test case demonstrates the effects.
 * I think the sandbox is pretty much ready to go live, now, but I'll hold off a bit in case anyone objects / notices any issue I missed. FeRDNYC (talk) 22:22, 3 June 2023 (UTC)
 * I also changed how the Development infobox item renders, so that unless at least fam1 is set in the transclusion, Development will be completely suppressed, instead of just uselessly repeating the infobox title. Again, the second test case demonstrates the effects.
 * I think the sandbox is pretty much ready to go live, now, but I'll hold off a bit in case anyone objects / notices any issue I missed. FeRDNYC (talk) 22:22, 3 June 2023 (UTC)

Change/alias letter= parameter
It's pretty interesting that this avoiding being titled Infobox letter, but trips on a rake in the parameters. I think we should change the letter parameter to grapheme, and have letter (etc.) be an alias. Remsense 诉  16:23, 16 June 2024 (UTC)