Core Concepts

Key terms and concepts you'll encounter in Ploy.

Glossary

TermDescription
WorkspaceYour team's home base in Ploy. Contains your sites, documents, assets, brand design system, and integrations. Everything lives here.
SiteA website project inside your workspace. Each site has its own pages, components, and deploy history. You can have multiple sites in one workspace.
PloyA chat-based workflow where you collaborate with Ploy's Agent to get things done — build a page, run research, write copy, analyze performance. Think of it as a mission-focused conversation.
PloybookA reusable, step-by-step workflow Ploy's Agent can follow — written once, run on demand or on a recurring schedule. Use Ploybooks to codify the work you'd otherwise repeat by hand.
Ploy's AgentYour AI assistant. It lives in the Ploy dashboard and can build pages, write content, design layouts, run SEO research, analyze analytics, generate images, and more.
AgentAI workers that Ploy's Agent coordinates behind the scenes. When a task is complex, Ploy's Agent dispatches specialized agents to handle different parts in parallel — design, code, research, copywriting.
DeployA published snapshot of your site. Every time you publish, Ploy creates a new deploy. You can roll back to any previous deploy instantly.
Design SystemYour brand's visual DNA — colors, fonts, spacing, border radius, and other tokens. Stored in your workspace and automatically applied to every page and component.
BrandThe combination of your design system, logo, and company information. Ploy can extract your brand from an existing website or Figma file, or you can configure it manually.
AssetsImages, logos, and files stored in your workspace. Includes user uploads, AI-generated images, Figma exports, and website screenshots.
DocumentsMarkdown files in your workspace for research, plans, briefs, and content drafts. Ploy's Agent creates and edits these as part of its workflows.
PreviewA live, hot-reloading view of your site in the dashboard. Shows changes in real time as Ploy's Agent works.
PublishPush your site live. Deploys to Ploy's hosting infrastructure with automatic SSL. Add a custom domain whenever you're ready.
Custom DomainYour own domain (e.g. yourdomain.com) pointed at your Ploy-hosted site. Ploy handles DNS verification and SSL certificate provisioning automatically.
IntegrationsConnections to external tools — GitHub, Figma, Google Analytics, Google Search Console, Notion, Slack, HubSpot, and others. Configured in Settings.

Ploys

A Ploy is a chat-based workflow with Ploy's Agent — a mission-focused conversation where you describe what you want and it gets it done. Each Ploy has its own thread, plan, and artifacts (pages, documents, images, charts) so you can revisit the work later or hand it off to a teammate.

Inside a Ploy, Ploy's Agent can:

  • Build and edit your site — design pages, sections, and components; refactor layouts; apply your brand design system.
  • Write content — landing page copy, blog posts, ad creative, lifecycle emails, internal briefs.
  • Run research — competitor teardowns, audience research, positioning, SEO keyword analysis, market sizing.
  • Analyze performance — query Ploy analytics, GA4, and Search Console; build dashboards; surface enriched visitor data.
  • Generate and edit imagery — produce brand-aligned images, remove backgrounds, organize asset libraries.
  • Manage your brand — extract design tokens from a Figma file or live site, update the design system, manage logos and fonts.
  • Operate integrations — pull from Notion, sync GitHub, push to HubSpot, run Attio actions, and more.
  • Ship and route traffic — publish deploys, attach custom domains, configure routing rules and fallback proxies.

Tip: Each Ploy is scoped to one objective. Start a new Ploy when you switch contexts (e.g. from "redesign the pricing page" to "draft this month's blog calendar") so the thread stays focused and easy to find later.

Ploybooks

A Ploybook is a reusable, step-by-step workflow Ploy's Agent can follow. If a Ploy is a one-off conversation, a Ploybook is the playbook you save when that conversation is something you'll want to run again — same steps, same standards, same output shape, but with fresh inputs each time.

Common things teams turn into Ploybooks:

  • Recurring marketing ops — weekly SEO check, monthly analytics recap, quarterly competitor scan, end-of-week lead digest.
  • Content production — draft a blog post from a brief, repurpose a long-form post into LinkedIn + email, generate ad variants from a winning hook.
  • Lifecycle automations — process incoming leads from a webhook, enrich them, route to the right list, draft a personalized first touch.
  • Site maintenance — audit broken links, check Lighthouse scores, refresh testimonials from a CRM, sync a CMS into the design system.
  • Onboarding playbooks — set up a new tenant site, apply a brand from a Figma file, scaffold standard pages, publish a starter version.

Ploybooks are written in plain markdown — phases, steps, and instructions Ploy's Agent reads and executes. You can author them yourself, or ask Ploy's Agent to save a successful Ploy as a Ploybook so the workflow is captured and ready to re-run.

Triggering a Ploybook

Ploybooks can run three ways:

  • Manually — kick one off from chat any time ("Run our weekly SEO check").
  • On a recurring schedule — attach a cron schedule (e.g. every Monday at 9am, first of the month, weekdays at 6pm) and Ploy's Agent runs the Ploybook automatically. Schedules support any IANA timezone and can be enabled or disabled without losing their config.
  • From a webhook — wire an inbound endpoint to a Ploybook so every accepted event runs the workflow with the payload as context (e.g. Clay enrichment → generate a personalized ABM landing page per prospect).

Tip: Start a Ploybook by running the workflow once as a normal Ploy. When the output looks right, ask Ploy's Agent to "save this as a Ploybook" — it'll generalize the steps and tag the inputs that should be parameterized for future runs.

How They Fit Together

Workspace
├── Brand & Design System
├── Sites
│   ├── Pages & Components
│   ├── Deploys (publish history)
│   └── Custom Domain
├── Documents (research, plans, drafts)
├── Assets (images, logos, files)
├── Integrations (GitHub, Figma, GA4, etc.)
├── Ploys (chat workflows with Ploy's Agent)
└── Ploybooks (reusable workflows — manual, scheduled, or webhook-triggered)

Your workspace is the container for everything. Inside it, you create sites that are built from pages and components. Ploy's Agent works with you through Ploys — chat sessions where you describe what you need and it makes it happen, often dispatching agents for complex tasks. When a workflow is worth repeating, save it as a Ploybook so it can be run on demand, on a recurring schedule, or triggered by a webhook. Your design system keeps everything visually consistent, and integrations connect Ploy to your existing tools.

What's Next?