Community and sharing

The Playbook's documentation contains official product guides. Community guides, blog posts, and research papers are separately published contributions with author attribution and licensing.

Publish an article

In Studio's community authoring area, write a Markdown document and supply its title, summary, kind, topics, authors, and license. Save a draft, review the exact text you intend to make public, then submit it for moderation. Changes may be requested before publication.

Publishing copies the reviewed document revision. Later source edits do not silently change the public article. Private source-document comments, workspace membership, and draft history are not copied to the public page. Remove private information from the article text itself before submitting it.

Reading published content is public. Draft editing and moderation require the appropriate account and permissions; private drafts and review queues do not appear in public navigation or search.

Import a workflow template

1. Browse the workflow catalog and inspect a template's graph, supported runtime, plugin dependencies, permissions, and license.
2. Import it from Studio into the intended destination project.
3. Review dependency and permission consent, then configure required placeholders with your own values and credentials.
4. Inspect the resulting workflow and run it when ready.

A template is an immutable snapshot. Import creates an independent copy and does not execute it. Credentials, private environment values, source execution history, and private workspace discussions are not included. An imported workflow does not receive automatic changes from the original author's workspace.

Keep project documentation private

Project documents and Design Doc drafts remain in their existing workspace scope. They do not become public simply because they are Markdown or because the project has a Documentation tab. Use the explicit publication and review flow when you intend to share an article or template publicly.