From Document to Everywhere

Part 7 of 7: Documents in the Wild

Back to Nadia from Part 1, who moved her newsletter out of a pile of half-synced docs and into one searchable room. She has been writing in that room for six posts now. This last one is about getting the writing out of the room, because a finished document does not have to stay a private document. It has two exits, and neither one makes you retype anything.

Exit one: make it a page anyone can read

The first exit is the Make public toggle, the one that lived in the Share modal back in Part 5. Flip it on and your document becomes a real, read-only web page on your profile, at a clean /user/<name>/documents/<id> URL. No login wall, no account required for the reader. You can hand that link to anyone.

The public, read-only view of a document on the author's profile: logged-out site chrome with Login and Sign Up, a breadcrumb, and the rendered document with a Print button

The reader's view. Logged out, no account, just the rendered document and a Print button.

The nice touch is that the private link keeps working too. If someone who is not the owner opens the internal document URL, they get redirected to that public page instead of hitting a wall, so an old link you shared before you flipped the switch does not rot. Nadia publishes an essay, drops the public link in a post, and anyone can read it for free. She paid to write it; the world reads it for nothing.

Exit two: spin it into a list

The second exit is the one people do not expect. In the document header there is a Create menu, and it turns the document you are looking at into something else: To List, To Doc, or To List & Doc.

The document editor's Create menu open, showing three options: To List, To Doc, and To List & Doc

The Create menu. A document is not a dead end; it is a source you can materialize into a list or a fresh doc.

To Doc forks a fresh copy, which is how a template-shaped document becomes a working one without disturbing the original. To List is the interesting one: it takes your document and materializes it into a structured List, the custom relational table type this product is built around. Nadia's long "books I read this year" document, all prose and bullet points, becomes a List with rows she can sort, filter, and add fields to. The writing was the thinking; the list is the thing she can actually query later. And To List & Doc does both at once when you want the readable version and the structured version side by side.

The quiet exit: it was always a file

There is a third way out that barely counts as a feature because it was true the entire time. Your document's body is Markdown, stored as a real .md file. That is the most portable format there is. Copy it into anything, keep a plain-text backup, move it somewhere else entirely. Nothing you wrote is trapped in a proprietary blob. The room has a door, and the door was never locked.

That is the series. A message is a box you throw a thought into. A document is the room you go to when the thought needs to grow up: structured, formatted, foldered, shared with real roles, co-edited live, and then published or spun into the next thing. Seven parts, one feature, and a lot of reasons to open the editor.

If you have been reading along, go write something too long for a post. That is what the room is for.

Adron