[wp-meta] [Making WordPress.org] #2191: Support Theme: Sub-forums are not discoverable

Making WordPress.org noreply at wordpress.org
Fri Nov 11 22:04:54 UTC 2016


#2191: Support Theme: Sub-forums are not discoverable
----------------------------+------------------
 Reporter:  Clorith         |       Owner:
     Type:  defect          |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by bcworkz):

 mapk's suggestion of including a link in the description is a good, easy,
 quick fix, but it doesn't really address the ramifications of having
 hierarchical forums in the first place. For one thing, such a link does
 not give us a description of what that sub-forum is for, and including a
 description in the parent forum's description would be confusing.

 On a basic level, the grid layout of forums does not lend itself to
 hierarchical forums at all simply because there isn't room, and making
 room would add a lot of whitespace to forums without sub-forums.

 To be consistent with a hierarchical structure, if there was to be a sub-
 forum link anywhere, it should occur below the main forum's link. This
 does not solve the lack of space problem for a description. That could be
 solved with a fly-out box triggered by the sub-forum link instead of going
 directly to the sub-forum. The fly-out would be a replica of a forum's
 grid content, except it would be for the sub-forum. The image below
 illustrates the concept. Forgive the graphics, that's not what I'm
 suggesting, consider only the concept.

 I see flaws with this concept as well, but I'm throwing it out there in
 hopes it'll trigger a better thought in someone. I actually support not
 having hierarchical forums at all, but as Clorith said, the ability to
 support hierarchy should be in place.

 [[Image(https://lh3.googleusercontent.com
 /l_Xpr6nEnwI2mqaNkJRYxL5XyaL7dbirv9MXj1XuplnYGxmjmP3InOlBPZakZ9AKM44UCefYp3J603MqWXpFSASAid0rmKqSw-
 SUarnz-
 7Y0Uk3VgPi4iKrrzSV2tSVTSlU5Kscdui850mS4lCPG3rWGi71VS7dRTgsVqbFeMjDwhAFhuDOqfJ41RX42XgFKThET3UnUMQtXkb1CwyOm682geJKLpdm99f
 --P_gilnoANNXDfbP2VUqD3GY7JqIfyar-
 6OIKbQve8rmEwp_kxLkl83OSV0CKcaWUvOBTzNySTLEruDexHOuhc70D8xmVbKyvrOzQNTdkZVVCCFNg9cxweYL69dWEhnPC58xKpGRnROX2P0VtlF40WIbmm8QoaXgEKESklY3zpBj1Lb3O87WTMdArw2EBm59anGxYVfh4a9YxV-
 U_hzYB4JNhbh6vtasETBdfVz2mkvfdJBp2XfH9rW1Gy8dIZBal0nzuF7wsJiGoohrEga3Eog1XksEoE09Zcb80VF9UMEbySOwao_Vg8Yu0JOgvGoxRINTk1B0A3fzPUTGkBKEL1AmNQstEZDEJ8D0ToEwSnZpPz_wqpCorut-
 EVt4dN34T-XO2cePffy0l=w556-h504-no)]]

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/2191#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list