Community Guidelines

Playbooks is a platform for creativity and knowledge sharing. These guidelines help keep the platform useful, respectful, and trustworthy.


Our Standard

We're committed to building a premium, curated, and safe ecosystem for developers at all skill levels. Published plays should be useful, presentable, deployable, and respectful of the broader developer community.


Publishing

If you publish on Playbooks, you are responsible for the code, assets, and claims attached to your play.

  • You must have the legal right to share, distribute, and monetize the code you publish.
  • Your play should be clearly presented and understandable to other developers.
  • Your play must follow our product requirements and community standards.
  • If we identify a policy, quality, or deployment issue, you are expected to address it promptly.

For the deeper product requirements, see Plays and Demos.


Deployment

Deployment is a core part of the Playbooks experience. We require internal hosting because working software is more useful than a static listing.

  • All published plays must deploy on Playbooks infrastructure.
  • All plays should include an interactive or visual way for others to evaluate the project.
  • When syncing a play, we automatically re-deploy it.
  • If a synced update breaks deployment, it's automatically removed from the marketplace until it is fixed.
  • Broken or unpublished plays can be managed through the web application.

Merchant / Account

  • Your account must be in good standing to publish a play.
  • Your account and merchant must be in good standing to receive transfers.
  • Your account and merchant must be in good standing to receive payouts.

For more, see Accounts and The Ledger.


Community Conduct

We expect participants to act in good faith and contribute to a healthy ecosystem.

  • Do not publish harmful, abusive, fraudulent, deceptive, or infringing content.
  • Do not use comments, messages, or profiles to harass, impersonate, or spam others.
  • Do not misrepresent what a play does, how it is licensed, or what users will receive.
  • Respect the broader community and the collaborative spirit of the platform.

Consumer Responsibility

Playbooks gives developers better tools to evaluate software, but you are still responsible for the code you take with you.

  • Review code, dependencies, licenses, and production-readiness before shipping.
  • Use your own judgment when adopting third-party software.
  • Treat downloaded code as something to evaluate carefully, not blindly trust.

Reporting and Moderation

We rely on the community to help identify both high-quality work and content that should not be on the platform.

  • If something appears offensive, harmful, fraudulent, or out of place, please report it.
  • Use the built-in reporting tools where available so our team receives the right context.
  • We reserve the right to remove content, restrict accounts, or take other moderation actions when necessary.

These Will Evolve

Playbooks is still growing, and these guidelines will evolve as the product and community mature.