Every design lives in a project. A project keeps the cards, component collections, rules documents, artwork, layouts, and playtests for one game together. The project picker at the upper left is your workspace switcher: use it before you add or edit anything, especially if you maintain more than one game.
Start a project
From the project picker, choose New project, or open Projects and use its new-project action. Give the game a clear name; a description and logo are optional and can be added later. The guided first-project flow also asks for a genre, which helps set the initial context for the workspace.
After creation, ShuffleKit opens that project as your active workspace. Add cards, collections, documents, and images there rather than keeping early drafts in an unrelated test project.
Use the project overview as a checkpoint
Open Projects, then select a project to see its overview. It gathers the practical starting points for that game:
- project name, description, logo, and status;
- card, collection, and document counts;
- shortcuts to the Cards and Docs & Rules workspaces;
- recent or representative project content.
Use Edit details when the public-facing title, description, logo, or project status changes. It is a useful final checkpoint before a playtest, export, or print run, because it confirms you are working in the right game.
Switch safely
The project picker changes the active project without merging data. Before a large import, artwork generation run, or playtest, glance at its name and logo. If a screen says it has no content, first check that the picker still points to the project you expect.
For a deliberate handoff, make the project overview accurate, give the card collections readable names, and keep its rules in Docs & Rules. That makes the next collaborator—or your future self—able to orient quickly without changing your game data.
A simple workspace rhythm
- Create or switch to the game project.
- Capture its concept in Shufflo Ideator and its rules in Docs & Rules.
- Build the card and physical collections in Components & Collections.
- Return to the overview before testing, exporting, or publishing to make sure the whole workflow is scoped to this project.
Projects are the boundaries between games; collections are the boundaries between physical products inside one game. Keeping that distinction clean makes every later screen easier to read.
