User blog comment:Emitewiki2/A new project!/@comment-1455034-20150620164712/@comment-4628859-20150624150352

The point I'm trying to get across is that the file names in their current states do not harm finding images. I say this because the most obvious way to find images is to go to the specific page which would not involve knowing the file name but what the image looks like. Now if the user doesn't know the page's specific name, they would most likely go to the template and then find the link and go to that (I state this only to avoid having to state this later).

Now with the naming system proposed, the primary usage of it is to find existing files, right? These files are categorized by the game they come from, then their component type, and finally their name. In order for this system to work, the user needs to know the specific game and then the component type and — as you pointed out – then they complete the rest of the file name themselves. However, the very fact you stated this implies that the users using this system would have prior knowledge of the subject they are looking for.

What else uses the game name and component type to help users find things? Game templates! Everything about a game is organized in its template and divided by its component type! Now if the user knows the game name and the component type, which is implied they would know in order to use the file system, they have everything they need to use the template, to find that page, to find the image – which they know is there because they have prior knowledge of it!

This seems like the most logical pattern to me, making standardizing file names unnecessary.

As for that part you wanted explained, I was saying that with the standardized naming of images only would include the game name and the article name, not that the files today include them. That paragraphs point was explained in the below sentence, which, for you information, is actually all one paragraph.