Repository navigation
Create from…: entry points on documents, including a highlighted selection #14
Description
Activity
Implemented in the PR above (branch
issue/14-materialize-docs-entry). Closing here — review and any follow-up happens on the PR.This also answers the open question #15 left for the entry-point issues. The default column
sourceKeys are not published in the help centre or the OpenAPI spec, but the live web client's JS bundle contains the real Create-from window: for adocument/docElementssource the columns are Section / Text / Type withsourceKeysection/text/type, rows are elements filtered toheading|list-item(falling back to all elements), and the title/file-name defaults areCopy of X/slug-<id8>.md/X (selection). #12 and #13 can use the same source for the messages and lists spellings.The element-identity concern turned out to be a non-issue:
docElementscarriesdocumentId+markdown, so a selection's markdown is its identity — which is how #11 already modelled it. Nothing was invented.One bug in
:core:materializewas found and fixed while wiring this: without areset(), dismissing and reopening the same launch resurrected the previous success pane, becausestart()deliberately preserves edits across recomposition.- added a commit that references this issue
on Sep 16, 2026
Part of #10 — "Create from…" (materialize) — turn messages, lists, rows and documents into new lists/documents/posts
Web behaviour: Create-from works on a whole document and on a highlighted passage inside
the editor — highlight some markdown (headings, bullets) and use the Selection menu to turn
just that part into a list or a new document.
DocumentEditorScreenfor the highlighted range.are dropped.
Tests: heading/bullet → rows mapping; markdown → plain-text conversion incl. code-block
removal.
Filed from the parity review of
feature/parity-wip@14d7795against interlinedlist.com (OpenAPI/api/openapi.json, 233 paths) and the public help centre.