For developers
Stop building CMS schemas from scratch
You’ve built the same blog collection five times this year. The same case study structure, the same reference relationships. Trellis encodes those architecture decisions into expert-designed schemas — define it once, deploy it everywhere, skip the decisions you already know the answer to.
API-first
Webflow CMS API v2 + Airtable API integration
Trellis talks directly to the Webflow CMS API v2 and the Airtable REST API. No browser automation, no scraping, no fragile workarounds. Every operation is a documented API call you can inspect, log, and replay. Collections, fields, items, and references are all first-class objects.
POST /v2/collections
{
"displayName": "Blog Posts",
"singularName": "Blog Post",
"fields": [
{ "type": "PlainText", "displayName": "Title" },
{ "type": "RichText", "displayName": "Body" },
{ "type": "ImageRef", "displayName": "Hero Image" }
]
}Schema as code
Export your architecture as JSON
Every schema Trellis generates is a structured JSON object: collection names, field definitions, types, validation rules, reference relationships. Version it in Git. Diff it between environments. Review it in a PR. Your CMS structure becomes as auditable as your application code.
// trellis-schema.json
{
"version": "1.0",
"collections": [
{
"name": "Blog Posts",
"fields": [
{ "name": "title", "type": "PlainText" },
{ "name": "author", "type": "Reference" }
]
}
]
}CI/CD friendly
Deploy schema changes programmatically
Trellis schemas can be applied via API, meaning you can integrate CMS structure changes into your existing deployment pipeline. Push a schema update, run it through staging, promote to production. No manual clicking in the Webflow Designer to add a field.
# .github/workflows/cms-deploy.yml
- name: Deploy CMS schema
run: trellis apply --schema ./schema.json
--site ${WEBFLOW_SITE_ID}
--env productionIntegrations
Connect the tools your team already uses
Airtable, Webflow, Notion, Guesty, and CSV/Excel today. Google Sheets and more coming soon. Trellis normalizes data between platforms so you can swap sources without rewriting your content pipeline. One schema definition, multiple destinations.
Source connectors: ✓ Airtable — live ✓ Webflow — live ✓ Notion — live ✓ Guesty — live ✓ CSV / Excel — live ○ Google Sheets — coming soon ○ ClickUp — coming soon
Developer tools
Field type validation and relationship integrity checks
Trellis validates field types against Webflow’s actual constraints before writing anything. Multi-reference fields resolve dependencies in the correct order. Slug fields are checked for route collisions. Image fields enforce alt text requirements. You get a structural linter for your CMS.
Schema validation: ✓ Field type constraints ✓ Reference dependency order ✓ Slug collision detection ✓ Alt text enforcement ✓ Help text coverage ✓ Naming convention audit
Why not just use the API directly?
You could. Here’s what you’d build.
Field dependency resolution (references must be created after their targets)
Type coercion between source and destination field systems
Rate limit handling with exponential backoff
Idempotent sync state tracking per record and per field
Slug deduplication and route collision detection
Schema diffing for incremental updates
Trellis handles all of this out of the box. You focus on your application logic. We handle the CMS plumbing.