Production Playbook

building a production playbook for your team the problem most teams share comfyui workflows by exporting json and dropping it in slack, google drive, or a shared folder that works for a while then someone runs an old version someone else can't find the workflow they need the model files don't match nobody knows which workflow produced last week's deliverable a production playbook solves this it's a single page where your team finds the workflows they need, the documentation that explains them, and the examples that show what good output looks like what a team page is a team page on floyo is a private landing page visible only to your team members think of it as an internal homepage you build it with blocks headers, rich text, workflow cards, image galleries, and custom html workflow cards are the key they're not links to json files they're live, runnable workflows a team member clicks one and it opens in the floyo canvas, ready to run creating your first playbook open your team home from the top navigation go to the pages tab and click the + card the page editor opens with a blank canvas start simple one header, a short description of what your team produces, and 3 5 of your most used workflows you can always add more later adding workflows drag a workflow block into the canvas select the workflows you want to include each one appears as a card with a preview image, title, and description team members can run any of them directly from the page good playbook organization group by use case (product photos, social content, video generation) or group by pipeline stage (input prep, generation, upscaling, post processing) add a header block above each group adding documentation use rich text blocks for process notes, style guidelines, or model requirements use gallery blocks to show reference outputs so the team knows what quality standard to hit publishing click preview to check the layout, then publish the page is now visible to all team members only team members it's not public you can password protect a page for an extra layer of access control useful if your team has contractors or external collaborators faq can i update the playbook after publishing? yes edits save automatically published pages are always showing the latest version who can create team pages? owners and admins regular members can view and run workflows from team pages but can't create or edit them is there a limit on how many workflows i can add? no add as many as you need for large teams, consider splitting into multiple pages by department or project