Data Model

[vorg]

Client - Server

• Client runs local copy of PouchDB with text only data
• Server runs master copy of CouchDB with text only data
• Server runs another CouchDB with images or a file server

  Data

Everything is the same type of object

Item

• id : String - id of the item
• pid : String - id of the parent item or null for root nodes
• text : String - the text or title of the item
• tags : String[] - tags of the item
• attachments : String[] - list of attachment IDs

  Discussion

• Are tags a separate thing or just part of text e.g. "Update CSS on my website #todo #bug @next"
• One attachment per item? Create subitems if you want more?
• Workflowy has also note field. We could add markdown support there.
• Metadata or custom attributes e.g. @url(http://variable.io) for bookmarks, @x(100) @y(300) for canvas mode, @due(2015-10-10) for reminders, @date(2015-10-01) creation date

[vorg]

Use case: Bookmark

Minimalistic:

{
  "text": "Marcin Ignac @url(http://marcinignac.com) @date(2015-10-11)",
  "tags": ["data", "visualization", "generative", "art", "portfolio"],
  "attachment": "a9ec723260234db51fb4013924ceae42_screeshot.png"
}

With attributes expanded:

{
  "text": "Marcin Ignac",
  "url" : "http://marcinignac.com",
  "date" : "2015-10-11",
  "tags": ["data", "visualization", "generative", "art", "portfolio"],
  "attachment": "a9ec723260234db51fb4013924ceae42_screeshot.png"
}

[vorg]

Use case: Long note

A. Markdown powered node attribute:

{
  "text": "My thoughts about data driven art",
  "tags": ["data", "art"],
  "note" "# Data art\n\nLet's start by comparing data art to data viz..."
}

B. Every paragraph is a separate node:

{
  "id: "1",
  "text": "My thoughts about data driven art",
  "tags": ["data", "art"]
},
{
  "id: "2",
  "pid: "1",
  "text": ""# Data art",
},
{
  "id: "3",
  "pid: "1",
  "text": "Let's start by comparing data art to data viz..."
}

[nicknikolov]

A note could be this box... http://prosemirror.net/demo_markdown.html