Glossary #73

Closed
opened 2018-05-24 00:11:29 +02:00 by kauffj · 1 comment
kauffj commented 2018-05-24 00:11:29 +02:00 (Migrated from github.com)

One of the resource documents we create should be a glossary.

This can be a simple table (or header/paragraph) structure that provides a technical definition of various terms, like outpoint, claim, claim id, sd_hash, etc.

It is important that each term be directly linkable. Definitions should be no longer than a few sentences, though it's appropriate to link to longer resource articles within those sentences.

One of the resource documents we create should be a glossary. This can be a simple table (or header/paragraph) structure that provides a technical definition of various terms, like outpoint, claim, claim id, sd_hash, etc. It is important that each term be directly linkable. Definitions should be no longer than a few sentences, though it's appropriate to link to longer resource articles within those sentences.
tzarebczan commented 2018-06-20 17:34:51 +02:00 (Migrated from github.com)

First take is live.

First take is live.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry.tech#73
No description provided.