Thread:Ffets/@comment-27219153-20170511211040/@comment-27219153-20170518232051

Ffets wrote: ...We don't have so many recipes per page...

I actually prefer them being all on one page, as it makes it easy to edit many recipes at once. Furthermore, having to write rather than  seems less intuitive to me. I think it requires more memorization (or if not memorization, looking up the names in pages), thus making it more difficult for the other users to use. Of course, those of us involved with this project will have a good understanding of what pages the recipes are on, but what about the users who aren't a part of this?

Example: "We have to take a decision, if the Gambeson recipes belong more to their respective armour, e.g. Dol Amroth Armour or on the Gambeson page."

Example 2: "Also, shall we keep the equipment recipes on the equipment pages, or distribute them onto the hoes/swords/pikes/daggers/etc. pages?"

My point is, that in cases such as these two, the user may not know which page to choose and may choose the wrong one. Then the user has to go to the page and see what they did wrong. For the gambeson, having a link to it from the Dol Amroth armour would allow for either pagename to be used and help to eliminate this problem. This would go on the DA armour page: |Dol Amroth Gambeson= However, when that logic is applied to every page, the list of pages which must be converted to templates expands significantly and its likely that several would get left out.

Ffets wrote: ...We could then have the "Orcish" crafting table on the Morgul Armour page, and then include it to all Orcish crafting tables...

I'm not quite sure what you mean, would you mind explaining it more?

Ffets wrote: ...Sorry Milk, that this means a lot of extra work on the Angmar table...

I know I just wrote several reasons to have the recipes on the table pages, but the work is not one of them. I really don't mind the extra work :)

''SamwiseFilmore wrote: ...Yeah. Better to change them again than revert and start over in my opinion. But if you want to revert, I trust your judgment.''

Indeed, I can do them all myself if and when its fully decided that the recipes should not be on the CT pages (except for the CT itself).

Ffets, I noticed for the armour recipes, you only used 'helmet' instead of 'Rivendell Helmet'. While just calling it 'helmet' might be simpler for the most part, it raises the question of what to do for armours with multiple helmets such as the Golden Rhûnic Armour. To me, this is just another case where it isn't as intuitive as I'd like it to be. Having the recipe named exactly as it is in game seems the most intuitive to me and easiest for users to learn.

This isn't directly related to the topic at hand, but rather than create a new thread, I'll bring it up here. In the armour recipes you've done, Ffets, you've changed the helmet, chestplate, etc. to be lowercase. I make Helmet capitalized because that's how it is in game, and I think this wiki should represent the game as closely as possible, even with little things such as capitalization in recipe tooltips. ''Note: This view only applies to grids, as it shows what the player would see when they hover over it in game. For article text, I think its good to have them lowercase for grammar's sake.''