Plays are the core unit of distribution on Playbooks. They can range from a small primitive or partial to a full application, and each one stays connected to a GitHub repository or subdirectory. Playbooks then organizes the project, presents it on the platform, and prepares it for deployment on our infrastructure.

Any signed-in user or team with access to the submission flow can create a draft. To publish publicly, your play should meet our product, deployment, and community standards, and your account should be in good standing.

Start by pasting a GitHub repository URL into the submission field. From there, you'll move through the guided flow for basics, repository connection, media, technology, demo setup, and final review. When the play is ready and the demo is working, you can publish it from the review step.

Playbooks gives your code a live, structured distribution layer. A published play can be discovered through taxonomy, evaluated through a working demo, previewed in the code explorer, shared through direct links or widgets, and monetized when you choose to charge for access.

Plays can range from small building blocks to layered, production-leaning applications. During setup, you'll choose the variant that best matches the scope of your project: starter, partial, template, stack, or app. The best submissions are clear, useful, and easy for another developer to evaluate.

You should have a connected GitHub repository, a clear title and description, cover media, and the legal rights to distribute the code. Public plays should also include a README, stay under 100MB, and successfully deploy on Playbooks infrastructure. A working demo is important because people should be able to evaluate software in a live state, not just through screenshots.

Yes. Private plays stay out of public discovery surfaces and can be shared directly by URL. This is useful when you want tighter control over distribution while still managing the play inside Playbooks.

Yes. You can keep updating your metadata, media, taxonomy, connection, and demo configuration after the draft is created. Once published, syncing will pull in the latest GitHub changes, but you should still verify that the updated play continues to deploy successfully.

No. Creating and submitting a play is free.

Submitting a play does not guarantee downloads or revenue. Plays that are respectful, well-presented, legally distributable, and actually deploy tend to perform best. If something is broken, unclear, or unfinished, it's worth tightening up before you publish.