Template talk:Aboutfile

Fields

What fields should we include in this template? character? location? Tacopill (talk) 12:34, 24 July 2023 (UTC)

Those two sound good. They're not all enemies. Some might also be of book or game covers, or merchandise, or game items. That may help too. Mysthalery (talk) 22:09, 24 July 2023 (UTC)

I grabbed the categories on the Main page (Characters, Enemies, Games, Items, Locations, Mechanics, Music, PSI) and added them to the mix. Tacopill (talk) 22:19, 24 July 2023 (UTC)

Use and function

This is not a very useful aboutfile template. I would prefer to use the TMWA version I have implemented on Inkipedia (here) and other sites. The reasons for doing so are as such:

1. The existing File template is not well utilized as is. Moving to a new form and more strictly enforcing its use will ensure that all files actually follow the same protocol when on the site.
2. The existing File template isn't that useful. Nothing is automatically linked, which means there is no significant advantage to using the template as opposed to just writing a sentence or two for the description. Even then, there's not a lot of information that is necessary to describe the image. Enemies, Items, Locations, and Mechanics are all things that could be described in the description or included in the new "type" structure of the template.
3. TMWA File makes your job a whole lot easier. This is the main meat of the argument: TMWA File will automatically categorize and license files based off its parameters. Instead of having to remember a dozen or more categories offhand, or needing to search around, by entering the simple parameters, the template does it for you. Gone too are the days of needing to make a second header and section and template for licensing an image, where the file will automatically list it appropriately. Instead of having 10 to 12 templates to remember for files, get it done with just one.
4. TMWA File is pretty easy to learn. My template is as straightforward as it can be. The "Game", "Description", and "Type" sections do not require much difficulty in explaining what they do. The game is X. The point of the image is Y. The form of the image is Z. Everything can be deciphered by looking right at the file itself.
5. It's more text optimized. This is pretty minor, but fewer characters per file would add up a little bit over time.
6. It's super customizable, and broad changes apply quickly. Is there a type or automatic linking that needs to be done? It can always be easily added and would therefore enable consistent use on all files. Furthermore, if an existing change needs done (say that a category name gets moved, instead of needing one massive text replace, a simple small tweak is made here instead.
7. Places a greater incentive to properly source and attribute files, and other maintenance. This will be a great opportunity to flag images that are of low quality, use unused files, remove or replace duplicate images, and to really nail down as many linked or attributed sources for files as possible.

There are a few minor inconveniences:

1. It does get a little more complicated. Lua is tricky to utilize for the average user, and so some training may need to be necessary to help out other people make changes to the module.
2. You can't automate retroactively updating files. They're all going to need updated. Manually. I am happy to do every last one, and I know I can do it because I've done this several times already. I am still working to update StrategyWiki, which also use the template, as well. That said, it would be much cooler if people could help. I am happy to make resources to chip in, but it overall does create a lot more of Things To Do.
   

Let me know what y'all think. Trig - 18:16, 24 August 2023 (UTC)

So broadly, I've ported it over to demonstrate what it would look like/how it would function. The code can be found at Module:File; the examples at User talk:Trig Jegman/Sandbox. Documentation isn't up yet, but is very similar to how it would appear on Inkipedia.

One major change is that a lot of the existing parameters (characters, enemies, locations, items, mechanics, music, and PSI) are converted to either be covered by directly writing them into the description or uses the new "type" parameter to categorize and indicate them instead. I think this is a method that is more effective in being descriptive, as well as useful for navigation. Please let me know how you feel about these changes, and if you'd be interested in implementation. Trig - 16:47, 20 October 2023 (UTC)