Some components to display pull & stage opportunities; accessible from Toolbar
https://www.figma.com/file/BzfIRl7ewp3NPw4IvnZSBW/Engram?node-id=241%3A14354

Store information like:

• current ships
• connection state

https://www.figma.com/file/BzfIRl7ewp3NPw4IvnZSBW/Engram?node-id=80%3A253

The filetree component

• a heading with the user's id & a connection status symbol
• a file tree that lists documents & simulates folders
  - documents will be provided as a flat list, document names with a / will need to be rendered as being children of a folder
  - ex {folder-name}/{doc-name} should be rendered as {doc-name} in a folder {folder-name}

https://github.com/holium/engram/blob/ui/ui/README.md

• Urbit connection state
• Theme state
• Document State (the active document & prosemirror view)
• Version state (updates to pull and push for the active document)
• App state (availible documents and user information)

• users should be able to share access with other ships
• edit & view permissions
• groups

On shrunken view the expansion is adjusted to that specific view size.

a default page to display when no document is open

Since some of the code used to use font awesome, we still have that in the package.json, which causes issues when you try to install it from a non-developer computer (when we don't have the private key for our font-awesome account). As the frontend no longer uses this, we should ensure users don't have to access our token to install our document.

This is from a design for the stealth documentation site we are working on. The uppercase headers with gray text + the simplicity of the dropdown is why I am posting it.

• Functions to encode and decode documents into basic types

Build a react router;
key routes:

• root -- path: "/"
• document -- path: "/:id"

this will let us send modifications about the current document from anywhere in the app

When you create a document, the first time you open up the share panel it will not show you as having access to your own document (when it should be showing you as owner)

After I close and open the document again it now shows me as the owner of the document

When you first open a document, our code looks at the other ships to fetch the data that you need, so the data you missed since you last had the document open. We achieve this by gathering the Document state and the Settings state, however this misses one thing, the Update state.

Let me give an example scenario that I ran into during testing. We have three ships, all have already connected to the document before, but only two are open right now, lets say ~zod and ~bus. ~bus is writing changes and sending them to ~zod, but not adding it to its document state yet as ~zod is in the zone working. ~bus closes its document, so now the only place those changes are stored in is ~zods update set. Now if ~nut boots up the document, it will query the document state and settings from ~zod, however fail to gather any of ~buss changes.

Plausible Solutions:

1. We add the update set to the %init query for subscriptions
2. We find a way to auto-merge updates on the query into the doc state (I don't think this one is plausible as the %init arm never touches the frontend

https://developers.urbit.org/guides/quickstart/chat-guide
https://developers.urbit.org/guides/core/app-school-full-stack/8-desk
https://developers.urbit.org/guides/additional/software-distribution

Set up a way to serve the app over either http or ames (would require a ship)
///\ may require hosting a planet so it's up 24/7

• Table
• Video Embed
• Better Selection UX
• Block specific links & menus

When adding users to a whitelist, sometimes the Hoon backend logs a "bad wire" notification.

"Reached agent on wire"
/settings
"bad wire"
"Reached agent on wire"
/createsnap
"bad wire"
"Reached agent on wire"
/make
"bad wire"

This is accompanied by the frontend hanging and refusing to move the document away from the current one, however it is still receiving data in the console. There are no frontend errors that show up with the "bad wire" notification in Hoon.

Maybe adding margin-top: 16px; to #document-wrapper will be enough

• Header
  - [X] Title
  - [X] Description
  - [X] Meta
• Body
  - [X] Paragraph
  - [X] Heading
  - [X] Blockquote
  - [X] Aside
  - [X] Lists
  - [X] Checklist
  - [X] Inter-document links
  - [X] Inter-document embeds
  - [X] Images
  - [X] Basic Marks

https://www.figma.com/file/BzfIRl7ewp3NPw4IvnZSBW/Engram?node-id=80%3A253

• An editable document path
• Button for settings and placeholder buttons for version history, groups, and notifs

• Side Menu
  - [X] Plugin
  - [X] Component
  - [ ] Implementation
• Highlight Menu
  - [X] Plugin
  - [X] Component
  - [ ] Implementation
• Slash Menu
  - [ ] Plugin
  - [ ] Component
  - [ ] Implementation

• deterministic document merging

• intention preservation

• build XML CRDT

• build prosemirror binding

When creating a local file on 0xtimmy-development-unsub, the file is marked with a ~ (denoting that it is a remote file). This is incorrect as it is a local file, and thus should be represented with a dot.

All the documents shown in the following screenshot are local documents: