◊(Local Yarn Code "View Ticket")

16:16 Closed ticket [10e20e5a]: Implement excerpts plus 4 other changes artifact: debcb1da user: joel
Implement excerpts ([10e20e5ab65]) check-in: 8af3b9ce user: joel tags: trunk
21:02 Ticket [10e20e5a] Implement excerpts status still Open with 3 other changes artifact: f9036e33 user: joel
19:37 Ticket [10e20e5a]: 4 changes artifact: f99a3894 user: joel
19:37 New ticket [10e20e5a]. artifact: 149403a2 user: joel

Ticket Hash: 10e20e5ab6515714652c41d400a7d0f83a6e82f7
Title: Implement excerpts
Status: Closed Type: Feature Proposal
Severity: Important Priority: Immediate
Subsystem: Resolution: Fixed
Last Modified: 2020-02-29 16:16:55
Version Found In:
User Comments:
joel added on 2020-02-19 19:37:19:

Articles should be able to specify the passage that will be used (or reused) as the excerpt in shortened listings. An inline excerpt would reuse an existing passage of the article or note as the excerpt. A non-inline excerpt would be filtered out of the article or note and only used in excerpted views.

A hypothetical ◊excerpt tag function would be passed through untouched in the doc and then snagged during the caching process in crystalize.rkt (similar to ◊note and ◊title).

If not supplied, an article or note's “excerpt” form would be the same as its “full” form. Excerpts will only be used when the note or article is too long to display fully in a listing context.

joel added on 2020-02-29 16:16:55:

Article excerpts are done with [8af3b9ce0c30051a].

Separate ticket [23e419df24ec51ea] for excerpts in notes.