Bug 704156 - Style the navigation links around the topic
Summary: Style the navigation links around the topic
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Joshua Wulf
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 704161
TreeView+ depends on / blocked
 
Reported: 2011-05-12 09:53 UTC by Joshua Wulf
Modified: 2014-10-19 22:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-03 07:24:12 UTC


Attachments (Terms of Use)

Description Joshua Wulf 2011-05-12 09:53:37 UTC
The inspiration for the design is the Talmudic page.

ref: http://people.ucalgary.ca/~elsegal/TalmudL.GIF

The topic sits in the center. View traversal links are above and below, navigation links are to the side.

We will use X / Y positioning as a visual cue to the function of the link class.

Comment 1 Joshua Wulf 2011-05-22 23:40:49 UTC
<bforte> Jokes aside, I’ve long been a proponent of the Talmud as instructional design. To quote myself from an unfinished essay | article | blog post | something:
<bforte> The Talmud page as an organisational and structural element is a compelling argument for the limited canvas as a key element in information design. The human capacity to connect bits of information is limited, especially if some of those bits are moved out of sight. To sustain deep and wide information connections, put these bits into a single information space that can be comprehended as a single object.
<bforte> The Talmud page may be a consequence of technological limitation (although that’s not necessarily the case: the Talmud dates to when books and scrolls were in competition, making it likely they chose the page deliberately) but it’s still a brilliant use of a deliberately limited canvas to make complex arguments and dense information readily apprehended.


My note: scroll = screen


Note You need to log in before you can comment on or make changes to this bug.