VertcieDocumentation
Content Creation / content creation overview

Content creation overview

Category: Content Creation. Status: Normative.

Vertcie content is organized as spaces, boards, and cards. A card owns the authoring history and assets for one content unit. Model cards use a node workflow to describe configuration, geometry, materials, rules, and scene behavior; image cards use a versioned media workflow.

End-to-end model authoring

Create model card → upload/verify mesh assets → build workflow
→ assign options and materials → configure scene → preview selections
→ validate → publish immutable version → test runtime package
  1. Create or open a model card in the correct board.
  2. Upload model assets and confirm the intended active mesh version.
  3. Open the model workflow and establish one Product settings root.
  4. Add option sets and options that match how customers make decisions.
  5. Connect geometry and material behavior beneath the appropriate choices.
  6. Add signature rules only when an external configuration code must resolve to those choices.
  7. Configure the default environment, camera, ground plane, and visibility.
  8. Use View model to exercise defaults and representative combinations.
  9. Save the authored workflow, then publish a selected state as an immutable version.
  10. Verify the published version through the runtime—not only the authoring preview.

Content concepts

ConceptMeaning
CardOwnership, metadata, assets, workflow, versions, and collaboration boundary
WorkflowAuthored graph of nodes and directed connections
Option setA customer-facing decision group
OptionOne selectable value within a decision group
MeshGeometry made visible, hidden, transformed, patterned, or replicated
MaterialSurface appearance, including shader graph and texture mapping
SignatureOrdered external configuration data mapped to Vertcie selections
Working stateEditable workflow and current asset versions
Published versionImmutable runtime snapshot with its own identifier

Choose the next guide

Safety rules

  • Never edit a published version in place; publish another version.
  • Never delete an asset merely because it appears unused. Move it to Trash so it remains recoverable under the configured retention policy.
  • Treat display labels as editable copy. References and resolution use stable identifiers.
  • Preserve the imported production archive even when repairing a working workflow.
  • Test default state, every option group, representative combinations, signatures, materials, and missing-asset behavior before promotion.