Documentation+Wagn

Ideally, we document everything before we release. In reality, we haven't put enough person-hours to it to do that. Priorities:

  • Fix anything that's inaccurate.
  • ??

Some things we don't want to document very publicly, because we don't feel settled anough about them, or they're half-done. Does it make sense to include these "unadvertised" docs in the Tips section of relevant documentation, and make them readable by Wagneers?

 

PROPERTY: [OPERATOR, VALUE]

or

PROPERTY: VALUE (OPERATOR is "eq")

or
OPERATOR: VALUE (PROPERTY is "content")


RELATIONSHIP: CARD_DEFINITION

ARRANGEMENT: (depends on arrangement)


Properties - id, name, type, content
Operators - match, gt, lt, eq, ne


Relationships

compound name: part, left, right, plus, left_plus, right_plus
reference: link_to, linked_to_by, include, included_by, refer_to, referred_to_by
account: member_of, member, edited_by, edited

Arrangements
limit (number), sort (update, create, name, plusses), dir (asc, desc), view (see views)
 

Other:

alteration: append, prepend

extenstion: found_by

conjunction: and, or

Sorting by card content works, but so far only sorts on raw content as text, which works well for PlainText and Phrase cards if they don't begin with a link or inclusion. So:

/* {"type": "PlainText", "sort": "content"} */