Share the reason, keep the reveal

SHARING DESK / SPOILERS & CONTEXT

A collection can explain why a game mattered without explaining its ending. Treat the finished file as a new reading experience, separate from the private draft.

First decide what the reader already knows

A board for friends who finished a game differs from an introduction for someone who has only seen the title. For a general audience, write about the way you played, the question it raised, or the mood it left behind. If a particular reveal is essential to your note, mark that note as a spoiler.

Original fictional editing examples
Revealing draftA shareable alternative
The station keeper is your future self.I kept revisiting the meaning of the early conversations.
The final island was inside the lantern.The journey made small objects feel unexpectedly important.
I cried when the guide disappeared.I became attached to the company along the way.

These sentences are writing exercises about invented situations, not claims about real games.

A spoiler mark covers a note, not the whole board

Marked notes are hidden from export by default. Include them only when you explicitly choose to reveal spoiler notes for the intended audience. A spoiler setting cannot recognize a revealing title, an ending screenshot, a character name in artwork, or the implication of an unusual ordering.

  1. Read the board title and each game title first.
  2. Mark revealing notes, or rewrite them without the reveal.
  3. Inspect every image at full view, including small background details.
  4. Review the export preview with spoiler notes hidden.
  5. Open the downloaded PNG and check the result again. Repeat for a caption or print output if you use it.

Give the public version its own identity

Duplicate a board for sharing when your private notes carry details you want to keep. A title such as “Year in games — sharing copy” makes that purpose clear. Keep the source board and its JSON backup private. Removing a note from a picture does not remove it from an editable backup.

Do not send a JSON file as a convenient substitute for a PNG. JSON can contain hidden spoiler notes, personal text, and processed images. It is not encrypted. A template application link carries a template ID, not your finished story. Following it opens a confirmation to create a separate blank work; it does not publish anything.

Read the file as a stranger would

Check whether a caption mentions a person by name, whether a photographed screen includes a username, and whether the board title implies an ending. Then decide where to share the actual file. The studio does not post to social networks or create a public profile for you.

For a useful opening line, try: “Nine games that changed the way I explore. Unranked; notes about endings are hidden.” That explains scope and reading order without asking the reader to guess.

Make a retrospective to share

Keep creating

Back to the studio ↗