• This forum is strictly intended to be used by members of the VS Battles wiki. Please only register if you have an autoconfirmed account there, as otherwise your registration will be rejected. If you have already registered once, do not do so again, and contact Antvasima if you encounter any problems.

    For instructions regarding the exact procedure to sign up to this forum, please click here.
  • We need Patreon donations for this forum to have all of its running costs financially secured.

    Community members who help us out will receive badges that give them several different benefits, including the removal of all advertisements in this forum, but donations from non-members are also extremely appreciated.

    Please click here for further information, or here to directly visit our Patreon donations page.
  • Please click here for information about a large petition to help children in need.

Implementing Wikipedia's {{Reflist}} template

Messages
10,776
Reaction score
9,664
I think the VS Battles Wiki should update its current {{Reflist}} template to reflect that of Wikipedia's, which can accomplished through Wikipedia's handy Transwiki guide.

The current {{Reflist}} template's syntax is heavily restricted in its functionality, only allows for multiple columns (of varying widths) and only rendering the default references; the option to render additional reference groups is not even available. However, the proposed updated template's syntax allows for:
  • (1) multiple columns (of varying widths);
  • (2) grouped references and, thus, multiple uses of {{Reflist}} rendering unique reference groups; as opposed to being restricted to the <references> tag hooks, which lack the accessibility and customization features of the {{Reflist}} template, when rendering alternate reference groups;
  • (3) list-defined references, which allows user to define references (via <ref name>) within {{Reflist}} itself and then invoke them in the body text of pages (via <ref name="name1" /> or {{r|name}}), thus simplifying the process of referencing sources and minimizing clutter in the body text;
  • (4) list styles, which control how both the reference list and footnote markers are rendered, simply offering alternatives to the default numbered citations;
  • (5) pre-defined groups, which automatically assign list styles to reference lists and markers;
  • (5) footnotes (via {{Efn}} and {{Notelist}}), which allows you to easily insert explanatory footnotes separate from references;
  • (6) nested references (via {{r}} or {{Ref}}), which allows you to insert references and footnotes within one another.
 
Last edited:
Please explain further what you mean and what benefits this would bring.

We already have a {{reflist}} standard template, for example. 🙏
 
Please explain further what you mean and what benefits this would bring.

We already have a {{reflist}} standard template, for example. 🙏
The basic function of the {{reflist}} template does not change with the proposed revisions, even after modified to reflect the Transwiki guide. The only significant difference is simply the addition of a new set of pre-defined reference groups (i.e., markers which stylize the label representing individual references) like (and alongside) the pre-existing default reference group, which renders the labels as basics integers [1]. For example, the "lower-alpha" group renders labels as the lowercase English alphabet [a], whereas "upper-roman" renders labels as uppercase Roman numerals [II]. They simply add more visual diversity with easy access.
 
The basic function of the {{reflist}} template does not change with the proposed revisions, even after modified to reflect the Transwiki guide. The only significant difference is simply the addition of a new set of pre-defined reference groups (i.e., markers which stylize the label representing individual references) like (and alongside) the pre-existing default reference group, which renders the labels as basics integers [1]. For example, the "lower-alpha" group renders labels as the lowercase English alphabet [a], whereas "upper-roman" renders labels as uppercase Roman numerals [II]. They simply add more visual diversity with easy access.
Hmm. I personally think that we should stick to a standard formatting style as much as possible, and that {{reflist}} and {{reflist|2}} seem sufficient for most reference sections, with a scroll bar added if it is absolutely necessary.

I still do not understand the benefits of your suggestions. My apologies. 🙏
 
I personally think that we should stick to a standard formatting style as much as possible, and that {{reflist}} and {{reflist|2}} seem sufficient for most reference sections
The current {{Reflist}} template's syntax is heavily restricted in its functionality, only allows for multiple columns (of varying widths) and only rendering the default references; the option to render additional reference groups is not even available. However, the proposed updated template's syntax allows for:
  • (1) multiple columns (of varying widths);
  • (2) grouped references and, thus, multiple uses of {{Reflist}} rendering unique reference groups; as opposed to being restricted to the <references> tag hooks, which lack the accessibility and customization features of the {{Reflist}} template, when rendering alternate reference groups;
  • (3) list-defined references, which allows user to define references (via <ref name>) within {{Reflist}} itself and then invoke them in the body text of pages (via <ref name="name1" /> or {{r|name}}), thus simplifying the process of referencing sources and minimizing clutter in the body text;
  • (4) list styles, which control how both the reference list and footnote markers are rendered, simply offering alternatives to the default numbered citations;
  • (5) pre-defined groups, which automatically assign list styles to reference lists and markers;
