Pinned pages

ScreenSpace Specifications

The row (41 passages, no note) of tabs (33 passages, no note) under the bar (28 passages, no note) of every page of the generated site (note: Site), holding the pages a reader (note: Reader) chose to keep: pinned (19 passages, no note) from the header (9 passages, no note) of a page, unpinned by hand, kept in the browser (31 passages, no note) from page to page and from one visit (3 passages, no note) to the next. Tabs, but chosen: nothing preloads, nothing closes by mistake, and the selection survives (3 passages, no note) a reload. The exploration trail that once followed the pages visited is gone, because it had no rule (note: Rule) to start over; the one breadcrumb (20 passages, no note) left is the filing (3 passages, no note) of the page.

Today

The header of an entity page, a keyword page, a meeting page, an API page or a document page carries, after the title, a "Pin" button drawn (23 passages, no note) as a chip (20 passages, no note) with a pin (note: Pinned page): pressing it pins the page at the end of the row, and the button, pressed (3 passages, no note) and reading "Pinned", unpins it. A page is never pinned twice. Without JavaScript neither the button nor the row exists, and the page stays whole: both are drawn by the script (37 passages, no note) of the island (note: Island) under the bar, which is served empty.

The row exists only once a page is pinned. It reads "Pinned", then one chip per page in the order of pinning, an order that never changes on its own, the page being read filled in the ink (3 passages, no note) and marked as the current page, every chip a link (note: Link) to its page with a cross (6 passages, no note) that removes (5 passages, no note) it, and the count, "3 pinned", at the end. Moving to another page leaves the row as it is; a reload, a new tab, a new session (note: Meeting) find it again. There is no cap: the row shows the chips that fit (3 passages, no note) and folds the others behind "+N", a summary (24 passages, no note) that opens the full list: the heading "All pinned" with the count, a filter (note: Facet) on the title and the space (note: Space), every pin as a row with its title, the space its identifier (note: Identifier) starts with and its cross, and "Remove all" at the foot (10 passages, no note), the one destructive action (10 passages, no note), asked for a confirmation. The chips are measured again when the window resizes.

The pins live in the local storage (3 passages, no note) of the browser under concordance-pins, as the identifier of each page and its title at the time it was pinned, so that a chip still reads once a later publication (40 passages, no note) removed the page; they never expire on their own, having been set on purpose, and never enter the address (56 passages, no note): nothing is fetched and nothing leaves the browser. The back button of the browser stays the way to step (note: Step) back: a pin serves to keep, not to return.

Objects

Actions

  1. Pin or unpin the page being read → entity page
  2. Open a pinned page → entity page
  3. Open a pinned keyword page (note: Keyword)keyword page

Rules

Properties5

Application
Generated site
Status
valid
Roles
Reader
URL pattern
/{source}/{path}

5 declared keys. The rest of the file is free text.

On this page4

  1. Today
  2. Objects
  3. Actions
  4. Rules
See the neighbourhood map6 pages6Neighbourhood mapPinned pages

Neighbourhood map Pinned pages

Distance1 hop

Neighbourhood map. The list below carries the same information as the map.existing pageword without a note

57 neighbours in total, more than the map shows.

textual equivalent

Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.