DocumentationEveryday use

Rust · 0.1.0

Write and manage memos

Capture a small thought, then decide where it belongs and who can read it.

Write the first memo

Open the workspace, enter a short note in the editor, and review its visibility before saving. Markdown, links and attachments can live in one memo. Add a descriptive tag when it helps future retrieval. A memo does not need a separate title to be useful; keep the first sentence meaningful.

An idea worth testing tomorrow. #ideas

- [ ] Make a small example
- [ ] Write down what changed

Edit, pin and archive

Use the memo's actions to edit its content, adjust visibility, pin it or archive it. Pinning helps keep a useful record nearby. Archival changes the memo state and removes it from ordinary active listings; it is different from deletion. Read the archive guide before using it as an organizational tool.

Check the result

After a slow or interrupted save, reload or search for the memo before creating another copy. An integration should likewise distinguish a failed response from a request that may already have reached the server. Keep private material private until you deliberately choose to share it.

A five-minute first-memo check

Use an account that can create memos. Start with non-sensitive text and choose PRIVATE before saving. Do not rely on a #private tag to set visibility. The following exercise also verifies that you can edit and find your own notes.

  • Create a memo containing “Documentation test” and #docs-check; save it once.
  • Reload the page and find the same memo by its text or tag.
  • Open its action menu, choose Edit, add a second sentence and save.
  • Open that memo again and verify both sentences and its PRIVATE visibility.
  • If the save response was interrupted, search before trying a second creation.