[wp-meta] [Making WordPress.org] #6761: Enhance UX of navigation in archive pages

[Making WordPress.org]

#6761: Enhance UX of navigation in archive pages
--------------------------------------+----------------------
 Reporter:  tresorama                 |       Owner:  (none)
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Make (Get Involved) / P2  |  Resolution:  invalid
 Keywords:                            |
--------------------------------------+----------------------

Comment (by tresorama):

 > Those sites are built on a theme called P2. It is intentionally designed
 to allow quick posting, commenting on the front page, and other
 interactions outside of the single page. Additionally, it has a number of
 features designed to allow cross posting and @ addressing of users, among
 other things.
 >
 > In other words, not showing titles is intentional, because posts made
 with it may not actually have titles. Showing the full content and
 comments on the front page, as well as on "archive" pages, is intentional
 as well. P2 is a theme for collaboration and working together on projects,
 not necessarily for reading as a blog.

 Slack and Github Issues could be better suited for discussion.
 I would use Slack and Github Issues for internal collaboration.
 And wordpress.org for publish condensed news, and receive external
 feedback.

 I don't see the point to discuss in two places, it can be source of
 confusion and require manual sync.
 But maybe it's just me and it's not my intention to be rude.

 **In my opinion a new entry in the community should be able to travel back
 in time in official press and study the entire system.
 It will reduce time to being an active member.**

 ----

 == New Proposed Change - Compact View

 Let user toggle between compact and an expanded view.
 You can see it live right now by using this bookmarklet
 [https://codesandbox.io/s/wordpress-org--enable-compact-view-j0ysjg Get
 the Bookmarklet]

 I did this for myself, and i share here for exploration and posterity.
 It's a ''bookmarklet'', that injects a ''button'' in the page at the top
 that toggle "post content" visibility via css.

 This could be implemented in the website without a theme  redesign.
 Maybe under the "Keyboard Shortcut" panel.

 For me this is a good compromise, it's not a breaking changes and the
 consumer can decide if use it or not.

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