A post's detail
Posts carry tasks now, so a draft under review has more to show than its row can hold. A gives the post a scope of its own, as a project has: click the title of an expanded post (or its ⓘ) to open it, and ‹ to go back. B is the expanded row as built in 0.102.0, for comparison. The same draft, w42's manifesto, is in both.
Proposed (A)
- A post's scope, like a project's. ‹ goes back to the site. The title opens the post in its editor, as a project's name opens the project.
- One raised card for the post's state and links, folded by default (the user, 2026-10-23) to one line: the state, the date and how many tasks are done, with a bar. A click opens it. Its rows are State (draft, its date, the
working_on:note), Tasks (a count and a bar), Words (the body's count and its sections), Preview (the tape deck, opening this post's page), Site (View on Site, published posts only) and File (the path, with Show in Finder). Front matter goes in the ⓘ, as decided on 2026-10-21. - Its tasks below, grouped by
##section, the way Tasks groups a file's items. Each section's → opens the post at that heading (the user, 2026-10-23: the → used elsewhere to open a file). + beside "Tasks" adds one, with Add Task's chip picking the section, and a task's text opens the post at its line. - Focus, Open and Publish at the foot. Publish keeps its warning about open tasks. The focus card leads, as on every view.
- The expanded row stays for a quick look: its title becomes the way in, with a → after it.
Open questions
- Give a post its own scope (A), or keep the expanded row as the detail (B)? (A or B)
- If A, how do you get there: the expanded row's title (as here), its ⓘ, or both? (title, ⓘ, or both)
- Are the card's rows the right ones (State, Tasks, Words, Preview, Site, File)? (yes, or name what to add or drop)
- Should a post's scope be in the Posts scope menu too, under its site, while you're in it? (yes/no; recommended yes, like a project's scope)