| name | bynder-bootstrap |
| description | Bootstrap a new Bynder deployment — portal architecture, metaproperty schema, derivatives, permissions, brand guidelines, integrations, with optional Contentful pairing. Orchestrator that sequences across the bynder-* skills end-to-end. Use this skill on greenfield Bynder stand-ups; do NOT run on deployments that already have thousands of assets and active conventions (use bynder-optimization-audit instead). |
| type | skill |
| project | skills-library |
| plugin | bynder |
| aliases | ["bynder-bootstrap"] |
| tags | ["type/skill","plugin/bynder","topic/bynder","topic/bootstrap","scope/orchestrator"] |
| status | active |
Bynder bootstrap (orchestrator)
Use the bynder-agent to orchestrate a greenfield Bynder stand-up. Pick the engagement shape first:
- Greenfield Bynder + Contentful (most common Slalom pattern) — full sequence below, ending in
bynder-contentful-pairing.
- Greenfield Bynder-only — same upstream sequence; downstream depends on which non-Contentful system consumes assets.
The flow runs 7 stages:
- Portal architecture —
bynder-portal-architect decides single portal vs. sub-portals vs. multi-account, custom domain, sandbox plan, cross-system mapping.
- Asset model —
bynder-asset-model designs the metaproperty taxonomy (6–10 facets), naming conventions, tag policy, asset-type scoping. Brand-team walkthrough is required.
- Brand Guidelines —
bynder-brand-guidelines stands up the module with the standard 8-section outline, embedded asset strategy, sync-with-design-system plan.
- Derivatives —
bynder-derivatives defines the pre-rendered set (10–20 max) aligned to design-system breakpoints, plus the dynamic-transformation preset map.
- Permissions and workflow —
bynder-permissions-workflow builds the 6–12 profile spine, group structure, IdP/SSO mapping, optional Workflow module setup.
- Integrations —
bynder-marketplace-connectors installs the Tier 1 adoption drivers (Microsoft 365, Slack, Adobe CC, Figma) and any Tier 2 systems in scope. For Contentful, route to bynder-contentful-pairing for OOTB install + custom UCV layering plan.
- Webhook plumbing —
bynder-webhooks-events wires asset-event sync to downstream caches. Required for any CMS pairing.
Pick the engagement level first (Low Touch / Standard / Complex per references/slalom-context.md) — this calibrates the choices in each stage.
Don't skip stages. Each builds on the previous. If the user wants to skip Stage 5 ("we'll figure permissions out later"), push back — permission drift on a deployment without a v1 model becomes the optimization engagement two years later.
After bootstrap completes, schedule the first bynder-sweep for ~90 days out as a validation pass.
Don't run bootstrap on a deployment that already has thousands of assets and active conventions — that's an optimization engagement. Use bynder-optimization-audit instead.
