Talk:List of methods
Table Structure
This is potentially a fantastic page but i feel it is organised poorly. I would like to propose a new layout that features the following columns.
Method : Puzzle : Type : Characteristics : (Year) Proposer
So for example the entry for Roux would be ...
Roux : 3x3 cube : Block-building : Speedsolving, fewest moves : (2003) Gilles Roux
What do people think?
Cubo
I think we need to be careful about making the table unnecessarily wide. Inserting puzzle and purpose in the table will cause a lot of unnecessary repetition, making the table wider, and less likely to be organized well. Headers encourage the information to be placed in blocks of similar methods (eg 3x3 speedsolving).
Perhaps adding the year it was invented would be valuable, but it would be better as a separate column rather than inserted as brackets.
The proposed 'Characteristics' column is too ambiguous (eg, 'looks cool' might be added here) - I would call it 'Purpose', and leave it in the table sub-headers. Methods generally have a main purpose, since they are often designed with a specific need in-mind. They may also be applied in other domains - almost all methods have lessons that can be used in fewest moves. For example block building in Roux is useful for FM, but doing the whole solve using Roux is not really appropriate. Roux's main purpose is speedsolving, so to avoid confusing beginners it should be called a 'speedsolving' method. Clicking on the method page can provide more information to indicate whether it may be used for other secondary purposes, with a bit more context. For example: "Roux is not an FM method, but familiarity with block-building used at the start may help the user in FM solving."
