Tutorials

Tutorials turn the concepts in the Platform documentation into practical workflows. They are organized around Backfield's three connected applications: Agate, Stylebook, and the Backfield API.

How tutorials work

Each tutorial focuses on a task with a visible result. A page usually includes:

• what you will learn;
• what must already be configured;
• step-by-step instructions;
• screenshots of the relevant interface;
• a result to review;
• links to the underlying concepts.

Tutorials use a fictional Tutorial Organization, Tutorial Workspace, Tutorial Project, and Tutorial Stylebook. The names in your environment may differ, but the workflow is the same. Sample stories and records are kept separate from client data.

Within a section, tutorials often build on earlier work. Check Before you begin before starting, and follow linked next steps when you want the full sequence.

Agate

Agate is where you configure projects, build flows, process stories, and review article-level results.

Start with:

• Create and tour a project
• Build your first flow
• Run and monitor a flow
• Correct processed items

Organization administrators can also use the administration tutorials for users, AI models, integrations, and Stylebooks.

Stylebook

Stylebook is where editors maintain canonical people, places, organizations, metadata, connections, and review queues.

Start with:

• Import canonical records
• Edit canonical records
• Review candidate queues
• Check catalog quality

Backfield API

Backfield API tutorials show how to access project data from the API Playground or trusted software.

Start with:

• Create an API key
• Use the API Playground
• Query project data
• Search project data

API keys and responses are project-scoped. Use tutorial credentials and data for practice rather than copying keys or client content into documentation.

Concepts and tutorials

Use tutorials when you want to complete a task. Use the Platform documentation when you need to understand a feature, its data model, or its editorial implications. API endpoint details remain in the API reference.