Sharing a project

The share sheet, who has access, what the link does, forking, and embedding a running circuit in a page.

The share sheet

Press Share in the header. It is one column, read top to bottom: who has access, what that access is, and the button that hands the link over. Everything sharing can do is on that one path.

People with access

At the top, a field placed Add people: an email address, a Can edit or Can watch choice, and Invite. Under it are circles for you and everybody in the room, and a + that puts the cursor back in the field.

Inviting by email needs a signed-in account, on any plan, the same as starting a room. What the plan changes is how many people the room holds: you and one other person on Free, five people on Pro and the student price, the whole class on Teacher and a school's plan. The mail carries the room's standing link for that role, so there is one thing to take back rather than two, and the reply goes to you and not to a noreply address.

Signed out there is nobody to add and nothing to add them to, so the sheet offers Sign in to publish instead.

Access level

One row with an icon and a sentence, and the sentence is the state:

  • Only you can open it. Where a project starts.
  • Anyone with the link can open it. The project is public, so it can also appear in the gallery at /projects.
  • Anyone with the link can watch live.
  • Anyone with the link can edit live.

The last two start a live room, and leaving them ends it. Signed out there is one line rather than a choice: Anyone with the link can open it, the project travels inside the link.

Public and private wait for the server before the row changes: what you read is what the account says, not what was clicked. A level that could not be reached puts the row back where it was and says why underneath.

While a live level is on, a small New link sits under the row. See watch links and edit links.

Somebody who joined a room they did not open gets their own state there instead: You are watching this live, with Ask to edit and Leave the room.

One full-width button. It says Copied for two seconds. Under it, Show link opens the link itself if you would rather read it or select it by hand.

The link the button hands over is the one for the level the row is on, so a watch link and an edit link are never mixed up.

Signed out, the link carries the whole project inside its own fragment. Nothing is uploaded; the link is the document. It works, and it can be long.

Signed in, the link points at the project on your account, at /p/<id>.

Opening someone else's project

It opens in the editor and runs, with no sign-up. The editor is read-only for it, and pressing Save forks it into a project of your own. The fork is named by the server, which adds (fork) to the original's name, and the heart count on the original stays with the original.

PNG, SVG and Embed

Three quiet lines at the foot of the sheet: Export PNG, Export SVG and Embed, described in exporting PNG and SVG.

Neither export has a plan gate: anybody, signed in or not, can press Export PNG or Export SVG and get the file. A Free account and a signed-out reader both get a small "made with mokxi.com" badge in the corner; Pro, Classroom and the student price pay it away, and so does being a student in a class whose teacher pays for Classroom or is inside the trial. Embed follows the same rule (what a paid plan buys there is the absence of the small Mokxi badge too), but it does need a saved, public project, because an iframe cannot point at something only you can open.

Exporting the file itself

Any project can be saved to a file and opened again later, on any machine, with no account. That is deliberate: a portfolio should not depend on us still being here in five years.