DocsGetting started

Studio tour

The Studio is the workspace for a single game. Once your assets have generated a first draft, the game opens here and you spend the rest of your time refining it. Everything you change is just rearranging a physical table — taybl never enforces turns, score, or legality, so the Studio is about what is on the table and where, not about programming behaviour.

The header shows the game name, a status badge (Draft / Processing / Ready / Published), and — once the game is Ready — a Publish Game button. Below that sits the tab bar.

The five tabs

TabWhat it is for
PreviewPlay the table yourself. This is the most-tested play surface — drag, flip, and deal exactly as a player would, to sanity-check the generated game. Its Refine with Feedback box lets you describe a change in plain language and have the AI revise the table (see refining).
DetailsThe public-facing description: name, blurb, player count, and the cover that appears in the catalogue.
LayoutThe canvas editor. Select any zone or seat on the table and edit it in the inspector — role, scope, arrangement, visibility, size, and position. Components, the table itself, and setup placements all live here too.
SettingsA narrow form editor for the things the canvas does not show — name and players, setup automation, rules text, and decks. Split into the four sub-tabs below.
PublishShip the game to a public Game Home at its own URL, listed in the catalogue and playable online. You can keep editing afterward — edits to details and layout appear immediately. See publishing.

Preview and Layout share the same full-viewport table view; switching to Layout just opens the canvas editor over it. The active tab lives in the URL, so deep links and reloads land you back where you were.

The Settings sub-tabs

The Settings tab edits a local draft and validates it live against the same schema that gates AI generation, so you can never save a structurally broken game. A red badge on a sub-tab counts the validation errors waiting there.

Sub-tabWhat you edit
MetaName, player count, and play duration.
Setup automationShuffle / deal steps and starting component properties — what happens automatically when the table is dealt. See setup automation.
RulesThe plain-language rules text players read in the rules sidebar, plus objectives. See rules reference.
DecksBuild and edit decks of cards, including uploading a shared back image.

Components, zones, the table, and faces are not here — they are the canvas editor’s job, on the Layout tab.

Keeping a game current

If a game was generated against an older schema, a banner at the top of the Studio offers to Update game. This fills in new fields without redoing your hand-edits, and only calls the AI if a structural change forces it — see refining and regenerating.

Sign in to ask Pip about building games.
Sign in