Share a page by link

A document in LogiShell is a markdown file in your project, edited by the same editor as the code next to it. That is deliberate: your writing lives in git, with its history, and not in a second product.

It also means the text is on your machine. Sending someone a path is useless, and sending a copy in a message makes a second version of the truth an hour later. Publishing solves that: the page gets an address you can paste into a chat.

Publish it

Open the page, in the Docs surface or as a tab. In the line under the title, next to the page type and its path, there is Share.

One click publishes and hands you the link, which looks like app.logishell.com/d/<id>. Anyone who opens it sees the page: title, text, tables, code, nothing else. No sign-in, no LogiShell account.

What exactly is on that link

A copy, taken when you pressed the button. Not a live view of the file. This is not a shortcut: the file lives on your machine, and your machine goes into a bag, falls asleep, and loses wifi. A live link would answer 404 exactly when the person you sent it to opens it. The published page says which version it is showing and when it was published.

So after you edit the page, the link still shows the old text until you press Update the copy. The panel says so; the person on the other side does not have to find out for you.

Who can read it

Anyone with the link. The address is the only lock, so it is long and random, and the page asks search engines not to index it. Treat it the way you treat any link with contents: fine for a document you would show a colleague, wrong for a secret.

Stop sharing turns the link off. It does not hide the page from a list: the row is deleted, and the address answers "not published (any more)" afterwards. A revoked link that keeps working would be the worst possible version of this feature.

Two things it does not do yet

• Canvases are not published. A page by link is text. Rendering a .canvas.json as markdown would show a stranger a wall of JSON, so the button is simply absent on a canvas.
• A page on a desk without a project cannot be shared. Those documents live only on that device, and there is no project to publish them from. Connect the folder as a project first.

Where this is not the right tool

If you want a page with an address you keep, on a shelf people can browse, that is the public docs site, and its pages are markdown in a repository built by a deploy. Publishing by link is for one document and one conversation.