Making a map

1. In Studio, press Create and choose Map. Give it a title, an optional description, up to seven tags, and set its visibility.
2. On the next step, search for the internotes you want in it, or none yet. Press Create Map when you are happy with the selection.

You land on the new map, ready to arrange. Nothing is fixed at that point — internotes can be added or removed whenever you like.

A map can also take its members from a folder of a connected GitHub repository, so that adding a file to the folder adds a node — see Publishing from GitHub.

The internotes step is optional. A map made with none is an empty canvas waiting for members: the arrange view’s Add Internote brings existing ones in, its New shortcut creates one for this map without leaving the canvas, and Connect to a folder in the details panel fills it from a repository — see Publishing from GitHub.

Maps go live on visibility alone. Make one public and it is findable in Explore and openable by anyone; keep it private and it stays between you and the people you have shared it with. There is no separate publish step to forget.

A map and the internotes inside it keep their own visibility independently. An unpublished draft sitting in a public map stays invisible to readers until you publish the internote itself — so adding something to a map never publishes it by accident.

A public map gives a reader the whole path from a single link, which is most of the point of making one.

For a private map, Share invites people by email with View or Edit access, and the map appears under Shared with me in their library. Sharing and permissions covers the detail.

A reader opening your map has their own controls: Bookmark, Rate and Share. Each node carries a mark for where they are with it — completed, up next, or not yet started — and a map offers a continue point, so returning readers do not have to retrace their steps to find their place.