Board Thread:Wiki discussions and announcements/@comment-4881935-20141122052611/@comment-658634-20141123195557

Clari_S wrote: First, the database can be edited by anyone. It just that, not many people know how to edit it, or where. I'm sure when it is finish, the item page will have a direct link to the database, something like the current champion pages. There is this general thing among wikis that goes more or less 'regular users over specialists'. What I gather from your comment, you understand this and yet you suggest we go down this road. With a direct link to edit them from anywhere sounds really risky to get whole data corrupted or if editing link is show only on some places the if clause puts more (unneeded) stress to the server. Clari_S wrote: And second, you're putting a lot of unneeded extra writing on the item pages if you want the wiki to be pulling all it's information from the item template themselves. Not only are you writing what the item has, you also have to code it to inform what it doesn't have. Not really, the strain is the same as your 'database' pull. (I am a computer science major, that is not a database. More like a datasheet). Your example pulls a template that pulls a template that pulls a template that in turn pulls a template. By storing information to the article itself, you can distribute the data from the article anywhere with max two pulls. Plus its easier for regular joe to edit the article than go diving in datasheets and break something site wide in process. Or if the page would be protected, then you are limiting the 'everyone can edit' part. For the part of 'coding' of information that it does not have, I don't get. Neither method would store null (empty) information. Clari_S wrote: For the stat pages, question. No they don't, but I personally see people making poor judgement if they see an item like, listed as 80 AD, 3800g. Or just - 80 AD. There's a lack of stuff and it feels empty for me to look at. People do great judgments based on _relevant_ information. If a reader is reading about health then I find it most likely that the reader feels that everything else than how much health the item gives feels as a spam/irrelevant. Including everything everywhere is simply pointless and it makes articles heavy to read and load. Clari_S wrote: And for a tooltip suggestion, you do realize how hard it's going to read everything that will have to be fit within the small tooltip. I don't have any problems but then again, I have just one eye. If more info than that is needed, reader can head down to the actual article. Article that has only stuff under its header thus its small and thus fast to load thus making navigation a breeze thus making the site pleasant to use. Clari_S wrote: So no, we're not going to store the information on the item pages. It made be easier for the common user, but it makes the coder's jobs harder because now they have to actually pull out the right information without pulling out all the other additional information on the item pages, such as the trivial and patch history. Who are these 'we' as I am not voting for unnecessarily datasheets that make things too complex and heavy. Also why would trivia and patch information be pulled if not specially asked in the pull? I feel like you have copy&pasted the sheet idea from another wiki without knowing how it works under the hood.