If the page only has references, then the current template is sufficient, yes, but for more in-depth and thoroughly researched pages—such as Explanation Pages or blogs and Verse-Specific Powers and Abilities, requiring references, notes, explanations, etc.—the current template's limited flexibility becomes a hinderance.
 
I think this should have been in the OP
The current {{Reflist}} template's syntax is heavily restricted in its functionality, only allows for multiple columns (of varying widths) and only rendering the default references; the option to render additional reference groups is not even available. However, the proposed updated template's syntax allows for:
  • (1) multiple columns (of varying widths);
  • (2) grouped references and, thus, multiple uses of {{Reflist}} rendering unique reference groups; as opposed to being restricted to the <references> tag hooks, which lack the accessibility and customization features of the {{Reflist}} template, when rendering alternate reference groups;
  • (3) list-defined references, which allows user to define references (via <ref name>) within {{Reflist}} itself and then invoke them in the body text of pages (via <ref name="name1" /> or {{r|name}}), thus simplifying the process of referencing sources and minimizing clutter in the body text;
  • (4) list styles, which control how both the reference list and footnote markers are rendered, simply offering alternatives to the default numbered citations;
  • (5) pre-defined groups, which automatically assign list styles to reference lists and markers;
If the page only has references, then the current template is sufficient, yes, but for more in-depth and thoroughly researched pages—such as Explanation Pages or blogs and Verse-Specific Powers and Abilities, requiring references, notes, explanations, etc.—the current template's limited flexibility becomes a hinderance.
From all those number (3) does sound useful even more so when we talk about ref with values linking to a calc or if an ability/power requires multiple links to explain, it can be hard to apply changes sometimes as it gets really long links in the mid of the words.
Aside that I don't really see much use for this maybe (2) could be of some use but I think it's not really needed.
 
Hmm. I unfortunately still do not quite understand everything with the limited time I have available, but I am concerned that we would make our wiki even more disorganised and confusing to edit, but maybe my resistance to change is too strong?

Also, do you know exactly how to edit our {{Reflist}} template so it allows for higher flexibility?

@AKM sama @DontTalkDT @Mr. Bambu @DarkDragonMedeus @Just_a_Random_Butler @Agnaa @Celestial_Pegasus @Ultima_Reality @Elizhaa @Qawsedf234 @Damage3245 @Starter_Pack @Abstractions @Colonel_Krukov @SamanPatou @GyroNutz @Firestorm808 @Everything12 @Maverick_Zero_X @Crabwhale @GrathOfLux @Dereck03 @Planck69 @LephyrTheRevanchist

What do you think about this? 🙏
 
If this is all backwards compatible, I see no harm in principle. That said, I also don't really get how to implement this on fandom. But that might just be because I never messed with the background code much.
 
Seems fine, if it turns out to be bad we can just undo it. How would we implement it?
 
What if we did more coding for it if it was bad? Would we place it at the bottom of pages?
?????????????

Why would we force it at the bottom of pages if it doesn't suit our needs?

Just revert it to the current one which does fine.
 
How would we implement it?
The Transwiki guide includes a list of (almost) everything required.

Copy and transfer the following Templates:
Copy and transfer the following MediaWiki pages:
Copy and transfer the following Modules:
All of the MediaWiki extensions required are already installed in our Wiki, apparently.
 
Hmm. That seems like a lot of rather confusing work. I do not want us to apply any drastic changes that we do not know the full consequences for, especially given that I think our current system seems to work fine.

@Just_a_Random_Butler

What do you think? This seems to be your area. 🙏
 
?????????????

Why would we force it at the bottom of pages if it doesn't suit our needs?

Just revert it to the current one which does fine.
I wasn't saying anything about forcing it; I was asking whether it'd go at the top or bottom of pages.
 
It would go the same place as it is now, and the same place as it is on Wikipedia; the bottom of pages.
 
Please wait at least twelve hours from the last post to bump.
 
Eh sure I can move it.
 
Back
Top