Memo authoring and browsing UI
The memo UI lets a person write, find, read, change, and discuss memos in one web flow. It joins shared Markdown writing and reading with memo feeds, filters, saved views, attachments, relations, comments, reactions, and detail navigation. See Web application experience for the wider web shell, Web settings and account management for account-level editor choices, Calendar and temporal memo views and Map-based memo exploration for other entry points, and Memo lifecycle and collaboration for server-side memo behavior.
Memo workspace
The memo workspace is the main place to create and scan notes. Home, Explore, Archived, profile, and saved-view collections use the same memo-card language, while a full route provides a focused view of one memo.
Memo collections
Home places the signed-in person's composer before the personal memo list. Explore shows memos that the visitor can access, and Archived shows the person's archived memos. A card opens the detail route with its source collection preserved, so returning from a memo keeps the person in the right context.
The main workspace flow connects collection entry points to cards and then to either a full memo route or a shared read-only route.
flowchart LR
A[Home] --> C[Memo collection]
B[Explore or archived view] --> C
D[Saved view or profile] --> C
C --> E[Memo card]
E --> F[Memo detail]
E --> G[Shared memo view]
References: web/…/Home.tsx• L15-55 web/…/Explore.tsx• L8-37 web/…/Archived.tsx• L8-31 web/…/index.tsx• L73-101 web/…/MemoEditor.tsx• L108-146
Memo feed presentation
The feed keeps reading content in bounded columns on wide screens and uses one normal document flow on narrow screens. The composer, active filters, loading state, empty state, and route-specific leading content remain at the start of the collection.
The feed loads more pages near the end and also fills a short first page when the viewport still has room. A newly saved top-level memo appears at the front until the normal query catches up. An initial failure replaces the list with recovery actions; a later failure keeps loaded memos visible and offers retry.
References: web/…/PagedMemoList.tsx• L28-32 web/…/PagedMemoList.tsx• L58-120 web/…/PagedMemoList.tsx• L122-183 web/…/PagedMemoList.tsx• L185-251 web/…/MemoListError.tsx• L15-65 web/…/MemoDisplaySettingMenu.tsx• L43-57
Memo discovery
Discovery narrows a large memo set into a useful reading set. Quick Find, filter chips, URL filters, and saved views share the same collection filter state, so a person can refine a list and return to it later.
Search and filter controls
Quick Find accepts words and turns them into content filters. On a memo collection route it keeps the current scope, such as Home, Explore, Archived, or a profile. From another route it moves the search to Home. Active filters appear as removable chips above the list.
Filters can live in the URL, which makes a result restorable and shareable. A route change without a filter in the URL clears the previous filter so one collection does not silently affect another.
References: web/…/QuickFindDialog.tsx• L15-21 web/…/QuickFindDialog.tsx• L30-68 web/…/MemoFilterContext.tsx• L23-47 web/…/MemoFilterContext.tsx• L65-101 web/…/MemoFilters.tsx• L64-105
Saved memo views
A saved memo view is a named collection rule that a person can reuse from the sidebar. The view manager offers examples and filter-field help, checks the filter expression before saving, and supports later edit or delete. Selecting a view applies its rule to the current collection, or returns the person to Home when selected elsewhere.
The built-in Tasks view provides a ready-made way to find memos with task lists and unfinished tasks. A deleted view is also cleared from the active filter when it was selected.
References: web/…/MemoViews.tsx• L45-219 web/…/MemoViews.tsx• L268-305 web/…/MemoViews.tsx• L310-493 web/…/AppSidebar.tsx• L104-177 web/…/useMemoFilters.ts• L75-125
Memo authoring
The composer supports quick entry in a feed, an expanded writing view, new memos, edits, and comments. It gives each action the same Markdown language and the same controls for content, audience, associated items, and saving.
Memo composition
web/…/MemoEditor.tsx is the shared entry point for viewing a memo, editing an existing memo, composing a new memo, and composing a comment. It loads the editing session only when needed, while the read-only view remains available during loading. Its read-only and editing surfaces use the same @usememos/editor binding and standard Markdown storage, so a memo stays consistent between writing and reading. Unedited blocks retain their saved form, while edited blocks use the editor's normalized form.
MemoMarkdown is the common memo-aware editor surface. It applies the memo Markdown dialect, labels, theme, attachment URL policy, and tag and mention decorations in both read-only and editing modes. Task items can be changed while a memo is read-only when the host allows task toggles. (See web/…/MemoMarkdown.tsx.)
The editor supports formatting, headings, lists, code, tasks, links, math, mentions, tags, emoji, and Mermaid content. A source mode lets a person edit the whole memo as Markdown text. It turns off rich editing controls and stores the choice in the person's account editor setting, so the preference applies across composers and devices. Focus mode expands the writing area to fill its frame without changing the memo content.
Tag completion uses the person's known tags. Mention styling and links apply only to known people, and lookup waits briefly after typing stops. In read-only content, known tags can also be reached and activated with the keyboard when the host provides tag navigation. Files can enter by paste, drop, or the insert menu. Pasted files become attachments, while dropped images can be placed where they land in the text. Uploads started in the text show progress at their source position and offer retry or attachment fallback if they fail. The editor also supports keyboard save with Meta+Enter or Ctrl+Enter and context-based suggestions for new top-level memos. Suggestions can add tags, a task list, or an allowed visibility. Suggestions disappear after acceptance and do not return during Undo.
The insert menu gives one place to add an attachment, insert an image at the caret, create a drawing, record audio, link another memo, or set a location. Attachment upload and inline image insertion are separate actions, so a selected image can keep its place in the memo body while other files remain associated content. The menu also exposes focus mode and Markdown source mode when the host permits the focus control. A drawing opens in a separate editing sheet and returns to the draft as an image attachment. Recorded audio shows a live waveform while it is captured. It can become an attachment or, when transcription is available, text in the draft. Existing audio attachments can also be transcribed without changing the source file. A new memo can receive a suggested creation time from a calendar context, and the timestamp control lets a person adjust creation and update times before saving. Invalid date values remain marked until corrected. (See web/…/InsertMenu.tsx and web/…/TimestampPopover.tsx.)
References: web/…/README.md• L3-7 web/…/README.md• L26-30 web/…/README.md• L48-54 web/…/MemoEditor.tsx• L17-34 web/…/MemoEditor.tsx• L108-146 web/…/MemoEditor.tsx• L150-241 web/…/EditSession.tsx• L252-293 web/…/InsertMenu.tsx• L125-176 web/…/AudioRecorderPanel.tsx• L10-100 web/…/EditorSuggestions.tsx• L49-135 web/…/VoiceWaveform.tsx• L8-33 web/…/TimestampPopover.tsx• L15-23 web/…/useMemoDecorations.ts• L25-34 web/…/uploadAnchors.ts• L32-71 web/…/editor.css• L75-87
Memo editing surfaces
An editing session places the Markdown editor inside the presentation chosen by its host. An inline session can enter focus mode and become a centered sheet with a backdrop, while a hosted session starts in that layout and lets its host close it. The session keeps the page layout stable when the sheet is fixed and restores page scrolling after it closes.
The same session can appear inside a memo card, in a normal page composer, or in a host-owned full-screen surface. Focus mode reserves the session's old space, fills the sheet with the writing area, and uses a short view transition when the browser supports it. Reduced-motion settings disable that animation. A hosted editor does not show a second focus-mode toggle because its host owns the frame.
Source mode changes only how the Markdown is edited. The editor labels the mode, hides rich block controls that do not apply to source text, and keeps the document content unchanged when the person switches modes. The mode is read from the account editor setting and updates it immediately; if the setting update fails, the prior mode returns and the error is shown. The insert menu marks Markdown mode with a code icon and keeps it available in every composer.
References: web/…/README.md• L38-54 web/…/README.md• L68-76 web/…/EditSession.tsx• L109-125 web/…/EditSession.tsx• L236-245 web/…/EditSession.tsx• L313-381 web/…/EditorToolbar.tsx• L39-61 web/…/InsertMenu.tsx• L164-176 web/…/constants.ts• L1-9 web/…/editor.css• L8-73
Memo metadata
Metadata adds context that text alone cannot provide. A person can add attachments, place visual media in the text, create or edit a drawing, link another memo, choose a location, set a timestamp, and choose an audience or Space when the memo type allows it.
When a person links a memo, the link dialog searches memo content after a short pause. It excludes the current memo and marks existing references as unavailable, so a person can add a new reference without creating a self-link or duplicate relation.
The audience menu combines visibility with optional Space placement. A top-level memo may choose a Space when the person can manage that placement, while a comment inherits its parent's Space. Removing a Space-only placement returns the memo to Private. Duplicate Space titles show a short identifier so the destination stays clear, and a placement that is no longer in the member list remains available for removal. If Spaces cannot load, the menu keeps the choice available for retry.
Attachments can remain in an attachment area or appear in the memo body. Visual media and motion media form a gallery, while audio and documents form rows below it. Saved attachments and new files share one order, so a person can place an uploaded file among existing files before saving. An edited drawing keeps the place and name of the attachment it replaces. The editor supports visual previews, audio transcription, reordering, removal, inline placement, and drawing edits. Saved memos present visual media as a gallery, audio as a playback row, and other files as downloads. Locations open as read-only map content, and relations show both referenced memos and backlinks.
References: web/…/EditorToolbar.tsx• L53-63 web/…/AudienceMenu.tsx• L22-42 web/…/AudienceMenu.tsx• L88-141 web/…/InsertMenu.tsx• L125-176 web/…/useLinkMemo.ts• L23-79 web/…/LinkMemoDialog.tsx• L20-75 web/…/EditorMetadata.tsx• L19-70 web/…/attachment.ts• L6-20 web/…/attachment.ts• L22-40 web/…/attachmentOrder.ts• L4-25 web/…/attachmentOrder.ts• L42-68 web/…/AttachmentListEditor.tsx• L147-277 web/…/AttachmentListView.tsx• L149-225 web/…/MemoMetadataRows.tsx• L10-39 web/…/RelationRows.tsx• L15-73
Draft recovery and save flow
New memo and comment drafts stay in the browser while the session is open. The draft is tied to its identity: an edit, a comment parent, or a new-memo scope and Space. Text, attachments, audience, Space, location, timestamps, attachment order, accepted suggestions, and the writing position can return when the same session opens again. Existing memo edits start from the saved memo instead of a local draft.
Saving validates the draft, waits for uploads, recordings, transcription, and inline image insertion to finish, then creates or updates the memo. New files upload before the memo is created. An edit of a saved drawing uploads the replacement after the memo change, so the attachment keeps its name and place. If a file reaches storage before a later save step fails, it stays with the draft for retry. Uploads that begin in the text are not saved as editor content; their visible progress and failure actions stay attached to the source block until the person retries or keeps the file as an attachment.
The save flow connects the local draft to the memo service and then refreshes the visible memo surfaces. The service compares an existing memo with the draft and sends only changed content or metadata. A save with no changes reports that state and closes the edit path. After a successful save, the draft is cleared, the composer resets, and the feed can place a new top-level memo at the front while list data catches up. A host-owned edit or comment closes after the save succeeds. Save errors use server, quota, or general error text when available; a drawing replacement can remain pending for another save.
sequenceDiagram
participant P as Person
participant E as Editor session
participant D as Browser draft
participant U as Attachment service
participant S as Memo service
participant V as Memo views
P->>E: Write or edit memo
E->>D: Keep new draft state
P->>E: Save
E->>U: Upload files or replacements
E->>S: Create or update memo
S-->>E: Return saved memo
E->>D: Clear saved draft
E->>V: Refresh lists and related views
References: web/…/README.md• L32-36 web/…/README.md• L52-58 web/…/EditSession.tsx• L114-123 web/…/EditSession.tsx• L205-216 web/…/useMemoSave.ts• L53-84 web/…/useMemoSave.ts• L97-176 web/…/memoService.ts• L127-200 web/…/uploadService.ts• L12-81 web/…/validationService.ts• L11-52 web/…/types.ts• L8-43 web/…/reducer.ts• L4-119 web/…/useDrawing.ts• L25-112 web/…/uploadAnchors.ts• L32-71
Memo reading
Memo reading uses one card model in feeds and detail pages. The card presents time, creator and context labels, rendered content, associated items, reactions, comments, and actions that match the person's access.
Memo cards and content
A compact card bounds the body and associated content behind one reveal action while keeping reactions available. A full detail view shows the complete memo. A permitted person can replace the body with an inline editor while the card frame and its surrounding context remain in place, then return to the card after the edit.
The card header connects the memo's time to its permalink and shows the creator, visibility, Space, reaction, and action controls according to context. The creator leads to that person's memo collection, while the time can show relative, local, or updated time. Its tooltip gives the full created and updated values. The header hides actions during inline editing so the editing surface remains the single active control area. On the memo's own detail route, the time is plain text instead of a link to the same page.
The read-only content surface uses the same Markdown language as the composer. It renders headings, lists, links, code, tables, tasks, images, tags, mentions, and math. Known mentions open the person's page, tag clicks apply a collection filter, and bare web links can become nearby preview cards when the person's link-preview setting allows it. The preview loads near the viewport and falls back to the normal link when useful title or description data is not available. An image that fails to load also returns the link to its normal form. Sensitive content keeps the body and associated content hidden until the reader chooses to show it.
In-page anchors scroll within a full memo. In a compact card, a heading or footnote link opens the detail route because the target may be hidden below the clamp. The content surface also lets a person who can manage the memo tick task items; the changed Markdown is saved through the memo update flow. Link-preview changes refresh the rendered blocks without a page reload. Code and Mermaid content keep readable source fallbacks, while tables and media remain usable on narrow or partially loaded views.
References: web/…/MemoEditor.tsx• L126-146 web/…/MemoContentView.tsx• L42-50 web/…/MemoContentView.tsx• L58-75 web/…/MemoContentView.tsx• L77-147 web/…/LinkMetadataCard.tsx• L20-70 web/…/MemoView.tsx• L35-117 web/…/MemoView.tsx• L183-224 web/…/MemoBody.tsx• L30-85 web/…/MemoHeader.tsx• L26-123 web/…/constants.ts• L3-15 web/…/index.tsx• L54-75 web/…/useMemoDecorations.ts• L52-125
Memo detail navigation
The detail page is the focused reading and collaboration surface for one memo. It loads a direct memo or a share-link memo, shows the parent when the item is a reply, and registers detail actions with the application sidebar.
URL hashes identify headings, footnotes, comments, and legacy comment anchors. The page waits until the target is present before scrolling to it. The detail sidebar adds a heading outline, comment entry, parent navigation, backlinks, and share actions. A normal detail page loads comments in pages; a share view is read-only and does not expose comments or private actions.
Share mode adapts attachment links for the shared reader and treats missing or unauthorized share tokens as not found. Direct unavailable memos also route to the not-found page. Parent loading can show a retry or unavailable state without blocking the memo itself.
References: web/…/MemoDetail.tsx• L92-137 web/…/MemoDetail.tsx• L143-213 web/…/MemoDetail.tsx• L215-300 web/…/MemoDetailSidebar.tsx• L100-203 web/…/MemoOutline.tsx• L21-96
Memo relations and attachments
Associated content stays next to the memo that explains it. Readers can preview visual media, play audio, download files, inspect a location, and open related memos without leaving the main reading context.
Relation sections distinguish memos that the current memo references from memos that reference it. The UI can show a stored snippet first and resolve a current summary near the viewport. A missing related memo is removed instead of becoming a dead link.
References: web/…/AttachmentListView.tsx• L149-225 web/…/attachmentHelpers.ts• L20-64 web/…/LocationDisplayView.tsx• L13-43 web/…/RelationRows.tsx• L15-73 web/…/useResolvedRelationMemos.ts• L6-23
Memo reactions and actions
Signed-in people can respond to a normal memo with an allowed reaction. The card groups reactions by type and shows the number of people for each type. A person can add or remove their own response from a reaction pill or from the reaction picker. The picker uses the instance's allowed reaction set and returns focus to its trigger after a choice or Escape. Archived memos and anonymous readers do not get write controls.
The action menu follows memo state and access. A writable memo can be edited, pinned, archived, deleted, copied, or opened. Task memos add a bulk action for open tasks. Archived memos offer restore and delete, while read-only memos keep open and copy actions. Comment actions stay in the parent memo context.
Copy can produce a memo link or Markdown content. A comment link includes its parent route and anchor, so it opens at the same comment. A memo moved between Spaces reports the move and returns from detail to the correct collection.
References: web/…/ReactionSelector.tsx• L19-85 web/…/ReactionView.tsx• L15-63 web/…/MemoHeader.tsx• L87-123 web/…/MemoActionMenu.tsx• L37-203 web/…/hooks.ts• L26-170 web/…/MemoCommentListView.tsx• L30-83
Change checklist
When these files or sections are changed, remember to consider these:
- Keep the shared Markdown language aligned between
MemoMarkdown, the composer extensions, and the read-only content view. A format change must not make saved content look different from the draft. - Keep editing-session identity aligned with draft keys, restored metadata, and cursor mode. A new scope or Space must not reopen another session's draft.
- Keep source mode aligned with its account setting, insert menu, toolbar, slash menu, suggestions, and task controls. Source editing must not expose rich-block actions that cannot work on plain Markdown text, and a failed setting update must restore the prior mode.
- Keep paste and drop file paths aligned with inline placement. A paste must remain an attachment, while a dropped image must keep its document position.
- Keep save validation aligned with content presence, managed image URLs, upload, recording, transcription, drawing replacement, and inline-image state. The save action must not submit incomplete content or replace a saved drawing before the memo change is accepted.
- Keep audience and Space rules aligned across the menu, draft state, create request, and update request. Replies must continue to inherit the parent's Space.
- Keep timestamp defaults aligned with calendar-selected dates and the create/update time fields. A date change must not leave the composer with a stale day.
- Keep insert-menu actions aligned with upload state and the editor's placement rules. Inline image input must not fall back to an attachment-only path, and drawing edits must use the replacement path when the person can manage the saved attachment.
- Keep linked-memo search scope, current-memo exclusion, and existing-relation checks aligned. A link dialog must not offer a self-link or allow a duplicate relation.
- Keep compact-card anchor behavior aligned with detail routing. A hidden heading or footnote must still open at the correct detail target.
- Keep relation direction and resolved summaries aligned. A reference must not become a backlink, and a deleted memo must not remain a live row.
- Keep detail share mode aligned with attachment links, comment access, and not-found handling. A shared memo must remain readable without private actions.
- Keep mutation refreshes aligned across lists, detail content, comments, attachments, and account summaries. A saved or changed memo must not remain stale on one surface.
- Keep editor layout states aligned with focus mode, source mode, upload anchors, and the editor's floating controls. A visual state change must not hide the caret, file status, or usable menu surface.
- Keep the shared attachment order aligned across saved attachments, local files, edited drawings, upload results, and the final memo request. A reorder must survive upload and replacement without moving an item to a different place.
- Keep upload-anchor status aligned with the upload service and editor content. A failed in-text upload must offer a valid retry or attachment fallback without becoming saved memo content.
- Keep recorder, waveform, and transcription state aligned with save validation. The commit action must stay blocked until the resulting audio or text is ready, and the recording status must remain clear while capture is active.
- Keep memo-view filter, persistence, and active-filter cleanup aligned. A saved or deleted view must not leave the sidebar or collection using an invalid rule.
- Keep link-preview setting changes aligned with the content-view refresh. A reader must not need to reload the page to switch preview behavior.
- Keep reaction availability aligned with instance settings, archived state, current-user access, and picker focus. A reaction control must not offer a choice that the instance does not allow or remain interactive for an archived memo.
- Keep memo header time links aligned with detail routing and navigation state. A time control must not create a useless self-link on the memo's own page.
Important failure modes
| Trigger | Consequence | Guard |
|---|---|---|
| A new draft uses a key that does not include its scope or Space | Content from one composer can appear in another | draftKeyFor gives each edit, comment, and new-memo identity its own key |
| A local draft is cleared before the memo save succeeds | A failed save loses the person's work | useMemoSave clears the draft only after a successful result and keeps completed uploads for retry |
| Save starts during upload, inline image insertion, recording, or transcription | The memo can miss files or contain incomplete inline content | validationService blocks save while these states are active |
| A dropped image loses its document position | The image appears only as an attachment or in the wrong place | EditSession sends drop position to inline image handling and keeps paste as attachment input |
| An inline image upload partially fails | The draft can contain missing image references or lose already uploaded files | Upload anchors offer retry or keep-as-attachments, and save retains completed uploads after later failure |
| A Space is removed while visibility remains Space-only | The save request contains an invalid audience and destination pair | EditorToolbar changes visibility to Private when it removes the Space |
| A Space list fails while the audience menu is open | A person cannot remove an old placement or choose a valid destination | AudienceMenu keeps the current placement visible and offers a retry item for the Space list |
| Source mode keeps rich-editor controls active | A person can use actions that do not apply to source text | EditorContent and the source-mode state hide rich controls and parse needed text from Markdown |
| The account source-mode update fails after the UI switches | The editor can show a preference that the account did not save | useSourceMode restores the prior setting and reports the error |
| A timestamp field accepts an invalid date | The draft can show a date that the timestamp contract cannot represent | TimestampPopover validates the complete date before dispatching it and marks invalid input |
| Audio recording is unsupported or microphone access is denied | The composer cannot create a voice attachment or transcription | useAudioRecorder reports unsupported and permission errors and resets its recorder state |
| An inline image is inserted through the attachment path | The image is saved without the intended position in the memo | InsertMenu uses a separate image input and EditSession routes it to inline image handling |
| Focus mode does not reserve the original editor height | A grid or page can jump when the fixed editor leaves its old place | useFocusMode measures the normal frame and EditSession renders a placeholder while focus mode is active |
| A compact card handles an anchor as a local scroll only | The target stays hidden below the card clamp | MemoContentView routes compact anchors to the memo detail page |
| Link metadata is treated as required content | A normal link can disappear when the preview service has no useful data or its image fails | LinkMetadataCard falls back to the original link |
| A share token is missing or unauthorized | A private memo can appear as a partial shared page | MemoDetail treats not-found and unauthenticated share results as 404 and keeps share mode read-only |
| A relation summary is stale or cannot resolve | The reader sees a dead link or the wrong relation direction | Relation rows separate direction and remove unresolved related memos |
| A list mutation refreshes only the detail query | Feed cards show old text, metadata, or actions | Memo mutation handling patches matching list entries and refreshes affected queries |
| Focus or source layout does not reserve space for editor controls | Text or the caret can sit under a control, or the writing area does not fill the frame | Editor layout rules reserve source-mode space and expand the scroller only in focus mode |
| A memo-view filter is saved without validation | A named view can fail when a person selects it later | MemoViews validates the filter before create and requires a title and filter |
| A deleted memo view remains selected | The collection can keep using a rule that no longer exists | MemoViews clears the active view when its selected view is deleted |
| A link dialog does not exclude the current memo or existing relations | A person can create a self-link or duplicate relation | useLinkMemo filters the current memo and LinkMemoDialog disables already linked memos |
| A reordered local file keeps its preview key after upload | The saved memo falls back to natural attachment order | renameUploadedKeys changes local upload keys to attachment names before the next save or retry |
| An edited drawing is treated as a new attachment | The saved drawing loses its name or old place | Replacement files keep the replaced attachment key and memoService uploads them through the replacement path |
| An upload failure has no source anchor or fallback action | A person cannot tell which content failed or recover the file | renderUploadAnchor keeps the status beside the source block and exposes Retry or Keep |
| Audio transcription finishes after save starts | The memo can save without the recording text or attachment | EditSession mirrors recording and transcription work into shared save-blocking state |
| A drawing replacement fails after the memo update | The memo text and metadata save but the drawing stays old | DrawingNotSavedError keeps the replacement in the draft and asks for another save |
| Audio transcription downloads an oversized attachment | The UI spends time and data on a request the service will reject | transcriptionService checks the 25 MiB limit before and after download |
| An upload response is lost after a chunk is committed | A retry can create duplicate or corrupt attachment data | uploadService retries only the same unavailable chunk and checks the committed offset |
| A reaction picker uses a reaction outside the instance set | A person can request a response the instance does not support | ReactionSelector builds its choices from memoRelatedSetting.reactions |
| A reaction pill remains active for an archived memo | A reader can try to change a response that must be read-only | ReactionView disables its action when the memo state is archived |
| A picker closes without returning focus to its trigger | Keyboard users lose their place in the memo header or card | ReactionSelector restores focus after selection and Escape |
| A memo time is always rendered as a link | The memo detail page contains a useless link to itself | MemoHeader renders plain time text for the current detail route |
Key files
| File | Why to read it |
|---|---|
| web/…/MemoEditor.tsx | Defines the shared view, edit, new-memo, and comment entry points. |
| web/…/README.md | Gives the high-level model for the shared content and editing surfaces. |
| web/…/MemoMarkdown.tsx | Defines the common Markdown surface used by writing and reading. |
| web/…/useMemoDecorations.ts | Connects tag colors, known mentions, and read-only keyboard navigation to the shared content surface. |
| web/…/EditSession.tsx | Connects the draft store to metadata, focus mode, audio, suggestions, source mode, and save controls. |
| web/…/useSourceMode.ts | Keeps the Markdown source-mode choice in the account editor setting and restores it when the setting update fails. |
| web/…/Editor.tsx | Shows the editable Markdown surface and authoring extensions. |
| web/…/InsertMenu.tsx | Shows how authoring adds files, images, drawings, audio, relations, locations, and presentation modes. |
| web/…/useLinkMemo.ts | Defines memo-link search, self-link exclusion, and duplicate-relation checks for authoring. |
| web/…/LinkMemoDialog.tsx | Shows the search and selection surface for adding a memo relation. |
| web/…/EditorToolbar.tsx | Shows save validation, audience selection, Space placement, source-mode status, and commit actions. |
| web/…/AudienceMenu.tsx | Shows visibility and Space selection in one authoring control. |
| web/…/EditorMetadata.tsx | Connects attachments, relations, locations, transcription, drawing edits, and shared attachment order to the draft. |
| web/…/AudioRecorderPanel.tsx | Shows recording status, cancellation, stopping, and optional transcription controls. |
| web/…/VoiceWaveform.tsx | Shows the compact live waveform used during audio capture. |
| web/…/EditorSuggestions.tsx | Shows context-based draft suggestions for tags, task lists, and visibility. |
| web/…/TimestampPopover.tsx | Shows creation and update time editing and complete date validation. |
| web/…/editor.css | Defines the editor frame, focus layout, upload status, and floating editor surfaces. |
| web/…/constants.ts | Defines the shared focus-mode frame and transition contract. |
| web/…/uploadAnchors.ts | Shows how in-text upload progress and recovery actions appear at the upload source. |
| web/…/types.ts | Defines the draft's content, metadata, loading, attachment order, recorder, and suggestion state. |
| web/…/actions.ts | Defines the editor events for content, metadata, files, timestamps, loading, drawing, and reset state. |
| web/…/reducer.ts | Shows how editor actions change the shared draft state and reset it after save. |
| web/…/attachmentOrder.ts | Defines the order contract shared by attachment tiles, local files, replacements, and save requests. |
| web/…/useDrawing.ts | Shows how new drawings and edits to saved drawings join the memo save flow. |
| web/…/useMemoSave.ts | Shows validation, upload-aware saving, draft clearing, and visible-query refresh behavior. |
| web/…/validationService.ts | Defines the conditions that must be clear before a memo can be saved. |
| web/…/memoService.ts | Shows how draft changes, attachment references, Space moves, and drawing replacements become memo mutations. |
| web/…/uploadService.ts | Shows chunked attachment upload, replacement uploads, and retry behavior. |
| web/…/transcriptionService.ts | Shows audio size checks and the service path for attachment or recording transcription. |
| web/…/attachment.ts | Defines the common model for saved files, local files, grouped media, voice notes, and drawing replacement targets. |
| web/…/errorService.ts | Shows how save and media errors become useful user-facing messages. |
| web/…/MemoContentView.tsx | Shows read-only content, tags, mentions, anchors, task toggles, search highlights, and link previews. |
| web/…/LinkMetadataCard.tsx | Shows the metadata preview and plain-link fallback for external links. |
| web/…/PagedMemoList.tsx | Shows shared feed layout, pagination, new-memo placement, and list loading behavior. |
| web/…/MemoDetail.tsx | Shows direct and shared detail loading, parent navigation, comments, and URL anchors. |
| web/…/MemoViews.tsx | Shows creation, validation, editing, deletion, and help for saved memo views. |
| web/…/MemoView.tsx | Shows the card lifecycle, inline editing surface, sensitive-content reveal, and detail-context behavior. |
| web/…/MemoBody.tsx | Shows the compact reveal boundary between content, associated items, and reactions. |
| web/…/MemoHeader.tsx | Shows memo time links, creator and context labels, reaction entry, visibility details, and action placement. |
| web/…/constants.ts | Defines the shared visual contract for memo cards and time controls. |
| web/…/ReactionSelector.tsx | Shows the allowed reaction picker and its keyboard focus behavior. |
| web/…/ReactionView.tsx | Shows grouped reaction counts and read-only behavior for archived memos. |
| web/…/MemoActionMenu.tsx | Shows actions available for different memo states and access levels. |
| web/…/AttachmentListView.tsx | Shows saved attachment presentation and media access. |
| web/…/RelationRows.tsx | Shows reference and backlink presentation. |
| web/…/MemoOutline.tsx | Shows heading-based navigation in a long memo. |