Skip to content

docs: describe Logue as the workspace it is, not a writing assistant - #82

Merged
westerosweb merged 1 commit into
mainfrom
docs/workspace-positioning
Aug 30, 2026
Merged

docs: describe Logue as the workspace it is, not a writing assistant#82
westerosweb merged 1 commit into
mainfrom
docs/workspace-positioning

Conversation

@westerosweb

Copy link
Copy Markdown
Contributor

The README led with "Privacy-first AI meeting notes & writing assistant for macOS", and the
document half of the app was a single bullet list under AI Writing Editor — with spaces,
typed properties, relations, saved views and the document graph sitting at the bottom of
it, below tone analysis and vocabulary suggestions.

That reads as a meeting recorder with a text box attached, and it is how the app has been
described everywhere: in the repository description, in this README, and in the copy written
from it. What is actually in the source is a workspace.

What is there

Checked against the code, not the previous README:

Previously in the README In the source
Spaces not mentioned nested via parentID, with icons and colours
Properties "typed fields" in one bullet text, number, date, boolean, list
Relations "named links" belongsTo / has / relatedTo, inverses computed
Saved views "save any filter" 8 filter fields x 6 comparators, nested all/any groups, relative dates, regex
Blocks "block-based rich text" H1-H3, lists, quote, callout, code, table, divider, Mermaid, LaTeX
Templates not mentioned 55 built in
Document graph not mentioned Connect panel, grouped by how each item connects

The change

Split ✍️ AI Writing Editor into 📁 Documents & Workspace and ✍️ AI Writing Tools.
The workspace features were bullets 9-13 of a section headed "Writing Editor"; they are the
larger half of the app and now have their own section, with the block types spelled out and
the saved-view filter model described concretely rather than as "save any filter".

Added nested spaces, the document graph and the 55 built-in templates — none of which
appeared anywhere in the README.

Reordered the ten feature sections. Documents & Workspace previously sat below Tasks and
below three sections about where you can talk to the agent. The order is now workspace,
writing, meetings, tasks, agent, then the surfaces that reach it.

Header and Introduction rewritten to match, and the Logue/Views/ line in Project Layout,
which said "Meeting workspace, Writing editor".

One thing to weigh

The Introduction now says "If you have used Notion or Obsidian, you know the shape." It
orients a reader in one sentence, but it also frames the project against those products
rather than against the problem. Easy to cut if you would rather it stand alone.

Note on history

This commit was written on the docs/fingerprint-readme-images branch but pushed after #81
had already merged, so it never reached main and #81 shows only its own commit. This is the
same failure mode as #73. Cherry-picked onto a fresh branch off current main; no other
change is carried along.

The README led with "AI meeting notes & writing assistant", and the
document half of the app was one bullet list under "AI Writing Editor" —
with spaces, typed properties, relations, saved views and the graph
buried at the bottom of it, below tone analysis.

That reads as a meeting recorder with a text box attached. What is
actually there is a workspace: nested spaces, a block editor with tables,
callouts, code, Mermaid and LaTeX, typed properties, relations that
compute their own inverses, wiki links with backlinks and a graph, saved
views over eight filter fields and six comparators, an inbox, and 55
built-in templates. Meetings and tasks live in it; they are not the point
of it.

Split the section into Documents & Workspace and AI Writing Tools, and
order the features so the workspace comes first and the surfaces that
reach it come last. Header and Introduction rewritten to match.
@westerosweb
westerosweb requested a review from shanforge as a code owner August 30, 2026 03:11
@westerosweb
westerosweb merged commit 009a609 into main Aug 30, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant